This documentation applies to the 8.1 version of BMC Atrium Core, which is in "End of Version Support." You will not be able to leave comments.

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

Using server groups with Drift Management


There is an open issue (SW00278808) with the server group implementation of Drift Management. If the primary server goes down, all scheduled jobs fail, even though you expect that the secondary server should pick up all the pending jobs.

In a server group environment, two or more AR System servers point to the same database. This is often done for load balancing or high availability issues. For example, if one of the AR System servers goes off-line, the other AR System server is still available to process transactions. Because both servers use the same database, there are no database synchronization problems.

To use a server group, the AR System server must first be configured to support this type of environment. For information about installing the AR System server for a server group environment and for supporting multiple servers, see Installing a server group in BMC Remedy AR System online documentation.

This section describes how to use Drift Management in an existing AR System server group environment.


Perform the following procedure on every secondary server after you finish a standard installation, as described in Installing BMC Configuration Drift Management. For example, if you have one primary server and three secondary servers in your server group, you must apply this procedure to each secondary server.

To use server groups with Drift Management

  1. Stop the AR System server.
  2. From the primary server, copy the following folders to the <AR_Server_Install_Dir>\pluginsvrfolder that will be used for your secondary server.
    • <Drift_Install_Dir>\Common_Components\java-plugin-libs\common
    • <Drift_Install_Dir>\Common_Components\java-plugin-libs\<platform> (Windows or Solaris)
  3. Create a directory to store your Java plug-ins.
    This will be your <Drift_Install_Dir_secondary_server> in the following example.
    You should create the same directory structure on the secondary server that was used with the primary server.
  4. From the primary server, copy the following folders to the new Java plug-ins directory that will be used for your secondary server.
  5. Use your favorite text editor to open the pluginsvr_config.xml file in the <AR_Server_Install_Dir_secondary_server>\pluginsvr folder used for your secondary server.
  6. From the pluginsvr_config.xml file copy the plugin details from primary server for Drift Management to the pluginsvr_config.xml file on the secondary server. You should copy the entire xml snippet that resides in the <plugin> and </plugin> tags. After copying this snippet, verify that the directory structure matches to the one created on the secondary server as described in step 2 and step 3.

    <filename>< _Drift_Install_Dir_secondary_server_>\BMC_Configuration_Drift_Management\ar\javaplugins\jobmanager\jobmgmt.jar</filename>
    <pathelement type="location"><Drift_Install_Dir_secondary_server>\BMC_Configuration_Drift_Management\ar\javaplugins\job-manager\common-2.5r87.jar</pathelement>
    <pathelement type="location"><Drift_Install_Dir_secondary_server>\BMC_Configuration_Drift_Management\ar\javaplugins\job-manager\io-2.3r7.jar</pathelement>
    <pathelement type="location"><Drift_Install_Dir_secondary_server>\BMC_Configuration_Drift_Management\ar\javaplugins\job-manager\jta.jar</pathelement>
    <pathelement type="location"><Drift_Install_Dir_secondary_server>\BMC_Configuration_Drift_Management\ar\javaplugins\job-manager\quartz.jar</pathelement>
    <pathelement type="location"><Drift_Install_Dir_secondary_server>\BMC_Configuration_Drift_Management\ar\javaplugins\job-manager\rulemgmt.jar</pathelement>
    <pathelement type="location"><Drift_Install_Dir_secondary_server>\BMC_Configuration_Drift_Management\ar\javaplugins\job-manager\tools-config-2.2r6.jar</pathelement>
    <pathelement type="location"><Drift_Install_Dir_secondary_server>\BMC_Configuration_Drift_Management\ar\javaplugins\job-manager\tools-logs-2.2r6.jar</pathelement>
    <pathelement type="location"><Drift_Install_Dir_secondary_server>\BMC_Configuration_Drift_Management\ar\javaplugins\job-manager\tools-regex-2.0r2.jar</pathelement>
    <pathelement type="location"><AR_Server_Install_Dir_secondary_server>\pluginsvr\arapi.jar</pathelement>
    <pathelement type="location"><AR_Server_Install_Dir_secondary_server>\pluginsvr\arutil.jar</pathelement>
    <pathelement type="location"><AR_Server_Install_Dir_secondary_server>\pluginsvr\cmdbapi.jar</pathelement>
    <pathelement type="location"><AR_Server_Install_Dir_secondary_server>\pluginsvr\Logger.jar</pathelement>
    <pathelement type="location"><AR_Server_Install_Dir_secondary_server>\pluginsvr\</pathelement>


    Make sure that you replace <Drift_Install_Dir> and <AR_Server_Install_Dir> with the appropriate values for your system.

  7. Open the ar.cfg (or ar.conf) file and append the following two lines:

    Server-Plugin-Alias: JOBMGR.FILTERAPI JOBMGR.FILTERAPI <AR_Server_Name_secondary_server>:<Java_Plugin_Port_secondary_server>


    Make sure that you replace <AR_Server_Name_secondary_server> and <Java_Plugin_Port_secondary_server> with the appropriate values for your system.

  8. Edit the armonitor.cfg (or armonitor.conf ) file to include the heap size -Xmx768m in the java plugin startup line (if it is not already there).
  9. Make sure the PATH environment variable points to right location. (Windows only)
    For example:

    C:\Program Files\AR System\<_AR_SERVER_NAME_>\pluginsvr;C:\Program Files\AR System\<_AR_SERVER_NAME_>;
  10. Edit the and ar.port key values in the properties.txt file to point to the local server.
    The file is located by default in the <Drift_Install_Dir_secondary_server>\BMC_Configuration_Drift_Management\ar\java-plugins\data folder.
  11. Restart the AR System server and the BMC Remedy Mid Tier.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.