Add or manage Service

In this section you will learn how to add or manage an Service.

Instructions

Add a new Service or Edit an existing from the list in the overview. A Service can host Message Types, Endpoints, System and Custom Fields after you have successfully created the Service.

Add Service

Mandatory Fields

A Name is required to create the Service.

Name, Description, and Website

Optional fields

Adding a Description and a Web Site is optional.

  • Description: A user friendly description.
  • Web Site: You can provide a quick link for users when working with and viewing the Service. This quick link is usually a WIKI/Sharepoint site with additional documentation.

System

Set the Monitoring Agent Configuration or Destination System for Service. This setting provides information for the graphical overview in order to paint the symbols. This setting also acts as a filter when providing information about the Monitoring Agent Configuration Service (Only sending Services can be a Monitoring Agent Configuration for a Receiving Service).

If the System is not yet created, it is possible to create it by clicking Quick Add System. Only the name will be is set in the System, further editing must be done within Add or manage System.

QuickAddSystem

Transport Contracts

Transport contracts defines one or more log points. The Transport Contract is always a combination of one or more Message Types, Endpoints,

Simple log point example

The most basic example would be exactly one specific message (Message Type) for example an invoice, that goes in (Receive) or out (Send) on one specific transport location (Endpoint). This

graph TD subgraph "Transport Contract " subgraph "Logpoint" roMT(fa:fa-file Message Type) roEP(fa:fa-sign-in Endpoint) end end

When you create a New Service the list of Transport Contracts is empty. You can either 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.

Empty Transport Contract

Shared Endpoint example

Let's imagine the actual endpoint in use is a shared endpoint like a shared mailbox (info@company.com). In order to separate different flows of information for end users you can create multiple Services with different sets of definitions for Transport Contracts where you filter on relevant combinations of Message Types and Endpoints.

graph TD subgraph "Transport Contract " subgraph "Logpoint" roMT(fa:fa-file Message Type, 'Order') roMT2(fa:fa-file Message Type, 'Order Response') roEP(fa:fa-sign-in Endpoint) end end

Multiple Endpoints for the same Message Type example

Let's imagine now the same message (Message Type) is distributed on many different Endpoints (for example the old production environment and the new production environment).

graph TD subgraph "Transport Contract " subgraph "Logpoint" roMT(fa:fa-file Message Type, 'Order') roEP(fa:fa-sign-in Endpoint, 'Old port') roEP1(fa:fa-sign-in Endpoint, 'New port') end end

Transport Contract

Add, Edit or Delete transport contracts

Transport Contracts Add/Edit

When the list of Transport Contracts is empty you must first create a new Transport Contract Empty Example for empty list of Transport Contracts

Click on the Add button to create the first new Transport Contract.

Transport Contract

You must provide a Name for the Transport Contract. This name helps you understand what type of relation you are creating. It's just a name and can be changed later without any functional consequence anywhere within Nodinite.

Message Types

Add the expected Message Types. There can be any number of members.

Message Types

End Points

Add the expected Endpoints. There can be any number of members.

Endpoints

Relations

To draw a landscape with connections relations between Services are required
Relations Result

A in Service connection to a out Service must be running on the same System to be connected.
A out Service connection to a in Service can run on on same or different Systems.
Relations Edit

Custom Fields

As part of the Repository Model model, You can also add Custom Fields to provide additional documentation about your Service.

Direction

Set the Direction. You can choose between

  • Receive
  • Send
  • Direction two way Receive
  • Direction two way Send
  • None
  • Unknown

If a Service in the graphical overview is not defined Direction Unknown will be displayed.
direction

Next Step

Add or manage Custom Field

Systems
Repository Model
Services
Custom Fields