Processes published on one host process execution engine can call processes or sub-processes published on a different host process execution engine. The called or remote processes are called external processes.
For example, a warehouse company may have a process that calls a sub-process that resides in a shipping company. Both processes are published and deployed on different host process execution engines in different networks, which are typically behind firewalls. The warehouse process must be able to find the connection information for the shipping process in order to send the instance to the shipping process. An external process scenario could also include internal processes that are published and deployed on different host process execution engines.
When a process execution engine needs to communicate with a process located on a process execution engine other than the one where the process is deployed, it starts looking for an external process to establish the connection and reach the process. The external processes defined in the External Process List are evaluated in descending order until an external process matching the required process information is found.
To add a connection to an external process:
In the left pane of Process Administrator, select External Processes.
On the External Processes page, click Add.
On the Identify Location of External Processes page, enter the Directory Service Name for the host process execution engine on which the external processes reside. The external processes are the processes being called by processes published on this host process execution engine. The directory service name for a host process execution engine can be found in the that engine's fuegodb fuego_schInfo table in the fuego_orgName column. The directory service name is configured when setting up the directory service for a host process execution engine using the Admin Center Configuration Utility. The default directory service name is "company."
On the Identify Location of External Processes | Add External Processes page, click Add.
On the Identify Location of External Processes | Add External Processes | Edit External Process 'n' page, where n represents the creation number of the external process, enter the Properties needed to establish the connection with the external process:
The Process field should contain the name of the external process.
The URL field should contain a URL in following format:
standalone: http://host:IPCport#/fuego where host is the name of the computer on which the process execution engine for the external process resides, the IPC port # is the port configured on the Engines | Services tab of the process execution engine on which the external process is deployed, and /fuego is a mandatory element of the URL.
J2EE: http://host:app_server_listening_port/fuegoServices/b2b
The User and Password fields should contain the case-sensitive administrator user name and password used to log onto Process Administrator. If there is not a password set, enter a few characters so that this field is not blank.
Click Save.
On the Identify Location of External Processes | Add External Processes page, click Add to continue adding external processes that reside on the same host process execution engine or click the external process Number to edit the connection information for an external process.
Re-start both process executions engines (the one calling the external process and the one on which the external process resides).
Note: In order for the process execution engine to be able to use the external process configurations, the IPC port must be configured and enabled on the Engines | Services tab of the process execution engine on which the external process is deployed.
Note: If the external process must reconnect to the calling process after it is finished processing, such as through Subflow, Termination Wait, or Process Notification activities, the process execution engine for the external process must have its own external process configured to reach the calling process.
Related Topics: