Verifying the RPC socket number

Identity Request Management no longer supported

The Identity Request Management (IRM) module is no longer supported in versions 9.0 and later of BMC Service Request Management. However, IRM continues to be shipped for reference in BMC Service Request Management.

For more information about the end of life of IRM, see Product announcements.

Note

 You can skip this procedure if you have not installed Identity Request Management.

All servers include an admin queue, which is the default server setting and cannot be configured. The admin queue can have only one thread at any time. When you define additional queues, you must assign corresponding Remote Procedure Call (RPC) program numbers, and you must define the minimum and maximum number of threads for each queue that you are using.

Identity Request Management uses the RPC socket to communicate with the BMC Remedy AR System server. The default socket that is used by Identity Request Management is 390685. Before you run the installation wizard, you must verify that this socket is not in use by either the BMC Remedy AR System server or by any other application on the computer where the BMC Remedy AR System server is installed. If it is in use, you must reserve another socket.

To verify the RPC socket

  1. Log on to the computer where the BMC Remedy AR System server is installed.
  2. Depending on your operating system, open one of the following files in any text editor:
    • (Microsoft Windows)%BMC_AR_SYSTEM_HOME%\Conf\ar.cfg
    • (UNIX)$BMC_AR_SYSTEM_HOME/conf/ar.conf
  3. Find the Private-RPC-Socket lines in the file. If 390685 appears, it is not available for Identity Request Management. Reserve an alternative socket that does not appear in the file to be entered during the installation process.
    The valid ranges of socket numbers are as follows:
    • 390621 – 390634
    • 390636 – 390669
    • 390680 – 390694

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*