- 3 minutes to read

What is a Service?

You need to know the SOA architecture to maximize the usage of the Nodinite Repository Model.

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

graph LR subgraph "Service" roSystem(fal:fa-dice-d6 System) roService(fal:fa-cog Service)--- |1..1| roDirection[fal:fa-directions Direction] roTCS(fal:fa-dot-circle TransportContracts) roMessageType(fal:fa-file MessageTypes) roEndpoint(fal:fa-sign-in Endpoints) roService --> |1..1| roSystem roService -.->|0..*| roTCS roTCS -.-> |0..*| roMessageType roTCS-.-> |0..*| roEndpoint end

A Service in Nodinite has a unique name and contains information about the following other pre-defined properties:

System - either the sending or receiving side of the communication chain
Direction - one of the following
- Send - One-way send, like to a file system
- Receive - One-way receive, like from a file system
- Two-way Receive - Like a Web Service that is being called by a consumer (Request/Response)
- Two-way Send - Like 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 for Endpoints

Transport Contracts (log points)
- Endpoints - The data about how the message is transmitted.
- Message Types - The data about the type of the message payload? (Order, Invoice, ...).
Restrictions within Log Views can easily be enforced if the Service also is appropriately configured.
- A Service should include the Endpoints and Message Types for Nodinite to figure out which Integration the message exchange belongs to dynamically.

You should name a Service like this:

SVC001 - Receive Invoices from Customer A
SVC001 - Send monthly salary to the bank

TIP: Having a unique identifier part like SVC001 in this example makes it possible to filter a large number of Services, making the administration much simpler

This naming convention will make the notion of Services easier to understand and follow. There are many information elements in the examples. Transportation of messages, this information in the Endpoints. The 'Invoice' and 'Salary' are the Message Types. In the examples, you will also find out the direction for the message. The source or destination was also mentioned; 'Customer A' and 'Bank' is the System.

Custom Metadata

As with all the entities of the Nodinite Repository Model, a System can have any number of Custom Metadata fields assigned.

Custom Fields

As with all the entities of the Nodinite Repository Model, a System can have any number of Custom Fields assigned.

Resources

^{New 6.0}

The System Administrator can add one or more Resources from the Monitoring and assign these to the Service. Doing so presents the Service with the Monitoring State (the most severe state it the chosen one) in the Integration Landscape.

Sample screenshot of the Interactive Landscape feature.