This documentation supports the 9.1 to 9.1 Service Pack 3 version and its patches of BMC Atrium Core. The documentation for version 9.1.04 and its patches is available here.

To view the latest version, select the version from the Product version menu.

Configuring ports for BMC Atrium core using RPC program numbers

This section explains how to configure ports for BMC Atrium Core to improve the performance using RPC program numbers. The following topics provide information about configuring ports: 

To configure port on the AR System Server

BMC Remedy AR System Server receives requests from BMC Atrium Core. Before you configure the ports in Atrium Core, you must first configure the ports on the AR System server. The steps to configure a port on the AR System server are as follows:  

  1. Log in to the AR System server.
  2. Open AR System Administration > Server Information > Ports and Queues.
  3. Add an entry to the Server Queues table.
    For information about which RPC program numbers can be used, see RPC program numbers for BMC Atrium Core
  4. Configure the Min Threads and the Max Threads for each port.
  5. Click Apply.
  6. Restart AR System server.

RPC program numbers used by BMC Atrium Core

The following table lists the RPC program numbers used by BMC Atrium Core.

To avoid collision or interference with other BMC Remedy products, do not set an RPC program number on your computer with any of the values listed in the following table.

RPC program number

Queue type

Additional information


CMDB API calls

By default, all BMC Atrium CMDB API calls use this program number.


CMDB calls

Admin thread only

390698, 390699

Extra CMDB queues

Other BMC Atrium Core products (for example, Reconciliation Engine and Atrium Integrator ) use these RPC program numbers as their private queues to the BMC Atrium CMDB.

(Applicable from BMC Atrium Core version 9.1.03 or later.)
300867 through 300886 
Extra CMDB queuesOther BMC Atrium Core products (for example, Unified Service Modeling, and Normalization Engine ) use these RPC program numbers as their private queues to the BMC Atrium CMDB.
3906215/12Created during BMC Atrium Core installation. Used by Product Catalog Data Loader.

Verifying private queues

To avoid collisions with BMC Remedy products, you can use the following methods to examine the private queues on your computer:

  • Inspect the ar.conf (UNIX) or ar.cfg (Windows) files for RPC program numbers in use.
    For example, 390626 is used by the Plugin-Loopback-RPC-Socket (with the Report Creator plug-in). For more information, see BMC Remedy Approval Server configuration file settings in the BMC Remedy Action Request System online documentation.
  • Use the AR_SERVER_INFO_PS_RPC_SOCKET (87) ARGetServerInfo API call.
    For more information, see ARGetServerInfo in the BMC Remedy Action Request System online documentation. For more information about queues and threads function in the AR System server, see Remedy AR System server architecture and scalability in the BMC Remedy Action Request System online documentation.
Was this page helpful? Yes No Submitting... Thank you


  1. Sandeep Das

    RPC queues 390695, 390696, 390698, 390699  are not created by default  on the Ports and Queues tab of Server Information page. Do I need to add them manually after Atrium Core installation? 

    Mar 27, 2017 06:36
    1. Anagha Deshpande

      Hello Sandeep,

      I will check with SME and will write back to you.



      Mar 27, 2017 10:59
      1. Anagha Deshpande

        Hello Sandeep,

        390695 is not used for CMDB components. CMDB has following four RPC queues allocated to it (till version 9.1.02):
        If you need to use some queue for making CMDB calls on private queue, you should add them manually to BMC Remedy AR System configurations along with the number of threads. These threads are not added by default.
        Out of these queues, you can only use 390698 and 390699. 390696 is RPC program number for all CMDB calls and 390697 is for admin call.




        Mar 28, 2017 09:38
  2. Stefan Hall

    Are you sure that all the new RPCs starts with 300 instead of 390? After upgrading to 9.1.03 ADDM sync is terrible slow with settings from 9.1.02.

    Aug 30, 2017 12:57
    1. Nidhi Das

      Hello Stefan,

      I will discuss this with the concerned SME and will write back to you.


      Aug 31, 2017 11:53
    1. Nidhi Das

      Hello Stefan,

      As per the SME, all the new ports starts from 300.

      No issues have been reported so far in this area. If you are facing any issue, please raise it.


      Sep 07, 2017 06:39
  3. Stefan Hall

    Can you give some more information about the new RPCs, no other page knows them. - Which port for CMDB sync from ADDM? - IS Min / Max configuration required? Where should I do it?

    I've tested it with 300880 for ADDM CMDB sync and it seems not working.

    Aug 31, 2017 01:51
    1. Nidhi Das

      Hello Stefan,

      I will discuss your query with the concerned SME and will write back to you.


      Aug 31, 2017 11:55
    1. Nidhi Das

      Hello Stefan,

      Sorry for the delayed response. 

      The RPC ports are not for CMDB sync from ADDM. The ports are consumed within CMDB by CMDB components as described in this topic.

      Yes,the Min and Max thread configuration is required. This should be done at AR Server information under Ports and Queues.


      Jan 18, 2018 04:42
      1. Stefan Hall

        Hi Nidhi,
        Your information seems not correct or I found another documentation failure.
        Take a look at and you will see explicit information about cmdb sync with new ports.

        Please check it again with your experts

        Jan 21, 2018 10:14
        1. Sachin Tappe

          Hi Stefan Thanks for pointing this out. You are right, the range of 300867 -300886(both inclusive) is new range of Ports introduced for Atrium CMDB starting 9.1 SP3. If you are on CMDB 9.1 SP3 and above versions, setting up 300880 should ideally work. What is the ADDM version at your end? ADDM CMDB Sync has been enhanced to use the new range of ports. Once you confirm ADDM version that you are using, I will confirm whether it is compatible to use the new range.

          Thanks, Sachin

          Jan 22, 2018 04:53