Space banner


This documentation supports the 19.11 version of BMC Knowledge Management, which is available only to BMC Helix subscribers (SaaS).
To view an earlier version, select the version from the Product version menu.

Converting articles for new templates

Perform this procedure if you want to convert articles that are based on new templates created for the 7.2 and 7.5 releases.

Best Practice

Review the parameters in the file before performing this procedure and update the file as needed. For more information, see Updating the file.

We recommend that you disable the notifications during the conversion process to avoid generating unwanted alerts.

To convert articles and associations

Conversion of new templates is supported only if the XML schema of the new template is identical to the XML schema of the 7.2 or 7.5 release.

  1. In the Knowledge Management Console, choose Functions > Article Conversion Tool and click the New Conversion icon.
  2. In the Conversion Type field of the General tab, select the Upgrade option.
  3. Enter the following information in the General tab:
    • Full path—Specify a full path to the data folder that contains the articles you want to convert. The path can be:
      • A full path to a folder on the local file system such as C:\data.
      • A UNC (Uniform Naming Convention) for remote access in the following format: \\ComputerName\SharedFolder\Resource.\

      • A full path to a shared folder on the network.

        Make sure that the data\kms_data folder contains four subfolders: templates, draft, publish, and attachments.

    • Owner Group — Select a user group from the list to specify the group.
    • Owner — Select the articles owner from the list.
    • Convert Only Visibility Groups--Select this option if you want to convert only visibility groups information. This option is useful when you already converted old articles without visibility groups information and now you want to convert the visibility group information without converting all the articles again.
  4. Click Organization and Categorization and select a company from the list.
    Select one of the following conversions mode:
    • Use Template Fields — The conversion tool copies organization and categorization values from the XML template into the AR form.
    • Use Fixed Values — You enter organization and categorization values in the fields below and the conversion tool automatically enters these values for all the converted articles.
      Enter values for Product CategorizationOperational CategorizationBusiness ServiceOrganization, and Location fields.
  5. Click the Mapping tab to match fields in an XML template to fields in the appropriate AR form.
    1. In the XML Template Name list, select a template for mapping.
    2. In the AR Form Name list, select an BMC Remedy AR System form to which the selected XML template is converted.
    3.  Select a field from the AR Field list.
    4. Select a matching field from the XML Field list.
    5.  Click Add Field.
      The matched fields are added to the Mapping box.
    6. Repeat steps c to e to map all the fields in the template.
    7. After you complete mapping all the fields, click Save .
  6. (optional ) Repeat step 3 for all of the XML templates that you want to convert.
  7. Click the Run tab and select one or more XML templates for conversion.
  8. Click Run to start the conversion.
    The conversion may take a while, depending on the number of articles that exist in the folder you specified.
    The tool does not provide progress indication of the conversion. you can retrieve progress information from the arjavaplugin.log file that is located in the InstallationHome\ARSystem\Arserver\Db folder.
    The following text indicates that the conversion has completed.

    ** Knowledge Article Conversion REPORT **
    There are types of Articles that were
    selected to transfer:
    There were 50 found for Migration
    Migrated successfully: 50
    Failed: 0
    ###############END REPORT##################


    To ensure that the results of the conversion job are saved to the arjavaplugin.log file, verify that the log level parameter in the log4j_pluginsvr.xml file is set to info, as follows:

    <logger additivity="true" name="com.bmc.itsm.rkm">   
          <level value="info"/>

    If you manually update the log level parameter value value to info, you must restart the BMC Remedy AR System Server for the change to take effect.

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