Endpoints

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 agrees on the type of protocol and security policies to comply with. The information about this transport channel is defined within Nodinite as an Endpoint.

Overview 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
  • URI
  • Direction
  • End Point Type
  • Log Agent

EndPointExample Example of a BizTalk endpoint where additional tracking information is provided

Repository

An Endpoint can be part of a Transport Contract in either a Service or a Contract.

URI

The URI is expected to contain the filename like order123.json, %MessageID%.xml or *.xml if the last path is a folder than the path is expected to end with \.

An Endpoint is part of the [Repository Model][Repository] and can therefore also have Custom Meta Data and/or Custom Fields.

Origin of Message Types

Endpoints origin from the process of logging. There are 2 entry paths for messages:

  1. BizTalk logging, governed by the Logging Service.
  2. Log API (IBM Integration Bus, Mule, Custom code, Log4Net, .NET, Java, ...)

New Endpoints will be automatically created and is displayed in the overview. All logged Messages will be processed by the Logging Service. During this processing the Endpoint will get known. Messages are not allowed to be logged without the information about the Endpoint.

Next Step

Add or manage Endpoint

Endpoints Overview
Integration
Log Views
Logging Service
Log API
Custom Meta Data
Custom Fields
Service