- 3 minutes to read

Endpoints

System Integration Solutions typically communicate by sending messages over a physical transport medium as part of a conversation. Participants agree on the protocol and security policies to use. Information about these transport channels is managed in Nodinite as Endpoints.
Endpoints Overview Example list of Endpoints filtered by the Nodinite BizTalk Server Log Agent.

All Nodinite Log Events include mandatory and essential information about the Endpoint. This is crucial for documentation and for understanding your Systems Integration Solutions within your service portfolio.

Tip

Notice the last column; it provides information about the last known logged event.

An Endpoint must have a user-friendly name and an address (URI). Endpoints are unique in their composition of the following fields:

  • Name – The name of the Endpoint. This should be user-friendly.
  • URI – The address of the Endpoint. This is the actual address used on the wire.
  • Direction – The direction for the Endpoint. Is this an inbound or outbound message?
  • Endpoint Type – The type of Endpoint. How is the information sent on the wire? Which protocol is used?
  • Log Agent – Information about the source for this Endpoint. What is the ID?

Manage Endpoint
Here's an example of a BizTalk Server Endpoint with additional tracking information provided.

Repository

End-users with sufficient permissions manage the Nodinite Repository Model and assign relationships between Services and Contracts.

An example follows:

  1. Service A in the source System creates a message (file) and writes it to the file system.
  2. Service B in the destination System reads the message using the SFTP protocol.
graph LR subgraph "Service A" EA[File based Endpoint] end subgraph "Service B" EA--> |Message with a Message Type and Direction| roSB[FTP Based Endpoint] end

Furthermore, an Endpoint can be part of a Transport Contract (log point) in Services and Contracts.

Custom Metadata

As with all entities in the Nodinite Repository Model, an Endpoint can have any number of Custom Metadata fields assigned.

Custom Fields

Similarly, an Endpoint can have any number of Custom Fields assigned.

Origin of Endpoints

Endpoints originate from the process of logging. For example:
Log Agents using the Log API: See the Asynchronous Logging user guide for details.

Endpoints are automatically created by the Logging feature and are displayed in the overview.
All logged messages are processed by the Logging Service. During processing, the Endpoint is defined and becomes well-known.

Info

Nodinite Messages (Log Event) must include information about the Endpoint (and the Message Type).

Statistics

Nodinite provides persistent, built-in statistics about Endpoints. A compelling feature is that all MessageTypes recorded on that Endpoint are listed.
Endpoint statistics Here's an example of traffic statistics for the selected Endpoint.

Next Step

Add or manage Endpoint.

Custom Fields
Custom Metadata
Endpoints Overview
Integration
Log API
Log Views
Logging Service
Service
System