Hitachi

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

9.1.4 Correspondence between information to be imported using the jamimport command and classes

A CSV file to be imported by the jamimport command is created for each class. Therefore, before creating a CSV file, check its relationship with classes and determine the class to be imported to register desired information.

With some asset information, such as hardware information, you need to import multiple classes before you can use the registered information with asset management jobs.

For details on class relationships managed by the asset management database, see 20.1.3 Relationships between classes.

When an association class must be imported

To import object classes associated with different key properties, you must also import the association class that associates the object classes.

When there is a weak association with an object class

If the object class to be imported has a weak association with AssetInfo, information about AssetInfo must have been registered. If AssetInfo is deleted, all object classes that have weak association with AssetInfo are also deleted.

The same applies to object classes that have weak association with SoftwareInfo, InstalledInfo, SoftwareList, Contract, or ContractHistory.

The following sections describe the information that needs to be imported when multiple classes are imported using the jamimport command. Notes about creating CSV files are also provided.

Organization of this subsection

(1) Importing devices and information about devices

The table below describes the classes that need to be imported in order to add, update, or delete device information.

Table 9‒2: Classes to be imported in order to register device information

Class that needs to be imported

Associated class

Description

AssetInfo

GroupInfo#

To specify information about a group, specify the same value as the property corresponding to the GroupInfo object class.

LocationInfo#

To specify information about a location, specify the same value as the property corresponding to the LocationInfo object class.

UserInfo#

To specify information about a user, specify the same value as the property corresponding to the UserInfo object class.

HardwareInfo

AssetInfo

For AssetID, specify the same ID as for the corresponding AssetInfo object class.

#

For a group, location, or user, the corresponding name is set by the Data maintenance task if GroupID, LocationID, or UserID is specified correctly.

However, if the IDs specified for GroupID and LocationID are not in the corresponding classes, the name is not displayed in the window.

Notes

  • To delete information about a device, Hitachi recommends that you change the value of the AssetStatus property of AssetInfo to 999 (Erase) and then use the Data maintenance task to delete it. When deleting information during an import operation, make sure that AssetInfo is also deleted, not just HardwareInfo.

  • The IPAddress of the HardwareInfo is not the IP address used as the IP address management information.

(a) Importing information about the software installed on a device

The table below describes the classes that need to be imported in order to add, update, or delete information about software installed on a device.

You can register installed software information for a device whose device type is computing (code: 100 to 198).

Table 9‒3: Classes to be imported in order to register installed software information

Class that needs to be imported

Associated class

Description

InstalledInfo

AssetInfo

For AssetID, specify the same ID as for the corresponding AssetInfo object class.

InstalledList

For InstalledID, specify the same ID as for the corresponding InstalledList object class.

(b) Importing network information for a device

The table below describes the classes that need to be imported in order to add, update, or delete network information for a device.

You can register network information for a device whose device type is computing (code: 100 to 198) or networking (code: 300 to 398).

Table 9‒4: Classes to be imported in order to register network information

Class that needs to be imported

Associated class

Description

NetworkInfo

AssetInfo

For AssetID, specify the same ID as for the corresponding AssetInfo object class.

IPAddress

To specify IPAddress, the IP address to be specified must have been registered in the IPAddress object class.

However, if you use the DHCP server, do not import IPAddress.

IPAddressLink

If you do not set DHCP server name, you need to register the association with the IPAddress object class at the corresponding IP address.

Notes

  • To update or delete the value of the IPAddress property of NetworkInfo, also update or delete IPAddressLink. If you update or delete the value of IPAddress without deleting IPAddressLink, the delete IP address is treated as being in use.

  • If a device using an IP address is deleted, delete only IPAddressLink.

    The IP addresses beyond the range defined in the AddressGroup object class are deleted by the Data maintenance task unless they are in use by a device.

To Page Top

(2) Importing information about software and licenses

The table below describes the classes that need to be imported in order to add, update, or delete the information about software.

Table 9‒5: Classes to be imported in order to register information about software

Class that needs to be imported

Associated class

Description

AssetInfo

GroupInfo#

To specify information about a group, specify the same value as the property corresponding to the GroupInfo object class.

SoftwareInfo

AssetInfo

For AssetID, specify the same ID as for the corresponding AssetInfo object class.

SoftwareList

For SoftwareListID, specify the same ID as for the SoftwareList object class.

#

For a group and user name, the corresponding name is set by the Data maintenance task if GroupID is specified correctly.

However, if the ID specified for GroupID is not in the corresponding class, the name is not displayed in the window.

Notes

  • In the case of a software with unlimited licenses, specify nothing for NumberOFLicense. If specified, the software is registered as an asset with the specified number of licenses owned.

  • To delete information about software, Hitachi recommends that you set the value of the SoftwareStatus property of AssetInfo to 999 (Erase) and then delete it using the Data maintenance task.

    When deleting information during an import operation, make sure that AssetInfo is also deleted, not just SoftwareInfo.

(a) Importing software key information

The table below describes the classes that need to be imported in order to add, update, or delete software key information.

Table 9‒6: Classes to be imported in order to register software key information

Class that needs to be imported

Associated class

Description

SoftwareKeyInfo

AssetInfo

For AssetID, specify the same ID as for the corresponding AssetInfo object class.

SoftwareList

For SoftwareListID, specify the same ID as for the SoftwareList object class.

MachinePermitLink

To register the target of an install license, you need to register its association with the target AssetInfo object class.

UserPermitLink

To register the target of a user license, you need to register its association with the target UserInfo object class.

(b) Importing license information

The table below describes the classes that need to be imported in order to add, update, or delete license information.

Table 9‒7: Classes to be imported in order to register license information

Class that needs to be imported

Associated class

Description

LicenseInfo

SoftwareList

For SoftwareListID, specify the same ID as for the SoftwareList object class.

(c) Importing volume contract information

The table below describes the classes that need to be imported in order to add, update, or delete volume contract information.

Table 9‒8: Classes to be imported in order to register volume contract information

Class that needs to be imported

Associated class

Description

VolumeContract

VolumeContractLink

To register an asset that is subject to volume license, you need to register its association with the target AssetInfo object class.

Note

If you delete volume contract information, Hitachi recommends that you change the value of the ContractStatus property of VolumeContract to Erase (999) and use the Data maintenance task to delete it.

To Page Top

(3) Importing contract information

The table below describes the classes that need to be imported in order to add, update, or delete contract information.

Table 9‒9: Classes to be imported in order to register contract information

Class that needs to be imported

Associated class

Description

Contract

ContractLeaseLink

To register an asset subject to lease contract, you need to register its association with the target AssetInfo object class.

ContractMaintenanceLink

To register an asset subject to maintenance contract, you need to register its association with the target AssetInfo object class.

ContractRentalLink

To register an asset subject to rental contract, you need to register its association with the target AssetInfo object class.

Note

To delete information about a contract, Hitachi recommends that you change the value of the ContractStatus property of Contract to 999 (Erase) and then use the Data maintenance task to delete it.

To Page Top

(4) Importing IP group information

The table below describes the classes that need to be imported in order to add, update, or delete IP group information.

Table 9‒10: Classes to be imported in order to register IP group information

Class that needs to be imported

Associated class

Description

AddressGroup

IPAddress

To define a new group or change a range, you need to register all IP addresses in the range defined as group in the IPAddress object class.

Note

During an import operation, do not delete any IP group information. If deleted, the IP addresses in use can no longer be managed correctly.

To Page Top

(5) Importing group information

The table below describes the classes that need to be imported in order to register group information.

Table 9‒11: Classes to be imported in order to register group information

Class that needs to be imported

Associated class

Description

GroupInfo

UserInfo

To register a user belonging to a group, import the UserInfo object class.

MemberLink

To register a user belonging to each group, you need to register its association with the UserInfo object class.

To Page Top

(6)  Importing user information

The table below describes the classes that need to be imported in order to register user information.

Table 9‒12: Classes to be imported in order to register user information

Class that needs to be imported

Associated class

Description

UserInfo

GroupInfo

To add a user's group, import the GroupInfo object class.

MemberLink

To register a new user or change user's group, you need to register its association with the GroupInfo object class.

If a user is not associated with a group, the imported user will not be displayed in windows.

RoleInfo

To set a role for a user, import the RoleInfo object class.

A user with no role set cannot log in to Asset Consol.

AuthorityLink

To set a role for a user, you need to register its association with the RoleInfo object class.

Note

Do not delete a user whose UserID is admin and that is used in the AssetInfo object class.

To Page Top

(7) Importing role information

The table below describes the classes that need to be imported in order to register role information.

Table 9‒13: Classes to be imported in order to register role information

Class that needs to be imported

Associated class

Description

RoleInfo

UserInfo

To set a role for a user, import the UserInfo object class.

A user with no role set cannot log in to Asset Console.

AuthorityLink

To set a role for a user, you need to register its association with the UserInfo object class.

Notes

  • To revoke the role set for a user, delete the AuthorityLink association class.

  • Do not delete a role whose RoleID is administrator.

To Page Top

(8) Importing patch information

The table below describes the classes that need to be imported in order to register search conditions for devices needing patches.

Table 9‒14: Classes to be imported in order to register patch information

Class that needs to be imported

Associated class

Description

PatchInfo

AssetInfo

For AssetID, specify the same ID as for the corresponding object class AssetInfo.

PatchList

For PatchID, specify the same ID as for the corresponding patch list.

To Page Top

(9) Importing virus definition information

The table below describes the classes that need to be imported in order to register search conditions for virus definition information.

Table 9‒15: Classes to be imported in order to register virus definition information

Class that needs to be imported

Associated class

Description

InstalledVirusDefInfo

AssetInfo

For AssetID, specify the same ID as for the corresponding object class AssetInfo.

To Page Top

(10) Importing a maintenance log

The table below describes the classes that need to be imported in order to register a maintenance log.

Table 9‒16: Classes to be imported in order to register a maintenance log

Class that needs to be imported

Associated class

Description

Maintenance

AssetInfo

To associate a maintenance log with an asset and register it, specify the same ID as for the AssetInfo object class that corresponds to AssetID.

To not associate a maintenance log with any asset, this class is not needed.

To Page Top

(11) Importing a transfer log

The table below describes the classes that need to be imported in order to register a transfer log.

Table 9‒17: Classes to be imported in order to register a transfer log

Class that needs to be imported

Associated class

Description

AssetUpdateRecord

AssetInfo

For AssetID, specify the same ID as for the corresponding AssetInfo object class.

Note

For the group, location, and user names, the specified values are registered, regardless of whether they exist in the GroupInfo, LocationInfo, and UserInfo object classes.

To Page Top

(12) Importing contract history

The table below describes the classes that need to be imported to register contract history.

Table 9‒18: Classes to be imported to register contract history

Class that needs to be imported

Associated class

Description

ContractHistory

Contract

For ContractID, specify the same ID as for the corresponding Contract object class.

To Page Top

(13) Importing contract asset history

The table below describes the classes that need to be imported to register contract asset history.

Table 9‒19: Classes to be imported to register contract asset history

Class that needs to be imported

Associated class

Description

ContractAssetHistory

ContractHistory

For ContractID, specify the same ID as for the corresponding ContractHistory object class.

AssetInfo

For AssetID, specify the same ID as for the corresponding AssetInfo object class.

To Page Top

(14) Importing official authority information

The table below describes the classes that need to be imported in order to register official authority information.

Table 9‒20: Classes to be imported in order to register official authority information

Class that needs to be imported

Associated class

Description

JobRoleInfo

UserInfo

When registering a user with authority, import the object class UserInfo.

JobRoleLink

When registering a user with authority, the relationship with the object class UserInfo must be registered.

Note

Before deleting official authority information, confirm that there are no Items that use that official authority.

To Page Top

(15) Importing related asset information

The following table describes the classes that must be imported in order to register related asset information.

Table 9‒21: Classes to be imported in order to register related asset information

Class that needs to be imported

Associated class

Description

RelationAssetInfo

AssetInfo

For ParentAssetID and ChildAssetID, specify the same ID as for the corresponding object class AssetInfo.

Note

For the processing method, specify Add or Delete. You cannot specify Update or Add/update.

To Page Top

(16) Importing division information

The following table describes the classes that must be imported in order to register division information.

Table 9‒22: Classes to be imported in order to register division information

Class that needs to be imported

Associated class

Description

DivisionInfo

GroupInfo

For DivisionID, specify the same ID as for the corresponding object class GroupInfo.

DivisionLink

For DivisionID, specify the same ID as for the corresponding object class DivisionInfo.

For GroupID, specify the same ID as for the corresponding object class GroupInfo.

DivisionUserLink

For DivisionID, specify the same ID as for the corresponding object class DivisionInfo.

For UserID, specify the same ID as for the corresponding object class UserInfo.

Note

For the processing method, specify Add or Delete. You cannot specify Update or Add/update.

To Page Top

Copyright (C) 2019, 2022, Hitachi, Ltd.

Copyright (C) 2019, 2022, Hitachi Solutions, Ltd.

Copyright, patent, trademark, and other intellectual property rights related to the "TMEng.dll" file are owned exclusively by Trend Micro Incorporated.