The TIBCO iProcess Engine RPC Service
The process that monitors the RPC calls that request a connection to the TIBCO iProcess Engine is known as the RPC listener. This has a pre-defined RPC number (Default: 391875). If a TIBCO iProcess Engine is communicating with another TIBCO iProcess Engine, the default port is 391870. The SWDIR\swdefs file contains the RPC numbers.
When the iProcess Engine starts:
1. | The RPC TCP listener process starts and requests the operating system to allocate it a port. |
2. | It binds a TCP socket to this port. |
3. | It then contacts the portmapper and requests that its RPC number (391875) is registered on the port that the operating system has allocated it. |
4. | The portmapper makes an entry in an internal table of the RPC number and port. |
5. | The iProcess Engine starts a number of other RPC servers but with dynamically allocated RPC numbers. These servers bind to a port dynamically allocated by the operating system and then registers the relationship between the RPC number and port with the portmapper. |
The following describes what happens when an TIBCO iProcess Workspace connects to an iProcess Engine:
-
The TIBCO iProcess Workspace connects to the portmapper program.
-
The TIBCO iProcess Workspace requests details of the port to which the client RPC listener is bound. The request specifies the RPC number (Default: 391875).
-
The TIBCO iProcess Workspace connects to the client RPC listener using the port details and then requests details of the RPC numbers of the other RPC servers the TIBCO iProcess Workspace needs.
-
For each of the RPC numbers obtained, the TIBCO iProcess Workspace:
-
Contacts the portmapper.
-
Requests details of the port to which the RPC number is bound.
-