Integration Process Component 

Use

To be able to address an integration process from the Enterprise Services Repository as the sender or receiver of messages, you must create it as an integration process component in the Integration Directory.

Integration

An integration process can send or receive messages by using its abstract interfaces. Correspondingly, an integration process can be treated like a business system at configuration time: during routing an integration process acts like a sender or receiver of messages. Therefore, when defining receiver determinations you can specify an integration process as the sender or receiver of messages, provided you have already defined it as a communication component in the instance integration process (integration process component for short) in the Integration Directory.

You do not assign a communication channel to an integration process component.

Prerequisites

The integration process must be defined in the Enterprise Services Repository.

To define an integration process component in the Integration Directory, use the integration process Wizard.

See: Defining an Integration Process Component

Features

The following information is displayed about the integration process component:

Attributes of an Integration Process Component

Attribute	Description
Integration Process in the Enterprise Services Repository	Displays the name and namespace of the integration process from the Enterprise Services Repository.
Parameter	Only if configurable parameters are defined in the integration process in the Enterprise Services Repository: Displays the configurable parameters of the integration process. You can assign a value to every parameter. For this purpose, click the input help icon to call the expression editor.
Outbound/Inbound Interfaces	Displays the abstract interfaces that enable the integration process to send or receive messages ( Process Signature).