Logical Id

Logical Id provides a name for the instance of an application connected to ION. As the sender and or receiver of all messages, the application instance is identified by its Logical Id.

Applications must ensure that the Logical Id used in the message matches the Logical Id defined in ION.

Logical Ids are also used to drill back to an application in an environment.

The Logical Id has this format:

lid://[provider].[productcode].[ applicationinstanceid]:[Connection]/[path]

This list explains the Logical Id format:

  • lid:// - Schema name
  • provider - The name of the provider owning the application. For Infor applications use infor.
  • productcode - Unique identifier for an Infor product or ION connector type. Can refer to Infor applications such as ‘syteline’, ‘eam’ or ’ln’, or refer to technology connectors, such as ‘file’, ‘api’ or ‘database’.
  • applicationinstanceid - Identifier for an application instance, functionally behaving as one application. In ION it is derived from the connection point name or message listener name.
  • connection – Optional connection identifier for the application instance. Used if an application requires multiple connections.
  • path – Optional data section Identifier within the application instance. Used if an application makes use of internal routing.

Logical Ids are alphanumeric, maximum length is 250 characters. The only characters permitted in a Logical Id are the lowercase letters a-z, the dot(.), the digits 0-9, an underscore (_) and a hyphen (-)