What is a Service?

Use Nodinite Services to document, govern, and integrate your enterprise systems with clarity and control. This page shows you how to map, manage, and automate every service endpoint in your integration landscape for robust SOA and seamless operations.

✅ Precisely document every service endpoint and its relationships
✅ Enable flexible SOA integration and robust governance
✅ Visualize and manage dependencies, direction, and contracts
✅ Empower your teams to automate, monitor, and evolve integrations with confidence

Understand SOA architecture to maximize the value of the Nodinite Repository Model.

A Nodinite Service represents one end of a communication chain and, by definition, belongs to a Nodinite System.

A Service in Nodinite has a unique name and includes these pre-defined properties:

• System – Acts as either the sending or receiving side of the communication chain

• Direction – Choose one of the following:

  • Send – Send one-way, such as to a file system
  • Receive – Receive one-way, such as from a file system
  • Two-way Receive – Act as a Web Service being called by a consumer (Request/Response)
  • Two-way Send – Act as a Consumer calling a Web Service, this is the outbound initiating call (Request/Response)
  • None – Not set, should be avoided
  • Unknown – Enough said...

    Review the Endpoint Directions user guide for related information about Endpoints.

• Transport Contracts (log points)

  • Endpoints – Define how the message is transmitted.
  • Message Types – Define the type of message payload (Order, Invoice, etc.).

• Enforce restrictions within Log Views by configuring the Service properly.

  • Always include the Endpoints and Message Types for Nodinite to dynamically determine which Integration the message exchange belongs to.

Name your Service for clarity and management:

• SVC001 – Receive Invoices from Customer A
• SVC002 – Send monthly salary to the bank

Tip

Include a unique identifier such as SVC001 to make it easier to filter and manage a large number of Services, simplifying administration.

This naming convention helps you understand and manage Services. The examples above include several information elements: the transport of messages (found in Endpoints), the type of message (the Message Types 'Invoice' and 'Salary'), the direction, and the source or destination (System such as 'Customer A' and 'Bank').

Custom Metadata

As with all entities in the Nodinite Repository Model, a Service can have any number of Custom Metadata fields assigned, supporting flexible documentation and governance.

Custom Fields

Similarly, a Service can have any number of Custom Fields assigned, enabling tailored information management for your integration landscape.

Resources

^{New 6.0}

The System Administrator can add one or more Resources from Monitoring and assign them to the Service. Doing so presents the Service with the Monitoring State (the most severe state is shown) in the Integration Landscape.
Sample screenshot of the Interactive Landscape feature.

To add a Resource, Edit the Service, then click Edit on the Resources panel.

Example of an empty configuration.

Next, select any number of Resources.

Example with a Resource tied to the Service.

With Nodinite 6.1, you can also add Custom Metadata to Resources.

Transport Contracts

Transport Contracts define one or more log points. A Transport Contract is always a combination of one or more Message Types, Endpoints.

Simple log point example

The most basic example is a single specific message (Message Type), such as an invoice, that is received or sent on a specific transport location (Endpoint).

Here, the Transport Contract is a single log point with one Message Type and one Endpoint.

When you create a New Service, the list of Transport Contracts is empty. You can create new Transport Contracts from the management page, or if you are a Nodinite administrator, you can more easily bind logged messages to the Service.

Shared Endpoint example

Suppose the actual endpoint in use is a shared endpoint, such as a shared mailbox (info@company.com). To separate different flows of information for end-users, you can create multiple Services with different sets of definitions for Transport Contracts, filtering on relevant combinations of Message Types and Endpoints.

Here, the Transport Contract is a single log point with two Message Types and one Endpoint.

Multiple Endpoints for the Same Message Type example

Now imagine the same message (Message Type) is distributed across many different Endpoints (for example, the old production environment and the new production environment).

Here, the Transport Contract is a single log point with one Message Type and two Endpoints.

Add, Edit, or Delete Transport Contracts.

Read more about managing Transport Contracts on this page.

Next Step

Add or manage Service
Add or manage System
Add or manage Endpoint
Add or manage Message Types
Add or manage Integration

Related Topics

Repository Model
Message Types
Endpoints
Endpoint Directions
Systems
Integrations
Log Views