Composite service

The Composite Service node allows users to specify multiple services that must be executed as part of a single service. However, services that can be invoked synchronously can only be a part of the Composite Service node.

If the Composite Service node contain multiple services, it passes the same input to all the services. As it is not possible to determine the service that returned the output, the Composite Service node returns input as output.

Note: If a transaction fails after executing a service in a composite component which drops the message into Oracle WebLogic JMS, MQ JMS, DB or FILE I/O. The message in the asynchronous medium cannot be rolled back.
Note: Never configure a composite service to call its parent service if not it leads to an infinite loop.
Table 1. Composite service configuration properties
Property Description
Service Name Select services to be invoked by this service.

After you add a service, you can view and edit its properties. On the list of services, double-click the name of the Composite service you want to view or edit. It opens in a new window.

Connection properties

The following are the Composite Service node’s connection properties:

Table 2. Composite service connection properties
Connection Node Connection Rules
Can be the first node after the start node Only for services invoked synchronously
Can be placed before
  • Any transport node except for FTP or File I/O
  • Any other component node
Can be placed after
  • Start node
  • Any transport node except for FTP or File I/O
  • Any other component node
Passes data unchanged Yes