Add or manage Service
In this section you will learn how to add or manage an Service.
A Name is required to create the Service.
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.
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.
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.
Let's imagine the actual endpoint in use is a shared endpoint like a shared mailbox (email@example.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.
Add, Edit or Delete transport contracts
When the list of Transport Contracts is empty you must first create a new Transport Contract Example for empty list of Transport Contracts
Click on the Add button to create the first new 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.
Add the expected Message Types. There can be any number of members.
Add the expected Endpoints. There can be any number of members.
To draw a landscape with connections relations between Services are required
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.
Set the Direction. You can choose between
- Direction two way Receive
- Direction two way Send
If a Service in the graphical overview is not defined Direction Unknown will be displayed.