Skip to Content

Configuring connections between Publishing Server and BMC Atrium CMDB

  1. To communicate with BMC Atrium CMDB, the Publishing Server uses the host/port that is set in the pserver.conf file:

    # ------------------------------------------------------------------------------
    # Atrium CMDB
    # ------------------------------------------------------------------------------
    # If you are not using AR Server Group, then you set the server name of your AR
    # Server on which Publishing Server will connect.
    # If you are using AR Server Group and you have a load balancer, then you set
    # the address of the load balancer.
    # If no load balancer is deployed then you set the address of the AR Server group
    # member on which you want Publishing Server to connect.
    CMDBServer=<cmdbServer>
    # This gives the tcp/ip port that PS will use to connect to AR Server.
    # Use 0 for dynamic port detection.
    #CMDBPort=0
    CMDBPort=<cmdbPort>
    CMDBUser=<cmdbUser>
    CMDBPassword=<cmdbPassword>
  2. For automated publication, the Publishing Server connects to SIM NOTIFY ARDBC plugin.

    1. To get the port from the Notify:Servers form, the Publishing Server connects to the AR Server that has the Notify plugin deployed.
      In case of an AR Server Group, see Configuring-the-Publishing-Server-to-integrate-with-an-AR-Server-group.

      # If no AR Server Group is deployed then this parameter does not need to be set.
      # If a AR Server Group is deployed then you have to run Notify plugin on
      # every group member.
      # Automated publication will only function if Publishing Server can connect the
      # individual group members. To verify this: from the PS host, login with
      # Remedy User to server group member itself, then open the form NOTIFY:Servers
      # and search for the entries. If this fails then your AR Server Group is not
      # correctly configured, and automated publication will not work. Please correct
      # your AR Server Group configuration.
      # ARSGroupMembers lists the host and tcp/ip port of every group member.
      # Remark that you do NOT specify the notify port here, but the tcp/ip port.
      # If a AR Server Group is deployed then you have to set this parameter,
      # regardless if you use a load balancer.
      # Use 0 for dynamic port detection.
      # As long as Publishing Server is not able to connect to the NOTIFY server of
      # all the specified server group members, psstat will return "Starting automated
      # mode". This may be because there is an error in the configuration, or there
      # is a network issue, or the server group member is not running. In pserver.trace
      # you find the server details.
      # ARSGroupMembers=<host>:<port>{,<host>:<port>}
      ARSGroupMembers=

    2. The port on which the Notify plugin is listening (and that is exposed in the Notify:Servers form) is configured in the parameter ServerPort. See Configuring-the-Notify-ARDBC-plug-in.

       

 

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

BMC ProactiveNet 9.6