Configuring CMDB synchronization through a private queue

Depending on what other integration components (for example, Atrium Integrator, Reconciliation, Normalization) are running on the BMC Remedy AR server to which BMC Discovery is syncing, there may be a performance benefit to those applications and the sync process from setting up a private queue configuration.

By default BMC Discovery uses the BMC Atrium CMDB API RPC Queue (390696), which is also the default queue for other integration components. By configuring BMC Discovery to use one of the private Atrium queues (currently 390698 and 390699 - which are also used for Reconciliation and Normalization CMDB API calls respectively), it may be possible to improve the performance of other components.

The "private" queue is actually a queue shared with Reconciliation or Normalization, so it is especially important to avoid running manual or scheduled Reconciliation and Normalization jobs at the same time as BMC Discovery synchronizing. Failure to do so could result in these operations completing in indeterminate order, for example data being reconciled to the Asset dataset before being normalized. When populating datasets for the first time, the recommended workflow is to manually run Normalization and Reconciliation jobs following an initial sync, then configure inline normalization as well as continuous reconciliation from that point on (see the BMC Atrium Core documentation for further details). The best queue to share depends on the amount and timing of activity for each of these three components on the system being configured.

Use the following procedures to manage private queues for CMDB synchronization:

Configuring a private queue

To start CMDB synchronization using a private queue, complete the following steps:

  • Configure the use of a private queue on the BMC Remedy AR Server
  • Configure BMC Discovery to use a private queue

Warning

Ensure that you avoid a hybrid configuration, where private queues are enabled on the BMC Discovery appliance but not on the AR server, and the reverse.

To configure the use of private queues on the BMC Remedy AR Server

  1. Ensure the following ports appear on the Server Information > Ports and Queues page:
    • 390681
       
    • 390696
       
    •  390698
    • 390699
  2. From the Server Configuration Editor dialog  in the Reconciliation application, set the RPC Socket attribute to 390698.
  3. From the System Configuration tab in the Normalization Configuration Editor, set the following attributes as in the following example:

    FieldValue
    AR RPC Queue390681
    CMDB RPC Queue390699

     

  4. Restart the BMC Remedy AR Server

Configure BMC Discovery to use a private queue

When you create or edit a CMDB sync connection in the UI, you can enter the required private RPC queue port in Specify RPC Queue. The following ports are available:

  • 390696 (the default, which is also used by CMDB for various tasks)
  • 390698 (used by Reconciliation)
  • 390699 (used by Normalization)

See Setting up a CMDB synchronization connection for information on adding connections.

To specify that a CMDB sync connection uses the default queue, either enter 390696, or leave the Specify RPC Queue field empty.

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Stefan Hall

    RPC setting between ADDM and CMDB are very confused at documentation.

    390681 is documented as email rpc on itsm site. the cmdb backport is 390621 and so on

    Hope you can clearify these missmatches

    Dec 12, 2016 02:19
    1. Duncan Tweed

      Hi Stefan. Thanks for the comment. I shall look into it.

      Duncan.

      Dec 14, 2016 04:23
  2. Hans-joachim Ballin

    Despite from the former complained item, the port Settings entierly are not harmonized obviously.

    Under Setting up a CMDB synchronization Connection these 3 RPCs may be used:

    • 390696 (the default, which is also used by the CMDB for various tasks)
    • 390698 (used by Reconciliation)
    • 390699 (used by Normalization)

    Under this page Configuring CMDB synchronization through a private Queue these 3 RPCs may be used:

    • 390698
    • 390681
    • 390699

    Puzzleing this out is not my Goal and needs to be corrected.

    Jan 23, 2017 08:23
  3. Stefan Hall

    Since AR/Core 9.1.03 this page need an update for all the new RPCs for integrations.

    I mean these RPCs https://docs.bmc.com/docs/ac91/configuring-ports-for-bmc-atrium-core-using-rpc-program-numbers-609846558.html - 300867 to 300886

    Stefan

    Aug 31, 2017 01:43
  4. Stefan Hall

    What about the new content?

    Sep 10, 2017 12:17
    1. Brice-emmanuel Loiseaux

      Actually, Discovery using a value into this new set of rpc queues is not accepted by AR/CMDB 9.1.03 server (which then use the default 390696 queue) because it requires for the same exact API calls, the use of AR & CMDB 9.1.03 client API libraries. Discovery still uses an older version (DRUD1-23386).

      Jun 29, 2018 08:10
      1. Stefan Hall

        Are you sure, the new RPCs seem to confuse even BMC.

        I have already received other answers and tried it myself with RPC 300880 in ADDM/DISCO CMDB sync. In the AR logs I see that 300880 is also used.


        What makes you think that's not the case?

        Jun 29, 2018 01:32
        1. Stefan Hall

          Here is the other official answer from BMC. It's annoying when there's no real official answer. Please clarify this bindingly and inform everyone here. Thank you

          ---

          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

          copied from Configuring ports for BMC Atrium core using RPC program numbers

          Jun 29, 2018 01:50
        1. Brice-emmanuel Loiseaux

          "What makes you think that's not the case?"

          Well, this is your comment into Configuring ports for BMC Atrium core using RPC program numbers:

          "

          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.

          "

          So, does it work or not for you?

          Jul 03, 2018 07:41
          1. Stefan Hall

            Are you asking me if it works?

            I want clear and concise information from the manufacturer, you. What about the new RPCs under 9.1.04? When I use 300880 in ADDM, I also see this RPC in the log files. But that doesn't match your statement!

            Please clarify it bindingly and correct the documentation.

            Jul 15, 2018 04:29