RPC ports registered dynamically by the installer
This reference topic describes how the installer registers new RPC ports (Private-RPC-Socket) for the Cloud Portal, EAR_DB, Session_Manager, and Cloud_DB services during BMC Cloud Lifecycle Management installations.
In 4.x, specific RPC program numbers are now reserved for BMC Cloud Lifecycle Management. But if that RPC port is already being used, the installer dynamically assigns a new RPC port.
This topic is critical in the following scenarios:
- Upgrading Single VM RDS 3.1.x to 4.x
- All new 4.x installations
Cloud Portal service
During typical installations of Cloud Portal, the installer registers RPC port 390690 in the ar.config file. For example:
Private-RPC-Socket: 390690 2 12
But if 390690 is already being used, the installer reports a warning and then dynamically registers a new RPC port for Cloud Portal in the ar.config file and updates the <CLM_INSTALL_DIR>/Cloud_Portal/plugin/pluginsvr_config.xml file.
EAR_DB and Session_Manager services
During installation of Platform Manager (where the EAR_DB and Session_Manager services are installed), the installer registers RPC port 390691 in the ar.config file. For example:
Private-RPC-Socket: 390691 12 24
But if 390691 is already being used, the installer reports a warning and then dynamically registers a new RPC port for Enterprise-AR and Session Manager and updates the EAR_DB and Session_Manager services in the <CLM_INSTALL_DIR>/Platform_Manager/configuration/cloudservices.json file.
The process for registering a new port for Cloud_DB is slightly different than Cloud Portal, EAR_DB, and Session_Manager. During installation of Platform Manager (where the Cloud_DB service is installed), the installer registers either RPC port 390696, 390698, or 390699 (based on their availability). The min and max thread settings are 12 and 20, respectively.
If all three RPC ports are already being used, the installer reports a warning and uses one of the RPC port among the three that is configured with a higher max thread setting. The installer will not increment any thread settings of the used port. The installer then displays a message about which RPC port is being used and refers you to a configuring RPC programs topic that explains RPC socket configuration.
The installer also updates the Cloud_DB service in the <CLM_INSTALL_DIR>/Platform_Manager/configuration/cloudservices.json file.