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.

Exporting data from the Product Catalog

When migrating Product Catalog data, you must export the form data from the staging forms on the pre-production server. These staging forms are listed in Required forms for importing custom entries into the Product Catalog.

When an alias is defined for the form, you must use the alias to open the staging form in your browser.

Before you begin

Create a new report of BMC Remedy AR System type for each staging form. When designing this report, include all the fields. You use this report to export the data in .arx format.

To export data from the Product Catalog

  1. With your web browser, log on to the BMC Remedy ITSM server as an administrator.
  2. Use one of the following methods to open the appropriate staging form:
    • Enter the direct access URL.
      http://<midTierServer>:<port>/arsys/forms/<arSystemServer>/<yourForm>
      For example, to open the PDL:ESIDversioninfoCustom form:
      http://CalbroServer:8080/arsys/forms/SanJoseServer/PDL:ESIDversioninfoCustom
    • Open the Object List to search for the form.
      http://<midTierServer>:<port>/arsys/forms
      If the form has an alias, you must search for the alias. Otherwise, search for the form name. If you see two versions of the form listed, select the object listed as a Form, and not the Join Form.
      For more information about creating reports and configuring the object list, see Creating reports and Using the Object List.
  3. Make sure the form is in Search mode.
  4. Search for all records in the form--or for just the subset that you want to export.
    To search for all records, leave the form blank and click Search.
    If you get an error when performing an unqualified search or if your query hits the 1000-record query limit, perform the following steps:
    1. Open the IT Home page.
    2. Open the AR System Administration Console for the BMC Remedy ITSM server.
    3. Select System > General > Server Information.
    4. On the AR System Administration: Server Information form, click the Configuration tab.
    5. Click Allow Unqualified Searches.
    6. In the Server Table Field Chunk Size field, enter a different value (for example, 0, for unlimited records returned in the query). This setting can result in slower performance.
    7. Click OK.
      You can then return to the form and perform the search.
  5. Create reports to export the data from the staging forms.
    1. Select all the records returned in the search.
    2. Click Report.
      When the Reporting Console opens, reports that are associated with the form and that you have permission to access appear in the list. The list can include reports of type AR System, BIRT, and Crystal. If no reports appear in the Reporting Console list, you must create a new report of type AR System.
    3. To generate .arx output, select an AR System type report, as identified in the Report Type field.
      All the records that you selected are passed to the report.
      If no reports appear in the Reporting Console list, then either there is no report associated with this form, or you do not have permission to access it. In that case, you must create a new report of type AR System.
    4. In the Destination field, select File.
    5. In the Format field, select AR Export.
    6. Enter a name for your report.
      Change the file name to the form name, without using illegal characters.
    7. Click Run.
  6. Repeat this procedure for each staging form that you are exporting.

Required forms for importing custom entries into the Product Catalog


Required forms for importing custom entries into the Product Catalog

Object

Form name

Description

Console area

Version Info

PDL:ESIDversioninfoCustom

This table contains information about the custom version of the data to be imported. You must create an entry in this table because the entry identifies the set of custom data being imported.

Version Info is not displayed on the Product Catalog Console.

Manufacturer

PDL:ESIDmanufacturerCustom

This table contains information about the application manufacturers. You must create an entry in this table.

The manufacturer name is displayed in Area 1 of the console. Specific information about a manufacturer is on the COM:Company form.

File

PDL:ESIDfilesCustom

This table contains information about each file.

File information is not displayed on the console, but you can view it by clicking View in Area 3.

Application

PDL:ESIDappsCustom

This table contains information about each application.

Application information is displayed in Area 1.

Application to File relationship

PDL:ESIDappfilesCustom

This table maps files to the applications to which they are associated. Each application consists of a single main executable and zero or more support files.

Files that are related to an application are displayed in Area 3.

Suite

PDL:ESIDsuitesCustom

This table contains information about suites. Suites are collections of applications identified by a combination of the applications and an identifying GUID.

Suites are displayed in Area 1 if the Suite field for the product entry is set to Yes.

Suite to Application relationship

PDL:ESIDsuiteappsCustom

This table contains information that relates suites to applications.

Area 2 displays either of the following items:

  • The products that are part of the suite
  • The suite to which the product is associated.

Signature

PDL:ESIDsignatureCustom

This table contains information about a product signature.

Signatures are not displayed on the Product Catalog Console.

Signature to product relationship

PDL:ESIDsignatureProductCustom

This table contains information about signature product association records.

Signature data is not displayed on the Product Catalog Console.

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.

Comments

  1. Leonard Warren

    There has to be a better way to export the data from the different Remedy Forms as the BMC Remedy User Client is stopped at version 7.6.04 and is no longer supported and that using the AR System option in the AR System Web Report feature is a nightmare as it requires one to sit there and pick EACH ATTRIBUTE one at a time.  There is NOT an option to select all of the attributes at once.

    Also, the Web reporting feature limits the returns to 2000.  Does the AR System option also have this limitation?  I am not sure because I have not accessed over 2000 records using the AR System report method as it is very unfriendly to use.

    So either the customers will need to install BMC Remedy User Client 7.6.04 to run the arx reports or beg for report headers from BMC to support these export processes. Can that be done?

    May 10, 2014 06:54
    1. Bhakti Paranjpe

      Hi Leonard,

      Thank you for your comment. We have contacted the concerned SME for this and someone will get back to you shortly.

      Thanks,

      Bhakti

      May 26, 2014 03:25
    1. Bhakti Paranjpe

      Hi Leonard,

      As per my discussion with the SME:

      Currently, the only solution is to generate reports. It would be great if you can suggest an idea on BMC Communities.

      You can use BMC Remedy Migrator or some other Data Management tool to migrate this information.

      Thank you for your comments.

      Bhakti

      Jun 05, 2014 03:37
  2. Leonard Warren

    Bhakti

     

    Not every one has the BMC Remedy Migrator to export and import data from one environment to the next.  Also, there are no other Data Management Tools that can be used to export the data that I am aware of.  The UDM allows one to move data into the ITSM forms but not into custom forms.  The Atrium Integrator could be used, but that is a lot of work to set it up.

     

    So the issue is if I have to export all of my data of 15,000 people records from a custom form into another environment, I would need to get BMC Remedy Migrator or do it in chunks.  Another options would be to consider running SQL statements or doing a DB to DB copy of the tables into the targeted source and then set up a View or Vendor form and workflow to push the data over.  A lot of work for getting data from what used to be simple in using the BMC Remedy User Report option to export out the information.

     

    Lenny

     

    Jun 05, 2014 07:34