Choosing the right client
Axual offers multiple methods to get data in and out of the platform. Which method you choose depends on a number of factors. The overview below should help you make the right choice and get you started.
Connector Applications are your friend. Connector applications contain logic (and drivers) to connect to known systems, like JMS queues, and know how to read or write data originating from those systems to the platform.
Perform the following steps to see if you can proceed with a Connector Application:
Check if there is a supported connector available for your use case, see Supported Connectors. Is the connector listed? Proceed with step 2.
Log in to Self-Service and proceed with Creating a Connector Application. Is the connector listed in the dropdown? Continue creating the connector application using the documentation.
It seems that you will need an Application to get the job done. The application is created using Self-Service and is used to authorize requests to any stream it produces to and you need to create or extend an existing application to produce the data.
You need an Application to get the job done. The application is created using Self-Service and is used to authorize requests to any stream it consumes from and you need to create or extend an existing application to consume the data.
Check if the data you need is available on an existing stream. To see which streams are available on the platform, log in to Self-Service and click the "Streams" icon in the menu on the left. The following overview will be shown:
Create and deploy your consumer app by looking at the consumer examples for Java, .NET or Python or use a REST client (see below)
Once again you need an Application to get the job done, and it is created using Self-Service. And you need to define HTTP calls in the system that needs to produce or consume the data.
|the performance of REST proxy is limited in comparison to language specific clients (Java, .NET or Python). If you can use such a client, this is always preferred.|
|REST Proxy resources are shared by all applications. Maximum parallel throughput for REST proxy is 30 produce requests per second and 14 consume requests per second with a request size of 1 KB|