Category Archives: BMC Remedy

Asset Management Atrium CMDB Atrium CMDB 1.x Atrium CMDB 2.x

Adding an Attribute to the CMDB via a CMDB Driver Script

There are a number of ways to create an attribute in the CMDB. You could use the BMC Atrium Core Console, Remedy API, or the CMDBDriver.

The BMC Atrium Core Console offers a nice GUI interface, and is fairly slick when used via the mid-tier. I have noticed some issues using the mid-tier version vs the UserTool version. One issue that I’ve noticed is that sometimes custom fields do not show up when your viewing the classes. When viewed from the UserTool, everything is there. Another issue I have noticed is that the Menu Style field shows different results when compaired to what one see’s in the UserTool.

The Remedy API is a very powerfull feature, if used correctly, and you understand what your doing. I have built everything from forms, fields, active links, filters, and guides with the API and really, one takes for granted what the GUI does for you.

But the topic is the CMDBDriver tool. This is not a user friendly tool, but once you understand it, its great for automating alot of your work.

The one feature is the “execute” command. This allows you to execute a driver script that is basically a list of commands (like a macro) that you want the driver to execute. The following text is what is used to create a selection field, with 3 entries, on the BMC_Application class:

Corporate Group
Customer Group
Enterprise Group

These lines would sit in a text file, and the driver would execute the contents. The first line is the “CA” command which stands for Create Attribute. The following lines would be the supplied input for the process of manually creating an attribute.

The power of this feature is that you could maintain a number of these commands in the text file, allowing you to create as many fields, on as many forms as you like. For example, when I build out a new server environment, I can execute just one file that will add every custom field we added to the CMDB, bringing it upto speed with our existing environments.

CMDBDriver - Start Up
CMDBDriver – Start Up
 The next step is to enter the “init” command. This initizlizes the session, closing off any other session that you may have been already logged into. This is the first step that you must do when first opening the application. The next step is to enter the “log” command. Here you are logging in with your UserID, Password, and Server Name. Finally, if you are using a port number to connect to your server, enter the “ssp” command. This allows you to enter your TCP port number.
Initialization and Login
Initialization and Login

The next step is to issue the “ex” command. This will prompt you for the command/driver file to load. Enter in the full path and filename. No need to enclose everything in quotes, as spaces dont matter.

Execute Command
Execute Command

This is the part of the process that gets cluttered, and leaving you wondering whats going on. As the CMDBdriver executes the script, prompts for data are appearing on the screen. Normally you would manually enter the values, but our command file is supplying the data for us. I would have been nice if the values were actually displayed as the system exectued the file. Depending on how many attributes, which class your hitting, and the amount of data in your CMDB, this could take a few seconds or minutes to complete.

If you have multiple attributes being created, this screen will repeat the the cluttered block for each one. Once done, you should finally see the Command prompt come back.

Execution of the command file
Execution of the command file

Over the years, dealing with problem tickets with BMC Support and talking with the application engineers, they all have said that they use the CMDBDriver for most of the work that they do. When you use the Atrium Core/Class Manager to add attributes, the CMDBDriver is actually being called in the background to do the work. It pulls its information from the OBJSTR:Class form (these are your Pending records). Once the driver completes the task, the record in the OBJSTR:Pending form is removed.

One nice thing about the CMDBDriver is that if something goes wrong, it tells your right away. If something goes wrong using the AtriumCore/ClassManager, you have to go in and start deleting records in various forms.

One last helpful hint if AtriumCore/ClassManager does not appear to be completing the building of your new field, you can grab the ‘Pending ID’ and from within the CMDBDriver, issue the “sync” command, which will prompt you for the Pending ID. This will force the attribute to complete for you, and the matching record in the OBJSTR:Pending form will disapear (As long as there are no errors in your system, but thats another issue to resolve). Note that the ‘Pending ID’ is not visible on the form, but you have to export the data, or manually type it out from the report option. On most of my sites, we have made this field visible (read only) so its easy to grab.



7.1.x 7.6.04

Troubleshooting Plugins


For reference and to assist in the troubleshooting process, we have listed the following plugins used in the applcation.  The reference shows the plugin name as seen in the corresponding ar.cfg/ar.conf file, the actual plugin name shown in the Plugin log, and what the specific plugin does.
Plugin: arapprove

What it does:Runs the approval process
Plugin: libcmdbconsolefilterapi20

Actual Plugin Name:  BMC.ARF.CMDBCONSOLE
What it does: Used to compare instances in CMDB Console

Plugin: ardbcQuery

What it does: Used to query the overview console and return data from the vendor form for Incident, Problem, Change and Asset

Plugin: arfcbdata

Actual Plugin Name:  REMEDY.ARF.CBDATA
What it does: Used for chargebacks

Plugin: caieventcmd

Actual Plugin Name:  REMEDY.ARF.CAI
What it does: Takes data from the CAI Event form and creates a record in the appropriate Interface_Create form.

Plugin: omfobjiefilapi

Actual Plugin Name:  REMEDY.ARF.OMFOBJIE
What it does: Used for exporting sla’s

Plugin: arfslasetup

What it does: When you Register Application forms in SLA, this builds the _SLA join form

From the application standpoint we expect to see the ar.cfg/ar.conf file show the Plugin and the plugin path.  The plugin path should only be seen one time for each plugin used in multiple apps.  Whichever application was installed first will update the ar.cfg/ar.conf file with the plugin and plugin path.  For example, the caieventcmd plugin on unix would show the following if Problem Management was the first app installed:

Plugin-Path: /usr/arsystem/appslinux02/problem/bin
Plugin: /usr/arsystem/appslinux02/problem/bin/

On a windows server it would show the plugin path and plugin in one line:
Plugin: “D:\AR System Applications\itsm70ars70w2k3\BMC Remedy Problem Management\bin\caieventcmd.dll”


Troubleshooting ARERR [8755] The specified plug-in does not exist errors: <Plugin Name>

The name of the plugin will show in the above error.  For this type of error message, you must know the actual plugin name from above, for example, REMEDY.ARF.CAI, to know which entry to look for in the ar.cfg/ar.conf file. 

1.  Verify the ar.cfg/ar.conf file has the plugin and plugin path.
On windows:
 “D:\AR System Applications\itsm70ars70w2k3\BMC Remedy Problem Management\bin\caieventcmd.dll”

Plugin-Path: /usr/arsystem/appslinux02/problem/bin
Plugin: /usr/arsystem/appslinux02/problem/bin/

2.  For the above location, go to the directory on the server and verify that the actual plugin resides in the directory listed and permissions are consistent with the user arserverd/arserver.exe run as (especially important when transitioning to a non-root install.)


Troubleshooting ARERR [8939] The AR System Plug-In server is not responding.  Cannot connect to the system at this time.  Contact your AR System Administrator for assistance. : RPC: Timed out

1.Enable Plugin and API logging on the server and perform the action that generates the timeout message.
2.Review both the Plugin and API log for delays in processing.  3.If the delay occurs in the Plugin log but the API log looks ok, then the issue is with the plugin entries in the ar.cfg/ar.conf file.

You should have the following:
 Server-Plugin-Default-Timeout:<your setting>
 Plugin-Loopback-RPC-Socket: <your setting>
 Plugin-ARDBC-Threads: <your setting>
 Plugin-Filter-API-Threads: 1 15
***Please see the AR System Configuration Guide beginning on page 330 for more information on these settings and how to adjust them for your specific environment*****

4.For the REMEDY.ARF.CAI plugin, make sure Approval Server is installed and you have configured the CAI:Plugin registry form as noted on page 124 of the BMC Remedy IT Service Management Architecture Guide  As a technique for reducing thread contention, the private queue and number of threads to be used for the CAI plug-in can be defined using this form. To use this feature, you must define a private queue using BMC Remedy Administrator, and then update the CAI Plug-in Registry with the queue number and number of threads. If the applications are running on a specific port and not on portmapper, you will need to update the plugin from patch 004 of the applications. A change was made to this plugin to allow it run on a specific port. 
5.  If the delay is in the API logging, then the server may not have enough fast and list threads to perform plugin operations.  Adjust your threads via the Administrator tool as needed.


7.5 Plugin config and log files


  • How to determine which plugin is which
    How to determine which config file goes with which plugin
    How to determine which file to edit to enable plugin logging for a given plugin
    BMC Remedy AR System Server


  • Your paths and server names will differ. These are all the defaults except we used /data1 instead of /opt for the install; the server name is rhel4-rs-vm1. Also see KB KM-000010023751 for an explanation of what the ITSM plugins do.



The configuration for the arplugin daemon is in the ar.conf file. “Plugin:”, “Plugin-Path:” and “Plugin-Port:” only apply to the C arplugin daemon. The configuration for the Java plugins are done via separate .xml files. The port the Java plugin server runs on and which plugins are loaded by that Java plugin server are in the pluginsvr_config.xml file. Logging for each Java plugin server and the individual plugins loaded by that Java plugin server are configured in the log4j_pluginsvr.xml file for each. The actual log file name is listed in each log4j_pluginsvr.xml file.

C plugins (loaded by arplugin daemon):
Plugin: /data1/bmc/ARSystem/arealdap/
Plugin: /data1/bmc/ARSystem/ardbcldap/
Plugin: /data1/bmc/ARSystem/approval/bin/
Plugin: /data1/bmc/AtriumCore/rhel4-rs-vm1/cmdb/server/bin/
Plugin: /data1/bmc/BMCRemedyITSMSuite/rhel4-rs-vm1/Shared_Components/bin/
Plugin: /data1/bmc/BMCRemedyITSMSuite/rhel4-rs-vm1/Shared_Components/bin/
Plugin: /data1/bmc/BMCRemedyITSMSuite/rhel4-rs-vm1/Shared_Components/bin/
Plugin: /data1/bmc/BMCRemedyITSMSuite/rhel4-rs-vm1/Shared_Components/bin/

 Java plugins (loaded by 3 separate Java plugin servers, all of which call the same Java plugin server class from the ARServer directory).
Because these don’t run on the C arplugin daemon specified by Plugin-Port: they must be aliased to point to the individual Java plugin server port so that arserverd knows where to call them at.
Server-Plugin-Alias: RMDY.ITSM.RLE RMDY.ITSM.RLE rhel4-rs-vm1:9999
Server-Plugin-Alias: ARSYS.ARF.WEBSERVICE ARSYS.ARF.WEBSERVICE rhel4-rs-vm1:9999
Server-Plugin-Alias: AIS.FILTERAPI AIS.FILTERAPI rhel4-rs-vm1:9556
Server-Plugin-Alias: BMC.ARDBC.ATRIUM.API BMC.ARDBC.ATRIUM.API rhel4-rs-vm1:9556
Server-Plugin-Alias: DSM.FILTER DSM.FILTER rhel4-rs-vm1:9556

From armonitor.conf
            C plugin daemon:
            /data1/bmc/ARSystem/bin/arplugin -s rhel4-rs-vm1 -i /data1/bmc/ARSystem

             ARSystem Java plugin (port 9999 by default):
            /usr/java/jdk1.6.0_06/jre/bin/java -Xmx512m -classpath /data1/bmc/ARSystem/pluginsvr:/data1/bmc/ARSystem/pluginsvr/arpluginsvr75.jar com.bmc.arsys.pluginsvr.ARPluginServerMain -x rhel4-rs-vm1 -i /data1/bmc/ARSystem
            Atrium Java plugin (port 9556 by default):
            Normalization Engine – which is a plugin loaded by a Java plugin server (port 9555 by default):
ARSystem Java Plugin config file and log4j (logging config file):
            Config: pluginsvr_config.xml
            Logging: log4j_pluginsvr.xml
            Plugin logfile: /data1/bmc/ARSystem/db/arjavaplugin.log
Atrium Java Plugin config file and log4j (logging config file):
            Config: pluginsvr_config.xml
            Logging: log4j_pluginsvr.xml
            Plugin logfile: /data1/bmc/AtriumCore/rhel4-rs-vm1/Logs/AtriumPluginSvr.log
Normalization Engine config file and log4j (logging config file):
            Config: pluginsvr_config.xml
            Logging: log4j_pluginsvr.xml
            Plugin logfile: /data1/bmc/AtriumCore/rhel4-rs-vm1/Logs/AtriumPlugin.log