The prerequisite for defining a “IMS via API Gateway” connector is to add and define Non-Infor API Suite in Cloud Multi-Tenant environment.
To add and define the Non-Infor Gateway suite, follow the steps below.
Go to API Gateway in the Infor OS menu.
Click Add for a new Non-Infor suite.
Click Create New to define a Non-Infor API suite with the details below.
Add a target endpoint and then provide EAM target endpoint with below details.
-
EAM target Endpoint URL : https://<eam host>:<port>/axis/imsservice. See the note below to find EAM IMS end point URL.
-
Proxy Context : eamims
-
Proxy Security : OAuth 2.0
-
Target Endpoint Security : OAuth 1.0a
-
Algorithm : HMAC-SHA256
-
Target Endpoint Access Key : tenant-specific Databridge IMS access key you will define in EAM in the section, Enabling Infor ION connection with IMS via API Gateway connection point using IMS Partner.
-
Target Endpoint Secret Key : tenant-specific Databridge IMS secret key you will define in EAM in the section, Enabling Infor ION connection with IMS via API Gateway connection point using IMS Partner.
You will need to determine the EAM IMS access/secret key values now to finish the
above steps although EAM IMS access/secret keys may not yet be configured in EAM at
this point.
To find EAM IMS end point URL, locate and copy AXISURL install parameter in EAM to some text editor and then replace “services/EWSConnector” with “imsservice”. The result will be the EAM IMS end point URL.
Add the attached (EAMIMS.json) documentation to the API Suite so that the services defined in the IMS endpoint are available for the ‘IMS via API Gateway’ Connector. User needs to edit the file to provide the tenant information in the documentation json before importing it into API Gateway as shown below.
The EAMIMS.json file is attached to this document. To access the file, browse to the left-hand menu
for this page, and then click 1 attachment. The attachments view opens with the selected document available for downloading.
The Edited swagger documentation should be imported into the API endpoint by clicking on the “+” in the Documentation section as shown below.
Provide the Name and Type as shown below and then browse to the edited EAMIMS.json file and click SAVE.
After importing the json file user should see the below swagger documentation with ping, protocol and v2/message operations as shown below,
Once the Non-Infor API suite with documentation is successfully created, ensure it is active and we are done with API Gateway configuration.
