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.

Creating the package.xml file

After you export class definitions, you create the package.xml file. The package.xml file contains the registration and dependency information for the extension. The registration information defines the extension that you are creating. When the extension loader runs, it stores the extension registration values that you specify in the package.xml file, such as the extension name, version, and GUID in the SHARE:Application_Properties form.

To create the package.xml file

  1. Depending on whether you are creating a new extension or modifying an existing extension, perform one of the following steps:
    • If you are creating a new extension, generate a GUID using the cg command of the cmdbdriver program.
    • If you are modifying an existing extension, skip to step 2.
  2. Specify values for the following elements in the package.xml file:
    • Registration information – Specify the following registration information for the extension:

      <name>

      The name of the extension.

      <guid>

      The GUID of the extension. For new extensions, specify the GUID that you created in step 1. For existing extensions, specify the currently existing GUID.

      <version>

      The version number of the extension. Modify the version number only if you are modifying an extension.

    • Dependencies – Specify the following dependency information for the extension:

      <applications>

      The applications that the extension depends upon. The applications specified here can be other extensions, BMC Remedy AR System applications, or the BMC Remedy AR System Server on which you want to install the extension.

      <version>

      The version number of the application specified in the <application> element. You can either specify a value for the <version> element, which indicates the exact version number required for the application, or you can specify values for the <minversion> and <maxversion> elements, which indicate the range of permissible version numbers for the application.

      Note

      The <minversion> and <maxversion> elements are optional. Use them to restrict the extension up to a specific existing application version, and do not use version numbers that do not exist, such as BMC Atrium CMDB 99.99.9.

  3. Save the package.xml file under the extension subdirectory you created in Exporting class definitions by using cmdbdriver

GUIDs, extensions, and the package.xml file

In the the package.xml file, a GUID is a unique ID for the extension. This ID is used by the extension loader program to determine if an extension is already installed. After you create an extension with a specific GUID, you can only change the version number to update the extension. The GUID remains the same for the life span of an extension.

Example: package.xml


<?xml version="1.0" standalone="yes" ?>
<package>
   <!-- This extension adds a class.-->
   <name> ComSys Hardware Component</name>
   <guid>OS005056C0000898YWQgUsMLAAKwAA</guid>
   <version>1.0</version>
   <dependencies>
      <applications>
      <list>cmdb</list>
         <!-- Requires CMDB -->
         <cmdb>


         </cmdb>
      </applications>
   </dependencies>
</package>



This package.xml example instructs the extension loader program to install the ComSys Hardware Component class extension version 1.0. The first line of code is an XML version tag that is required for all XML files.

Note

When you specify a GUID for the BMC Atrium CMDB dependency in your package.xml file, make sure you use the same GUID as shown in the example. This is the GUID stored in the SHARE:Application_Properties AR System form for the BMC Atrium CMDB.

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

Comments