Setting up ION API for on-premise EAM - HxGN EAM - 12.0.1 - Feature Briefs - Hexagon

1. Log in to Infor® OS, and browse to Infor ION® API.

2. Click Add New API suite to create a new API suite.

3. Click Create New to create a Non-Infor suite for EAM.

   

4. Specify the Application Name, Suite Name, API Context, and Description.

   

5. Define the EAM target endpoint:

   • Target Endpoint URL: http://<eamserver>:<port>/axis/services, the url can be a http or a https url like https://inhywxxxxxxx.infor.com:447/axis/services.

   • Proxy Endpoint URL: EWS (can be any name).

   • Public Facing URL will be built with the above information.

   • Proxy Endpoint Security: Anonymous/Oauth 2.

   • Target Endpoint Security: Anonymous/Oauth 1a.

     

     If the user is using target endpoint security as Anonymous instead of Oauth 1.0 in the ION API suite, then the user must mention the Proxy endpoint security as Oauth 2 he cannot use Anonymous as Proxy endpoint security, if the User uses both Target Endpoint Security and Proxy Endpoint security then he may encounter an OIDC token Exception “com.dstm.mp.common.util.OIDCException: OIDC is not configured.”

6. You can use the public facing ION API URL to access the target endpoint from the client.

   https://<mingleserver>:port/<tenantId>/CustomerApi/<contextname>/<proxy_end_pointurl>

   https://inhyxxxxxxxxx.acme.com:7443/infor/CustomerApi/eam_api/EWS

   In the above URL:

   • Tenant is infor for on-premise deployments. For cloud deployments refer "For Cloud EAM" section

   • CustomerApi is a constant which is generated by the application.

   • eam_api is the context defined in the API interface screen shown in point 4.

   • EWS is the proxy endpoint URL name shown in the above screen shot.

     If you want to enable Oauth security for Target Endpoint and Proxy endpoint, see Option 2 in the "Security" section of this document.

For more information on ION API see the Infor ION® API Administration Guide.