Testing the integration using Postman

Everything is prepared to send messages to ION CE using IMS via ION API.

To verify the correct working, you can use a REST client such as Postman API Client.

Complete these steps:

  1. Install Postman.
  2. Import on Postman the IMS v3 template.postman_collection.json file. This creates the 'IMS via ION API' project.
  3. At the root level of the newly imported project, edit the configuration.
  4. In the Variables section, add the values of the variables as you find them in the downloaded authorized app credential file.
    If you created a connection point with another lid than infor.ims.cp_myapp, then adjust the logicalId here accordingly. DO NOT include lid:// in the value.
    1. You must specify both, the initial value and the current value for the variables.
      Note: 
      • The defaults set in this Postman project are prepared for an ION CE integration. If you use your own Infor OS deployment, then you must adjust "oa" and "ot" to the values found in the authorized app credential file.
      • You can skip the properties that start with directIMS. These are used for the Oauth 1.0a integration.
    2. Save the changes.
  5. Right-click IMS via ION API (Oauth2.0) and click Edit.

    Scroll to the bottom of the Authorization tab and click Get a New Access Token.

    1. Request a new token.
      If the request is successful, then an access token is generated.
      Note: For "scope" you may have to define the value . Specify this setting if the response on the token request is "invalid_scope".
    2. In the response panel, select Use Token.
  6. You should now be able to successfully run these IMS methods defined in the Postman project:
    1. Gateway Health Check

      A basic check whether there is connectivity with ION API.

    2. ping

      A successful ping returns HTTP status code 200 and body: {"status":"OK","code": 200}.

    3. versions

      A successful versionsA successful response returns HTTP status code 200 returns HTTP status code 200 and body: {"supportedVersions": ["v1","v2","v3"]}.

    4. AcceptedDocuments

      An inactive connection point returns HTTP status code 412.

      A successful acceptedDocuments returns HTTP status code 200 and a body such as: {"logicalId": "lid://infor.ims.cp_myapp","acceptedDocuments": ["Confirm.BOD","Sync.SalesOrder"]}.

    5. multipartMessage

      An inactive connection point returns HTTP status code 412.

      A successful multipartMessage returns HTTP status code 202 and body: {"status": "OK","code": 202,"message": "The request was processed successfully"}.