- 2 minutes to read

What is a Service?

You need to be aware of SOA architecture to maximize the usage of the Nodinite Repository Model A Service is defined as a member of an Integration within Nodinite as one end of a communication chain.

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 can contain information about the following 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 - How and Where was the message transmitted
    • Message Types - What is the message (Order, Invoice, ...)
  • Restrictions within Log Views can easily be enforced if the Service also is properly configured.

A Service should be named like:

  • 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

With this naming convention, the notion of Services will be easier to understand and follow. There are actually many information elements in the examples. Obviously, messages are being transported on a physical medium, this is the Endpoints. The 'Invoice' and 'Salary' are the Message Types. The direction is also provided in the examples. The Monitoring Agent Configuration or destination was also mentioned; 'Customer A' and 'Bank' is the System.

Custom Meta Data

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

Custom Fields

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

Next Step

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

Repository Model
Message Types
Endpoint Directions
Log Views