I'm looking for CRUD Java APIs for IoT Hub. I'm specifically looking for the java equivalent for this REST API (https://learn.microsoft.com/en-us/rest/api/iothub/iothubresource).
I was able to find APIs to create/register devices and send/receive messages but wasn't able find APIs to CRUD Azure IoT hub.
The Azure IoT Hub provided different endpoints for manipulate it. These endpoints can be classified as device, service, resource provider, etc(More detail about endpoints of Azure IoT Hub, please refer Azure IoT Hub endpoints).
And Microsoft provide the SDK in different lanuages for Azure IoT hub based on the different endpoints. For example, Microsoft provides C# SDK for Azure IoT Hub for the device and service endpoints named client library(refer here). And Microsoft also provides the C# SDK for the resource provider as Management.
However there is no JAVA SDK for the resource provider for Azure IoT Hub(refer here). You can use the REST in Java for resource provider endpoint of Azure IoT hub. The REST of CRUD Azure IoT Hub, you can refer the links below:
Create Or Update
Delete
Get
In-addition, if you also want Microsoft to provide the Azure IoT resource provider Java SDK, you can vote the feedback from link below:
Azure IoT Hub management SDK for Java
Related
I am working with a device that cannot include Azure IoT SDK. It can only send HTTO calls.
Is there any guide explain the simplest REST calls that allow my device send telemetry data to Azure IoT Hub?
Azure IoT Hub also offer the REST API to Send a device-to-cloud message.
The REST APIs for IoT Hub offer programmatic access to the device, messaging, and job services, as well as the resource provider, in IoT Hub. You can access messaging services from within an IoT service running in Azure, or directly over the Internet from any application that can send an HTTPS request and receive an HTTPS response.
You can use the Send Device Event for sending device-to-cloud message.
POST https://fully-qualified-iothubname.azure-devices.net/devices/{id}/messages/events?api-version=2020-03-13
You can go through the below documentations for more details.
Azure IoT Hub Device Rest API Operations and Azure IoT Hub REST API
My companys Services are a little bit complicated. Thats why my company demands that i write an NestJS API that requests the Data from the Azure Industrial IoT Services(those are APIs or hubs i dont realy know) for a particular job.
My problem now is, that i dont know how to authenticate nestjs to azure. So that i can request from those Azure Services the Data.
The structure of this project looks like this:
AZURE - Services are behind<--------->NestJS-Api + Postgres<---------->AngularApp
The nestJS-Api should have authorisation to request data 24/7(the whole time)
If you want to manage Azure services such as create/delete an Azure IOT hub service, you will need to get an access token by passport.js and call Azure management API.
But if you already have an Azure IOT hub service, you want to use this service by API, and you are facing the authentication issue, you can just refer to this official guide.
I and my team are trying to build an app for data visualization and analysis in WebApp the data source is from Stream Analytics Services,
can we connect to Stream Analytics from .NET core web app, if there is any way please provide reference resources.
what is the best practice or service to use for data stream if I am using WebApp?
Or can we connect to IOTHub from WebApp, which is a better option compared with the above one?
Thank you, Ranjith
Unfortunately, Azure Stream Analytics cannot stream data directly into a .Net core web app.
Option1: You can visualize data from your Azure IoT Hub in a web application.
Option2: If you want to use Azure Stream Analytics, you need to send the data into supported outputs and then connect to the Web app.
Reference:
Visualize real-time sensor data from your Azure IoT hub in a web application
Creating a simple IoT application using a RaspberryPi+ NET Core and Azure
What is the difference between SAP Netweaver Gateway and SAP JCo Adapters ?
SAP Netweaver Gateway Adapter:
IBM MobileFirst Platform Foundation applications can communicate with SAP Netweaver Gateway back-end services by using SAP adapters. Using HTTP rest calls and the OData protocol, applications can remotely create, retrieve, update, and delete entities through the adapter.
No additional middleware required to communicate with SAP system.
SAP JCo Adapter:
The SAP Java Connector (SAP JCo) is a middleware component that enables the development of SAP-compatible components and applications in Java.
Correct me if I am wrong.
The Service Discovery for SAP NetWeaver support enables the ability to codelessly generate MFP Adapters through exploring SAP sources and altering response data from SAP, through their Gateway product. Gateway is an extra layer of SAP middleware. For clients that have Gateway as part of their topology, this is a solid tool for generating custom mobile services.
The MFP JCo adapter provides support for writing custom implementation of service creation. This solution requires custom coding, using the JCo APIs, but is available for all SAP installations.
Summary, they are different animals that solve the same problem, in dramatically different way. Hope this helps.
am new to API LM & confused about Building APIs using tools such as apigee, 3scale, mashery, mulesoft, TIBCO APIX etc
all these years , I know API is all about a language's API or SDK which you use to write/build code/application to solve a business problem. Say Java API or J2EE API etc
Do I have to build my own dataservice using my application/system and expose it as a service (WS/REST) and use the above tools (apigee, 3scale, mashery, mulesoft ec) or does these tools allow a developer to Build APIs from the scratch?
In other words, do I create your own application within your enterprise (be it Java based, DB or a .Net service or a Web App hosted on weblogic) and expose it as API for B2D or DX (with auth, analytics, portal, developer access) which is called as "build an API"?
When using Apigee Edge, you must expose your backend as an http/https endpoint first. Then, you can add security, caching, quota, and many other features to your API facade. When using the Apigee-127 product, you can create an entire backend using Node.js locally and then deploy it to run in the cloud.