infor

IMS Messaging Service

This method is used to retrieve the expected IMS API version and protocol parameters of the client application.

PROTOCOL :: Gets IMS API supported version and protocol parameters

This method returns the server availability status.

PING :: Ping Service interface, checks whether the server is available or not.

IMS Messaging Service v2

This method will be validating message request as per API specification and publish the message and returns whether the message is successfully published or not. The IMS via ION API Connector verifies if the calling request is done with the defined ION API Client Id. ION API swagger uses a different Client ID, so the test for this method will fail for this method.

MULTIPARTMESSAGE :: Publish message to ION via IMS

Test tenant service request contains the logicalId, documentName(optional) and tenantId as header parameter.It checks for entitlement and whether route exists for the mentioned document and returns success message or the error details in case of failure. The IMS via ION API Connector verifies if the calling request is done with the defined ION API Client Id. ION API swagger uses a different Client ID, so the test for this method will fail for this method.

TEST :: Test tenant and logicalIds registered or not.

This method will be validating message request as per API specification and publish the message and returns whether the message is successfully published or not. The IMS via ION API Connector verifies if the calling request is done with the defined ION API Client Id. ION API swagger uses a different Client ID, so the test for this method will fail for this method.
 The document content must be configured in the value field, in string format, and the JSON must be escaped. Encode the JSON string to BASE64 and send the BASE64 encrypted content as a string in the value field.

MESSAGE_V2 :: Publish message to ION via IMS

IMS Messaging Service v3

Accepted Documents service request contains the logicalId and tenantId as header parameter. It checks for entitlement, connection point active status and returns a list of documents configured in the IMS connection point or empty list if connection point is not in active state or it is not entitled to tenant. The IMS via ION API Connector verifies if the calling request is done with the defined ION API Client Id. ION API swagger uses a different Client ID, so the test for this method will fail for this method.

ACCEPTEDDOCUMENTS :: List out all accepted documents for a given tenant and logical id

This method will be validating multipart message request as per API specification and publish the message and returns whether the message is successfully published or not. The IMS via ION API Connector verifies if the calling request is done with the defined ION API Client Id. ION API swagger uses a different Client ID, so the test for this method will fail for this method.

MULTIPARTMESSAGE_V3 :: Publish message to ION via IMS

This method retains core "message" concept from the v2 version but now supports multipart form data. It offers the possibility of sending message payload in request body (of type multipart/form-data), mandatory and optional properties are now moved to headers and query parameters. This method will be validating message request as per API specification and publish the message and returns whether the message is successfully published or not. The IMS via ION API Connector verifies if the calling request is done with the defined ION API Client Id. ION API swagger uses a different Client ID, so the test for this method will fail for this method.

MESSAGE_MULTIPART_V3 :: Publish message to ION via IMS

Default

Api Ion Messaging Service

Infor API | Api Ion Messaging Service

Parameter Request File. The content type must be set to application/json. Mandatory fields are documentName, encoding, characterSet and fromLogicalId
 Example: 
{
  "documentName" : "Sync.SalesOrder",
  "messageId" : "message1",
  "fromLogicalId" : "lid://infor.ims.imsap",
  "toLogicalId" : "lid://default",
  "encoding" : "NONE",
  "characterSet" : "UTF-8",
  "accountingEntity" : "ae1",
  "location" : "loc123",
  "documentId" : "sdafas",
  "variationId" : 1,
  "revisionId" : "123",
  "batchId" : "infor.SSJE:1",
  "batchSequence" : 2,
  "batchSize" : 1,
  "batchRevision" : 1,
  "batchAbortIndicator" : true,
  "instances" : "1",
  "source" : "DB Connector",
  "custom_property1" : "value1",
  "custom_property2" : "value2"
}

Sections