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.

Creating the custom Product Catalog data

Before creating the data, you must decide whether you will import custom data on a regular basis. If you import custom data more than once, you must make sure that you are using a unique Version Info in the PDL:ESIDversioninfoCustom form. However, if you clear all entries from the custom staging forms before starting a subsequent custom data import, the unique Version Info is not required. For more information about Version Info, see Staging forms used for importing custom Product Catalog data.

Note

When you import custom data, the BMC_Product and BMC_OperatingSystem classes are populated with entries. No products exist for other classes.

Loading the custom Product Catalog data into the staging forms

You can use BMC Remedy Data Import to load data from supported data sources, such as formatted files and spreadsheets, into the following custom staging forms:

  • PDL:ESIDversioninfoCustom
  • PDL:ESIDmanufacturerCustom
  • PDL:ESIDfilesCustom
  • PDL:ESIDappsCustom
  • PDL:ESIDappfilesCustom
  • PDL:ESIDsuitesCustom
  • PDL:ESIDsuiteappsCustom
  • PDL:ESIDsignatureCustom
  • PDL:ESIDsignatureProductCustom

Note

  • To load data from spreadsheets, you also must create mapping files that specify which spreadsheet fields map to the destination form fields.
  • There is no custom staging form PDL:ESIDaliasesCustom for importing aliases. To import or to create aliases you should use the NE:ProductNameAlias form.

You can also manually create entries in each of the staging forms. The required fields and sample data are shown in the following tables.

Common fields in the custom Product Catalog product staging forms

The following table lists fields that exist on all the staging forms. The Sample data column shows the data values that produce the Product Catalog entries displayed in the Product Catalog Console.


Common fields in staging forms

Field name

Description

Maximum length

Values

Sample data

dataStatus

Status field used to track import progress. All entries should be created as New.

Not applicable

  • New
  • Validated
  • Inactive
  • Imported
  • Update

New

EventCommand

Action field used to trigger import.

60

Status

Additional status field used to track import status.

Not applicable

  • New
  • Assigned
  • Fixed
  • Rejected
  • Closed

New

Short Description

Character field that stores error notes during import.

254

None or "."

Data Version

Data version identifier. Used on all the forms to identify which custom version this entry belongs to.

50

Sample data version

The following sections list the fields in each of the staging forms:

PDL ESIDversioninfoCustom form

The PDL:ESIDversioninfoCustom staging form contains information about the version of custom data that is loaded into the Product Catalog. Use this data to keep track of which version of custom data is installed on your system.


PDL:ESIDversioninfoCustom fields

Field name

Description

Maximum length

Sample data

component

Component name

20

Sample

versionmajor

Major version number

1

versionminor

Minor version number

0

versionmaint

Maintenance version number

0

versionbuild

Build version number

1

description

Complete version number in string format

20

Sample Custom Data

recver

Not currently used

255

PDL ESIDmanufacturerCustom form

The PDL:ESIDmanufacturerCustom staging form contains information about the manufacturers whose applications are loaded in the Product Catalog.

DL:ESIDmanufacturerCustom fields

Field name

Description

Maximum length

Sample data

name

Manufacturer name

254

Sample Manufacturer

mfgid

Manufacturer ID assigned to this manufacturer, as referenced in the COM:Company form

30

Mfgl

address1

Manufacturer address

90 (address1 + address2)

1234 Main Street

address2

Manufacturer address

city

Manufacturer city

60

Sunnyvale

state

Manufacturer state

60

CA

zip

Manufacturer zip

15

94086

country

Manufacturer country

60

United States

businessphone

Manufacturer phone

50

(408) 777-1234

techsupport

Manufacturer technical support information

*http://support.sample.com*

customerservice

Manufacturer support reference

45

(800) 777-1234

url

Manufacturer web address

128

www.sample.com

comments

Miscellaneous comments

254

countrycode

Two-character ISO country code

2

US

Entries where the manufacturer country is not known can be marked with country = "UNKNOWN" and countrycode = "ZY."

PDL ESIDfilesCustom form

The PDL:ESIDfilesCustom staging form contains metadata about the files that are related to applications. Each entry contains the file name and file size of each file that is associated with an application.

PDL:ESIDfilesCustom

Field name

Description

Maximum length

Sample data

name

File name

254

sample.exe

kbfileid

Unique file ID

60

File1

filesize

File size in bytes

50

9482

quickcrc

CRC (ISO 3309) based on the first 1024 bytes of the file

50

timestamp

DOS-style date/time stamp of the file

versionmajor

File major version number

60

1

versionminor

File minor version number

60

1

versionmaint

File maintenance version number

60

1

versionbuild

File build version number

60

1

PDL ESIDappsCustom form

The PDL:ESIDappsCustom staging form contains information about the applications that are loaded in the Product Catalog. Each entry contains the application name and references the manufacturer by manufacturer ID. The main executable file is referenced by file ID.

PDL:ESIDappsCustom Fields

Field name

Description

Maximum length

Sample data

name

Application name

254

Sample Application

kbappid

Application ID

60

App1

filesize

File size in bytes

50

9482

mfgid

Manufacturer ID

90 (address1 + address2)

Mfgl

versionstring

Application version in string format

240

1.0.0.1

versionmajor

Application major version number

60

1

versionminor

Application minor version number

60

0

versionmaint

Application maintenance version number

60

0

versionbuild

Application build version number

60

1

mainexe

File ID of the application's main executable

60

File1

OpSys

0 = Not an operating system 1 = operating system

0

Product Categorization Tier 1

Tier 1 category

60

Software

Product Categorization Tier 2

Tier 2 category

60

Application

Product Categorization Tier 3

Tier 3 category

60

Sample

Origin

0 = Third party 1 = Custom

1

Suite Definition

0 = No 1 = Yes

0

Operating System

Platform description

254

Requires Contract

0 = Yes 1 = No

0

PDL ESIDappfilesCustom form

The PDL:ESIDappfilesCustom staging form relates applications to files.

Note

Each application can have only one main executable file.

PDL:ESIDappfilesCustom

Field name

Description

Maximum length

Sample data

kbappid

Application ID

60

App1

kbfileid

Unique field ID

60

File1

flags

1 = File is the main executable 0 = File is not the main executable

1

AssignedTo

Unique ID to identify this application-file entry

A1F1

PDL ESIDsuitesCustom form

The PDL:ESIDsuitesCustom staging form contains information about the suites that are loaded in the Product Catalog. Suites are named collections of applications. Each entry contains the suite name and references the manufacturer by the manufacturer ID.

PDL:ESIDsuitesCustom fields

Field name

Description

Maximum length

Sample data

identityGuid

GUID for the suite

254

kbsuiteid

Unique suite ID

60

Suite1

name

Suite name

254

Sample Suite

versionstring

Suite version in string format

240

2.0

mfgid

Manufacturer ID

60

Mfgl

OpSys

0 = Not an operating system 1 = Operating system

0

licensesuiteID

The ID of the grouping-level entry for this suite

254

Product Categorization Tier 1

Tier 1 category

60

Software

Product Categorization Tier 2

Tier 2 category

60

Application

Product Categorization Tier 3

Tier 3 category

60

Sample

Origin

0 = Third party 1 = Custom

1

Suite Definition

0 = No 1 = Yes

1

Operating System

Platform description

254

Requires Contract

0 = Yes 1 = No

0

PDL ESIDsuiteappsCustom form

The PDL:ESIDsuiteappsCustom staging form identifies which applications are associated with a particular suite.

PDL:ESIDsuiteappsCustom fields

Field name

Description

Maximum length

Sample data

kbappid

Application ID

60

App2

kbsuiteid

Unique suite ID

60

Suite1

AssignedTo

Unique ID to identify this application-suite entry

SuiteApp2

PDL ESIDsignatureCustom form

The PDL:ESIDsignatureCustom staging form contains information about the signature file of a product.

Note

If you have customized the signature, you must include this form for migrating Product Catalog data.

PDL:ESIDsignatureCustom

Field name

Description

Data type

Maximum length

Signature ID

Random unique string

String

254

Version

Signature version

String

50

Grouping

Signature group

String

50

Type

User-defined string used for data segregation

String

50

Signature file

Location of the signature file

String

Not applicable

PDL ESIDsignatureProductCustom form

The PDL:ESIDsignatureProductCustom staging form contains information about the signature product association records.

Note

If you have customized the signature, you must include this form for migrating Product Catalog data.


PDL:ESIDsignatureProductCustom

Column

Description

Maximum length

kbappid

Application ID

60

Signature ID

Random unique string

254

Platform

Name of the platform

254

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