9.1.1 Import flow

(1) Flow of import from the Import job menu

This section explains the workflow when you use the Import job menu.

To import from the Import job menu:

1. Create the CSV file to be imported.

   Create the CSV file that contains the information to be imported into the asset management database. The first line of each CSV file is a title line. If an exported CSV file is to be used as a file for import, the data must have been exported from the same version of Asset Console.

   For the items to be imported, see 20.4 Items to be imported or exported using a job menu.

2. Select the Import job menu.

   The Import window is displayed.

3. Create the import conditions.

   Select the type of information to be imported (such as Device information). Then, for the items managed by the Asset Console, assign the corresponding items in the CSV file, set the constants, and create the conditions.

4. Register the import conditions.

   Specify any name, and register the conditions.

5. Specify the conditions, and execute the import.

   If there is an error in creating conditions, a warning message is displayed. Revise the conditions as necessary to correct the error.

For the procedure for importing information using the Import job menu, see 16.10 Changing asset information in a batch operation (Import).

To Page Top

(2) Flow of import using jamCsvImport.bat

This section explains the workflow when you execute jamCsvImport.bat for import.

To import using jamCsvImport.bat:

1. Create the CSV file to be imported.

   Create the CSV file that contains the information to be imported into the asset management database. The first line of each CSV file is a title line. The items to be imported are the same as those that are imported using the Import job menu. For the items to be imported, see 20.4 Items to be imported or exported using a job menu.

2. Execute jamCsvImport.bat from the command line of the asset management server.

   Import executes in accordance with the specified conditions. If there is an error, an error message is displayed.

   For details about executing jamCsvImport.bat, see 9.1.3 Executing jamCsvImport.bat.

Notes

• When importing information by specifying a customized asset type, be sure to use the data exported by the same version of Asset Console.

• If the number of items managed by the asset management database increases as a result of an Asset Console version upgrade, the number of items to be imported or exported might also increase. Consequently, it might not be possible to import, under the specified condition, data that was exported before the version upgrade.

  When you import data that was exported before the upgrade, specify the properties added after the upgrade in the CSV file.

To Page Top

(3) Flow of import using the jamimport command

Notes

Before executing the jamimport command, stop all the Asset Console services, commands, and tasks in the following order:

1. World Wide Web Publishing Service or World Wide Web Publishing

2. Asset Console commands and tasks

To run Asset Console after having executed the jamimport command, start the services in the reverse of the order in which they were stopped.

This section explains the workflow when you use the jamimport command for import.

To import using the jamimport command:

1. Check the information to be imported and the corresponding class.

   Check to determine the class to which the information to be imported into the asset management database belongs. Also check to determine whether there are other classes that should be imported at the same time.

   For details about the classes corresponding to the information to be imported and the relationships among classes, see 9.1.4 Correspondence between information to be imported using the jamimport command and classes.

2. Create the CSV files to be imported.

   Create CSV files containing the information to be imported into the asset management database as formatted files (data files). There must be a separate data file for each class to be imported.

   When you create data files, including for registering new information, it is useful to have CSV files into which the corresponding classes have been exported.

   For details about the export procedure, see 9.2 Outputting CSV data (exporting). For details about creating data files, see 9.1.6 Creating data files.

3. Create a data files definition file.

   To import multiple data files in a batch operation, create a data files definition file that defines the names of the data files to be imported. If you are importing only one data file, there is no need to create a data files definition file.

   For details about creating a data files definition file, see 9.1.7 Creating a data files definition file.

4. Execute the jamimport command.

   From the asset management server's command line, execute the jamimport command.

   For details about the jamimport command, see 9.1.8 Executing the jamimport (import) command.

   When the jamimport command is executed, the asset information is registered from the CSV files into the asset management database. If there are multiple data files, the asset information is imported in the order specified in the data files definition file.

   When importing association classes, you must first import the object classes to be associated.

   When there is invalid data

   When a data file is imported, the system checks the item title line. If an error is detected, such as the item title line does not match the asset management database table, the import operation is terminated at that point.

   If there is no error in the item title line, the data is imported one line at a time according to the operation code specified in the data line. If there is invalid data, the import operation continues, but the erroneous line is not imported.

To Page Top