Hitachi

JP1 Version 12 JP1/IT Desktop Management 2 - Asset Console Configuration and Administration Guide


9.1.2 Notes on the import operation

This section provides notes about creating CSV files and specifying import conditions.

Organization of this subsection

(1) Non-editable properties

The Update indicator managed item (UpdateInd property) is information that is used by the asset management system, so do not edit it. When information loaded from JP1/IT Desktop Management 2 - Manager is imported using the jamimport command for updating, the value for Update indicator must be specified correctly. If an invalid value is specified, the information might be deleted the next time information is loaded from JP1/IT Desktop Management 2 - Manager.

To avoid such a situation, it is recommended that when loading management information from JP1/IT Desktop Management 2 - Manager after executing an import, all information be loaded irrespective of the update date.

(2) Importing classes with ID

When importing other than exported data, to import a class with an ID, such as Asset ID or Contract ID, specify the ID in the range 10001 to 1000000000. For the department ID or location ID, specify a value that is not in the range from 1000000001 to 9999999999. Each specified ID must be unique. If a specified ID is not within this range, it might duplicate a value assigned automatically by Asset Console, thereby resulting in an error.

Specify an ID within the range from 10001 to 1000000000 for the following properties:

For the following ID specification properties, you must specify a value that is not in the range from 1000000001 to 9999999999:

(3) Importing properties that can be specified using only alphanumeric characters

To import the following properties, their values must be specified using alphanumeric characters:

(4) Specifying the managed items (properties) for user extension

For some managed items, items have been prepared for adding as needed. These are items (properties) for which the name includes UserProperty.

For such a user extension item, add a managed item in the Customize window and then specify the value to be managed.

For details about adding managed items, see 11.2 Changing managed items (Customize Managed Items).

(5) Importing object classes that are associated by the matching key property

When importing using the jamimport command, and when importing object classes that are associated by the matching key property, make sure that all have the same keyproperty value.

For an object class that is always paired with asset information, such as hardware information, make sure that part of the hardware information and asset information is imported.

(6) Update control during import operation

Class properties include information (Update control) that determines whether the update operation is to be allowed when an attempt is made to update the same information more than once.

If exported data is imported and the same information had been updated after the export operation, the value of this Update control has changed. Therefore, the data cannot be imported with the value used during the export operation.

To overwrite the data to be imported regardless of whether any changes have been made since the export operation, delete the Update control column (UpdateTime) and then import the data.

(7) Specification of CreationClassName

If you use the jamimport command to import data, make sure that you specify the object class name in the CreationClassName property of each object class.

(8) Using Microsoft Excel for editing CSV files

When editing CSV files to be registered in Asset Console, if you use Microsoft Excel to open the files directly, the beginning 0 is automatically deleted from numerical values that begin with 0, such as codes and IDs. As a result, these values might be updated into those different from the original. Therefore, when using Microsoft Excel, use the Import Text File command to set the column data format to Text, and then load and edit the file.