The Fiorano Platform allows composition of 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. When the producer microservice is in a calling event process, then the producer microservice needs to send messages to the consumer microservice in a called event process. In this case, a remote instance of the consumer microservice 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. The 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 steps below:

  1. Click the Insert Element into Event Process icon and select the Insert Remote Service instance option or right-click on the orchestration editor and select the 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 to add as a Remote Service Instance and click the OK button.

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


The service instance bears the originating event process name as the prefix, which helps to identify the source of the service instance.

Figure 3: Remote service added

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


When using the Remote Service instance with the Event Process Life Cycle Management (EPLCM), if a microservice is running in a configured mode (say Testing) in the parent Event Process and if this microservice 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 will continue to use the mode used in the parent Event Process.

Tracing the event processes that use a Service Instance remotely

A service instance may be used remotely in one or more event processes and hence, later on, it may be difficult to trace/remember the event processes where a service instance is used remotely. Perform the following actions to see the event processes where the instance is being used.

Right-click the microservice which needs to be checked and select the View Referring Applications option.

Figure 4: Checking the applications to which the service instance is referred

The View Referring Applications and Components pop-up window displays the event processes that use the selected service instance remotely.

Figure 5: Tracing the applications to which the service instance is referred


In the example above, it is seen that the Feeder microservice bearing the name "Flow Trigger" is being used remotely in the event processes DATABASE_REPLICATION and EVENT_PROCESS1.

Adaptavist ThemeBuilder EngineAtlassian Confluence