EagleML REST API
The EagleMLApi library can execute the requests in Asynchronous or Synchronous mode.
The Asynchronous mode will receive the reply from EagleML API thru a callback. The EagleML API client sends a REST request to MC2 and waits for the Task Status Reply and the extract data to be delivered asynchronously when ready via a callback.
The Synchronous mode will execute the request and will wait for the TSR/reply on the same connection.
To use the library add the following dependency:
dependencies { compile 'com.eagleinvsys.eaglemlapi:eaglemlapiclient:1.2.0' }
In your gradle.build
script add:
repositories { maven { url "http://inno-artifactory/artifactory/libs-release" } }
Initialization
Before using the EagleML API for REST calls it should be initialized as described here:
The above should be executed only once. After that multiple requests can be executed concurrently on the eaglemlApi object.
To stop the eaglemlApi instance and clean up the resources run:
eaglemlApi.stop();
Executing the request Asynchronously
The requests can be executed only after EagleML Client API was started using the EagleApi.start() method.
The asynchronous requests can be executed in two modes - with an asynchronous callback or by waiting on Future<IEagleApiResult> object.
Waiting on a Future<IEagleApiResult> object
Asynchronous execution with a callback
Executing the request Synchronously
Command line interface for executing REST requests
Synchronous Mode
To enable synchronous mode enter in the console:
-execution=sync -rest
To launch a single request you can determine all necessary parameters directly in console with the "-data=" option, for example:
-data="httpMethod|httpPath|basecorrid|contentType|pathToFile"
contentType and pathToFile are optional.
When you want to launch several extracts or just want to read all parameters from a file, use the "-file=" option:
-file="C:\Users\User\Documents\my_config.txt"
In synchronous mode the client works like this:
- Sends a REST request.
- Saved response in the temporary folder with correlation id as its name. (temporary folder is the system %TEMP%, e.g., C:\Users\admin\AppData\Local\Temp\ - this folder is not purged automatically).
- The client will move to the next request on the list.
Asynchronous Mode
To enable asynchronous mode enter in the console:
-execution=async -rest
To launch a single request you can determine all necessary parameters directly in console with the "-data=" option, for example:
-data="httpMethod|httpPath|basecorrid|contentType|pathToFile"
When you want to launch several requests or just want to read all parameters from a file, use the "-file=" option:
-file="C:\Users\User\Documents\my_config.txt"
In asynchronous mode the client works like this:
- First of all, a callback is created. It is represented by a Jetty HTTP Servlet server which starts to listen on a random free port. You can set a timeout here, when it expires, the callback will be unregistered and the timeout error will be displayed. For example, a 5 min t/o:
-timeout=300
- The client then executes REST request. The request will contain x-eagle-rest-callback header with the IP address of the Eagle API client, the communication port and /eagleapicallback suffix, for example:
x-eagle-rest-callback: http://99.99.99.999:63345/eagleapicallback
- When the server receives a request with x-eagle-rest-callback header, it sends the TaskAcknowledged (ACK) message back to the client, performs the request, archives the result data, then tries to send a multipart message consisting of the TaskStatusResponse and the result data.
- The client receives the ACK and starts to await incoming multiparts (TSR+data).
- On multipart arrival it switched off the callback (the port is free now) and:
- Parses the TaskStatusResponse to understand if its task status is SUCCESS, FAILED or NO_DATA.
- If the status is SUCCESS, the result data will be uploaded as an archive file and saved in the temporary folder with correlation id as its name. (temporary folder is the system %TEMP%, e.g., C:\Users\admin\AppData\Local\Temp\ - this folder is not purged automatically)
- If a folder is specified in the “resultsdir” parameter, the result data will be unzipped and stored in this particular folder.
- If “resultsdir” is not specified or empty, the extract remains unzipped in the temp folder.
- If the status is FAILED or NO_DATA, error description will be displayed.
- If the multipart does not arrive before the -timeout expires, the callback will be unregistered and the timeout error will be displayed.
Available Settings
Name | Valid Values | Description |
---|---|---|
-login | username | Username to log in the environment |
EAGLEAPIPASS | password | Password for the environment set as a global system variable. Can be defined in the command line, for example: set EAGLEAPIPASS=my_password |
-resultsdir | empty or folder path | The folder in which unzipped result file will be stored. If not specified, the result will remain unzipped in the temp folder |
-csvmetricsdir | empty or folder path | The folder in which metrics will be stored |
-threads | even number, 1 or greater | Defines the number of separate threads for an async process. For each thread a separate listener are created. |
-endpoint | address of the environment | Endpoint address |
-file | file path | Path to the file with the query |
-execution | sync or async | Execution mode - synchronous or asynchronous |
Query File Details
The file with the query is selected by the -file command, for example:
-file="C:\Users\User\Documents\my_config.txt"
It should be formatted as follows:
httpMethod|httpPath|basecorrid|contentType|pathToFile
contentType and pathToFile are not necessaryoptional.
For example:
GET|/eagle/v2/manager-relationships?entityselectiontype=EntityID&entityselectionvalue=EMLFUN10&outputformat=XML|ABCDEF POST|/eagle/v2|ABCDEF|application/xml|test.xml
Example of Use
Synchronous Mode
In this example we launch EagleMLAPI Client in synchronous mode from the command line.
- Request is formed from this query:
-data="GET|/eagle/v2/manager-relationships?entityselectiontype=EntityID&entityselectionvalue=EMLFUN10&outputformat=XML|ABCDEF"
- To start execution we execute the following command:
SET EAGLEAPIPASS=eagle1 java -jar eaglemlapiclient-1.0.3-SNAPSHOT.jar "-data=GET|/eagle/v2/manager-relationships?entityselectiontype=EntityID&entityselectionvalue=EMLFUN10&outputformat=XML|ABCDEF" -execution=sync -login=eagleadmin -endpoint=http://sbnyl1312qa003.eagleinvsys.com:20427 -rest
Asynchronous Mode
In this example we are launching 2 asynchronous requests.
- Requests are formed from the request.txt query file located in testFolder:
GET|/eagle/v2/manager-relationships?entityselectiontype=EntityID&entityselectionvalue=EMLFUN10&outputformat=XML|ABCDEF GET|/eagle/v2/manager-relationships?entityselectiontype=EntityID&entityselectionvalue=EMLFUN10|ABCDEF
Two queries are executed in parallel (-threads=2)
- To start execution we execute the following command:
SET EAGLEAPIPASS=eagle1 java -jar eaglemlapiclient-1.0.3-SNAPSHOT.jar "-data=GET|/eagle/v2/manager-relationships?entityselectiontype=EntityID&entityselectionvalue=EMLFUN10&outputformat=XML|ABCDEF" -login=eagleadmin -endpoint=http://sbnyl1312qa003.eagleinvsys.com:20427 -threads=2 -rest