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.

Generating forms for other applications

Some BMC Remedy AR System applications, such as BMC Remedy Asset Management, use their own forms as an interface to BMC Atrium CMDB data. These forms are typically self-joins, where a BMC Atrium CMDB class form is both the primary and secondary form. If you have developed such an application, you can allow BMC Atrium CMDB generate those forms. This method of generation keeps the forms synchronized with extensions that you make to the data model.

You must configure the generation of forms in advance to specify how you want them created, and then, after modifying the data model, launch form generation.

To configure form generation for another application

  1. Using BMC Remedy Developer Studio, create a companion form for each class in the data model for which you want to generate forms.
  2. Create a form to specify information about the classes for which you want to generate forms.
    Each entry in the form corresponds to one class. The form must have the following character fields, all with a maximum input length of 80 characters:
    • Class Keyword
    • Form Name
    • Primary Join Form
    • Secondary Join Form
  3. Create entries in the new form for each class for which you want to generate a form, entering this information:

    Class KeywordThe class ID of the class for which a form is generated. This field is required. The class ID is case sensitive, and might not be the same as the class name. For example, the class with a name of BMC_ComputerSystem has a class ID of BMC_COMPUTERSYSTEM. For more information about the class ID of a specific class, see the BMC Atrium CMDB Data Model Help.
    Form NameThe name of the companion form that your application uses for the class. This form is modified if it exists and created if it does not exist. This field is required.
    Primary Join Form(optional) If you specify a form name here, the form generated is a join of this form as the primary join form and the BMC Atrium CMDB class form as the secondary join form. This field must be blank if a secondary join form is specified.
    Secondary Join Form(optional) If you specify a form name here, the form generated is a join of the BMC Atrium CMDB class form as the primary join form and this form as the secondary join form. This field must be blank if a primary join form is specified.

    Forms are not necessarily generated for every entry in this form when the form generation utility runs. You specify the forms that are generated for each run of the utility with parameters explained in the following procedure.


    Note

    If you do not specify a primary join form or secondary join form, the form generated is a self-join of the BMC Atrium CMDB class form as both the primary and secondary join forms. Unless you have other data you want to display with BMC Atrium CMDB data, you should leave both fields blank.

To launch form generation

  1. Wait until synchronization completes and no classes are in the Change Pending state.
    If any classes are still in the Change Pending state, the form generation utility aborts with an error.
  2. Create an entry in the Application Pending form, specifying the following field values:
    • CategoryCMDB
    • CommandSync-UI
    • Other Short — <commandSyntax>

      <commandSyntax> must include the following parameters:

      ParameterDescription
      -f<configFormName>The name of the form created in step 2.
      -g<formNameFieldID>The field ID of the Form Name field on the form created in step 2.
      -c<classKeywordFieldID>The field ID of the Class Keyword field on the form created in step 2.
      -C<classID>

      The class ID of the class for which a form is generated. You must provide either this parameter or -t, but not both.

      Note

      The class ID is case sensitive, and might not be the same as the class name. For example, the class with a name of BMC_ComputerSystem has a class ID of BMC_COMPUTERSYSTEM. For more information about the class ID of a specific class, see the BMC Atrium CMDB Data Model Help.
      -t<timeStamp>A UNIX epoch time value. Forms are generated only for classes modified after this time and all of their subclasses. You must provide either this parameter or -C, but not both.


      <commandSyntax> can also include these optional parameters:

      ParameterDescription
      -RSpecifies that forms are also generated for all subclasses of the class specified with -C.
      -p<primaryJoinFormNameFieldID>The field ID of the Primary Join Form field on the form created in step 2. If you populated the Primary Join Form field, you must specify this parameter.
      -s<secondaryJoinFormNameFieldID>The field ID of the Secondary Join Form field on the form created in step 2. If you populated the Secondary Join Form field, you must specify this parameter.
      -DEnables debugging for this operation. Debugging increases the details that are written to the log file.

After you generate and synchronize the forms, log messages are saved in the CMDBSynchronizeUI.log file. You can view the log file to track the status of of the synchronization. The file can be accessed from the AtriumCore/Logs folder.

The CMDBSynchronizeUI.log file saves the following information:

  • Errors and Warnings for Active Link, Filter, Escalation associations and missing Attributes or Classes.
  • Synchronization completion status. If this line is missing from the last line of the log then the synchronization has not yet completed.

Note

You can use workflow to create these Application Pending entries, but as mentioned in step 1, it cannot be executed while any classes are in Change Pending state.

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

Comments

  1. Andreas Mitterdorfer

    Please can you review log file location? CMDBSynchronizeUI.log is still (19.08) generated in AtriumCore/Logs folder.

    Jun 30, 2020 08:19
    1. Maithili Deshpande

      Hi Andreas, 

      Thank you for pointing out this issue with the content. We have corrected the topic with your feedback. Additionally, the log files in the recent versions (20.02 and later) are generated in the following location:

      • (Windows) <installationdirectory\ARSystem\Arserver\db 
      • (UNIX) <serverInstallationDirectory>/db

      Regards,
      Maithili

      Aug 03, 2020 12:04