Page Comparison

Adapter

Generic symbol for a connection to an integrating application

Image Added

Image Added

• EndPointRef: ​Endpoint ID

• of physical endpoint in integration catalogue

• ​​Type: ​Adapter type or protocol

Ap​plication (Sending/Receiving)​

​Defines an interface to an integrating system sending/receiving messages to the integration platform.

• ​EndPointRef: ​Endpoint ID of physical endpoint in integration catalogue

• ​​Protocol: Communication protocol. E.g. HTTP, FTP etc

• MsgFormat: Message format. E.g. XML, CSV etc

• MsgType: Message type. E.g. Student, Kurs etc

Aggregator

Message aggregator. Aggregates several messages into one combined message.

Content Based Router

​Route a message based on the content of the message

Content Enricher

​Enrich a message with additional data from one or several sources

Content Filter

​Extract relevant information from an original message to create a smaller message or to filter out information that is not valid for the specific application

Contract

​A service contract as defined  in the integration catalogue.

• ​Cont.Id: Contract Id (in integration catalogue)

Durable Subscriber

Represent a named object that receives persistant messages in a pub-sub scenario.

• ​NamedObj: Type of object, eg. wmTrigger or MQ Queue
  

Error Handler

​General error handler. Only to be used when none standard error handling (according to Developer Guidelines ICC) should be implemented.

• HandlType: Error handling type

• ErrCode: Error code

File Transfer Adapter (left)

Any type of file transfer with active receiver (eg FTP GET operation)

Image Added

• EndpointId

  • ​Endpoint ID of physical endpoint in integration catalogue

• EndpointOwner

  • System that owns the endpoint (used for clarity)

• Protocol

  • The protocol used (eg FTP, SFTP, FTPS, TFTP...)

• Filename

  • The filename or filename pattern for the poll/receive (use a callout for complex patterns)

File Transfer Adapter (right)

Any type of file transfer with active sender (eg FTP PUT operation)

• EndpointId

  • ​Endpoint ID of physical endpoint in integration catalogue

• EndpointOwner

  • System that owns the endpoint (used for clarity)

• Protocol

  • The protocol used (eg FTP, SFTP, FTPS, TFTP...)

• Filename

  • The filename or filename pattern for the send (use a callout for complex patterns)

Ladok Event Manager

​General event manager component managing events from Ladok

Service Message

Represent a message as defined in the integration catalogue

• MsgId: Message id (in integration catalogue)

• MsgName: Message name. E.g. personRecord, personCanonical, kodplan, PAData

​Message

Represents any message handled as part of a service or consumer adapter. For messages defined as a message in then integration catalogue use the icon ServiceMessage.

Image Added

• MsgFormat: Message format. E.g. XML, CSV​

• MsgName: ​Message name. E.g. personRecord, personCanonical, kodplan, PAData

​Message Creator

Initial creation of a new message.

• MsgFormat: Message format. E.g. XML, CSV​

• MsgName: ​Message name. E.g. personRecord, personCanonical, kodplan, PAData

Message Filter

​Message filter that decides which messages that should be passed on for further processing

Message Translator

​Any transformation of a message. Normally a message mapping but can also represent other types of transformations

Image Added

• MapName: Mapping name. The name should describe the function of the transformation. E.g From format A to Format B.

Message Validator

​Validates that a message is correct according to a specific schema or message definition

• Schema​: Schema reference

Non-Durable Subscriber

​Represent a Universal Messaging named object that receives non-persistant messages in a pub-sub scenario.

Image Added

• NamedObj: Named object could be wMTrigger och queue. Queues should be named according to queue naming convention, <consumer>_<entity>_<servicetype>_<optional>_<contract id>.

Pub-Sub Channel

​Channel for publishing messages in a pub-sub scenario

• Channel: Channel name as topic. Service topics are named MQ Topic.

Distribution List

​Distribute a message to a list of known recipients

Service

​​A service as defined  in the integration catalogue.

• SrvId: Service id as defined in integration catalogue

• SrvName: Service name

Splitter

​Split a combined or enveloped message inte its individual messages

​Timer

Trigger an activity based on a time schedule.

The timer interval is documented on the Service or Contract in the Integration catalogue.

​Web Service (REST)

HTTP/REST web service

• EndPointRef: ​Endpoint ID of physical endpoint in integration catalogue

• Method: HTTP method. E.g. GET,PUT or POST

• Resource: Resource, relative to Endpoint URI. eg /Users

​Web Service (SOAP)

HTTP/SOAP web service

• ​EndPointRef: ​Endpoint ID of physical endpoint in integration catalogue

• Operation: Service operation