System Integration Solutions typically communicate by sending messages on a physical transport medium to each other as part of a conversation. The participants in a conversation agree on the type of protocol and security policies to comply with. The information about this transport channel is defined within Nodinite as an Endpoint.
Example list of Endpoints filtered by BizTalk Log Agent
TIP: Notice the last column where you can easily find out when there was last communication on that port
An Endpoint must have a user-friendly name and an address (URI). The End Points are unique by their composition of:
- Name - Name of the endpoint
- URI - The address of the endpoint
- Direction - Direction for endpoint
- Endpoint Type - The type of endpoint
- Log Agent - Information about the source for this endpoint
Example of a BizTalk endpoint where also some additional tracking information is provided
The URI is expected to contain fine-grained information about the endpoint.
- For example, if this is a file pickup location the URI may be
*.xmlif the last path is a folder than the path is expected to end with
- For example, if this is a HTTP based weather service the URI may be
Endpoints origin from the process of logging. There are 2 entry paths for messages:
- BizTalk logging, governed by the Logging Service.
- Log API (IBM Integration Bus, Mule, Custom code, Log4Net Appender, .NET, Java, ...)
New Endpoints will be automatically created and are displayed in the overview. All logged Messages will be processed by the Logging Service. During this processing, the Endpoint will eventually get known.
Nodinite Messages (Log Event) are not allowed to be logged without the information about the Endpoint.