About web services and Landmark applications

You can use pre-defined or define a web service that enables you to programmatically access Landmark business class data and actions based on standard SOAP/WSDL and REST/JSON formats to retrieve or update data. These actions are passed by the Infor ION API Gateway.

Provided as part of Infor OS, the ION API Gateway is integrated within Infor OS and Infor applications. It gives you the ability to use one domain, one authentication method, and a unified client code.

Every Landmark web service is accessible through the ION API Gateway. This means that every field of every screen of every Infor Landmark-based application is accessible through the ION API Gateway. This includes user-defined fields and user-defined business classes configured with Configuration Console.

The ION API Gateway is a server that acts as an API front-end to Infor products. It receives API requests and enforces throttling and security policies. The ION API Gateway passes requests to the back-end service, and then passes the response back to the requester. It includes a transformation engine to orchestrate and modify the requests and responses on the fly, and provides functionality such as the collection of analytics data and caching. You can use the ION API Gateway to support authentication, authorization, security, audit, and regulatory compliance.

Note: 

Previously provisioned Infor multi-tenant cloud instance customers not already using the Infor ION API Gateway must work with Infor Cloud Operations to provision the Infor ION API Gateway to their Infor multi-tenant cloud instances.

Landmark contains a full public web services API, including public API documentation (https://<deployment>/hcm/soap/doco/html/api) and full swagger list (http://<deployment>/hcm/soap/doco/swagger). You must have Infor OS Portal or Infor Ming.le installed to view the Swagger API documentation.

Inbound web services can be defined or dynamic:

  • Defined web service: define a web service using the web service builder application, which is part of the Configuration Console. Once a web service has been defined in Configuration Console, you can invoke it via standard protocols.

  • Dynamic web service: do not require a web services builder definition in the Configuration Console. The service works by URL convention, using the Infor ION API Gateway. The response will include the fields that are in the request.

Outbound web services:

  • Infor Process Automation (IPA) web service activity node: the IPA Web Service node has a built-in wizard to aid in the construction of the SOAP XML that is sent to the web service, and a built-in output wizard to let you know what XML elements are expected as output. That information is retrieved from the web service’s WSDL document. For more information, see Infor Process Designer User Help.

  • Web Services Interface (WSI): use LPL to create a .wsi file to call the service. This requires knowledge of Landmark Pattern Language (LPL).

  • FTP client: abstraction/communication layer for ftp.