The Fiorano Platform allows you to compose an Event Process with Business Component instances from other Event Processes. The Remote Service instance is one of the available options for communication between different event processes. If the producer component is in a calling event process, then the producer component needs to send messages to the consumer component in a called event process, then a remote instance of the consumer component can be used in the calling event process.

The imported service instance is the reference to the service instance in the parent Event Process. Any changes made to the imported service instance in the parent Event Process are reflected in the current Event Process. Current Event process can be launched only when the Event Process of the remote service instance is running.

To add a remote service instance, perform the following steps:

  1. Click the Insert Element into Event Process icon and select Insert Remote Service instance option (or) right-click on orchestration editor and select Insert Remote Service instance.


    Figure 1: Insert Remote Service Instance option

  2. The Select Remote Service Instance wizard starts, as shown in the figure below. This dialog box lists all the Event Processes and their service instances.

    Figure 2: Select Remote Service Instance dialog
     
  3. Select the service instance you want to add as Remote Service Instance and click the OK button.

The Remote service is added to your Event Process with a satellite like icon in the component as shown in the the figure below.


Figure 3: Remote service added

A Remote Service instance can be used in a similar manner to normal a service instance. Routes can be created between other service instances in the Event Process and the ports of the Remote Service instance.

Icon

While using Remote Service instance with Event Process Life Cycle Management (EPLCM), and if a component is running in a configured mode (say Testing) in the parent Event Process and if this component is used as a Remote Service instance in a caller Event Process, then changing the mode in the caller Event Process will not have any effect. It still uses the mode used in parent Event Process.

Adaptavist ThemeBuilder EngineAtlassian Confluence