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

3021-3-E16-20(E)

Notices

Relevant program products

For details about the supported operating systems and the service packs or patches that are required by JP1/IT Desktop Management 2, see the Release Notes.

JP1/IT Desktop Management 2 - Manager

P-2A42-78CL JP1/IT Desktop Management 2 - Manager version 12-60

The above product includes the following:

P-CC2A42-7ACL JP1/IT Desktop Management 2 - Manager version 12-60 (for Windows Server 2019, Windows Server 2016, and Windows Server 2012)

P-CC2A42-7BCL JP1/IT Desktop Management 2 - Agent version 12-60 (for Windows Server 2019, Windows Server 2016, Windows 10, Windows 8.1, Windows 8, Windows Server 2012, Windows 7, and Windows Server 2008 R2)

P-CC2A42-7CCL JP1/IT Desktop Management 2 - Network Monitor version 12-00 (for Windows Server 2019, Windows Server 2016, Windows 10, Windows 8.1 Enterprise, Windows 8.1 Pro, Windows 8 Enterprise, Windows 8 Pro, Windows Server 2012, Windows 7 Enterprise, Windows 7 Professional, and Windows 7 Ultimate)

P-CC2A42-7DCL JP1/IT Desktop Management 2 - Asset Console version 12-60 (for Windows Server 2019, Windows Server 2016, and Windows Server 2012)

P-CC2A42-7PCL JP1/IT Desktop Management 2 - Internet Gateway version 12-00 (for Windows Server 2019, Windows Server 2016, and Windows Server 2012)

Trademarks

HITACHI, HiRDB, Job Management Partner 1, JP1, uCosminexus are either trademarks or registered trademarks of Hitachi, Ltd. in Japan and other countries.

Acrobat is a registered trademark or a trademark of Adobe Systems Incorporated in the United States and/or other countries.

Active Directory is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.

ActiveX is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.

Adobe is a registered trademark or a trademark of Adobe Systems Incorporated in the United States and/or other countries.

AIX is a trademark of International Business Machines Corporation, registered in many jurisdictions worldwide.

All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc., in the United States and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc.

AMD is a trademark (or registered trademark) of Advanced Micro Devices, Inc.

AMD Athlon is a trademark (or registered trademark) of Advanced Micro Devices, Inc.

AMD Opteron is a trademark (or registered trademark) of Advanced Micro Devices, Inc.

BSAFE is a trademark or registered trademark of Dell Inc. in the United States and other countries.

Excel is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.

Hyper-V is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.

IBM is a trademark of International Business Machines Corporation, registered in many jurisdictions worldwide.

Intel is a trademark of Intel Corporation or its subsidiaries.

Internet Explorer is either a registered trademark or trademark of Microsoft Corporation in the United States and/or other countries.

Itanium is a trademark of Intel Corporation or its subsidiaries.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Microsoft is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.

OneDrive is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Pentium is a trademark of Intel Corporation or its subsidiaries.

PowerPC is a trademark of International Business Machines Corporation, registered in many jurisdictions worldwide.

Reader is a registered trademark or a trademark of Adobe Systems Incorporated in the United States and/or other countries.

SQL Server is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.

Windows Server is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.

Xeon is a trademark of Intel Corporation or its subsidiaries.

Other company and product names mentioned in this document may be the trademarks of their respective owners.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/).

This product includes software developed by Ben Laurie for use in the Apache-SSL HTTP server project.

Portions of this software were developed at the National Center for Supercomputing Applications (NCSA) at the University of Illinois at Urbana-Champaign.

This product includes software developed by the University of California, Berkeley and its contributors.

This software contains code derived from the RSA Data Security Inc. MD5 Message-Digest Algorithm, including various modifications by Spyglass Inc., Carnegie Mellon University, and Bell Communications Research, Inc (Bellcore).

Regular expression support is provided by the PCRE library package, which is open source software, written by Philip Hazel, and copyright by the University of Cambridge, England. The original software is available from ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/

This product includes software developed by Ralf S. Engelschall <rse@engelschall.com> for use in the mod_ssl project (http://www.modssl.org/).

This product includes software developed by IAIK of Graz University of Technology.

This product includes software developed by Daisuke Okajima and Kohsuke Kawaguchi (http://relaxngcc.sf.net/).

This product includes software developed by the Java Apache Project for use in the Apache JServ servlet engine project (http://java.apache.org/).

This product includes software developed by Andy Clark.

This product bundles Dell BSAFE? software developed by Dell Inc. in the United States.

Java is a registered trademark of Oracle and/or its affiliates.

Java is a registered trademark of Oracle and/or its affiliates.

1. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)

2. This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)

3. This product includes software written by Tim Hudson (tjh@cryptsoft.com)

4. This product includes the OpenSSL Toolkit software used under OpenSSL License and Original SSLeay License. OpenSSL License and Original SSLeay License are as follow:

LICENSE ISSUES

==============

The OpenSSL toolkit stays under a dual license, i.e. both the conditions of

the OpenSSL License and the original SSLeay license apply to the toolkit.

See below for the actual license texts. Actually both licenses are BSD-style

Open Source licenses. In case of any license issues related to OpenSSL

please contact openssl-core@openssl.org.

OpenSSL License

---------------

/* ====================================================================

* Copyright (c) 1998-2016 The OpenSSL Project. All rights reserved.

*

* Redistribution and use in source and binary forms, with or without

* modification, are permitted provided that the following conditions

* are met:

*

* 1. Redistributions of source code must retain the above copyright

* notice, this list of conditions and the following disclaimer.

*

* 2. Redistributions in binary form must reproduce the above copyright

* notice, this list of conditions and the following disclaimer in

* the documentation and/or other materials provided with the

* distribution.

*

* 3. All advertising materials mentioning features or use of this

* software must display the following acknowledgment:

* "This product includes software developed by the OpenSSL Project

* for use in the OpenSSL Toolkit. (http://www.openssl.org/)"

*

* 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to

* endorse or promote products derived from this software without

* prior written permission. For written permission, please contact

* openssl-core@openssl.org.

*

* 5. Products derived from this software may not be called "OpenSSL"

* nor may "OpenSSL" appear in their names without prior written

* permission of the OpenSSL Project.

*

* 6. Redistributions of any form whatsoever must retain the following

* acknowledgment:

* "This product includes software developed by the OpenSSL Project

* for use in the OpenSSL Toolkit (http://www.openssl.org/)"

*

* THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY

* EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR

* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT

* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;

* LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,

* STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)

* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED

* OF THE POSSIBILITY OF SUCH DAMAGE.

* ====================================================================

*

* This product includes cryptographic software written by Eric Young

* (eay@cryptsoft.com). This product includes software written by Tim

* Hudson (tjh@cryptsoft.com).

*

*/

Original SSLeay License

-----------------------

/* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)

* All rights reserved.

*

* This package is an SSL implementation written

* by Eric Young (eay@cryptsoft.com).

* The implementation was written so as to conform with Netscapes SSL.

*

* This library is free for commercial and non-commercial use as long as

* the following conditions are aheared to. The following conditions

* apply to all code found in this distribution, be it the RC4, RSA,

* lhash, DES, etc., code; not just the SSL code. The SSL documentation

* included with this distribution is covered by the same copyright terms

* except that the holder is Tim Hudson (tjh@cryptsoft.com).

*

* Copyright remains Eric Young's, and as such any Copyright notices in

* the code are not to be removed.

* If this package is used in a product, Eric Young should be given attribution

* as the author of the parts of the library used.

* This can be in the form of a textual message at program startup or

* in documentation (online or textual) provided with the package.

*

* Redistribution and use in source and binary forms, with or without

* modification, are permitted provided that the following conditions

* are met:

* 1. Redistributions of source code must retain the copyright

* notice, this list of conditions and the following disclaimer.

* 2. Redistributions in binary form must reproduce the above copyright

* notice, this list of conditions and the following disclaimer in the

* documentation and/or other materials provided with the distribution.

* 3. All advertising materials mentioning features or use of this software

* must display the following acknowledgement:

* "This product includes cryptographic software written by

* Eric Young (eay@cryptsoft.com)"

* The word 'cryptographic' can be left out if the rouines from the library

* being used are not cryptographic related :-).

* 4. If you include any Windows specific code (or a derivative thereof) from

* the apps directory (application code) you must include an acknowledgement:

* "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"

*

* THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND

* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE

* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE

* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL

* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS

* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT

* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY

* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF

* SUCH DAMAGE.

*

* The licence and distribution terms for any publically available version or

* derivative of this code cannot be changed. i.e. this code cannot simply be

* copied and put under another distribution licence

* [including the GNU Public Licence.]

*/

Microsoft product screen shots

Microsoft product screen shots reprinted with permission from Microsoft Corporation.

Restrictions

Information in this document is subject to change without notice and does not represent a commitment on the part of Hitachi. The software described in this manual is furnished according to a license agreement with Hitachi. The license agreement contains all of the terms and conditions governing your use of the software and documentation, including all warranty rights, limitations of liability, and disclaimers of warranty.

Material contained in this document may describe Hitachi products not available or features not available in your country.

No part of this material may be reproduced in any form or by any means without permission in writing from the publisher.

Issued

Jan. 2022: 3021-3-E16-20(E)

Copyright

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.

Colophon

Publisher

Hitachi, Ltd.

6-6, Marunouchi 1-chome, Chiyoda-ku, Tokyo, 100‒8280 Japan

Summary of amendments

The following table lists changes in this manual (3021-3-E16-20(E)) and product changes related to this manual.

Changes

Location

A procedure for auto-assigning a software name with the definition file was added.

5.2.5

Legend:

--: Not applicable

In addition to the above changes, minor editorial corrections were made.

Preface

This manual provides an overview of the functions and describes the typical uses, considerations required for configuration, the installation and setup procedures, and the usage or operation method of JP1/IT Desktop Management 2 - Asset Console (abbreviated hereafter to Asset Console).

For the latest notes, see the Release Notes.

Intended readers

The explanations in this manual assume that the readers are the following:

System administrators planning to set up an asset management system that uses Asset Console

Asset managers who will manage asset information

Organization of this manual

This manual is organized into the following chapters and appendixes:

PART 1: Introduction

1. Overview

Chapter 1 describes the purpose and features of Asset Console. This chapter also provides an overview of the information and applications that can be managed and executed by Asset Console.

2. Typical Uses

Chapter 2 describes the typical uses of Asset Console, such as how to use Asset Console in asset management jobs, and the preparation needed to use Asset Console after it has been installed.

PART 2: Design

3. Design Overview

Chapter 3 provides an overview of the work necessary for designing an asset management system that uses Asset Console. It also explains the design flow and the items that must be considered in the design process.

4. Jobs To Be Executed in an Asset Management System

Chapter 4 explains the items required when designing an asset management system and considering jobs to be executed in the asset management system.

5. Operating Method

Chapter 5 explains the items required when designing an asset management system and considering how to use the asset management system.

6. Evaluating System Configuration

Chapter 6 describes the organization of the programs for an asset management system and provides an example of a system configuration.

PART 3: Setup

7. Installation and Setup

Chapter 7 explains how to install and uninstall Asset Console. It also describes how to set up the environment for using Asset Console.

8. Achieving Asset Management by Linking to Other Products

Chapter 8 describes how to link Asset Console to other products such as JP1/IM.

9. Registration and Output of CSV Data

Chapter 9 explains how to register CSV data into the asset management database and how to output asset information from the asset management database.

PART 4: System Definition

10. Basic Knowledge Needed to Use Asset Console

Chapter 10 describes the mechanism of an asset management database and the management of asset statuses that constitute the basic knowledge needed in order to use Asset Console.

11. Changing the Window Operations and User Roles

Chapter 11 explains how to change window operations and user roles.

12. Item Definition

Chapter 12 describes how to define Items for executing asset management jobs.

PART 5: Administration

13. Basic Operating Procedure

Chapter 13 describes the basic operation and setup of the Asset Console operation windows. It also describes how to select the job menu that best suits your goals.

14. Executing Asset Management Jobs

Chapter 14 describes the details of work to be executed in each job and how to manage and control tasks through the operation windows.

15. Executing Asset Management Jobs That Use Items

Chapter 15 explains how to execute asset management jobs that use Items.

16. Managing Shared Information

Chapter 16 explains how to execute jobs that manage the shared information used for system operations.

PART 6: Troubleshooting

17. Troubleshooting

Chapter 17 describes the procedures for handling errors in an asset management system.

18. Maintaining the Asset Management Database

Chapter 18 describes how to maintain the asset management database.

PART 7: Reference

19. Details of Information That Can Be Acquired from Linked Products and Details of JP1 Events That Are Issued

Chapter 19 provides details of information that can be imported from other systems to the asset management database for use by applications. This chapter also provides in tabular format the details of JP1 events that are issued by Asset Console.

20. Management Information Details

Chapter 20 provides in tabular format the details of the properties of each class that is managed by Asset Console's asset management database. Additionally, this chapter explains in tabular format the items that are imported or exported using the Import or Export job menu.

A. Differences Between the Asset Management Functions in Asset Console and in JP1/IT Desktop Management 2 Windows

Appendix A describes the differences between the asset management functions in Asset Console and in JP1/IT Desktop Management 2 windows.

B. Organization of Folders

Appendix B describes in tabular format the organization of folders after Asset Console has been installed.

C. List of Processes

Appendix C provides a list of the Asset Console processes.

D. System Requirements and Estimates

Appendix D describes the memory, disk space, and CPU performance requirements for Asset Console.

E. Section and Key Names for Environment Setup Information

Appendix E provides a table that lists section and key names corresponding to environment settings that are needed to add processing via an access definition file.

F. Replacing the Asset Management Server and Changing Its Settings

Appendix F explains how to replace an asset management server.

G. Notes on Executing Asset Console Commands and Tasks

Appendix G provides notes on executing Asset Console commands and tasks.

H. Audit Log Output

Appendix H provides information about audit log output.

I. Applying Information Updated in Asset Console to JP1/IT Desktop Management 2 - Manager

Appendix I explains how to apply information updated in Asset Console to JP1/IT Desktop Management 2 - Manager.

J. Version Changes

Appendix J provides the details of changes in each version.

K. Reference Material for This Manual

Appendix K provides reference material for readers of this manual.

L. Glossary

Appendix L defines the terms used in this manual.

Part 1: Introduction

1 Overview

Asset Console is a product developed to help solve problems that might occur during IT asset management. Asset Console provides efficient ways to manage IT assets through the centralized management of information.

This chapter describes the purpose and features of Asset Console. It also provides an overview of the information and tasks that can be managed and executed by Asset Console.

1.1 Overview of Asset Console

This section provides an overview of Asset Console.

Asset Console is one of the components of JP1/IT Desktop Management 2. Asset Console centrally manages information about components such as hardware (including network devices), software, and contracts. This facilitates streamlining and cost reduction of IT asset management jobs, such as deploying assets, managing software licenses, and maintaining hardware.

JP1/IT Desktop Management 2 provides two asset management methods:

Using Asset Console to manage assets

Asset Console is used to manage assets and provides more advanced asset management than is available with window operation of JP1/IT Desktop Management 2. For example, the asset information search window can be customized, and asset management jobs can be executed based on Items (units of work that have defined routes).

Using JP1/IT Desktop Management 2 windows to manage assets

Asset windows of JP1/IT Desktop Management 2 - Manager are used to manage assets. This method is recommended for users who want to easily manage asset information collected by JP1/IT Desktop Management 2.

For details about the differences between the above two methods, see Appendix A. Differences Between the Asset Management Functions in Asset Console and in JP1/IT Desktop Management 2 Windows.

This manual describes only the asset management method that uses Asset Console.

Note that only one of these methods can be used. Using both methods will create inconsistencies in the asset information. During system setup of JP1/IT Desktop Management 2, you must specify whether to use Asset Console for asset management.

However, Asset Console cannot be used for asset management when you operate a large-scale environment using the large-scale management server. If the asset management method needs to be switched, the system must be set up again.

1.2 Purpose of Asset Console

This section explains the purpose of Asset Console, which can be used for the centralized management of IT asset information.

1.2.1 Resolving issues through the management of IT assets

The number of PCs and workstations owned by corporations increases every year, and the overhead of managing information about IT assets, including hardware and software assets, has become significant.

In many corporations, IT asset information is managed by various departments according to purpose. For example, device information is managed by the system management department, network information is managed by the network management department, and maintenance contract information is managed by the resources department. In addition, individual tools and databases are used for gathering and managing information, and formats vary between different management departments. Having the various departments manage IT asset information individually while maintaining a record of everything in a variety of different formats requires a large amount of overhead and costs.

Furthermore, if the improper use of licenses were to become public knowledge, adverse effects on business would be unavoidable, due to the damage to the corporation's reputation. To prevent this, it is essential that software licenses be properly managed not only to reduce costs but also to protect against copyright violations.

To address these issues concerning corporate IT asset management, there is a need for an asset management system that can handle IT assets efficiently. By using Asset Console to construct your asset management system, you can handle your corporate IT assets efficiently and solve any existing issues concerning asset management.

1.2.2 Improving the efficiency of asset management tasks and reducing management costs

An asset management system using Asset Console allows you to centrally manage collected corporate IT asset information, as well as view that information from various perspectives. More specifically, all IT asset information, including information on both hardware and software assets, as well as information on network devices and maintenance contract information, can be stored in a database and centrally managed. This improves the efficiency of asset management tasks and reduces management costs associated with stocktaking and with introducing and transferring devices.

1.2.3 Providing support for security measures

To protect IT devices against the threat of computer viruses, security measures must be systematically and exhaustively established and maintained on every device throughout the entire system. Asset Console allows you to detect devices to which the latest patches or virus definition files have not been applied. Such devices can be detected by using a variety of management information associated with the devices.

1.2.4 Allowing broad sharing of IT asset information via Web browsers

Asset Console uses a Web browser to manage IT asset information. Because no special program is required, you can manage your IT assets by logging into Asset Console from any location.

Users other than the administrator can also use the information in the database to check information about their PCs and the status of licenses for installed software programs.

1.3 Features of Asset Console

This section explains the Asset Console features developed to support solutions to a wide variety of issues that can occur in managing IT assets.

1.3.1 Linkage with JP1 products

You can assemble an integrated asset management system by linking Asset Console to such JP1 products as JP1/IT Desktop Management 2 - Manager, JP1/IM - Manager, and JP1/Service Support.

For example, you can efficiently execute asset management jobs by loading database information from a linked product into Asset Console's asset management database or by referencing information about a linked product from Asset Console operation windows.

The following figure shows the concept of the integrated operation of an asset management system linked to JP1 products.

Figure 1‒1: Concept of integrated asset management by linking to JP1 products

Registering JP1 product information in the asset management database

If Asset Console links with JP1/IT Desktop Management 2 - Manager, the CPU information, OS type, installed software, and other management information collected by JP1/IT Desktop Management 2 - Manager can be added to the asset management database.

Registering various kinds of information into a database and keeping that information up-to-date requires a large amount of time and effort. In an asset management system that uses Asset Console, a task registered in Windows Task Scheduler can be used to collect management information periodically from JP1/IT Desktop Management 2 - Manager. The database can be updated periodically with the collected information. This function can be easily deployed even in a large-scale system.

Sharing information with JP1 products

If JP1/IM is used to monitor events occurring in the system by centrally managing networks, servers, applications, and other items, you can share the information about those events. You can also check problems and response statuses from Asset Console windows. For a problem for which action has been taken, you can register the details of the action and report the completion of the action to JP1/IM - Manager.

You can also view asset information related to JP1 events by displaying Asset Console operation windows from the JP1/IM - Manager Event Console window.

Using centrally managed asset information with Asset Console

JP1/Service Support can reference the device information in Asset Console during management of service support Items.

1.3.2 Integrated management of corporate asset information

Managing corporate assets requires various types of information, such as information about devices, software programs, networks, and about maintenance and lease contracts. Defining inter-relationships among these information types allows you to effectively use this information. For example, you can perform operations such as comparing licenses installed on devices to the number of licenses owned by each group.

An asset management system based on Asset Console can achieve integrated management of the asset information needed for asset management. For any specific device or software program, asset information can be added based on a variety of approaches. Corporate assets, such as equipment and networks, can be managed comprehensively by storing asset information in an asset management database.

Additionally, you can easily handle changes to the organization because the information managed for each group can be extracted from the centrally managed asset information. A user to whom a division is assigned can also manage the asset information of other groups.

The following figure shows the concept of the integrated management of asset information using Asset Console.

Figure 1‒2: Concept of the integrated management of asset information

Asset Console can manage many types of information, in addition to those shown in Figure 1-2. Figure 1-3 shows the connection between the various types of information managed by Asset Console and asset management databases.

Figure 1‒3: Connection between asset information

Information that can be managed by Asset Console can be classified broadly into hardware asset information, software asset information, contract information, user information, and location information.

Asset information is management information created for each and every unit of hardware and unit of software. The information is designed to connect the various types of attribute information of each asset. Asset information is also used as a generic term to refer to information that can be managed by Asset Console.

The various types of interconnected information, such as network information, IP address control information, and IP group information, can also be associated and managed in the asset management database. For details about how to manage information using the asset management database, see 10.1 Asset management database.

1.3.3 Practical totaling functions and search functions designed for each type of work task

Taking advantage of centrally managed asset information for actual work requires the ability to perform certain tasks, such as totaling information, and selecting lists of required information.

Asset Console allows you to use the main totaling functions used in asset management tasks and the search functions for listing appropriate asset information in each operation window. These totaling and search functions (which are performed from operation windows) can also be classified by group or location. A user to whom a division is assigned can also search the asset information of other groups.

You can use the results of such operations to determine the status of current assets, and take appropriate action.

The following figure shows the concept of performing a search for appropriate information from an operation window.

Figure 1‒4: Concept of asset management tasks that use operation windows

For details about the configuration of the operation windows and common search and registration procedures, see 13. Basic Operating Procedure. For details about the operating procedures in each operation window, see 14. Executing Asset Management Jobs.

1.3.4 Automating database maintenance and status monitoring

Among the issues in managing a large number of assets are the issues of how to efficiently maintain the asset management database containing the information and how to monitor the status of the assets.

Asset Console allows you to use Windows Task Scheduler to maintain the asset management database containing the asset information as well as monitor asset statuses. Specified processing is executed automatically by tasks at specified dates and times. This reduces the workload on asset managers to maintain the database and monitor managed information.

The following figure shows the concept of maintaining the asset management database and monitoring operating statuses.

Figure 1‒5: Concept of using tasks to update and monitor data in the asset management database

Database maintenance:

Asset Console allows you to effectively use database capacity while maintaining the integrity of data in the asset management database by also updating information related to the information being updated by Asset Console and removing unnecessary information.

You can also register and periodically update information from linked products in the asset management databases based on information collected by JP1/IT Desktop Management 2 - Manager.

Monitoring of operating statuses:

You can periodically check for contracts whose expiration dates are getting close, and notify an asset manager by email. This informs the asset manager about contracts that are about to expire, so that they can be renewed in a timely manner.

You can also periodically total the usage statuses of software licenses, and provide an email notification if an installation exceeds the number of owned licenses or an installation using an unauthorized license is detected.

For details about setting up tasks with Task Scheduler, see 7.9 Setting the tasks that are registered in Task Scheduler.

1.3.5 Creating operation windows for routine jobs

You can improve operational efficiency by creating operation windows suitable for routine jobs that search for a specific type of information. For example, by creating an operation window, you can search by group for information that normally can be searched for only by device, or search for only the IP addresses that are currently in use.

You can use the provided GUI to easily create windows appropriate for routine jobs. Note that you can create a window that searches the asset information managed by the asset management database and displays the results as a list, but you cannot create a window that totals or registers asset information.

The following figure shows the concept of managing assets by using a window created for a routine job.

Figure 1‒6: Concept of managing assets by using a window created for a routine job

For details about creating windows, see 11.5 Adding windows for routine jobs (Create User Report).

1.3.6 Restricting and extending tasks according to user roles

User permissions can be used to restrict or extend the scope of jobs that can be performed by the user. Being able to change the functionality that is available for each set of user permissions allows you to better use the centrally managed asset information for your desired purposes.

For example, for users who will use the windows only for checking their own PC information and the statuses of the licenses for installed software programs, you can restrict the window functionality associated with updating asset information, and permit those users to only being able to perform view operations.

For the asset manager, you can extend the window functionality available so that the asset manager can register multiple contracts with a contract company or delete contract information from the Contract List window.

The following figure shows the concept of restricting and extending work tasks by using user permissions.

Figure 1‒7: Concept of restricting and extending work tasks by using user permissions

For details about restricting and extending functions of window operations, see 2.6 Limiting available functions by user roles. For details about how to perform such operations, see 11.3 Changing a window for a user role (Customize Job Windows).

1.3.7 License management of various license types

Asset Console allows you to manage various types of software licenses.

This subsection describes the typical license types and the license management methods, and the license management method used by Asset Console.

(1) License types

There are many types of licenses, but the main ones are as follows.

Installation license

This license permits installation on a single device.

User license

This license permits use by a single user. It permits installation on multiple devices that are owned by the same user.

Pre-installed

This license covers installation on a purchased device.

Server license

This is a license for server products. Server products normally have additional licenses, such as for the permitted number of times the server can be accessed (client access license), the permitted number of CPUs (CPU license), or the permitted number of manageable nodes (managed node license).

Second license

This license permits installation on a specific second device, such as a portable device. It is typically together with an installation license that permits installation on only a single device.

Concurrent execution license

This license might be necessary, depending on the number of software programs that are to be concurrently executed or reside on a device.

Volume license

This license allows you to freely purchase any number of licenses within the predefined range. The purchaser can choose the desired combination and number of licenses, but both the minimum and maximum number of points that can be used during the contract period are predetermined.

In addition to the above types of licenses, there are various options, such as whether software is upgradeable or downgradable.

(2) License management methods

The two main license management methods are total count management and per-license management. You can select the method that is best for your asset management system (or is appropriate for your software programs).

Total count management

This method manages licenses by comparing the total number of software licenses owned by the company or a group to the number of licenses in use. It eliminates the need for allocating individual licenses, thereby making management tasks comparatively easy.

However, if licenses are not used properly, it is difficult to identify a specific device or user where a license violation is occurring. Even with the same license, if permitted options depend on purchase contract terms, it is difficult to determine whether the license is being used properly by each device or user.

You cannot clearly determine which devices downgrade software licenses are being used for.

Per-license management

This method manages licenses by associating each owned license with a specific device or user. This method allows you to accurately determine the usage status according to each license's terms of purchase. It is also easy to identify devices or users that are illegally using licenses.

However, this method requires that each license be associated with a device or a user.

(3) License management via Asset Console

Asset Console provides you with the flexibility to create license information appropriate to the types of licenses you have and the management method you are already using, thereby making it possible to manage licenses on a very detailed level.

For example, you can efficiently manage licenses by using the appropriate management method for each license, such as employing total count management for licenses that are used throughout the entire company and per-license management for licenses that are individually purchased.

In addition to the volume license management method, this section describes total count management and per-license management, which are license management methods supported by Asset Console.

(a) Managing licenses based on the number of owned licenses and the number of used licenses

This is the total count management method.

This method registers the number of licenses you own when a license is purchased, obtains the number of licenses being used from the licenses installed on devices, and then compares these numbers.

The following figure shows the concept of managing licenses on the basis of the number of owned licenses and the number of used licenses.

Figure 1‒8: Concept of managing on the basis of the number of owned licenses and the number of used licenses

For an example of total count management, see 2.4.1 Checking the operation status by comparing the number of owned licenses to the number of used licenses.

(b) Managing licenses by assigning them to devices or users

This is the per-license management method.

Managing licenses by assigning them to devices

This method manages licenses that are required for each device, such as installation licenses and second licenses, by assigning them to devices.

A license's acquisition method, such as part of a package or pre-installed, can be managed as an attribute within the license information.

The following figure shows the concept of managing licenses by assigning them to devices.

Figure 1‒9: Concept of managing licenses by assigning them to devices

Managing licenses by assigning them to users

This method manages licenses as User licenses by assigning them to users who are managed by Asset Console.

The following figure shows the concept of managing licenses by assigning them to users.

Figure 1‒10: Concept of managing licenses by assigning them to users

Second and concurrent execution licenses are managed as follows:

Managing second licenses

You can manage second licenses by adding and assigning them to devices, or by managing them as User licenses without adding the licenses.

Managing concurrent execution licenses

You can manage concurrent execution licenses by registering the number of licenses that can be executed concurrently as the number of owned licenses, or you can manage the number of copies that can be executed concurrently as a license attribute.

For an example of per-license management, see 2.4.2 Accurately managing targets according to the assigned licenses.

(c) Managing downgrade software

When you use a purchased license for an older version of some software, the older version of the software is called downgrade software. For example, if you use Windows 7 with a license purchased for Windows 8, Windows 7 is downgrade software. To manage downgrade software, you must perform per-license management as described in subsection (b) above.

The following figure shows the concept of managing downgrade software by assigning licenses for each device and managing them as installation licenses.

Figure 1‒11: Concept of managing downgrade software

Managing downgrade software requires specifying a number of settings in addition to performing per-license management. For details, see 16.6.9 Adding downgrade software assets.

(d) Managing volume license points

You can manage the status of the number of accrued points by registering the volume license information and associating it with the applicable licenses.

Options for volume licenses (such as whether software is upgradeable) are managed as part of the license information for software.

The following figure shows the concept of managing volume license points.

Figure 1‒12: Concept of managing volume license points

1.3.8 Using a flow to apply for requests and approve tasks

Asset management tasks include those that require applying for and getting approval for something, as well as tasks that must be passed through an acceptance and handling process. For example, the installation of a new device requires a process for obtaining approval from a manager. Also, the details of actually arranging for and distributing the device must be dealt with by persons within the organization responsible for the overall management of the system.

With Asset Console, these types of jobs are performed by creating an Item. An Item is a job that travels along a defined route. An Item can also be thought of as the electronic form used when performing the job.

A task, such as the installation of a device or software program, proceeds through a system as it is sent and received by various parties. This process is referred to as a flow. Flows make it easier to achieve ITIL processing.

Asset management tasks that use flows have the following benefits:

By creating a single Item, you can process an application without needing to know who will handle the details, thereby making it easier to distribute required information.

Information to be used by the procedure is registered onto the server, enabling the information to be managed reliably.

Items can be managed centrally, making it easier to understand how far work related to the task has progressed.

The use of Items for applying for and approving things also allows Items to be used as draft planning instruments, since all approvals are obtained through a formal processing route.

Furthermore, Asset Console enables more efficient asset management with features, such as automatically registering information for problem resolutions as requested by an Item when a problem is resolved.

The following figure shows the concept of performing application and approval tasks by using a flow.

Figure 1‒13: Concept of performing application and approval tasks by using a flow

1.3.9 Login authentication using Active Directory services

Active Directory services can be used for authentication when logging in to Asset Console. This allows login passwords to be consolidated in Active Directory, and means that you do not have to use Asset Console to manage passwords.

2 Typical Uses

This chapter describes the typical uses of Asset Console, such as how to use Asset Console in asset management tasks and the preparation needed to use Asset Console after it has been installed.

2.1 Importing and exporting device information

With Asset Console, you can import CSV data into asset management databases, and export asset management database information in CSV format.

The following are examples of tasks that you can perform:

Importing data from another system into the asset management database.

Select output items, and perform regular backups.

This section explains how to import and export information by using device information as an example.

2.1.1 Importing data from another system into the asset management database

You can register the data migrated from other systems in a batch operation by importing the data into the asset management database. Provided you are working in a system environment that allows you to log in to Asset Console, you can import data from any location.

You can use the Import window to import data from a CSV file.

To import data, you must first create conditions and then import the data based on the conditions. Samples of import conditions are provided for each type of information. For details on the asset types used in these samples, see 16.10.2(1) Selecting the asset type.

In addition to using the Import window, you can also import data by executing jamCsvImport.bat or the jamimport command. For details about these data import methods, see 9.1.1 Import flow.

The procedure below explains how to import information managed by another system into the asset management database. In the example, the device information being managed includes machine numbers (a unique value assigned to each IT asset), names, PC statuses (Used or Unused), and MAC addresses.

Figure 2‒1: Workflow for importing information regarding devices managed by another system

Create a CSV file.

Only CSV data can be imported into the asset management database. As such, you must first create a CSV file containing the data you want to import. You can use any character strings for the item names in the CSV file. For details about the CSV file format, see 16.10.1(1) CSV file format.

The following figure shows an example of a created CSV file.

Figure 2‒2: Example of a created CSV file

Change the Used and Unused character strings under PC Status.

To unify the statuses with those already being used in Asset Console, the PC statuses Used and Unused in the CSV file must be changed to Active and Stock, respectively.

To inherit the pre-migration names, use the Code window to change the character strings used as the statuses. For details about how to use the Code window, see 16.8.2 Changing a code's display value.

Create import conditions.

To register data into the asset management database, create import conditions and assign the item names in the CSV file to the managed items. To create import conditions, first click the Pattern button in the Import window to display the Select Category dialog box. After that, select Device information in the Category column. Next, click the Browse button for the managed items to display the Setting Assignment dialog box.

When specifying the import conditions, assign information to the managed items as shown below.

Table 2‒1: Settings for assigned items when the conditions are created

Managed items

Setting for assigned items

Asset information.Asset No.

Specify Machine No. for CSV items.

Asset information.User name

Specify Name for CSV items.

Asset information.Usage management

Specify Used for Constant value.

Asset information.Status

Specify PC Status for CSV items.

Select the Assigned items check box, and select Active.

Asset information.Reg. date

Specify 2006/01/01 for Constant value.

Hardware information.MAC address

Specify MAC Address for CSV items.

Note the following when specifying the import conditions:

A star () indicates an item that must be specified.

If each asset is assigned a unique value as its asset number, the value that was used to manage the asset in another system can then be used as the asset number in Asset Console. If you do not register any values, asset numbers are provided automatically.

When you import MAC addresses, the management information collected from JP1/IT Desktop Management 2 - Manager is assigned as the information of the imported devices.

For details about how to create import conditions, see 16.10.2 Creating import conditions.

After you save the conditions, click the Back button to return to the previous window.

Import the data.

In the Import window, specify the created conditions, and import the data. For details about how to import data, see 16.10.3 Executing imports.

Check the import results.

In the Result Import window, check the results of the import operation. For details about how to check the import results, see 16.12 Checking the import results (Result Import).

Manage the devices.

By using the Device Totals window, you can calculate the total number of devices you own, change device information from the Batch Update window, and perform other device management operations.

Repeat steps 1 to 4 of the import procedure until you have imported all of the information.

2.1.2 Limiting the items to be exported for regular backups

By creating conditions in advance to filter the items to be exported, you can export only the information that you want to output. By using the conditions you created, you can also easily limit the items to be exported when you back up the asset management database.

The Export window is used to export the data to be backed up.

To export data, first create conditions, and then export the data based on those conditions. Samples of export conditions are provided for each type of information. You can use these samples to export all items. For details on the asset types used in these samples, see 16.10.2(1) Selecting the asset type.

In addition to using the Export window, you can also export data by executing jamCsvExport.bat or the jamexport command. For details about the differences among these export methods, see 5.2.2 Collecting from CSV files.

The procedure explains how to export device information in CSV format.

Create export conditions.

Begin by creating export conditions for backing up data. To create export conditions, first click the Pattern button in the Export window to display the Select Category dialog box. After that, select Device information in the Category column. Next, specify the items to be exported to the CSV file.

When creating the export conditions, specify the following export items:

Asset No. (Asset information)

User name (Asset information)

Status (Asset information)

MAC address (Hardware information)

For details about how to create export conditions, see 16.11.1 Creating export conditions.

Save the conditions, and then click the Back button to return to the previous window.

Export the data.

In the Export window, specify the conditions created in step 1 and export the data. If you want to export only information from managed groups or otherwise filter the data being exported, click the Filter link to display the Set Condition dialog box, where you can filter the number of items. For details about how to export data, see 16.11.2 Executing an export operation.

Specify a file name, and then save the data.

We recommend that you specify a file name that makes it easy to determine the date the file was exported and the contents of the file (for example, 060701_device-info.csv).

Check the exported data.

Check the data to make sure the export executed normally.

To make use of the export functionality when you make regular data backups, repeat steps 2 to 4 using the export conditions created in step 1.

2.2 Managing the usage statuses of IP addresses

The usage statuses of IP addresses are managed by associating them with groups. By separating the IP addresses into IP address ranges and managing them in group-specific IP groups, the group associated with the IP address of any particular device can be set automatically, even if JP1/IT Desktop Management 2 - Manager does not collect the group information as user information. This allows you to manage the usage statuses of IP addresses by group.

The usage statuses of IP addresses are managed in the IP Group window.

The figure below shows the workflow for managing the usage statuses of IP addresses by group, by registering the group associated with the IP addresses that are assigned to devices owned by the group. This example assumes that JP1/IT Desktop Management 2 - Manager does not collect group information as user information.

Figure 2‒3: Workflow for associating a group with IP addresses, and managing the IP group

Set up automatic registration for the group to be associated with the IP addresses.

To configure the system so that, when the IP address of a device changes, the group that includes the changed IP address is set automatically, specify Set for Settings for a group that uses a group-specific IP group in the Server Setup dialog box. For details about how to set values in the Server Setup dialog box, see 7.3.4 Setting Basic Information.

Note

You can also have the group corresponding to the IP address be recorded automatically during a task scheduler data maintenance task. Even when group information is being collected from the JP1/IT Desktop Management 2 - Manager management information, by executing this task, you can update the group to match the values set with the IP Group job menu.

Add an IP group.

Add the IP group you want to manage using the Group-Specific IP Group tab in the IP Group window. For details about how to add an IP group, see 16.4.1 Adding an IP group.

Register management information to the asset management database.

You can register the desired device information using the management information collected by JP1/IT Desktop Management 2 - Manager. For details about how to register management information, see 7.1.1 Workflow necessary for acquiring JP1/IT Desktop Management 2 - Manager management information.

View the IP address usage status.

In the IP Address Management dialog box, you can view information about devices to which IP addresses are assigned and check for unused IP addresses. You can also display the Device Details dialog box by clicking the Asset No. link. For details about how to view IP address usage status, see 16.4.2 Viewing IP address usage.

When a new device is installed, you can check the IP group of the distribution destination group, and instruct the person responsible to assign an available IP address to the device. If more than one device is assigned to a single IP address, you can release the IP address of the invalidly assigned device, and assign a different IP address to that device. For details about how to release an IP address assigned to a device, see 16.4.4 Releasing the IP addresses assigned to devices. For details about how to assign an IP address to a device, see 16.4.3 Assigning IP addresses to devices.

2.3 Stocktaking

You can search for devices for which stocktaking has not been completed by registering information about the devices for which stocktaking has been completed and the stocktaking date. This reduces the complexity of stocktaking jobs because you can check job progress and prevent items from being overlooked. If it exists, you can also use actual stocktaking data obtained using a device such as a bar-code reader to register such devices.

To search for devices for which stocktaking has not been completed, use the Totals of Stocktaking-Unexecuted Devices window. The number of devices for which stocktaking has not yet been completed from the stocktaking start date can be confirmed in the Totals of Stocktaking-Unexecuted Devices window.

You can easily register the actual stocktaking data into the asset management database by reading it with a bar-code reader or saving existing data in a ledger in CSV format.

The following figure shows by way of example the procedure for a stocktaking job when a bar-code reader is used.

Figure 2‒4: Procedure for stocktaking job

Use a bar-code reader to read the asset number of each device.

Create a CSV file from the obtained data.

To manage the allocation of asset numbers for each device, specify the asset number and the stocktaking date in the CSV file that contains the actual stocktaking data. You can omit the stocktaking date, but make sure that the asset number is specified.

For details about the format of the CSV file for actual stocktaking data, see 14.1.7 Registering actual stocktaking data (Confirm Stocktaking Device).

Register the CSV file containing the actual stocktaking data into the asset management database.

You can register the actual stocktaking data by specifying its file from a window. For details about registering the actual stocktaking data, see 14.1.7 Registering actual stocktaking data (Confirm Stocktaking Device).

In the Totals of Stocktaking-Unexecuted Devices window, search for devices for which stocktaking has not been performed.

Specify Stocktaking start date and Totals by to search for the devices for which stocktaking has not been performed. For Totals by, you can select Group name or Location.

For details about using the Totals of Stocktaking-Unexecuted Devices window, see 14.1.6 Checking the number of devices that require stocktaking (Totals of Stocktaking-Unexecuted Devices).

Instruct the user in charge of stocktaking to inventory the devices that were not counted.

The search results for missing devices is useful for issuing instructions because it is provided for each group or location, making it easy to identify groups or locations that have not been included in stocktaking.

You can also use the search results to view details about each device's users and group. You can also output the search results to a CSV file.

Repeat steps 1 to 5 of the stocktaking job until stocktaking is completed for all devices.

2.4 Determining whether licenses are handled legally

You can determine whether licenses are being handled legally by totaling usage in terms of whether the numbers of licenses being used have exceeded permitted values and whether licenses are being used by the correct users.

There are two ways to manage licenses. One is called total count management, and it is based on comparing the number of licenses held (called owned licenses) with the number of licenses actually in use. The other is called per-license management, and it assigns each license individually.

This section describes the job for managing licenses with each method.

2.4.1 Checking the operation status by comparing the number of owned licenses to the number of used licenses

You can perform basic license management, such as determining use of an excess number of licenses and use of unauthorized licenses, by managing the license totals based on information about the installed licenses on all devices.

To manage licenses, start from the job menus under Software License.

In the Owned License List window (opened by clicking the Owned License List job menu), you can obtain the license usage status at a glance, because this window displays a table comparing the number of owned licenses, the number of licenses being used, and the number of available licenses.

You can use this comparison table to purchase licenses when no more are available or to search for groups with too many licenses for transfer to groups with too few licenses.

You can use the following job menus to identify inappropriate license usage:

Excess License List

Allows you to check if any licenses are being used that exceed the number that has been set for owned licenses.

Unauthorized Usage List

Allows you to check if any expired licenses are being used, or whether licenses that have not been obtained are being used.

Unknown Usage List

Allows you to check if software programs with unregistered software names are being used.

Tip

You can set up the system to notify the asset manager by email if an excess license is detected. This means you can prevent excess licenses from being overlooked, thereby reducing the asset manager's workload. Events that trigger asset manager email notification can be monitored by registering a task to the Windows Task Scheduler to check for excess licenses. For details about how to set tasks, see 7.9 Setting the tasks that are registered in Task Scheduler.

The following figure shows the procedure for checking license status.

Figure 2‒5: Procedure for checking license status

Register management information into the asset management database.

To check license usage status, you need two types of information:

Information about devices

Information about the software programs installed on the devices

You can use the management information acquired by JP1/IT Desktop Management 2 - Manager to register information about devices and about software programs installed on the devices. For details about registering management information, see 7.1.1 Workflow necessary for acquiring JP1/IT Desktop Management 2 - Manager management information.

To efficiently manage licenses, we recommend that you configure the system to automatically assign the installed software name to a software name when you collect management information. For details about how to automatically assign the installed software name to a software name, see 5.2.4 Setting the software name assignment method. If the assignments are not performed automatically, you must use the Software Name job menu to assign names one at a time.

Register purchased license information.

In this step, register the purchased license. For details about how to register licenses, see 14.4.5 Adding a license (New Software).

In Task Scheduler, enable the Notice of license excess task.

The task totals the license usage statuses and reports excess licenses.

The task registered in Task Scheduler is executed at the specified date and time and totals the licenses. If any software exceeds a usage threshold (the default threshold is 100%), the task sends an email to the asset manager reporting that excess licenses are in use.

You can also total the licenses from the window that is displayed by selecting Totals List & Execution from the job menu. For details about how to total licenses using window operations, see 14.4.10 Totaling licenses (Totals List & Execution).

Check license usage status.

In the window that is displayed by selecting Excess License List from the job menu, check for licenses that have been installed in excess of the number owned.

You can also download the totals using a CSV file. For details about checking the excess licenses, see 14.4.2 Checking for exceeded licenses (Excess License List).

2.4.2 Accurately managing targets according to the assigned licenses

You can accurately manage license usage status by creating license information according to license types and options and assigning licenses to specific targets.

The figure below shows the procedure for managing licenses by assigning them. This procedure is an alternative to the procedure for total count management described in 2.4.1 Checking the operation status by comparing the number of owned licenses to the number of used licenses.

Figure 2‒6: Procedure for managing licenses by assignment

Create and register license information when you purchase licenses.

Create the license information according to the license type and option settings.

For example, for an Install license, register information such as upgrade assurance and compatibility with downgrade software. For details about how to register license information, see 14.4.5 Adding a license (New Software).

Assign the licenses to the targets.

Assign the licenses to devices or users according to the license category.

To assign a license, establish correspondence between the key information such as product ID and the targets. For details about assigning licenses, see 14.4.6(2) Assigning licenses.

Execute the same steps as for total count management.

Install the software program on the devices to which licenses have been assigned and then execute the steps common to total count management (register management information, establish correspondence between software names, set up the task, and total the licenses).

Check to see if the licenses are handled correctly.

Under Software License, you can use the following job menus to check the registered license information:

Owned License List

This menu lets you check the total for each license category.

Excess License List

This menu lets you check for any licenses being used that exceed the threshold set by the license category for owned licenses. If illegal use of a license is detected, you can identify the user or device immediately.

To accurately manage licenses, it is important to create license information according to the license type and options and select an assignment method that is appropriate for your operating procedures. Also, all types of information that can be managed as license information must have been prepared, and the total number owned is executed on the basis of the license category.

The following presents examples of license management that are suggested for license management using Asset Console:

(1) Example of managing Install licenses

You can manage licenses assigned to devices as follows:

Create license information as Install license.

To assign a license to a device, specify Install license for License category. Also specify other settings appropriate to the license, such as downgrade and upgrade assurance.

Register the key information, such as the product ID of the purchased licenses, and assign one license to each device.

This allows you to check whether use of the license is permitted for any particular device.

(2) Example of managing User licenses

You can manage licenses assigned to users as follows:

Create license information as User license.

To assign a license to a user, specify User license for License category. Also specify other settings appropriate to the license, such as downgrade and upgrade assurance.

Register the key information, such as the product ID of the purchased license, and assign one license to each user.

This allows you to total licenses correctly, even when the same user uses a license on multiple devices.

To manage a license by assigning it to a user, the user must be registered in the applicable device. Additionally, this user must also be registered as an Asset Console user.

(3) Example of managing pre-installed licenses

You can manage pre-installed software licenses as follows:

Create license information as Install license.

Specify Install license for License category. Use Licensing method to specify that this is a pre-installed license.

Disable the Downgrade property because normal pre-installed software programs are not downgradable.

This enables you to determine whether the correct version has been installed.

For the number of owned licenses, specify unlimited licenses.

You can register a license by owning a single license per device; however, by specifying unlimited licenses, you can manage software programs more efficiently because any additional pre-installed licenses for the same software program can be assigned later, simply by adding its key information.

Assign a license to a single device by registering the key information such as product ID.

As a result, you can determine whether the pre-installed software program is being used on the assigned device.

(4) Example of managing server licenses

You can manage the license of a server product as follows:

Create license information as Install license.

To assign a license to a device, specify Install license for License category. Also specify other settings appropriate to the license, such as downgrade and upgrade assurance.

A server license is accompanied by other licenses, such as Client access, Managed node, and CPU licenses. The following describes a management example for each license:

Client access license

This license is given according to the number of administrators' computers (or the number of users) that access the server. Select one of the following management methods:

Managing accessible administrators' computers as the number of owned licenses

Register a single license separately from the server license and create client access license information. For example, register a client license with 100 accesses permitted as a software asset with 100 licenses owned. For License type, specify Client access license.

This allows you to total the number of accesses permitted as the number of owned licenses.

Note that information such as the number of used licenses is not totaled because there is no device-related information.

Managing as the additional information for the server license

As a simple method, register the number of accesses as remarks without registering the client access license as a license. You need to calculate the number of owned licenses manually.

Managed node license

This license is given according to the number of administrators' computers managed by the server. Select one of the following management methods:

Managing the number of administrators' computers managed by the server as the number of owned licenses

Register a single license separately from the server license and create managed node license information. For example, register a managed node license that permits 100 managed nodes as 100 owned licenses. For License type, specify Managed node license.

This allows you to total the number of managed nodes permitted as the number of owned licenses.

Note that information such as the number of used licenses is not totaled because there is no device-related information.

Managing as the additional information for the server license

As a simple method, register the number of managed nodes as additional information associated with the server license, without registering the managed node license as a license. In this case, you need to calculate the number of owned licenses manually.

CPU license

This license is given according to the number of CPUs. Create license information as CPU license, not as server license.

(5) Example of managing second licenses

This subsection presents an example of managing licenses when installation on a second device is permitted. Select one of the following management methods:

Managing as User license

Create license information as User license (specify User license for License category).

The license is managed assuming that installation on a second device that is used by the same user is permitted. However, the system cannot detect exceeded licenses even if the applicable software program is installed on more than two devices.

Managing the license by adding second license information

Register a license separately from the server license and create second license information. In this case, remarks about its correspondence with the original license would be useful.

(6) Example of managing concurrent execution licenses

This subsection presents an example of managing concurrent execution licenses. Select one of the following managing methods:

Managing the number of concurrently executable licenses as the number of owned licenses

Register a single license separately from the server license, and create concurrent execution license information.

For example, register a concurrent execution license that permits 100 concurrent executions as 100 owned licenses. For License type, specify Concurrent execution license.

This allows you to total the number of concurrent executions permitted by the license as the number of owned licenses.

Note that information such as the number of used licenses is not totaled because there is no device-related information.

Managing as the additional information for the server license

As a simple method, register the number of executions as additional information associated with the server license without registering the concurrent execution license as a license. In this case, you need to calculate the number of owned licenses manually.

Managing by assigning to devices

Register the license using the permitted number of concurrent executions as the number of owned licenses.

Create the license information as concurrent execution license, not as server license.

Register the key information, such as the product ID of the purchased licenses, and assign one license to each device.

You can limit the number of concurrent executions by permitting as many installations as there are permitted concurrent executions.

2.5 Adding asset information statuses, managed items, and windows

You might want to perform more in-depth management of device and contract status or to use more management items than available with standard window operations of Asset Console, by customizing the system environment, according to the job. In this case, you can easily use window operations to add statuses and managed items.

You can also create a window for searching your assets on the basis of the added statuses or managed items as key values and then add asset management jobs that can be executed from Asset Console.

For example, you can add a job that groups devices by installation period and then manages the distribution status of the devices in groups. To do this, the following preparations are needed:

Adding the status Waiting for distribution indicating that distribution has not been made to the device.

Adding the managed item Group to manage the devices installed in the same period as a group.

Adding a window for searching for devices by group to which distribution has not been made since installation

You can easily do all this from the windows that are displayed by selecting the job menus under the System Management and System Definition job categories.

The following figure shows the procedure for preparing and executing the job for checking the distribution status.

Figure 2‒7: Procedure for checking the distribution status of devices by group

In the Code window, add the status.

Add the status Waiting for distribution indicating that the device has not been distributed to a group after installation.

The status is associated with the code and managed by the asset management database. Therefore, to add the status Waiting for distribution to devices, add the corresponding code to Status.

For details about the operation in the Code window, see 16.8 Adding and changing types and statuses (Code).

In the Customize Managed Items window, add a managed item.

To manage the devices installed in the same period as a group, add Group to the managed items of Asset information.

The added managed item takes effect in the entire asset management system. For details about the operation in the Customize Managed Items window, see 11.2 Changing managed items (Customize Managed Items).

In the Create User Report window, add a window.

Add a window for checking for any device that was installed in the same period, but has not been distributed. In the window, search for devices using Group as the condition and list only those devices whose status is Waiting for distribution as the result.

You can display the added window from the menu that is added to the job menu. You can also change the window's view setting (view or hide) from the Customize Job Menu window.

For details about the operation in the Create User Report window, see 11.5 Adding windows for routine jobs (Create User Report). For details about the operation in the Customize Job Menu window, see 11.4 Changing the executable jobs (Customize Job Menu).

In the New Device window, register new devices.

Register newly installed devices. When registering the devices, specify Waiting for distribution as Status. To manage the devices installed in the same period as one group, register the same number in Group. If the device installation date is included in the number, device management by group is facilitated.

For details about the operation in the New Device window, see 14.1.4 Registering device information (New Device).

Distribute the newly installed devices to groups.

After distributing the devices, the system administrator must use the Batch Update window to change the status of the distributed devices from Waiting for distribution to Active.

For details about the operation in the Batch Update window, see 14.1.5 Changing device information (Batch Update).

Use the added window to search for any devices that have not been distributed.

By executing a search with Group specified as the search condition, you can display a list of devices in the specified group that have not been distributed. You can then distribute those devices on the basis of this list.

2.6 Limiting available functions by user roles

Asset Console's asset management system enables corporate assets information to be widely shared among users, from general users to the staff in charge of the asset management jobs. However, the asset management system might contain some information that should not be shared or manipulated by general users.

If the usage of Asset Console depends on the nature of user jobs, available information and functions can be limited by means of user roles.

For example, you can set the following limitations for general users:

Prohibit updating of information about software programs installed on devices.

Prohibit execution of Transfer License jobs.

This section describes the procedures executed by the asset manager to set limitations on the operations available to general users.

2.6.1 Prohibiting updating of information about software programs installed on devices

To strictly control the installation of unauthorized software, set up the system in such a manner that no user other than an administrator can update information about installed software. To limit the functions of a specific window, use the Customize Job Windows window.

This window lists all Asset Console windows by job. Clicking the link for a desired window displays the window for changing the settings for that window (Customize Job Windows - Edit Form). The window settings are called a form.

The following figure shows the procedure for limiting the functions of a specific window.

Figure 2‒8: Procedure for limiting the functions of a window for a user role

In the Customize Job Windows - Edit Form window for the Software tab of the Device Details dialog box, specify the form settings.

In the Customize Job Windows window, from the list of window names, select Device, and then Software. Then, in the Customize Job Windows - Edit Form window that is displayed, specify the following settings:

Target role: Set User.

Buttons: Hide the Add and Delete buttons.

For details about the operation in the Customize Job Windows window, see 11.3 Changing a window for a user role (Customize Job Windows).

In the Customize Job Windows - Edit Form window for the Installed Software Details dialog box, specify the form settings.

In the Customize Job Windows window, from the list of window names, select Device, Software, and then Installed Software Details. Click the link to display the Customize Job Windows - Edit Form window, and then specify the following settings:

Target role: Set User.

Buttons: Hide the Update button.

Editable items: Set Read-only for all items.

Log in to Asset Console, and execute a job.

For a general user, the displayed Software tab of the Device Details dialog box and the Installed Software Details dialog box allow only information referencing.

Note that steps 1 and 2 can be reversed.

2.6.2 Prohibiting execution of a Transfer License job

If the asset manager is to use a batch operation to transfer licenses, you must hide the job menu itself from general users. To hide a specific job menu, use the Customize Job Menu window.

In the tab for each user role, specify the view setting (show or hide) for a job menu.

The following figure shows the procedure for hiding a specific job menu.

Figure 2‒9: Procedure for hiding a job menu according to the user role

In the Customize Job Menu window, change the job assignment.

Select the Customize Job Menu job menu, and then, in the displayed window, remove Transfer License from the jobs that are available to general users.

For details about the operation in the Customize Job Menu window, see 11.4 Changing the executable jobs (Customize Job Menu).

Log in to Asset Console, and execute a job.

For a general user, the Transfer License job menu is no longer displayed.

2.7 Solving problems using Items

If any type of problem occurs in a device used by the system, it is necessary in order to solve the problem to distribute information about the problem to pre-designated individuals within the organization who are responsible for receiving and solving problems.

Normally, problem information is conveyed in a document or by email, but this makes it difficult to keep track of the processing progress. By using Items, an overview of the problem can be easily determined and the processing status can be tracked.

Items are selected and created from the New Item window. In the New Item window, the Items that can be used are displayed by tab according to category.

Asset Console provides a Problem Report Form as a sample Item. Using this sample Item, the figure below is an overview of the actions required to handle an asset problem. The steps involve requesting help from concerned personnel, discovering the problem, implementing a solution, and completing the task.

Figure 2‒10: Overview of handling an asset problem using a sample Item

Define the job flow.

When a problem occurs, define the types of information, the path over which that information will be routed, and whether to perform troubleshooting. If you use the sample Item provided without any change, you can skip this step.

Use the Item Definition window to define a workflow that uses an Item. For details about how to define an Item, see 12.1 Overview of Item definition.

Use the Official Authority window to assign authorities to the users who will handle the Item.

In the Problem Report Form Item, problem receivers and problem solvers have been defined as official authorities (authorities required to process the Item).

Because all necessary authorities are already defined in the sample Item, simply assign the authorities to users who have sufficient permissions to perform the processing involved. For details about how to define users with authorities, see 12.2 Defining authority for processing the Item (Official Authority).

Exhibit the Problem Report Form Item.

Because the status of the sample Item is registered as Creating, the status must be changed to Exhibit. For details about how to exhibit Items, see 12.7.2 Setting an Item to Exhibit or Not exhibit.

Note

In the New Item window, Items are displayed in tabs on the basis of the Item category. Initially, the Template tab is provided. Depending on the type or the contents of the work, change the name of this tab or add new tabs. For details about how to add or change Item categories, see 16.8.1 Adding codes.

To display the Item in the Item category that was added, change the Item category before you exhibit the Item. For details about how to change Item categories, see 12.3.2 Placing workers and processing.

Create a Problem Report Form and request a problem resolution.

From the New Item window, create a Problem Report Form Item and submit an application. The sent Item is placed in the next worker's inbox.

The person responsible for receiving the problem opens the Problem Report Form in the inbox, checks the overview of the application, and requests a solution from the person responsible for solving the problem.

For details about how to create Items and how to process received Items, see 15. Executing Asset Management Jobs That Use Items.

Confirm the overview of the problem resolution.

After having solved the problem, the problem solver records the fact that the problem has been solved in the Problem Report Form, and then sends the form back to the applicant. To complete the Item, the applicant confirms that the problem has been solved.

Changing the contents of an Item definition

The sample Item provided by Asset Console is a model case of an asset management job. Change the settings, based on this sample, depending on the details of the actual asset management job.

For details about how to confirm and change the contents of an Item definition, see 12.1 Overview of Item definition.

The following figure shows the Item definition elements required during consideration of jobs that use Items.

Figure 2‒11: Item definition elements

Item route

This defines the workers who are responsible, from the applicant and the problem reception desk until the Item is completed. The department and the personnel who execute the series of work, and the contents of that work, until completion of an Item are known as the node.

For details about how to define the route, see 12.3 Defining the route (Flow Designer).

Worker role

The management node problem reception desk and problem resolution desk are defined so that Items are sent to workers with authority to execute the processing. The authority required to process Items is called official authority. For details about how to define official authority, see 12.2 Defining authority for processing the Item (Official Authority).

Window components processed by each worker

Each worker defines the items to be specified and the buttons for execution in the windows. Such worker-processed windows are called Item window.

For details about how to define the Item window, see 12.4 Defining the Item window (Form Designer).

Processing that accompanies Item execution

This defines the processing to be executed once the solution has been implemented, when the overview of the problem and the overview of the solution are registered and the Item is sent to the next worker. Such processing that accompanies execution is called an activity.

For details about how to define this processing, see 12.5 Defining each node's task (Activity Designer).

Setting whether to send email and processing time limits

You can set options for an Item, such as whether the worker is to be notified by email when the Item arrives at the next worker, or to specify a processing time limit. These send-time options for Items are called Item options.

For details about how to define Item options, see 12.6 Setting the Item options (Flow Designer).

2.8 Login authentication via linkage with Active Directory

Active Directory services can be used for authentication when logging in to Asset Console. This allows login passwords to be consolidated in Active Directory, and means that you do not have to manage passwords separately for each system you are using.

Note

Only passwords can be consolidated when Active Directory is used for login authentication. Asset Console user information must be used to manage user group information.

The following figure shows the workflow for user authentication via linkage with Active Directory.

Figure 2‒12: Workflow for user authentication via linkage with Active Directory

Obtain configuration information and attribute names from the Active Directory server.

The information required to configure linkage with Active Directory must be obtained in advance. For details about how to obtain this information, see 5.5.1 Login authentication.

Specify the settings to link with Active Directory.

In order to link to Active Directory, you must configure the settings under Link with Directory Server in the Server Setup dialog box. For details about the settings required to link with Active Directory, see 7.3.6 Setting Link with Directory Server.

2.9 Importing Active Directory information into the asset management database

User information managed by Active Directory services can be imported into the asset management database.

You must create and periodically execute an Asset Console script in order to update the asset management database (user management information) with the user information that is managed by Active Directory services. Asset Console provides a sample script that can be used as a reference for creating your own script. The sample script updates the following items:

Role names

Email addresses

Phone numbers

For details about how to update the asset management database via linkage with Active Directory, see 5.5.2 Acquiring user organization information.

Part 2: Design

3 Design Overview

This chapter explains the design flow and the items that must be considered in the design process. It provides an overview of the work necessary for designing an asset management system that uses Asset Console.

3.1 Design flow

The figure below shows the flow of designing an asset management system that uses Asset Console.

Figure 3‒1: Design flow

Decide which jobs (work) to handle using Asset Console.

Investigate and decide what is to be managed and the types of information to be managed according to the work. Additionally, decide whether executing the target jobs requires linkage with other program products.

Investigate and decide how the asset management system is to be operated.

Investigate and decide how the daily operations will be carried out, including the access permissions, the asset information acquisition method, and the need for email notification.

Investigate and decide the system configuration.

Based on the decisions reached in steps 1 and 2, determine the programs needed and their positioning in the system.

3.2 List of items to consider

This section provides an overview, and explains the items that you need to consider when designing an asset management system that uses Asset Console. Use this section to get a general understanding of the items to be investigated and decided in the design phase. If you find an item you might need, consult the section indicated inside the parentheses, and decide whether to use that item.

3.2.1  Evaluating the management target

Investigate and decide the management targets (what is to be managed) and what information about each management target is to be managed. The parentheses following each list item indicate the section that provides a detailed explanation.

For managing devices:

Types of devices such as PCs, displays, printers, and hubs (subsection 4.1.1(1))

Information to be managed that is related to devices, such as group names, contracts, and problems (subsection 4.1.1(2))

For managing software:

Software types such as shareware and freeware (subsection 4.1.2(1))

Information to be managed that is related to software, such as the number of licenses being used and detailed licensing modes (subsection 4.1.2(2))

3.2.2 Evaluating operation methods

Investigate and decide how to operate the asset management system. The parentheses following each list item indicate the section that provides a detailed explanation.

For setting up access permissions:

Types of user roles (subsection 5.1.1)

Types of access permissions, such as login restrictions, hierarchical restrictions, and restrictions on the menus that can be used (subsection 5.1.2)

For selecting the method of acquiring asset information:

Collecting from JP1/IT Desktop Management 2 - Manager (subsection 5.2.1)

Collecting from a CSV file (subsection 5.2.2)

For using notification by email

Types of information to be sent via email, such as contracts nearing expiration and the number of licenses exceeded (section 5.3)

For outputting the search results to a PDF file

Whether the search result needs to be output to a form (subsection 4.2.2)

For introducing into a cluster system

Whether a cluster configuration is available that allows the introduction of Asset Console (section 5.4)

3.2.3 Evaluating the system configuration

Select the programs to use and consider potential system configurations. The parentheses following each list item indicate the section that provides detailed explanation.

Prerequisite programs for the asset management server

Required

Types of OS to use, such as Windows Server 2012, Windows Server 2008, and Windows Server 2003 (subsection 6.1.1(1))

Version of the Web server to use (Microsoft Internet Information Services) (subsection 6.1.1(1))

Optional

Whether to send notification by email (subsection 6.1.1(3))

Whether to use Active Directory to authenticate a user (subsection 6.1.1(5))

Prerequisite programs for the administrator's computer

Required Web browser (subsection 6.1.1(2))

Asset Console components

Positioning of the asset management server (subsection 6.2.1)

Linkage to other program products

Types of program products that can be linked (subsection 6.1.1, subsection 6.1.2)

4  Jobs To Be Executed in an Asset Management System

This chapter explains the method of selecting the jobs to be executed, when designing an asset management system.

4.1 Management targets

When designing an asset management system that uses Asset Console, first investigate and decide what is to be managed (the management targets). Asset Console can manage devices and software programs.

This section explains the information that can be managed for each management target.

Information about the management targets

You can acquire the main information about a management target by linking Asset Console to JP1/IT Desktop Management 2 - Manager.

To import the information collected by JP1/IT Desktop Management 2 - Manager for utilization in an asset management database, select the targets to be managed by the asset management database. This must be done based on the information collected by JP1/IT Desktop Management 2 - Manager. For details about the information that can be acquired from JP1/IT Desktop Management 2 - Manager, see 19.1 Management information that can be acquired from JP1/IT Desktop Management 2 - Manager.

To register information not collected by JP1/IT Desktop Management 2 - Manager or information unrelated to JP1/IT Desktop Management 2 - Manager in the asset management database, and to manage such information, use either of the following methods:

- Register information about individual devices and software programs.

- Acquire information from a CSV file and import the information.

For details about how to register new information about devices and software programs, see 14.1.4 Registering device information (New Device) and 14.4.5 Adding a license (New Software).

For details about acquiring asset information, see 5.2 Collecting asset information.

4.1.1 Managing devices

Asset Console can centrally manage the devices on a network. This section explains the types of devices that can be managed, and the types of information that can be managed in connection with these devices.

Device types and related information can be used as the attribute information of the devices, for stocktaking. Additionally, when managed along with contract information, device types and related information can be used in various types of work, such as troubleshooting. Therefore, investigate and decide what level of management and what information are required.

The following figure shows the concept of utilizing the device information in various types of work. In this example, the attribute information of the devices is used in contract and problem management.

Figure 4‒1: Using device information in various types of work

(1) Device types

Device types can be classified into the following three categories: computing, accessories, and networking, each of which can be further classified into detailed categories. The default device types are listed in the table below.

Device type

Detailed category

Computing

PC

PC server

UNIX

UNIX server

Smart Devices

Other system devices

Accessories

Monitor

Hard disk

CD-R

CD-R/W

DVD

DAT

MO

Printer

Peripheral Devices

USB Devices

Other storage devices

Networking

HUB

Router

Network printer

Network devices

By precisely managing device types, you can retrieve the desired device information quickly from a device management job, and can also simplify contract and license management. Furthermore, if management history information is used for preventive maintenance, precise management of device types makes thorough security measure implementation possible.

You can use device type information to delete unnecessary types from the management targets or to add necessary types. For details about how to change the default types, see 16.8 Adding and changing types and statuses (Code).

(2) Information associated with devices

Asset Console can efficiently manage devices by associating information such as group names and location names with devices and managing such information. The following types of information can be associated with devices and managed:

Group name, user, and location name

You can manage the names of groups that use a device, the device users, and device locations. Group names, users, and location names can be used in all device management jobs, including stocktaking of devices and quick troubleshooting.

Not only can you use window operations to register the group names, users, and location information, but you can also acquire this information from JP1/IT Desktop Management 2 - Manager. Furthermore, you can automatically set the corresponding group and location names from IP addresses.

Contract information

You can use contract information to manage device maintenance as well as lease and rental contract details. By registering the contract information, you can manage it in association with the devices covered by the contract.

Problems

When an error occurs in a device, you can register the error details as problems and manage them. You can use this information to devise countermeasures against the same kind of problem, or use it in device purchasing or replacement jobs.

You can also register JP1 events of JP1/IM and share the problems on the asset management system. For details about linkage to JP1/IM, see 4.2.1 Managing problems by linking to JP1/IM.

Network information

You can manage a network configuration by associating it with network information such as IP addresses, subnet masks, and default gateways.

Related devices

You can manage devices by establishing parent-child relationships among them. By searching for devices that are related and registering them as related devices, you can easily keep track of the devices that are related to the device of interest.

4.1.2 Managing software

Asset Console can manage the software installed in devices and the licenses owned. This section explains the types of software that can be managed, and software-related information. Information about the software installed in the devices can be used in various jobs, such as checking the number of licenses being used, thoroughly implementing anti-virus measures, and preventing illegal use. You can also manage assignment destinations according to license categories. Therefore, consider the extent of the information to be managed and, based on this consideration, determine the information that is required.

The following figure shows the concept of utilizing the information about the software installed in devices in various jobs. In this example, software information is used to manage the usage of software.

Figure 4‒2: Using software information in various jobs

(1) Software types

Software types can be classified into the following three categories: commercial, shareware, and freeware. You can delete unneeded types from the managed target, and add required types. For details about how to change the default types, see 16.8 Adding and changing types and statuses (Code).

(2) Information to be managed

Two types of software information can be managed. One type is the information related to purchased licenses. The other type is the information related to software that is installed on devices. By combining these two types of software information, you can compare the number of licensed users allowed with the actual number of users, or detect illegal installation. The following types of software-related information can be managed.

License-related information

Number of licensed users

You can use this information to manage the number of users licensed to use the software.

License information

You can centrally manage detailed option information, including license categories (machine-specific or user-specific), downgrade, and upgrade assurance.

License keys and assignment destinations

By comparing the license keys with license assignment destinations, you can determine which devices (or users) are using which licenses.

Information related to the software installed in devices

Number of licenses being used

You can use this information to manage the names and versions of software installed in devices, and file names.

Patch information

You can acquire JP1/IT Desktop Management 2 - Manager system information and manage information about patches that have been installed in the devices. You can use this information to determine whether the latest patches have been applied.

Virus definition information

You can acquire anti-virus product information for JP1/IT Desktop Management 2 - Manager and manage the virus definition files installed on the devices. You can use this information to determine whether the latest virus definition files have been installed.

4.2 Asset management system linked to other program products

Asset Console can be linked to various programs other than JP1/IT Desktop Management 2 - Manager to build a comprehensive asset management system. Consider linking previously purchased programs to Asset Console. For program products not yet purchased, decide whether they are necessary for achieving the objectives of the work.

This section explains the functions that can be expanded through linkage to other program products.

4.2.1 Managing problems by linking to JP1/IM

JP1/IM can acquire information on problems in the asset management system. This information can be registered in the asset management database and managed. Asset management tasks that can be achieved by linking to JP1/IM are explained below.

Linking to JP1/IM enables automatic registration of problems into the asset management system on the basis of JP1 events and SNMP trap information. In addition, problems from JP1/IM can be confirmed. Managing these problems is useful for preventive maintenance.

The figure below shows asset management tasks that can be achieved by linking to JP1/IM.

Figure 4‒3: Asset management tasks performed by linkage to JP1/IM

Information on JP1 events and SNMP traps collected by JP1/IM can be used to confirm and respond to problems in the asset management system

You can browse the problems collected by JP1/IM events from the Problems job menu. Also, notification can be issued that JP1/IM measures have been taken, and problem information status can be changed to handled.

Displaying detailed information for problems from JP1/IM

In the JP1/IM Event Console window, you can view detailed information for the problems registered in Asset Console from JP1 events (notifications of completed countermeasures for problems) issued by Asset Console.

For details about Asset Console JP1 events issued when you link to JP1/IM, see 19.2 Details of JP1 events issued from Asset Console.

4.2.2 Linking to EUR and outputting the search results in PDF format

EUR is a program that prints out forms by using input data in table format. EUR provides various functions that let you design forms without creating difficult programs. Asset Console can link to EUR, and display and print out data searched by Asset Console as forms in PDF-file format. Because the searched data can be set in EUR to be displayed as bar codes, you can use the asset numbers searched in Device List as bar codes for stocktaking. You can also print a bar code on a seal, and put the seal on a managed device. You can output the information below as the search results in PDF format. The buttons for outputting these information items are set to be displayed by default.

Device List

Contract List

Problem Details

Owned License List - by Used

Excess License List - by Used

Unauthorized Usage List - by Used

Unknown Usage List - by Used

Software List

Software Details

Volume License List

Volume License Details

Maintenance Log Detail

User Report

5 Operating Method

This chapter explains how to choose the operating method when designing an asset management system.

5.1 Access permissions

Asset information includes not only device and software information, such as an asset's type, name, and registration date, but also information that should be edited only by specified users. In this case, you can limit the scope of access by specifying roles for the users who use the asset information.

If only applicable asset information is to be made available to the system administrator of each group, you can limit the scope of access according to groups by specifying user roles.

This section explains the access permissions that can be set by Asset Console.

5.1.1 Types of user roles

Two user roles are supported by Asset Console, the administrator and the user. This section describes each of these roles.

Administrator

This is a user in charge of device and network management in the asset management group (data system management department).

The administrator is authorized to change the settings for the entire asset management system and acquire, remove, and select the asset information to be managed.

The asset manager (user ID: admin) that is created when Asset Console is installed has this role.

User

This can be a user in charge of device or network management in each group or a general user. The user can use the information managed in the asset management system to execute various asset management jobs, but cannot allocate jobs whose execution depends on the role.

You can change the details of the user roles and create new user roles. For details about changing user roles, see 11.1 Changing user roles (Role).

5.1.2  Types of access permissions for users

This section describes the access permissions that can be set for the Asset Console users according to their user roles.

Availability of Asset Console login

To use Asset Console, register each user, and assign to each user the appropriate user role. The users can then log in to Asset Console.

During the construction of an asset management system, the administrator user (user ID and password: admin) is registered.

Access permissions by group level

Limit the asset information available to each user at the group level according to the user role. The figure below provides an overview of the access permissions by group level.

Figure 5‒1: Access permissions by group level

To set access permissions by group level, specify the group level that can handle asset information (managed label).

For details about how to specify managed labels for individual user roles, see 5.1.3 Assigning access permissions according to organizational hierarchy.

Limiting the functions that can be executed from windows

You can customize window operations by user role by limiting the items and buttons that are displayed.

For details about limiting the functions that can be executed from windows according to user role, see 11.3 Changing a window for a user role (Customize Job Windows).

You can also display the buttons that are hidden in the default settings and use them along with the settings for the Customize Job Windows. For details about the types of buttons that are hidden in the default settings, see 11.2.4 Changing the names and view/hide settings for buttons and tabs.

Limiting the available menus

You can limit the functions available to each user role and display only applicable menus.

For details about setting the menus for each user role, see 11.4 Changing the executable jobs (Customize Job Menu).

5.1.3  Assigning access permissions according to organizational hierarchy

To limit accesses at the group level, you must set a Managed label for the desired group and then set the same Managed label for the user role. The example below shows the flow of limiting access by either User or Manager. The job menu selected when this is set is shown in parentheses.

Figure 5‒2: Flow of setting access control

Set Managed label in the detail information for the group level whose access you wish to limit (Group and User).

Set Section as the Managed label for Sales Section 1 and Sales Section 2, and set Department as the Managed label for the Sales Department. For details about setting Managed label, see 16.1.1 Adding a group.

Set Managed label in the detail information for the user role (Role).

Set the Managed label set for the group (Section or Department) to the user role (User or Department head) for which you wish to limit access. For details on setting user roles, see 11.1.1 Adding a new user role.

Log in under the user role for which access has been limited.

User A, who holds User role, can display only information for Sales Section 2, to which this user belongs. User B, who holds Department head role, can display information for the entire Sales Department.

The order of steps 1 and 2 can be reversed.

If you assign a division to a user for whom access control is set according to an organizational hierarchy, you can view and modify the asset information of the group belonging to the division, in addition to the access scope that is set for the user.

Note

When changing a managed label, make sure that the managed label set for the user role is also changed.

5.2  Collecting asset information

The asset information to be managed by the asset management database can be collected either from JP1/IT Desktop Management 2 - Manager or from a CSV file.

If you want to manage various types of information in a large system, Hitachi recommends that you collect asset information from JP1/IT Desktop Management 2 - Manager. However, if data already exists when Asset Console is being installed for the first time, or if there is information not being collected by JP1/IT Desktop Management 2 - Manager, you can also collect asset information from a CSV file. Choose an appropriate asset information collection method based on the application objective and timing, such as during initial installation or daily operations.

The two methods of collecting asset information, the first from JP1/IT Desktop Management 2 - Manager and the second from a CSV file, are explained below. For the collection of asset information from JP1/IT Desktop Management 2 - Manager, how to set the management information assignment method and how to set the software name assignment are also explained.

5.2.1 Collecting from JP1/IT Desktop Management 2 - Manager

JP1/IT Desktop Management 2 - Manager management information is periodically collected by a task in the Windows Task Scheduler.

The figure below shows how the management information collected by JP1/IT Desktop Management 2 - Manager is registered into the asset management database.

Figure 5‒3: Registering JP1/IT Desktop Management 2 - Manager management information into the asset management database

A Windows Task Scheduler task periodically executes to update the changes in the JP1/IT Desktop Management 2 - Manager management information into the asset management database. You can achieve network and asset management server operation with no workload by adjusting the execution timing of the Acquisition of ITDM2 - Manager management information (Asset Console) task.

For details about the information that can be collected from the JP1/IT Desktop Management 2 - Manager management information, see 19.1 Management information that can be acquired from JP1/IT Desktop Management 2 - Manager.

Deletion of asset information that is not included in the JP1/IT Desktop Management 2 - Manager management information

Registering JP1/IT Desktop Management 2 - Manager management information does not automatically delete asset information in the asset management database. However, for network information or installed software information, asset information that is not included in the newly acquired JP1/IT Desktop Management 2 - Manager management information is assumed to have been either deleted from the network or uninstalled from a device, and can be deleted. For each device, you can set ITDM2 management information acquisition control on the Device Details dialog to specify whether to delete the asset information. For details about the setting of ITDM2 management information acquisition control, see 14.6.2 Viewing and changing network information (Network tab) or 14.6.3 Viewing and changing installed software assets (Software tab).

Notes on usage in an environment where Daylight Saving Time is used

If you acquire the JP1/IT Desktop Management 2 management information during the period when Daylight Saving Time is being used, all the information related to time is adjusted according to Daylight Saving Time and then registered. If you acquire the JP1/IT Desktop Management 2 management information after the state of Daylight Saving Time is changed, the information is updated and its update history is also registered (Only when it is selected to be acquired as change logs).

If device information is registered into JP1/IT Desktop Management 2 - Manager one hour before or after the state of Daylight Saving Time being changed, the management information may not be acquired even if you execute the acquisition of JP1/IT Desktop Management 2 management information. In such cases, wait for a while and then retry. Or, execute the acquisition command (jamTakeITDM2Info.exe) by specifying -ALL option.

5.2.2 Collecting from CSV files

Asset Console enables you to acquire asset information from CSV files and insert it into the asset management database in a batch operation. This is called importing.

There are three ways to perform importing:

From the Import job menu

Using jamCsvImport.bat

Using the jamimport command

This section explains the advantages of the various methods of importing. Select the method that will give you the best efficiency on the basis of the information that you want to import.

Importing from the Import job menu

You can create import conditions for the CSV file in order to obtain the asset information that you want to register and update the CSV file asset information in a batch operation. You can specify in the conditions the items in the CSV file that are to be assigned to the Asset Console management items.

This method can import from anywhere, as long as it is an environment that can log in to the Asset Console.

You do not have to have knowledge of the CSV file format or of the classes or the relationships among classes in order to update information into the asset management database.

You can also register user reports, job window forms, JP1/IT Desktop Management 2 - Manager management information assignment settings, and import/export conditions.

However, you cannot import multiple CSV files at the same time or both register and delete at the same time.

Importing using jamCsvImport.bat

The same processing as when you use the Import job menu can be performed from the command line on the asset management server. This method is useful for automating asset information updating operations because you can update the asset information according to a job category, such as Device information, without being concerned about the CSV file format, the class, or the class relationship. However, processing time is greater than when you use the jamimport command.

With this method, the import conditions cannot be changed or saved.

Importing using the jamimport command

A CSV file with asset information to be updated can be created for each class, and the CSV files can be imported in a batch operation without having to accept or reject the contents of the CSV files.

With this method, you can import all object classes and you can import multiple CSV files at the same time. Moreover, each line in a CSV file can contain a register, change, or delete specification.

Because updates can be done in units of classes, data exported for backup can be restored and pinpoint data updates can be used. However, if CSV files are created following the method for data files and there are related classes, the shared property values must be made the same and must be imported at the same time.

For details about each import method, see 9.1 Registering CSV data (importing). For details about the information that can be imported (classes), see 20.1 Organization of classes.

5.2.3  Setting the management information assignment method

JP1/IT Desktop Management 2 - Manager can collect information about PCs, printers, and other devices in the network, as well as information about software installed on PCs. In order to load this collected information (management information) into the asset management database and use it for management, the devices managed by JP1/IT Desktop Management 2 - Manager and the devices managed by Asset Console must match. This is to avoid registration errors such as the information for one device being registered as information for a different device.

To accurately assign the information collected by JP1/IT Desktop Management 2 - Manager as asset information in the asset management database, you must set the key for management and the asset information.

In addition, if a communication card, such as a mobile card or wireless LAN card, is shared by multiple PCs, the information collected by JP1/IT Desktop Management 2 - Manager will contain the same MAC address assigned to multiple management-target devices. In such a case, if the MAC address is set up as the key for Asset Console to assign asset information to the asset management database, these devices will be registered as a single device. By registering MAC addresses in an assignment-exclusion MAC list, you can register and manage devices as separate assets. For details about how to define an assignment-exclusion MAC list, see 5.2.3(5) Defining an assignment-exclusion MAC list.

This section describes how management information is registered depending on the settings in the ITDM2 management information acquisition job menu.

The figure below shows the flow of settings and assignment in ITDM2 management information acquisition.

Figure 5‒4: Flow of settings and assignment in ITDM2 management information acquisition

Numbers (1) through (4) in the figure correspond to the headings for the explanations provided below.

Note

If the device type of the target asset information is not Computing (the Device type code is between 100 and 199), the new asset is registered.

(1) Host IDs

Host IDs, each of which has a unique value in the JP1/IT Desktop Management 2 - Manager system, are used to identify individual devices. Host IDs are generated when JP1/IT Desktop Management 2 - Agent is installed, and automatically reported to the management server. The host IDs are used in Asset Console to assign devices.

(2) Assigning management information

There are two ways to assign management information to asset information. One is to use the asset number, and the other is to use the assigned key.

Using the asset number

Assign management information sets collected by JP1/IT Desktop Management 2 - Manager to asset numbers.

For details about the settings for assigning management information to asset numbers, see 16.14.1 Setting an assigned item for asset numbers.

Using the assigned key

An assigned key is set for each device type. The following table shows the types of devices and assigned keys.

Table 5‒1: Device types

Device type

Contents

Computing

PCs, PC servers, UNIX, UNIX servers, Smart Devices, Other system devices

Accessories

Monitors, Hard disks, CD-Rs, CD-RWs, DVDs, DATs, MOs, Printers, Peripheral Devices, USB Devices, Other storage devices

Networking

HUBs, Routers, Network printers, Network devices

Table 5‒2: Types of assigned keys

Assigned key#1, #3

Remarks

Not set

--

Serial number of the machine

--

MAC address#2

The following classes are subject to assignment:

1. 20.2.10 HardwareInfo (hardware information)

2. 20.2.21 NetworkInfo (network information)

In the target class, devices are searched for in the above order.

IP address (default)

Host name

Legend:

--: Not applicable.

#1

Multiple assigned keys can be combined and specified.

#2

The MAC addresses registered in the assignment-exception MAC list (5.2.3(5) Defining an assignment-exclusion MAC list) are excluded.

#3

Only when all items specified as assigned keys exist in the management information collected from JP1/IT Desktop Management 2 - Manager, the management information is assigned to the assets managed by Asset Console.

(3) New registration of unassigned assets

If there is no corresponding asset information, whether the asset is to be registered depends on the Register information in the ITDM2 management information acquisition job menu. If Register new information is specified, the asset will be newly registered. If Do not register new information is specified, the asset will not be registered.

(4) Status of the deleted asset devices

If asset devices are deleted from JP1/IT Desktop Management 2 - Manager, the status of the deleted asset devices can be changed in Asset Console. For details about how to change the device status, see 16.8 Adding and changing types and statuses (Code).

(5) Defining an assignment-exclusion MAC list

Assume that multiple management-target devices have the same MAC address assigned to them when MAC addresses are set up as the key for Asset Console to assign asset information to the asset management database. In this case, to register these devices as separate assets, you must create an assignment-exception MAC list (MacListOfOmitMatching.ini).

The storage destination, the description method, and a description example of the assignment-exception MAC list are as follows:

Assignment-exception MAC list storage destination

Asset-Console-installation-folder\env

A sample file of the assignment-exception MAC list (MacListOfOmitMatching.ini.org) is provided in the aforementioned storage destination for use as a reference when creating an assignment-exception MAC list. View this sample when creating an assignment-exception MAC list.

Note

When assigning keys, Asset Console checks the file in the aforementioned storage destination. If no file is found in this storage destination, it is assumed that there are no MAC addresses to be excluded from assignment.

Assignment-exception MAC list (MacListOfOmitMatching.ini) entry method

; MAC Address List of Omit Matching.
[OMIT_MAC]
OMIT_MAC = 00:11:22:33:44:55

[OMIT_MAC]

Specifies the MAC address to be registered in the assignment-exception MAC list.

Specify the MAC address to be excluded from assignment in the OMIT_MAC = MAC-address format.

When specifying a MAC address to be excluded from assignment, note the following points:

Do not specify an abbreviation.

The delimiter for MAC addresses is the colon (:).

Specify 17 characters. Note that MAC addresses are not case-sensitive.

Specifying the same value more than once does not cause an error.

You can specify a maximum of 1,000 MAC addresses. However, if a large number of unnecessary key names or values are entered, errors might occur, even if the number of addresses does not exceed 1,000.

Assignment-exception MAC list definition example

;
; MAC Address List of Omit Matching.
;
[OMIT_MAC]
OMIT_MAC = 11:22:33:44:55:66
OMIT_MAC = aa:bb:cc:dd:ee:ff

In the above example, 11:22:33:44:55:66 and aa:bb:cc:dd:ee:ff are set as MAC addresses to be excluded from assignment. If there are multiple devices with these addresses, they are registered as separate devices (assets) in the asset management database.

5.2.4 Setting the software name assignment method

To manage software licenses, it is necessary to assign the name of the software installed in each device (installed software name) to the name of the software (software name) whose license is being managed.

If Asset Console is set to collect installed software information from JP1/IT Desktop Management 2 - Manager, installed software names can be automatically assigned to software names.

Select the ITDM2 management information acquisition job menu, Action settings, and then Acquisition target. Then in Software information, select the following check boxes.

Automatically assign software

When management information is acquired from JP1/IT Desktop Management 2 - Manager, if the same software is already registered in the install software list, you can specify whether to add the assignment to the same software name.

You can specify either of the following two values for Automatically assign software:

- Do not assign automatically (default)

- Assign automatically

Automatically register software

When acquiring management information from JP1/IT Desktop Management 2 - Manager, choose whether to register a software name using the same name as the installed software name and assign them to each other.

If Do not automatically register new information (default) is chosen, only the installed software name is registered, and software name registration or assignment are not executed. If an installed software name not registered in the asset management database is contained in the acquired management information, assign a software name using the Software Name job menu.

If Automatically register new information is specified, an installed software name having the same name in the management information acquired from JP1/IT Desktop Management 2 - Manager and the software name is registered and automatically assigned. Note that Commercial is registered as the software type. For the procedure for changing the software type, see 16.6.4 Changing a software name and attributes.

Click the Set button.

Note

If software with a software type of Commercial is already registered in the asset management database, the software is registered under a name with an _X suffix (where X is a number between 1 and 99) and is assigned to an installed software name. The number is sequentially assigned, beginning with 1 to 99. If numbers up to 99 are already registered, no assignment is executed, and the fact that the software name was not registered because it had already been registered is output to the log.

5.2.5 Setting the software name auto-assignment with the definition file

When management information is collected from JP1/IT Desktop Management 2 - Manager, a software name is registered and associated with according to the definition in a software identification rule definition file. The software identification rule definition file defines strings for identifying installed software programs and match conditions for these strings. If an installed software name collected matches one of the conditions in the definition file, the corresponding managed software name is assigned to the software program.

If the software identification rule definition file does not exist, the software name is registered according to software auto-assignment settings.

Important

When a name has already been assigned to a software program, the name will not be reassigned even if it is different from the definition in the definition file. Only if the software identification rule definition file exists when a new software program is added, the name is assigned to the program. If you want to reassign a name, first remove the installed software program from the list, and then collect its management information from JP1/IT Desktop Management 2 - Manager again.

(1) Software identification rule definition file

The following describes the software identification rule definition file.

(a) File specifications

Item

Description

File name

SoftwareName.csv

Storage location

Asset-Console-installation-folder\env

Character code

Depends on the OS running Asset Console as follows:

If the OS language is set to Japanese: Shift-JIS

If the OS language is set to English: Windows-1252

If the OS language is set to Chinese: GBK

Effective number of rows

If the number of rows exceeds the following value, the definition is ignored:

Parameter: 1 row per key

Software identification rule: 20,000 rows including the match and exclusion conditions

(b) Format

P,parameter-key,parameter-value
T,match-condition,"target-matching-string",[exclusion-from-match-condition,"target-exclusion-from-match-string",]"software-name"
E,exclusion-condition,"target-string"

Note

If the target matching string, target exclusion-from-match string, or software name contains a double quotation mark ("), specify it as "".

(c) Definition

Definitions in the software identification rule definition file (parameters)

The parameters define general operations.

Column

Value to be defined

Type

(first column)

Specify P.

Parameter key

Specify the value below for this column. This column defines how an installed software program is handled when its software identification rule is not found in the definition file.

NO_RULE_INSTALLEDSOFTWARES

Parameter value

Specify either of the values below. The default value is 0.

0: Managed software names are not registered.

1: Names of managed software programs with the same name as installed software programs are assigned. If managed software names already exist, the names are assigned to existing managed software programs.

Definitions in the software identification rule definition file (match conditions)

The match condition defines conditions for identifying installed software programs.

Column

Value to be defined

Type

(first column)

Specify T.

Match condition

Defines how the target match string matches the installed software name. Specify either of the following:

1: Start-with match

2: Partial match

Target matching string

Defines the name of the installed software program to be matched. Specify any character string with no more than 1,024 characters. The match condition determines which part of the string is matched.

Exclusion-from-match condition

Defines how the target exclusion-from-match string matches the installed software name. Specify either of the following:

1: Start-with match

2: Partial match

If an installed software program matches the exclusion-from-match condition, it is excluded from identification even when it matches the match condition.

In this case, if it matches a different match condition, it is registered using the managed software name defined in that condition.

Target exclusion-from-match string

Defines the name of the installed software program to be excluded from matching. Specify any character string with no more than 1,024 characters. The exclusion-from-match condition determines which part of the string is matched.

Managed software name

Defines the name of the managed software program to be identified. Specify any character string with no more than 1,024 characters.

Definitions in the software identification rule definition file (exclusion conditions)

The exclusion condition defines conditions for excluding software in the software identification rule. If an installed software program matches the condition in this type of definition, it is excluded from the targets whose software names are auto-assigned according to the definitions in the software identification rule definition file. The software program is not identified and registered even if it matches the match condition.

Column

Value to be defined

Type

(first column)

Specify E.

Exclusion condition

Defines how the target string matches the installed software name. Specify either of the following:

1: Start-with match

2: Partial match

Target string

Defines the target installed software name. Specify any character string with no more than 1,024 characters. The exclusion condition determines which part of the string is matched.

Important

If the first column in a row has a value other than P, T, or E, the row is treated as a comment line and thus ignored. A row is also ignored due to a syntax error if:

It does not have the correct number of columns that corresponds to the type specified in the first column.

Any of the match condition, exclusion-from-match condition, and exclusion condition has an invalid value.

Any of the target string, managed software name, parameter key, and parameter value has a value that exceeds their limit.

(d) Example

#software identification rule definition file
P, NO_RULE_INSTALLEDSOFTWARES,1
T,1,"Adobe Acrobat",2,"Reader","Adobe Acrobat"
T,2,"Document Reader","Document Reader"
E,1,"Microsoft .NET Framework"
E,2,"Debug"

(e) Notes

Behavior when multiple definitions are matched:

The following describes the behavior if a target string matches multiple definitions:

If multiple rules with the same type are matched, the first matching rule is used.

If both the match condition and exclusion condition of the rules are matched, the exclusion condition takes precedence.

If none of the match condition and exclusion condition of the rules is matched, the NO_RULE_INSTALLEDSOFTWARES setting is used.

If multiple rules with the same parameter key are specified, the first defined rule is used.

Behavior when the function is enabled/disabled:

The following describes the behavior when the software identification rule definition file is modified or when the function is enabled or disabled through the presence or absence of software identification rule definition file:

If you add, modify, or delete a rule to, in, or from the software identification rule definition file, the change will take effect when the management information is collected from JP1/IT Desktop Management 2 - Manager after the editing.

If the software identification rule definition file is removed after the name of a managed software program is registered, the program assigned by the definition file remains unremoved.

Even if the definition of the rule for the installed software program already registered is modified, no reassignment to the managed software is performed. If you want auto-assignment, first remove the installed software program from the list, and then collect its management information from JP1/IT Desktop Management 2 - Manager again.

Behavior when management information is collected from sources other than JP1/IT Desktop Management 2 - Manager:

If management information is migrated to Asset Console through a migration tool or CSV file, the information from the source is used as it is. Even when the management information is collected from JP1/IT Desktop Management 2 - Manager later, reassignment according to the software identification rule definition file will not be performed.

5.3 Notification by email to the asset manager

Asset Console can use the Windows task scheduler function to send email notification to the asset manager when it detects contract expiration, an excess number of licenses, unauthorized installation, or a change to device information. Additionally, when an Item is sent to another worker, Asset Console can send an email notification to that worker.

This section explains the environment necessary for using notification by email and the content that is sent, so that you can decide whether to use notification by email and for what jobs.

To use notification by email, you must specify it in both Asset Console and Microsoft Internet Information Services.

Settings in Asset Console

Notification by e-mail

In the Server Setup dialog box, under Mail Notification Information, set Notification by e-mail to Notify.

Address to e-mail

In the Server Setup dialog box, under Mail Notification Information, for Address to e-mail, set the email address of the asset manager to which email notification is to be sent.

For details about specifying the settings in the Server Setup dialog box, see 7.3.5 Setting Mail Notification Information.

Settings in Microsoft Internet Information Services

SMTP virtual server execution

Make sure that the SMTP virtual server is running.

For details about setting up the SMTP virtual server, see 7.10.1 Executing the SMTP virtual server.

Relay of received email to a remote domain

Add a remote domain to the SMTP virtual server and specify the settings in such a manner that received email will be relayed to that remote domain.

For details about the settings for relaying received email to a remote domain, see 7.10.2 Adding a remote domain.

5.3.1 Notification of invalid contract information

You can use the Notification of invalid contract information (Asset Console) task to periodically send email notifications regarding maintenance, lease, and rental contracts that have expired.

The email sent by this task lists the category, end date, and contract number of each contract, as shown in the figure below.

Figure 5‒5: End date notification email

The task also sends CSV files as email attachments. These files contain lists of the assets corresponding to the contracts that are about to expire. If no lease or maintenance contracts are about to expire, the task does not attach any files.

The following table describes the names and contents of the files that can be attached.

File name

Contents

jamexpiration_A.csv

List of assets corresponding to lease contracts that are about to expire

jamexpiration_B.csv

List of assets corresponding to maintenance contracts that are about to expire

jamexpiration_C.csv

List of assets corresponding to rental contracts that are about to expire

The figure below shows an example of the contents of a file attached to an email notification of expiring lease contracts.

Figure 5‒6: File attachment to email notification of expiring lease contracts

In the default setting for the Notification of invalid contract information (Asset Console) task, the task is executed at 6:00 am on the first day of every month, and it sends a notification by email about any contract that will expire within two months. For details about how to change the date and time and the frequency of task execution, see 7.9.2 Task setup procedure.

Note

Because the task is set to execute only once a month, a short contract whose duration is less than one month might not be included in the notification under the default settings. For example, if a contract is in effect from March 20 through March 30 and was not registered on March 1, it will never be subject to notification by the task.

If such short-time contracts might be common, you should add a schedule for sending email notifications that will include them. For details about the procedure for adding schedules, see 7.9.2(2) Changing a task schedule.

5.3.2 Notice of license excess

You can use the Notice of license excess (Asset Console) task to periodically total up the numbers of licenses owned and used. Based on the results, license usage status can be managed from each license management job menu.

If the totaled results show any licenses that exceed the owned numbers, a list can be sent by email. If email notification is not needed, use the Totals number of licenses (Asset Console) task. The totals given in Notice of license excess (Asset Console) and Totals number of licenses (Asset Console) are the same. If email notification is required, use Notice of license excess (Asset Console). If it is not required, use Totals number of licenses (Asset Console). Because these tasks take some time to execute, it is recommended that you not use Totals number of licenses (Asset Console) together with Notice of license excess (Asset Console).

This task is created when Asset Console is installed.

As shown in the figure below, the notification email includes an explanation that the number of use licenses exceeds the threshold value of the number of retained licenses.

Figure 5‒7: Notification email about excessive number of licenses

A list of licenses exceeding the number of retained licenses is attached to the email as a CSV file.

The figure below shows the contents of the email attachment.

Figure 5‒8: File attached to an email sent regarding the licenses exceeding the number of retained licenses

With the default setting for the Notice of license excess (Asset Console) task, the task is executed at 5:30 am every week on Monday. For details about the procedure for changing the date and time and the frequency of task execution, see 7.9.2(2) Changing a task schedule.

Notes

This task sends notifications only for licenses that are being managed as assets. Even if unregistered licenses are being used, no email notification is sent.

This task sends notification by email when the licenses exceed the number of retained licenses when the task is executed. Consequently, if the number of licenses exceeds the number of retained licenses during a week, and additional licenses are obtained, the task sends no notification by email. To increase the frequency of monitoring from the default setting, reduce the execution interval of email notification schedule.

If totaling is executed multiple times in a large system with several thousand devices, then a large amount of old totals results data remaining in the database increases the time required for searches, additions, and deletions, reducing the performance of totaling.

If you have a large asset management system with several thousand devices, it is important to delete old totals results periodically.

By changing the threshold value of the number of retained licenses, which is set to 100% by default, notification by email can be sent for licenses that are about to exceed their threshold values. To change the threshold value for each license, use the Software Name window. If no threshold value has been set, use the Server Setup dialog box.

For details about how to change the threshold value in the Software Name window, see 16.6 Establishing correspondence between software names (Software Name). For details about how to change the threshold value in the Server Setup dialog box, see 7.3.4 Setting Basic Information.

5.3.3  Notification of unauthorized install

You can use the Notification of unauthorized install (Asset Console) task to automatically send email notification about devices on which unauthorized software is installed.

An email notification sent by this task describes the devices on which unauthorized software is installed, as shown in the figure below.

Figure 5‒9: Email notification of unauthorized software

The task also sends a CSV file as attachment to the email. This file contains a list of the devices on which the unauthorized software is installed.

The following figure shows the contents of the email attachment.

Figure 5‒10: Email attachment to the notification of unauthorized software

With the default setting for the Notification of unauthorized install (Asset Console) task, the task is executed every week at 5:30 am on Tuesday. For details about the procedure for changing the date and time and the frequency of task execution, see 7.9.2(2) Changing a task schedule.

Note

This task includes in the email notification any device it detects during execution on which unauthorized software is installed. It does not provide notification of a device on which unauthorized software was installed and uninstalled within the preceding week. To increase the frequency of monitoring from the default setting, reduce the execution interval of the email notification schedule.

5.3.4  Notification of Item arrival

When application and approval jobs are executed using Items, you can send notification by email when an Item arrives (submitted for approval or rejected). You can edit the text of the email when sending it. The figure below shows the email that is sent when a sample Item called Problem Report Form is submitted.

Figure 5‒11: Item arrival notification email

Item arrival notification is sent to the email addresses provided in the user information. Therefore, when using notification of Item arrival, you need to manage the email addresses in the user information.

5.3.5  Notification of hardware change

You can send email notifications when device information is updated.

The email reports the number of devices that have been changed, as shown in the following figure.

Figure 5‒12: Hardware change notification email

To send email notification about updated device information, you must register the task after installing Asset Console. For details about how to register the task, see 7.9.8 Notification of device information change.

5.4 Installation in a cluster system

You can also install Asset Console in a cluster system that uses cluster software. A cluster system links multiple servers and runs them as a single system. If there is a problem on one of the systems, applications can be inherited by another server (this is called failover), which saves the entire system from being shut down.

Asset Console supports active-standby configuration, which is one of the operation modes for cluster systems. The active-standby configuration is a two-node cluster system in which one server is set as the executing system and the other as the standby system.

The following figure provides an overview of a cluster system that uses Asset Console.

Figure 5‒13: Overview of cluster system using Asset Console

Separately from the physical host name and IP address of the asset management server, a logical host name or logical IP address is used to connect to the logical server. This enables the user to establish connection without having to know which server is actually executing the processing.

The following OSs are supported as the OS required for the asset management server when a cluster system is established:

Microsoft Windows Server 2019 Datacenter

Microsoft Windows Server 2019 Standard

Microsoft Windows Server 2016 Datacenter

Microsoft Windows Server 2016 Standard

Microsoft Windows Server 2012 R2 Datacenter

Microsoft Windows Server 2012 R2 Standard

Microsoft Windows Server 2012 Datacenter

Microsoft Windows Server 2012 Standard

5.5 Linking to Active Directory

By linking to Active Directory, you can, for example, authenticate attempts to log in to Asset Console and import user information managed by Active Directory into the asset management database.

For details about the prerequisite programs for linking to Active Directory, see 6.1.1(5) Prerequisite programs for linking to Active Directory.

This section explains the settings necessary for linking to Active Directory and the procedure for importing user organization information.

5.5.1 Login authentication

To authenticate Asset Console logins by linking to Active Directory, you must specify the necessary settings in Directory server usage in the Server Setup dialog box. For details about the settings in the Server Setup dialog box, see 7.3.6 Setting Link with Directory Server.

Be sure to gather in advance the information necessary for the settings in the Server Setup dialog box.

Note

To gather the necessary information in advance:

Use administrator permissions to log in to the computer that Active Directory is running on.

Execute the LDIFDE command of Active Directory and output the DN information of users who are permitted to log on.

The following is the command to be executed:

ldifde -u -p Subtree -r "objectclass=user" -l dn -f out1.txt

The following information is output to out1.txt:

dn: CN=Administrator,CN=Users,DC=Sample,DC=co,DC=jp

changetype: add

dn: CN=Guest,CN=Users,CN=Users,DC=Sample,DC=co,DC=jp

changetype: add

:

Based on the output information, set the user DN to be used for connecting to Asset Console in Access user in the Server Setup dialog box.

Execute the LDIFDE command of Active Directory and output the DN information of the organization from which to search for users during Asset Console login authentication.

The following is the command to be executed:

ldifde -u -p SUBTree -r "(objectclass=organizationalUnit)" -l dn -f out2.txt

The following information is output to out2.txt:

dn: OU=Domain Controllers, DC=Sample,DC=co,DC=jp

changetype: add

dn: OU=people, DC=Sample,DC=co,DC=jp

changetype: add

dn: OU=hitachi,OU=people, DC=Sample,DC=co,DC=jp

changetype: add

:

Based on the output information, set the DN of the organization from which to search for users during Asset Console login authentication in User information DN in the Server Setup dialog box.

Output the attribute information of the user information to be used during Asset Console login authentication.

The following is the command to be executed:

ldifde -u -p Subtree -r "cn=Administrator" -f out3.txt

The following information is output to out3.txt:

dn: CN=user1,OU=Design3,OU=hitachi,OU=people, DC=Sample,DC=co,DC=jp

changetype: add

objectClass: top

objectClass: person

objectClass: organizationalPerson

objectClass: user

cn: user1

son: customerA

telephoneNumber: 030303

givenName: user1

distinguishedName:

CN=user1,OU= Design3,OU=hitachi,OU=people, DC=Sample,DC=co,DC=jp

instanceType: 4

:

displayName: customerAuser1

uSNCreated: 376915

uSNChanged: 487476

name: user1

uid: user1

mail: a-user1@sample.co.jp

:

Based on the output information, set the attribute name to be used as the user ID during Asset Console login authentication in User ID attribute name in the Server Setup dialog box. Additionally, specify the attribute name to be recognized as a user name by Asset Console in User name attribute name in the Server Setup dialog box.

5.5.2 Acquiring user organization information

To update the asset management database (user management information) with user information managed by the Active Directory services, you must create an Asset Console script and execute it on a regular basis. Asset Console provides a sample script. This sample script updates the following items:

Post

Email address

Telephone number

The sample scripts (files) are located in the following folder:

Asset-Console-installation-folder\sample\AD\

In addition to the sample script, a document providing a sample script explanation and usage example is also provided. Make sure to read this document before executing the sample script.

The following table explains the sample scripts (files).

Table 5‒3: Sample script explanations

File name

Explanation

ADImport.txt

This sample script imports property values from the Active Directory information entries into the user management information of Asset Console.

ADImportExtend.txt

This subroutine group sample script is called from ADImport.txt and imports property values from the Active Directory information entry attributes into the user management information of Asset Console. To customize this script, modify the file directly.

ADImportCustomize.txt

This document provides explanations and usage examples of ADImport.txt and ADImportExtend.txt.

6 Evaluating System Configuration

This chapter describes the organization of the programs for an asset management system and describes an example system configuration.

6.1 Organization of programs

This section describes the programs that constitute the asset management system and the prerequisite and related programs.

The figure below shows the organization of the programs that constitute the asset management system.

Figure 6‒1: Organization of programs that constitute the asset management system (Asset management server)

Figure 6‒2: Organization of programs that constitute the asset management system (Directory server)

Figure 6‒3: Organization of programs that constitute the asset management system (Agent)

6.1.1 Prerequisite programs

This section describes the programs that are required on the server and administrator's computer in order to run Asset Console.

(1) Prerequisite server programs

OS

Use Windows Server 2019, Windows Server 2016, or Windows Server 2012. However, Server Core installation is not supported. Also, operations in an environment in which OneDrive is used are not supported.

Web server

Use Microsoft Internet Information Services 7.5, 8.0, or 8.5.

You must also install the Web service as a Windows component.

(2) Prerequisite programs on the administrator's computer

OS

Use an OS (Windows) that supports Windows Internet Explorer 9, Windows Internet Explorer 10, or Windows Internet Explorer 11.

Web browser

This is an administrator's computer used for the asset management server to register and reference asset information. Use Windows Internet Explorer 9, Windows Internet Explorer 10, or Windows Internet Explorer 11.

Note that the Metro version of Windows Internet Explorer is not supported.

Important

The enterprise mode in Internet Explorer 11 is not supported.

If you use Internet Explorer 10 or 11, enable the Compatibility View settings. When you add the URL of JP1/IT Desktop Management 2 - Asset Console to the Compatibility View settings, note that IP-address-based and host-name-based URLs are distinguished. Add the URL in the format that is used for actual access.

(3) Prerequisite programs for using notification by email

You may want to use the task scheduler function to automatically send information via email about contracts with approaching expiration dates and licenses that exceed the threshold value of the number of retained licenses. In this case, you need an environment in which Microsoft Windows Script Host Version 5.1 or later and Microsoft Internet Information Services 7.5 or later are both installed.

You must also install SMTP, which is a subcomponent of the Internet Information Service (IIS) Windows component.

For details about setting up email notification, see 7.10 Settings for using notification by email.

(4) Prerequisite programs for displaying PDF files

Asset Console must link with EUR (uCosminexus EUR Server Enterprise 09-00 or later) to display and print out the searched asset information as a PDF file form.

(5) Prerequisite programs for linking to Active Directory

Active Directory that can be linked with can operate on the following OSs:

Windows Server 2019

Windows Server 2016

Windows Server 2012 R2

Windows Server 2012

Windows Server 2008 R2

Hitachi recommends that you operate the asset management server and directory server on different machines.

6.1.2 Related programs

Besides the linkage programs products described as the prerequisite programs, the following programs can be linked to the asset management system and used for operation:

JP1/IT Desktop Management 2

Asset Console can link with JP1/IT Desktop Management 2 with the same version as JP1/IT Desktop Management 2 - Asset Console.

JP1/IM - Manager

Asset Console can link with JP1/IM - Manager 10-00 or later.

JP1/IM - Manager is a product that achieves integrated management of an entire corporate information system.

Linked with JP1-series products that manage diverse system operations, JP1/IM - Manager uses JP1 events to achieve integrated management of the events that occur in the system. In the event of an error, JP1/IM - Manager promptly notifies the administrator and provides the infrastructure for operations needed to locate the error and investigate its cause.

Asset Console can share information about JP1 events that are managed by JP1/IM - Manager and manage the events that have occurred in the asset management system.

For an overview of the JP1/IM - Manager functions, see the JP1/Integrated Management - Manager Overview and System Design Guide.

JP1/Base

Asset Console can link with Job Management Partner 1/Base 10-00 or later, or Job Management Partner 1/Base 10-01 or later.

JP1/Base provides the basic functions of JP1/IM - Manager.

By using the JP1/Base functions, you can manage the events (JP1 events) that are reported when they occur in the system and exchange JP1 events with other hosts.

Asset Console uses the functions provided by JP1/Base to transfer JP1 events managed by JP1/IM - Manager.

For details about the functions of JP1/Base, see the JP1/Base User's Guide.

JP1/Service Support

Asset Console can link with JP1/Integrated Management Service Support 10-10 or later, or JP1/Service Support 11-00 or later.

JP1/Service Support provides functions to promptly check the contents of an Item that occurs and needs to be solved (for example, a query or system failure) and take actions.

By linking JP1/Service Support with Asset Console, you can view information about the device corresponding to an Item from a JP1/Service Support window.

For details about the JP1/Service Support functions, see the JP1/Service Support Configuration and Administration Guide.

6.2 Example of a system configuration

This section provides examples of system configurations for running an asset management system linked with JP1/IT Desktop Management 2 - Manager.

You can implement more efficient single-source management for the networked IT assets within your enterprise by linking Asset Console to JP1/IT Desktop Management 2 - Manager to run asset management jobs. Therefore, for the explanation below, the basic configuration will be a system configuration linked to JP1/IT Desktop Management 2 - Manager.

6.2.1 Basic system configuration

The figure below shows an example of the basic system configuration for an asset management system linked to JP1/IT Desktop Management 2 - Manager. This example shows a basic configuration where the asset management server connects to the management server and acquires the asset information on the managed computers. The examples shown in 6.2.3 through 6.2.7 are also based on this system configuration.

Figure 6‒4: Example of the basic system configuration of an asset management system

The following points should be noted about your system configuration:

Asset management server

Asset Console cannot be installed on a machine on which JP1/NETM/Asset Information Manager, JP1/Asset Manager, or JP1/NETM/Asset Manager is installed.

The network must be configured so that the asset management server and JP1/IT Desktop Management 2 - Manager can view each other's host names and IP addresses.

Only one asset management server can be connected to one JP1/IT Desktop Management 2 - Manager program.

Management server

You can place Asset Console and the management server on the same machine. However, if there are many devices to be managed and the machine will be accessed frequently from the administrator's computer, Hitachi recommends that you place the asset management server and the asset management database server on different machines.

Administrator's computer

If the environment supports Windows Internet Explorer 9, Windows Internet Explorer 10, or Windows Internet Explorer 11, no programs are required.

6.2.2 Multi-server configuration

The figure below shows an example of the basic system configuration for an asset management system linked to JP1/IT Desktop Management 2 - Manager which is in a multi-server configuration. This example shows a configuration where two asset management servers connect to the management relay servers respectively and acquire the asset information on the managed computers.

Figure 6‒5: Example of the system configuration of an asset management system linked to JP1/IT Desktop Management 2 - Manager which is in a multi-server configuration

In addition to the notes on the basic system configuration, the following points should be noted about your system configuration:

Asset management server

An asset management server must be connected to a management server to manage asset information. For example, when you want to manage asset information by using the management relay server, connect the management relay server to the asset management server as shown in the above system configuration example. Before configuring the system, consider which management server is to be connected to which asset management server in the system configuration.

Primary management server and management relay server (management server)

Data whose language is different from the OS language for the asset management server might be garbled. Therefore, set OS languages for the management server, computers under the management server, and the asset management server to be in the combination shown in the following table.

Table 6‒1: Combination of OS languages for the management server, computers under the management server, and the asset management server

OS language for the management server

OS language for computers under the management server

OS language for the asset management server

Support

Japanese

Japanese

Japanese

Y

English

N

Chinese

N

English

Japanese

Y

English

N

Chinese

N

Chinese

Japanese

N

English

N

Chinese

N

English

Japanese

Japanese

N

English

N

Chinese

N

English

Japanese

Y

English

Y

Chinese

Y

Chinese

Japanese

N

English

N

Chinese

N

Chinese

Japanese

Japanese

N

English

N

Chinese

N

English

Japanese

N

English

N

Chinese

Y

Chinese

Japanese

N

English

N

Chinese

Y

Legend:

Y: Supported

N: Not supported

6.2.3 System configuration linked to JP1/IM - Manager

The figure below shows an example of asset management system configuration linked to JP1/IM - Manager. In this system configuration, the asset management server connects to the JP1/IM - Manager server and acquires the managed computer's program information.

Figure 6‒6: System configuration example linked to JP1/IM - Manager

6.2.4  System configuration linked to JP1/Service Support

The figure below shows an example of asset management system configuration linked to JP1/Service Support. In this system configuration, the asset management server connects to the JP1/Service Support server and views the device information managed by Asset Console from JP1/Service Support.

Figure 6‒7: System configuration example linked to JP1/Service Support

6.2.5 System configuration linked to EUR

The figure below shows an example of asset management system configuration linked to EUR. In this system configuration, the search results in Asset Console are output as a PDF file, and displayed and printed.

Figure 6‒8: System configuration example linked to EUR

To output a PDF-file form in the window created as a user report, uCosminexus EUR Server Enterprise is required to create a form.

In addition, the Japanese version of Adobe Reader 7.0 or later must be installed on the administrator's computer.

6.2.6 System configuration linked to Active Directory

The figure below shows an example of asset management system configuration linked to Active Directory. In this system configuration, the asset management server connects to the directory server for Asset Console login authentication or for importing user information managed by Active Directory to the asset management database.

Figure 6‒9: System configuration example linked to Active Directory

6.2.7 System configuration in a cluster system

This subsection describes examples of cluster system configurations that support failover of Asset Console.

Set the higher connection destination as follows when you set up Asset Console programs:

http://logical-host-name-or-logical-IP-address/jp1asset/login.htm

You must also store the following files on a shared disk:

DBMS database files

Transaction log files

Files under the asset management server's virtual directory

If the Asset Console service is set to use the failover facility in a cluster environment using cluster software, hardware problems and Asset Console service problems are automatically detected. Then the active server is automatically switched to the standby server.

You can set the asset management database server in the same cluster group, or you can use the asset management database server set in a different cluster group.

The following figure provides an example of a cluster system configuration.

Figure 6‒10: Example of a cluster system configuration

Part 3: Setup

7 Installation and Setup

This chapter explains how to install and uninstall Asset Console. It also describes how to set up the environment for using Asset Console.

7.1 Setup procedure for Asset Console

This section describes the procedure for setting up the environment for the asset management system. The figure below shows the setup procedure.

Figure 7‒1: Setup procedure

The subsequent sections describe the setup method by following the procedure shown in Figure 7-1.

Note

After setting up the asset management server, you must enable the Data maintenance task that is created in Windows Task Scheduler. For details about the task and its setup method, see 7.9 Setting the tasks that are registered in Task Scheduler.

Tip

To move the data registered in a test environment or the settings made in the system definition, first use the Export job menu and output the information registered in the asset management database and the settings information to a CSV file, and then use the Import job menu to import the information into the target environment. For the operating procedure for the Export and Import job menus, see 16.11 Exporting asset information in CSV format (Export) and 16.10 Changing asset information in a batch operation (Import).

7.1.1  Workflow necessary for acquiring JP1/IT Desktop Management 2 - Manager management information

For linking to JP1/IT Desktop Management 2 - Manager, certain settings are necessary when Asset Console is being installed. Therefore, when setting up Asset Console, also make sure to prepare for linking it to JP1/IT Desktop Management 2 - Manager as follows.

Setting various items necessary for linking to JP1/IT Desktop Management 2 - Manager

Use the Server Setup dialog box to set the login ID and service name for connecting to the JP1/IT Desktop Management 2 - Manager database.

For details about these settings, see 7.3.7 Setting JP1/IT Desktop Management 2 - Manager management information acquisition.

Use the ITDM2 management information acquisition window to set the assignment method for management information and the software name assignment method.

Creating a data source

To connect to the JP1/IT Desktop Management 2 - Manager database, create a data source during setup. For details about how to create a data source, see 7.5 Creating a data source.

Settings for acquiring the asset number, user name, group, and location information

Specify the JP1/IT Desktop Management 2- management information set that is to be assigned to an item (asset number, user name, group name, or location). This is required when you assign a JP1/IT Desktop Management 2- management information set to an asset number, or when you acquire information about the user name, group name, and location from management information.

You can also change assigned items and add information to be acquired from the JP1/IT Desktop Management 2 - Manager management information.

For details about how to assign JP1/IT Desktop Management 2 - Manager management information to managed items, see 16.14 Setting assigned items (ITDM2 Management Information Acquisition).

Task settings

To use a task registered in Windows Task Scheduler to periodically collect JP1/IT Desktop Management 2 - Manager management information, enable the Acquisition of ITDM2 - Manager management information (Asset Console) task. This task is disabled by default.

For details about setting tasks, see 7.9 Setting the tasks that are registered in Task Scheduler.

7.2 Installing and uninstalling Asset Console

This section explains how to install the programs that are used to run the asset management system. It also explains how to uninstall Asset Console.

7.2.1 Installing the prerequisite programs

This subsection describes how to install the prerequisite programs for the asset management server and administrator's computer.

(1) Installing the prerequisite programs required for the asset management server

Windows Server 2019, Windows Server 2016, Windows Server 2012

For details about how to install Windows Server 2019, Windows Server 2016, and Windows Server 2012, see the applicable installation manual and Help.

Microsoft Internet Information Services

For details about how to install Microsoft Internet Information Services, see the Windows documentation.

Simple Mail Transport Protocol (SMTP)

Install this program when the execution results of the tasks registered in Windows Task Scheduler are to be sent to the asset manager via email or when the next worker is to be notified via email when an Item has been set. For details about how to install Simple Mail Transport Protocol (SMTP), see the Windows documentation.

(2) Installing the prerequisite programs for the administrator's computer

Windows Internet Explorer 9, Windows Internet Explorer 10, or Windows Internet Explorer 11

For details about how to install the Web browser to be used, see the instructions for installing Microsoft Internet Explorer.

In the language setting for the browser, set either of the following languages that corresponds to the system locale of the machine on which the asset management server is installed. The operation cannot be performed if other settings are applied.

Japanese: [ja] as the first preference

English: [en] as the first preference

Chinese: [zh] as the first preference

7.2.2 Installing Asset Console

This section explains how to install Asset Console.

(1) Installation notes

Note the following items when installing Asset Console:

You cannot install Asset Console on a machine on which one of the following products has been installed:

JP1/NETM/Asset Information Manager

JP1/Asset Manager and JP1/NETM/Asset Manager

JP1/NETM/Asset Information Manager Smart Edition

JP1/NETM/Asset Information Manager for Blade PC

JP1/NETM/DM Asset Information Manager Limited

When you specify the Asset Console installation folder, the folder path must not include double-byte characters.

For the Asset Console installation folder, do not specify a folder directly under the drive root or a folder used for other applications. This is because Asset Console files might overwrite other files. Create a folder dedicated to Asset Console, and then install Asset Console in that folder.

When the component that has already been installed is reinstalled, select Repair from the maintenance window.

The following settings cannot be changed during reinstallation:

Program folders

Virtual directory of the asset management server

When adding or deleting a component, if you cancel installation by clicking the Cancel button during installation, you must re-install Asset Console.

A tmp folder is created directly under the installation drive root. Do not delete the tmp folder.

You must be careful when specifying the drive name or installation folder when restoring the database backup following installation. If you specify an incorrect name or folder, you cannot restore the backup. To use the backed-up database on another machine, install it using the same path that was used for acquiring the backup.

If restart of the computer is required, a dialog box requesting a restart appears. You should restart the computer. If you do not restart the computer, necessary environment information will not be set and an error will occur when the asset management server is started.

Asset Console cannot be installed on a computer on which software that requires the 64-bit Microsoft Internet Information Service has been installed.

If Asset Console and anti-virus products are installed on the same host, remove the following files and folders from the virus-check target. If you run a virus check while Asset Console is stopped and then restart Asset Console, confirm that the following files and folders were checked for viruses.

All files and folders in JP1/IT Desktop Management 2-Asset Console-installation-folder

All files and folders in %ProgramFiles(x86)%\Hitachi\jp1common\jp1asset\

Virtual directories#

Folders that store asset management databases#

Output destination of audit logs#

#

If you previously changed a file or folder from the default file or folder, be sure to remove the current file or folder from the virus-check target.

If you do not remove the files and folders from the virus-check target, file access errors might occur, because the files and folders used by Asset Console will be in use by the anti-virus products. If such an error occurs, problems such as the following might occur:

You might not be able to log in to the management window of Asset Console.

You might not be able to execute commands or tasks in Asset Console.

Attempts to output audit logs might fail.

(2) Pre-installation work

The following jobs must be completed prior to installing Asset Console. When Asset Console is installed, settings for running 32-bit applications are required.

Log on to Windows Server 2019, Windows Server 2016, or Windows Server 2012, as a user with administrator permissions.

Exit all Windows applications.

Start the Task Scheduler service.

To register the tasks provided by Asset Console in Windows Task Scheduler, the Task Scheduler task must be active.

Stop services, commands, and tasks.

When you reinstall the components, stop all Asset Console services, commands, and tasks.

Before you perform a new installation of Asset Console, stop World Wide Web Publishing Service or World Wide Web Publishing.

Before you perform an overwrite installation of Asset Console, stop the services, commands, and tasks in the following order:

World Wide Web Publishing Service or World Wide Web Publishing

Asset Console commands and tasks

To run Asset Console following an overwrite installation, start the services in the reverse of the order in which they were stopped.

If a connection pool is set in an ODBC data source, the connected state continues after an Asset Console job is stopped until the timeout time set in the connection pool expires. Therefore, wait for the connected state to be released before installing Asset Console.

When using Microsoft Internet Information Services version 7.5, 8.0, or 8.5, Hitachi recommends that you install the required role services before installing Asset Console so that the virtual directory is automatically generated. The virtual directory is not created automatically if the required role services are installed after Asset Console has been installed. For details about how to install role services, see 7.8.1(1) Installing the role services.

(3) Installation procedure

To install Asset Console:

Insert the provided media in to the CD-ROM drive.

Install the program by following the installer's instructions. During installation, set up the installation folder.

When the installer starts, a dialog box appears for selecting the component to be installed. Select the Asset Console component.

Click the Install button.

A dialog box appears for confirming that you wish to start installation.

Click the OK button.

A dialog box for starting installation of Asset Console appears.

Click the Next button.

A dialog box for entering user information appears.

Enter your user name and company name.

Click the Next button.

A dialog box for specifying the installation folder appears.

Specify the installation folder.

The program is installed in the specified folder. The default installation folder is as follows:

C:\Program Files (x86)\Hitachi\jp1asset

In the above folder path, C: is the drive where the OS is installed.

Click the Next button.

A dialog box for setting the virtual directory of the asset management server appears. When you need to upload a large volume of files or to make the virtual directory into a shared folder in a cluster configuration, change the virtual directory. Specify the folder to be used as the virtual directory.

Click the Next button.

A dialog box appears for you to confirm the program folder. Check the folder to which the program icon is to be added. The default folder name is JP1_IT Desktop Management 2 - Asset Console.

Click the Next button.

A dialog box appears for confirming the current settings. Check the settings.

Click the Next button.

Installation begins.

When installation is completed, a dialog box to that effect appears.

If a dialog box opens, asking whether to restart the computer, restart it. If you do not restart the computer, environment information required for operations will not be set, and the asset management server will not operate correctly.

(4) Reinstallation procedure

Overwriting or upgrading the Asset Console on a machine that already has the Asset Console installed is called "Reinstallation".

The procedure for Asset Console Reinstallation is as follows:

Insert the provided media in to the CD-ROM drive.

Install the program by following the installer's instructions. During installation, set up the installation folder.

When the installer starts, a dialog box appears for selecting the component to be installed. Select the Asset Console component.

Click the Install button.

A dialog box appears for confirming that you wish to start installation.

Click the OK button.

A dialog box for starting installation of Asset Console appears.

Click the Next button.

A dialog for selecting the type of maintenance will be displayed.

Select Repair and click the Next button.

Maintenance process will start.

When the maintenance is completed, a dialog will be displayed to notify you that the maintenance has been completed.

If a dialog box opens, asking whether to restart the computer, restart it. If you do not restart the computer, environment information required for operations will not be set, and the asset management server will not operate correctly.

7.2.3 Uninstalling Asset Console

This subsection describes how to uninstall Asset Console.

Before you start this procedure, stop all the following services, commands, and tasks in the following order:

World Wide Web Publishing Service or World Wide Web Publishing

Asset Console commands and tasks

Notes

Uninstallation does not necessarily delete the installation folders and files or the Microsoft Internet Information Services virtual directory, and these might remain on the computer. When reinstalling, delete any remaining folders.

Uninstalling Asset Console also deletes the tables inside the asset management database. If you need to use these tables after uninstallation, back up these tables before uninstallation.

For details about how to acquire a database backup, see 18.1.2(1) Backing up the asset management database from the Database Manager dialog box.

To uninstall Asset Console:

On Windows Control Panel, select Add/Remove Programs, JP1/IT Desktop Management 2 - Asset Console, and then click the Uninstall button.

A dialog box appears confirming the deletion.

Click the Yes button.

Asset Console is uninstalled. Note that files and folders that were created after Asset Console was installed are not deleted.

When uninstallation is completed, a dialog box to that effect appears.

7.3 Setting up the asset management server

In Asset Console, you specify the information necessary for setup by using the Server Setup dialog box. This section explains the items that need to be specified in the Server Setup dialog box, and the setup procedure.

In the Server Setup dialog box, specify the following settings:

Database Information

Specifies information such as the login ID and service name to be used to connect to the asset management database.

Session Information

Specifies the forced logout time and the number of users that can be logged in concurrently.

Basic Information

Specifies information such as the items displayed in windows and the maximum values during operation.

Mail Notification Information

Specifies information such as the recipient's email address.

Link with Directory Server

Specifies the character encoding type to be used by Directory Server as well as the server name and port number necessary for linking with Directory Server. These settings are required only when Directory Server is used.

Link with ITDM2

Specifies information such as the login ID and service name to be used to collect management information from the linked JP1/IT Desktop Management 2 - Manager. This setting is required only when linking with JP1/IT Desktop Management 2 - Manager.

7.3.1 Settings in the Server Setup dialog box

This section describes the specification of each setting in the Server Setup dialog box.

Click the Start button and point to Programs, JP1_IT Desktop Management 2 - Asset Console, and then select Setup.

The Setup dialog box appears.

Click the Server Setup icon.

The Server Setup dialog box appears

From the list, select a desired item.

An input field with a drop-down list for entering an appropriate value for the chosen item appears under the list.

Figure 7‒2: Server Setup dialog box

Set the appropriate values for your environment.

To set the items listed below, specify a password in the Set Password dialog box, which opens when you click the Password button.

Login ID in Database Information

Access user in Link with Directory Server

JP1/ITDM2-Manager database login ID in Linkage with JP1/ITDM2

Click the OK button.

The asset management server is set up based on the information you have provided, and the Server Setup dialog box is closed.

To close the Server Setup dialog box without setting up the environment, click the Cancel button.

7.3.2 Setting Database Information

Database Information specifies information such as the login ID and service name to be used to connect to the asset management database.

This section describes the settings for Database Information.

(1) Login ID

Login ID specifies the login ID of the user who will be connecting to the database. For details about creating a database field, see 7.4 Creating an asset management database.

In the Set Password dialog box, set the password.

This setting is mandatory.

Permitted value

For Login ID and password, specify from 1 to 8 characters. By default, both Login ID and the password are admin.

Only the following single-byte characters can be used for Login ID and password:

Letters (A to Z and a to z)

Numeric values (0 to 9)

A letter must be specified for the first character.

Do not specify ALL, MASTER, or PUBLIC for Login ID (case-insensitive).

This value is applied to Connection user ID in the dialog boxes listed below. If you change the value after creating a new asset management database, re-create the data source.

Basic Database Settings dialog box

Dialog box for creating a data source

(2) Service name

Service name specifies the service name for asset management.

Specification of this item is mandatory.

Permitted value

1-32 bytes of alphanumeric and special characters. The default is ASSET_DB_SERVICE_NAME.

!, (, ), *, ,, ;, =, ?, @, [, ], {, }, and spaces cannot be specified for Service name.

This value is applied to ODBC data source name in the dialog boxes listed below. If you change the value after creating a new asset management database, re-create the data source.

Basic Database Settings dialog box

Dialog box for creating a data source

(3) Number of concurrent connections

Number of concurrent connections specifies the number of connections that can be established with the database at the same time.

Specification of this item is optional.

Permitted value

1 to 64. The default is 20. Specify a value that is greater than the value of Number of connections for search in Database Information.

(4) Number of connections for search

Number of connections for search specifies the number of concurrent connections that can be established by transactions that use the database for an extended period of time. By specifying this setting, you can prevent the database from being locked by a long-running transaction such as a search request.

Specification of this item is optional.

Permitted value

1 to 64. The default is 5. The value of this item must be less than the value of Number of concurrent connections in Database Information.

(5) Case sensitivity in LIKE searches

Case sensitivity in LIKE searches specifies whether the search is to be case-sensitive when searching for a partial match, including a leading or trailing match.

Permitted value

Case sensitive (default)

The search is case-sensitive.

Case insensitive

The search is not case-sensitive.

7.3.3 Setting Session Information

Session Information specifies the forced logout time and the number of users that can be logged in concurrently.

This section describes the settings for Session Information.

(1) Communication-less monitoring time

Communication-less monitoring time specifies the length of time before the session is forcibly logged out if no action is requested from the Web browser.

Specification of this item is optional.

Permitted value

5 to 2,880 minutes. The default is 60 minutes.

(2) Number of concurrent user logins

Number of concurrent user logins specifies the number of logged-in users that can use Asset Console concurrently.

This setting is mandatory.

Permitted value

1-100,000. The default is 300.

7.3.4 Setting Basic Information

Basic Information specifies information such as the items that are displayed in windows and the maximum values during operation.

This section describes the settings for Basic Information.

(1) Show PDF button

Show PDF button specifies whether to link with EUR and use the PDF button to display PDF files.

Specify Show to link Asset Console with EUR.

Permitted value

Show (Default)

Display the PDF button.

Hide

Do not display the PDF button.

(2) Time-out time for PDF file creation

Time-out time for PDF file creation specifies the time until creation of a PDF file (by linkage with EUR) must finish. If creation of a PDF file exceeds the specified time, it will be canceled.

If 0 is set for this item, PDF file creation basically continues until it finishes.

However, if the processing takes longer than the timeout time of the Web browser waiting for the response, connection to the Web browser will be disconnected, and creation of the PDF file might stop.

Specification of this item can be omitted.

Permitted value

0 to 99,999 seconds. The default is 300 seconds.

(3) Number of result lines to display

Number of result lines to display specifies the number of items to be listed as search results in a window. This setting is applicable to windows in which search results are not divided into pages. For the names of windows whose search results are divided into pages, see Asset-Console-installation-folder\help\ScreenWithPage.pdf. This setting is applicable to all windows not listed in ScreenWithPage.pdf.

Specification of this item is optional.

Permitted value

1 to 1,000 items. The default is 200 items.

(4) Show number column

Show number column specifies whether to display the Display nnnn results per page column on the window. This specifies the number of search results to display per page. This setting is applicable to windows used to execute searches and that divide the search results into pages. For the names of windows whose search results are divided into pages, see Asset-Console-installation-folder\help\ScreenWithPage.pdf.

Permitted value

Show (default)

Display the Display nnnn results per page column.

Hide

Do not display the Display nnnn results per page column. The number of search results that displays per page becomes the number specified in the Server Setup dialog box, Basic Information, Number of search results displayed on a page.

(5) Number of search results displayed on a page

Number of search results displayed on a page specifies the number of search results to be displayed per page on a window. This setting is applicable to windows in which search results are divided into pages. For the names of windows whose search results are divided into pages, see Asset-Console-installation-folder\help\ScreenWithPage.pdf.

Specification of this item can be omitted.

Permitted value

1 to 1,000 items. The default is 200 items.

(6) Trash group ID for deletions

When a group is deleted, a group called Trash is created automatically in order to save temporarily the user information that was registered for the deleted group. Trash group ID for deletions specifies the group ID for Trash.

Specification of this item is optional.

Permitted value

Between 0 and 64 alphanumeric characters. The default is 99999999.

(7) Trash location ID for deletions

When a location is deleted, a location called Trash is created automatically to save the deleted location temporarily. Trash location ID for deletions specifies the location ID for Trash.

The setting for this item can be omitted.

Permitted value

Between 0 and 64 alphanumeric characters. The default is 99999999.

(8) Threshold for license excess

Threshold for license excess specifies the threshold value for sending a warning about software being used in excess of its valid number of licenses. Express the threshold value as a percentage (%) of the valid licenses. For details about how to send a warning about software being used in excess of its valid number of licenses, see 7.9.1 Types of tasks.

If you use Task Scheduler to send email about excess licenses being used, make sure that this setting is specified.

Permitted value

0 to 100%. The default is 100%.

(9) Automatic login settings

In Automatic login settings, specify whether to display the Log in automatically from next time check box in the login window when referencing the Asset Console information from the following linkage products:

JP1/IM

JP1/Service Support

If you log in with Log in automatically from next time selected, the user ID and password do not need to be subsequently entered again on the login window during the period set for Number of days that cookies are effective.

Permitted value

Show (default)

Display the Log in automatically from next time check box.

Hide

Do not display the Log in automatically from next time check box.

(10) Number of days that cookies are effective

Number of days that cookies are effective specifies the number of days to save the user ID and password to enable automatic login the next time when referencing Asset Console information from the following linkage products:

JP1/IM

JP1/Service Support

Specification of this item is optional.

Permitted value

1 to 365 days. The default is 14 days.

(11) Settings for a group that uses a group-specific IP group

Settings for a group that uses a group-specific IP group specifies whether to set up IP address-specific groups that are using devices. To register IP address-specific groups, use the IP Group job menu. Groups are set according to the IP addresses of the hardware asset information.

This setting is enabled when you execute the Data maintenance (Asset Console) task. To enable the setting when executing the Data maintenance (Asset Console) task, you must modify the settings file (taskopt.ini). For details about how to modify the settings file, see 7.9.3(3) Changing the tasks to be executed.

Permitted value

Do not set (default)

Does not set up an IP address-specific device group.

Set

Sets up an IP address-specific device group. Even if a value is already specified, it is overwritten with the new group-specific IP group value.

Specify this value if you need to update groups according to the setting in the IP Group job menu.

To only set a location that has not been set

Sets up an IP address-specific location only when no device location has been registered.

Specify this option mainly when you need to set up a location for a newly registered device.

Note

Even when Set is selected, the existing value is not overwritten if it is a value acquired from the JP1/IT Desktop Management 2 - Manager management information or a value entered from the New Device window or the Device Details dialog box. Therefore, to set location-specific IP groups for all devices, first use the Batch Update job menu to delete the values for all locations. Also make sure that Overwrite setting for asset-information.location-name in the ITDM2 management information acquisition job menu is set to Overwrite (Do not overwrite when there is no data.).

Note

You can use the Data maintenance (Asset Console) task to reliably update the locations according to the settings in the IP Group job menu, even when a value acquired from the JP1/IT Desktop Management 2 - Manager management information or a value entered from the New Device window or the Device Details dialog box is set. For details about how to set the Data maintenance (Asset Console) task, see 7.9.3 Specifying the task to be executed in the Data maintenance (Asset Console) task.

(12) Settings for a location that uses a location-specific IP group

Settings for a location that uses a location-specific IP group specifies whether to set up IP address-specific locations as device locations. To register IP address-specific locations, use the IP Group job menu. Locations are set according to the IP addresses of the hardware asset information.

This setting is enabled when you execute the Data maintenance (Asset Console) task. To enable the setting when executing the Data maintenance (Asset Console) task, you must modify the settings file (taskopt.ini). For details about how to modify the settings file, see 7.9.3(3) Changing the tasks to be executed.

Permitted value

Do not set (default)

Does not set up an IP address-specific device location.

Set

Sets up an IP address-specific location as the device location. Even if a value is already specified, it is overwritten with the new location-specific IP group value.

Specify this value if you need to update locations according to the setting in the IP Group job menu.

To only set a location that has not been set

Sets up an IP address-specific location only when no device location has been registered.

Specify this option mainly when you need to set up a location for a newly registered device.

Note

Even when Set is selected, the existing value is not overwritten if it is a value acquired from the JP1/IT Desktop Management 2 - Manager management information or a value entered from the New Device window or the Device Details dialog box. Therefore, to set location-specific IP groups for all devices, first use the Batch Update job menu to delete the values for all locations. Also make sure that Overwrite setting for asset-information.location-name in the ITDM2 management information acquisition job menu is set to Overwrite (Do not overwrite when there is no data.).

Note

You can use the Data maintenance (Asset Console) task to reliably update the locations according to the settings in the IP Group job menu, even when a value acquired from the JP1/IT Desktop Management 2 - Manager management information or a value entered from the New Device window or the Device Details dialog box is set. For details about how to set the Data maintenance (Asset Console) task, see 7.9.3 Specifying the task to be executed in the Data maintenance (Asset Console) task.

(13) Acquisition of DHCP address update log

Acquisition of DHCP address update log specifies whether log information about a change to the IP address allocated by DHCP is to be acquired in the change logs that are acquired when a device's IP address is changed.

Permitted value

Acquire

Acquires all changes to device's IP address as change log.

Do not acquire (default)

Does not acquire a change to the IP address allocated by DHCP. In the case of the addition or deletion of a MAC address resulting from the addition or deletion of a network card, the change log is acquired even if this operation is selected.

The device is treated as using the DHCP server when one of the following is true:

The network information set for the corresponding device contains DHCP server name.

The IP address is included in the range of IP addresses that has been defined as DHCP operation group in the IP Group job menu.

The IP address has been assigned to the MAC address of a device for which DHCP is enabled in the management information acquired from JP1/IT Desktop Management 2 - Manager.

(14) Sort key for the group-specific tree display

In Sort key for the group-specific tree display, specify the key for sorting the group names displayed in the group-specific tree or group list from the group information (GroupInfo) property. This sort key is applied to the following windows and dialog boxes:

Each operation window (simple search condition)

Browse Groups dialog box

Division group in the Browse Groups dialog box (list)

Browse Users dialog box

Substitute Settings dialog box

Register Divisions dialog box

Refresh Divisions dialog box

Assign Divisions dialog box

Select Destination dialog box

Permitted values

Group ID

Group name

Group name (English)

Group (default)

User property field 128-1

User property field 128-2

User property field 255-1

User property field 255-2

(15) Acquisition of contract history

Acquisition of contract history specifies whether to manage the registered content of the contract information as contract history.

Permitted value

Acquire

Acquires contract history when a contract is being registered in the new contract registration window or when contract information is being updated in the Contract Details dialog box. When updating contract information in the Contract Details dialog box, you can choose whether to register the information as contract history. You can also use the History Information button displayed in the Contract Details dialog box to view the history information.

Do not acquire (default)

Does not acquire contract history even when contract information is registered or updated. The History Information button is not displayed in the Contract Details dialog box, either.

(16) Display substitute items by default

Display substitute items by default specifies whether substitute Items are displayed by default, by setting the default status of the Display substitute items as well check box in the Inbox window.

Permitted value

Show

Displays substitute Items by default when the Inbox window is displayed.

Hide (default)

Hides substitute Items by default when the Inbox window is displayed.

(17) Create new Item from Item outbox

Create new Item from Item outbox specifies whether to allow an Item to be created by copying an existing one.

Permitted value

Create

The Copy and Create New button is displayed in the Outbox window in the Outbox job menu and the Item window that is displayed when you click the Item name anchor in Outbox. As a result, you can copy and create a new Item.

Do not create (default)

The Copy and Create New button is not displayed.

(18) Status to display in device search windows

In Status to display in device search windows, specify the device status to be displayed for the Status search condition in the Device Totals, Device List, and Add Related Device windows.

Permitted value

Display only active codes (default)

Displays the statuses whose codes are in the range from 0 to 499. By default, Active and Stock are displayed.

Display all codes

Displays the statuses whose codes are in the range from 0 to 999. By default, Active, Stock, Restore, Scrap, Pre-Scrap, and Erase are displayed.

(19) Device log management

In Device log management, specify whether to manage the initial device change log of the management-target device. Hitachi recommends that you select Do not manage if you want to improve the performance of importing management information from JP1/IT Desktop Management 2 - Manager.

Permitted value

Manage

When you execute the Delete change log (Asset Console) task, the initial device change log is saved.

Do not manage (default)

When you execute the Delete change log (Asset Console) task, the initial device change log is deleted.

(20) Audit log entry output

In Audit log entry output, specify whether to output audit log entries.

Permitted value

Do not output audit log entries (default)

Audit log entries are not output.

Output audit log entries

Audit log entries are output to the folder specified in Audit log entry output folder.

(21) Audit log entry output folder

Audit log entry output folder specifies the folder to which audit log entries are to be output.

Permitted value

From 3 to 240 bytes of characters. The following symbols cannot be used:

#, /, ,, ;, *, ?, ", <, >, |

Specify a full path for the folder.

The default is the Asset-Console-installation-folder\auditlog.

7.3.5 Setting Mail Notification Information

Mail Notification Information specifies whether you wish to have Task Scheduler use email to report on asset status. If so, you can specify the report recipient's email address. For details about setting the tasks registered in Task Scheduler, see 7.9 Setting the tasks that are registered in Task Scheduler.

Also specifies whether to send an email notification to a user who is set up as an Item agent when an Item is executed. For details about setting up an Item agent, see 15.2.2 Specifying a substitute.

This section describes the settings for Mail Notification Information.

(1) Notification by e-mail

Notification by e-mail specifies whether you wish to have Task Scheduler automatically send an email notification.

To send an email notification, specify Notify.

Permitted value

Notify

Sends an email notification.

Do not notify (default)

Does not send an email notification.

(2) Email notification to Item agents

When an Item agent is set up, Email notification to Item agents specifies whether to send an email notification to the Item agent.

To send an email notification, specify Email. In this case, the user who is set up as the Item agent receives a copy of the notification (CC).

Permitted value

Email

Sends email notifications also to the Item agent.

Do not email (default)

Does not send email notifications to the Item agent.

(3) Address to e-mail

Address to e-mail specifies the destination address when you wish to send email notification of the execution results of a task registered in the Task Scheduler. To specify multiple destination addresses, use commas (,) as the delimiter.

If you wish email notification to be sent, make sure that you specify this item.

Permitted value

String of 5-160 alphanumeric characters, the underscore (_), hyphen (-), and

period (.), delimited by the at mark (@). The default is a space.

(4) Sender's e-mail address

Sender's e-mail address specifies the sender's address when you wish to send email notification of the execution results of a task registered in the Task Scheduler. To specify multiple sender's addresses, use commas (,) as the delimiter.

Permitted value

String of 5-160 alphanumeric characters, the underscore (_), hyphen (-), and

period (.), delimited by the at mark (@). The default is manager@asset.message.

7.3.6 Setting Link with Directory Server

Link with Directory Server specifies the server name, port number, or other information necessary for authenticating login by linking with a directory server. It also specifies the type of character encoding that is used by the directory server when an access definition file is created to link with the directory server.

Link with Directory Server specifies the following items:

(1) Directory server usage

In Directory server usage, specify whether to use a directory server for login authentication.

To use a directory server for login authentication, select Use for authentication only.

Permitted value

Use for authentication only

Uses a directory server for login authentication.

Do not use (default)

Does not use a directory server for login authentication.

(2) Code set

In Code set, specify the type of character encoding to be used. You must specify this item if you are creating an access definition file to link with a directory server.

Permitted value

SHIFT-JIS

Sets SHIFT-JIS encoding.

UTF-8 (default)

Sets UTF-8 encoding.

(3) Server name

Server name specifies the host name or IP address of the directory server. You must specify this item if you plan to perform login authentication by linking with a directory server.

Permitted value

The permitted value is 1 to 255 bytes of alphanumeric characters and symbols. The default is AssetHost.

(4) Port number

Port number specifies the port number of the directory server. You must specify this item if you plan to perform login authentication by linking with a directory server.

Permitted value

A value between 1 and 65,535. The default is 389.

(5) Access user

Access user specifies the DN of the user who will access the directory server's information entries. You must specify this item if you plan to perform login authentication by linking with a directory server.

You must execute the LDIFDE command of Active Directory in advance and output a user information list to investigate the DN of the user whom you wish to use as an access user. For details about the investigation method, see 5.5.1 Login authentication.

Additionally, specify a password in the Set Password dialog box.

Permitted value

The permitted value for an access user is 1 to 255 bytes of alphanumeric characters, symbols, and kanji characters. By default, this item is left blank.

The permitted value for a password is 1 to 255 bytes of alphanumeric characters, symbols ,and single-byte katakana characters. By default, this item is left blank.

(6) Response monitoring time

Response monitoring time specifies the time in seconds to monitor for the directory server to respond to a search request. If the directory server does not return a response within the monitoring time, a communication error is considered to have occurred and the processing is terminated. If a large number of processes use the directory server service and communication errors occur frequently during login authentication, specify a large value for the monitoring time. You must specify this item if you plan to perform login authentication by linking with a directory server.

Permitted value

The permitted value is 1 to 65,535 seconds. The default is 60 seconds.

(7) User information DN

User information DN specifies the DN that becomes the basis for user information search. You must specify this item if you plan to perform login authentication by linking with a directory server.

You must execute the LDIFDE command of Active Directory in advance and output a user information list to investigate the DN of the organization from which to search for users during Asset Console login authentication. For details about the investigation method, see 5.5.1 Login authentication.

Permitted value

The permitted value is 1 to 255 bytes of alphanumeric characters , single-byte katakana characters, symbols, and kanji characters. The default is ou=people,o=xxxxxxx.com.

(8) User ID attribute name

User ID attribute name specifies the attribute name of the user information to be used as the user ID for logging in to Asset Console. You must specify this item if you plan to perform login authentication by linking with a directory server.

You must execute the LDIFDE command of Active Directory in advance and output a user information list to investigate the attribute name of the user ID to be used during Asset Console login authentication. For details about the investigation method, see 5.5.1 Login authentication.

Permitted value

The permitted value for a user ID attribute name is 1 to 255 bytes of alphanumeric characters, symbols, single-byte katakana characters, and kanji characters. The default is uid.

Note that an attribute called uid is not provided in the directory server's standard user object. Therefore, add the uid attribute to the directory server's user object as needed and specify the user ID to be used for login authentication. Alternatively, instead of uid, specify an attribute name under which a user ID to be used for Asset Console login authentication is stored.

(9) User name attribute name

User name attribute name specifies the attribute name of the user information to be used as the Asset Console user name.

You must execute the LDIFDE command of Active Directory in advance and output a user information list to investigate the attribute name to be used as the Asset Console user name. For details about the investigation method, see 5.5.1 Login authentication.

Permitted value

The permitted value for a user ID attribute name is 1 to 255 bytes of alphanumeric characters, symbols, single-byte katakana characters, and kanji characters. The default is cn.

7.3.7 Setting JP1/IT Desktop Management 2 - Manager management information acquisition

ITDM2 linkage specifies the login ID and service name that are used to collect management information by linking with JP1/IT Desktop Management 2 - Manager. This setting is required only when you link Asset Console with JP1/IT Desktop Management 2 - Manager. For ITDM2 linkage, enter the values set in the JP1/IT Desktop Management 2 - Manager setup window.

The following items can be set in ITDM2 linkage.

(1) JP1/ITDM2-Manager database login ID

JP1/ITDM2-Manager database login ID specifies the login ID to be used to connect to the JP1/IT Desktop Management 2 - Manager database.

Specify the password in the Set Password dialog box.

If you are linking JP1/IT Desktop Management 2 - Manager, this setting must be specified. The value cannot be left blank even when JP1/IT Desktop Management 2 - Manager is not linked.

Permitted value

From 1 to 28 bytes of characters (JP1/ITDM2-Manager database login ID and password). By default, both JP1/ITDM2-Manager database login ID and the password is itdm2m.

The values for JP1/ITDM2-Manager database login ID and the password must begin with alphabetical characters.

The values specified here are applied to Connection user ID in the dialog box used for creating a data source.

(2) Name of the service connecting to the JP1/ITDM2-Manager database

Name of the service connecting to the JP1/ITDM2-Manager database specifies the service name to be used to connect to the P1/IT Desktop Management 2 - Manager database. Specify the ODBC data source name that is to be set at the JP1/IT Desktop Management 2 - Manager database connection setup. For details about setup of the database connection, see 7.5 Creating a data source.

If you will be linking JP1/IT Desktop Management 2 - Manager, this setting must be specified.

Permitted value

1 to 32 bytes of alphanumeric and special characters. The default is ITDM2_DB_SERVICE_NAME.

!, (, ), *, ,, ;, =, ?, @, [, ], {, }, and spaces cannot be specified for Name of the service connecting to the JP1/ITDM2-Manager database.

This value is applied to ODBC data source name in the dialog box used to create a data source

(3) Multiplex

Multiplex specifies the multiplex (the number of threads) for acquisition processing.

Permitted value

1 to 16. The default is 4.

7.4 Creating an asset management database

This section explains how to create an environment for an asset management database.

To create an environment for an asset management database, use the Database Manager dialog box. After you have created an asset management database, perform the following tasks:

Create an ODBC data source name

Create a database

Create a user for database access

Initialize the database

Hitachi recommends that you establish an asset management server environment after confirming the local database connection to avoid problems related to the database connection.

While Database Manager is running, do not execute other programs.

To create an asset management database:

Click the Start button and select Programs, JP1_IT Desktop Management 2 - Asset Console, and then Setup.

The Setup dialog box appears.

Click the Database Manager icon.

The following Database Manager dialog box appears.

Figure 7‒3: Database Manager dialog box

Select Create the database, and then click the Next button.

The dialog box used to set cluster system information appears.

Set the cluster system information.

Set the database connection information and database area.

Create a database.

The setting of cluster system information in step 4 and the setting of database connection information and database area in step 5 are described in section 7.4.1.

7.4.1 How to create an asset management database

To create an asset management database:

Specify necessary information in the dialog box for setting information about the cluster system.

To specify necessary information, use the following dialog box for setting cluster system information.

Figure 7‒4: Dialog box for setting cluster system information

If you do not use Asset Console in a cluster environment, do not specify anything here and go to step 2.

If you use Asset Console in a cluster environment, select the Used in cluster system environment check box. The following describes each item to be specified for both executing and standby databases.

For the executing database

Execution mode / Standby mode

Select Execution mode. By default this item is selected.

Logical host name

Specifies the name of a logical host created in the cluster system. The permitted value is 1 to 64 bytes of alphanumeric characters, double-byte characters, and %, -, and _.

For the standby database

Execution mode / Standby mode

Select Standby mode.

Logical host name

Specifies the name of a logical host created in the cluster system. The permitted value is 1 to 64 bytes of alphanumeric characters, double-byte characters, and %, -, and _.

Execution system host name

Specifies the name of an executing host created in the cluster system. The permitted value is 1 to 64 bytes of alphanumeric characters, double-byte characters, and %, -, and _.

For details about how to rename logical hosts, see F.3 Renaming the host. For details about how to rename the executing host, see 7.12.6(1)(b) How to rename the executing host.

Click the Next button.

The following Basic Database Settings dialog box appears.

Figure 7‒5: Basic Database Settings dialog box

In the Basic Database Settings dialog box, specify Port number.

The following describes each item in the dialog box.

Port number

Specify the port number of the database server to be connected. Specify a port number that is not used as an integer from 5001 to 65535. By default, 31022 is specified.

ODBC data source name

Displays the value specified for Service name in the Server Setup dialog box. This item cannot be changed.

Connection user ID

Displays the value specified for Login ID in the Server Setup dialog box. This item cannot be changed.

Click the Next button.

The following Detailed Database Settings dialog box appears.

Figure 7‒6: Detailed Database Settings dialog box

Specify Storage folder name and Size.

The following describes each item in the dialog box.

Storage folder name

In Storage folder name, specify the name of the folder for storing the database. Clicking the ... button displays a dialog box in which you can browse folders and specify a desired folder name. The permitted value is 1 to 125 bytes of alphanumeric characters and _, \, :, ., (, ), and the space.

By default, Asset Console-installation-folder\db is specified.

If you use Database Manager to specify the path, do not specify a device name such as CON or NUL.

Size

Specifies the maximum size of the database. By default, the estimated value obtained in the Estimate Capacity dialog box is specified. Specify 100 or a greater integer.

If the Automatically increase size check box is selected, the initial value of the database is used as the maximum size. Specify an integer between 100 and 65,535.

Estimate Capacity button

Enables you to estimate the database capacity. The estimated value is reflected in Size. For details about how to estimate the database capacity, see 7.4.2 Estimating the database capacity.

Automatically increase size

Select this checkbox to set the database to automatically increase in size. By default, this check box is cleared. If this check box is selected, the database size is automatically increased to a maximum value of 65,535 megabytes.

Management area

Displays the size required for the management area. This item cannot be changed.

Operation area

Displays the size that is automatically allocated under the Asset Console installation folder when the database is running. This item cannot be changed.

Click the Create button.

The asset management database is created. When database creation is completed, a message indicating the completion of setup is displayed and the Database Manager dialog box closes. If database creation fails, a message to that effect is displayed, in which case, take an appropriate action according to the displayed message.

For the temporary area of the database, use an area other than the data area. If you specify the same table area for the temporary area and the data area, search and deletion will not be available if the table area is insufficient.

Important

If one of the following messages is output while you are creating a database by using the database manager, check and correct the specified folder name, size, and port number, and then try again:

KFPX29616-E Errors occurred in creation of HiRDB file system

KFPX29617-E Errors occurred in Initialization of system file

KFPX29618-E Errors occurred in Initialization of database

KFPX29620-E Errors occurred in creation of temprary file

7.4.2 Estimating the database capacity

You can estimate the database capacity using the Estimate Capacity dialog box that is displayed by clicking the Estimate Capacity button in the Detailed Database Settings dialog box. The following figure shows the Estimate Capacity dialog box.

Figure 7‒7: Estimate Capacity dialog box

To estimate the database capacity and apply the obtained value to the Detailed Database Settings dialog box:

In Registration Items under Scale of operations, specify the number of items to be registered for each type of information.

Select information from the list in Scale of operations and then specify the number of items to be registered. In Estimated Sizes [MB] under Estimated capacity requirements; capacity is estimated in megabytes. For details about the formula for estimating the capacity, see D.2(1) Disk space required for the asset management database. To reset information to the default value for a selected item, click the Default button.

Click the Apply button.

The estimated value is applied to the Detailed Database Settings dialog box. To save the registered information and registration items displayed in Scale of operations, click the Save button.

Click the Close button.

The Estimate Capacity dialog box closes.

7.5 Creating a data source

To link to JP1/IT Desktop Management 2 - Manager, you must create a data source in order to connect to the database used in JP1/IT Desktop Management 2 - Manager. You must also re-create the data source if you have changed Login ID or Service name in the Server Setup dialog box after creating the asset management database.

Before creating the data source, you must use the Asset Console's Server Setup dialog box to specify the settings required during creation of the data source. For details about the settings in the Server Setup dialog box, see 7.3 Setting up the asset management server.

Notes

Before you start creating a data source, stop all Asset Console services, commands, and tasks in the following order:

World Wide Web Publishing Service or World Wide Web Publishing

Asset Console commands, and tasks

To run Asset Console after having created a data source, start the services in the reverse of the order in which they were stopped.

If a connection pool is set in an ODBC data source, the connected state will continue after an Asset Console job is stopped until the timeout time set in the connection pool expires. Therefore, wait for the connected state to be released before creating a data source.

Before you start creating a data source, use the following method to set up the database connection:

From the Windows Start menu, select Run. Specify %windir%\syswow64\odbcad32.exe and execute it.

To connect to the asset management database and a linked product's database:

Click the Start button and select Programs, JP1_IT Desktop Management 2 - Asset Console, and then Setup.

The Setup dialog box appears.

Click the Create Data Source icon.

The Create Data Source dialog box appears.

From Products for connection, select the name of the database product to be connected and then click the Next button.

A dialog box for creating a data source appears.

Enter the required items and then click the OK button.

Details about the settings during data source creation are provided in section 7.5.1.

The data source is created and the asset management database and linked product's database can now be connected.

7.5.1  Creating a data source

To create a data source, specify information about the database to be connected.

The following shows the dialog box for creating a data source.

Figure 7‒8: Dialog box for creating a data source

To return to the list of connection targets, click the Back button.

To create a data source:

In the dialog box for creating a data source, specify Server and Port number.

The following describes each item in the dialog box.

Server

Specifies the host name of the database to be connected. The permitted value is 1 to 63 bytes of alphanumeric characters, double-byte characters, and %, ~, -, _, ., /, and \. If the connection target is Asset Console, localhost is specified by default. For JP1/IT Desktop Management 2 - Manager, a space is specified by default.

Port number

Specify the port number of the database server to be connected. Specify an integer from 5001 to 65535. By default, 31022 is specified if the connection target is Asset Console and 31010 if the connection target is JP1/IT Desktop Management 2 - Manager.

ODBC data source name

Displays the value specified in the Server Setup dialog box. This item cannot be changed. The displayed value depends on the product selected in Products for connection. The following table shows the items in the Server Setup dialog box that correspond to the selected product.

Table 7‒1: Items in the Server Setup dialog box that correspond to the selected product (ODBC data source name)

Selected product

Item in the Server Setup dialog box

JP1/IT Desktop Management 2 - Asset Console

Service name

JP1/IT Desktop Management 2 - Manager

Connection service for ITDM2-Manager database

Connection user ID

Displays the value specified in the Server Setup dialog box. This item cannot be changed. The displayed value depends on the product selected in Products for connection. The following table shows the items in the Server Setup dialog box that correspond to the selected product.

Table 7‒2: Items in the Server Setup dialog box that correspond to the selected product (connection user ID)

Selected product

Item in the Server Setup dialog box

JP1/IT Desktop Management 2 - Asset Console

Login ID

JP1/IT Desktop Management 2 - Manager

ITDM2-Manager database login ID

Click the OK button.

The data source is created according to the specified settings. When the data source creation is completed, a message to that effect is displayed.

Click the OK button.

The dialog box for creating a data source is closed and the list of connection targets is displayed again.

7.6 Setting a virtual directory

In Microsoft Internet Information Services, set Asset Console's virtual directory. You can change the path specified during the installation of Asset Console. You can also specify a website other than the Default Web Site that is set in Microsoft Internet Information Services during the installation of Asset Console. You can also create and change an application pool.

To change Asset Console's virtual directory and create and change an application pool:

Click the Start button and select Programs, JP1_IT Desktop Management 2 - Asset Console, and then Setup.

The Setup dialog box appears.

Click the Virtual Directory Settings icon.

The following Virtual Directory Settings dialog box appears.

Figure 7‒9: Virtual Directory Settings dialog box

In the Virtual Directory Settings dialog box, specify the necessary information.

The following describes each item.

Web site

Specifies the website at which the asset management server's virtual directory is to be registered. Select a website from the drop-down list. By default, the website displaying Asset Console's virtual directory is specified. If no virtual directory has been registered, Default Web Site is specified. If no website has been registered, a space is specified.

Application pool

Specifies the application pool that is to be associated with the asset management server's virtual directory. Select an application pool from the combo box. To create a new application pool, enter the name of the application pool in the input field. The permitted value is 1 to 255 bytes of characters. Note that /, \, =, :, and , cannot be specified. By default, the application pool associated with Asset Console's virtual directory is displayed.

If the name of an application pool registered by the Internet Information Service Manager contains =, :, or ,, the application pool is not displayed in the combo box.

Click the OK button.

The virtual directory is changed or the application pool is created or changed according to the specified information. When the processing is completed, a message indicating completion of virtual directory setting is displayed.

The application pool created here is the same as when an application pool is created from Microsoft Internet Information Services. Therefore, there is no need to re-create the application pool from Microsoft Internet Information Services.

For details about the operation that is executed during application pool creation, see 7.8.1(3) Creating application pools.

Click the OK button.

The Virtual Directory Settings dialog box closes.

7.7 Setting up the services to be used by the asset management server

The asset management server uses the following services:

IIS Admin Services

World Wide Web Publishing Service or World Wide Web Publishing

Simple Mail Transport Protocol (SMTP)

This service is required if it is necessary to notify the asset manager by email about the execution results of the tasks registered in Windows Task Scheduler, or to notify the next worker by email when an Item has been sent.

The services to be used by the asset management server must be set to start automatically.

To set Asset Console to start automatically:

In the Service window, select the service to be used by the asset management server.

From the menu, select Action and then Property.

The Property dialog box opens.

On the General tab, change Startup type to Automatic.

Click the OK button.

The Property dialog box closes, and the service is set to start automatically.

Start the service.

7.8 Settings for using Microsoft Internet Information Services

This section describes notes and required settings when Asset Console is installed when Microsoft Internet Information Services is used.

7.8.1 Setting the Web server

This subsection describes the settings that are required when Asset Console is installed. It also provides notes that are applicable if you are using Microsoft Internet Information Services 7.5, 8.0, or 8.5.

(1) Installing the role services

If you are using Microsoft Internet Information Services 7.5, 8.0, or 8.5, you must install the appropriate role services.

To install the role services for Microsoft Internet Information Services 7.5, 8.0, or 8.5:

In the Server Manager window, select Roles and then Add Roles Service.

A dialog box for selecting role services is displayed.

Select the role services according to the purpose for which they are needed, and then click the Next button.

A dialog box confirming the installation options is displayed.

The following table lists and describes the role services that can be selected when the asset management server is configured.

Table 7‒3: Role services that can be selected when the asset management server is configured

Item

Role service

Asset management server

Common HTTP Features

Static Content

S

Default Document

S

Directory Browse

S

HTTP Errors

S

Application Development

ASP.NET

--

ISAPI Extensions

S

ISAPI Filters

S

Performance

Static Content Compression

S

IIS Management Console

IIS Management Console

S

IIS 6 Management Compatibility

IIS 6 Metabase Compatibility

S

IIS Management Console

S#

Legend:

S: Role service whose selection is required.

--: Not applicable.

#: Selection is required only when the email notification function is used.

Make sure that the role services selected in step 2 are displayed, and then click the Install button.

When installation is completed, a dialog box reporting the installation result is displayed.

Click the Close button.

(2) Registering the extensions of the files to be uploaded

Register in Internet Information Service Manager the information related to the extensions of the files to be uploaded as file attachments into each window operation or Item.

To register the information related to file extensions:

Start Internet Information Service Manager.

From the asset management server's Sites, select Default Web Site, jp1asset, and then MIME types.

From the Action menu, select Add.

The Add MIME type dialog box appears.

Register the extension and MIME type to be used and click the OK button.

For details about MIME types, see Help in Internet Information Service Manager.

(3) Creating application pools

You need to set up an application pool in Internet Information Service Manager.

To create an application pool:

Start Internet Information Service Manager.

Select Application Pools on the asset management server.

From the Action menu, select Add Application Pool.

The Add Application Pool dialog box appears.

In Name, enter a desired application pool name, set Managed pipeline mode to Classic, and then click the OK button.

Do not include =, :, or , in the application pool name. If these characters are used, the application pool name will not be displayed in the combo box in the Virtual Directory Settings dialog box.

Select the newly created application pool, and then select Advanced Settings from the Action menu.

The Advanced Settings dialog box appears.

Specify the required settings, and then click the OK button.

In the Advanced Settings dialog box, specify the following settings. The other items can be set to the default value.

(General)

Queue Length: 4000

Enable 32-Bit Applications: True

Process Model

Identity: LocalSystem

Ping Enabled: False

Idle Time-out (minutes): 0

Rapid-Fail Protection

Enabled: False

Recycling

Isapi Reported Unhealthy: True

Manual Recycle: True

Specific Time: True

Application Pool Configuration Changed: True

Request Limit Exceeded: True

Disable Recycling for Configuration Changes: True

Regular Time Interval (minutes): 0

From the Action menu, select Recycling.

The Edit Application Pool Recycling Settings dialog box appears.

Clear all check boxes for the recycle conditions, and then click the Next button.

Of the recycling events that are to be logged, select the check boxes for the recycling events that you wish to be logged during recycling of the application pool, and then click the Finish button.

Hitachi recommends that you select all enabled check boxes. If there is any recycling event that you wish not to be logged during recycling of the application pool, clear its check box, and then click the Finish button.

Restart World Wide Web Publishing Service.

(4) Setting applications (virtual directories)

If you added the IIS 6 Metabase Compatibility role service after installing Asset Console, you must set applications (virtual directories) using Internet Information Service Manager.

To create new applications (virtual directories):

From the asset management server's Sites, select Default Web Site, and then from the right-click menu, select Add Application.

The Add Application dialog box appears.

Click the Select button and specify the application pool created in Application Pools.

In Physical path, specify the virtual directory for the asset management server, and then click the OK button.

The default virtual directory for the asset management server is Asset-Console-installation-folder\wwwroot.

To change the settings of existing applications (virtual directories):

From the asset management server's Sites, select Default Web Site, jp1asset, and then from the Action menu, select Advanced Settings.

The Advanced Settings dialog box appears.

Specify the created application pool in Application Pools and the asset management server's virtual directory in Physical path, and then click the OK button.

The default virtual directory for the asset management server is Asset-Console-installation-folder\wwwroot.

Notes

Set the application pool for both of the following sites, or create an application pool for the jp1asset site and then apply the settings to the following sites:

jp1asset site

Higher-order website above the jp1asset site

If there are higher-order websites, specify the application pool settings for use up to the top website.

Note that the specified settings affect any websites subordinate to the top website. If you find any problems, create the jp1asset site in a separate website.

(5) Setting ISAPI restrictions

If you added the IIS 6 Metabase Compatibility and ISAPI Extensions role services after you installed Asset Console, you must set ISAPI restrictions in Internet Information Service Manager.

To set ISAPI restrictions:

Select the asset management server, and then select ISAPI and CGI Restrictions.

From the Action menu, select Add.

The Add ISAPI or CGI Restriction dialog box appears.

In ISAPI or CGI path, specify the file path, select the Allow extension path to execute check box, and then click the OK button.

In ISAPI or CGI path, specify the path to the following files that have been stored in the asset management server's virtual directory:

jamwscript.dll

bin\jamlogin.dll

jamenter.dll

jamfile.dll

jamhtmlfile.dll

Repeat steps 1 through 3 to add all of these files.

The default virtual directory for the asset management server is Asset-Console-installation-folder\wwwroot.

(6) Setting ISAPI filters

If you added the IIS 6 Metabase Compatibility and ISAPI Filters role services after you installed Asset Console, you must specify the ISAPI filters settings in Internet Information Service Manager.

To specify the ISAPI filters settings:

From the asset management server's Sites, select Default Web Site, and then ISAPI Filters.

From the Action menu, select Add.

The Add ISAPI Filter dialog box appears.

Specify a filter name in Filter name and specify the file path in Executable, and then click the OK button.

In Executable, specify the path to bin\jamssessionfilter.dll that has been stored in the Asset Console installation folder.

(7) Setting handler mappings

If you added the IIS 6 Metabase Compatibility role service after you installed Asset Console, you must set handler mappings using Internet Information Service Manager.

To set handler mappings:

From the asset management server's Sites, select Default Web Site, jp1asset, and then Handler Mappings.

From the Action menu, select Edit Feature Permissions.

The Edit Feature Permissions dialog box appears.

Select all check boxes (Read, Script, and Execute), and then click the OK button.

(8) Specifying the directory browse settings

If you added the IIS 6 Metabase Compatibility and Directory Browse role services after you installed Asset Console, you must specify the directory browse settings in Internet Information Service Manager.

To specify the directory browse settings:

From the asset management server's Sites, select Default Web Site, jp1asset, log, and then Directory Browse.

From the Action menu, select enable.

(9) Adding an Asset Console site

If Microsoft Internet Information Services 7.5, 8.0, or 8.5 is used, you must add an Asset Console site in order to use Asset Console from Microsoft Internet Explorer. The same setting is also required when you need to view the Asset Console information from other program products such as JP1/IM.

To add the Asset Console site:

In Microsoft Internet Explorer, select Tools and then Internet Options.

The Internet Options dialog box opens.

On the Security tab, select the Local intranet icon and then click the Sites button.

In the displayed dialog box, add the Asset Console site and click the Close button.

(10) Notes on creating a site

If you use Microsoft Internet Information Services 7.5 and have installed Asset Console, do not create a site for recycling worker processes in the virtual directory that was specified in Web site in the Virtual Directory Settings dialog box. By default, Default Web Site is specified in Web site.

7.9 Setting the tasks that are registered in Task Scheduler

Asset Console enables you to use Windows Task Scheduler to automatically maintain and monitor asset information that is created by daily asset management jobs.

When you install Asset Console, tasks are created in Windows Task Scheduler. You can modify this task schedule and settings for enabling or disabling tasks as appropriate for how you handle asset information.

Note that when Asset Console is first installed, all tasks are disabled.

This section provides the details of the tasks and describes each task's setup procedure.

Notes

A user with administrator permissions must perform task scheduling.

When executing an Asset Console task, you must use the 32-bit command prompt. For the execution procedure, see Appendix G. Notes on Executing Asset Console Commands and Tasks.

Note

You can create tasks for executing unique processing in addition to the tasks that are created automatically when Asset Console is installed. To define the processing to be executed by a task, use an access definition file (file for defining processing using scripts provided by Asset Console). For details about creating an access definition file and adding tasks, see the JP1/IT Desktop Management 2 - Asset Console Creating an Access Definition File Guide.

7.9.1 Types of tasks

This section describes the tasks, the details of each task, and the default when each task is enabled that are set in Windows Task Scheduler.

(1) Name and details of each task

This subsection describes the name and details of each task. Do not change the files that are used by each task.

Data maintenance (Asset Console)

Updates information related to updated information in order to maintain conformity of data in the asset management database. This task also deletes unneeded information.

After setting up the asset management server, make sure that this task is enabled.

For details about how to specify the tasks to be executed in Data maintenance (Asset Console), see 7.9.3 Specifying the task to be executed in the Data maintenance (Asset Console) task.

The following table describes the return values for the Data maintenance (Asset Console) task.

Table 7‒4: Return values for the Data maintenance (Asset Console) task

Return value

Description

0x0

Normal termination

0x1

No applicable data was found.

0x2 or higher

Terminated with some other error.

Notification of invalid contract information (Asset Console)

Sends email notification to the asset manager concerning maintenance and lease contract information that is to expire within two months. The default is to send notification for contracts due to expire within two months. For details about how to specify the timing to send notification by email, see 7.9.4 Specifying the timing to send notification about impending contract expiration.

To send email notifications automatically, you need settings in both Asset Console and Microsoft Internet Information Services. For details about the setup procedure for email notification, see 7.10 Settings for using notification by email.

The following table describes the return values for the Notification of invalid contract information (Asset Console) task.

Table 7‒5: Return values for the Notification of invalid contract information (Asset Console) task

Return value

Description

0x0

Normal termination

0x1

No applicable data was found.

0x2 or higher

Terminated with some other error.

Notice of license excess (Asset Console)

Totals the number of licenses retained and the number of licenses being used in each group, and sends email notification of excess licenses if the number of licenses being used exceeds the number of licenses retained. If email notification is not required, use the Totals number of licenses (Asset Console) task. For details about how to specify the timing to delete the summation results, see 7.9.5 Specifying the timing to delete the license totaling results.

To send email notifications automatically, you need settings in both Asset Console and Microsoft Internet Information Services. For details about the setup procedure for email notification, see 7.10 Settings for using notification by email.

Note

If totaling is executed multiple times in a large system with several thousand devices, then a large amount of old totals results data remaining in the database will reduce the performance of totaling. In such environment, longer time is required for searches, additions, and deletions. If you have a large asset management system with several thousand devices, it is important to delete old totals results periodically.

The following table describes the return values for the Notice of license excess (Asset Console) task.

Table 7‒6: Return values for the Notice of license excess (Asset Console) task

Return value

Description

0x0

Normal termination

0x1

No applicable data was found.

0x2 or higher

Terminated with some other error.

Totals number of licenses (Asset Console)

Totals the number of licenses retained and the number of licenses being used in each group. No email notification is sent, even if the number of licenses being used exceeds the number of licenses retained.

If you want notification by email on exceeded licenses, use the Notice of license excess (Asset Console) task. Hitachi recommends that you do not use the Notice of license excess (Asset Console) task because this task takes time.

For details about how to specify the timing to delete the summation results, see 7.9.5 Specifying the timing to delete the license totaling results.

Note

If totaling is executed multiple times in a large system with several thousand devices, then a large amount of old totals results data remaining in the database will reduce the performance of totaling. In such environment, longer time is required for searches, additions, and deletions. If you have a large asset management system with several thousand devices, it is important to delete old totals results periodically.

The following table describes the return values for the Totals number of licenses (Asset Console) task.

Table 7‒7: Return values for the Totals number of licenses (Asset Console) task

Return value

Description

0x0

Normal termination

0x1

No applicable data was found.

0x2 or higher

Terminated with some other error.

Notification of unauthorized install (Asset Console)

Sends email notification to the asset manager concerning devices on which unauthorized software is installed.

To send email notifications automatically, you need settings in both Asset Console and Microsoft Internet Information Services. For details about the setup procedure for email notification, see 7.10 Settings for using notification by email.

The following table describes the return values for the Notification of unauthorized install (Asset Console) task.

Table 7‒8: Return values for the Notification of unauthorized install (Asset Console) task

Return value

Description

0x0

Normal termination

0x1

No applicable data was found.

0x2 or higher

Terminated with some other error.

Delete change log (Asset Console)

Deletes all logged information about maintenance, assets, and changes except for the information for a specified period.

In the default setting, the history information that is six months old or older will be deleted. For details about how to specify the history information to be deleted, see 7.9.6 Specifying the types of history information to be deleted and the deletion timing.

The following table describes the return values for the Delete change log (Asset Console) task.

Table 7‒9: Return values for the Delete change log (Asset Console) task

Return value

Description

0x0

Normal termination

0x1

No applicable data was found.

0x2 or higher

Terminated with some other error.

Acquisition of ITDM2 - Manager management information (Asset Console)

Loads JP1/IT Desktop Management 2 - Manager management information into the asset management database.

For details about the information that can be acquired as management information, see 19.1 Management information that can be acquired from JP1/IT Desktop Management 2 - Manager.

The following table describes the return values for the Acquisition of ITDM2 - Manager management information (Asset Console) task.

Table 7‒10: Return values for the Acquisition of ITDM2 - Manager management information (Asset Console) task

Return value

Description

0x0

Normal termination

0x1

No applicable data was found.

0xA

Stopped by user direction.

0x1F or higher

Terminated with some other error.

If an error occurs, check the message log related to JP1/IT Desktop Management 2 - Manager linkage (ASTINVn.LOG) for the cause and handling.

(2) Default settings for the tasks

The table below lists the default schedule settings that take effect when the various tasks are enabled.

Table 7‒11: Default settings when tasks are enabled

Task name

Default schedule setting

Data maintenance (Asset Console)

5:00 a.m. every day

Notification of invalid contract information (Asset Console)

6:00 a.m. on the first of every month

Notice of license excess (Asset Console)

5:30 a.m. every Monday

Totals number of licenses (Asset Console)

5:30 a.m. every Monday

Notification of unauthorized install (Asset Console)

5:30 a.m. every Tuesday

Delete change log (Asset Console)

6:00 a.m. on the first of every month

Acquisition of ITDM2 - Manager management information (Asset Console)

0:00 a.m. every day

Adjust the schedule so that multiple tasks are not executed concurrently.

7.9.2 Task setup procedure

This section describes the procedures for using Windows Task Scheduler to enable and disable tasks, change a task execution schedule, and delete tasks.

(1) Enabling a task

By default, all Asset Console tasks created in Windows Task Scheduler are disabled. To use a task, you must enable it. You can disable any task that you are not using.

In addition, to use a task, see Appendix G. Notes on Executing Asset Console Commands and Tasks.

To enable or disable a task registered in Task Scheduler:

Start Task Scheduler.

Select the task that you want to enable or disable.

From the Actions menu, select Enable.

To disable the task, select Disable.

The task is enabled or disabled. The result (return value) of task execution can be confirmed in Last Run Result in the list of tasks.

The table below shows the Run setting for each task.

The notations WINDOWS and INSTALL in the table correspond to the following folders:

INSTALL: Asset Console installation folder

WINDOWS: Windows installation folder

Table 7‒12: Run setting for each task

Task name

Run setting

Data maintenance (Asset Console)

"INSTALL\exe\jamscript.exe" -f "INSTALL\scriptbatch\DataMaintenance.txt"

Notification of invalid contract information (Asset Console)

"WINDOWS\system32\cscript.exe" "INSTALL\exe\jamexpiration.vbs"

Notice of license excess (Asset Console)

"WINDOWS\system32\cscript.exe" "INSTALL\exe\jamLicenseOver.vbs"

Totals number of licenses (Asset Console)

"WINDOWS\system32\cscript.exe" "INSTALL\exe\jamSoftwareAddUp.vbs"

Notification of unauthorized install (Asset Console)

"WINDOWS\system32\cscript.exe" "INSTALL\exe\jamPermitInstall.vbs"

Delete change log (Asset Console)

"INSTALL\exe\jamscript.exe" -f "INSTALL\scriptbatch\RemoveRecord.txt" -s TARGET=A -s MONTH=6

Acquisition of ITDM2 - Manager management information (Asset Console)

"INSTALL\exe\jamTakeITDM2Info.exe"

(2) Changing a task schedule

You can change a task's execution date and time. You can also add a schedule.

Changing the execution date and time

To change a task execution date and time:

Start Task Scheduler.

Select the task whose execution date and time are to be changed and display its properties.

The selected task's Properties dialog box appears.

On the Triggers tab, select the trigger to be changed and then click the Edit button.

Edit the settings of the trigger and then click the OK button.

The task is modified to the specified schedule.

Adding an execution schedule

To add a task execution schedule:

Start Task Scheduler.

Select the task for which a schedule is to be added and display its properties.

The selected task's Properties dialog box appears.

On the Triggers tab, click the New button.

The New Trigger dialog box appears.

Set a trigger.

Click the OK button.

A schedule is added to the task.

(3) Deleting a task

To delete an unneeded task:

Start Task Scheduler.

Select the task you wish to delete, and then from the Actions menu, select Delete.

The selected task is deleted.

(4) Task execution results

You can check the execution results (return values) of tasks in Last Run Result in the list of tasks that is displayed in Task Scheduler.

For details about the execution results, see ASTINVn.LOG (for the Acquisition of ITDM2 - Manager management information (Asset Console) task) or ASTMESn.log (for tasks other than the Acquisition of ITDM2 - Manager management information (Asset Console) task).

For the return values and their descriptions, see the description of each task in 7.9.1(1)Name and details of each task.

7.9.3 Specifying the task to be executed in the Data maintenance (Asset Console) task

You must enable this task immediately after you set up the asset management server.

When information is updated, the Data maintenance (Asset Console) task updates other related information and deletes unnecessary information to maintain data integrity in the asset management database. You can also select for execution only those tasks that are necessary from among the ones that can be executed. For details about how to select the tasks to execute, see 7.9.3(3) Changing the tasks to be executed.

When you execute the Data maintenance (Asset Console) task, Hitachi recommends that you stop all Asset Console services, commands, and tasks.

To stop Asset Console services, stop the following services in the listed order:

World Wide Web Publishing Service or World Wide Web Publishing

Asset Console commands and tasks

When you use Asset Console after having executed the Data maintenance (Asset Console) task, start the services in the reverse of the order in which they were stopped.

(1) Tasks to be executed in the Data maintenance (Asset Console) task

Use the Data maintenance (Asset Console) task to execute the following procedures:

Deleting asset information, contract information, and volume contract information in Erase status

When asset information is deleted, the following related information is also deleted:

Hardware information, software information, network information, installed software information, patch information, virus definition information, transfer logs, related asset information, device and key link, and user and key link

When contract information is deleted, the following types of related information are also deleted:

Maintenance contract information, lease contract information, rental contract information, volume contract information, contract history, and contract asset history

Deleting information related to asset information in Restore, Scrap, or Pre-Scrap status

The following information is deleted:

Installed software information, patch information, virus definition information, and network information#

The license key assigned to an asset is also released.

#: Only the IP address is deleted as network information.

Changing the group names, location names, and user names registered in the existing asset information according to the changes made to them in windows

This task reflects the group name, location, and user name changed in window operations onto the asset information and contract information, and a changed history is collected into a transfer log.

Setting the groups, locations, and user names corresponding to IDs in the asset information

If the asset information contains group IDs, location IDs, user IDs, administrator IDs, and administrator group IDs, but no corresponding groups, locations, user names, administrators, or administrator groups are set, the corresponding names are set.

Deleting unneeded IP address control information

The IP address control information of an unused IP address outside the range of IP group information is deleted.

Deleting installed software information for which no installed software name is registered

Deleting the association between the user and the software key information for licenses whose license category is not User license

Deleting the association between the hardware asset information and the software key information for licenses whose license category is not Install license

Combining the license count and the license keys if a transferred license has the same Group ID and Asset No. as an existing license

This operation targets licenses whose software status is Active.

Deleting the installed software information of the software whose management level is set to Unused

Deleting group- or location-specific IP groups from which the corresponding groups or locations have been deleted

Registering the group that corresponds to the IP address in the hardware asset information in Group in the asset information

For the correspondence between IP addresses and groups, the IP group settings created by the IP Group job menu are used. By default, this task is not set to be executed.

Registering the location that corresponds to the IP address in the hardware asset information in Location in the asset information

For the correspondence between IP addresses and locations, the IP group settings created by the IP Group job menu are used. By default, this task is not set to be executed.

Deleting file attachments that do not have corresponding information (hardware asset information, device catalog, contract information, contract history, volume contract, software asset information, or maintenance history)

Deleting related asset information that does not have target asset information

Deleting division information set for groups that no longer exist

(2) Specifying options

In the Data maintenance (Asset Console) task, you can use an option to specify and execute the processing in the [MAINTE_n] section described in the settings file (taskopt.ini).

To specify an option, display the task properties. On the Task tab, specify the option after the file name in Run.

Format

-s OPT=section-to-be-executed

For the section to be executed, specify a single alphanumeric character (0 to 9 or a to z) to indicate one of the [MAINTE_n] sections described in the taskopt.ini file. The section name is not case-sensitive.

Specification example

"C:\jp1asset\exe\jamscript.exe"

-f "C:\jp1asset\scriptbatch\DataMaintenance.txt" -dp

-s OPT=1

C:\jp1asset indicates the Asset Console installation folder.

(3) Changing the tasks to be executed

To change the task to be executed in the Data maintenance (Asset Console) task, describe the task to be changed in the settings file (taskopt.ini). Specify in different sections the tasks to be normally executed and those that are to be executed when options are specified.

The storage destination and the coding method for the settings file are described below.

Settings file storage destination

Asset-Console-installation-folder\env

A settings file sample file (taskopt.org) is provided in the above folder so that it can be referenced when creating a settings file. Modify the sample to create a settings file.

Settings file (taskopt.ini) coding method

Figure 7‒10: taskopt.ini coding method

[DATAMAINTENANCE]

Describe the variable name and specification value that correspond to the task to be changed.

To change the basic execution content of the Data maintenance (Asset Console) task, describe the change in this section. The content described here is enabled even when no option is specified. Even when an option is specified, the content described here is enabled if it does not overlap the processing in the section in which the option is specified.

Tasks not described in this section are executed according to the default settings.

[MAINTE_n]

Describe the variable name and specification value that correspond to the task to be changed.

To change the execution content of the Data maintenance (Asset Console) task to match various purposes, describe the changes in separate sections. Specify the section names using the [MAINTE_n] format. For n, specify a single alphanumeric character (0 to 9 or a to z). The section name is not case-sensitive. When specifying an option, you can select the execution content by specifying the character specified for n.

Tasks not described in this section are executed according to the settings in the [DATAMAINTENANCE] section.

The table below shows the variable names, processing content, specification values, and default values to be described for the individual sections. Variable names and default values are described in taskopt.org stored in the same folder as taskopt.ini.

Table 7‒13: Variable names to be specified in taskopt.ini

Processing content

Variable name

Specification value

Default

Deleting asset information and related information for devices in Erase status.

ASSET_ERASE_DEL

YES

Deletes.

NO

Does not delete.

YES

Deleting information related to devices in Restore, Scrap, or Pre-Scrap status.

ASSET_ASSOC_DEL

YES

Deletes.

NO

Does not delete.

YES

Deleting asset information and related information for software in Erase status.

SOFTINFO_ERASE_DEL

YES

Deletes.

NO

Does not delete.

YES

Deleting information related to software in Restore or Scrap status.

SOFTINFO_ASSOC_DEL

YES

Deletes.

NO

Does not delete.

YES

Deleting contract information in Erase status.

CONTRACT_ERASE_DEL

YES

Deletes.

NO

Does not delete.

YES

Deleting volume contract information in Erase status.

VOLUME_ERASE_DEL

YES

Deletes.

NO

Does not delete.

YES

Changing the user name registered in the existing asset information according to the user name changed in a window operation.

Setting the user name that corresponds to an ID in the asset information.

USER_ASSOC_UPD

YES

Updates.

NO

Does not update.

YES

Changing the group name registered in the existing asset information according to the group name changed in a window operation.

Setting the group name that corresponds to an ID in the asset information.

GROUP_ASSOC_UPD

YES

Updates.

NO

Does not update.

YES

Changing the location registered in the existing asset information according to the location changed in a window operation.

Setting the location that corresponds to an ID in the asset information.

LOCATION_ASSOC_UPD

YES

Updates.

NO

Does not update.

YES

Deleting unnecessary IP address management information.

IP_UNNECESSARY_DEL

YES

Deletes.

NO

Does not delete.

YES

Deleting installed software information for which no installed software name is registered.

INSTINFO_NOLIST_DEL

YES

Deletes.

NO

Does not delete.

YES

Deleting the association between the user and the software key information for licenses whose license category is not User license.

Deleting the association between the hardware asset information and the software key information for licenses whose license category is not Install license.

LICENSELINK_UNNECESSARY_DEL

YES

Deletes.

NO

Does not delete.

YES

Combining the license count and the license keys if a transferred license has the same Group ID and Asset No. as an existing license.

SOFTINFO_CONSOLIDATE

YES

Combines.

NO

Does not combine.

YES

Deleting the installed software information of the software whose management level is set to Unused.

INSTINFO_UNMANAGED_DEL

YES

Deletes.

NO

Does not delete.

YES

Deleting group- or location-specific IP groups from which the corresponding groups or locations have been deleted.

IPGROUP_NOOBJECT_DEL

YES

Deletes.

NO

Does not delete.

YES

Registering, in Group in the asset information, the group that corresponds to the IP address in the hardware asset information.

IP_GROUP_ASSOC

NO

Does not register.

OVERWRITE#

Always overwrites with the group assigned from the IP address.

YES

Follows Settings for a group that uses a group-specific IP group in the Server Setup dialog box.

NO

Registering, in Location in the asset information, the location that corresponds to the IP address in the hardware asset information.

IP_LOCATION_ASSOC

NO

Does not register.

OVERWRITE#

Always overwrites with the group assigned from the IP address.

YES

Follows Settings for a location that uses a location-specific IP group in the Server Setup dialog box.

NO

Deleting file attachments that do not have corresponding information.

ATTACHFILE_DEL

YES

Deletes.

NO

Does not delete.

YES

Deleting related asset information that does not have an asset ID of asset information that matches the child asset ID of the related asset information.

RELATION_NOOBJECT_DEL

YES

Deletes.

NO

Does not delete.

YES

Deleting division information set for groups that no longer exist.

DIVISIONINFO_NOOBJECT_DEL

YES

Deletes.

NO

Does not delete.

YES

#

Overwrites even when a value acquired from the JP1/IT Desktop Management 2 - Manager management information or a value entered in the New Device window or the Device Details dialog box is set. Specify this task when you want to update all group names and locations according to the setting in the IP Group job menu.

(4) Specification example of the tasks to be executed in the Data maintenance (Asset Console) task

In this example, only the necessary tasks are executed and the task execution interval is changed according to the task content of each task.

The following tasks are to be executed in the Data maintenance (Asset Console) task at the intervals described:

Only the tasks of deleting devices in Erase status, deleting software in Erase status, and deleting software in Restore or Scrap status are to be executed every day.

Only the task of deleting unnecessary IP addresses is executed once a week.

taskopt.ini specification:

[DATAMAINTENANCE]
ASSET_ERASE_DEL               = NO
ASSET_ASSOC_DEL               = NO
SOFTINFO_ERASE_DEL            = NO
SOFTINFO_ASSOC_DEL            = NO
CONTRACT_ERASE_DEL            = NO
VOLUME_ERASE_DEL              = NO
IP_UNNECESSARY_DEL            = NO
INSTINFO_NOLIST_DEL           = NO
LICENSELINK_UNNECESSARY_DEL   = NO
INSTINFO_UNMANAGED_DEL        = NO
USER_ASSOC_UPD                = NO
GROUP_ASSOC_UPD               = NO
LOCATION_ASSOC_UPD            = NO
SOFTINFO_CONSOLIDATE          = NO

[MAINTE_1]
ASSET_ERASE_DEL               = YES
SOFTINFO_ERASE_DEL            = YES
SOFTINFO_ASSOC_DEL            = YES

[MAINTE_2]
IP_UNNECESSARY_DEL            = YES

Option specification:

Specify the options for the Data maintenance (Asset Console) task as shown below. C:\jp1asset indicates the Asset Console installation folder.

"C:\jp1asset\exe\jamscript.exe"

-f "C:\jp1asset\scriptbatch\DataMaintenance.txt" -dp

-s OPT=1

Next, copy the Data maintenance (Asset Console) task and specify options as follows.

"C:\jp1asset\exe\jamscript.exe"

-f "C:\jp1asset\scriptbatch\DataMaintenance.txt" -dp

-s OPT=2

Make a change so that the added task is executed once a week. For the procedure for changing the task execution dates and frequency, see 7.9.2 Task setup procedure.

7.9.4 Specifying the timing to send notification about impending contract expiration

You can use the Notification of invalid contract information (Asset Console) task to specify when to send email notifications about impending expiration of maintenance, lease, and rental contracts.

Specify the notification timing in the format shown below after a file name in Run on the Task tab (Δ indicates a space).

ΔMONTH=(time-until-contract-expires)

Specify this time in months, in the range from 1 to 24.

If nothing is specified, an email notification is issued for all contracts due to expire within two months.

Specification example

This example specifies email notification for contracts due to expire within 12 months (1 year):

"C:\WINDOWS\system32\cscript.exe" "C:\jp1asset\exe\jamexpiration.vbs" MONTH=12

Here, C:\Windows refers to the Windows installation folder, and C:\jp1asset refers to the Asset Console installation folder.

7.9.5 Specifying the timing to delete the license totaling results

The results totaled by the Notice of license excess (Asset Console) and Totals number of licenses (Asset Console) tasks are saved the number of times specified. Older data is automatically deleted. You can change the number of summation results to be saved to a value of your choice. (The default is 10.)

Specify the number of totaling results to be saved, in the format shown below, after a file name in Run on the Task tab (Δ indicates a space).

ΔGENERATION=(number-of-totals-results-remaining)

Specify the number of remaining log information items, in the range from 0 to 120. If 0 is specified, nothing is deleted.

If nothing is specified, everything is deleted but the most recent 10 totals results.

Specification example

This example specifies that all but the most recent totals results are always to be deleted.

"C:\WINDOWS\system32\cscript.exe" "C:\jp1asset\exe\jamSoftwareAddUp.vbs" GENERATION=1

Here, C:\Windows refers to the Windows installation folder, and C:\jp1asset refers to the Asset Console installation folder.

7.9.6 Specifying the types of history information to be deleted and the deletion timing

This subsection describes how to specify the types of history information to be deleted and the deletion timing.

(1) Specifying the types of history information to be deleted

On the Task tab, in Run, specify -s TARGET=(change-log-code-to-be-deleted) following the file name. You can specify multiple codes.

If nothing is specified, the task deletes only the change log for asset information.

Codes for the change log that can be deleted are as follows:

A

Asset information history. The corresponding class is AssetUpdateRecord.

M

Maintenance log. The corresponding class is Maintenance.

U

Device change log. The corresponding classes are UpdateRecord and InstalledUpdateRecord.

If you specify multiple codes, specify them consecutively, such as -s TARGET=AMU.

(2) Specifying the duration for retaining history information

On the Task tab, in Run, specify the value following the file name in the format shown below:

Change log and maintenance log for asset information

-s TARGET=A (or M) -s MONTH=(retention-period)

Specify the retention period in number of months (0 to 120). Specifying 0 deletes all change log information.

If nothing is specified, the task deletes all change log data that is at least six months old.

Device change log

-s TARGET=U -s UMONTH=(retention-period)

Specify the retention period in number of months (0 to 120). Specifying 0 deletes all change log information.

If nothing is specified, the task deletes all change log data.

Specification example

This example shows the specification for deleting asset information logs and maintenance logs that are more than three months old.

"C:\jp1asset\exe\jamscript.exe"

-f "C:\jp1asset\scriptbatch\RemoveRecord.txt"

-s TARGET=AM -s MONTH=3

Here, C:\jp1asset refers to the Asset Console installation folder.

7.9.7 Acquiring JP1/IT Desktop Management 2 - Manager management information

This subsection describes how to acquire JP1/IT Desktop Management 2 - Manager management information. If no options are specified for this operation, only updated management information is acquired.

If you specify ALL after a file name in Run on the Task tab, all JP1/IT Desktop Management 2 - Manager management information sets are acquired regardless of whether the information has been updated. Specify this option only when you want to re-acquire all information sets, for example, when the settings for assignment items are changed.

Specification example

"C:\jp1asset\exe\jamTakeITDM2Info.exe" -ALL

Here, C:\jp1asset indicates Asset Console installation folder.

7.9.8 Notification of device information change

You can send email notification of a device information change to the asset manager. Because this task is not registered in Windows Task Scheduler, you must register the task if you use it.

To register the Notification of hardware change task to Windows Task Scheduler:

Start Task Scheduler.

From the Actions menu, select Create Basic Task.

Set the items below according to the wizard that appears.

Set items other than the following items as you wish.

Name in the Create a Basic Task window: Notification of hardware change

The Action window: Start a Program

Program/script in the Start a program window: Asset-Console-installation-folder\exe\jamscript.exe

Add arguments (optional) in the Start a program window: -f Asset-Console-installation-folder\scriptbatch\NoticeUpdateRecord.txt

Open the Properties dialog for this task when I click Finish in the Finish window: Checked

Click Finish in the wizard.

Specify the name of a user with administrator permissions in When running the task, use the following user account on the General tab in the displayed dialog box.

Click OK.

The dialog box closes and the Notification of hardware change task is registered.

When you execute the Notification of hardware change task, the task reports the number of devices that have been changed since the last task execution. It might take a long time to report the information when the task is executed for the first time or after a long period of time since the previous task.

To automatically send email notifications, you must set up Asset Console and Microsoft Internet Information Services accordingly. For details about the settings for using notification by email, see 7.10 Settings for using notification by email.

The following table describes the return values for the Notification of hardware change task.

Table 7‒14: Return values for the Notification of hardware change task

Return value

Description

0x0

The task terminated normally.

0x1

No applicable data was found.

0x2

Email notification is not specified.

0x3 or higher

The task terminated with some other error.

7.10 Settings for using notification by email

This section explains how to set Microsoft Internet Information Services to be able to use email to send the task execution results registered in Windows Task Scheduler or notification when an Item has been sent.

To send email notifications about task execution results and Item transmission, you must also specify some settings in the Server Setup dialog box. For details about how to specify settings in the Server Setup dialog box, see 7.3.5 Setting Mail Notification Information.

Additionally, maintain the SMTP Service's invalid mail directory on a regular basis. For details, see the documentation for Microsoft Internet Information Services.

7.10.1 Executing the SMTP virtual server

To execute the SMTP virtual server with Microsoft Internet Information Services:

Start the Internet Information Services 6.0 manager.

Expand the asset management server, and then select the default SMTP virtual server.

From the Action menu, select Start.

The status of the default SMTP virtual server is set to Running.

Notes on the use of SMTP authentication

Email sent by the asset management system is registered temporarily in the Microsoft Internet Information Services SMTP virtual server. Then the SMTP virtual server performs an SMTP relay to forward it to the mail server of the destination email account.

The Microsoft Internet Information Services SMTP virtual server does not support SMTP authentication (SMTP AUTH). Therefore, on the SMTP server side that first forwarded the email from Microsoft Internet Information Services SMTP virtual server, set SMTP AUTH to invalid for the asset management server PC.

Also, if the environment is set so that the asset management system's SMTP virtual server can connect directly to an external network, the SMTP virtual server can be used as an open relay SMTP server.

To ensure that it is not used as an open relay SMTP server, go to the properties of the default SMTP virtual server, and on the connection control settings of the Access tab, select Only the list below. Do not specify anything in the list.

Note also that open relay SMTP server refers to the SMTP server used as the source of various types of annoying email known as spam mail, regardless of its locator's will.

7.10.2 Adding a remote domain

To add a remote domain to the SMTP virtual server and relay received email on Microsoft Internet Information Services:

Start the Internet Information Services (IIS) 6.0 manager.

Expand the asset management server's default SMTP virtual server and select Domains.

From the Action menu, select New, and then Domains.

New SMTP Domain Wizard appears.

Choose Remote and then click Next.

Enter the server name that has the asset manager's email account, and then click Finish.

The remote domain is created.

Sending notification emails with an Item is attached

Enter the name of the mail server that holds the destination email account. If multiple mail servers are used, add the remote domain that they belong to. However, if the mail server's domain name is shared, a combined remote domain can be created.

For example, if the mail servers to be added to the remote domain are msrv01.abc.def.com, msrv02.abc.def.com, and msrv03.abc.def.com, you can create a remote domain for the three mail servers by specifying *.abc.def.com.

Select the created remote domain and then from the Action menu, select Properties.

The remote domain's Properties dialog box is displayed.

On the General tab, select the Allow incoming mail to be relayed to this domain check box.

Click OK.

Relaying of received email to the remote domain is set and the remote domain's Properties dialog box closes.

7.11 Notes on handling the asset management database

This section provides notes on the following topics related to the asset management database:

Characters supported by the windows that are displayed from the asset management database

Notes on database maintenance

7.11.1 Characters supported by windows that are displayed from the asset management database

With the asset management database, character strings are adjusted to be the same length and then compared. Therefore, short character strings are padded with trailing spaces during search operations. When you enter character strings such as device numbers, you should pad short character strings with leading zeros to make the lengths of all such character strings consistent.

7.11.2  Notes on database maintenance

Hitachi recommends that you back up your asset management database periodically as a protection in the event of errors and for reconstructing the environment.

For details about database maintenance and tuning, see 18. Maintaining the Asset Management Database.

7.12 Procedure for creating a cluster system environment

This section describes how to create an environment for an Asset Console cluster system. It also includes notes about using a cluster system.

For details about the OSs required for the asset management servers when a cluster system is configured, see 5.4 Installation in a cluster system.

This section describes the procedure for creating an environment for supporting failover of Asset Console.

7.12.1 Group resource creation by the cluster software's cluster administrator

Create the IP address resources, network name resources, and shared disk resources in the same group. Create these resources separately from the cluster group that is created when the cluster software is initially installed. Set the server that is to be used as the executing server as the preferential server.

For details about how to create these resources, see the documentation for the cluster software.

7.12.2 Creating a cluster environment for using Asset Console's failover function

This subsection describes how to create a cluster environment in which to use Asset Console's failover function.

On the executing server, install Asset Console.

The table below describes the settings. Specify them in the order they are listed in the table.

For items that are not included in the table, set them as you would normally.

For details about the installation procedure, see 7.2.2 Installing Asset Console. For details about the setup procedure, see 7.3 Setting up the asset management server.

Table 7‒15: Asset Console settings

Program

Setup item

Setting

Asset Console installation wizard

Selection of the installation destination

Specify a local disk.

Asset management server's virtual directory (the default is Asset-Console-installation-folder\wwwroot)

Specify a shared disk.

Asset Console's Setup dialog box

Service name

Specify the ODBC data source name.

Login ID and password

Specify the same login ID and password for the executing and standby servers.

Create the database in the Database Manager dialog box

--

Execute on both the executing and standby servers.

Basic Database Settings dialog box

Port number

Specify the same port number for the executing and standby servers.

Detailed Database Settings dialog box

Storage folder name

Specify a shared disk.

Use the same path for the executing and standby servers.

Detailed Database Settings dialog box

Size, automatic increase size

Specify the same size and the same automatic increase size for both executing and standby servers.

Create Data Source dialog box

Creation of data source

The data source is automatically created according to the settings when a new database is created. On the executing server, change the connection target of the data source to a logical host name (network name) after database creation is completed. (Immediately after a new database has been created, the connection target of the data source is set to localhost).

On the standby server, create a database after installation, and then change the connection target of the data source to the same logical host name (network name) as for the executing server.

Legend:

--: Not applicable

Check the operation at the executing server.

The database service might reference a file on the shared disk. Therefore, execute the following tasks when the operation completion is confirmed.

Stop World Wide Web Publishing Service or World Wide Web Publishing.

As a user with administrator permissions, execute jamemb_dbstop.bat and stop the asset management database.

jamemb_dbstop.bat is stored in the following folder:

Asset-Console-installation-folder\exe

Use Cluster Administrator to move the group.

This makes the standby server the owner.

At the standby server, execute environment creation step 1.

Each setting is the same. However, there is no need to create an asset management database.

Use Cluster Administrator to create the Microsoft Internet Information Services resource.

The tables below show the settings detail.

Table 7‒16: Resource settings for Microsoft Internet Information Services

Resource type

Input into the script file path

Dependence relationship

General-purpose script

%systemroot%\System32\Inetsrv\Clusweb.vbs

Sets up shared disk and client access point resources.

Note

The script file (Clusweb.vbs) for setting up resources in a cluster environment under Windows Server 2019, Windows Server 2016, or Windows Server 2012 is not installed as a standard component. If IIS 6 Management Compatibility of IIS Scripting Tools is installed when adding the role services of Microsoft Internet Information Services 7.0, the script file is stored in the designated path (%systemroot%\System32\Inetsrv).

Therefore, when setting up resources in a cluster environment, install IIS Scripting Tools beforehand. For details about the installation method, see the documentation for Microsoft Internet Information Services.

If Microsoft Internet Information Services 7.5, 8.0, or 8.5 is used, Clusweb.vbs is not created even if IIS 6 Management Compatibility of IIS Scripting Tools is installed when adding the role services. Refer to the technical information (KB970759) released by Microsoft, and download and use the sample general-purpose script.

When IIS Server Instance is placed online by the Cluster Administrator, the service starts. To subsequently stop or start the World Wide Web Publishing Service or World Wide Web Publishing, use the Cluster Administrator to change the status to offline or online, as appropriate.

Create the DBMS service's resources using the Cluster Administrator.

Create the resources with the settings shown in the table below. When the status is set to online, the asset management database starts.

The tables below show the settings details.

Table 7‒17: Resource settings details of the database service

Resource type

Service name to be specified

Dependence relationship

General-purpose service

HiRDBClusterService_AM1

Sets up shared disk and client access point resources.

7.12.3 Specifying the Web browser's connection target

Specify the Web browser's connection target as follows:

http://logical-host-name-or-logical-IP-adress/jp1asset/login.htm

7.12.4 Settings in an environment that uses a firewall

If you are configuring Asset Console as a cluster system that uses a firewall, set the physical address as the transparent address.

7.12.5 Handling after failover

The following table describes the user's action in the event of failover.

Table 7‒18: User's action after failover

Processing underway at the time of failover

Action to be taken after failover

Waiting to log in

With the Web browser, reload to display the Login window.

Logging in (no action)

Log out and then log in again.

Adding new information

Log out and search for the added information. If the addition process has not been completed, add the information again.

Referencing information

Log out, log in again, and then search for the information.

Totaling

If failover occurred during totaling, the totals result is not displayed in the list. Log in and then click the Execute button again or re-execute the Notice of license excess task.

Executing the task Data maintenance (Asset Console)

The task stops. Re-execute the task.

7.12.6 Notes about using a cluster system

The following notes apply when a cluster system is used:

When you install or uninstall Asset Console, use the Cluster Administrator to place the service resources of World Wide Web Publishing Service offline. After that, stop World Wide Web Publishing Service from Services, which is displayed by selecting Administrative Tools from Control Panel. If you start the installer or uninstaller while the service resource is online, failover might occur depending on the resource settings, or the installer or uninstaller might hang up or terminate abnormally.

If you change server setup settings, the settings specified at the executing server are not applied to the standby server, regardless of whether the service resource is online or offline. Make sure that each server has the same server settings.

World Wide Web Publishing Service or World Wide Web Publishing on the standby server must be stopped.

After you have set up for a cluster system environment, do not change Logical host name and Execution host name. If these settings are changed, the cluster functions will not work normally with Asset Console. To change the logical host name and execution host name, you must re-create the asset management database. For details about how to rename logical hosts, see F.3 Renaming the host. For details about how to rename the executing host, see 7.12.6(1)(b) How to rename the executing host.

When a failover occurs, World Wide Web Publishing Service (or World Wide Web Publishing) that has stopped must be started on the standby server. Therefore, World Wide Web Publishing Service on the standby server must be stopped before a failover occurs. For example, you can stop World Wide Web Publishing Service when Microsoft Internet Information Services on the standby server is offline by writing the code shown below for the Offline function in Clusweb.vbs (or Clusweb7.vbs). Using this setting, you can automate stoppage of World Wide Web Publishing Service.

Coding example

...
Function Offline( )
    Dim objWmiProvider
    Dim objService
    set objWmiProvider = GetObject("winmgmts:/root/cimv2")
    set objService = objWmiProvider.get("win32_service='w3svc'")
    StopWebSite()
    Offline = true
    objService.StopService()
End Function
...

(1) How to change the logical host name and execution host name

This subsection describes how to rename the logical host and executing host.

(a) How to rename the logical host

For details about how to rename logical hosts, see F.3 Renaming the host.

(b) How to rename the executing host

Before you rename the executing host, stop all Asset Console services, commands, and tasks on the asset management server.

To stop Asset Console services, stop the following services in the listed order:

World Wide Web Publishing Service or World Wide Web Publishing

Asset Console commands and tasks

To run Asset Console after having changed the executing host name, start the services in the reverse of the order in which they were stopped.

To rename the executing host:

Stop the database.

For details about how to stop the database, see F.4(2) Stopping the database.

Use a text editor to open the pdutsys file that is stored in Asset-Console-installation-folder\aimdb\conf.

In the pdutsys file, change host-name in set pd_hostname=host-name.

Rename the OS host.

Restart the OS.

7.12.7 Uninstalling Asset Console in a cluster system

This section explains how to uninstall Asset Console in a cluster system.

Set the following general service resources to an offline status.

Resources of Microsoft Internet Information Services

Resources of using DBMS service

Stop World Wide Web Publishing Service running on the executing server.

Stop all the Asset Console commands and tasks running on the executing server.

Uninstall Asset Console on the executing server.

Uninstall Asset Console on the standby server.

7.13 Suppressing operations on asset information from JP1/IT Desktop Management 2 operation windows

When you manage assets, you cannot use both Asset Console and JP1/IT Desktop Management 2 operation windows.

To maintain integrity of asset information, determine whether to use Asset Console for asset management when establishing a JP1/IT Desktop Management 2 system. If you choose asset management using Asset Console, you must suppress operations on asset information from JP1/IT Desktop Management 2 operation windows. For details about the suppression procedure, see Procedure for suppressing asset information registration and modification in the JP1/IT Desktop Management 2 Configuration Guide.

8 Achieving Asset Management by Linking to Other Products

This chapter describes the asset management jobs that can be performed by linking to other products, and how to implement such jobs.

8.1 Settings to link to JP1/IM

The figure below shows the procedure for checking problems from Asset Console, based on JP1 event information and SNMP trap information that you obtain by linking Asset Console to JP1/IM. For details about the required programs, see 6.2.3 System configuration linked to JP1/IM - Manager.

Figure 8‒1: Procedure for checking problems from Asset Console

To link to JP1/IM - Manager:

Set the JP1/IM - Manager automatic action setting, which will result in automatic collection of JP1 events and automatic notification of resolution completion.

When problem information is collected at a JP1/IM - Manager server, the automatic action facility notifies the asset management server via JP1/Base (automatic collection of JP1 events). When problem resolution completion is registered by Asset Console, the JP1 event that notifies of the resolution completion sends it to the JP1/IM - Manager server via JP1/Base. Then the automatic action function causes the JP1/IM - Manager problem information status to be updated (resolution completion notification).

For details about setting automatic collection of JP1 events, see 8.1.1(1) Setting automatic collection of JP1 events. For details about setting resolution completion notification, see 8.1.1(2) Setting error completion notification.

For details about the automatic action function, see the JP1/Integrated Management - Manager Overview and System Design Guide.

Select settings to forward JP1 events.

To forward a JP1 event from Asset Console, you must specify environment settings so that JP1/Base automatically forwards JP1 events to other event servers. For details about automatic forwarding of JP1 events, see 8.1.2 Settings to forward JP1 events.

Change issued JP1 events.

The event generation definition file is used to define the types of JP1 events to be issued from Asset Console. By default, all JP1 events are issued. For details about defining the event generation definition file, see 8.1.3 Changing issued JP1 events.

Set automatic login.

In the Group and User job menu for Asset Console, set a password in advance for the user provided for linkage. This will let you log in automatically without entering a user ID and password when viewing the Problem Details dialog box of Asset Console from the Event Console window.

The user ID JP1_IM and the user name Event Manager are provided for linkage with JP1/IM.

For details on setting a password, see 16.1 Changing user and group information (Group and User).

Deleting automatic login settings

Once a password has been set, the automatic login setting can be deleted either by deleting the related user or by using the jamimport (import) command to change the password to a blank password.

For details about importing using the jamimport command, see 9.1.1(3) Flow of import using the jamimport command.

8.1.1 Setting automatic action by JP1/IM - Manager

This section explains the settings for automatic collection by JP1/IM - Manager of JP1 events issued by Asset Console. It also explains the settings for notifying JP1/IM -Manager of problem resolution by Asset Console.

(1) Setting automatic collection of JP1 events

The figure below shows a specification example for notifying Asset Console of only emergencies and warnings from the information displayed on the JP1/IM side.

The following describes the values to be specified in JP1/IM - Manager's Action Parameter Detailed Definitions dialog box.

Leave the Parameter group settings unchanged.

For Action name, specify a desired name.

For Comment, enter a comment as necessary.

Action Condition tab (Condition)

For Event ID, select All IDs.

In Event conditions, click the Add button, and select Importance. Then select the Emergency and Warning check boxes in Specify directly, and click the Apply button.

Action Condition tab (Action Definition)

For Execution user name, specify the name of the user who executes actions.

For Target host, specify the name of the host that executes actions.

For Action, specify jamTakeIMEvent.bat "$EVDATE" "$EVTIME" "$EVUSR" "$EVHOST" "$EVIPADDR" "$EVSEQNO" "$EVMSG" "$EVSEV" "$ACTHOST" "$EV"OBJECT_TYPE"" "$EV"SNMP_SOURCE"".

Do not express a file name as a path.

Leave Environment variable file blank.

Execution monitoring tab

Specify the settings as needed.

(2) Setting error completion notification

When you register a resolution to a problem in Asset Console, you must set the JP1/IM - Manager jcochstat command for automatic notification to notify JP1/IM - Manager that the problem has been resolved.

The following shows the value specified in the JP1/IM - Manager Action Parameter Detailed Definitions dialog box.

Specify the Parameter group settings different from the setting in (1).

For Action name, specify a desired name.

For Comment, enter a comment as necessary.

Action Condition tab (Condition)

Select Specify ID for Event ID, and specify 00005581.

Leave Event conditions blank.

Action Condition tab(Action Definition)

Specify the user name to execute actions in Execution user name.

Specify the host name to execute actions in Target host.

Specify the full path to the jcochstat command in Action and -n "$EV"EVENT_SEQNO"" -k PROCESSED.

Leave Environment variable file blank.

Execution monitoring tab

Specify the settings as needed.

To reflect the JP1 event or SNMP trap resolution status changed by Asset Console, select the Resolution status change approval check box for the jcochstat command on the Communication tab of the System Environment Settings dialog box.

8.1.2 Settings to forward JP1 events

In order for JP1 events to be forwarded from Asset Console, the environment setting must be set for JP1/Base to automatically forward JP1 events to other event servers.

For details about JP1 event forwarding and definition information distribution, see the JP1/Base User's Guide.

8.1.3 Changing issued JP1 events

Define the JP1 events to be issued from Asset Console in the event issuance definition file (acevent.conf). By default, all JP1 events are issued.

The acevent.conf file is stored at Asset-Console-installation-folder\conf\event.

Shown below is an example of the contents of acevent.conf, followed by the format for defining issued JP1 events:

[EventID]
00005531=1
00005532=1
00005533=1
00005541=1
00005542=1
00005543=1
00005581=1
00005582=0
00005583=0

Define the [EventID] section in the format (EventID=1 (or 0)).

For each event ID, specify 1 if the JP1 event is to be issued or 0 if the JP1 event is not to be issued. For details about the JP1 event IDs, see 19.2 Details of JP1 events issued from Asset Console.

8.1.4 Displaying asset information from JP1/IM

You can view details by displaying the Problem Details dialog box corresponding to the selected JP1 event from the JP1/IM - Manager Event Console window.

To display the Problem Details dialog box:

Select the JP1 event issued by Asset Console in the JP1/IM - Manager Event Console window.

Display the event details window.

Click the Monitor button.

The Problem Details dialog box is displayed.

For information about using the Event Console window, see the manual JP1/Integrated Management - Manager GUI Reference.

8.2 Settings for linking to JP1/Service Support

To view device information managed by Asset Console from JP1/Service Support, log in to Asset Console.

If you have set a password to allow you to handle linkage in the Asset Console's Group and User job menu, you can automatically log in without the need of specifying your user ID and password.

User ID JP1_IM_SS and user name Event Manager are provided for linkage to JP1/Service Support.

For details about how to set the users and passwords provided for linkage to individual products, see 16.1 Changing user and group information (Group and User).

Canceling the automatic login settings

To cancel the automatic login settings after you have set a password, delete the specified password. Alternately, you can use the jamimport (import) command to delete the password.

For details about import using the jamimport command, see 9.1.1(3) Flow of import using the jamimport command.

8.2.1 Displaying asset information from JP1/Service Support

When you view Item information in JP1/Service Support, you can also view device information managed by Asset Console.

To view device information in the Device Details dialog box (which is displayed from the View Item window):

In the Main window (Item list) window, double-click an Item whose detailed information you want to display.

The View Item window is displayed. You can also display the View Item window by clicking the icon for opening the View Item window from the Item preview.

Click the anchor for the information registered in Device information.

The Device Details dialog box of Asset Console is displayed. In this dialog box, you can view information, such as device type, user, group, and maintenance log.

8.3 Settings for linking to EUR

This section describes the settings for linking to EUR, outputting forms to PDF files, and displaying and printing the contents in the Web browser. For details about the required programs, see 6.2.5 System configuration linked to EUR.

Set to show the button used for viewing and printing PDF files.

In the Server Setup dialog box, for the Show PDF button item in Basic Information, select Show.

For details about how to set information in the Server Setup dialog box, see 7.3.4 Setting Basic Information.

8.3.1 Displaying and printing PDF files

To display and print PDF files from Asset Console:

Click the PDF button in an operation window.

Adobe Reader displays the PDF file.

Print a PDF file by using Adobe Reader's print function.

The displayed PDF file is printed.

(1) Notes when the settings are changed in Customize Managed Items and Customize Job Windows

Items output to a form might have only header lines and their data lines might be output as blank. This might occur if you change the display names of the corresponding items in Customize Managed Items, or if you change the settings of whether to show or hide these items in Customize Job Windows. In such a case, the changed display names and display order are also not applied.

In order to apply changes in Customize Managed Items and Customize Job Windows, you need to edit the form and CSV file in EUR.

To edit forms and CSV files:

Copy the CSV file corresponding to a form to the EUR folder.

When you edit a form in EUR, a CSV file is required as mapping data or user-defined data.

Before editing a form, copy the CSV file corresponding to that form to the following folder:

Copy source

Asset-Console-installation-folder\eur

Copy destination

EUR-installation-folder\SAMPLE\Reports

Modify the CSV file according to the setting change in Customize Managed Items and Customize Job Windows.

Modify the CSV file stored in step 1, according to the settings in Customize Managed Items and Customize Job Windows.

If display names are changed in Customize Managed Items, modify the header lines to match the changed display names.

If the settings of show and hide are changed in Customize Job Windows, add or delete columns corresponding to the CSV file.

Modify the form according to the setting change in Customize Managed Items and Customize Job Windows.

Change the display names of the relevant form to match the settings in Customize Managed Items. The corresponding items must have the settings displayed in Customize Job Windows.

In addition, add or delete items in the form to match the settings in Customize Job Windows.

The forms are stored at Asset-Console-installation-folder\eur.

The following table lists the file names of the forms used for individual windows, and the corresponding CSV file names.

Table 8‒1: Names of the form and CSV files

Window

Form file name

CSV file name

Device List

PossessionApparatusList.fms

PossessionApparatusList.csv

Contract List

ContractInformationList.fms

ContractInformationList.csv

Problem Details

MaintenancePDFList.fms

MaintenancePDFList.csv

Owned License List - by Used

MachineDetailPossLic.fms

MachineDetailPossLic.csv

MachineDetailPossLic2.csv

Excess License List - by Used

MachineDetailExcessLic.fms

MachineDetailExcessLic.csv

MachineDetailExcessLic2.csv

Unauthorized Usage List - by Used

MachineDetailUnPossLic.fms

MachineDetailUnPossLic.csv

MachineDetailUnPossLic2.csv

Unknown Usage List - by Used

MachineDetailUnRegSoft.fms

MachineDetailUnRegSoft.csv

MachineDetailUnRegSoft2.csv

Software List

KeepSoftwareList.fms

KeepSoftwareList.csv

Software Details

SoftwareDetail.fms

SoftwareDetail.csv

SoftwareKeyInfo.csv

Volume License List

VolumeContractInformationList.fms

VolumeContractInformationList.csv

License Details

VolumeContractInformation.fms

VolumeContractInformation.csv

VolumeContractInformation2.csv

Maintenance Log Details

MaintenancePDFList.fms

MaintenancePDFList.csv

9  Registration and Output of CSV Data

This chapter explains how to register CSV data into the asset management database and how to output asset information from the asset management database.

When executing an Asset Console command, you must use the 32-bit command prompt. For the execution procedure, see Appendix G. Notes on Executing Asset Console Commands and Tasks.

9.1 Registering CSV data (importing)

This section explains how to import information (import asset information from CSV files in a batch operation).

There are three ways to perform importing:

From the Import job menu

Using jamCsvImport.bat

Using the jamimport command

You can use this function to batch-register a large amount of information in the asset management database. You may need to do this when information other than that collected by JP1/IT Desktop Management 2 - Manager is to be registered. You can also use this function to update or delete registration information in the asset management database in a batch operation.

9.1.1 Import flow

This subsection describes how to import information.

(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:

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.

Select the Import job menu.

The Import window is displayed.

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.

Register the import conditions.

Specify any name, and register the conditions.

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).

(2) Flow of import using jamCsvImport.bat

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

To import using jamCsvImport.bat:

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.

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.

(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:

World Wide Web Publishing Service or World Wide Web Publishing

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:

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.

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.

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.

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.

9.1.2 Notes on the import operation

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

(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:

IPGroupID (IP group ID) of AddressGroup (IP group information) class

AssetID (asset ID) of AssetInfo (asset information) class

AssetBranchNo (branch number) of AssetInfo (asset information) class

ContractID (contract ID) of Contract (contract information) class

DivisionID (division ID) of DivisionInfo (division information) class

InstalledID (installed software ID) of InstalledList (installed software list) class

LicenseID (license ID) of LicenseInfo (license information) class

CatalogID (catalog ID) of MachineCatalog (device catalog) class

MaintenanceID (maintenance log ID) of Maintenance (maintenance log) class

NetworkID (network information ID) of NetworkInfo (network information) class

PatchConditionID (patch ID) of PatchConditionInfo (conditions of search device) class

ParentAssetID (parent asset ID) of RelationAssetInfo (related asset information) class

ChildAssetID (child asset ID) of RelationAssetInfo (related asset information) class

KeyID (key ID) of SoftwareKeyInfo (software key information) class

SoftwareListID (software list ID) of SoftwareList (software list) class

VolumeID (volume contract ID) of VolumeContract (volume contract information) class

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

GroupID (group ID) of GroupInfo (group information) class

LocationID (location ID) of LocationInfo (location information) class

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

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

DivisionID (division ID) of DivisionInfo (division information) class

GroupID (group ID) of GroupInfo (group information) class

UpperLinkID (upper group ID) of GroupInfo (group information) class

LocationID (location ID) of LocationInfo (location information) class

UpperLinkID (upper location ID) of LocationInfo (location information) class

RoleID (role ID) of RoleInfo (role information) class

JobRoleID (official authority ID) of JobRoleInfo (official authority) class

UserID (user ID) of UserInfo (user information) class

(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.

9.1.3 Executing jamCsvImport.bat

This subsection gives the function, format, options, return value, notes about command execution, and an execution example of jamCsvImport.bat, which executes the import operation equivalent to the Import job menu from the command line.

jamCsvImport.bat is stored in the following folder:

Asset-Console-installation-folder\exe

(1) Function

This command registers, updates, and deletes CSV file data from the asset management database. The CSV file information is registered in a batch operation into the asset management database, based on the conditions. For details about how to create conditions, see 16.10.2 Creating import conditions.

When an asset type is specified, information is registered in a batch operation into the asset management database based on the default settings. For details about the items imported based on the default settings, see 20.4 Items to be imported or exported using a job menu.

(2) Format

jamCsvImport.bat "CSV-file-path"  " { -c conditions-name [-o processing-format] | -a asset-type -o processing-format } "

(3) Options

CSV-file-path

Specifies the CSV file to import, in terms of the file path. This option is mandatory.

-c conditions-name

Specifies the name of the import conditions saved from the Import window.

-o processing-format

Specifies a code indicating the import processing format, as shown in the table below. This option can be omitted when a conditions name is specified. This option must be specified when an asset type is specified.

Processing format

Meaning

001

Add

002

Update

003

Add update

004

Delete

-a asset-type

Specifies a code indicating the type of asset information to be imported, as shown in the table below. When this option is specified, import adheres to the default settings.

Table 9‒1: Asset type codes

Code

Meaning

001

Device information

002

Installed software information

003

Installed software list

004

Software information

005

Software list

006

Group information

007

User information

008

Location information

009

Maintenance contract information

010

Rental contract information

011

Lease contract information

012

Volume contract information

013

IP group information

014

Device catalog information

015

User definition (user report)

016

User definition (form)

017

Customize (Acquiring ITDM2 management information)

018

User definition (import/export)

019

Problems

020

Assigned license information

021

Patches

022

Virus definition

023

User definition (Item definition)

024

User definition (contract history)

025

Related asset information

026

Division information

027

Division assignment

(4) Return value

The following table shows the return values.

Return value

Meaning

0

Normal end.

1

No data.

2 or more

Error occurred during processing.

(5) Notes on command execution

A user with administrator permissions must execute jamCsvImport.bat.

(6) Example

jamCsvImport.bat "c:\temp\Hardware.csv" -a 001 -o 001

If the file path is omitted during command execution, Asset-Console-installation-folder\scriptwork becomes the current working directory.

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.

(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.

(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.

(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.

(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.

(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.

(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.

(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.

(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.

(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.

(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.

(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.

(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.

(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.

(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.

(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.

(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.

9.1.5 File format for importing with the jamimport command

This section describes the formats of data files and data files definition files.

(1) Data files

To import into the asset management database using the jamimport command, you must create data files containing the asset information. The following describes the supported data file format, character encoding, delimiters, and the location of delimiters:

File format

Create a data file in CSV format.

Supported character encoding

Depending on the system locale of the machine on which the asset management server is installed, the character encoding used for the description differs.

Japanese: Shift_JIS encoding

English: ASCII encoding

Chinese: GBK encoding

Delimiters and their locations

Delimit each class data item by a linefeed code (CRLF or LF). Also delimit each class property by a comma (,). There is no limit to the number of classes or properties that can be specified in a data file.

(2) Data files definition file

To import multiple data files in a batch operation, create a data files definition file. The following describes the supported data files definition file format, character encoding, delimiters, and the location of delimiters:

File format

Create a data files definition file in text format.

Supported character encoding

Depending on the system locale of the machine on which the asset management server is installed, the character encoding used for the description differs.

Japanese: Shift_JIS encoding

English: ASCII encoding

Chinese: GBK encoding

Delimiters and their locations

When importing object classes

Specify the name of a data file to be imported paired with the corresponding object class name and delimit the pair with a linefeed code (CRLF or LF). Enclose each data file name and object class name in double quotation marks (") and separate the two with a comma.

When importing association classes

Specify the name of a data file to be imported, the corresponding association class name, and the associated two object class names as a set, and delimit the set with a linefeed code (CRLF or LF). Enclose each data file name, association class name, and object class name in double quotation marks (") and separate them with a comma.

The figure below shows how to specify delimiters and their locations.

Figure 9‒1: Specifying delimiters and their locations

9.1.6 Creating data files

This section explains the specification format for and provides specification examples of CSV files (data files) that are to be imported using the jamimport command.

When creating data files, make sure that data conformity is achieved in related information and control information such as IDs.

(1) Data file creation units

Create one data file for each class to be imported.

For association classes, you need to create data files only when object classes are to be associated with each other by different key information. There is no need to import association classes when the same key information is used to associate object classes.

For details about the association between object classes, see 10.1.3 Types of associations.

(2) Data file specification format

The following figure shows the data file specification format.

Figure 9‒2: Data file specification format

This section describes the following items:

Item title line

Operation code

Key data

Data

(a) Item title line

The item title line always begins with OP (operation code).

Following OP, specify a property name as the title of each item. On the item title line, make sure that the key property of the class to be imported is specified.

For an association class, specify the item title line in the format class-name.property-name. Make sure the object class name is separated from the property name by a period (.). For details about the class and property names, see Chapter 20. Management Information Details.

If the imported class contains a property that is not specified in the item title line, the null data is set as the value of that property.

(b) Operation code

Specify one character indicating the type of change to the table (addition, change, deletion, no change). If more than one character is specified, only the first character is recognized.

The following table lists the characters that can be used as operation codes and their meanings.

Table 9‒23: Characters used as operation codes

Operation code

Meaning

Description

A

Addition

Adds the data specified in the data file.

If no value is specified for a class property, the null data is added for that property.

C

Change

Replaces existing data with data specified in the data file. All properties specified in the item title line are subject to this change.

If no value is specified for a class property, the null data is added for that property.

D

Deletion

Deletes the classes specified in the data file and the values of the properties related to those classes.

N

No change

Does not import data with operation code N, treating it as being unchanged.

R

Comment

Does not import the data, treating it as a comment line.

When importing association classes, you can use only A (addition) and D (deletion). To make changes, specify data to be deleted in the data file and then add new data.

(c) Key data

Specify the key data used to determine the object of processing and the class. Make sure a value is specified.

For an object class, specify key data in the format property-name. For an association class, specify it in the format object-class-name.property-name.

Whether the data is to be changed or deleted is determined by the key data. Therefore, if you import data that had been exported and then modified, do not change its key data.

(d) Data

Specify the property value of the class to be imported.

For an object class, specify data in the format property-name. For an association class, specify it in the format object-class-name.property-name.

For data, there is no need to specify all properties in the object class. Specify only those data items that are needed as asset data. Specify the value of each property according to the specification format and limitations. For details about the specification format and limitations for each property, see Chapter 20. Management Information Details.

When there are no more property values to be set, you can omit values by placing a linefeed code immediately after the last property value. In such a case, the null data is imported for all properties following the linefeed code.

Notes on specifying property values

Some property values use a code, as is the case with the asset information Asset type. For details about the properties that require specification of a code and details about the code, see 20.2 Lists of properties for object classes.

(3) Specification example of data file (object class)

This section describes an example of specifying a data file for importing an object class.

The figure below shows an example of importing data for the AssetInfo (asset information) object class, where the key for AssetInfo is AssetID (asset ID).

Figure 9‒3: Specification example of a data file (object class)

This example updates the asset management database as follows:

The device with asset ID 1 is added with the property value specified in the item title line.

All information about the device with asset ID 2 is changed by the property values specified in the item title line.

All information about the device with asset ID 3 is deleted.

All information, such as hardware and network information, that has weak association with the device with asset ID 3 is also deleted.

(4) Specification example of data file (association class)

To add or delete an association class, use operation code A (addition) or D (deletion) in the data file. You cannot use operation code C (change).

The figure below shows an example of a data file for importing data for the association class ContractMaintenanceLink (maintenance contract link). The keys for ContractMaintenanceLink are AssetID (asset ID) and ContractID (contract ID).

Figure 9‒4: Specification example of data file (association class)

This example specifies the key data AssetID for the associated object class AssetInfo (asset information). On the same line, it also specifies the key data ContractID for another object class Contract (contract information).

This example updates the asset information as follows:

The asset with asset ID 1 is added to the target of contract ID 123456.

The target contract ID for the asset with asset ID 2 is changed from 000123 to 123456.

9.1.7 Creating a data files definition file

This section describes the specification format and specification examples for a data files definition file that is used by the jamimport command to import multiple data files in a batch operation.

(1) Specification format for data files definition file

You must specify, in a data files definition file, the names of data files to be imported and the names of corresponding object classes.

To import an association class, specify the name of the data file to be imported, the name of corresponding association class, and the names of two associated object classes.

The following figure shows the specification format for a data files definition file.

Figure 9‒5: Specification format for a data files definition file

The items specified in the data files definition file are explained below.

data-file-name

Specifies the path of the data file that is to be imported. You can specify a full or a relative path. A relative path is based on the path where the data files definition file is located. Neither .\ nor ..\ is permitted.

object-class-name and association-class-name

Specifies the name of the class corresponding to the specified data file or a class name.

associated-object-class-name and another-associated-object-class-name

Specifies the names of two object classes that are associated with each other as association classes.

Specify this information only when an association class is to be imported.

Note that you can omit associated-object-class-name and another-associated-object-class-name.

For details about class names, see 20.1 Organization of classes.

(2) Specification example of data files definition file (object class)

This section describes an example of specifying a data files definition file when object classes are imported.

The following figure shows a specification example of a data files definition file.

Figure 9‒6: Specification example of data files definition file (object class)

Line 1 indicates that the name of the data file is C:\temp\AssetInfo.csv and that the name of the object class is AssetInfo (asset information).

By executing the jamimport command, this example imports the contents of C:\temp\AssetInfo.csv to the object class AssetInfo.

The subsequent lines are processed in the same manner as with line 1.

(3) Creating a data files definition file (association class)

This section describes an example of a data files definition file when association classes are imported.

The following figure shows a specification example of data files definition file.

Figure 9‒7: Specification example of data files definition file (association class)

Line 1 indicates that the name of the data file is C:\temp\ContMLink.csv, and that the name of the association class is ContractMaintenanceLink (maintenance contact link). It also indicates that the names of the associated object classes are AssetInfo (asset information) and Contract (contract information).

By executing the jamimport command, this example imports the contents of C:\temp\ContMLink.csv to the association class ContractMaintenanceLink.

The subsequent lines are processed in the same manner as with line 1.

9.1.8 Executing the jamimport (import) command

This subsection gives the function, format, options, return values, notes about command execution, and an execution example of the jamimport command, which is used for import operations.

The executable file for the command is stored in the following folder:

Asset-Console-installation-folder\exe

(1) Function

The jamimport command registers data in a CSV file into the asset management database and updates the database. The command registers all data in the CSV file into the asset management database as is in a batch operation. A CSV file to be registered is created for each class.

To register information about multiple classes at one time, you must use a data files definition file.

(2) Format

jamimport
      {{-f data-file-name
          -gc object-class-name-or-association-class-name}
       |-dc data-files-definition-file}
      [-e log-file-name[-s]]
      [-l message-type]

(3) Options

-f data-file-name

Specifies the name of the data file if there is only one data file to be imported. The data file name can be a full or relative path.

Make sure that this option is specified together with the -gc option. The -f and -dc options are mutually exclusive.

-gc object-class-name-or-association-class-name

Specifies the class name corresponding to the data file if there is only one data file to be imported.

If you are importing an object class, specify the name of the object class. If you are importing an association class, specify the name of the association class. For details about class names, see 20.1 Organization of classes.

Make sure that this option is specified together with the -f option. The -gc and -dc options are mutually exclusive.

-dc data-files-definition-file

Specifies that multiple data files are to be imported in a batch operation. You cannot specify this option together with the -f or -gc option.

The name of the data files definition file can be a full or relative path.

-e log-file-name

Specifies the file to which messages, which are usually output to the console, are to be output. Specify the name of the log file to which messages are to be output.

This option can be omitted, in which case the system outputs the messages to the console where the jamimport command was executed.

For details about the log file output format, see Chapter 17. Troubleshooting.

-s

Specifies that the number of imported items is to be displayed on the console as the progress status. You can specify this option only when the -e option is specified. When the -s option is omitted, the number of processed items is not displayed.

The progress status is displayed each time 50 items are processed.

-l message-type

Specifies the type of messages to be output to the log file. This option can be omitted. When the option is omitted, E is assumed.

The following shows the permitted message types and the information that is output:

E

Outputs only messages that report a serious error requiring termination of the program.

W

Outputs the following two types of messages:

Messages with type E

Messages reporting an error that does not require termination of the program but that disables some functions

I

Outputs information messages plus messages with types E and W.

(4) Return value

The jamimport command returns the following values.

Return value

Description

0

Normal end

1

Warning occurred, but processing terminated normally.

11

Format error was detected in the command options.

21

The file to be imported is not accessible or contains an error.

52

Processing was canceled by the user.

101 or greater

The command terminated due to some other error.

(5) Notes on command execution

A user with administrator permissions must execute the jamimport command.

If an import operation is executed while a window operation is underway or JP1/IT Desktop Management 2 - Manager management information is being registered, the data might not be registered or updated correctly due to other data updating operations. When you execute an import operation, you should ensure that no other operations are underway, such as window operations or registering JP1/IT Desktop Management 2 - Manager management information.

If the import operation is terminated by pressing Ctrl+C or Ctrl+Break or due to a system error (such as a database error or file I/O error), an error message to that effect is displayed and the processing is terminated. In this case, the data up to the data that was being processed when the operation was stopped or canceled has been imported into the asset management database.

However, data conformity might be lost in the asset management database because the import operation terminated when the operation was stopped or canceled. To be prepared for such events, Hitachi recommends that you make a backup of your asset management database.

If the import operation is canceled or stopped due to an error and the same data file is re-imported with the same operation code A (addition), a warning error occurs for the data that has already been registered into the asset management database.

If the specified jamimport command contains an invalid option, the error message and command format are displayed on the screen. This error is not output to the log file.

If the command contains an option argument that specifies a character string containing a space, you must enclose the entire argument in double quotation marks (").

(6) Example

jamimport -f "c:\temp\Hardware.csv" -gc HardwareInfo

9.2 Outputting CSV data (exporting)

This section describes how to output asset information from the asset management database to CSV files.

Asset Console can output asset information from the asset management database to CSV files in a batch operation. This is called exporting.

There are three ways to perform exporting:

From the Export job menu

Using jamCsvExport.bat

Using the jamexport command

The export operation outputs asset information to CSV files in a batch operation. This is useful when data is to be backed up. By modifying the exported CSV files and then importing them, you can also make changes to or delete asset information in the asset management database.

9.2.1 Selecting the method for outputting CSV data

This section explains the advantages of the various methods of exporting. Select the method that will give you the best efficiency on the basis of the information that you want to export.

Exporting from the Export job menu

You can create export conditions for the CSV file in order to obtain the asset information that you want to output and output to the CSV file in a batch operation. You can specify in the conditions the Asset Console management items in the CSV file to be output.

This method can export from anywhere, as long as it is an environment that can log in to Asset Console.

By specifying tight search conditions, you can output only the precise information that you want.

If your purpose is to make a backup or to migrate the asset information system to another machine, you can output user reports, job window forms, management information assignment settings, and the import/export conditions.

Exporting using jamCsvExport.bat

The same processing as when you use the Export job menu can be performed from the command line on the asset management server. This method is useful for automating operation because you can output asset information according to categories such as Device information, without being concerned about the CSV file format or the relationship between classes.

With this method, the export conditions cannot be changed or saved.

Exporting using the jamexport command

Export can be executed in units of desired classes. Multiple classes can be exported at the same time, but the contents of the export are selected in units of classes. If your purpose is to make a backup, output can be performed in a batch operation without having to accept or reject the contents of the asset management database information.

For details about information (classes) that can share export, see 20.1 Organization of classes.

9.2.2 Export procedure

This subsection describes the export procedure for each method.

(1) Exporting from the Export job menu

This section explains the workflow when exporting asset information from the Export job menu.

To export asset information from the Export job menu:

Select the Export job menu.

The Export window is displayed.

Create the export conditions.

Select the type of information to be exported (such as Device information), select the Asset Console managed items to be output, and then create the conditions. For the items to be imported, see 20.4 Items to be imported or exported using a job menu.

For details about operations in the Export window, see 16.11 Exporting asset information in CSV format (Export).

Save the export conditions.

Specify any name, and save the conditions.

Search the saved conditions, and execute the export.

For details about searching the conditions and executing export, see 16.11.2 Executing an export operation.

(2) Exporting using jamCsvExport.bat

This section explains the workflow when you execute jamCsvExport.bat for export.

To export using jamCsvExport.bat:

Execute jamCsvExport.bat from the command line on the asset management server.

Export executes in accordance with the specified conditions.

For details about executing jamCsvExport.bat, see 9.2.3 Executing jamCsvExport.bat. For the items to be exported, see 20.4 Items to be imported or exported using a job menu.

(3) Exporting using the jamexport command

Notes

Before you execute the jamexport command, stop all Asset Console services, commands, and tasks in the following order:

World Wide Web Publishing Service or World Wide Web Publishing

Asset Console commands and tasks

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

To export asset information by using the jamexport command:

Create a data files definition file.

To export information about multiple object classes in a batch operation, create a file defining the names of the data files to be exported to (data files definition file). If you are exporting only one object class, there is no need to create a data files definition file.

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

From the asset management server's command line, execute the jamexport (export) command.

For details about the jamexport command, see 9.2.6 Executing the jamexport (export) command.

The asset information is output to the data files in units of object classes or association classes.

If there is no asset information for a specified object class or association class, a data file containing only the item title lines is output.

9.2.3 Executing jamCsvExport.bat

This subsection gives the function, format, options, return value, notes about command execution, and an execution example of jamCsvExport.bat, which executes the export operation equivalent to the Export job menu from the command line.

jamCsvExport.bat is stored in the following folder:

Asset-Console-installation-folder\exe

(1) Function

This command outputs asset management database information to a CSV file. The CSV file information is output in a batch operation, based on the conditions. For details about how to create conditions, see 16.11.1 Creating export conditions.

When an asset type is specified, information is registered in a batch operation into the asset management database based on the default settings. For details about the items imported based on the default settings, see 20.4 Items to be imported or exported using a job menu.

(2) Format

jamCsvExport.bat "CSV-file-path"  " -c conditions-name | -a asset-type "

(3) Options

CSV-file-path

Specifies the CSV file to export, in terms of the file path. This option is mandatory.

-c conditions-name

Specifies the name of the export conditions saved from the Export window.

-a asset-type

The table below lists the codes that indicate the type of asset information to be exported. When this option is specified, all properties of the class set in the Customize Managed Items job menu are output.

Table 9‒24: Asset type codes

Code

Meaning

001

Device information

002

Installed software information

003

Installed software list

004

Software information

005

Software list

006

Group information

007

User information

008

Location information

009

Maintenance contract information

010

Rental contract information

011

Lease contract information

012

Volume contract information

013

IP group information

014

Device catalog information

015

User definition (user report)

016

User definition (form)

017

Customize (Acquiring ITDM2 management information)

018

User definition (import/export)

019

Problems

020

Assigned license information

021

Patches

022

Virus definition

023

User definition (Item definition)

024

User definition (contract history)

025

Related asset information

026

Division information

027

Division assignment

(4) Return value

The following table shows the return values.

Return value

Meaning

0

Normal end

1

No data

2 or more

Error occurred during processing.

(5) Notes on command execution

A user with administrator permissions must execute jamCsvExport.bat.

(6) Example

jamCsvExport.bat "c:\temp\Hardware.csv" -a 001

9.2.4 Output format of data files

This section describes the output format of data files when object classes or association classes are exported by the jamexport command.

A data file is created as a CSV file with the specified name. One data file is created for each object class or association class.

In each data file, all properties of the specified object class or association class are output according to the operation code. If no operation code is specified for a data file, N (no change) is assumed for all properties.

The key property is output to the column immediately following the operation code. Numeric values are output as is, while character strings are enclosed in double quotation marks (").

Note that a data file is created even when there is no value (data) to be exported for the properties of specified object class or association class. In this case, only the item title lines are output.

9.2.5 Creating a data files definition file

This section describes the file format and specification format for, and provides specification examples of data files definition files for which the jamexport command is used to export object classes.

(1) Format of data files definition file

To export multiple asset data items in a batch operation, create a data files definition file. This section describes the format of a data files definition file, the character encoding, delimiters, and the location of delimiters.

File format

You must create a data files definition file in the text format.

Supported character encoding

Depending on the system locale of the machine on which the asset management server is installed, the character encoding used for the description differs.

Japanese: Shift_JIS encoding

English: ASCII encoding

Chinese: GBK encoding

Delimiters and their locations

When exporting object classes

Specify the name of a data file to be exported paired with the corresponding object class name and delimit the pair with a linefeed code (CRLF or LF). Enclose each data file name and object class name in double quotation marks (") and separate the two with a comma.

When exporting association classes

Specify the name of a data file to be exported, the corresponding association class name, and the associated two object class names as a set and delimit the set with a linefeed code (CRLF or LF). Enclose each data file name, association class name, and object class names in double quotation marks (") and separate them with the comma.

(2) Specification format for data files definition file

You must create a data files definition file as a text file. In the file, specify the name of the target data file and the corresponding object class name.

To export an association class, specify the name of the target data file, corresponding association class name, and associated two object class names.

The following figure shows the specification format for a data files definition file.

Figure 9‒8: Specification format for a data files definition file

The following describes the items specified in a data files definition file:

data-file-name

Specifies the name of the data file in which asset data is to be written. You can specify a full or relative path. A relative path is based on the path where the data files definition file is located. Neither .\ nor ..\ is permitted.

object-class-name and association-class-name

Specifies the class name for the asset data to be exported.

associated-object-class-name and another-associated-object-class-name

Specifies the names of two object classes that are associated with each other as association classes.

Specify this information only when an association class is to be imported.

(3) Specification example of data files definition file (object class)

This section describes an example of specifying a data files definition file when object classes are exported using the jamexport command.

The following figure shows a specification example of a data files definition file.

Figure 9‒9: Specification example of data files definition file (object class)

Line 1 indicates that the name of the data file is C:\temp\AssetInfo.csv and that the name of the object class is AssetInfo.

By executing the jamexport command, this example exports the entire contents of the object class AssetInfo to C:\temp\AssetInfo.csv.

The subsequent lines are processed in the same manner as with line 1.

(4) Specification example of data files definition file (association class)

This section describes an example of a data files definition file when association classes are exported using the jamexport command.

The following figure shows a specification example of a data files definition file.

Figure 9‒10: Specification example of data files definition file (association class)

Line 1 indicates that the name of the data file is C:\temp\ContMLink.csv, that the name of the association class is ContractMaintenanceLink, and that the names of the associated object classes are AssetInfo and Contract.

By executing the jamexport command, this example exports the entire contents of the association class ContractMaintenanceLink to C:\temp\ContMLink.csv.

The subsequent lines are processed in the same manner as with line 1.

Note

You can export weak association classes, but you cannot import them. For details about weak association classes, see 10.1.3 Types of associations.

9.2.6 Executing the jamexport (export) command

This subsection gives the function, format, options, return values, notes about command execution, and an execution example of the jamexport command, which is used for export operations.

The executable file for the command is stored in the following folder:

Asset-Consoler-installation-folder\exe

(1) Function

The jamexport command outputs information from the asset management database information to a CSV file for each class. For the specified classes, all property values are output as is to the CSV files.

To output information about multiple classes at one time, you must use a data files definition file that defines the correspondence between the classes to be output and the CSV file names.

(2) Format

When exporting object classes

jamexport

{{-f data-file-name

-gc object-class-name}

|-dc data-files-definition-file}

[-e log-file-name[-s]]

[-l message-type]

[-op operation-code]

When exporting association classes

jamexport

{{-f data-file-name

-ac association-class-name

-c1 associated-object-class-name

-c2 another-associated-object-class-name}

|-dc data-files-definition-file}

[-e log-file-name[-s]]

[-l message-type]

[-op operation-code]

(3) Options

-f data-file-name

Specifies the name of the data file if the asset data to be exported is only one object class or association class.

The data file name can be a full or relative path. Make sure that this option is specified together with the -gc (or -ac, -c1, or -c2) option. The -f and -dc options are mutually exclusive.

-gc object-class-name

Specifies the object class name if the asset data to be exported is only one object class or association class.

Make sure that this option is specified together with the -f option. The -gc and -dc options are mutually exclusive.

For details about class names, see 20.1 Organization of classes.

-ac association-class-name

Specifies the name of the association class if asset data is to be exported for a single association class.

Make sure that this option is specified together with the -f, -c1, or -c2 option. The -ac and -dc options are mutually exclusive.

-c1 associated-object-class-name

Specifies the name of the object class associated with the association class if asset data is to be exported for a single association class.

-c2 another-associated-object-class-name

Specifies the name of another object class associated with the association class if asset data is to be exported for a single association class.

-dc data-files-definition-file

Specifies that multiple asset data items are to be exported in a batch operation and the name of the classes to be exported are used in the data files definition file. You cannot specify this option together with the -f, -gc, -ac, -c1, or -c2 option.

The name of a data files definition file can be a full or relative path.

-e log-file-name

Specifies the file to which messages, which are usually output to the console, are to be output. Specify the name of the log file to which messages are to be output.

This option can be omitted. When the option is omitted, the system outputs the messages to the console where the jamexport command was executed.

For details about the log file output format, see Chapter 17. Troubleshooting.

-s

Specifies that the number of exported items is to be displayed on the console as the progress status. You can specify this option only when the -e option is specified. When the -s option is omitted, the number of processed items is not displayed.

-l message-type

Specifies the type of message to be output to the log file. This option can be omitted. When the option is omitted, E is assumed.

The following shows the permitted message types and the information that is output:

E

Output only those messages that report a serious error requiring termination of the program.

W

Output the following two types of messages:

Messages with type E

Messages reporting an error that does not require termination of the program but that disables some functions

I

Output information messages plus the messages with types E and W

-op operation-code

Specifies either A (addition), C (change), D (deletion), N (no change), or R (comment) as the operation code to be output to each line in the exported file. The operation code is a single character indicating the type of change to the table during import operation. If this option is omitted, N is assumed.

For details about the operation code, see 9.1.6(2) Data file specification format.

(4) Return value

The jamexport command returns the following values:

Return value

Description

0

Normal end

1

Warning occurred, but processing terminated normally.

11

Format error was detected in the command options.

21

The file to be exported is not accessible or contains an error.

52

Processing was canceled by the user.

101 or greater

The command terminated due to some other error.

(5) Notes on command execution

A user with administrator permissions must execute the jamexport command.

If the jamexport command contains an invalid option, the error message and command format are displayed on the screen. This error is not output to the log file.

If the export operation is terminated by pressing Ctrl+C or Ctrl+Break or the command prompt is closed, an error message to that effect is displayed and processing is terminated.

If an error occurs during export operation, the export operation is terminated at that point. In such a case, re-execute the jamexport command. Data is acquired again from the beginning.

You can export weak association classes, but you cannot import them. For details about weak association classes, see 10.1.3 Types of associations.

(6) Example

jamexport -f "c:\temp\Hardware.csv" -gc HardwareInfo

Part 4: System Definition

10 Basic Knowledge Needed to Use Asset Console

This chapter describes the mechanism of an asset management database and asset statuses that constitute the basic knowledge needed in order to use Asset Console.

10.1 Asset management database

This section describes the mechanism of an asset management database, as part of the knowledge needed to run Asset Console.

You need a basic understanding of an asset management database in order to do the following:

Use the jamimport command to register (import) CSV data into the asset management database

Use the jamexport command to output (export) CSV data from the asset management database

Change the managed items in windows (Customize Managed Items)

Change window operations (Customize Job Windows)

Add job menus (Create User Report)

Assign ITDM2 management information to managed items (Assigning ITDM2 management information)

An asset management database employs an object-oriented data management model that associates asset information with supported classes and properties.

This section provides an overview of the classes and properties that are managed by the asset management database.

10.1.1 Classes managed by the asset management database

The asset management database is used to manage two classes, the object class and the association class.

Object class

The object class is a set of information managed by Asset Console whose items are classified by categories. It is the unit of input/output operations on the asset management database.

For example, classes HardwareInfo and SoftwareInfo are groups of items that are managed as asset information and that are classified by the Asset type category. They represent a set of hardware information and a set of software information, respectively. The figure below shows the object class concept.

Figure 10‒1: Object class concept

Association class

The association class represents the relationships (associations) between object classes.

For example, PC information is associated with information such as the PC's asset number and user name (AssetInfo class), manufacturer and specifications (HardwareInfo class), and IP address (NetworkInfo class). In this case, HardwareLink and NetworkLink that indicate associations between individual information items are the association classes. The figure below shows the association class concept.

Figure 10‒2: Association class concept

For details about the relationship between classes, see 20.1.3 Relationships between classes.

10.1.2 Properties managed by the asset management database

The classes managed by the asset management database have attributes called properties. By setting details about classes for these properties, you can accurately manage asset items.

As class attributes, for example, the AssetInfo object class that defines asset information has properties AssetKind and GroupName. The asset type and group are defined for these properties, respectively.

For details about the class properties supported by the asset management system, see Chapter 20. Management Information Details.

10.1.3 Types of associations

Association classes designate the two types of relationship between object classes. These are, relationship by the same key property and relationship by different key properties.

Some association classes have a master-slave relationship (Weak association).

This section describes the relationships between object classes that are indicated by association and weak association.

Relationship by the same key property

For example, the association class HardwareLink indicates the relationship between asset information AssetInfo and hardware information HardwareInfo. The key property of both object classes is AssetID.

Because AssetInfo and HardwareInfo always have a one-to-one correspondence, the relationship between these two object classes can be represented by AssetID.

For this reason, information defining the relationship between AssetInfo and HardwareInfo (association class information) is not created in the asset management database.

The figure below shows the relationship between object classes that is represented by HardwareLink.

Figure 10‒3: Relationship by the same key property

Relationship by the different key properties

For example, the association class ContractLeaseLink indicates the relationship between contract information Contract and asset information AssetInfo. Their key properties are ContractID and AssetID, which are not the same.

This is because when multiple devices are contracted as a group, multiple AssetInfos are associated with a single Contract.

In the asset management database, information defining the relationship between two object classes is created (as an association class) using different key properties.

The figure below shows the relationship between the object classes represented by ContractLeaseLink:

Figure 10‒4: Relationship by different key properties

Master-slave relationship (weak association)

Two different classes are represented by a master-slave relationship. In this relationship, deleting the master class automatically deletes the slave class (weak class).

HardwareLink is an example of an association class that indicates a master-slave relationship. When the asset is hardware, the asset information class AssetInfo is associated with the hardware asset class HardwareInfo. This means that there is an asset, and that it has hardware information as its additional information. Therefore, AssetInfo is the master class and this master class has a weak association with HardwareInfo, which is the slave class.

For details about the master-slave relationship between object classes, see 20.1.3 Relationships between classes.

10.2 Management of asset status

Asset Console manages the status of devices, contracts, software programs, and errors. You can set the applicable statuses at the time of registration and change them from windows at any time during operation.

For devices, contracts, and software programs, the following statuses are pre-defined, but you can add new statuses as appropriate for your jobs:

Device statuses

Active, Stock, Restore, Scrap, Pre-Scrap, Erase

Contract statuses

Under contract, Expire, Erase

Software statuses

Active, Restore, Scrap, Erase

Maintenance statuses

Wrong, Informed, Under repair, Complete

The statuses are managed by codes in the asset management database.

The device, contract, and software statuses are classified into the Active, Scrap, and Erase categories, and a target job is determined by category. When adding a status, note the range of the code to be added.

When changing statuses, note that asset information in Erase status is deleted by the Data maintenance task that has been registered in Windows Task Scheduler.

The following table shows the correspondence between the categories of device, contract, and software statuses and the jobs subject to search:

Device status

Category

Code range

Default status

Target job

Active

--

000 to 499

--

Jobs under the Device Management job category

Used

000 to 299

002: Active

Not used

300 to 499

301: Stock

Jobs under the Device Management job category (other than Unused Device List).

Scrap

--

500 to 719

--

Device Totals#

Device List#

Batch Update

Add Related Device#

Restore

500 to 599

501: Restore

Scrap

600 to 699

601: Scrap

Pre-Scrap

700 to 719

701: Pre-Scrap

Erase

999

999: Erase

Device Totals#

Device List#

Batch Update

Add Related Device#

Legend:

--: Not applicable

#

Applicable only when Status to display in device search windows is set to Display all codes in Basic Information in the Server Setup dialog box.

Contract status

Category

Code range

Default status

Target job

Active

000 to 499

001: Under contract

Contract List

Expire

500 to 998

501: Expire

Contract List#1

Erase

999

999: Erase

Contract List#2

#1

No target device can be added.

#2

Deleted if the Data maintenance task that has been registered in Windows Task Scheduler is executed.

Software stats

Category

Code range

Default status

Target job

Active

000 to 499

001: Active

Jobs under the Software License job category

Scrap

500 to 998

501: Retore

601: Scrap

Software List#1

Erase

999

999: Erase

Software List#2

#1

Searched if Restore or Scrap is specified as the search condition.

#2

Searched if Erase is specified as the search condition.

The information is also deleted if the Data maintenance task registered in Windows Task Scheduler is executed.

For details about adding statuses, see 16.8 Adding and changing types and statuses (Code).

11 Changing the Window Operations and User Roles

This chapter explains how to change window operations and user roles. These changes are executed from the System Definition job category.

Note that only the administrator can change window operations and user permissions.

11.1 Changing user roles (Role)

You use this job to set the range of permitted functions and accessible information as appropriate for different user jobs by changing the scope of accessibility depending on the user role. You also use this job to set new user roles.

You execute a user role change from the Role window displayed by clicking the Role job menu. The figure below shows the Role window.

Figure 11‒1: Role window

This window lists the user roles that are currently registered.

11.1.1 Adding a new user role

To add a new user role:

In the Role window, click the Add button.

The Add Role dialog box appears.

Role ID

Specify a unique ID for each role. This item is mandatory.

Role name

Specify a name for the new role. A role with the same name cannot be created more than once. When this item is omitted, the specified Role ID is set as the role name.

Managed label

This item is set when accesses are to be limited by group level.

For example, to enable the users covered by the new role to handle only the information that belongs to their section and subsections, set the same managed label as for the section. If no managed label has been set for a section, use the Group and User window to set managed labels.

For details about setting access permissions by group level, see 5.1.3 Assigning access permissions according to organizational hierarchy.

To cancel, click the Close button.

Click the OK button.

The new role is added based on the specified information.

The added role is set to be able to access all job menus. To limit the accessible job menus, use the Customize Job Menu window.

For details about using the Customize Job Menu window, see 11.4 Changing the executable jobs (Customize Job Menu).

The figure below shows the Add Role dialog box in which the information to be registered is specified.

Figure 11‒2: Add Role dialog box

11.1.2 Changing the settings for a user role

To change the contents of a user role, in the Role window, click the Role ID link for the appropriate role. The Role Details dialog box appears that enables you to change settings.

If Role name was omitted, the specified Role ID is set as the role name. For details about specifying each item, see 11.1.1 Adding a new user role.

In the Role Details dialog box, click the Delete button to delete the selected role. To delete multiple roles simultaneously, select their check boxes in the Role window, and then click the Delete button.

11.1.3 Deleting a user role

To delete a user role, select the check box of the Role ID to be deleted in the Role window, and then click the Delete button.

Note that the role of administrator cannot be deleted. A user role cannot be deleted if there is a user with that user role.

11.2 Changing managed items (Customize Managed Items)

You use this job to specify the view/hide setting for items in windows and to change their names. You can improve efficiency by hiding items that are not used and by renaming items to facilitate management.

Changes to the managed items take effect globally regardless of the user permissions.

To change managed items, start from the Customize Managed Items window, which is displayed by clicking the Customize Managed Items job menu. The figure below shows the Customize Managed Items window.

Figure 11‒3: Customize Managed Items window

The managed items are managed as class properties in the asset management database. To change a managed item, you change the properties of the corresponding class.

The Customize Managed Items window lists the managed class names corresponding to the managed classes. In Managed class, clicking the link of the class you want to change displays a list of properties. You can then change the view/hide settings and names.

For details about the effects of editing each property on window operations, see the documentation explaining the managed items for each window (ScreenItemList.pdf). ScreenItemList.pdf is stored at the following location:

Asset-Console-installation-folder\help

11.2.1 Changing the items to be managed

In each window operation, you can specify items in the search condition and hide the items displayed in the search and totaled results to exclude them from the managed target. You can also add required items. Note that even when an item is removed from the management range, information about it will still be managed in the asset management database.

To set the hide/view setting for a managed item, use the Show check box for the applicable property. Note that you cannot hide managed items that are required for jobs.

The procedure for hiding a managed item is shown below using an example of removing a device's machine type (desktop or notebook) from the management range.

To hide a managed item:

Click the link for the class name HardwareInfo in the hardware information.

The following Property List for the hardware information is displayed:

Figure 11‒4: Property List for the hardware information

Clear the check Show box for the property named ModelKind, which indicates the machine type.

Click the Update button.

The machine type of the device is removed from the management range and will no longer be displayed in windows.

For details about the properties named User property, see 11.2.3 Adding managed items.

11.2.2 Renaming managed items

You can rename the items that are specified for search conditions, and rename the items displayed as search and totaled results in each window.

The procedure for renaming a managed item is shown below using an example of renaming Developer to Maker.

To rename a managed item:

Click the link for the class name HardwareInfo in the hardware information.

The hardware information Property List dialog box shown above is displayed.

Click the link for the developer's property name Developer.

The following Edit Property dialog box appears:

Figure 11‒5: Edit Property dialog box (Developer)

In Display name, specify the new name Maker.

Click the OK button.

The Edit Property dialog box closes, and the name Developer is changed to Maker in the Property List.

Note

At this point, this change has not been applied to the asset management database. If you now select another job menu or you exit the Web browser, the change is discarded.

Click the Update button.

The change is applied to the asset management database.

Note

If you rename a managed item, the condition provided in the sample of the Import job menu becomes disabled. Therefore, you must create a new import condition for the Import job menu.

11.2.3 Adding managed items

By adding unique managed items, you can extend the asset management jobs that you execute from windows.

To add managed items, use the property user property that is provided for extension purposes. There are five types of user property depending on the type of manageable information. Select the appropriate type for the information to be added:

User property fieldxxx

You use this item to manage information up to the bytes indicated by xxx. The value of xxx is expressed as alphanumeric characters, double-byte characters, and symbols.

User property area

You use this item to manage information up to 255 bytes in length. In the window, the column displayed for entering such a value consists of multiple lines. The value is expressed as alphanumeric characters, double-byte characters, and symbols.

User property code

You use this item to manage information up to 64 bytes in length. This type associates a code with information to be referenced by the code, such as a status or type. The value is expressed as alphanumeric characters.

This item is displayed as a drop-down list in search conditions. A value to be specified and the corresponding display value are set in the Code window. For details about using the Code window, see 16.8 Adding and changing types and statuses (Code).

User property uint

You use this item to manage a numerical value up to 10 bytes in length. The value is expressed as numeric characters.

User property date

You use this item to manage a date of up to 8 bytes in length. The value is expressed as alphanumeric characters.

Shown below are examples of adding managed items for User property field xxx, User property area, User property code, User property uint, and User property date.

(1) Example of adding a managed item (for user property field xxx)

To add managed item Group to the asset information in order to manage assets in groups:

In Managed class, click the AssetInfo link.

The property list for AssetInfo appears.

In Property, click the link for UserPropertyField128_1.

The following Edit Property dialog box appears:

Figure 11‒6: Edit Property dialog box (UserPropertyField128_1)

In the Display name column, enter Group, and then click the OK button.

The Edit Property dialog box closes, and in the list of properties, User property Field128-1 changes to Group.

Note

At this point, this change has not been applied to the asset management database. If you now select another job menu or you exit the Web browser, the change is discarded.

Select the Show check box for UserPropertyField128_1.

The added managed item Group is now displayed in windows.

Click the Update button.

The change is applied to the asset management database.

(2) Example of adding a managed item (for user property area)

To add managed item Details to the maintenance log in order to manage detailed information:

In Managed class, click the Maintenance link.

The property list for Maintenance appears.

In Property, click the link of UserPropertyArea_1.

The Edit Property dialog box shown previously appears.

In the Display name column, enter Details, and then click the OK button.

The Edit Property dialog box closes, and in the list of properties, User property Area-1 changes to Details.

Note

At this point, this change has not been applied to the asset management database. If you now select another job menu or you exit the Web browser, the change is discarded.

Select the Show check box for UserPropertyArea_1.

The added managed item Details is now displayed in windows.

Click the Update button.

The change is applied to the asset management database.

(3) Example of adding a managed item (for user property code)

To add managed item Replace to the hardware information in order to manage the devices that are to be replaced:

In Managed class, click the HardwareInfo link.

The property list for HardwareInfo appears.

In Property, click the link of UserPropertyCode_1.

The Edit Property dialog box shown previously appears.

In the Display name column, enter Replace, and then click the OK button.

The Edit Property dialog box closes, and in the list of properties, User property Code-1 changes to Replace.

Note

At this point, this change has not been applied to the asset management database. If you now select another job menu or you exit the Web browser, the change is discarded.

Select the Show check box for UserPropertyCode_1.

The added managed item Replace is now displayed in windows.

Click the Update button.

The change is applied to the asset management database.

Next, add the value for the added managed item Replace (Yes or No) from the Code window, which is displayed by clicking the Code job menu.

For details about adding codes that are to be associated with Yes and No, see 16.8.1 Adding codes.

(4) Example of adding a managed item (for user property uint)

To add managed item RentalFee to the asset information in order to manage detailed information:

In Managed class, click the AssetInfo link.

The property list for AssetInfo appears.

In Property, click the link of UserPropertyUint_1.

The Edit Property dialog box shown previously appears.

In the Display name column, enter RentalFee, and then click the OK button.

The Edit Property dialog box closes, and in the list of properties, User property uint-1 changes to RentalFee.

Note

At this point, this change has not been applied to the asset management database. If you now select another job menu or you exit the Web browser, the change is discarded.

Select the Show check box for UserPropertyUint_1.

The added managed item Rental Fee is now displayed in windows.

Click the Update button.

The change is applied to the asset management database.

(5) Example of adding a managed item (for user property date)

To add the managed item RentalStartDate to the asset information in order to manage detailed information:

In Managed class, click the AssetInfo link.

The property list for AssetInfo appears.

In Property, click the link of UserPropertyDate_1.

The Edit Property dialog box shown previously appears.

In the Display name column, enter RentalStartDate, and then click the OK button.

The Edit Property dialog box closes, and in the list of properties, User property date-1 changes to RentalStartDate.

Note

At this point, this change has not been applied to the asset management database. If you now select another job menu or you exit the Web browser, the change is discarded.

Select the Show check box for UserPropertyDate_1.

The added managed item RentalStartDate is now displayed in windows.

Click the Update button.

The change is applied to the asset management database.

11.2.4 Changing the names and view/hide settings for buttons and tabs

You can change the names and view/hide settings for the buttons and tabs that are displayed in windows.

The names and view/hide settings for buttons and tabs are managed as VariousInfo together with the list headers and search conditions that do not correspond to class properties.

VariousInfo contains the following items:

Button (text for button)

This is the text for a button that is displayed in windows (such as Search button).

ConditionText (text for search condition)

This is the text for a search condition that does not correspond to any class property (such as Totals by).

Text_ListHDR (text for list header)

This is the text for a list header that does not correspond to any class property (such as IP address range).

Text_TAB (text for tab)

This is the text for a tab that is displayed in windows (such as Group and Location).

Text_Title (dialog box title)

This is the dialog box title (such as Inbox).

Notes

Renaming of a dialog box using this item has nothing to do with the renaming of a job menu using the job menu Customize Job Menu.

Renaming a dialog box using this item has no effect on the Window name in the Customize Job Windows window.

ValueText (text for other items)

This is the text for other items that do not correspond to any class property.

To rename the PDF button to Print Form:

Click the link for the managed class VariousInfo.

The window elements contained in VariousInfo are listed.

Click the link for the managed class Button.

A list of buttons appears.

Click the PDF link for the property.

The Edit Property dialog box appears.

In Display name, specify the new name Print Form.

Click the OK button.

The Edit Property dialog box closes. In the list of properties, the name changes from PDF to Print Form.

Note

At this point, this change has not been applied to the asset management database. If you now select another job menu or you exit the Web browser, the change is discarded.

Click the Update button.

The change is applied to the asset management database.

This change takes effect globally on the windows of all user roles.

Displaying the buttons that are hidden by default

Customize Managed Items enables you to display the buttons that are hidden by default.

When you display the Deletion2 or Deletion3 button, both of which are hidden by default, the button is displayed in the window operations listed below.

Deletion2

Device Details dialog box

Delete button

Contract List window

Delete button

Contract Details dialog box

Delete button

Volume License List dialog box

Delete button

Volume License Details dialog box

Delete button

Deletion3

Contract History dialog box

Delete (History Information) button

An item that is set to be displayed in Customize Managed Items is displayed in the windows of all user roles. To display it only for a specified user role, first specify the settings in Customize Managed Items, and then specify the settings using Customize Job Windows. For details about changing window settings from Customize Job Windows, see 11.3 Changing a window for a user role (Customize Job Windows).

11.3 Changing a window for a user role (Customize Job Windows)

You use this job to change the components of a window (such as buttons, search conditions, and editable items) for a particular user role.

For example, you can hide the Update button or editable items in the Contract Details dialog box so that general users cannot update contract information. You can also change the display order of search conditions and editable items.

Customize Job Windows enables you to easily customize job settings windows as appropriate for different user roles. Note that the items being managed are set based on the settings in the Customize Managed Items window.

To change windows according to a user role, start from the Customize Job Windows window, which is displayed by clicking the Customize Job Windows job menu. The figure below shows the Customize Job Windows window.

Figure 11‒7: Customize Job Windows window

The Customize Job Windows window lists the names of the jobs displayed in a job menu, the windows used by each job, and the form set for each window (settings for customizing each window).

In the Window name list, clicking the link for a window displays the Customize Job Windows - Edit Form window that enables you to change the tasks to be executed from that window.

This section describes the form settings (such as the view/hide settings for buttons and search conditions). It also explains how to create new forms and how to change and delete form names.

11.3.1 Setting a form

Customize Job Windows enables you to specify desired changes to the form for a window.

The following points should be noted about the form setup method and how to set a form:

There must be a form for each window. The same form cannot be shared among multiple windows, because each window has its own organization.

A form can have any name.

When you create a form, make sure that only one Customize Job Windows - Edit Form window is open. If you open more than one Customize Job Windows - Edit Form windows to create a form, multiple forms with the same name might be created for the same window depending on how you save the form.

You can set multiple forms for the same window. For example, you can set one form for administrators and a different form for users.

One form can be shared among multiple user roles.

The same user role cannot access multiple forms for the same window. For example, the Administrator role cannot be applied to both Form-1 and Form-2 that have been set for the same window.

The settings that you specify in the Customize Job Windows - Edit Form window will depend on the type of window for which the form is being set. The subsections below explain how to set forms for each type of window.

(1) Procedure for setting a form for a registration or edit window

To set a form in the Customize Job Windows - Edit Form window for a registration or edit window (such as the New Device window) (steps 1 through 3 can be executed in any order):

Set Object role.

Set the user role to which the form is to be applied. For details about setting the role, see 11.3.2 Setting the object role.

Set Button.

Set the view/hide settings for the buttons. For details about how setting buttons, see 11.3.3 Setting the buttons to be used.

Set Editable items.

Set the items to be displayed in the window, the editable items, and the order of the items. For details about setting the editable items, see 11.3.4 Setting items to be displayed as editable items.

When you finish setting all the items, click the OK button.

The settings are applied to the window corresponding to this form, and then the Customize Job Windows - Edit Form window closes.

The figure below shows the Customize Job Windows - Edit Form window for a registration or edit window.

Figure 11‒8: Customize Job Windows - Edit Form window for a registration or edit window

(2) Procedure for setting a form for a search or summation window

To set a form in the Customize Job Windows - Edit Form window for a window (such as the Device List window) used for searching or totaling (steps 1 through 4 can be executed in any order):

Set Object role.

Set the user role to which the form is to be applied. For details about setting the role, see 11.3.2 Setting the object role.

Set Button.

Set the view/hide settings for the buttons. For details about setting buttons, see 11.3.3 Setting the buttons to be used.

Set Search condition.

Set the view/hide settings and the order of the search conditions. For details about setting the search conditions, see 11.3.5 Setting items to be displayed as search conditions.

Set Search result.

Set the items to be displayed in the search results list, their display order, and the display width for each item.

Changing the order or the view/hide settings for the items in the totaled results list does not change the key items for totaling.

For details about setting the search results, see 11.3.6 Setting the items to be displayed in search results.

When you finish setting all the items, click the OK button.

The settings are applied to the window corresponding to this form, and then the Customize Job Windows - Edit Form window closes.

The following figure shows the Customize Job Windows - Edit Form window for a search or totals window.

Figure 11‒9: Customize Job Windows - Edit Form window for a search or totals window

(3) Procedure for setting a form for a breakdown window displayed from totaled results

To set a form in the Customize Job Windows - Edit Form window for a breakdown window that is displayed from totaled results (such as a window displaying a breakdown of device types by group or location that is displayed from totaled results from the Device Totals window) (steps 1 through 3 can be executed in any order):

Set Object role.

Set the user role to which the form is to be applied. For details about setting the role, see 11.3.2 Setting the object role.

Set Button.

Set the view/hide settings for the buttons. For details about setting buttons, see 11.3.3 Setting the buttons to be used.

Set Search result.

Set the items to be displayed in the search results list, their display order, and the display width for each item.

Changing the order or the view/hide settings for the items in the totaled results list does not change the key items for totaling.

For details about setting the search results, see 11.3.6 Setting the items to be displayed in search results.

When you finish setting all the items, click the OK button.

The settings are applied to the window corresponding to this form, and then the Customize Job Windows - Edit Form window closes.

The figure below shows the Customize Job Windows - Edit Form window for a breakdown window that is displayed from totaled results.

Figure 11‒10: Customize Job Windows - Edit Form window for a breakdown window that is displayed from totaled results

11.3.2 Setting the object role

To set the user role to which a form is to be applied, use Object role in the Customize Job Windows - Edit Form window.

The following shows Object role in the Customize Job Windows - Edit Form window.

Figure 11‒11: Object role in the Customize Job Windows - Edit Form window

To set the object role, select the desired user role from the Do Not Apply list, and then click the Apply button. To apply all user roles, click the Apply All button.

The selected user role is moved to the Apply list, and the object role is set.

To remove a user role from the object roles, select it from the Apply list and then click the Do Not Apply button. To remove all user roles, click the Do Not Apply Any button.

When creating multiple forms for a single window

Each user role can access only one form in a window. If a form has already been applied to a user role, the form name is displayed in square brackets immediately following the role name.

You can apply a user role that has already been set as an object role to another form. However, this user role will automatically be removed from the object role for the initial form.

11.3.3 Setting the buttons to be used

To set the buttons to be used in a window, use Button in the Customize Job Windows - Edit Form window.

The following shows Button in the Customize Job Windows - Edit Form window.

Figure 11‒12: Button in the Customize Job Windows - Edit Form window

To set buttons to be used in window operations, select the desired buttons from the Hide list and click the Show button. To use all listed buttons, click the Show All button.

The selected button is moved to the Show list and becomes enabled.

To hide a button, select it from the Show list, and then click the Hide button. To hide all buttons, click the Hide All button.

11.3.4 Setting items to be displayed as editable items

You can specify whether items are to be viewed and whether items are to be editable in the windows for registering new asset information and in dialog boxes for editing information. To specify these settings, use Editable items in the Customize Job Windows - Edit Form window.

The following shows Editable items in the Customize Job Windows - Edit Form window.

Figure 11‒13: Editable items in the Customize Job Windows - Edit Form window

The Hide list shows the items that can be set to be editable in each window operation. Each item is shown in the format item-name (class-name).

In the Show list, the items with the gray background cannot be hidden or cannot be changed to read-only because they are default system items.

(1) Setting the view/hide settings for editable items

You can hide information that you do not want to disclose to a user role or that are not related to jobs that can be executed by a user role.

To set items to be displayed as editable items, select them from the Hide list and click the Show button. To display all items, click the Show All button.

The selected item is moved to the Show list and set to be displayed.

To hide an item, select it from the Show list, and then click the Hide button. To hide all items, click the Hide All button.

Note

Editable items enables you to set only those items that are set to be available to Customize Managed Items. To add items that can be set in Editable items, evaluate the settings in the Customize Managed Items window.

For details about changing the items to be managed, see 11.2.1 Changing the items to be managed.

(2) Setting the display order of editable items

The editable items are displayed in the order that they are listed in Show. You can change this display order, such as by displaying the mandatory items at the top.

To change the display order of an editable item, select it from the Show list, and then click the Up or Down button.

You cannot change the display order of multiple items at the same time. You must change items one at a time.

(3) Setting editable items to read-only

Editable items displayed in the Show list can be set to read-only (uneditable). You can avoid erroneous operations by making those items uneditable that do not need to be updated or that should not be updated by general users.

To set an editable item to read-only, select it from the Show list, and then select the Read-only check box.

The read-only editable items are displayed in red.

11.3.5 Setting items to be displayed as search conditions

You can set the search conditions that are displayed in the windows for searching or summing up asset information. To specify settings for search conditions, use Search condition in the Customize Job Windows - Edit Form window.

The following shows Search condition in the Customize Job Windows - Edit Form window.

Figure 11‒14: Search condition in the Customize Job Windows - Edit Form window

In the Show list, the items with the gray background cannot be hidden.

(1) Setting the view/hide settings for search conditions

To set items to be displayed as search conditions, select them from the Hide list and click the Show button. To display all items, click the Show All button.

The selected item is moved to the Show list and set to be displayed.

To hide an item, select it from the Show list, and then click the Hide button. To hide all items, click the Hide All button.

Note

Search condition enables you to set only those items that are set to be available to Customize Managed Items. To add items that can be set in Search condition, evaluate the settings in the Customize Managed Items window.

For details about changing the items to be managed, see 11.2.1 Changing the items to be managed.

(2) Setting the display order of search conditions

The search conditions are displayed in the order that they are listed in Show. You can change this display order, such as by displaying the frequently used items at the top.

To change the display order of a search condition, select it from the Show list, and then click the Up or Down button.

You cannot change the display order of multiple items at the same time. You must change items one at a time.

11.3.6 Setting the items to be displayed in search results

You can set the items to be displayed in listings of asset information search or summation results, their display order, and the display widths. To specify these settings, use Search result in the Customize Job Windows - Edit Form window.

The following shows Search result in the Customize Job Windows - Edit Form window.

Figure 11‒15: Search result in the Customize Job Windows - Edit Form window

(1) Setting the view/hide settings for search results

To set items to be displayed in the search results list, select them from the Hide list and click the Show button. To display all items, click the Show All button.

The selected item is moved to the Show list and set to be displayed.

To hide an item, select it from the Show lists and then click the Hide button. To hide all items, click the Hide All button.

Note

Search result enables you to set only those items that are set to be available to Customize Managed Items. To add items that can be set in Search result, evaluate the settings in the Customize Managed Items window.

For details about changing the items to be managed, see 11.2.1 Changing the items to be managed.

(2) Setting the display order of search results

Items are displayed in search results from left to right in the order that they are listed in the Show list. You can change this display order, such as by displaying the more important items on the left side.

To change the display order in search results, select a desired item from the Show list, and then click the Up or Down button. To move the item to the left, use the Up button. To move it to the right, use the Down button.

You cannot change the display order of multiple items at the same time. You must change items one at a time.

(3) Setting the display widths for the items in search results

You can set the display widths for the items that are displayed in Search result. You can reduce the display width if the default width is too large, or you can turn off wrap-around mode.

To set a display width in search results, select the desired item from the Show list, and then enter a numeric value in the range 0 to 999 (pixels). If 0 is specified, or if no value is specified, the display width is automatically adjusted according to the screen size.

If you want to change the display width of items selected by Point of totals from the total results of the Device Totals window, set the display width of the Device type (Hardware information) display item. If anything other than Device type is selected by Point of totals, it will be displayed at this width.

11.3.7 Adding forms

You can set multiple forms for the same window. For example, you can set one form for administrators and a different form for users.

There can be only one form for each user role for a window. For example, Form-1 and Form-2 that are for the same window cannot both apply to the Administrator role. Each form for the same window must be for a different user role.

To add a new form:

In the Customize Job Windows - Edit Form window, click the Add Form button.

The dialog box for specifying a form name appears.

You can set any form name. However, the same window cannot have multiple forms with the same name.

To cancel, click the Cancel button.

Specify a form name, and then click the OK button.

A tab is added for setting the new form with the specified name.

Set the form using the items in the Customize Job Windows - Edit Form window.

11.3.8 Copying a form

You can add a form by copying an existing form. This is useful when you want to add limitations on the basis of an existing form.

To copy an existing form:

In the Customize Job Windows - Edit Form window, select the form you wish to copy.

Click the Copy Form button.

The dialog box for specifying a name for the new form appears.

You can set any form name. However, the same window cannot have multiple forms with the same name.

To cancel, click the Cancel button.

Specify a form name, and then click the OK button.

Note that the only settings for Object role are reset.

Set the form using the items in the Customize Job Windows - Edit Form window.

11.3.9 Renaming a form

To rename an existing form:

In the Customize Job Windows - Edit Form window, click the Rename Form button.

The dialog box for renaming the form appears.

You can set any form name. However, the same window cannot have multiple forms with the same name.

To cancel, click the Cancel button.

Specify the new name for the form, and then click the OK button.

The form is renamed to the specified name.

To cancel, click the Cancel button.

Click the OK button.

The change is applied to the window.

11.3.10 Deleting a form

This subsection explains how to delete all created forms in a batch operation and how to delete specific forms.

(1) Deleting all forms in a batch operation

To delete all created forms to initialize the window settings, from the Customize Job Window, click the Initialize Form button.

(2) Deleting specific forms

To delete specific forms:

In the Customize Job Windows - Edit Form window, select the form you wish to delete.

Click the Delete Form button.

A confirmation dialog box appears.

To cancel, click the Cancel button.

Click the OK button.

The selected form is deleted.

If all forms are deleted, the initial Form-1 is displayed the next time this window is opened.

To cancel, click the Cancel button.

Click the OK button.

The form is deleted from the window.

11.4 Changing the executable jobs (Customize Job Menu)

By specifying the view/hide settings for the job menus, you can change the available jobs according to the user permissions. You can also rename job menus and add new job categories.

To assign jobs by user role, start from the Customize Job Menu window, which is displayed by clicking the Customize Job Menu job menu. The figure below shows the Customize Job Menu window.

Figure 11‒16: Customize Job Menu window

This window uses a separate tab to display the job menus and settings that are available to each user role.

11.4.1 Changing the executable jobs

You use this job to change the jobs assigned to a user role. Note that this job of assigning jobs cannot be performed by any user other than the administrator.

This subsection describes how to assign jobs by user role by way of example.

To change the settings so that only the administrator can execute New Device:

Click the User tab.

The window for assigning user jobs appears.

Clear the Show check box for New Device.

New Device disappears from the left-hand preview area.

Note

At this point, this change has not been applied to the asset management database. If you now select another job menu or you exit the Web browser, the change is discarded.

Click the Update button.

The New Device job menu is no longer displayed in windows for the general users user role.

To make the New Device job menu available again, select its Show check box.

If the Show check box for an entire job menu, such as Device Management, is cleared, all the job menu items belonging to that menu will be hidden.

Show/Hide the Item job category

When the Item job category is displayed, the Inbox and Outbox job categories, which are under the Item job category, display without fail.

11.4.2 Renaming a job menu

This section describes the procedure for renaming a job menu using an example of renaming Device Management to Hardware Management.

Click the Device Management link under Job name.

The dialog box for renaming a job appears as shown below:

Figure 11‒17: Dialog box for renaming a job

In Job name, enter Hardware Management, and then click the OK button.

The job name in the left-hand preview area changes from Device Management to Hardware Management.

Note

At this point, this change has not been applied to the asset management database. If you now select another job menu or you exit the Web browser, the change is discarded.

Click the Update button.

The change is applied to the asset management database, and the job menu is changed.

If you rename a job menu, the change also takes place for other user roles.

Note

Renaming a job menu has no effect on the name of the window that is used by each job. To rename a window, use the Customize Managed Items job menu. For details about how to rename windows, see 11.2.4 Changing the names and view/hide settings for buttons and tabs.

11.4.3 Adding job categories

There are several job menus, such as Device Management and Contract Management. In addition to the default job menus, you can add job menus Job to Customize 1 through Job to Customize 8.

You can display your new job menus by registering user reports that you create in job menus Job to Customize 1 through Job to Customize 8. This capability is useful for managing user reports in separate categories from the default job menus.

For details about registering user reports, see 11.5.8 Registering a created user report.

You can change the job menu names for the added job menus in the same manner as for the default job menus.

11.5 Adding windows for routine jobs (Create User Report)

In addition to the windows provided by Asset Console, you can add windows for searching unique information (user reports).

As a user report, you can create a window for searching the asset information managed in the asset management database and displaying the results. A window for registering or summing up data cannot be created.

You can display added windows from added job menus in the same manner as with other windows. You can also assign them by user role using the Customize Job Menu window.

To add a window, start from the Create User Report window, which is displayed by clicking the Create User Report job menu.

The figure below shows the Create User Report window.

Figure 11‒18: Create User Report window

From this window, you can start the creation of user reports. To create a new user report, click the Add button.

To edit an existing user report, select it from the job menu tree, and then click the Edit button. To delete an existing user report, select it from the job menu tree, and then click the Delete button.

You can execute a created user report from the command line. If you execute a user report from the command line, you should use variable names that are easy to remember as arguments when you define search conditions.

This section describes the procedure for creating a user report.

The following figure shows the user report creation procedure.

Figure 11‒19: Procedure for creating a user report

To create a user report according to a provided example, see 11.5.12 Example of creating a user report.

11.5.1 Selecting a search method

In the window that is displayed by clicking the Add button in the Create User Report window, you select a search method appropriate to the information to be searched for in the window.

From the items displayed in the search method specification field, select the desired search method, and then click the Next button.

The following figure shows the search method specification field.

Figure 11‒20: Search method specification field

(1) Types of search methods

There are three ways to search asset information in the asset management database:

Class search

This method searches information in only one class.

Associated class search

This method searches information in classes that are associated by association class.

Joined class search

This method searches information in classes that are not associated by association class. Use this method when you are defining an association between new classes for searching information or associating more than two classes for searching information.

(2) Procedure for determining the search method

The following figure shows the procedure for determining the search method.

Figure 11‒21: Procedure for determining the search method

For details about classes and the relationship between classes, see Chapter 20. Management Information Details.

11.5.2 Specifying classes to be searched

After selecting the search method, specify the classes that contain the target information.

When Class search was selected as the search method

From the target object class specification field, select the class that contains the target information.

The following figure shows the target object class specification field.

Figure 11‒22: Target object class specification field

When Associated class search was selected as the search method

From the target association class specification field, select the class that contains the target information.

The following figure shows the target association class specification field.

Figure 11‒23: Target association class specification field

When Joined class search was selected as the search method

In the class join method specification field, select Association class or Specify class, and then specify the class that contains the target information.

The following figure shows the class join method specification field.

Figure 11‒24: Class join method specification field

For details about how to specify classes when Joined class search is selected, see 11.5.9 Specifying a class join method.

11.5.3 Defining search conditions

To define search conditions, use each item on the Screen tab.

The following shows the Screen tab.

Figure 11‒25: Definition items for search conditions (Screen tab)

Show

Specify whether each search condition is to be displayed in the window. Selecting a check box enables the corresponding search condition to be specified in the window.

When a check box is selected, the Value field is disabled.

Column

Specify the information to be searched for. The drop-down list displays information in the format class-name.property-name.

Condition code

Specify one of the conditional expressions listed below that indicates the relationship between the property specified in Column and the value specified in Value.

The following table lists the conditional expressions.

Table 11‒1: List of conditional expressions

Conditional expression

Data type of property specified in Column

Character string displayed in user report or drop-down list

=

--

equal

!=

--

not equal

<

--

less than

<=

--

less than or equal to

>

--

greater than

>=

--

greater than or equal to

LIKE

--

including

NOT_LIKE

--

not including

OPTIONS

Date

before

after

Numeric value

not greater than

not less than

Character string

match all the words

match part of the words

match beginning of the words

match end of the words

Legend:

--: Not applicable

When a group or location is specified as the search condition, information is always searched based on right truncation.

Value

Specify the value determined for the information specified in Column.

When the Show check box is selected to specify the value in the window, this field is disabled

If the property value is defined as a code, specify the code.

Condition

Specify AND or OR to connect the search items when multiple search items are to be set.

Parentheses

Specify parentheses to enclose multiple search items. Note that double parentheses are not permitted.

Add button

Click this button to add a field for specifying a search item.

Defining the variable names to be used as arguments

To execute the same search as for the created user report, specify the conditions that are specified by window operation as arguments. In this case, each search condition is represented by a variable name.

On the Command Argument tab, you can change the variable names that are used when you specify arguments to names that are easy to remember.

The following figure shows the Command Argument tab.

Figure 11‒26: Definition items for search conditions (Command Argument tab)

Define the variable names corresponding to the search conditions whose Show check boxes are selected on the Screen tab. By default, Variantn (n: sequential number beginning at 1) is set.

A permitted variable name consists of 1 to 32 bytes of alphanumeric characters and is case sensitive. The same variable name cannot be specified more than once.

If you specify OPTIONS in Condition code on the Screen tab, = is displayed in Condition code on the Command Argument tab.

11.5.4 Setting the output items

You use the output item specification fields to set the items to be output to the search results list.

The following figure shows the output item specification fields.

Figure 11‒27: Output item specification fields

The information that can be specified in Output Items is displayed according to the class specified as the search target. Select the check boxes of the items that you want to output to the search results list.

Settings for displaying details from the search results list

You can make a setting to display a dialog box containing details from the search results list, as is the case with the search results of Device List.

The dialog boxes that can be displayed from a search results list are Device Details, Installed Software Details, and Contract Details.

If you are specifying Asset No. for asset information and Contract ID for contract information as output items, select either Show details or Hide details.

How to display properties defined as codes

For a property value defined as a code, you can select the display name, value, or both as the information to be displayed for the code as well as the normal display method. For example, in the case of Status, Stock or Active would be its display name, and 1 or 2 would be its value.

11.5.5 Setting the sort order and display width of the output items

On the Screen display information field, set the sort order and display width for the items that are displayed in the list of search results.

The following figure shows the Screen display information field.

Figure 11‒28: Screen display information field

The items are listed from left to right in the order shown in the Show column. To change the sort order, select the item whose order is to be changed from the Show column and then click the Up or Down button.

To change the display width, select the item whose display width is to be changed from the Show column and then in the Width column, specify a numeric value from 0 to 999. The default is 150 pixels.

11.5.6 Specifying whether to include duplicated data in the search results

If the search results contain duplicated data, select whether to output the results as is. You specify this item only when Joined class search is selected as the search method.

The figure below shows the settings for specifying whether search results can contain duplicated data.

Figure 11‒29: Field for specifying whether duplicated data is included

Select either Duplicated data is output or Duplicated data is not output. By default, Duplicated data is output is selected.

11.5.7 Checking the results in the preview window

You use the preview window to check the specified settings, such as the search method, target class, search conditions, output items, and whether duplicated data is to be output.

Clicking the Preview button displays the created window that enables you to execute an actual search for purposes of checking the search results.

If Joined class search was selected for creating a report, the error message An error occurred during script execution or Processing cannot continue due to a database access error might be displayed depending on the join method. Before registering the user report, use the preview window to execute a search and make sure that the correct search results are obtained.

If the message The data size to be registered exceeds the maximum is displayed, the data size for the specified search conditions or items to be output exceeds the upper limit. Reduce the number of search conditions or output items.

11.5.8 Registering a created user report

You must register a created user report. Once registered, the user report is displayed and can be selected from the job menu in the same manner as with other jobs.

To register a user report, use the window that is displayed by clicking the Next button in the window for defining search conditions. The figure below shows the window used to register a user report.

Figure 11‒30: Window for registering a user report

To register a user report:

Select a job category.

From the tree, select the job menu category to which the user report is to be added. If nothing is selected, the user report is added in the same level as the job menu categories.

Set Report name, Form file name, and the applicable roles.

Set the name for the user report, specify whether to output a form in PDF format, and then set the applicable user role.

Report name

Specify a desired name. When this item is omitted, the ID that is assigned automatically is set as the name.

To execute the created user report from the command line, specify a unique name. A user report whose name is duplicated cannot be executed from the command line.

Form file name

To output search results as a form in PDF format, specify the form file (.fms) created by EUR. You must store the form file specified here in Asset-Console-installation-folder\eur.

For details about settings required for outputting a form in PDF format, see 7.3 Setting up the asset management server.

Role

Select the check box for the user role that is to use the created user report. If this item is omitted, the user report will not be added to the job menu.

You can use the Create User Report window or Customize Job Menu window to change the Report name, Form file name, and Role settings for a user report once it has been registered.

Click the Entry button.

The created user report is registered.

Note

If Joined class search was selected in creating the report, the error message An error occurred during script execution or Processing cannot continue due to a database access error might be displayed depending on the join method. Before registering the user report, use the preview window to execute a search and make sure that the correct search results are obtained.

11.5.9 Specifying a class join method

A class join method is specified only when Joined class search is selected. You can define a new class join method and create a window with unique search conditions. The figure below shows the fields for defining a class join method when Joined class search is selected as the search method.

Figure 11‒31: Fields for specifying a class join method

Select one of the two join methods for classes:

Association

Select this method to search the object classes that are associated as association classes.

When this join method is selected, the values of Class name join, Class name join to, and Key property are specified based on the contents of the object classes associated as association classes.

Specify class

Select this method to search the object classes by joining classes that are not associated as association classes.

When this method is selected, drop-down list for specifying Class name join, Class name join to, and Key property are enabled.

Order of Class name join and Class name join to

If you are specifying more than two classes, Class name join and Class name join to must be specified in the correct order. For example, to join classes A and B and then join classes B and C, specify as follows:

Joining classes A and B

Specify class A in Class name join.

Joining classes B and C

Specify class B in Class name join.

If you select Association as the class join method, use the Order button to place Class name join and Class name join to in the correct order.

Adding and deleting key properties

If you need to identify the search target by multiple items, add key properties. There is no need to add key properties if you have selected Association as the class join method.

Clicking the Add Key button displays the fields for specifying key properties, where you can add key properties.

To delete key properties, click the Delete Key button.

Inner join and outer join

Separately from the association between classes, select Join type for classes.

To output information about the device only when it contains the key values of both join source and target, select INNER (inner join).

To output the item as null information even when the join target does not contain the key value of the join source, select OUTER (outer join).

11.5.10 Deleting a user report

To delete a created user report, use the Create User Report window that is displayed by clicking the Create User Report job menu.

In the tree view that displays created user reports, select the user report you wish to delete, and then click the Delete button.

11.5.11 Executing a search from the command line

This subsection gives the function, format, options, return value, notes about command execution, and an execution example of the jamUserReport command, which executes a search using the created user report.

The executable file for the command is stored in the following folder:

Asset-Console-installation-folder\exe

(1) Function

The jamUserReport command executes a search using a user report created by the Create User Report job menu. The search result is output to the standard output in the CSV format.

(2) Format

jamUserReport
      -n "report-name"
      { [ -cv "variable-name=condition-value" [ -cv "variable-name=condition-value" ] ] |
        [ -cf "condition-value-definition-file-name" ] }
      [ -pf "output-file-name" ]

(3) Options

-n "report-name"

Specifies the report name used to execute the search. A report name assigned to multiple reports cannot be specified. This option is mandatory.

-cv "variable-name=condition-value"

Specifies the search condition. The -cv option can specify a condition during a search using a user report. The -cv and -cf options are mutually exclusive. If the specified variable name is undefined or the condition value is omitted, this option is ignored.

variable-name

Specifies the variable name defined on the Command Argument tab in Search condition when a user report was created.

condition-value

Specifies the condition value for the variable. The following describes how to specify the condition value according to the property specified in the search condition:

If the property is managed based on its correspondence with code, specify a display name for the condition value, not a numeric value.

To specify a date, use the format yyyy/mm/dd or yyyy/mm/ddΔhh:mm:ss (Δ indicates a space).

To specify a numeric value, specify a value such as 1000. Do not use commas such as 1,000.

For the hardware information Hard disk sizes and Hard disk free space and the device catalog information Hard disk sizes, specify a value in gigabytes. The search result is output in megabytes.

For the group information, there is no access permissions depending on the login user, such as in window operations.

If the length of a numeric value is predefined, such as an IP address, you can specify as 11.111.111.1 (there is no need to use zeros to adjust the length).

-cf "condition-value-definition-file-name"

Specifies the name of the file that defines the condition value (condition value definition file). The -cf and -cv options are mutually exclusive.

The condition value definition file is useful when frequently used search conditions or multiple search conditions are to be combined.

The following shows the format of the condition value definition file:

variable-name,condition-value
variable-name,condition-value
    :

Specify a variable name in column 1 and condition value in column 2, separated by a comma. Create the file in the CSV format.

-pf "output-file-name"

Specifies the name of the search result output file. If you specify a path, the search result is output to the specified folder. If you specify only a file name, the search result is output to the same folder as for the command's executable file, not the standard output.

If the specified output file name already exists, that file is overwritten. If the command terminates with an error, the contents of the existing file are cleared.

(4) Return value

The command returns the following values.

Return value

Description

0

Normal termination

1

Search result contains no item.

11

Processing was cancelled because the specified command option was invalid.

21

Processing was cancelled because the specified report name was invalid.

22

Processing was cancelled because the specified variable name was invalid.

23

Processing was cancelled because the specified condition value was invalid.

24

Processing was cancelled because the specified condition variable value definition file was invalid.

25

Processing was cancelled because the specified output file was invalid.

31

There is not enough memory.

52

Processing was cancelled by the user.

101 or greater

The command terminated due to other error.

(5) Notes during command execution

A user with administrator permissions must execute the jamUserReport command.

To specify a character string that contains a space in the command's option argument, the entire character string must be enclosed in double quotation marks (").

(6) Execution example

jamUserReport -n "List of Devices" -cv "Variant1=Head Office/IT Management Dept." -pf "C:\kiki.csv"

If you create a batch file (.bat), you can output the search results to a printer by executing the EUR command. The following is an example of a batch file:

jamUserReport -n "List of Devices" -cv "Variant1=Head Office/IT Management Dept." -pf "C:\kiki.csv"
IF errorlevel 1 then goto error
eurps C:\kiki.fms,C:\kiki.csv
IF errorlevel 1 then goto error
goto end
error:
echo Outputting to a printer failed.
end:

11.5.12 Example of creating a user report

This section describes the creation procedure using an example of searching for IP addresses that are in use and checking their usage status.

(1) Examining the information to be searched

To search for the IP addresses that are in use, first examine the class to be searched.

The IP address, Asset No., Device name, Device type, User name, Group name, and Location items are output to the search results list.

Next, search for the classes that have the above items as their properties. The correspondence between items and classes is as follows:

Items to be output to the search results list

Class

IP address

NetworkInfo

Asset No.

AssetInfo

Device name

HardwareInfo

Device type

HardwareInfo

User name

UserInfo

Group name

GroupInfo

Location

LocationInfo

(2) Examining the class join method

Once the information to be searched and their classes have been determined, examine the class join method.

The following figure shows an example of examining the class join method.

Figure 11‒32: Example of examining the class join method

Relationship between classes

NetworkInfo and AssetInfo are joined by association class NetworkLink.

AssetInfo and HardwareInfo are joined by association class HardwareLink.

AssetInfo and UserInfo, GroupInfo, and LocationInfo are not joined by association class. Therefore, use the same key to join them.

Inner and outer joins

To identify the devices that are currently using the IP addresses, those devices with no IP address are removed from the search results. Therefore, NetworkInfo and AssetInfo have an INNER relationship (inner join).

Information about Device name, User name, Group name, and Location is output to the search results even if there is no value. Therefore, AssetInfo and Hardware, UserInfo, GroupInfo, and LocationInfo each have an OUTER relationship (outer join).

To define class join in the window, define the inner join and then the outer join in this order.

For the order of source class (Class name join) and target class (Class name join to), if all classes are joined to a single class (AssetInfo) as in this example, specify AssetInfo as the source class for all classes.

(3) Examining the search conditions to be specified in the window

Separately from the items to be output as the search results, examine the items to be specified as the search conditions in the window and the search method.

To narrow down the IP addresses in use by managerial group or by location of the devices, this example defines these two items as the search conditions. To narrow down the IP addresses by range, define the IP address as a search condition.

(4) Procedure for creating a user report in windows

This step defines the selected join method for each class and search conditions in windows and creates a user report for searching for the IP addresses in use.

To create a user report in windows:

From the job menu, select Create User Report.

The Create User Report window appears.

Click the Add button.

The window for selecting search conditions appears.

Select Joined class search, and then click the Next button.

The window for defining the search conditions appears.

Define the join method for each class.

Define each join method between classes. To add an area for specifying the class join method, click the Add button.

The figure below shows an example of defining the class join method.

Figure 11‒33: Example of defining the class join method

Define the join method between classes NetworkInfo and AssetInfo

After selecting Association as the class join method, select Network link. For Join type, select INNER.

Define the join method between classes AssetInfo and Hardware

After selecting Association as the class join method, select Hardware link. For Join type, select OUTER.

Define the join method between classes AssetInfo and UserInfo

Specify Specify class as the class join method, and then specify as follows:

Class name join: Asset information, Key property: User ID

Class name join to: User information, Key property: User ID

Join type: OUTER

Define the join method between classes AssetInfo and GroupInfo

Specify Specify class as the class join method, and then specify as follows:

Class name join: Asset information, Key property: Group ID

Class name join to: Group information, Key property: Group ID

Join type: OUTER

Define the join method between classes AssetInfo and LocationInfo

Specify Specify class as the class join method, and then specify as follows:

Class name join: Asset information, Key property: Location ID

Class name join to: Location information, Key property: Location ID

Join type: OUTER

Define the search conditions.

The following figure shows how to specify search conditions on the Screen tab.

Figure 11‒34: How to specify search conditions on the Screen tab

Select the check boxes of the search conditions that are to be displayed in the window.

If Group name or Location is defined as the search condition, there is no need to specify Condition code. Right truncation is always assumed for search.

The following figure shows how to specify search conditions on the Command Argument tab.

Figure 11‒35: How to specify search conditions on the Command Argument tab

Specify the output items.

Specify the following output items:

IP address of Network information

Asset No. of Asset information

Select either Show details or Hide details to specify whether to display from the search results list a dialog box providing details.

Device name of Hardware information

Device type of Hardware information

Select Display name, Value, or All to specify whether to display the code (value) indicating the type and the display name.

User name of User information

Group name of Group information

Location of Location information

Specify the sort order and display width of output items.

In the Screen display information field, specify the order and display width of output items.

The following figure shows an example of the order of output items.

Figure 11‒36: Example of the order of output items

Select Duplicated data is not output.

Click the Preview button.

Check the specified information, and close the preview window.

Click the Next button.

The window for registering the user report appears.

Select the job category to which the user report is to be added.

From the tree, select Device Management.

Specify Report name for the user report and the user role that can use the user report.

Specify each item as follows:

Report name: Specify List of IP Addresses in Use.

Form file name: Specify the form file (.fms) created by EUR.

You must store the form file specified here in Asset-Console-installation-folder\eur.

Role: Select the check boxes for both Role: administrator and Role: user.

The following figure shows the user report registration window with items specified.

Figure 11‒37: User report registration window

Click the Entry button.

The user report for searching for the IP addresses that are in use is created.

11.5.13 Example of executing a user report

This subsection describes how to execute, by window operation and from the command line, the user report created in 11.5.12 Example of creating a user report.

(1) Example of execution by window operation

Under Device Management, select the List of Address in Use job menu to display the created user report window.

The figure below shows the created user report window.

Figure 11‒38: User report window for searching for the IP addresses in use

If you specify a search condition and then click the Search button, the list of IP addresses in use is displayed. As the search result, this example displays the devices that are using the IP addresses from 10.XXX.XX.200 to 10.XXX.XX.210 in Section 1.

In the search results, clicking a column title sorts the list in ascending or descending order of the data in that column.

Downloading the search results

By clicking the CSV button, you can download to a CSV file the information displayed as the search results.

Outputting the search results

By clicking the PDF button, you can output the information displayed in the Search result list to a form in PDF format. To do so, linkage with EUR is required. For details about how to link with EUR, see 7.3 Setting up the asset management server.

Displaying and editing details

Clicking an Asset No. link displays the Device Details dialog box that enables you to view and edit details about that device.

(2) Example of execution from the command line

In this example, a user with administrator permissions searches the List of Address in Use user report from a command line, and outputs the results to C:\Machine.csv.

When no search condition is specified

jamUserReport -n "List of Address in Use" -pf "C:\Machine.csv"

When groups and an IP address range 10.XXX.XX.200 to 10.XXX.XX.210 are specified as search conditions

jamUserReport -n "List of Address in Use" -cv "Group=Head Office/Sales Dept./Section 1"
 -cv "StartIPAddress=10.XXX.XX.200" -cv "EndIPAddress=10.XXX.XX.210"
 -pf "C:\Machine.csv"

11.6 Selecting the items to be acquired as device change logs (Acquire Device Update Record Items)

You can select the items that are to be acquired as device change logs according to management purposes.

The device change log is acquired when the inventory information of JP1/IT Desktop Management 2 - Manager is registered. Therefore, to manage the device change log, linkage with JP1/IT Desktop Management 2 - Manager is required.

You can change the items to be acquired as device change logs from the Acquire Device Update Record Items window, which is displayed by clicking the Acquire Device Update Record Items job menu. The following figure shows the Acquire Device Update Record Items window.

Figure 11‒39: Acquire Device Update Record Items window

This window lists the items that can be acquired as device change logs. If user-specific hardware information is used to manage the device information, you can also acquire a change log for the user-specific information. You can view the change log acquired based on the settings specified here using the Device Change Log job menu under Device Management and the Update Records tab in the Device Details dialog box.

To acquire information about an item as device change log, select its Acquire check box and then click the Update button.

To remove an item from the device change log, clear its Acquire check box and then click the Update button.

Email notification for device change log

If a device change log has been acquired, the number of changed devices can be reported to the asset manager by email notification. For details about how to notify the asset manager about the number of changed devices by email, see 7.9.8 Notification of device information change.

Notes

In the Customize Managed Items job menu, if you hide the items that can be acquired as device change logs, the device change log is not acquired. They will no longer be displayed in this window.

If the device change log is to be acquired for the item Network information.IP address or Network information.MAC address, a large amount of information about devices used in DHCP operation might be acquired. You can use the Server Setup dialog box to select whether the device change log is to be acquired for IP and MAC addresses during DHCP operation. For details about the settings for acquiring the device change log of IP and MAC addresses, see 7.3.4(13) Acquisition of DHCP address update log.

If the device change log is to be acquired for the item Network information.IP address or Network information.MAC address, the device change log for IP and MAC addresses is acquired using the MAC address as the key value. Therefore, if you set to not acquire the MAC address in the device change log, the device change log might be acquired even when there is no change to the IP address.

12 Item Definition

This chapter describes how to define Items in order to use Items in executing asset management jobs. It first provides an overview of the Item definition procedure, and then explains how to define official authorities and Items.

The chapter uses a FAQs format to highlight key points of Item definition.

12.1 Overview of Item definition

To use Items to execute an asset management job, you must define Items that are appropriate to the nature of the job.

Item definition starts in the Item Definition window, which is displayed by clicking the Item Definition job menu. The figure below shows the Item Definition window.

Figure 12‒1: Item Definition window

The Item Definition window displays a list of Items that have already been defined and can be used or that are still being created and are currently stored.

From this window, you can define new Items and change registered Items.

By default, the sample Items provided by Asset Console are registered. You can change the definition of an Item by clicking its Item name link.

An efficient way to define a new Item that is similar to one of the sample Items is to copy and edit the sample Item. For details about defining an Item by using an existing Item as a template, see 12.7 Changing registered Items.

12.1.1 Definition steps and procedure

This subsection describes the steps required in defining an Item and the definition procedure.

Figure 12‒2: Item definition procedure

Design the job.

Examine the details of the job that is to use the Item. When a job is designed, the items requiring examination include the groups or people (called workers) involved, the range of each asset management task, the route, the workers' role, application and notification information, window components, timing of applying information to the asset management database and the details of processing, migration from an existing job, and scheduling including completion notification.

For details about the Items to be examined at the job design stage, see 12.1.2 Designing a job that uses Items.

Define official authority.

Define the authority for executing each task, such as authorization, by a user with appropriate processing privilege, and then register the applicable user. In addition to the execution authority, also define the permission to reference the latest Item details, and then register the applicable user. You must define official authorities from the Official Authority job menu before defining an Item. For details about how to define official authorities, see 12.2 Defining authority for processing the Item (Official Authority).

Add an Item category.

Each Item belongs to an appropriate category. In the window for selecting a new Item (New Item window), Items are displayed on tabs classified by Item category.

If you need to add a new Item category, use the Code job menu to add the category prior to Item definition. For details about how to add an Item category, see 16.8.1 Adding codes.

Define the route.

Define the route of the Item's flow in terms of the workers and processing. After the route is defined, specify the details of the workers and the processing that they execute on the route.

To define the route of an Item, use the Flow Designer that is displayed from the Item Definition window. For details about how to define a route, see 12.3 Defining the route (Flow Designer).

Define the Item windows.

Define the Item windows that will be used by the workers. An Item window must be defined for each worker on the route as appropriate to the input information to be handled and the nature of the processing to be performed.

To define an Item window, use the Form Designer that is displayed from the Flow Designer. For details about how to define an Item window, see 12.4 Defining the Item window (Form Designer).

Define the processing.

Define the procedures for applying the contents of Item windows to the asset management database. If all that is needed is to send the Item to the next worker, this definition is not necessary. A processing definition is required when data in the asset management database is to be registered or updated when the Item is sent to the next worker. For example, in the case of an Item that involves requesting approval of an application and registration after final authorization, processing definition is required only for the final authorization.

To define processing, use the Activity Designer that is displayed from the Flow Designer. For details about how to define processing, see 12.5 Defining each node's task (Activity Designer).

Define the Item options.

After you finish defining the workers on the route and the details of the processing, the last step is to define options for the Item. The Item options include whether email notification is to be sent to the next worker when the Item is ready to be sent to that worker, and whether a deadline is to be specified for the Item. You define these Item options as required.

You use the Flow Designer to define Item options. For details about how to define Item options, see 12.6 Setting the Item options (Flow Designer).

Use the Item.

As you use an Item, some changes to the job might occur, necessitating changes to the existing definitions.

To change the definition of an exhibited Item, copy and edit the Item, and then re-register it as a new Item.

You can update an Item version by exhibiting a new Item, and then withdrawing use of the previous version of the Item.

For details about how to change a registered Item, see 12.7 Changing registered Items.

12.1.2 Designing a job that uses Items

Design the job that is to be executed using Items. The following describes the items required in order to define a job:

Related group or persons (workers) and the range of the asset management task

Determine the group or persons (workers) that are involved in the job. Also clarify the range of the tasks that each worker is responsible for.

Route

Once the nature of the job has been defined, examine the route of the Item's processing flow by determining the tasks required in order to execute the job as well as the order of the tasks.

Worker's privilege

Determine whether the route contains any task that requires processing by a specific worker, such as Approve.

Application and notification information

Examine the information to be requested by means of an Item and any notification that is to be sent. All processing executable from Items must be predefined. For details about the types of processing that can be executed from Items, see 12.5.2 Selecting tasks to be executed.

Window components

Once the route has been determined, examine the components of the window that is used by each worker on the route. Determine the settings and buttons to be placed in each window and clarify the processing to be executed from each window.

Timing of applying information to the asset management database and the processing details

Examine the details of the processing in conjunction with the window components. The types of processing available from an Item are predefined. In addition to the details of the processing, examine issues such as whether processing is to be executed on multiple targets and the base values when it is to be executed on multiple targets.

You should also examine the Item route in terms of the timing for registering or updating information.

Migration from an existing job and scheduling including completion notification

To migrate an Item job that has already been placed in use, such as because changes to the route or the workers have occurred, estimate the migration period and determine how to notify all the users.

12.1.3 Notes about definition

You should note the following points about defining Items:

The route of an Item is fixed, and cannot branch from a worker depending on specified conditions.

If you edit the Item window, make sure that the activity defining the task is re-registered. Even if there is no need to change the task, register the activity as is. This prevents Item execution from failing because if an Item defined by Activity Designer is changed by Form Designer, the Item will not execute correctly.

If a single user logs in to Asset Console from more than one browser to edit the same item, a malfunction might occur. You must create or edit an item from a single browser.

12.2 Defining authority for processing the Item (Official Authority)

Separately from the role of the user who logs in to the asset management system, you must define the role for executing the Item (official authority). When an Item is defined, a registered official authority is allocated. Therefore, official authorities must be defined before an Item is defined.

Official authority is defined as an independent role group separately from the Item definitions. This means that you can allocate the same official authority to the nodes for multiple Items. The official authority has no effect on the Item definitions even if the target user for the official authority changes due to personnel changes.

To define official authority, use the Official Authority window, which is displayed by selecting the Official Authority job menu.

The figure below shows the Official Authority window.

Figure 12‒3: Official Authority window

This window lists the defined official authorities. Clicking an Official authority ID link displays the details of that official authority.

12.2.1 Adding a new official authority

To add a new official authority:

In the Official Authority window, click the Entry button.

The Add Official Authority dialog box appears.

Official authority ID

Specifies an ID unique to each official authority. This Item is mandatory.

Official authority name

Specifies a name for the official authority. When this Item is omitted, the specified official authority ID is also used as the official authority name.

Description

Specifies a description of the official authority being registered, if necessary.

To cancel, click the Close button.

Click the OK button.

The official authority is registered based on the specified information and the Add Official Authority dialog box closes.

The figure below shows the Add Official Authority dialog box in which each Item has been specified.

Figure 12‒4: Add Official Authority dialog box

12.2.2 Changing official authority details

This subsection describes how to change the details of an official authority by registering and changing the name and target users for an existing official authority.

(1) Changing an official authority name

To change the name of an official authority:

In the Official Authority window, click the Official authority ID link of the official authority that you wish to change.

The Official Authority Details dialog box appears.

To cancel, click the Close button.

On the Official Authority tab, change the name shown for Official authority name, and then click the Update button.

The official authority name is changed.

(2) Registering and changing the target users

To register and change the target users for an official authority:

In the Official Authority window, click the Official authority ID link for the applicable official authority.

The Official Authority Details dialog box appears.

Click the User tab.

The registered target users are displayed.

To remove a user as a target

Select the check box for the user to be released, and then click the Delete button.

To cancel, click the Close button.

Click the Add button.

The Search Users dialog box appears.

If necessary, specify search conditions, and then click the Search button.

The list is searched and the users who satisfy the conditions are retrieved.

In the Official authority user option, specify whether the target users for other official authorities are also to be searched. By default, Include official authority user is selected.

Select the check boxes for the users to be added as target users, and then click the OK button.

You cannot add the user IDs admin, JP1_IM, and JP1_IM_SS, which are created by default, as targets for official authority.

Click the Close button.

The Search Users dialog box closes and the selected users are added as target users.

The figure below shows the procedure for adding target users in the Official Authority Details dialog box.

Figure 12‒5: Procedure for adding target users

12.2.3 Deleting official authorities

To delete official authorities, in the Official Authority window, select the check boxes for the official authorities that you wish to delete, and then click the Delete button. Note that you cannot delete an official authority while target users are registered for it or an official authority that is in use by exhibited Items.

Furthermore, you cannot delete the official authority Item auditor (Incident_Auditor).

12.3 Defining the route (Flow Designer)

This section describes how to define the route of an Item.

Flow Designer, which is displayed from the Item Definition window, is used to define the route of an Item. The route definition produced by Flow Designer becomes the basis for Item definition.

There are two ways to display Flow Designer:

By clicking the Add button

This method enables you to define a new route from scratch. If you specify an Item name in the dialog box for specifying Item names, a Flow Designer with only one node defined is displayed.

By clicking the Item name link

This method enables you to edit an Item that is being defined or reference the settings of a defined Item.

To use a defined Item as a template for creating a new one, first create a copy of the Item, and then click the Item name link.

Whether the Item is displayed as being editable by Flow Designer depends on the status of the Item. An Item whose status is Creating is displayed as being editable, while an Item whose status is Exhibit or Not exhibit can only be viewed and cannot be edited.

Note that Flow Designer cannot be displayed for an Item that is being edited by another user.

12.3.1 Names of Flow Designer components and how to use them

This subsection presents the name of each Flow Designer component and how to use it.

The figure below shows the Flow Designer.

Figure 12‒6: Flow Designer

You can use the Tool buttons to add nodes and activities to be placed on the Flow Designer. Each button is enabled only when it is available to the target selected on the Flow Designer.

The following describes each Tool button for each panel.

Add Items panel

: Add Node

Adds a node to the right of the node selected in Flow Designer. A maximum of 20 nodes can be defined on an Item route.

: Add Activity

Adds an activity to the node selected in Flow Designer.

: Add Completion Activity

Adds a completion activity to the node selected in Flow Designer in order to complete the Item.

: Add Notification Email

Adds a notification email that reports the arrival of an Item to each worker for the activity selected in Flow Designer.

Edit Items panel

: Edit

Edits the definition of an activity, of an Item window icon, of an official authority icon, or of a notification email selected in Flow Designer.

This button also enables you to rename nodes.

: Delete

Deletes the node and activity selected in Flow Designer. Note that the leftmost node cannot be deleted.

If an activity has been defined for the node selected in Flow Designer, deleting the node also deletes the activity.

Options panel

: Edit Emails

Defines a subject line and text for email to be used to notify a worker of the arrival of the Item. Set notification by email, if necessary.

This button is enabled when nothing is selected in Flow Designer.

: Set Deadline

Sets a deadline (since the first worker sent the Item) for completing the Item. Setting a deadline is optional. If you set a deadline, any Items whose deadline has passed are displayed in red in the Inbox and the Outbox. This button is enabled when nothing is selected in Flow Designer.

12.3.2 Placing workers and processing

This subsection describes how to define the route by using Flow Designer to place the Item's workers and processing.

Item definition involves defining information, such as manipulation of windows and the asset management database, on the basis of the layout of the workers and the processing steps defined by the Flow Designer. Therefore, if you determine the route for the Item before specifying detailed definitions, Item definition goes smoothly.

This example defines the same route from the Flow Designer, which is displayed by clicking the Add button, as for the provided sample Equipment Deployment Request Form.

Select a desired Item category.

By default, only the Template category is provided. To add a new category, in the Edit Code window, add the code to MatterCategory of Others (None). For details about how to add code, see 16.8.1 Adding codes.

Select the node name field for the node Applicant, and then click the Add Node button.

A dialog box for specifying a node name appears.

Specify Approval user as the node name, and then click the OK button.

The dialog box closes and the node Approval user is added to the right of the node Applicant.

Select the node name field for the added node and repeat steps 2 and 3 to add nodes Acceptance Desk, Distribution Management Group, and Applicant.

Select the first node Applicant at the left, and then click the Add Activity button.

A dialog box for specifying an activity name appears.

Specify Apply as the activity name, and then click the OK button.

The dialog box closes and the activity Apply is added to the right of the node Applicant.

Similarly, select the nodes Approval user, Acceptance Desk, and Distribution Management Group, and then repeat steps 4 and 5 to add the activities Approve, Distribution request, and Distribution.

Select the last node Applicant at right and click the Add Completion Activity button.

A dialog box for specifying the name of the completion activity appears.

Specify Complete as the name of the completion activity, and then click the OK button.

The dialog box closes and the completion activity is added below the last node Applicant at right.

The completion activity is used to complete the Item. You can add the completion activity anywhere on the route for the purpose of completing the Item.

The Item route has now been defined. To save the definitions, click the OK button.

To set the details of the official authority of users who are to execute the processing at each node, the Item windows, and the activities, click the applicable icon, and then click the Edit button on the Tool.

For details about how to set official authority, see 12.3.3 Setting official authority for a node. For details about how to define the Item window, see 12.4 Defining the Item window (Form Designer). For details about how to define activities, see 12.5 Defining each node's task (Activity Designer).

12.3.3 Setting official authority for a node

This subsection describes how to set official authority for a node so that only authorized users, such as Approval user and Acceptance Desk, can execute the task.

An official authority is always set on the basis of selecting a predefined official authority. For details about how to define an official authority, see 12.2 Defining authority for processing the Item (Official Authority).

Note

The official authority Item auditor (Incident_Auditor) is not set for a node of an Item.

To use Flow Designer to set official authority for a node:

Choose the Official authority icon ()of a node to set its official authority and then click the Edit button.

The Definition of Official Authority dialog box appears.

Select the Official authority user radio button and select the check box for the applicable official authority.

Click the OK button.

The Definition of Official Authority dialog box closes and the specified official authority is set for the node.

The figure below shows the Definition of Official Authority dialog box.

Figure 12‒7: Definition of Official Authority dialog box

When the Item is to be returned for completion to the user who submitted it initially

For a route where the user who first submitted the Item checks the results and then completes the Item, such as Equipment Deployment Request Form, set Item request user for the last node in the Item.

If this option is selected, the Item is sent back automatically to the user who requested the Item without displaying the Select Destination dialog box when the preceding worker finishes the processing.

Note that if you select the Item request user radio button, the Official authority check box is disabled.

Canceling official authority settings

In the Definition of Official Authority dialog box, select the Official authority user radio button and clear all the Official authority check boxes.

12.4 Defining the Item window (Form Designer)

This section describes how to define each worker's window (Item window) that is used when an Item is processed.

Form Designer is used to define each worker's window that is used to process an Item. To display Form Designer, click the Items Window icon () for the node defined in Flow Designer, and then click the Edit button.

If the status of the Item displayed from Flow Designer is Exhibit or Not exhibit, the Item's definition cannot be edited.

Item window definition sequence

Define the Item windows sequentially beginning with the first node at the left that was defined by Flow Designer. The Item window for this first node is for the worker who creates the Item. This Item window becomes the template for defining the Item windows for the other nodes. This helps you define the Item windows efficiently.

The items defined in the Item window for the first node at the left are inherited by the Item windows for all subsequent nodes. If you add an item to the Item window for a node other than the first node, the Item window is no longer inherited to the subsequent nodes.

Therefore, basically, you define all items that can be used for the Item in the Item window for the first node at the left. If any of these items are not needed for a particular worker, you can hide them at that stage.

Note

A session is not closed while Form Designer is displayed in editable status (the time setting of Communication-less monitoring time for Session Information in the Server Setup dialog box does not apply). Therefore, you must close Form Designer when you are no longer using it.

12.4.1 Names of Form Designer components and how to use them

This subsection presents the name of each Form Designer component and how to use it.

The figure below shows Form Designer.

Figure 12‒8: Form Designer

Form Designer is used to set the components of an Item window (objects) and the attributes of the Item window (window).

Menu

Clicking the Object menu displays the object types in cascade. Choosing a desired object inserts it in the editing area.

To insert objects, you must use the Object menu. You cannot insert objects from the Microsoft Internet Explorer menu.

Clicking the Window menu displays in cascade the items for which window attributes are to be set.

Clicking the Operation menu displays a menu for copying and pasting style attributes for the object. You can copy the style of an object selected in the editing area and paste it to other objects.

Editing area

This area is displayed in an Item window when an Item is actually used. You can set the size and background using the Window menu and place each object added from the Object menu to set style and object attributes.

Object location

Displays the object selected in the editing area in pixels. You can use this location information to adjust the locations of objects.

Style attributes

Sets the style of an object, such as color and font. This area displays only those items that can be set for the object selected in the editing area.

Object attributes

Sets attributes, such as data type and maximum, minimum, and initial values, according to the details specified for each object when the Item is actually used. This area is also used to specify such attributes as whether the Item is required and whether the Item is to be displayed in the window for each worker's processing.

This displays only those items that can be set for the object selected in the editing area.

12.4.2 Defining a window

This subsection explains how to use Form Designer to define window attributes.

You define a window by setting the size, background color, and background image of the Item window. You can display each setting by clicking Form Designer's Window menu.

The following shows the Window menu.

Figure 12‒9: Window menu

(1) Size

Select the desired width and height from the following values (in pixels):

Width

480, 640, 800, 1,024, 1,280

The default is 640.

Height

480, 600, 768, 1,024

The default is 480.

(2) Background color

Click the desired color under Background color. Also click a gradation pattern.

(3) Image

To set a background image:

In Set image, click the Browse button.

The Browse User Library dialog box appears.

To view the file contents before setting an image, click the Show button.

To cancel, click the Cancel button.

Click the File/Folder name link for the desired image file and then click the OK button.

The Browse User Library dialog box closes and the specified image is set as the background image. The specified files are tiled in the window.

To clear the specified image:

To clear the settings for the specified image, click the Browse button again in Set image. In the displayed Browse User Library dialog box, click the Clear button.

The figure below shows the Browse User Library dialog box.

Figure 12‒10: Browse User Library dialog box

The user library is used to share images among Items by uploading them to the asset management server. You must register in the user library all the images that you wish to insert in Item windows with Form Designer.

To add a file to the user library:

Click the Add File button.

The File Registration dialog box appears.

File name when saved

Specify the file name to be registered in the user library.

Upload file

Specify the file to be registered.

Click the OK button.

The File Registration dialog box closes and the specified file is added.

To add a folder to the user library, click the Add Folder button and specify the name of the folder.

To delete a folder or file from the user library, select the check box for the applicable folder or file, and then click the Delete button.

12.4.3 Inserting objects

This subsection describes how to define the items (objects) that constitute an Item window in Form Designer.

You can insert objects by selecting them from Form Designer's Object menu.

The following shows the Object menu.

Figure 12‒11: Object menu

To delete an inserted object, select the object in the editing area, and then press the Delete key.

(1) Types of objects that can be inserted

The following types of objects can be inserted:

Textbox

Image

Hyperlink

Text field

Text area

Table

Pulldown

Button

Defined object

This subsection describes how to define each type of object.

(a) Textbox

A text box inserts a character string in the window, such as the name of an item to be specified.

The following shows an example of a text box.

Figure 12‒12: Example of a text box

From the Object menu, select Textbox. A text box is inserted in the editing area. Specify the desired character string in this text box.

For details about how to set the character style (such as color and font), see 12.4.3(2) Setting the style of an object.

(b) Image

You can insert an image in the window, such as a company logo or an eyecatcher.

The following shows an example of an image.

Figure 12‒13: Example of an image

To insert an image:

From the Object menu, select Image.

The Browse User Library dialog box appears.

Click the File/Folder name link to select the file that you wish to insert, and then click the OK button.

The Browse User Library dialog box closes and the specified image is inserted in the editing area. Adjust the location and size of the image.

For details about how to set the order of inserted images, see 12.4.3(2) Setting the style of an object.

For details about how to use the Browse User Library dialog box, see 12.4.2(3) Image.

(c) Hyperlink

You can register a file to be set as a file attachment to the Item or a link to a specific website for referencing.

The following shows an example of a hyperlink.

Figure 12‒14: Example of a hyperlink

From the Object menu, selecting Hyperlink inserts Hyperlink in the editing area. In the editing area, specify an applicable character string to the inserted Hyperlink. For details about how to set the character style (such as color and font), see 12.4.3(2) Setting the style of an object.

For details about how to set a URL as a hyperlink, see 12.4.3(3)(g) URL.

(d) Text field and text area

You can insert input fields to enable each worker to enter information in the Item window.

The following shows an example of a text field.

Figure 12‒15: Example of a text field

From the Object menu, selecting Text field or Text area inserts a text field or text area in the editing area. If necessary, resize the object in the editing area.

Because values entered in text fields and text areas are registered in the asset management database, you must also set object attributes.

For details about the object attributes required when text fields and text areas are inserted and how to set the object attributes, see 12.4.3(3) Setting object attributes.

(e) Table

You can insert input fields to enable each worker to enter multiple Items in the Item window.

The following shows an example of a table.

Figure 12‒16: Example of a table

(f) Pulldown

You can insert an area from which a worker can select an item (drop-down list) in the Item window.

The following shows an example of a pulldown.

Figure 12‒17: Example of a pulldown

From the Object menu, selecting Pulldown inserts a drop-down list in the editing area. If necessary, resize the drop-down list.

Because values selected from drop-down lists are registered in the asset management database, you must also set object attributes.

For details about the object attributes required when Pulldown is inserted and how to set the object attributes, see 12.4.3(3) Setting object attributes.

(g) Button

You can insert in the Item window buttons for executing or canceling processing.

The following shows an example of a button.

Figure 12‒18: Example of a button

From the Object menu, selecting Button displays an area where you can select a button. Choosing a desired button inserts it in the editing area.

The figure below shows the area for selecting a button.

Figure 12‒19: Area for selecting a button

The five types of buttons that can be inserted in the Item window are those that are used for executing activities defined in Flow Designer and those that are used for common purposes: Complete, Save, Reject, New item, and Close. Note that the Complete button can be used only for the node immediately before the completed activity.

If a button used to execute an activity is to update data in the asset management database when the button is clicked, you must use Activity Designer to define the nature of the processing (activity) to be performed by clicking the button.

If a button is used simply to check the contents and send them to the next worker or for common purposes, there is no need to define an activity.

The following describes the types of buttons that can be inserted:

Buttons for executing activities

These buttons have the activity names defined in Flow Designer. To assign a different name, insert the applicable button in the editing area and then change the name.

Complete

Completes the Item.

Save

Saves the Item in the Outbox without sending it to the next worker.

Reject

Rejects the Item and sends it back to the immediately preceding worker or to the first worker.

New item

Displays an Item window for creating a new Item.

Close

Closes the Item window.

(h) Defined object

You can insert in an Item an object defined for another node. This feature is used so that the Item window for a subsequent node can inherit items defined with Flow Designer in the Item window for a preceding intermediate node on the Item route.

For example, suppose that an intermediate worker clicked the Browse button to specify a device and then sent it to the next worker. In order to enable the next worker to determine the received device, you must insert a Defined object.

Choosing Defined object from the Object menu and then selecting the management name of the object to be inserted inserts the selected object in the editing area. For the inserted object, you can set the style and attributes in the same manner as for other objects.

(2) Setting the style of an object

For each object inserted from the Object menu, you can set its style, such as a frame line, background color, and type font.

Selecting an object in the editing area displays a style attribute column that contains the styles available to the selected object.

The figure below shows the style attribute column.

Figure 12‒20: Style attribute column

Clicking a desired style item displays the available colors or values. Choose an appropriate value, and set the style as required.

The following describes the types of styles that can be set and their values:

Frame line

Click the set color area and then select either Non-frame or a color from the color palette.

Background color

Click the set color area and then select Transparent or a color from the color palette. To set gradation, click the desired gradation pattern.

Gradation cannot be set for Pulldown objects.

Font

Click the set font area, and then select the desired front.

Font size

Click the set font size area and then select the desired font size. Available sizes are 5 to 72 points.

Character color

Click the set color area and then select Default or a color from the color palette. When Default is chosen, the Web browser settings take effect.

Font decoration

Choose B (bold), I (italic), or U (underline).

(a) Copying style attributes

You can copy a set of style attributes specified for one object to another object. To use a uniform style for the items in the window, set the style, such as background color and font, for one object, copy the style attributes, and then paste them to the other objects. This saves time in setting the style for each item.

To copy and paste a style:

In the editing area, select the object whose style is to be copied, and from the Operation menu, click Copy attribute.

In the editing area, select the object to which you wish to paste the style, and from the Operation menu, click Paste attribute.

The copied style attributes and size are pasted to the object selected in the editing area.

You can select multiple objects to which you will paste a style.

(b) Setting the display order

To set the display order of an object that has been inserted in the editing area:

In the editing area, select the object whose display order you wish to change, and from the Operation menu, select Front or Back.

The selected object moves to the front or back.

You can select multiple objects.

Note that display order cannot be set for Pulldown objects.

(3) Setting object attributes

You can define the attributes of each object, such as an appropriate data type, whether it is mandatory, and whether it is to be displayed in the window.

When you select an object in the editing area, the attributes available to the selected object are displayed in the object attribute column.

Clicking a desired attribute displays available values and a dialog box for entering a value.

In the case of a Table object, the Table Designer button is displayed. Click this button to open the definition window (Table Designer) for the selected Table object. For details about Table Designer, see 12.4.5 Defining a table (Table Designer).

The table below provides a cross-reference of object types and object attributes that can be set.

Table 12‒1: Cross-reference of object types and object attributes

Object type

Object attribute

Mn

Dt

M1

Max

Min

Iv

Rr

C

URL

Rq

R-o

Nd

EI

Subject

Text box

N

N

N

N

N

N

N

N

N

N

N

N

N

N

Image

N

N

N

N

N

N

N

N

N

N

N

N

N

N

Hyperlink

N

N

N

N

N

N

N

N

M

N

N

N

N

N

Text field

M

M

M#1

M#1

M#1

Y

Y#1

N

N

Y

Y

Y

N

Y#1

Text area

M

M

M

N

N

Y

N

N

N

Y

Y

Y

N

Y

Table

M

N

N

N

N

N

N

N

N

N

Y

Y

N

N

Pulldown

M

N

N

N

N

Y

N

M

N

Y

Y

Y

N

N

Button

N

N

N

N

N

N

N

N

N

N

N

N

Y#2

N

Legend:

Mn: Management name

Dt: Data type

Ml: Maximum length

Max: Maximum

Min: Minimum

Iv: Initial value

Rr: Reference range

C: Code

URL: Uniform Resource Locator

Rq: Required

R-o: Read-only

Nd: Non-display

EI: Execution item

M: Mandatory

Y: Can be set

N: Cannot be set

#1

The attribute might not be supported depending on the specified data type. For details, see 12.4.3(3)(b) Data type.

#2

The attribute can be set only for a New item button.

(a) Management name

When you define an item for entering a value (such as a text field) in the Item window, this attribute sets a management name for the entered value.

The management name set here is used to define the item. It is not the management item for another job menu. Therefore, you can set any name without having to know classes and properties.

To set a management name, select a text field, text area, or drop-down object in the editing area and, then click the Management name specification area. In the displayed dialog box, enter a management name, and then click the OK button.

For text fields and text areas, you can select an object and then directly enter a management name in the editing area.

Processing steps are defined in the Item window with Activity Designer on the basis of the management name specified here.

Notes

All management names in the Item windows for the same Item must be unique except for objects that have been inherited from the Item creator's Item window or objects that have been inserted as Defined object.

In the case of multiple objects with the same management name, you must ensure that they have identical object attributes.

(b) Data type

Data type sets the data type or item specification method for registration into the asset management database.

Data type can be set for Text field, Text area, and Pulldown object types.

The table below provides a cross-reference of data types and applicable object types.

Table 12‒2: Cross-reference of data types and object types

Data type

Object type

Text field#1

Text area

Pulldown

Any double-byte character string

Y

Y

N

Any single-byte character string

Y

Y

N

Alphabetic

Y

Y

N

Alphanumeric

Y

Y

N

Group reference

Y

N

N

Location reference

Y

N

N

User reference

Y

N

N

Code reference

N

N

Y

File reference

Y

N

N

Device reference

Y

N

N

Browse Software

Y

N

N

Reference Software

Y

N

N

Numeric#2

Y

N

N

Date (YYYYMMDD)

Y

N

N

Date (YYYYMM)

Y

N

N

Date (MMDD)

Y

N

N

Time (HHMMSS)

Y

N

N

Time (HHMM)

Y

N

N

Legend:

Y: Can be set

N: Cannot be set

#1

The following data types can be set when the object attribute is Subject:

- Any double-byte character string

- Any single-byte character string

- Alphabetic

- Alphanumeric

- Date (YYYYMMDD)

- Date (YYYYMM)

- Date (MMDD)

#2

Because integers are used in Numeric fields defined by Form Designer for Item jobs, digits to the right of the decimal point are discarded.

For text fields and text areas that are specified directly, set the permitted data type.

For text fields that specify a group, location, user, file, device, software name, or software asset, set the data type for specifying applicable information using the Browse button.

The following describes the data types that are specified using the Browse button:

Group reference, Location reference, User reference, and File reference

When any of these types is set, the Browse button appears next to a text field. In the actual Item window, the user can specify applicable information from the dialog box that is displayed when this button is clicked.

Device reference

When this data type is set, the Browse button appears next to a text field. In the actual Item window, the user can search for and specify the applicable device managed by Asset Console from the dialog box that is displayed when this button is clicked.

The figure below shows the procedure for adding a device from the Reference Devices dialog box that is displayed when the Browse button is clicked.

Figure 12‒21: Procedure for adding a device from the Reference Devices dialog box

Selecting a desired device from the list of search results in the Selection dialog box and then clicking the OK button adds the device to the Reference Devices dialog box.

Browse Software

When this data type is set, the Browse button appears next to a text field. In the actual Item window, the user can specify a software name from the dialog box that is displayed when this button is clicked.

The figure below shows the Browse Software dialog box that is displayed when the Browse button is clicked.

Figure 12‒22: Browse Software dialog box

Reference Software

When this data type is set, the Browse button appears next to a text field. In the actual Item window, the user can specify a software asset from the dialog box that is displayed when this button is clicked.

The figure below shows the Reference Software dialog box that is displayed when the Browse button is clicked.

Figure 12‒23: Reference Software dialog box

When a software asset is specified in the Item window, the character string Selected appears in the specification field. To check the specified information, click the Browse button. In the displayed Reference Software dialog box, click the link for the asset number to the right of the Search button. The Software Details dialog box appears where you can check the specified software asset.

To check the software asset specified by the previous worker in the Item window, click the Browse button to display the Software Details dialog box, from where you can confirm the specified software asset.

Date (YYYYMMDD), Date (YYYYMM), and Date (MMDD)

When these data types are set, a button for displaying a calendar next to the text field is displayed. A numeric value entered in the field is treated as a date. You can select any of the three date formats.

(c) Maximum length, Maximum, and Minimum

These object attributes specify the maximum length for an item that is expressed as a character string, and the maximum and minimum values for an item that is expressed as a numeric value.

A maximum of 1,024 bytes of characters is permitted for Maximum length. The value range permitted for Maximum and Minimum is -2,147,483,648 to 2,147,483,647.

(d) Initial value

Initial value sets an initial value to be displayed in the Item window. The permitted initial value depends on the data type.

For data types Group reference, User reference, Date, and Time, you can set a user group name, user name, date, and time to their initial values when the Item is executed, according to the information displayed in the Item window.

For data type Code reference, you can set the initial value from selections. For other data types, you set a fixed character string.

For a text area, \n in a character string specified as an initial value is regarded as a linefeed.

(e) Reference range

Reference range selects either Reference the range of filtering or Reference all as the range of groups and users to be referenced.

If access is restricted by the organizational hierarchy, this attribute specifies whether the value is to be specifiable from within the restricted range (Reference the range of filtering) or from all organizational hierarchies (Reference all).

This attribute is applicable only to text fields whose data type is Group reference or User reference.

(f) Code

Code defines the selection items (contents of a drop-down list) that are displayed in a drop-down list in the Item window. Selection items in a drop-down list are selected by codes managed in the asset management database. For details about how to add code, see 16.8.1 Adding codes.

To define a selection item to be displayed in a drop-down list:

In the Code specification column, click the Edit button.

The Edit Code dialog box appears.

Click the Add button.

The Select Code dialog box appears.

In Managed class, click the link for the class that contains the code to be displayed.

A list of codes is displayed.

Select the check box for the code that you wish to add, and then click the OK button.

The Select Code dialog box closes and the specified code is displayed in the Edit Code dialog box.

To delete a code, select the check box for the code that you wish to delete, and then click the Delete button.

Click the Close button.

The Edit Code dialog box closes and the specified code is displayed in the Code drop-down list.

The figure below shows the Edit Code dialog box in which codes have been added.

Figure 12‒24: Edit Code dialog box

(g) URL

URL sets the target of a hyperlink object.

Two types of targets are available:

URL jump

Specifies the URL of the target.

File jump

Specifies the management name of a target file. Select the management name from text field objects with the File reference data type that were defined in the previous worker's Item window.

When the specified data type is File reference, only one file can be referenced.

(h) Required

Required sets an item whose specification in the Item window is mandatory.

To set a mandatory item, select the object, and then select its check box.

(i) Read-only

Read-only displays the applicable object as read-only in the Item window. Use this attribute when you wish to ensure that information entered by a previous worker will not be changed.

To set an object as read-only, select the object and then select its check box.

(j) Non-display

Non-display hides an object that is required as Item information but that you do not wish to display in an Item window. For example, suppose that the Item execution date is to be registered in the asset management database. If you insert a text field for entering the date, set the execution date as its initial value, and then hide the field. You can register the execution date and the worker can process the Item without having to know about it.

To hide an object, select the object, and then select its check box.

(k) Execution item

Execution item sets the Item to be displayed by the New item button. This attribute is applicable only to Items whose status is Exhibit.

If this setting is omitted, clicking the New item button displays the Select New Item dialog box for selecting an Item to be executed. If the set Item is no longer in Exhibit status, clicking this button also displays the Select New Item dialog box.

(l) Subject

Subject sets the item that is displayed as the subject of the Item in the Inbox, Outbox, and Execution Item Management windows. When multiple Items have the same name, the subject is useful for identifying each Item.

To set the subject, select the object and select the check box.

To display the subject of the Item in the Inbox, Outbox, and Execution Item Management windows:

Click the Customize Managed Items job menu and then in the displayed window, click the managed class VariousInfo link.

In the displayed window, click the managed class ValueText link.

In the displayed window, select the Show check box for the property Incident_Subject.

Click the Update button.

Only the Item applicant can set the subject. If the subject is changed by any other user, the change is not applied to the subject in the Inbox, Outbox, or Execution Item Management window.

12.4.4 Adjusting an object's style and position

For an inserted object, you can copy and paste style attributes, change its display order, and adjust its position.

(1) Copying and pasting attributes

You can copy attributes selected in the editing area and paste them to another object.

Copy attribute

Copies the size and style attributes of the object selected in the editing area, such as color and font. Select only one object in the editing area whose attributes are to be copied.

Paste attribute

Pastes the attributes copied by Copy attribute to the object selected in the editing area. Note that an attribute is not applied to the selected object if it is not supported for that object.

(2) Changing the display order to front or back

You can change the display order of the object selected in the editing area to the front or to the back. Note that the display order of a Pulldown object cannot be changed.

(3) Aligning vertical and horizontal positions

You can align objects selected in the editing area vertically or horizontally. Of the selected objects, the one on top (or bottom, or left, or right) is used as the reference for aligning the set of objects.

12.4.5 Defining a table (Table Designer)

This subsection explains how to define a Table object inserted using Form Designer.

Use Table Designer to define the Table object that you selected from the Object menu of Form Designer and inserted. Table Designer is displayed when you select the Table object in the edit area and click the Table Designer button displayed under the object attribute.

(1) Names of various components of Table Designer and how to use them

The following figure shows Table Designer.

Figure 12‒25: Table Designer

In Table Designer, you set the attribute of the items that constitute a table.

Table Operations

Displays the Table Operations menu. You can add or delete rows and columns.

Row Attributes

Sets a style for the selected row.

Column Attributes

Sets an object attribute for the selected column.

Click the OK button to save the Table object being edited and close Table Designer. Click the Cancel button to discard the Table object being edited and close Table Designer.

(2) Defining rows and columns for the table (Table Operations)

Click Table Operations to display a menu. Click the desired menu command and define rows and columns for the table. The following menu commands are displayed:

Add row

Adds a single row. The maximum number of rows that can be defined is 10.

Delete row

Deletes a single row. You cannot delete a row if the table has only a single row.

Add column

Adds a column to the last column. The maximum number of columns that can be defined is 10.

Delete column

Deletes the selected column. You can delete only a single column. You cannot delete a column if the table has only a single column.

(3) Setting the row style (Row Attributes)

Click Row Attributes to define a row style. Selecting a row or column displays Row Attributes. The following styles can be defined:

Background color

Sets a background color for the selected row. Select a color from the color palette that is displayed when you click the set color area. To set gradation, click a gradation pattern.

Font

Sets a font for the selected row. Select a font from the font list that is displayed when you click the set font area.

Font size

Sets a font size for the selected row. Select a font size from the font size list that is displayed when you click the set font size area.

Character color

Sets a character color for the selected row. Select a color from the color palette that is displayed when you click the set color area.

Font decoration

Sets font decoration for the selected row. Choose B (bold), I (italic), or U (underline).

(4) Setting the column object attributes (Column Attributes)

Click Column Attributes to define an object attribute for each column. Selecting a row or column displays Column Attributes. The following object attributes can be defined:

Item name

Sets an item name for the selected column. Specify a double-byte or single-byte character string between 1 and 32 bytes. The default is Item.

Data type

Sets a column data type. Select the desired data type from the drop-down list. The data types that can be set are listed below. The default is Any double-byte character string.

Any double-byte character string

Any single-byte character string

Alphabetic

Alphanumeric

Group reference

Location reference

User reference

Numeric

Date (YYYYMMDD)

Date (YYYYMM)

Date (MMDD)

Time (HHMMSS)

Time (HHMM)

Maximum length

Sets the maximum length for the data that can be input to a column item. The maximum value that can be set is 1,024 bytes. The default is 1,024 bytes.

Initial value

Sets the initial value for a column item. The initial value that can be set varies depending on the data type. The following table shows the initial value that can be set by data type.

Table 12‒3: Initial values that can be set

Data type

Initial value that can be set

Group reference

Group of applied user

User reference

Applied user name

Date

Applied date

Time

Applied time

Other data type

Any

Reference range

Sets the range of column items that can be referenced. Select either Reference the range of filtering or Reference all. The default is Reference the range of filtering.

This item is displayed when one of the following data types is set:

Group reference

User reference

Maximum and Minimum

Sets the maximum and minimum numeric values that can be specified for column items. The value range permitted for Maximum and Minimum is -2,147,483,648 to 2,147,483,647. The default for Maximum is 2,147,483,648. The default for Minimum is -2,147,483,647.

This item is displayed when Numeric is set for the data type.

Read-only

When this check box is selected, the set columns are displayed as read-only when the Item window is displayed.

Non-display

When this check box is selected, the set columns are not displayed when the Item window is displayed.

Note that some object attributes cannot be set (displayed) depending on the data type. The following table shows the correspondence between data types and object attributes.

Table 12‒4: Correspondence between data types and object attributes

Data type

Object attribute

Maximum length

Initial value

Reference range

Maximum

Minimum

Any double-byte character string

Y

Y

N

N

N

Any single-byte character string

Y

Y

N

N

N

Alphabetic

Y

Y

N

N

N

Alphanumeric

Y

Y

N

N

N

Group reference

N

Y

Y

N

N

Location reference

N

N

N

N

N

User reference

N

Y

Y

N

N

Numeric

N

Y

N

Y

Y

Date (YYYYMMDD)

N

Y

N

N

N

Date (YYYYMM)

N

Y

N

N

N

Date (MMDD)

N

Y

N

N

N

Time (HHMMSS)

N

Y

N

N

N

Time (HHMM)

N

Y

N

N

N

Legend:

Y: Can be set.

N: Cannot be set.

Note

When the number of rows or columns to be displayed is changed through a table operation or column display or non-display, the size of the entire table is changed based on the current row and column sizes.

12.4.6 Definition example of Item window

This subsection describes how to define an Item window with Form Designer using the sample Item Equipment Deployment Request Form provided by Asset Console.

Define the attributes of the window.

From the Window menu, set the size and background color.

You can change the window attributes at any time while you are defining objects.

Insert objects.

From the Object menu, insert as many objects as needed in the Item window.

Define the style of the objects.

Select one of the inserted objects and set style attributes, such as color, size, and font.

Copy the style attributes of this object and paste them to other objects for which you wish to set the same style attributes. When style attributes are copied, the resulting objects have not only the same color and font, but also the same size. This makes it easy to adjust the layout of the Item window.

You can change style attributes in a batch operation by selecting multiple objects.

Define the attributes of the objects.

Define the attributes of each object. Unlike the style attributes, the object attributes cannot be copied or specified for multiple objects in a batch operation.

You can reduce the workload of Item creation if you set attributes automatically, such as using the date and time the Item is displayed and the login user information to set the Item registration date, request user's name, and request user's group.

Add style and supplementary information according to the attributes of the object.

Attention is drawn to a mandatory item if the color of the item name is changed during an input operation.

If you have set the object attribute for a date, entry errors can be avoided if you add a note indicating that the date must be entered in the format year/month/date including the slashes (/), such as 2004/12/25. Such a note can be inserted as a supplementary information next to the input field.

Alternatively, a specification example can be displayed as the initial value in the input field.

Check the settings with a preview.

Check the Item window settings in the actual format that is displayed.

Register the Item window.

The Item window is displayed with the status Creating in the Item Definition window.

To actually use the Item window, change its status to Exhibit.

12.5 Defining each node's task (Activity Designer)

This section describes how to define details of the task (activity) at each node.

Activity Designer is used to define the details of the task at each node. In Activity Designer, you define how the contents of the asset management database are to be updated (added, changed, deleted) on the basis of the information specified by each worker in the Item window.

An activity is defined as a combination of specific processing actions on the asset management database (tasks), such as Add new device. By combining tasks, the nodes for Items can achieve a wide variety of processing. These tasks are different from those registered in Windows Task Scheduler.

Activity Designer is displayed from Flow Designer. To display Activity Designer, select an activity defined in Flow Designer () and then click the Edit button. If an activity was registered before its definition was completed or if an Item whose status is Exhibit or Not exhibit is displayed from Flow Designer, the definition cannot be edited.

12.5.1 Names of Activity Designer components and how to use them

This subsection presents the name of each Activity Designer component and how to use it.

The figure below shows Activity Designer.

Figure 12‒26: Activity Designer

Activity Designer defines processing to be executed from the Item window by setting a task and assignment information for each managed item.

Activity name

Displays the name that was specified when the activity was added in Flow Designer. Change the activity name, if necessary.

State of item after activity is executed

Specifies the status of the Item after the activity being defined here has been executed. When this information is omitted, (activity-name-defined-in-Flow-Designer) Done is displayed.

List of tasks

Enable tasks displays definable processing. Select one of the tasks and add it to Use tasks. Each task that is added will execute in the order it is displayed in the List of tasks. To specify a range for repeating the same processing, add the tasks *Loop start and *Loop end.

For details about the types of tasks and the details of each task, see 12.5.2 Selecting tasks to be executed. For details about how to set the order of tasks, see 12.5.3 Setting the order of tasks to be executed.

Task conditions

Sets the details of the task that has been added to Use tasks.

Assigned items is set for each task's Managed items.

Managed items lists the following three types of items:

Information to be managed in the asset management database (class properties)

You can set the method for updating the information (class properties) managed in the asset management database by Item execution.

For example, to register the execution date of an Item as the asset registration date, set the value indicating the item execution date using the Browse button for the managed Item Asset Information.Reg.date.

Item for identifying the processing target

You can set the item that identifies the target of the selected task (such as updating).

For example, to update device information, set the value indicating the target's Asset No. using the Browse button for the managed item Asset information.Asset No.

Item for setting a range of loop processing

If you have added the *Loop start and *Loop end tasks, set the range of the loop.

For details about how to set the assignment item for each managed item, see 12.5.4 Setting the information to be assigned to managed items.

If an activity is registered before its definition is completed and integrity is lacking among assigned items or there is more than one managed item that is a mandatory item but no assigned item is set, Now editing will be displayed next to the Back button when this activity is displayed.

12.5.2 Selecting tasks to be executed

This subsection describes the types of tasks that can be selected in Activity Designer and the details of each task.

To define an activity, select the processing to be executed in the Item window from Enable tasks, and then add it to Use tasks.

The table below lists the tasks that can be selected in Activity Designer.

No.

Task that can be selected in Activity Designer

No.

Task that can be selected in Activity Designer

1

*Loop start, *Loop end

2

Add new device

3

Update device information

4

Add new software

5

Add license key

6

Assign license key

7

Auto assign license key

8

Release license key

9

Transfer license

10

Transfer license key

11

Add network information

12

Delete network information

13

Add new contract

14

Add new volume license

15

Update contract

16

Update volume license

17

Assign asset to contract

18

Assign asset to volume license

19

Release asset from contract

20

Release asset from volume license

21

Add new user

22

Update user information

23

Delete user information

24

Add new problem

25

Update problem

26

JP1 event notification

Legend:

--: Not applicable

The following describes each executable task:

*Loop start and *Loop end

Use these tasks to specify the range of a processing repetition.

You can incorporate a set of *Loop start and *Loop end within another set of *Loop start and *Loop end. There is no limitation on the number of these tasks.

When you select a loop, you must set the target of the loop's processing. The following looping targets can be specified:

Number of objects selected on window

Number of lines of uploaded file

Number of table rows

For details about how to set the loop target, see 12.5.4(2) Setting the details of loop processing.

Add new device

Use this task to register a new device. The two methods are to register a single device as is into the asset management database by registering the value specified for the item in the Item window, and to register multiple devices by obtaining the common part from the value specified in the Item window and the variable part that depends on the device from a CSV file.

By combining this task with a network-related task, you can achieve a job such as device installation.

When you set assigned items for this task, note the following:

For User ID and User name, and User ID of administrator and administrator, if both ID and name are set, the ID takes precedence over the name for assignment of the corresponding user.

If ID has not been set, the name is used as the key value to assign the applicable user.

If ID is used to assign information, the specified name is ignored.

If only the name is set in the assigned item without setting the ID, user information is searched by the name. If the matching name is found, the corresponding ID is registered. If the matching name is not found, this name is registered as is as the user name. If there are multiple matching names, an error results.

If there is no information that corresponds to the ID, an error results.

An error occurs if a value cannot be acquired for any of the following Managed items: Asset information.Status, Asset information.Usage management, and ITDM2 Agent installed status.

Update device information

Use this task to change device information.

As with adding a new device, there are two methods, updating a single device and updating multiple devices.

When you set assigned items for this task, note the following:

Asset No. specified for Target asset no. is used as the key value to assign the information to be updated.

For User ID and User name, and User ID of administrator and administrator, if both ID and name are set, the ID takes precedence over the name for assignment of the corresponding user.

If ID has not been set, the name is used as the key value to assign the applicable user.

If ID is used to assign information, the specified name is ignored.

If only the name is set in the assigned item without setting the ID, user information is searched by the name. If the matching name is found, the corresponding ID is registered. If the matching name is not found, this name is registered as is as the user name. If there are multiple matching names, an error results.

If there is no information that corresponds to the ID, an error results.

Add new software

Use this task to register new software. This task registers software and license information.

By combining this task with a license-related task, you can achieve a job such as software installation.

The Software name specified in the Item is registered in the software list, if it has not been registered yet. Similarly, a specified License name is registered in the license information, if it has not been registered yet.

An error occurs if a value cannot be acquired for any of the following Managed items: Asset information.Status, Software list.Software name, and Software list.Software type.

Add license key

Use this task to register a license key for software. This task adds a license key to the registered software.

To identify the target software, the Asset No. of the software and information about the owner group are required.

Assign license key

Use this task to specify a license key and request use of the license. This task assigns a license for registered software to a device or user based on the specified key.

To identify the target software, the Asset No. of the software and information about the owner group are required.

When you set assigned items for this task, note the following:

If the license category is Install license, the applicable device is assigned by Asset No. . If the license category is User license, the applicable user is assigned by User name.

If multiple license keys with the specified value (license key, product ID, or serial No.) have been registered, one of the license keys is assigned. If license keys with the specified value have been registered but none of them is available, an error results.

Auto assign license key

Use this task to request the use of a license without specifying a license key. This task automatically selects an available key from the registered software licenses and assigns it to the device or user.

By combining with the Add license key task, you can achieve on-demand license addition and assignment.

To identify the target software, the Asset No. of the software and information about the owner group are required.

To assign license keys automatically, you must register license keys to the applicable software assets beforehand.

Release license key

Use this task to release a license in use. This task releases the assignment of registered software licenses.

To identify the target software, the Asset No. of the software and information about the owner group are required.

To release a specific license, you must specify License key, Product ID, or Serial No.. If multiple license keys for the same software asset have been assigned to the same device or user, all applicable license keys will be released.

Transfer license

Use this task when licenses are divided or groups have been changed for reasons such as reorganization. To transfer licenses to another group, this task copies the software information and distributes the numbers of licenses.

When you select this task, note the following:

An error results if the same Asset No. is registered more than once at the source.

If the same software information whose status is Active is found at the target group, the software information is integrated. If multiple sets have been registered, the software information is integrated with one of them.

If the target has the same Asset No. but its software status is not Active, the software is registered as a new asset.

The task cannot transfer license keys to multiple groups at the same time. To transfer license keys to multiple groups, you must issue a request for each group.

When freeware software is transferred, the source software is not deleted.

Licenses cannot be transferred if the number of licenses is unlimited at the source or the software is freeware, and the number of destination licenses has been specified. Also, licenses cannot be transferred if the number of licenses is unlimited at the source (not freeware), and the number of destination licenses is omitted.

Transfer license key

Use this task to transfer license keys for reasons such as reorganization. This task cannot transfer license keys to multiple groups at the same time. To transfer license keys to multiple groups, you must issue a request for each group.

Define license key transfer in the same activity as for the license transfer. An error results if the target does not have the software with the same Asset No. as the source.

To identify the target software, the Asset No. of the software and information about the owner group are required.

Add network information

Use this task to assign network information to a device (node name, computer name, IP address). The two methods of IP address allocation are automatic allocation and specified allocation.

When an IP address is specified to register network information, the task uses this IP address even if it is already in use by another device according to the inventory information (this means that there will be two devices with the same IP address).

When you set assigned items for this task, note the following:

When you use automatic allocation, set the IP group name. If you also set the IP address, the task uses the specified IP address for allocation instead of performing automatic allocation.

To update network information, specify the applicable IP address. You can change the IP address by specifying the new IP address after updating.

Set Target asset ID if you wish to use the ID of an asset that has already been registered, such as a device registered by the previous task.

Delete network information

Use this task to delete network information assigned to a device (node name, computer name, IP address). This task uses the specified Asset ID (or Asset No.) and IP address to find the applicable network information and then deletes it. If multiple IP addresses have been assigned to the specified device, the task deletes all of them.

When you set assigned items for this task, note the following:

Set Target asset ID if you wish to use the ID of an asset that has already been registered, such as a device registered by a previous task.

Add new contract

Use this task to register new contracts, such as lease, rental, and maintenance contracts.

An error occurs if a value cannot be acquired for any of the following Managed items: Contract information.Category, Contract information.Contract No., Contract information.Subject, Contract information.Contract date, Contract information.Contract start date, Contract information.Contract end date, Contract information.Contracted company, and Contract information.Status.

Add new volume license

Use this task to register new volume contracts.

An error occurs if a value cannot be acquired for any of the following Managed items: Volume Contract Information.Contract No. and Volume Contract Information.Status.

Update contract

Use this task to update contract information, such as when contracts are renewed.

When an Item is used to register a contract, Contract No. is the only information that can identify the contract. Therefore, if you update contracts using Items, you must manage information in such a manner that Contract No. is unique.

Update volume license

Use this task to update volume contract information, such as when contracts are renewed.

When an Item is used to register a contract, Contract No. is the only information that can identify the contract. Therefore, if you update contracts using Items, you must manage information in such a manner that Contract No. is unique.

Assign asset to contract

Use this task combined with the Release asset from contract task to change the allocation of devices and software that require contracts, such as when new contracts are registered or existing contracts are renewed.

This task can assign only those contracts whose status is Under contract.

An error results if there is more than one applicable contract and the applicable asset has already been assigned to another contract of the same type.

Assign asset to volume license

Use this task combined with the Release asset from volume license task to change the allocation of software that requires a volume contract, such as when new contracts are registered or existing contracts are renewed.

This task can assign only those contracts whose status is Under contract.

An error results if there is more than one applicable contract and the applicable software asset has already been assigned to another contract.

Release asset from contract

Use this task to release the allocation of devices or software that require a contract, such as when existing contracts are renewed.

If the applicable device can be identified, such as when a previous task has changed its device status, specify Asset information.Asset ID to inherit Asset ID from the previous task.

Release asset from volume license

Use this task to release the allocation of software that requires a volume contract, such as when existing contracts are renewed.

If the applicable device can be identified, such as when a previous task has changed its device status, specify Asset information.Asset ID to inherit Asset ID from the previous task.

Add new user

Use this task to register new users, such as when new personnel have been added. This task registers user information and assigns a user role to each user. It does not set a password. Use the registered User ID to log in to Asset Console without entering a password and then use a window operation to set a password.

An error occurs if a value cannot be acquired for any of the following Managed items: User Information.User ID and User Information.User name.

Update user information

Use this task to change user information, such as name, telephone number, or email address, and to change the role of a user for reasons such as reorganization.

This task uses User ID or User name to find the target user. If User ID is not specified, the task searches asset information using User name as the key value. If more than one user with the same first and last names is registered, an error results.

Delete user information

Use this task when registered user information is no longer needed for reasons such as reorganization.

This task uses User ID or User name to find the target user. If User ID is not specified, the task searches information using User name as the key value. If more than one user with the same first and last names is registered, an error results.

Add new problem

When Items are used to manage problems, use this task to register problems that have occurred in the asset management system.

An error occurs if a value cannot be acquired for any of the following Managed items: Maintenance.Managed No., Maintenance.Status, and Maintenance.Overview of problem.

Update problem

When Items are used to manage problems, use this task to add and update information until a problem is resolved, and to send the problem to the person in charge.

Specify Asset information.Asset ID to inherit Asset ID of a device for which information has been updated, such as when the previous task has changed the device information for error handling purposes.

JP1 event notification

Use this task to notify other linked products about Item transition by issuing an Item transition event. By defining this task for all Item-related activities, you can monitor the Item status. When you use the automatic action of JP1/IM to execute the desired command, other linked products can execute processing using the Item transition as a trigger.

An Item transition event is issued when an Item transitions normally (when an activity that contains the task is processed normally). If an Item that has transitioned normally is returned, rejected, or deleted, an Item status change event or Item deletion event is automatically issued.

For details about the JP1 events that are issued in conjunction with Item transition, see 19.2 Details of JP1 events issued from Asset Console.

12.5.3 Setting the order of tasks to be executed

This subsection describes how to set the order of the tasks that have been added to Activity Designer's Use tasks.

Each task added to Use tasks is executed in the order displayed in the list. To change the execution order, select a task whose execution order is to be changed from the Use tasks list, and then click the Up or Down button.

When setting the order in Use tasks, pay attention to the logical order of information. For example, when you execute the Add new device and Add network information tasks, you must execute the Add new device task first to register information about the device to which network information is assigned.

When you have added loop processing, make sure that *Loop start and *Loop end are always paired.

The following are examples of settings in the Use tasks field when software installation, license usage, and device transfer requests are executed:

Example of settings for software installation request

*Loop start
Add new software
*Loop end
*Loop start
Add license key
*Loop end

In this example, Number of lines of uploaded file is selected under Managed items in Task conditions, and after the number of software information items equaling the number of lines in the CSV file attached to the Item are registered, the license key for the registered software is added.

Example of settings for license usage request

*Loop start
Assign license key
*Loop end

In this example, Number of lines of uploaded file is selected under Managed items in Task conditions, and the license is assigned using the specified key to the software already registered for each line in the CSV file attached to the Item. If Assign license key is replaced with Auto assign license key, available key information is assigned automatically.

Example of settings for device transfer request

*Loop start
Update device information
*Loop end

In this example, Number of objects selected on window is selected under Managed items in Task conditions, and the device information is updated the number of times equaling the number of devices selected in the Item window or the number of lines in the CSV file attached to the Item.

12.5.4 Setting the information to be assigned to managed items

This subsection describes how to set the information to be assigned to managed items in Activity Designer's Task conditions. By setting the information that is assigned to managed items, you set the information to be updated by tasks added to Use tasks, the method for identifying the target of the processing, and the range of loop processing.

To display Task conditions, select a desired task from Use tasks, and then click the Edit button. From the list of Managed items, select the item to be processed, and then set the assigned item.

Managed items displays the information managed in the asset management database (in the format class.property), the item for identifying the target of the selected task process, and the item for setting a range of loop processing. From the displayed Managed items, you set the assigned items as needed. Make sure that you set the items identified by a star () in the Managed items field.

If you have selected *Loop start as Use tasks, select Loop target before setting an assigned item. For details about how to specify settings when *Loop start is selected as Use tasks, see 12.5.4(2) Setting the details of loop processing.

(1) Setting assigned items for tasks

Clicking the Browse button for each assigned item displays the Assigned Setting From Screen dialog box. The following figure shows an example of the Assigned Setting From Screen dialog box.

Figure 12‒27: Example of the Assigned Setting From Screen dialog box

This dialog box lists the items that are set automatically and the management names that were defined in the Item window. Select the information that you wish to assign to each managed item.

Select one of the following assigned items that are displayed in the Assigned Setting From Screen dialog box:

Do not set

Does not set an assigned item for the selected managed item.

Auto: Automatic numbering

Sets the value automatically obtained by the asset management system.

Automatic: Fixed value

Always sets the specified value. When you select this item, make sure that you specify a fixed value.

Auto: Executed date

Sets the date the Item executes. If a date has already been registered for the same managed item, it will be overwritten.

Automatic: Executed date (Register if there is no value)

Sets the date the Item executes. If a date has already been registered for the same managed item, it will not be overwritten.

Acquired from the upload file

Assigns the value in the CSV file that is uploaded as a file attachment to the Item. Only CSV files are supported for assignment of values. When you select this item, make sure that you specify the location of the value that is to be obtained from the file.

Also add *Loop start and *Loop end before and after the selected task, and in Task conditions for *Loop start, specify Number of lines of uploaded file in Loop target.

Acquired from table

Assigns the value that was defined as the Table object in the Item window. When this item is selected, you must also specify the table column from which the value is to be acquired.

Also add *Loop start and *Loop end before and after the selected task, and in Task conditions for *Loop start, specify Number of table rows in Loop target.

Acquired from the reference devices

Assigns the value of the device specified from the Browse button in the Item window. When this item is selected, add *Loop start and *Loop end before and after the selected task, and in Task conditions for *Loop start, specify Number of objects selected on window in Loop target.

Acquired from the reference software

Assigns the value of the software asset specified from the Browse button in the Item window. When this item is selected, add *Loop start and *Loop end before and after the selected task, and in Task conditions for *Loop start, specify Number of objects selected on window in Loop target.

Acquired from the task executed immediately before

Enables you to assign a value by acquiring applicable information from the immediately preceding task, as defined by the order defined in Use tasks. For example, if Add new device is defined to be executed immediately after Add new user, the user ID registered in Add new user can be assigned to Asset information.User ID for Add new device.

This item can be set for the following tasks and managed items:

Add new device:

Asset information.User name, Asset information.User ID, Asset information.User name of administrator, and Asset information.User ID of administrator

Assign license key:

Target device's Asset information.Asset No. or Asset information.User ID, and target software's Asset information.Asset No.

Auto assign license key:

Target device's Asset information.Asset No. or Asset information.User ID, and target software's Asset information.Asset No.

Add network information:

Network info ID.Asset ID

Assign asset to contract:

Asset information.Asset ID

Assign asset to volume license:

Asset information.Asset ID

Update problem:

Maintenance log ID.Asset ID

(Management name defined by Form Designer)

Displays a managed item defined by Form Designer that has the matching data type. In the Item window, the value entered for the selected item is assigned.

Note

If the assigned value is null, when the Item is processed, the null value is used for updating. However, an error results if the null value is assigned to a mandatory managed item.

(2) Setting the details of loop processing

This subsection describes how to set assigned items when the *Loop start and *Loop end tasks are added to Activity Designer's Use tasks.

When a single task is to be repeated, such as when multiple devices are to be registered or deleted, *Loop start and *Loop end are used to set the range of the repetitive task. The number of times one task is to be repeated is set in Task conditions.

Set the repetition count in Task conditions, which is displayed by selecting *Loop start from Use tasks, and then click the Edit button.

After selecting the target to be repeatedly executed in Loop target, specify an assigned item from the Browse button.

The following describes the value to be selected in Loop target and how to set the assigned item:

Number of objects selected on window

Executes the loop processing in the Item window as many times as there are devices or software assets selected from the Browse button.

For Assigned items, set the management name of the object for which the data type Device reference or Software reference was specified in Form Designer.

Number of lines of uploaded file

Executes the loop processing as many times as there are lines in the CSV file attached in the Item window.

For Assigned items, set the management name of the object for which the data type File reference was specified in Form Designer.

Number of table rows

Executes loop processing the number of times equaling the number of lines defined as the Table object in the Item window. For Assigned items, set the management name of the Table object.

(3) Information set in a managed item to which no value is assigned

When no assigned item has been set or when value acquisition fails, a value is set automatically in some items. The following table shows these items and the values that are set.

Task

Managed item

Value that is set

Add new device

Asset information.Reg. date

Execution date of Item

Hardware information.Device type

PC

Add new software

Asset information.Reg. date

Execution date of Item

Add new user

User information.User name (English)

User ID

Problems

Maintenance log.Reg. date

Execution date of Item

Maintenance log.Registrar

Login user name

Maintenance log.Importance

Emergency

Maintenance log.Problem type

User registered

If no assigned item is set for the following managed items, or if value acquisition fails, Item processing results in an error:

Add new contract

Contract information.Contract date, Contract information.Contract start date, Contract information.Contract end date, Contract information.Contracted company

Problems

Maintenance log.Reg. date, Maintenance log.Overview of problem

12.5.5 Examples of activity definitions

This subsection illustrates the procedure for defining activities with Activity Designer using the example of software installation request jobs.

There are two possible situations for software installation request activities:

Registering one software asset and multiple license keys (when only one software asset is registered)

Registering multiple software assets and multiple license keys for each software asset (when multiple software assets are registered)

The following subsections describe each definition example.

(1) Example of activity definition (when only one software asset is registered)

This activity registers the requested software asset and license keys. It assumes that the Item window has been defined in such a manner that the following items are specified and attached:

Request user name, Group of request user, Phone of request user, Software name (mandatory), Number of licenses (required), License keys (required) (file attachment), Notes, Reason for rejection

The following shows the contents of the file attachment for the license keys. License key, Product ID, and Serial No. are specified in the file.

Key101,aaa-aaa-aaa,123456789
Key102,bbb-bbb-bbb,123456789
Key103,ccc-ccc-ccc,123456789
Key104,ddd-ddd-ddd,123456789
Key105,eee-eee-eee,123456789

Settings in Use tasks

The tasks to be selected and their order are as follows:

Add new software
*Loop start
Add license key
*Loop end

Settings in Task conditions for Add new software

The following shows an example of setting assigned items for Add new software.

Figure 12‒28: Example of setting assigned items for Add new software (when only one software asset is registered)

Because only one software asset is registered, for Asset No., set the management name of the object that specifies Asset No. . For other required items, set a fixed value.

Settings in Task conditions for *Loop start

To register the license keys specified in the CSV file, set Number of lines of uploaded file for Loop target and the management name of the object that specifies License key for Assigned items.

Settings in Task conditions for Add license key

The following shows an example of setting assigned items for Add license key.

Figure 12‒29: Example of setting assigned items for Add license key (when only one software asset is registered)

For Target asset no. of software and Target group name, set the management names of the objects that specify their values. For Target group name, you can specify only the object for which Group reference was selected as the object attribute Data type.

For Product ID, License key, and Serial No., set the applicable column numbers in the CSV file.

(2) Example of activity definition (when multiple software assets are registered)

This activity registers requested multiple software assets and multiple license keys for each software asset. It assumes that the Item window has been defined in such a manner that the following items are specified and attached:

Request user name, Group of request user, Phone of request user, Software (required) (file attachment), License keys (required) (file attachment), Notes, Reason for rejection

The following shows the contents of the file attachment for the software. Asset No., Software name, Number of licenses, and License name are specified in the file.

Asset000001,Software001,2,License001
Asset000002,Software002,2,License002
Asset000003,Software003,2,License003

The following shows the contents of the file attachment for the license keys. Asset No., License key, Product ID, and Serial No. are specified in the file.

Asset000001,Key101,aaa-aaa-aaa,123456789
Asset000001,Key102,bbb-bbb-bbb,123456789
Asset000002,Key103,ccc-ccc-ccc,123456789
Asset000002,Key104,ddd-ddd-ddd,123456789
Asset000003,Key105,eee-eee-eee,123456789
Asset000003,Key106,fff-fff-fff,123456789

When multiple software assets are registered, you must specify Asset No. to identify each software asset.

Settings in Use tasks

The tasks to be selected and their order are as follows:

*Loop start
Add new software
*Loop end
*Loop start
Add license key
*Loop end

The loop processing itself can be structured hierarchically. However, this example does not use a hierarchical structure because if the license keys to be registered vary from one software asset to another, a hierarchical structure cannot provide the intended processing.

This example requires assignment of information between the CSV files for the Add new software and Add license key tasks. It is therefore necessary to specify the assigned key in both CSV files. In this example, Asset No. is the assigned key.

Settings in Task conditions (*Loop start)

To register the information specified in the CSV file, set Number of lines of uploaded file for Loop target. For Assigned items, set the management name of the object that specifies Software or License key.

Settings in Task conditions (Add new software)

The following shows an example of setting assigned items for Add new software.

Figure 12‒30: Example of setting assigned items for Add new software (when multiple software assets are registered)

For Asset No., Software name, Number of licenses, and License name, set the applicable column numbers in the CSV file. For Group name and Notes, set the management names of the objects that specify their values. For other required items, set fixed values.

Settings in Task conditions (Add license key)

The following shows an example of setting assigned items for Add license key.

Figure 12‒31: Example of setting assigned items for Add license key (when multiple software assets are registered)

For Target asset no. of software and Target group name, set the management names of the objects that specify Asset No. and Group name, respectively. For Product ID, License key, and Serial No., set the applicable column numbers in the CSV file.

12.6 Setting the Item options (Flow Designer)

This section describes how to set Item options.

When you send a created Item, you can specify whether a completion deadline is to be set and whether an email notification is to be sent to the next worker.

Flow Designer is used to set these Item options.

12.6.1 Setting a deadline

You can set a deadline for completing a new Item, based on an interval (number of days) since the Item is sent. This setting is optional. If you set a deadline, an Item whose deadline has passed is displayed in red in the Inbox.

To set a deadline for an Item:

In Flow Designer, from Tools, click the Set Deadline button.

A dialog box for specifying the deadline in days appears.

The permitted maximum value is 999 days.

Specify the deadline in days, and then click the OK button.

The dialog box for specifying the deadline closes and the specified deadline is set.

For an Item for which a deadline has been set, you can determine the Expiration date in the Inbox and Outbox windows.

To release the set deadline:

In the procedure for setting the deadline, specify 0 or blank as the deadline.

12.6.2 Selecting email transmission

When a worker sends an Item to the next worker after processing the Item, an email notification can be sent alerting the next worker that the Item has been sent. Whether an email is to be sent is specified for each Item or each activity.

To send email notification:

In Flow Designer, click the Edit Emails button.

Mail Designer appears.

Specify the default text to be displayed in Subject and Contents.

You can specify a maximum of 64 bytes of text in Subject (the subject line) and a maximum of 1,000 bytes of text in Contents (the body of the email).

The texts set here can be edited when each worker sends the email.

If no texts are specified, the email transmission setting does not take effect.

Click the OK button.

Mail Designer closes and the specified email transmission setting takes effect. When the settings take effect, the notification email item () is added to all activities for the Item.

Whether the email is actually to be sent can be selected when the Item is sent.

Select the notification email item () whose email transmission settings are to be changed, and then click the Edit or Delete button.

You can edit the email transmission settings for each activity.

If you click the Edit button, Mail Designer is displayed. Specify the desired information. If you click the OK button, the specified email transmission settings take effect and the notification email item is changed for the activity (). If you click the Delete button, a dialog box asking whether the notification email item is to be deleted is displayed. Click the OK button. If you do not wish to specify email transmission settings for each activity, skip step 4.

To add a notification email item that was deleted once, select the target activity and then click the Add Notification Email button ().

The figure below shows Mail Designer.

Figure 12‒32: Mail Designer

To change the email transmission settings for each activity to settings for each Item

Use the procedure for setting email transmission to delete all character strings specified in Subject and Contents. Clicking the OK button displays a dialog box asking whether you want to change the email transmission settings to settings for each Item. Click the Yes button.

To release the email transmission settings for each Item

In the procedure for setting the email transmission, delete the texts for Subject and Contents.

Clicking the OK button deletes all notification email items whose email transmission settings are enabled for each Item.

Note

Email for notifying Item transmission is sent on the basis of the email address registered in the user information. This means that if a user's email address has not been registered, email will not be sent to this user even if the email transmission setting has been specified. If no email address has been registered for the Item handler (email sender), the email address set in Sender's e-mail address in the Server Setup dialog box is used as the sender's email address.

Settings in Microsoft Internet Information Services

To send email notification of Item transmission, settings in Microsoft Internet Information Services are required in addition to the settings in Flow Designer.

Executing the SMTP Virtual Server

Make sure that the SMTP Virtual Server is executing. For details about how to set the SMTP Virtual Server, see 7.10.1 Executing the SMTP virtual server.

Relaying received email to a remote domain

By adding a remote domain to the SMTP Virtual Server, received email can be relayed to the remote domain. For details about how to relay received email to a remote domain, see 7.10.2 Adding a remote domain.

12.7 Changing registered Items

This section describes how to change an Item that was saved before completion and the sample Items provided by Asset Console.

You can define Items efficiently by using registered Items or by editing the sample Items that have been registered.

To modify a registered Item, select the Item Definition job menu to display the Item Definition window, and then modify the Item from the window.

12.7.1 Renaming an Item

You can rename an Item while its status is Creating.

To rename an Item:

In the Item Definition window, select the check box for the Item you wish to rename, and then click the Rename button.

A dialog box for specifying an Item name appears.

Specify an Item name.

You can register the same name for multiple Items.

To cancel, click the Cancel button.

Click the OK button.

The dialog box for specifying the Item name closes and the Item is renamed to the specified character string. In the Update user field, the name of the user that made this change appears.

12.7.2 Setting an Item to Exhibit or Not exhibit

You can change the status of an Item from Creating to Exhibit, so that a new Item can be created. Additionally, you can change the status of an Item from Exhibit to Not exhibit, so that a new Item cannot be created.

To change the Item status to Exhibit (or Not exhibit):

In the Item Definition window, select the check box for the Item whose status is to be changed, and then click the Exhibit (or Not Exhibit) button.

When the confirmation dialog box appears, click the OK button.

To cancel, click the Cancel button.

The status of the selected Item changes. In the Update user field, the name of the user that made this change appears.

You can also change the status of the Item from Not exhibit back to Exhibit.

12.7.3 Changing Item definitions

For a registered Item, you can change its definitions only while its status is Creating. For an Item in Exhibit or Not exhibit status, you must create a copy to change its definitions.

For an Item in Creating status, click its Item name link to display Flow Designer, where you can change the definitions.

To create a copy of an Item in Exhibit or Not exhibit status:

In the Item Definition window, select the Item name check box for the Item whose definitions are to be changed, and then click the Copy button.

A dialog box for specifying the Item name appears. You can register the same name for multiple Items.

To cancel, click the Cancel button.

Specify an Item name, and then click the OK button.

The dialog box closes.

Click Item name for the Item that was copied in the Item Definition window.

Flow Designer is displayed in editable status.

12.7.4 Deleting Items

You can delete Items that are in Creating or Not exhibit status. Note that an Item in Not exhibit status cannot be deleted while it is executing.

You can delete Items that are executing from the window that is displayed by clicking the Execution Item Management job menu. For details about how to delete Items that are executing, see 15.4 Managing Items (Execution Item Management).

To delete unneeded Items:

In the Item Definition window, select the Item name check box for the Item you wish to delete, and then click the Delete button.

To cancel, click the Cancel button.

When the confirmation dialog box appears, click the OK button.

The dialog box closes and the selected Item is deleted.

12.8 FAQs (Item definitions)

This section describes in the format of FAQs some of the problems that might occur during Item definition, along with the possible causes and actions to be taken.

12.8.1 The Edit Emails and Set Deadline buttons cannot be selected because they are disabled

When a node or activity is selected, the Edit Emails and Set Deadline buttons cannot be selected. Select somewhere other than a node or activity, such as a blank space in the background.

For details about how to use Flow Designer, see 12.3.1 Names of Flow Designer components and how to use them.

12.8.2 How can I change the email text that is created in Flow Designer for each node?

When you execute the Item, you can change the email text in the Select Destination dialog box.

For details about how to edit email at the time of sending it, see 15.1.1 Creating new Items.

12.8.3 How can I add and change the Item category?

In the Code window, click the managed class (Others) and then click the code ID MatterCategory. In the displayed window, add categories.

For details about how to add a code, see 16.8.1 Adding codes.

12.8.4 How can I interrupt at an intermediate point on the Item route?

Add a completed activity to the node on the route where you wish to interrupt.

For details about how to add completed activities, see 12.3.2 Placing workers and processing.

12.8.5 What happens to an Item for which a deadline is set when its deadline passes?

An icon indicating that the deadline has passed is displayed in the Outbox. Additionally, the Item information other than the Item name is displayed in red. An Item whose deadline has passed can still be executed.

For details about the Items that are displayed in the Outbox, see 15.3.1 Checking the status of a sent Item.

12.8.6 What is the difference between normal activities and completed activities?

For a normal activity, you can add the next node because it is sent to the next worker for further processing. For a completed activity, you cannot add a node because it is to complete the Item.

For details about how to add activities in Flow Designer, see 12.3.2 Placing workers and processing.

12.8.7 How can I set the objects to uniform attributes in Form Designer?

In Form Designer, you can use the Operation menu to set each object's attributes, such as color and size, to a uniform value.

For details about how to set objects to uniform attributes, see 12.4.4 Adjusting an object's style and position.

12.8.8 How can I align the position of objects in Form Designer?

In Form Designer, you can use the Operation menu to align the tops, bottoms, right sides, or left sides of selected objects.

For details about how to align objects, see 12.4.4 Adjusting an object's style and position.

12.8.9 In Form Designer, I specified an Item name for the New Item button, but why is it not displayed in the Select New Item dialog box?

The specified Item name is not displayed if the status of the specified Item is Not exhibit.

12.8.10 How can I display the objects, such as text fields, that were added at an intermediate node on the route also?

If you have defined a new object using the Form Designer for an intermediate node on the route, to inherit the same objects by the subsequent node, select the applicable objects from Defined object, which is displayed by selecting Form Designer's Object menu.

For details about how to add defined objects in Form Designer, see 12.4.3(1)(h) Defined object.

12.8.11 I defined the New Item button in Form Designer, but why is the desired Execution Item not displayed?

For Execution item, you can specify only those Items whose status is Exhibit. Other Items must be selected by the workers during Item execution or only their category can be specified.

For details about how to define the New item button in Form Designer, see 12.4.3(3)(k) Execution item.

12.8.12 I edited an Item window in Form Designer, but why is its OK button disabled, preventing me from registering it?

You may have edited an exhibit Item. You cannot edit an Item in Exhibit status. The same applies when email cannot be edited or an expiration date cannot be set or added.

If an Item has already been registered, its definitions can be edited only if its status is Creating. To change the definitions of an Item whose status is Exhibit or Not exhibit, make a copy, and then edit its definitions.

For details about how to create a copy of an Item, see 12.7.3 Changing Item definitions.

12.8.13 What happens if no activity is defined for the last node?

During Item execution, only confirmation takes place at the last node.

12.8.14 Why has nothing been defined for the Apply, Approve, Distribution request, and Complete activities for the provided standard Items?

This is because the asset management database is not updated.

Definition of an activity is required only if data is to be registered or updated in the asset management database when the Item is sent to the next worker. If the Item is to be simply sent to the next worker, no definition is required.

12.8.15 Why did my attempt to delete an Item fail (a message was displayed)?

An Item in Exhibit status cannot be deleted.

For details about how to delete Items, see 12.7.4 Deleting Items.

Part 5: Administration

13 Basic Operating Procedure

This chapter describes the basic operation and setup common to Asset Console operation windows.

The chapter also describes how to select the job menu that best suits your goals.

13.1 Logging in to and out of Asset Console

This section describes how to log in to and out of Asset Console.

13.1.1 Logging in

To use Asset Console, use a Web browser to access the login window and log in to Asset Console.

Notes

To ensure a secure environment, the first time you log in, make sure that you change the asset manager's default password (user ID: admin). We also recommend that you change the password periodically.

Even when Active Directory is used for authentication, the user IDs used for logging in must be managed as Asset Console user information. Only passwords can be consolidated when Active Directory is used for login authentication. To log in under a user ID that is not registered in Active Directory, that user ID must be authenticated as user information (user ID and password) managed in Asset Console. For example, user IDs and passwords that are registered only in Asset Console are managed in the asset management database, which is the case for the asset manager (user ID: admin).

To log in to Asset Console:

Open a Web browser and access the login window.

To access the login window, enter its URL into a Web browser. The URL of the login window is http://host-name/jp1asset/login.htm#.

When Asset Console is installed, a shortcut icon is created to the login window on the asset management server desktop. You can also use this shortcut icon to access the login window.

The following figure shows Asset Console's login window.

#

If you configure SSL on the Web site where the Asset Console's virtual directory is set in Microsoft Internet Information Services, the URL of the login window is https://host-name/jp1asset/login.htm.

Figure 13‒1: Login window

User ID text box

Enter the user ID.

Password text box

Enter the password.

Login button

Logs in to Asset Console and displays the top page.

Clear button

Clears the values that you specified for User ID and Password.

Enter your user ID and password to log in to Asset Console

Immediately after installation, only the asset manager (whose user ID and password are both admin) can use Asset Console. When you are logging in for the first time or when no Asset Console user has been registered, log in as the asset manager. Then use the Group and User job menu to register the users who will use Asset Console.

For details about registering users, see 16.1.2 Adding a user.

Click the Login button.

If Asset Console authentication is successful, the following initial window is displayed.

Figure 13‒2: Initial window

Note that if one of the following conditions applies, a message is displayed and the login is prohibited:

When a browser other than Windows Internet Explorer is used

When Windows(R) Internet Explorer(R) 10 or later was used without setting the website in Compatibility View Settings.

13.1.2 Logging out

To log out of Asset Console:

Click the Logout link in the upper right corner of the window.

If logout is successful, the message Logout was successful. is displayed, and then the login window is displayed.

From this window, you can log in to Asset Console again. To do so, enter your user ID and password.

Even if you do not log out manually, you are logged out automatically when the amount of time specified during setup elapses. If you have been logged out automatically, the character string The user has already logged out. is displayed when you execute a job from an operation window, and then the login window is displayed.

You can set the automatic logout time using the Communication-less monitoring time option, which is under Session Information in the Server Setup dialog box. For details about specifying settings in this dialog box, see 7.3.3 Setting Session Information.

13.2 Window component names and usage

This section describes the names of the window components used to execute asset management jobs, and explains how to use these components.

Asset Console consists of various windows for asset management jobs. The following figure shows the names of the window components.

Figure 13‒3: Names of window components

Simple search condition

To specify a group or location as a search condition or to specify registration and update values, simply select the corresponding group and location on the tree.

Use the tabs to switch between groups and locations.

The displayed group and location depend on the user role. For details about the access permission settings by user role, see 5.1.3 Assigning access permissions according to organizational hierarchy.

Also, if divisions are assigned to the login user, Divisions will be displayed when the Group tab is selected. Note that the assigned division names and division group names will be displayed for Divisions. Selecting a division name and group name from this tree enables you to specify group search conditions and values to be registered.

For details about how to configure settings for Divisions, see 16.1.6 Viewing and editing divisions. For details about selecting a division to use as a search condition or a value to be registered, see 13.6 Job menus that can be used to specify divisions as search conditions and values to be registered.

Display line

You can change the number of lines displayed in a page of search results by specifying the number of lines in the display lines input area and then clicking the Search button. You can specify a number from 1 to 1,000 for the number of lines; this setting is valid only for the specified window. The default number is 200.

To hide the display lines input area and display the same number of lines uniformly on all windows, specify the information in Basic information in the Server Setup dialog box. For details about how to hide the display lines input area, see 7.3.4(4) Show number column.

Calendar

Use the calendar to specify a date. Click the button to display the calendar.

The following figure shows how to use the calendar to specify a date.

Figure 13‒4: Using the calendar to specify a date

To close the calendar, click outside the calendar window (such as in the background).

Search condition

Displays the conditions for searching for asset information according to the selected job.

You can change the values to be specified in the search conditions according to the operation mode of the asset management system. You can also change the search conditions that can be specified depending on the user role. For details about each update method, see 11.2 Changing managed items (Customize Managed Items) or 11.3 Changing a window for a user role (Customize Job Windows).

Job menu

Enables you to select the work you wish to perform.

When you select a job menu in the tree, the corresponding window is displayed in the right-hand frame.

As is the case with simple search conditions, the displayed job menus depend on the user role.

You can also select the job menus to be displayed according to the operation mode of the asset management system. For details about how to view or hide job menus, see 11.4 Changing the executable jobs (Customize Job Menu).

Page transition

If the search results span multiple pages, click a link to display another page.

Each time you click a link, a different page is displayed.

>

Displays the next page.

<

Displays the previous page.

>>

Displays the last page.

<<

Displays the first page.

In the input area, you can also specify the page number of the page that you want to display. Clicking the Show button displays the specified page.

Search results list

Displays a list of asset information that satisfies the specified search condition. The search results contain only the asset information that can be processed by the user who is currently logged in.

You can select an item from these search results to perform further processing, such as viewing or editing details.

When an item title displays a down-pointing triangle () or up-pointing triangle (), clicking the title sorts the list in descending or ascending order respectively.

Message display area

Displays a message indicating the progress of processing.

Buttons

The window operation buttons are described next:

CSV button

Downloads as a CSV file the search results list, summary results list, or other list information displayed in the window.

PDF button

Outputs ( in PDF format) the search results list, summary results list, or other list information displayed in a window. For example, in the Device List window, asset number bar codes can be output. To output search results in PDF format, you must link with EUR.

For details about the required setup method for using the PDF button, see 7.3 Setting up the asset management server.

13.3 Search procedure

The asset management system enables you to total and search for managed asset information to best suit your goals.

This section describes the procedures for specifying search conditions to search for asset information and for executing various processing by using the search results. The following figure shows the search procedure and the window location that corresponds to each step.

Figure 13‒5: Search procedure

From the job menus, select the type of work you wish to execute (such as Device List).

The window for the selected job type is displayed.

Using a simple search condition or by clicking the Browse button, select a desired group or location.

You can easily specify a search condition by selecting a desired group or location from the appropriate tree. Use the tabs to switch between the group and location trees.

To clear a specified condition, click the icon on the top of the tree.

If divisions have been assigned to the login user, selecting the Group tab displays the assigned division names and division group names in the tree. If you wish to specify a division in a condition, select the corresponding division name and division group name from the tree. The Group and Division radio buttons are displayed in the Group field. Note that when you select Division, the Browse button is disabled. Select a desired division name and division group name from the tree to specify the search conditions.

Specify other search conditions, in addition to a group or location.

The possible search conditions depend on the job type. If you specify multiple search conditions, they are treated as being joined by logical AND.

Click the Search button.

A listing of the search results is displayed.

You can output the search results as a CSV file.

13.3.1 Hints on searching for asset information

This subsection provides advice on specifying conditions for searching for asset information.

Searching by Asset No. or Contract No.

If you know the asset number of the asset to be searched for, enter the asset number and select match all the words. You can identify the asset with a single search because a unique asset number is assigned to each asset.

If the asset numbers are classified by category and you know only a part of the asset number, you can specify match part of the words, match beginning of the words, or match end of the words to search for the asset. The same applies to the contract numbers that are used when contract information is searched.

Searching by Device type

For the device type, you can specify Computing, Networking, or Accessories, and then further narrow down the type.

By specifying the type in two stages, you can narrow down the search condition according to purpose, such as searching for devices by type or for a specific device.

Searching by Software name

If you search the asset information for software names managed by Asset Console, you need to be aware that there are two types of software names, as described below. Note that these software names might not match for the same software item.

Software name

This is the name of the software that was registered as the target for license management. Software name in the search condition normally assumes this name.

Installed software name

This is the name of the software installed on devices. If you register management information acquired by JP1/IT Desktop Management 2 - Manager, this is the name of the software collected by JP1/IT Desktop Management 2 - Manager.

Searching by match part of the words

Searches performed by using the match part of the words, match beginning of the words, or match end of the words options in the drop-down list, as well as searches for items under the including label such as user names, are case sensitive.

If you execute a search that returns thousands or tens of thousands of results, JavaScript runtime errors might occur in the browser. Therefore, specify as many search conditions as possible to reduce the number of output search results.

13.4 Registration procedure

The asset management system enables you to register asset information, such as devices, contracts, and software items, from the windows.

This section describes the procedure for registering asset information, such as devices, contracts, and software items. The following figure shows the registration procedure and the location in the window that corresponds to each step.

Figure 13‒6: Registration procedure

From the job menus, select the type of work you wish to execute (such as New Device).

The window for the selected job type is displayed.

In the displayed window, specify each item.

Items identified by a star () are mandatory.

Specify a group or location by selecting it from the simple search conditions. If a division has been assigned to a login user, the group of a job corresponding to a division can also be specified by selecting the division group from the tree.

To specify a user name, enter it from the keyboard or use the Browse button.

To specify an attached file, use the Attach button.

Click the OK button.

The specified information is registered into the asset management database.

13.4.1 How to specify a group

The two methods of specifying a group are to use the Browse button or to select the group from the simple search conditions tree. Note that when you select Division, the Browse button is disabled. Select the division group name from the simple search conditions tree. However, in the dialog box displayed by clicking a link or a button from the operation window, you cannot specify a group by selecting it from the simple search conditions tree.

To use the Browse button to specify a group:

In the group specification field, click the Browse button.

The Browse Groups dialog box is displayed.

From the tree, select the desired group, and then click the OK button.

The Browse Groups dialog box closes, and the selected group is specified.

The following figure shows the Browse Groups dialog box in which a group is selected.

Figure 13‒7: Browse Groups dialog box

13.4.2 How to specify a user name

You can specify a user name by using the Browse button or by directly typing the user name from the keyboard. If the user to be specified is registered in Asset Console, you can use either of these two methods. If the user is not registered, such as in the case of a user who only uses the device, you must directly type the user name from the keyboard.

To specify a user name by using the Browse button:

In the user name specification field, click the Browse button.

The Browse Users dialog box is displayed.

From the tree, select the group to which the user belongs.

A list of users belonging to the selected group is displayed.

Select the desired user name, and then click the OK button.

The Browse Users dialog box closes, and the selected user is specified.

The following figure shows the Browse Users dialog box with a user selected.

Figure 13‒8: Browse Users dialog box

13.4.3 How to specify an asset location

In the dialog box that is displayed by clicking a link or button in a window, use the Browse button to specify a location.

To specify a location:

In the location specification field, click the Browse button.

The Browse Locations dialog box is displayed.

From the tree, select a location, and then click the OK button.

The Browse Locations dialog box closes, and the selected location is specified.

The following figure shows the Browse Locations dialog box with a location selected.

Figure 13‒9: Browse Locations dialog box

13.4.4 How to specify an attached file

Files that are to be managed together with contracts, license certificates, and other contract information can be registered as attached files.

To specify an attached file:

Click the Attach button in the attach file specification area.

The Edit Attached Files dialog box is displayed.

Click the Add button.

The File Registration dialog box is displayed.

Click the Browse button.

A dialog box for selecting a file is displayed.

Select the file to be added, and click the Open button.

The specified file is added to File name when saved and Upload file. You can edit the character string displayed in File name when saved.

Click the OK button.

The specified file is added.

Click the Close button.

The File Registration dialog box closes.

Click the Close button.

The Edit Attached Files dialog box closes.

At this point, the added file is not yet registered in the asset management system. When you click the OK or Update button on a window that has an attached file specification area, the file is registered with the asset management system.

Note that if the added file is opened before the file is registered, it is downloaded with a file name that is different from the one specified in File name when saved.

The following figure shows the Edit Attached Files dialog box with files specified.

Figure 13‒10: Edit Attached Files dialog box

13.5 Differences in window functions by user role

This section presents the differences in the job menus displayed in the window depending on the user role, and describes limitations to the accessible asset information depending on the user role.

13.5.1 Differences in job menus

The functionality available in windows depends on the user role. The two user roles that use window operations are user and administrator.

The following table describes the default job menus for each user role.

Table 13‒1: Differences in job menus by user role

Job category

Job menu

User

Administrator

Item

New Item

Y

Y

Inbox

Y

Y

Outbox

Y

Y

Execution Item Management

N

Y

Device Management

Device Totals

Y

Y

Device List

Y

Y

Unused Device List

Y

Y

New Device

Y

Y

Batch Update

Y

Y

Totals of Stocktaking-Unexecuted Devices

Y

Y

Confirm Stocktaking Device

N

Y

Device Change Log

Y

Y

Contract Management

New Contract

N

Y

Contract List

N

Y

Problems

Problems

Y

Y

Software License

Owned License List

Y

Y

Excess License List

Y

Y

Unauthorized Usage List

Y

Y

Unknown Usage List

Y

Y

New Software

Y

Y

Software List

Y

Y

Transfer License

Y

Y

New Volume License

Y

Y

Volume License List

Y

Y

Totals List & Execution

N

Y

Update History

Y

Y

Software Usage Management

Unauthorized Install List

Y

Y

System Management

Group and User

N

Y

Search Users

Y

Y

Location

N

Y

IP Group

N

Y

Device Catalog

N

Y

Software Name

N

Y

Installed Software

N

Y

Code

N

Y

Individual Information

Y

Y

Import

N

Y

Export

N

Y

Result Import

N

Y

Log

N

Y

ITDM2 management information acquisition

N

Y

System Definition

Role

N

Y

Customize Managed Items

N

Y

Customize Job Windows

N

Y

Customize Job Menu

N

Y

Create User Report

N

Y

Acquire Device Update Record Items

N

Y

Item Definition

N

Y

Official Authority

N

Y

Legend:

Y: Available

N: Not available

You can change the available job menus for each user role. For details, see 11.4 Changing the executable jobs (Customize Job Menu).

13.5.2 Differences in accessible asset information

The asset information accessible from windows depends on the user role.

If access is limited by group level, a user can reference only the asset information permitted for his or her group, including all lower groups, assuming the group's managed label is the same as for the user role. For details about setting access control by group level, see 5.1.3 Assigning access permissions according to organizational hierarchy.

13.6 Job menus that can be used to specify divisions as search conditions and values to be registered

When Division is displayed in the tree of the Group tab of simple search conditions, you can select a division from this tree to specify a group search condition and registration values. However, some job menus do not allow you to specify divisions. Also, even among job menus that do allow you to specify divisions, some permit only a division group name to be specified.

The following table lists the job menus that support this function.

Table 13‒2: Job menus that can be used to specify divisions as search conditions and values to be registered

Job category

Job menu

Whether specifiable

Division name

Division group name#

Device Management

Device Totals

Y

Y

Device List

Y

Y

Unused Device List

Y

Y

New Device

N

Y

Batch Update

Y

Y

Totals of Stocktaking-Unexecuted Devices

Y

Y

Device Change Log

Y

Y

Contract Management

New Contract

N

Y

Contract List

Y

Y

Software License

Owned License List

Y

Y

Excess License List

Y

Y

Unauthorized Usage List

Y

Y

Unknown Usage List

Y

Y

New Software

N

Y

Software List

Y

Y

Transfer License

Y

Y

New Volume License

N

Y

Volume License List

Y

Y

Update History

Y

Y

Software Usage Management

Unauthorized Install List

Y

Y

Legend:

Y: Can be specified.

N: Cannot be specified.

#

For groups assigned to the division.

14 Executing Asset Management Jobs

This chapter describes the details of each job and of the window operations.

14.1 Device Management

This section describes how to execute device-related asset management jobs.

Device Management enables you to use the centrally managed information as a device management ledger, such as for totaling the number of devices held (owned) by each group and for searching for specific devices.

The job menus related to device management are displayed under the Device Management job category.

This section describes the operations available from each menu and shows the windows. Each subsection title contains the selected menu name in parentheses.

14.1.1 Checking the number of owned devices (Device Totals)

By using managed items, you can total the number of owned devices by group or location, as well as for the entire organization. You can check the number of each type of device and the number of devices that are to be replaced for each group or location. For example, Status can be used as the point of (filter for) totals to check the number of devices that are active or in stock for each status. Reg. date can also be used as a point of totals to check the number of installed devices.

To total the number of owned devices, start from the Device Totals window, which is displayed by clicking the Device Totals job menu. The following figure shows the Device Totals window.

Figure 14‒1: Device Totals window

In the Server Setup dialog box, you can set the device statuses that are displayed for the Status search condition. For details about how to configure this setting, see 7.3.4(18) Status to display in device search windows.

(1) Totaling the number of owned devices by specifying conditions

To total the number of owned devices by group or location, select Group name or Location for the Totals by search condition. You can filter the range to be totaled for the group or location by specifying simple search conditions or by using the Browse button.

To total by device status or by manufacturer, select the items to total via the Point of totals search condition. To change which items to total, select Asset information or Hardware information from the Point of totals search condition, and then select the details from the drop-down list to the right. The default is Device type for Hardware information.

(2) Displaying a breakdown of the totaled results

By clicking a link corresponding to the details specified via Point of totals and displayed for totaled results, a breakdown of totaled results is displayed. From here, you can also display details about an individual device. For details about how to view and edit details about an individual device, see 14.6 Managing device details.

The following figure shows the window that displays a breakdown of the details specified by Point of totals.

Figure 14‒2: Window displaying a breakdown of details specified by Point of totals (Device Totals)

(3) Changing the display widths of the totaled results

You can change the display widths of the items in the totaled results. For details about how to change the display widths, see 11.3.6(3) Setting the display widths for the items in search results.

14.1.2 Searching for devices (Device List)

By using the Device List job menu, you can search for specific devices among owned devices. For example, you can list devices for a particular purpose, such as to identify devices with an old registration date or devices whose performance is below a specified level. You can also change information about the listed devices.

To search for devices, start from the Device List window, which is displayed by clicking the Device List job menu. The following figure shows the Device List window.

Figure 14‒3: Device List window

In the Server Setup dialog box, you can set the device statuses that are available for the Status search condition. For details about how to configure this setting, see 7.3.4(18) Status to display in device search windows.

(1) Specifying search conditions for a particular purpose

In Device List, specify the necessary search conditions. The following are examples of specifying conditions for searching for owned devices.

Searching for devices to be replaced

To search for old devices or for devices whose performance is below a specific level, specify an item such as Reg. date, Processor speed, or Memory.

Searching for devices to be scheduled for maintenance

If you know the name of the device, specify Device name to search for it. If not all the device names are registered, also specify Device type for a more thorough search.

Be aware that IP address segments can be specified with two or fewer digits when both specifying an IP address for a search condition and searching for partial matches or beginning-of-word matches. For example, if 33.22.1 is specified for a search, the search is conducted in the range from 33.22.100.xxx to 33.22.199.xxx. Therefore, if you want to search for 33.22.1.xxx, enter a period (.) at the end, as in 33.22.1., or place zeros in front of the number, as in 33.22.001. For example, if you want to search for xxx.22.1.xxx, specify .22.1. or 022.001.

(2) Displaying device details

In the search results list, clicking a link under Asset No. displays the Device Details dialog box, which enables you to view and edit details about that device. For details about how to view and edit details about a device, see 14.6 Managing device details.

14.1.3 Searching for unused devices (Unused Device List)

By using the Unused Device List job menu, you can check for devices that are not being used. This helps you utilize your assets more efficiently because you can assign unused devices when device distribution requests are received from groups.

A device is unused if its information has not been updated for a specified period of time. To search for unused devices, start from the Unused Device List window, which is displayed by clicking the Unused Device List job menu. The following figure shows the Unused Device List window.

Figure 14‒4: Unused Device List window

In the Unused Device List window, the devices that are regarded as being active are searched for in order to identify the devices that have not been used for the period specified in the Last date used search condition.

From Unused Device List, only devices whose operation status is being managed can be displayed. Use the Device Details dialog box to specify whether a device's operation status is to be managed.

If management information is acquired from JP1/IT Desktop Management 2 - Manager, a device whose management information has not been updated (at the specified time since the management information was last acquired) is regarded as inactive.

For details about how to handle devices as unused devices, see 14.6.1 Viewing and changing device details (Device tab).

(1) Displaying device details

In the search results list, clicking a link under Asset No. displays the Device Details dialog box, which enables you to view and edit details about that device. For details about how to view and edit details about a device, see 14.6 Managing device details.

(2) Changing the status of unused devices in a batch operation

To change the status of unused devices to Scrap in a batch operation, the management information of the unused devices must be changed as follows:

Specify Group name and Location search conditions as necessary, specify Active for Status, and then click the Search button.

The devices that match the conditions are searched for.

Click the Select All button, and click the Batch Update button.

The Set Changes dialog box is displayed.

Select the Status check box.

From the Status drop-down list, select Scrap.

The Status is set to Scrap.

To cancel, click the Close button.

Click the Update button.

The Set Changes dialog box closes, and the devices for which Status is Active are changed to Scrap.

From the Set Changes dialog box, select the check box of the item to be changed. To delete a registered value, select the check box, and then click the Update button without setting a value. However, the values for Status, Usage management, and Device type cannot be deleted.

The following figure shows the Set Changes dialog box with Status set to Scrap.

Figure 14‒5: Set Changes dialog box

14.1.4 Registering device information (New Device)

By using the New Device job menu, you can register a new device. You can add devices to be managed by registering, for example, accessories for which information cannot be collected from JP1/IT Desktop Management 2 - Manager and devices that are not connected to the network.

To register a new device, start from the New Device window, which is displayed by clicking the New Device job menu. The following figure shows the New Device window.

Figure 14‒6: New Device window

Asset numbers when multiple devices are registered

You can use batch mode to register the same device information for multiple devices by specifying a numeric value in Number. The New Device window enables you to register a maximum of 500 devices at one time.

When more than one device is registered, the automatically assigned number is registered as the asset number, not a specified value.

If you want to specify the asset numbers to be assigned, you must register the devices one at a time, and specify the desired value in Asset No. along with any other required command information.

How to specify the user name

To specify a user name, either use the Browse button or directly enter the name using a keyboard. The latter method enables you to specify a user name that is not registered in Asset Console.

However, a user name cannot be directly entered if the user name is already registered. If that is the case, use the Browse button to find the user with that name.

Tip

You can specify attached files in the New Device window. Because attached files are hidden by default, perform the following procedure to change the display setting:

Select the job menu item System Definition, Customize Managed Items, and then click the anchor for VariousInfo under class.

Under managed class in the displayed dialog box, click ValueText.

Under properties in the displayed dialog box, select the check box for the display of HardwareInfo_AttachFile, and then click the Update button.

(1) How to register information using a device catalog

Device information, such as the CPU and memory size, is predetermined for each product. A device catalog is a collection of these information items registered for a product.

By selecting a product from among the device catalogs, because one or more items will already be set for that product, you can eliminate the time required to enter that information.

For details about registering a device catalog and the items that can be specified, see 16.5 Managing device catalog information (Device Catalog).

To register device information using a device catalog:

In the upper-right corner of the window, click the Browse Catalog button.

The Browse Device Catalog dialog box is displayed.

Specify search conditions, as necessary.

Specify one or more of the following: Device type, Device name, Model, and

Developer.

Click the Search button.

A list of catalog entries is displayed. Clicking a column title sorts the list in either ascending order or descending order by that column.

Clicking a link under Device name enables you to view the content of the catalog.

To cancel, click the Close button.

Select the desired catalog items, and then click the OK button.

The Browse Device Catalog dialog box closes, and the information in the catalog information is specified for the corresponding items.

Specify each item that cannot be registered from the catalog, and then click the OK button.

Items identified by a star () are mandatory.

The device information is registered based on the specified information.

You can change the information registered here from the Device Details dialog box that is displayed from the search results of a window such as Device List window.

The following figure shows the Browse Device Catalog dialog box in which device catalogs are searched for.

Figure 14‒7: Browse Device Catalog dialog box

14.1.5 Changing device information (Batch Update)

By using the Batch Update job menu, you can change such device information as Group name, Location, and Status in a batch operation. This is useful when moving your work location or changing the office layout.

To change device management information in a batch operation, start from the Batch Update window, which is displayed by clicking the Batch Update job menu. The following figure shows the Batch Update window.

Figure 14‒8: Batch Update window

Clicking a link under Asset No. enables you to view and edit the details about that device.

(1) Changing the location

To change device management information by, for example, moving the Sales Dept. from A Building to B Building:

For the search conditions, specify Head Office/Sales Dept. in Group name, New York/A Building in Location, and Active in Status, and then click the Search button.

The system searches for devices used by the Sales Dept. in the A Building.

Click the Select All button, and then click the OK button.

The Set Changes dialog box is displayed.

Select the Location check box.

Click the Browse button for Location, and select B Building from the Browse Locations dialog box.

New York/B Building is specified in Location.

To cancel, click the Close button.

Click the Update button.

The Set Changes dialog box closes, and the location of the devices used by the Sales Dept. changes from A Building to B Building.

From the Set Changes dialog box, select the check box of the item to be changed. To delete a registered value, select the check box, and then click the Update button without setting a value. The values for Status, Usage management, and Device type cannot be deleted.

The following figure shows the Set Changes dialog box in which the new location is specified.

Figure 14‒9: Set Changes dialog box

14.1.6 Checking the number of devices that require stocktaking (Totals of Stocktaking-Unexecuted Devices)

By using the Totals of Stocktaking-Unexecuted Devices job menu, you can total the number of devices for which stocktaking has not been completed by group or location. You can check the progress of stocktaking jobs, and perform stocktaking for devices that require stocktaking.

To total the number of devices for which stocktaking has not been performed, start from the Totals for Non-Stocktaking Devices window, which is displayed by clicking the Totals of Stocktaking-Unexecuted Devices job menu. The following figure shows the Totals of Stocktaking-Unexecuted Devices window.

Figure 14‒10: Totals of Stocktaking-Unexecuted Devices window

A list is displayed of devices whose device status category is Active, but for which stocktaking has not been performed since the date entered in Stocktaking start date in the search conditions.

(1) Totaling the devices for which stocktaking has not been executed by group

To total the devices for which stocktaking has not been performed for each group, select Group name as the search condition in Totals by. To narrow down the range of groups to total, use a simple search condition or the Browse button to specify desired groups.

(2) Totaling the devices for which stocktaking has not been executed by location

To total the devices for which stocktaking has not been performed for each location, select Location as the search condition in Totals by. To narrow down the range of locations to total, use a simple search condition or the Browse button to specify desired locations.

(3) Displaying a breakdown of the totaled results

From displayed totaled results, clicking a link under Device type displays a breakdown by device type. From here, you can also display details about individual devices. For details about how to view and edit details about an individual device, see 14.6 Managing device details.

The following figure shows the window that displays a breakdown of totaled results by device type.

Figure 14‒11: Window that displays a breakdown of totaled results by device type (Totals of Stocktaking-Unexecuted Devices)

(4) Downloading the totaled results

You can download the totaled list of devices for which stocktaking has not been performed as a CSV file. To do this, in the Totals of Stocktaking-Unexecuted Devices window or the window that displays the breakdown of totaled results, click the CSV button.

The information that is downloaded as a CSV file includes Group name, Asset No., Device type, Reg. date, User name, Status, Location, Start date of use, and End date of use.

14.1.7 Registering actual stocktaking data (Confirm Stocktaking Device)

You can add to the Asset Management database the information for the devices for which stocktaking has been performed (results of stocktaking). This enables you to exclude those devices for which stocktaking has not been performed.

By default, only the administrator can register actual stocktaking data.

To register actual stocktaking data, start from the Confirm Stocktaking Device window, which is displayed by clicking the Confirm Stocktaking Device job menu. The following figure shows the Confirm Stocktaking Device window.

Figure 14‒12: Confirm Stocktaking Device window

For Stocktaking data CSV file, specify the name of the CSV file that contains the actual stocktaking data.

You should check that the specified file is a CSV file. If a large file is specified and an error occurs, it might take a considerable amount of time before the error is reported.

Format of the CSV stocktaking data file

The format of the CSV file to be registered to the asset management database as actual stocktaking data is shown below.

Table 14‒1: Format for registering stocktaking data

Column

Item name

Description

Omissible

1

Asset No.

Specifies the asset number of the asset to be registered as a stocktaking-completed asset.

M

2

Stocktaking date

Specifies the stocktaking date according to the following format:

YYYY/MM/DD

O#

Legend:

M: Mandatory

O: Optional

#

If the stocktaking date is omitted, the date the CSV file is registered is used for the stocktaking date.

Note

If you use Microsoft Excel to directly open and edit a CSV file to be registered into Asset Console, any leading zeros (0) are automatically deleted from codes, IDs, and other numbers that start with one or more zeros (0). As such, the values might be updated with values that are different from the original values. When using Microsoft Excel, use the Import Text File function to set the data format for columns to Text, and then read and edit the file.

14.1.8 Managing the device change log (Device Change Log)

By using the Device Change Log job menu, you can manage change log information, such as for a computing device's CPU, memory size, and disk space. You can detect increases or changes in memory and hard disk drives by browsing for changes in the memory size and disk space. You can also use this job to manage the change logs of IP addresses and MAC addresses.

Device change logs are acquired when you register management information from JP1/IT Desktop Management 2 - Manager.

To manage device change logs, start from the Device Change Log window, which is displayed by clicking the Device Change Log job menu. The following figure shows the Device Change Log window.

Figure 14‒13: Device Change Log window

If you click an Asset No. link in the search results list, the Device Details dialog box is displayed, allowing you to view the details of the corresponding device.

Providing email notification for device change logs

When any device change log data is acquired, the asset administrator can be notified via email of the number of devices for which the change occurred. For details about how to provide email notification regarding the number of devices for which a change has occurred, see 7.9.8 Notification of device information change.

(1) Collecting the change logs for a specified period

In the Device Change Log window, for the search conditions, specify the period for which to acquire device change logs. By performing this type of search, you can obtain the change logs regarding the CPU, memory, and disk capacity devices for the specified period.

If you want to know when changes were made to a device's CPU, memory, or disk space, or if you want to see change logs related to the computing device type of each device, select the managed group, specify the start date and end date for Update date for the period over which you want to collect the logs, and then perform a search.

If the start date is omitted and only the end date is specified, logs are collected from the earliest date that JP1/IT Desktop Management 2 - Manager's management information was collected, until the end date.

If the end date is omitted and only the start date is specified, the logs are collected from the specified start date until the most recent log date.

(2) Collecting change logs for network addresses

To discover if an IP address or a MAC address has changed, specify Network address as a search condition.

Before you can acquire change logs for network addresses (IP or MAC addresses), you must first use the Acquire Device Update Record Items job menu to set IP addresses and MAC addresses as items for which to acquire change logs. For details about setting items to collect as change logs, see 11.6 Selecting the items to be acquired as device change logs (Acquire Device Update Record Items).

For Network address, IP addresses and MAC addresses are displayed in the form IP-address - MAC-address. If change logs are set to be acquired for only one of these types of addresses, however, only change logs for addresses of that type are displayed.

Note

The MAC address value is used as the key for acquiring change logs for network addresses. For this reason, if MAC addresses are not set to be acquired as change logs, a change log might be acquired even if the IP address has not changed.

14.2 Contract Management

This section describes how to execute asset management jobs related to maintenance, lease, and rental contracts.

Contract Management involves the registration of new contract information and the editing of existing contract information.

The jobs related to contract management are displayed under the Contract Management job category. This section describes the operations available from each menu and shows the windows. Each subsection title shows the selected menu name in parentheses.

14.2.1 Registering contract information (New Contract)

By using the New Contract job menu, you can register various types of contract information for devices and software assets.

When a new contract is registered, the corresponding device or software information is not registered. After the contract is registered, use the Contract List job menu to add the subject devices or software.

By default, only the administrator can register new contracts.

To register new contract information, start from the New Contract window, which is displayed by clicking the New Contract job menu. The following figure shows the New Contract window.

Figure 14‒14: New Contract window

(1) Using existing data to register new information

You can use existing data to specify information about a company with which a maintenance or lease contract is to be signed. To use existing data, use the Company Catalog.

The Contract Catalog dialog box can be used to specify the fields Contracted company, Contact post address, Contact phone/e-mail, Contact person, and User properties. For details about how to specify user properties, see 11.2.3 Adding managed items.

To specify information about a contracted company using existing information:

Click the Browse button for Contracted company.

The Company Catalog dialog box is displayed.

The Company Catalog dialog box displays a maximum of 20 contracted companies that have been registered most recently.

To cancel, click the Close button.

Select the applicable contracted company and then click the OK button.

The Contract Catalog dialog box closes and the values for Contracted company, Contact post address, Contact phone/e-mail, and Contact person are set. If user properties have been added as managed items, the user properties are also set.

Specify other information, and then click the OK button.

Items identified by a star () are mandatory.

Contract data can also be registered as attached data. For details about how to specify attached files, see 13.4.4 How to specify an attached file.

The contract information is registered based on the specified values.

The following figure shows the Company Catalog dialog box, which is displayed by clicking the Browse button.

Figure 14‒15: Company Catalog dialog box

To delete registered information, select the corresponding contracted company, and then click the Delete button.

14.2.2 Changing contract information (Contract List)

By using the Contract List job menu, you can search for contracts that are about to expire and change various contract information that has been registered. You can also use this job to add device and software information to newly registered contract information.

By default, only the administrator can change contract information.

To change contract information, start from the Contract List window, which is displayed by clicking the Contract List job menu. The following figure shows the Contract List window.

Figure 14‒16: Contract List window

(1) Searching for contracts that are about to expire

To search for contracts that are about to expire, specify Contract end date as the search condition.

In addition to using window operations to search for contracts that are about to expire, you can use a Notification of invalid contract information task registered in Windows Task Scheduler to have emails sent to the administrator. For details about using a task to send email notification, see 7.9 Setting the tasks that are registered in Task Scheduler.

(2) Browsing and changing contract information

Clicking a link under Contract No. displays the Contract Details dialog box below and enables you to change the contract's information items.

Figure 14‒17: Contract Details dialog box

You can update contract information by editing the information, and then clicking the Update button. To cancel, click the Close button.

If the system is set up to acquire contract history, clicking the Update button displays a dialog box that lets you choose whether the contract information is to be registered as contract history. Choose Yes to register the updated information and to register the information as contract history. Choose No to only register the updated information, but not register the information as contract history.

To acquire contract history, open the Server Setup dialog box, and select Acquire for Acquisition of contract history.

(3) Adding devices subject to a contract

To add devices to a contract:

Search for the contract to which devices are to be added.

You cannot add devices to a contract that is in the expire or erase status.

In the search results list, click the applicable Contract No. link.

The Contract Details dialog box is displayed.

From the Device tab, click the Add button.

The Search Device Details dialog box is displayed.

Specify conditions as necessary, and then click the Search button.

The system searches for the devices that are not under any other contracts for the devices that satisfy the specified conditions.

To cancel, click the Close button.

In the search results, select a desired device, and then click the OK button.

The selected device is added as a device that is subject to the contract.

The following figure shows the procedure for displaying the Search Device Details dialog box from the Device tab and then adding a target device.

Figure 14‒18: Procedure for adding a target device

(4) Changing the devices subject to a contract

To change (delete or restore) devices subject to a contract:

Search for the contract for which devices are to be changed.

You cannot change devices for a contract that is in the expire or erase status.

In the search results list, click the Contract No. link.

The Contract Details dialog box is displayed.

Click the Device tab.

The devices subject to the contract are listed.

To cancel, click the Close button instead of clicking the Delete or Restore button.

Deleting devices

Select the check box of each device to be deleted, and click the Delete button.

Restoring devices to a lease contract

Select the check box of each device to be restored, and click the Restore button.

Click the Close button.

The Contract Details dialog box closes, and the devices subject to the contract are changed.

(5) Adding software subject to a contract

To add or change the software subject to a contract:

Search for the contract to which software is to be added.

You cannot add software to a contract that is in the expire or erase status.

In the search results list, click the appropriate Contract No. link.

The Contract Details dialog box is displayed.

From the Software tab, click the Add button.

The Search Software dialog box is displayed.

Specify conditions as necessary, and then click the Search button.

The system searches for software that satisfies the specified conditions.

To cancel, click the Close button.

In the search results, select the desired software, and then click the OK button.

The selected software is added as software that is subject to the contract.

The following figure shows the flow for displaying the Search Software dialog box from the Software tab and then adding software.

Figure 14‒19: Procedure for adding software

(6) Changing software subject to a contract

To change (delete or restore) software subject to a contract:

Search for the contract for which software is to be changed.

You cannot change software for a contract that is in the expire or erase status.

In the search results list, click the Contract No. link.

The Contract Details dialog box is displayed.

Click the Software tab.

The software subject to the contract is listed.

To cancel, click the Close button instead of clicking the Delete or Restore button.

Deleting software

Select the check box for each software item to be deleted, and click the Delete button.

Restoring software

Select the check box of the software to be restored, and click the Restore button.

Click the Close button.

The Contract Details dialog box closes, and the software subject to the contract is changed.

(7) Viewing the contract update history

You can view the history of updated contract contents as well as previous contract contents. To view the contract history, open the Server Setup dialog box, and select Acquire for Acquisition of contract history. The Contract Details dialog box displays the History Information button. Click this button to view the contract history.

To view contract history:

Click the History Information button of the Contract Details dialog box.

The Contract History dialog box is displayed.

Click the link of the Update date/time for which you wish to view details.

The Contract History Details dialog box is displayed.

You can check the contract contents, which include the attached file, and output the contents to a CSV file.

The following figure shows the procedure for displaying the Contract History dialog box and Contract History Details dialog box from the Contract Details dialog box and checking contract history details.

Figure 14‒20: Flow for checking contract history details

Clicking a link under Asset No. displays the corresponding Device Details dialog box (or Software Details dialog box). However, if the relevant device or software has already been deleted, only the asset number is displayed.

When you output contract contents to a CSV file, the contents of attached files are not output.

14.3 Problems

This section explains how to execute asset management jobs related to problems.

Problems enables you to manage problems in the asset management system. If JP1/ IM is linked to, you can share JP1 events and SNMP trap information managed by JP1/ IM.

For details about linking to JP1/IM, see 8.1 Settings to link to JP1/IM.

The problem management jobs are displayed under the Problems job category.

This section describes the operations available from this job menu and shows the windows. Each subsection title shows the selected menu name in parentheses.

14.3.1 Managing system problems (Problems)

By using the Problems job menu, you can manage problems in the asset management system by viewing the JP1 events, the problems registered from SNMP traps converted to JP1 events, and the error information registered by Asset Console.

You can view information about problems in the Problems window, which is displayed by clicking the Problems job menu. The following figure shows the Problems window.

Figure 14‒21: Problems window

The window displays a list of JP1 events, problems registered from SNMP traps converted to JP1 events, and registered error information. Clicking a link under Reg. date displays the corresponding details.

Note

The Host where problem occurred value for an SNMP trap shows the IP address (or host name) of the server on which the JP1/Base that collected the SNMP trap is operating.

(1) Specifying search conditions for a particular purpose

This subsection describes the specification of conditions for searching for problems in the asset management system.

Searching for serious errors

To check whether there are any serious problems, specify Importance as the search condition for a search for problem information.

Referencing the previous error handling procedures

To reference previous error handling procedures, specify information, such as the nature of the error or the corrective action, as the search condition. Error handling might be facilitated by referencing the procedures used in the past to handle similar errors.

(2) Registering error information

To register error information:

Click the Add button.

The Add Problem dialog box is displayed.

Specify an overview of the problem, and then click the OK button.

Items identified by a star () are mandatory.

By default, only User Registered can be selected in Problem type. Make additions or changes, as necessary. For details about how to add or change the items in Problem type, see 16.8 Adding and changing types and statuses (Code).

Click the Close button.

The Add Problem dialog box closes, and the specified information is registered.

The following figure shows the Add Problem dialog box in which the information to be registered is specified.

Figure 14‒22: Add Problem dialog box

(3) Changing error information

To change registered error information:

In the search results list, click the Reg. date link for the information you wish to change.

The Problem Details dialog box is displayed.

Click the Edit button.

The Edit Problem dialog box is displayed.

Change the information, and then click the Update button.

Items identified by a star () are mandatory.

The Edit Problem dialog box closes, and the specified information is applied.

The following figure shows the Edit Problem dialog box.

Figure 14‒23: Edit Problem dialog box

(4) Reporting the completion of an action to JP1/IM

When a problem is resolved in the asset management system, you can report this event to JP1/IM. The status of the reported JP1 event is updated to Complete by JP1/IM. For details about the settings needed to report completion, see 8.1.1(2) Setting error completion notification.

To report completion of an action to JP1/IM:

In the search results list, click the Reg. date link for the JP1 event or SNMP trap that has been handled.

The Problem Details dialog box is displayed.

Click the Edit button.

The Edit Problem dialog box is displayed.

Specify an overview of the solution, and then click the Complete button.

The Complete button is displayed only for JP1 events and SNMP traps that have been acquired from JP1/IM.

Items identified by a star () are mandatory.

Completion of the action is reported to JP1/IM.

Click the Close button.

The Edit Problem dialog box closes.

(5) Deleting problem information

To delete problem information from the list of search results, select the check box of the problem information that you wish to delete, and then click the Delete button.

14.4 Software License

This section explains how to execute asset management jobs related to software licenses.

The following jobs are executed for license management:

Checking the license usage status from the totaled results to determine if there are exceeded licenses or invalid licenses being used.

Software asset information maintenance, such as registering information on purchased software and changing group licenses.

Registering information on volume licenses and managing points-based licenses.

The total number of licenses can be obtained by executing the Totals List & Execution job menu or by periodically executing a Notice of license excess task or a Totals number of licenses task registered in Windows Task Scheduler. If the totals are based on management information collected from JP1/IT Desktop Management 2 - Manager, select the Software information check box in Acquisition target in the ITDM2 management information acquisition job menu.

The jobs related to license management are displayed under the Software License job category. This section describes the operations available from each menu and shows the windows. Each subsection title shows the selected menu name in parentheses.

14.4.1 Checking the license usage status (Owned License List)

By using the Owned License List job menu, you can total the number of software licenses held (owned licenses), the number of software licenses being used, and the number of available software licenses. You also use this job to check the license usage status. If licenses are applied to downgrade software, their numbers are also totaled.

To total the usage status of licenses, start from the Owned License List window, which is displayed by clicking the Owned License List job menu. The following figure shows the Owned License List window.

Figure 14‒24: Owned License List window

From the Owned License List window, this job totals the software assets that are in the active status and within their valid usage period.

If nothing is displayed in the Date of summary search condition

Owned License List totals the license usage status on the basis of existing totaled results. If nothing is displayed in the Date of summary search condition, you must first perform totaling from the Totals List & Execution window. For details about performing totaling, see 14.4.10(1) Performing totaling.

How to interpret the totaled results

A hyphen (-) in the License category column identifies software whose license information has not been registered or whose license type is Other.

A hyphen (-) in the Owned and Available columns identifies an unlimited license owned by the local group.

This also applies to freeware that is owned by the local group.

If a single software asset name corresponds to multiple installed software names, its usage count is 1.

For example, installed software names AA and AB both correspond to software named A. If software AA and AB are both installed on a computer, the usage count for software A is 1.

The number of license keys assigned is displayed under Assigned. However, Assigned is set to be hidden by default. To show Assigned, you must edit the search results list of Owned License List in the Customize Job Windows job menu. For details about configuring items for display in the search results list, see 11.3.6 Setting the items to be displayed in search results.

(1) Displaying a breakdown by group

In the Owned License List window, clicking a link under Software name in the totaled results displays the total numbers of owned, assigned, used, and available licenses by group, including subgroups. The following figure shows the window that displays a breakdown by group.

Figure 14‒25: Window displaying a breakdown by group (Owned License List)

For software whose license information has not been registered or whose license category is Other, the numbers of owned and used licenses are totaled. The value displayed under Used indicates the number of software assets installed on the computers in the group that own the licenses.

Assigned displays the number of assigned devices when the license category is Install license and the number of assigned users when the license category is User license.

Parentheses enclose the number of licenses assigned to other groups.

In Used and Total used, parentheses enclose the number of downgrade software assets that are installed.

(2) Displaying a list of devices on which software is installed

In the window that displays a breakdown by group, clicking a link under Group name displays a list of that group's devices on which the corresponding software is installed. The following figure shows the window that displays the devices on which corresponding software is installed.

Figure 14‒26: Window displaying the devices on which software is installed (Owned License List)

This window displays the information that was in effect when the licenses were totaled. Therefore, the information displayed in the selected list might not match the information displayed in the Device Details dialog box or the applicable device might have been deleted.

14.4.2 Checking for exceeded licenses (Excess License List)

By using the Excess License List job menu, you can check for software whose number of installed copies has exceeded a preset threshold.

To search for software whose number of installed copies exceeds a specified threshold, start from the Excess License List window, which is displayed by clicking the Excess License List job menu. The following figure shows the Excess License List window.

Figure 14‒27: Excess License List window

In the Excess License List window, the job searches for software assets that are regarded as being active and within their valid usage period.

A hyphen (-) in the License category column indicates software whose license information has not been registered or whose license type is Other.

If nothing is displayed for the Date of summary search condition

Excess License List searches for software on the basis of existing totaled results. If no date of summary is displayed in the Date of summary search condition, you must first perform totaling from the Totals List & Execution window. For details about performing totaling, see 14.4.10(1) Performing totaling.

Sending email notification of exceeded licenses

If you are using the Notice of license excess task registered in Windows Task Scheduler for totaling license usage statuses, you can send email notification of software that remains installed beyond its period of validity. For details about settings for the task that monitors for expired licenses, see 7.9 Setting the tasks that are registered in Task Scheduler.

(1) Displaying a breakdown by group

In the Excess License List window, clicking a link under Software name in the totaled results displays the numbers of owned, assigned, used, and available licenses by group for that license category as well as cumulative totals that include subgroups. The following figure shows the window that displays a breakdown for a group.

Figure 14‒28: Window displaying a breakdown by group (Excess License List)

Assigned displays the number of devices assigned when the license category is Install license and the number of users assigned when the license category is User license.

Parentheses enclose the number of licenses assigned to other groups.

In Used and Total used, parentheses enclose the number of downgrade software assets that are installed.

(2) Displaying a list of devices on which software is installed

In the Excess License List window or the window displaying a breakdown by group, clicking a link under Group name displays a list of the devices on which the corresponding software is installed. The following figure shows the window that displays the devices on which corresponding software is installed.

Figure 14‒29: Window displaying the devices on which software is installed (Excess License List)

If a device has been assigned a license, the icon is displayed in the Asset No. column. Similarly, the icon is displayed if a license has been assigned to the user of a device.

This window displays the information that was in effect when the licenses were totaled. Therefore, the information displayed in the selected list might not match the information displayed in the Device Details dialog box or the applicable device might have been deleted.

(3) Assigning licenses to devices or users

Assign licenses from the available licenses to the devices or users retrieved as exceeded licenses.

To assign licenses from the Excess License List - by Used dialog box:

From the Excess License List - by Used dialog box, select the check boxes of the devices to which a license is to be assigned (or the devices being used by users to whom a license is to be assigned).

Do not select devices to which a license is already assigned (or devices being used by a user to whom a license is assigned).

Click the Assign button.

The Unassigned License List dialog box is displayed.

If necessary, specify search conditions, and click the Search button.

Software assets that match the search conditions and have available licenses are displayed. Only software assets whose status is active become search targets.

Select the check box of the software to be assigned, and click the OK button.

The Assigned Target List dialog box is displayed.

Check the devices and software to be assigned, and click the Execute button.

The assignment results are displayed in the Assigned Target List dialog box.

For a user license, the number of assigned licenses becomes 1 if the selected devices contain devices being used by the same users.

If key information has not been registered to the software to be assigned, the software is assigned with Product ID, License key, and Serial No. still blank.

Click the Close button.

The Assigned Target List dialog box and the Unassigned License List dialog box close.

The following figure shows the flow of displaying the Assigned Target List dialog box from the Unassigned License List dialog box and assigning licenses.

Figure 14‒30: Flow of assigning licenses to devices with exceeded licenses (or users who use those devices)

(4) Canceling a license assignment

To cancel a license assignment:

At the Excess License List - by Used dialog box, select the check boxes of the devices for which the license is to be canceled (or the devices being used by users for whom the license is to be canceled).

Click the Cancel button.

When the confirmation dialog box is displayed, click the OK button. The licenses assigned to the selected devices (or users) are canceled.

14.4.3 Checking for expired licenses (Unauthorized Usage List)

By using the Unauthorized Usage List job menu, you can check for software whose license has expired and for software that is managed as an asset (software name is registered) but for which no license is held.

To check for unauthorized licenses, start from the Unauthorized Usage List window, which is displayed by clicking the Unauthorized Usage List job menu. The following figure shows the Unauthorized Usage List window.

Figure 14‒31: Unauthorized Usage List window

If nothing is displayed in the Date of summary search condition

Unauthorized Usage List searches for software on the basis of existing totaled results. If no date of summary is displayed in the Date of summary search condition, you must first perform totaling from the Totals List & Execution window. For details about performing totaling, see 14.4.10(1) Performing totaling.

When downgrade software is assigned

In the case of a software asset whose name is registered, but no license is owned, if a license is assigned as downgrade software, it is not counted as an unauthorized license.

(1) Displaying a breakdown by group

In the Unauthorized Usage List window, clicking a link under Software name in the totaled results displays the usage count for each group. The following figure shows the window that displays the breakdown by group.

Figure 14‒32: Window displaying a breakdown by group (Unauthorized Usage List)

(2) Displaying a list of devices on which software is installed

In the window displaying a breakdown by group, clicking a link under Group name displays a list of the devices on which the corresponding software is installed. The following figure shows the window that displays the devices on which corresponding software is installed.

Figure 14‒33: Window displaying the devices on which software is installed (Unauthorized Usage List)

This window displays the information that was in effect when the licenses were totaled. Therefore, the information displayed in the selected list might not match the information displayed in the Device Details dialog box, or the applicable device might have been deleted.

14.4.4 Checking the usage status of unregistered software (Unknown Usage List)

By using the Unknown Usage List job menu, you can check the usage status of software items that are not being managed as assets (software items whose software names have not been registered).

You can total the number of software assets that are being used and whose names have not been registered, such as freeware that does not require license management.

To check the usage status of unregistered software, start from the Unknown Usage List window, which is displayed by clicking the Unknown Usage List job menu. The following figure shows the Unknown Usage List window.

Figure 14‒34: Unknown Usage List window

Unknown Usage List searches for software on the basis of existing totaled results. If no date of summary is displayed in the Date of summary search condition, you must first perform totaling from the Totals List & Execution window. For details about performing totaling, see 14.4.10(1) Performing totaling.

Installed software name displays the file name, size, and date, if registered, as well as the name of the installed software and its version.

(1) Displaying a breakdown by group

In the Unknown Usage List window, clicking a link under Installed software name in the totaled results displays the usage count by group. The following figure shows the window that displays a breakdown by group.

Figure 14‒35: Window that displays a breakdown by group (Unused License List)

(2) Displaying a list of devices on which software is installed

In the window that displays a breakdown by group, clicking a link under Group name displays a list of that group's devices on which the corresponding software is installed. The following figure shows the window that displays the devices on which corresponding software is installed.

Figure 14‒36: Window displaying the devices on which software is installed (Unknown Usage List)

This window displays the information that was in effect when the licenses were totaled. Therefore, the information displayed in the selected list might not match the information displayed in the Device Details dialog box or the applicable device might have been deleted.

14.4.5 Adding a license (New Software)

By using the New Software job menu, you can register a newly purchased or additionally purchased license.

To register a license, start from the New Software window, which is displayed by clicking the New Software job menu. The following figure shows the New Software window.

Figure 14‒37: New Software window

To register a license, specify a value for each item, and then click the OK button. Items identified by a star () are mandatory.

To specify Software name, Software type, and Developer, use the Software dialog box that is displayed by clicking the Browse button for Software name.

If Number of licenses shows Freeware as the Software type, do not specify anything.

Licenses and other data can be registered as attached files. For details about specifying attached files, see 13.4.4 How to specify an attached file.

To specify License name, License type, Licensing method, Upgrade assurance, Downgrade, License category, Description, and Notes, use the Licenses dialog box that is displayed by clicking the Browse button for License name.

In Use period, specify the expiration date of a trial version or the termination date of a lease contract.

(1) How to specify Software name

To specify Software name when registering a new license by, for example, registering a new software name and assigning an installed software name at the same time:

In the New Software window, click the Browse button for Software name.

The Software dialog box is displayed.

Specify the name of the software asset to be registered for the search condition, and then click the Search button.

If the applicable software name is found, select the Software name radio button, and then click the OK button.

The Installed software name field displays the installed software name that is assigned to a software name. If multiple installed software names are assigned, click the link to display a pop-up window that lets you view the installed software names that are assigned.

If the name of the software asset to be registered is not included in the search results, click the Add button.

The Add Software dialog box is displayed.

Specify each item, and then click the OK button.

Items identified by a star () are mandatory.

The software name is registered, and the Browse Software dialog box is displayed again.

Click the link of the registered software name.

The Software Name Details dialog box is displayed.

Click the Add button in the Assign tab.

The Add Installed Software dialog box is displayed.

Search for the installed software name that you want to assign.

Search for the installed software names that have not been assigned to other software names.

To cancel, click the Close button.

From the search results, select the installed software name to be assigned, and click the OK button.

The Add Installed Software dialog box closes, and the selected installed software name is added to the assigned installed software names.

Click the Close button.

The Software Name Details dialog box closes, and the Browse Software dialog box is displayed again.

Specify the registered software name, and click the OK button.

The Browse Software dialog box closes, and the New Software window is displayed again. The registered information is specified for Software name, Software type, and Developer.

The following figure shows the procedure for specifying Software name by registering a software name in the Add Software dialog box.

Figure 14‒38: Procedure for specifying a software name

(2) How to specify a license name

To specify License name when new license information is registered:

In the New Software window, click the Browse button for License name.

The License dialog box is displayed.

If the License dialog box contains the applicable license information, select the radio button for that License name, and then click the OK button.

Click the Add button.

The Add License dialog box is displayed.

Specify each item, and then click the OK button.

When specifying each item, note the following:

Items identified by a star () are mandatory.

Licenses are totaled by the value specified in License category. To manage license information, register the License type and Licensing method as supplementary information.

To set Downgrade to Enable, you must register the downgrade software name for the software name of the license to be registered. For details about how to register a downgrade software name, see 16.6.4 Changing a software name and attributes.

The license information is registered, and the License dialog box is displayed again.

Select the radio button for the registered license, and then click the OK button.

The New Software window is displayed again.

The registered information is specified in License name, License type, Licensing method, Upgrade assurance, Downgrade, License category, Description, and Notes.

The following figure shows the procedure for specifying License name by registering license information in the Add License dialog box.

Figure 14‒39: Procedure for specifying a license name

To clear specified license information

To clear license information that has been specified, click the Browse button again, and in the displayed License dialog box, click the Clear Settings button.

To change registered license information

To change registered license information, use the License tab of the Software Name Details dialog box. For details about changing license information, see 16.6.8 Changing license information.

(3) Notes on upgrading

To register an upgrade version of existing software that has already been registered in the asset management database, you must take into account the correspondence between the software name to be registered and the installed software name.

For example, in the case of a free upgrade, purchase information is not retained even when the version changes. After you install the upgraded license, you must decide whether the new or the old software name is to be used to manage its license. If you use the new software name after upgrading, be sure to change the old software name to the new software name in the Software Name Details dialog box, and then add the new installed software name to that name.

14.4.6 Searching for software (Software List)

By using the Software List job menu, you can search for the owned software assets for a specified software asset. For example, you can search for software assets for reasons such as to determine whether a software asset to be used has been registered or to determine the managerial group for software A.

This job can also be used to assign a retrieved software license to devices and users.

To search for a software asset and assign licenses for it, start from the Software List window, which is displayed by clicking the Software List job menu. The following figure shows the Software List window.

Figure 14‒40: Software List window

The Software List window displays the search results for each group that owns the license.

(1) Changing software information

To change software information, click the link of the Asset No. in the search results list and display the Software Details dialog box.

The Asset tab displays information about the software name and licenses.

Figure 14‒41: Software Details dialog box (Asset tab)

You can change the information for a software asset by editing the various items for the software, and then clicking the Update button. When editing the information, items identified with a star () are mandatory. To cancel, click the Close button.

This dialog box does not allow you to change License name for a software asset that has been assigned a license. In addition, you cannot change License name for a transferred software asset.

You can specify all license information in a batch operation by using the Browse button for License name. To assign licenses, you must register the license information in advance. For details about registering licenses, see 14.4.5(2) How to specify a license name.

Changing the number of owned instances of software by changing the software type to Freeware

If you change the software type to Freeware after it has been registered as Commercial or Shareware, the license is not automatically changed to an unlimited license. Therefore, after you delete (from the number of owned and registered software items) software whose software type was changed to Freeware, select the Unlimited license check box in order to change the license to an unlimited license.

(2) Assigning licenses

To accurately manage the installation destination of each owned license, correspondence is established between a device and the information used to identify the license (key information), such as the product ID and serial number. This task is not necessary if you do not manage the license assignment targets.

Licenses are allocated from the Key tab of the Software Details dialog box.

Figure 14‒42: Software Details dialog box (Key tab)

License category, Number of licenses, and Number assigned display the license information set in the Asset tab. A license key is assigned according to this information.

The list also displays the registered key information. The items for which Asset No. or User ID is displayed have already been assigned. Clicking a link under Asset No. displays the Device Details dialog box that enables you to view the details about the assigned device.

Because license assignment can be registered according to the license category, you must have already registered the License category in the Asset tab of the Software Details dialog box.

(a) Adding a key information

To add a license key for the purpose of assigning licenses:

In the Key tab of the Software Details dialog box, click the Add button.

The Add License Key dialog box is displayed.

Specify each key information item.

In Number of licenses, specify the number of licenses for which key information is to be created at the same time.

Click the OK button.

The Add License Key dialog box closes, and the Software Details dialog box displays the registered key information.

The following figure shows the Add License Key dialog box for specifying registration information.

Figure 14‒43: Add License Key dialog box

(b) Assigning a target

To assign an added license key to a license target:

Select the check box of the added license key in the Key tab of the Software Details dialog box.

To assign one at a time, click the Assign button.

The Target Specification dialog box is displayed.

To cancel, click the Cancel button.

Figure 14‒44: Target Specification dialog box

Specify Asset No. or User ID, and then click the OK button. The Target Specification dialog box closes and the license key is assigned.

To assign multiple devices in a batch operation, click the Auto button.

The Search Assignments dialog box is displayed.

Specify the desired search conditions, and then click the Search button.

The applicable devices are searched for.

Select the check box for the device to which the license is to be assigned, and then click the OK button.

The Search Assignments dialog box closes, and the key information is assigned to the selected device or user.

The following figure shows the Search Assignments dialog box after searching for the target device.

Figure 14‒45: Search Assignments dialog box

You cannot change or delete license information after it has been assigned to a usage target. To change or delete such license information, you must cancel the entire assignment of the license.

(3) Changing a license assignment

The following paragraphs describe how to change the license key and assignment target that were registered when a license was assigned.

(a) Changing the key information

To change the registered key information, in the Software Details dialog box, in the Key tab, click the Product ID link of the key information to be changed.

In the displayed License Key Details dialog box, change applicable items and then click the Update button.

(b) Changing the target

To change a license assignment:

In the Software Details dialog box, in the Key tab, select the check box for the item to be changed, and then click the Cancel button.

In order to change an assignment, you must first cancel the existing assignment.

Select the check box for the item to be changed, and then click the Assign button.

The target specification dialog box is displayed.

To cancel, click the Cancel button.

Specify the target asset number or user ID, and then click the OK button.

The target specification dialog box closes, and the assignment target is changed.

(4) Deleting software information

To delete software information, in the search results list, select the check box for the software asset to be deleted, and then click the Delete button.

(5) Downloading search results

You can download the search results list as a CSV file. To do this, select the check box for the desired software, and then click the CSV button. The search results are downloaded as a CSV file.

The information that is downloaded includes Asset No., Software name, Software type, Number of licenses, Group name, Reg. date, Start date of use, End date of use, Status, License name, License type, Licensing method, and License category.

14.4.7 Changing the managerial group of a license (Transfer License)

By using the Transfer License job menu, you can change the managerial group of a license.

To change the managerial group of a license, start from the Transfer License window, which is displayed by clicking the Transfer License job menu. The following figure shows the Transfer License window.

Figure 14‒46: Transfer License window

(1) Transferring a software asset together with its license key

To change the managerial group of a license:

Search for the software asset whose managerial group is to be changed.

In the search results list, select the check box for the software asset whose managerial group is to be changed.

In Number of objects, specify the number of licenses to be changed.

Click the Transfer button.

The Set Destination dialog box is displayed.

To cancel, click the Close button.

In the Destination Group tab, specify the target group.

In the Transfer Key tab, select the check box for the key information to be transferred.

If you do not manage license assignment, skip this step.

In the Destination Group tab, click the OK button.

The Set Destination dialog box closes, and the specified number of licenses are transferred.

The purchase price and points are managed for each software asset (they are not divided or consolidated depending on the number of licenses). Therefore, the target group inherits the purchase price and points of the software asset as is.

Figure 14‒47: Procedure for transferring a software asset together with its license key

(2) Transferring freeware and unlimited license software

When you transfer freeware and unlimited license software, you specify whether the transfer source information is to be deleted from the Set Destination dialog box.

To delete, select the Delete freeware or unlimited license check box, and then click the OK button.

When you transfer with this setting, the number of licenses in the software asset information of the transfer source becomes 0. If the software asset information of the transfer source is not needed, delete it from the Software List window.

If software already exists in the transfer destination group with the same asset number, then if either the transfer source or the transfer destination is an unlimited license, the license is unlimited after the transfer.

14.4.8 Registering volume contract information (New Volume License)

By using the New Volume License job menu, you can register contract information for a volume license. By registering the volume license information, you can manage points-based licenses.

Registration of a volume license does not accompany registration of information about the software subject to the contract. After the contract is signed, you must add the applicable software using the Volume License List job menu.

To register volume license information, start from the New Volume License window, which is displayed by clicking the New Volume License job menu. The following figure shows the New Volume License window.

Figure 14‒48: New Volume License window

Specify each item, and then click the OK button. Make sure that Contract No. is specified.

14.4.9 Changing volume contract information (Volume License List)

By using the Volume License List job menu, you can check the status of purchase points for volume licenses and change registered information. You also use this job to add software assets to newly registered volume licenses.

To change volume license information, start from the Volume License List window, which is displayed by clicking the Volume License List job menu. The following figure shows the Volume License List window.

Figure 14‒49: Volume License List window

(1) Viewing and changing contract information

In a search results list, clicking a link under Contract No. displays the Volume License Details dialog box, as shown below, which you use to change volume contract information.

Figure 14‒50: Volume License Details dialog box

You update volume contract information by editing the existing volume contract information and then clicking the Update button. To cancel, click the Close button.

(2) Adding target software

To add target software to a contract:

Search for the contract whose target software is to be added.

You cannot add a target to a contract that is in the expire or erase status.

In a search results list, click the applicable Contract No. link.

The Volume License Details dialog box is displayed.

In the Software tab, click the Add button.

The Search Software dialog box is displayed.

Specify conditions as necessary, and then click the Search button.

The software assets satisfying the conditions are retrieved.

To cancel, click the Close button.

From the search results, select a software asset, and then click the OK button.

The selected software asset is added as a contract target.

The following figure shows the procedure for opening the Search Software dialog box from the Software tab and then adding a target software.

Figure 14‒51: Procedure for adding a target software to a volume contract

(3) Changing target software

To change the target software of a contract:

Search for the contract whose target software is to be changed.

You cannot change the target software of a contract that is in the expire or erase status.

From the search results list, click the Asset No. link.

The Volume License Details dialog box is displayed.

Click the Software tab.

To cancel, click the Close button instead of the Cancel button.

Select the check box of the software to be canceled, and click the Cancel button.

Click the Close button

The Volume License Details dialog box closes, and the license of the contract software is changed.

14.4.10 Totaling licenses (Totals List & Execution)

By using the Totals List & Execution job menu, you can perform totaling, so that the information can be used for all license management work.

The license management jobs that extract required information on the basis of a set of totaled results include Owned License List, Excess License List, Unauthorized Usage List, and Unknown Usage List.

By default, only the administrator can execute Totals List & Execution.

To total licenses, start from the Totals List & Execution window, which is displayed by clicking the Totals List & Execution job menu. The following figure shows the Totals List & Execution window.

Figure 14‒52: Totals List & Execution window

You can also total licenses periodically by using the Notice of license excess task or the Totals number of licenses task registered in the Windows Task Scheduler.

Date of summary displays a history of totaling including totaling executed by tasks. To refresh the displayed information to the most recent status, click the Refresh button.

For details about using a task registered in Windows Task Scheduler to periodically perform totaling, see 7.9 Setting the tasks that are registered in Task Scheduler.

Note

If totaling is performed multiple times in a large system with several thousand devices, a large amount of old totaled results data might remain in the database, increasing the time required to search for, add, or delete information, reducing the performance of totaling.

If you have a large asset management system with several thousand devices, you should delete old totaled results periodically.

(1) Performing totaling

To perform totaling, click the Execute button. A history of execution dates and times is displayed in Date of summary.

To sum up the number of licenses, you must have registered information about the software assets installed on each device in the asset management database and you must have established correspondence between software names.

For details about how to register installed software information, see 5.2.4 Setting the software name assignment method. For details about establishing correspondence between software names, see 16.6 Establishing correspondence between software names (Software Name).

(2) Deleting totaled results

To delete a set of totaled results, select the check box of the totaled results in the Totals List & Execution window, and then click the Delete button.

14.4.11 Managing the installed software update history (Update History)

By using the Update History job menu, you can manage the update history for software installed on devices.

The software change log is collected when JP1/IT Desktop Management 2 - Manager's management information is registered.

Even when the contents collected from the JP1/IT Desktop Management 2 - Manager's management information are changed via window operations, the information remains in the change log. However, installed software information added in a window operation is not collected into the change log if it is deleted before the JP1/IT Desktop Management 2 - Manager's management information is assigned.

You manage the software change log by clicking the Update History job menu to display the Update History window. The following figure shows the Update History window.

Figure 14‒53: Update History window

If you click an Asset No. link in the change log search results list, the Device Details dialog box is displayed, enabling you to browse the associated software details.

(1) Collecting the change log at specified times

In the Update History window, specify, as a search condition, a period for which to acquire the update history for the installed software. By performing the search, you can determine the software programs that were installed on the device during the specified period. This is also helpful for checking the devices on which specific software is installed.

When you want to know the time that software was installed on a device or the change log associated with the software for each device, select the group that you are managing, specify in Update date the start date and end date of the log that you desire, and perform the search.

If the start date is omitted and only the end date is specified, the log is collected from the earliest date that JP1/IT Desktop Management 2 - Manager's management information was collected, until the specified end date.

If the end date is omitted and only the start date is specified, the log is collected from the specified start date until the most recent log date.

(2) Information collected in the change log

The information collected in the change log is software information that can be acquired from the ITDM2 management information acquisition job menu.

A log is also collected whenever any of the following items is edited from an Asset Console window operation:

File date

File name

File size

Installed software name

Version

A change log is not collected for managed items added to user properties.

14.5 Software usage management

This section describes how to execute asset management jobs related to software usage.

Software usage management enables you to make sure that unauthorized software is not installed.

Jobs related to software usage management are displayed under the Software Usage Management job category.

This section describes the operations available from the menu and shows the windows. Each subsection title shows the selected menu name in parentheses.

14.5.1 Checking for unauthorized software installations (Unauthorized Install List)

By using the Unauthorized Install List job menu, you can check for installation of unauthorized software assets.

To set the permission to install registered software assets, use the Installed Software window. To register the name of newly installed software from JP1/IT Desktop Management 2 - Manager's management information, use the ITDM2 management information acquisition job menu.

For details about the setup method in the Installed Software window, see 16.7 Changing information about installed software (Installed Software).

To determine whether the installation of software is permitted, check the Unauthorized Install List window that is displayed by clicking the Unauthorized Install List job menu. The following figure shows the Unauthorized Install List window.

Figure 14‒54: Unauthorized Install List window

(1) Displaying a breakdown by group

In totaled results, clicking a link under Installed software name displays the number of devices on which that software asset has been installed for each group.

The following figure shows the window that displays a breakdown by group of the number of devices on which a software asset has been installed.

Figure 14‒55: Window displaying a breakdown by group (Unauthorized Install List)

(2) Displaying a list of devices on which software is installed

In the window that displays a breakdown by group, clicking a link under Group name displays a list of devices on which the corresponding software has been installed. The following figure shows the window that displays the devices on which the software asset has been installed.

Figure 14‒56: Window displaying the devices on which a software asset has been installed (Unauthorized Install List)

(3) Downloading the search results

You can download the search results list as a CSV file. To do this, select the check box for the desired software, and then click the CSV button. The search results are downloaded as a CSV file.

The information that is downloaded to a CSV file includes Installed software name, Install software version, File name, File size, File date, Group name, Asset No., and User name.

14.6 Managing device details

This section explains how to manage details about a device. The details about a device are displayed in the Device Details dialog box from the search or totaled results obtained from each job.

The Device Details dialog box is used to view and edit various types of device-related information. The following information can be viewed in the tabs of the Device Details dialog box:

Asset and hardware information (Device tab)

Network information (Network tab)

Installed software information (Software tab)

Patch information (Patch tab)

Virus definition information (Anti-Virus tab)

Related asset information (Related devices tab)

License information (License tab)

Contract information (Contract tab)

Maintenance log (Maintenance tab)

Transfer log, change log, software change log (Update Records tab)

Tip

You can specify attached files in the Device Details dialog box. Because attached files are hidden by default, perform the following procedure to change the display setting:

Select the job menu item System Definition, Customize Managed Items, and then click the anchor for VariousInfo under class.

Under managed class in the displayed dialog box, click ValueText.

Under properties in the displayed dialog box, select the check box for the display of HardwareInfo_AttachFile, and then click the Update button.

14.6.1 Viewing and changing device details (Device tab)

In the Device tab in the Device Details dialog box, you can view and edit asset information, such as Asset No., User name, and Location, and hardware information, such as Processor and Memory. The following figure shows the Device tab in the Device Details dialog box.

Figure 14‒57: Device tab in the Device Details dialog box

(1) Enabling operation management

You can specify whether the operation status of the device is to be managed. When operation management is enabled for a device, the device becomes subject to search operations from the Unused Device List job menu.

To enable operation management of a device, set Usage management to Used.

(2) Changing the group and location

You can change the group using the device and change the location where the device is being used. Values that are changed in the Device Details dialog box are not overwritten, even if they differ from the management information acquired from JP1/IT Desktop Management 2 - Manager.

However, you can use the Data maintenance task if you want the Device Details dialog box group and location settings to be overwritten with the group-specific and location-specific IP group values created by the IP Group job menu. For details about selecting the contents executed by the Data maintenance task, see 7.9.3(3) Changing the tasks to be executed.

(3) Changing the device status

You can change the status of a device.

If you change a device's status to Restore, Scrap, or Pre-Scrap, the device's IP address and installed software information are all deleted when the next time the Data maintenance task registered in Windows Task Scheduler is executed. The assigned license key is also released.

This also applies to devices whose status is similarly updated from windows.

By default, you can select from the statuses Stock, Active, Restore, Scrap, Pre-Scrap, and Erase. To change the name of a status or the device statuses that can be selected, see 16.8 Adding and changing types and statuses (Code).

14.6.2 Viewing and changing network information (Network tab)

In the Network tab in the Device Details dialog box, you can view and edit network information related to IP address. The following figure shows the Network tab in the Device Details dialog box.

Figure 14‒58: Network tab in the Device Details dialog box

(1) Adding an IP address

To add an IP address:

Click the Add button.

The Add Network dialog box is displayed.

If you do not need to search for unused IP addresses, go to step 7.

To cancel, click the Close button.

To search for unused IP addresses, click the Browse button.

The Unused IP Address List dialog box is displayed.

Select the tab for the IP group to be specified.

Specify a search condition, if necessary, and then click the Search button.

The IP groups are retrieved.

Select the radio button for the desired IP group name, and then click the OK button.

The Unused IP Address dialog box is displayed.

To cancel, click the Close button.

Select the radio button for the desired Unused IP address, and then click the OK button.

The IP address is specified.

In the Add Network dialog box, click the OK button.

The specified IP address value is added.

If you specify both DHCP server name and IP address, the specified IP address is registered, but it is not treated as being in use; instead, it is treated as still being unused.

(2) Editing network information

In the Network Details dialog box, which is displayed by clicking a link under IP address, you can view and edit the information shown below for the IP address. The following figure shows the Network Details dialog box.

Figure 14‒59: Network Details dialog box

Editing the network information and then clicking the Update button updates the network information based on the specified information. Selecting the check box for an IP address and then clicking the Delete button deletes the network information. To cancel, click the Close button.

Deleting network information based on JP1/IT Desktop Management 2 - Manager's management information

You can use ITDM2 management information acquisition control setting to specify whether network information is to be deleted on the basis of JP1/IT Desktop Management 2 - Manager's management information. To handle a device for which no management information is collected by JP1/IT Desktop Management 2 - Manager as having been deleted from the network, select Delete when there is no corresponding information in the ITDM2 management information.

If the device information has been registered by a window operation, such as the case with UNIX computers and devices that are not connected to the network, you must select Do not delete when there is no corresponding information in the ITDM2 management information. The default is Do not delete when there is no corresponding information in the ITDM2 management information.

14.6.3 Viewing and changing installed software assets (Software tab)

In the Software tab in the Device Details dialog box, you can view and edit information about software assets that have been installed on a device. The following figure shows the Software tab in the Device Details dialog box.

Figure 14‒60: Software tab in the Device Details dialog box

Installed software name displays an installed software item's name and version. If a file name has been registered, the file name, file size, and file date are also displayed.

Deleting information based on JP1/IT Desktop Management 2 - Manager's management information

You can use ITDM2 management information acquisition control setting to specify whether information about installed software assets is to be deleted on the basis of JP1/IT Desktop Management 2 - Manager's management information. To handle a software asset for which no inventory information is collected by JP1/IT Desktop Management 2 - Manager as having been uninstalled from the device, select Delete when there is no corresponding information in the ITDM2 management information.

(1) Editing installed software information

Clicking the Installed software name link displays the Installed Software Details dialog box. In this dialog box, you can change the product ID, installation date, and ITDM2 management information acquisition control setting for installed software.

The following figure shows the Installed Software Details dialog box.

Figure 14‒61: Installed Software Details dialog box

You can change the installed software information by editing each item and then clicking the Update button. You can delete installed software information by clicking the Delete button. To cancel, click the Close button.

(2) Adding installed software assets

You can register software assets that have been installed on UNIX computers and other devices that are not connected to the network.

To add an installed software asset:

Click the Add button.

The Add Installed Software dialog box is displayed.

Click the Browse button for Installed software name.

The Installed Software dialog box is displayed.

Specify a search condition, if necessary, and then click the Search button.

The names of the installed software assets satisfying the specified condition are retrieved.

Select the radio button for the desired Installed software name and then click the OK button.

The Installed Software dialog box closes, and the specified installed software information is added to the Add Installed Software dialog box.

Click the OK button.

The specified information is registered.

The following figure shows the procedure for adding an installed software asset from the Add Installed Software dialog box.

Figure 14‒62: Procedure for assigning an installed software asset

(3) Deleting an installed software asset

To delete an installed software asset, select its check box and then click the Delete button.

14.6.4 Browsing and adding patch information (Patch tab)

In the Patch tab in the Device Details dialog box, you can browse and add patch information for a device.

The following figure shows the Patch tab in the Device Details dialog box.

Figure 14‒63: Patch tab in the Device Details dialog box

(1) Browsing patch information

To browse patch information:

Select the information that you wish to browse from the drop-down list.

Select Apply, Unapplied, or both (no selection). To browse both Apply and

Unapplied patch information, make no selection.

Click the Show button.

The information about the specified patches is displayed.

(2) Adding patch information

To add an applied patch:

Click the Add button.

The Add Patch dialog box is displayed.

Click the Browse button for the patch name.

The Browse Patch dialog box is displayed.

Specify search conditions as necessary, and click the Search button.

The patch names that match the conditions are searched for.

If you want to add new patch information, click the Add button and add the patch name and version from the displayed Add New Patch dialog box. When you click the Add button, the patch information is registered.

Select the radio button for the patch name to be registered, and click the OK button.

The Browse Patch dialog box closes, and the specified patch information is added to the Add Patch dialog box.

Click the OK button.

The specified information is registered.

The following figure shows the flow of adding a patch from the Add Patch dialog box.

Figure 14‒64: Flow of adding an applied patch

14.6.5 Browsing and adding anti-virus software (Anti-Virus tab)

In the Anti-Virus tab of the Device Details dialog box, you can browse and add virus definition information installed on a device.

The following figure shows the Anti-Virus tab of the Device Details dialog box.

Figure 14‒65: Anti-Virus tab in the Device Details dialog box

(1) Browsing virus definition information

To browse virus definition information:

Select the information that you wish to browse from the drop-down list.

The anti-virus product names and anti-virus product versions are displayed in a drop-down list. Select the information that you wish to display.

Click the Show button.

The virus definition information for the selected information is displayed.

(2) Adding virus definition information

You can add information about the installed anti-virus software product.

To add virus definition information:

Click the Add button.

The Add Anti-Virus Products dialog box is displayed.

Click the Browse button for the anti-virus product name.

The Browse Anti-Virus Products dialog box is displayed.

Specify conditions as necessary, and click the Search button.

Anti-virus product names that match the conditions are searched for.

Select the radio button for the anti-virus product name.

To register a virus definition version, click the Anti-virus product name link, and on the Browse Virus Definition Version dialog box that is displayed, select the radio button for the anti-virus definition version that you wish to register.

Click the OK button.

The Browse Virus Definition Version dialog box closes, and the specified virus definition version information is added to the Add Anti-Virus Products dialog box.

Click the OK button.

The specified contents are registered.

The following figure shows the flow of adding anti-virus software from the Add Anti-Virus Products dialog box.

Figure 14‒66: Flow of adding installed anti-virus software

14.6.6 Viewing or changing related asset information (Related devices tab)

You use the Related devices tab in the Device Details dialog box to view or edit the association of parent-child relationships among devices.

The following figure shows the Related devices tab in the Device Details dialog box.

Figure 14‒67: Related Devices tab in the Device Details dialog box

(1) Associating devices

To associate devices using parent-child relationships:

Click the Add related device button.

The Add Related Device dialog box is displayed.

Specify search conditions as necessary and click the Search button.

A search is conducted for devices that satisfy the specified search conditions and do not already have an association with the device that will become the parent device.

Select the check box of the device that you want to associate with the device that will become the parent device, and click the OK button.

The selected device is associated as a child asset of the device that has become the parent device, and the Add Related Device dialog box is closed.

The following figure shows the Add Related Device dialog box after a search has been performed for a device that matches the search conditions

Figure 14‒68: Add Related Device dialog box

(2) Releasing device associations

To release a device association, select the check box of the device from which you wish to remove the association, and click the Release button.

14.6.7 Browsing and changing assigned license information (License tab)

In the License tab in the Device Details dialog box, you can view and edit information about the licenses assigned to a device. The following figure shows the License tab in the Device Details dialog box.

Figure 14‒69: License tab in the Device Details dialog box

Software name displays the names of the software assets to which licenses have been assigned. Installed software name displays the names of the software assets that have been installed using the assigned licenses.

If the Installed software name column is blank, the licensed software asset has not been installed.

Clicking a link under Asset No. displays the Software Details dialog box, in which you can change the software information.

(1) Assigning a license to a device

To assign an Install license to the device for which the Device Details dialog box is displayed:

Click the Assign button.

The Assign License dialog box is displayed.

Specify a search condition, if necessary, and then click the Search button.

Available Install licenses that satisfy the specified condition are retrieved.

Select the check box for the desired license, and then click the OK button.

The Assign License dialog box closes, and the specified license is assigned.

The following figure shows the Assign License dialog box that displays the software assets for which licenses can be assigned.

Figure 14‒70: Assign License dialog box

(2) Releasing a license assignment

To release an assigned license, select its check box, and then click the Cancel button.

14.6.8 Viewing and changing contract information (Contract tab)

In the Contract tab in the Device Details dialog box, you can view details about maintenance, lease, and rental contracts, and register them. The following figure shows the Contract tab in the Device Details dialog box.

Figure 14‒71: Contract tab in the Device Details dialog box

Note

The Contract tab displays the latest contract information that targets that device.

(1) Adding a contract

To add a contract:

Click the Add button.

The Assign Contract dialog box is displayed.

Specify a search condition, if necessary, and then click the Search button.

Contract information is searched for. To view details about a contract, click its Contract No.

To cancel, click the Close button.

Select the radio button for the desired Contract No., and then click the OK button.

The selected contract is added.

Click the Close button.

The Assign Contract dialog box closes.

The following figure shows the Assign Contract dialog box that displays the contracts that can be registered.

Figure 14‒72: Assign Contract dialog box

(2) Canceling a contract

To cancel a contract, select the check box for the contract that you wish to cancel, and click the Cancel button.

14.6.9 Viewing and changing the maintenance log (Maintenance tab)

In the Maintenance tab in the Device Details dialog box, you can view and change information about the errors that occurred in the past and how they were handled. The following figure shows the Maintenance tab in the Device Details dialog box.

Figure 14‒73: Maintenance tab in the Device Details dialog box

Clicking a link under Reg. date displays details about that portion of the maintenance log.

(1) Registering completion of maintenance

This section describes the procedure for registering information about an action and completion of maintenance. In the case of a JP1 event or an SNMP trap, action completion can also be reported to JP1/IM at the same time.

To register completion of maintenance:

Click the Reg. date link for the maintenance log information whose action information you wish to register.

The Maintenance Log Details dialog box is displayed.

Click the Edit button.

The Edit Maintenance Log dialog box is displayed.

In Overview of solution, specify appropriate information, and change Status to Complete.

Click the Update button.

The maintenance log is updated based on the specified information.

Click the Complete button.

Action completion is reported to JP1/IM, and the status of the corresponding JP1 event is set to Complete.

Click the Close button.

The Edit Maintenance Log dialog box closes.

The following figure shows the Edit Maintenance Log dialog box in which an overview of the solution is specified.

Figure 14‒74: Edit Maintenance Log dialog box

(2) Registering maintenance log information

To register maintenance log information:

Click the Add button.

The Add Maintenance Log dialog box is displayed.

Items identified by a star () are mandatory.

By default, Problem type displays only User Registered. In Status, specify the status after the error.

To cancel, click the Close button.

Click the OK button.

The specified maintenance log information is registered.

The following figure shows the Add Maintenance Log dialog box in which an overview of the problem is displayed.

Figure 14‒75: Add Maintenance Log dialog box

(3) Deleting maintenance logs

To delete maintenance logs, select the check box for the maintenance log that you wish to delete, and click the Delete button.

14.6.10 Browsing update history (Update Records tab)

In the Update Records tab in the Device Details dialog box, you can browse the transfer log, the device change log, and the change log for software installed on devices. The following figure shows the Update Records tab in the Device Details dialog box.

Figure 14‒76: Update Records tab in the Device Details dialog box

To browse the change log:

Select the information that you wish to browse from the drop-down list.

Select Transfer, Hardware, or Software.

Click the Show button.

The change log for the selected information is displayed.

15 Executing Asset Management Jobs That Use Items

This chapter describes how to execute asset management jobs using the Item job category. Each section title shows the selected menu in parentheses.

The FAQ section contains important information about creating and processing Items.

15.1 Creating Items (New Item)

This section explains how to create new Items and make an application.

New Items are created from the New Item window, which is displayed by clicking the New Item job menu. The following figure shows the New Item window.

Figure 15‒1: New Item window

The Items that can be used are displayed on the New Item window in different tabs according to Item category.

By default, the following sample Items are provided: Problem Report Form, Equipment Deployment Request Form, and Equipment Order Request Form. If an Item's status is changed to Exhibit, it is displayed in the Template tab and becomes available for use.

The following table describes the purposes of Items and their official authorities (users authorized to use each Item).

Table 15‒1: Purposes of using Items and official authorities

Item

Purpose

Official authority

Problem Report Form

Request resolution when a problem occurs with an asset.

Problem receiver

Problem solver

Equipment Deployment Request Form

Request deployment when equipment is to be newly deployed.

Approval user

Receiver user

Distribution user

Equipment Order Request Form

Issuance of a purchase order when the equipment required to fulfill a deployment request is not in stock.

Order user

Recipient

Operational efficiency is enhanced when Items such as these are used as templates that can be edited to define new Items. For details about how to edit the provided sample Items and define official authorities, see 12.7 Changing registered Items or 12.2 Defining authority for processing the Item (Official Authority).

If there are no exhibit Items and no Items that can be created under the official authority assigned to the logged-in user, There are no usable items is displayed in the New Item window.

15.1.1 Creating new Items

To create a new Item and send it to the next worker:

In the tab for the appropriate category in the New Item window, click the link to the type of Item that you wish to create.

The Item window is displayed.

Enter the required information for the Item.

Click the button to send the Item.

The Select Destination dialog box is displayed.

Click the User name link, and then specify a user who has the official authority to execute the next processing.

The default send destination user is the user who holds the appropriate official authority and who belongs to the same group (or a superior group) as the user who sends the Item.

To send to a user other than the displayed default user, specify the appropriate user.

Click the Edit Mail button.

The Edit of Notification Mail dialog box is displayed.

Edit the email subject line and body text to notify the recipient of the Item's arrival.

If you do not wish to send an email, select the Mail is not transmitted check box on the Select Destination dialog box, and then skip steps 5 and 6.

Click the Add button.

The Edit of Notification Mail dialog box closes and the edited email is registered.

Click the OK button.

The Select Destination dialog box and the Item window close, and the Item is sent to the user specified as the send destination.

The sent Item is displayed in the outbox.

If the setting for sending out a notification when an Item arrives is enabled, an email is sent to the destination user. If a substitute has been specified for the user who has been set to receive the Item and also an email notification has been set to be sent to that substitute in the Server Setup dialog box, then an email will also be sent to the substitute.

For details about specifying a substitute, see 15.2.2 Specifying a substitute. For details about setting a substitute to be notified by email about an Item, see 7.3.5 Setting Mail Notification Information.

Note that you must click the Save button to save an Item while it is being created. The saved Item appears in the Outbox. At this time, the Item status becomes Creating.

Notes

When an Item is sent, an email notification might be sent depending on whether an email address was registered in the user management information. If there is no registered email address for the user set as the email send destination, the email is not sent. If no email address has been registered for the Item handler (email sender), the email address specified for Sender's e-mail address in the Server Setup dialog box is used as the sender's email address.

If a substitute for an Item is to be notified by email, the email address of the user set as the Item's substitute must be registered as user information.

15.1.2 Example of creating a Problem Report Form

This subsection explains how to create Items, using as an example the Problem Report Form that is provided by Asset Console.

When you actually use a Problem Report Form, you will have to change the Item's status to Exhibit. For details about how to change the status of an Item, see 12.4.6 Definition example of Item window.

The following figure shows the processing flow and status transitions of a Problem Report Form.

Figure 15‒2: Processing flow and status transitions of a Problem Report Form

A Problem Report Form can be used to execute a series of operations when a problem occurs in an asset, from applying for, requesting, and implementing corrective measures, through confirming that the measures resolved the problem.

The subsections below describe how each worker operates the Item window. Each subsection title displays in parentheses the person or group responsible for that work.

(1) Application for problem resolution measures (applicant)

This is the person who is first contacted when a problem occurs and who applies for corrective measures. Fields marked with a star () are mandatory, and other fields are entered as necessary.

The following figure shows how to specify each field on the applicant's Problem Report Form.

Figure 15‒3: Problem Report Form at time of application (applicant)

Apply button

Applies for problem resolution on the basis of the specified contents. Once submitted, the Item is sent to the Inbox of the worker at the problem reception desk, and the Item's status becomes Applied.

Save button

Saves the specified contents without submitting the application. When saved, the Item appears in the applicant's Outbox, and the Item's status becomes Creating.

Close button

Cancels creation of the application.

(2) Receiving the problem (Problem Reception Desk)

This person checks the contents of the application submitted on the Problem Report Form and requests resolution measures. The fields that can be edited at this time are Problem number, Importance, Notes, and Reason for rejection. Fields marked with a star () are mandatory.

The following figure shows how to specify each field on the problem acceptance desk's Problem Report Form.

Figure 15‒4: Problem Report Form at time of request (Problem Reception Desk)

Request button

Checks the contents of the application and requests corrective measures for the problem. Once requested, the Item is sent to the Inbox of the problem solver, and the Item's status becomes Requested.

Reject button

Rejects the application. Once rejected, the Item is sent back to the Inbox of the applicant, and the Item's status becomes Creating. The reasons for rejection should be noted in Reason for rejection.

Close button

Closes the Item window.

(3) Problem resolution measures (Problem Resolution Desk)

Once the problem has been resolved, the applicant is notified of the resolution. The fields that can be edited at this time are Solver name, Solver group, Solved date, Expense, Overview of solution, Importance, and Notes. Fields marked with a star () are mandatory.

The following figure shows how to specify each field on the problem resolution group's Problem Report Form.

Figure 15‒5: Problem Report Form when resolution has been completed (Problem Resolution Desk)

Complete button

Reports resolution of the reported problem. Once resolution has been completed, the Item is sent to the Inbox of the applicant, and the Item's status becomes Resolved.

Close button

Closes the Item window.

(4) Confirming the resolution results (applicant)

Completion of application of the corrective measures should be confirmed. Once the applicant confirms that the corrective measures have been implemented successfully, the Item's processing is complete. The following figure shows the Problem Report Form used by the applicant for confirmation.

Figure 15‒6: Problem Report Form when confirming (applicant)

The applicant can check the contents of the Item but cannot edit any of the fields. If there is a problem with the corrective measures, a new Item must be created.

The applicant browses and confirms the contents of the Item.

Confirmation button

Confirms that the corrective measures have resolved the problem. Once confirmed, the Item's status becomes Confirmed.

Close button

Closes the Item window.

15.1.3 Example of using the provided sample Items

On the New Item job menu, the following sample Items are provided: Problem Report Form, Equipment Deployment Request Form, and Equipment Order Request Form. These Items can be used individually, but they can also be used in pairs, such as the Equipment Deployment Request Form and the Equipment Order Request Form. This subsection presents examples of using the provided sample forms for problem resolution and for equipment deployment.

(1) Resolving a problem

The following figure shows the flow of problem resolution using the provided sample Problem Report Form.

Figure 15‒7: Flow of resolving a problem

The following explains the Item operations for resolving a software problem.

(a) Problem Report Form

The Problem Report Form Item is used when a problem occurs with an asset. It executes processing to describe the problem, apply for and request resolution, resolve the problem, and confirm that the problem has been resolved.

The following are the operations performed by each of the workers involved with a Problem Report Form:

Applicant

When a problem occurs with an asset, the applicant notes the details of the problem, such as the date of occurrence and the nature of the problem, and creates a Problem Report Form. The applicant clicks the Apply button to submit the application.

Files can be attached to the Problem Report Form. The applicant can also save an Item while in the process of creating it.

Problem Reception Desk

The problem receiver checks the contents of the Problem Report Form application. If resolution is necessary, the problem receiver assigns a problem number and clicks the Request button to send the Item to the problem resolution desk. If rejection is appropriate, the problem receiver notes the reasons that corrective measures are not required and clicks the Reject button to return the Item to the applicant.

Problem Resolution Desk

A worker at the problem resolution desk receives the request, determines the corrective measures that will resolve the problem, notes those measures, and then clicks the Complete button to return the Item to the applicant.

Applicant

The applicant confirms that the problem was resolved by the corrective measures and clicks the Confirmation button to complete the Item.

For details about how to create a Problem Report Form, see 15.1.2 Example of creating a Problem Report Form.

(2) Ordering and deploying requested equipment

The following figure shows the flow of using the provided sample Equipment Deployment Request Form and Equipment Order Request Form Items to deploy equipment.

Figure 15‒8: Flow of equipment deployment

The following explains the Item operations for deploying equipment:

(a) Equipment Deployment Request Form

The Equipment Deployment Request Form Item is used to request deployment of new equipment. It executes the processing for application, request, distribution, and completion of deployment of equipment.

The following are the operations performed by each of the workers involved with an Equipment Deployment Request Form:

Applicant

When new equipment is to be deployed, the applicant notes the equipment type and name, model, specifications, and other details, and creates an Equipment Deployment Request Form. The applicant clicks the Apply button to apply for equipment deployment. The applicant can also save an Item while still in the process of creating it.

Approval user

The approver checks the submitted Equipment Deployment Request Form application, approves it, and clicks the Approve button to send the Item to the acceptance desk. If rejection is appropriate, the approver notes the reasons why the software is not required and clicks the Reject button to return the Item to the applicant.

Acceptance Desk

A worker at the acceptance desk checks whether the equipment requested in the Equipment Deployment Request Form is in stock. If the equipment is in stock, the worker reserves it and clicks the Request Distribution button to send the Item to the distribution management group.

If the equipment is not in stock, the worker clicks the Order button on the displayed Equipment Order Request Form Item window to initiate a purchase order for the equipment. When the equipment becomes available, the worker reserves it for deployment and clicks the Request Distribution button to send the Item to the distribution management group.

Distribution Management Group

A worker in the distribution management group notes the pertinent information about the distributed equipment, including the user, group, location, and other details, and clicks the Distribute button to send the Item to the applicant.

Applicant

The applicant confirms that the requested equipment has been deployed and clicks the Complete button to complete the Item.

(b) Equipment Order Request Form

The Equipment Order Request Form Item is used to apply for, issue a purchase order for, provide, and confirm installation of equipment.

The following are the operations performed by each of the workers involved with an Equipment Order Request Form:

Applicant

A worker at the acceptance desk receives the approved application for equipment deployment. If the equipment is not in stock, the worker notes the specifications and other details about the asset that is to be distributed, creates an Equipment Order Request Form, and then clicks the Apply button to request a purchase order for the equipment. This worker can also save the Item while it is being created.

Order Desk

A worker at the order desk checks the order request, determines whether it is covered by the budget, and if there are no problems clicks the Order button to submit a purchase order for the equipment. If there is a problem with placing the order, the worker notes the reason, such as no funds in the budget, and then clicks the Reject button to return the Item to the applicant.

Delivery Desk

A worker at the delivery desk checks that the ordered equipment has been delivered and creates and uploads a list of the received equipment. The worker then clicks the Delivery button to register the requested equipment and send the Item to the applicant. If the equipment cannot be obtained, the worker clicks the Reject button to return the Item to the applicant or to the order desk.

Applicant

The applicant confirms that the requested equipment was delivered and clicks the Complete button to complete the Item.

15.2 Processing received Items (Inbox)

This section explains how an Item is approved or rejected after it has been checked. This section also explains how to resend an Item that was rejected and returned.

By clicking on the Inbox job menu, a received Item can be processed in the Inbox window that is displayed, as shown in the following figure.

Figure 15‒9: Inbox window

The Inbox window displays a list of received Items. The list of Items contains all Items addressed to the logged-in user that have not yet been processed, in descending order of the received dates. Clicking a link under Item name displays the corresponding Item window.

If the user is a substitute for another user, check the Display substitute items as well check box and click Refresh to also display substituted Items. In the Server Setup dialog box, you can set the status of the Display substitute items as well check box that is displayed when the Inbox window is displayed. For details about how to configure this setting, see 7.3.4(16) Display substitute items by default.

The following Item icons are displayed in the window:

: Normal processing

This indicates a sent Item that is being processed normally.

: Rejection

This indicates a rejected Item.

15.2.1 Approving or rejecting Items

From the list of Items in the Inbox window, you can click the link under Item name that is associated with an Item to display the corresponding Item window, where you can approve or reject the Item.

(1) Approving Items

To approve an Item:

In the Item window, click the appropriate button to approve the Item.

The Select Destination dialog box is displayed.

To cancel, click the Cancel button.

Click the User name link, and then specify a user who has official authority to execute the next processing.

The default send destination user is the user who holds the appropriate official authority and who belongs to the same group (or a superior group) as the user who sends the Item.

To send to a user other than the displayed default user, specify the appropriate user.

Click the Edit Mail button.

The Edit of Notification Mail dialog box is displayed.

Edit the email subject line and body text to notify the recipient of the Item's arrival.

If you do not wish to send an email, select the Mail is not transmitted check box on the Select Destination dialog box, and then skip steps 3 and 4.

Click the Add button.

The Edit of Notification Mail dialog box closes and the edited email is registered.

Click the OK button.

The Select Destination dialog box and the Item window close, and the Item is sent to the user specified as the send destination.

If you specified to send email notification of the Item's arrival, an email is sent to the recipient.

To save the Item while you are creating it, click the Save button. The saved Item appears in the Outbox. At this time, the Item status becomes Creating.

Notes

When an Item is sent, an email notification might be sent depending on whether an email address was registered in the user management information. If there is no registered email address for the user set as the email send destination, the email is not sent. If no email address has been registered for the Item handler (email sender), the email address specified for Sender's e-mail address in the Server Setup dialog box is used as the sender's email address.

You can specify only the Item's applicant as the Item's subject. Even if you change this subject to something other than the applicant, the change is not displayed in the Subject column of the Inbox, Outbox, and Execution Item Management windows. Note that, to display the Subject column in the Inbox, Outbox, and Execution Item Management windows, you must change a setting using the Customize Managed Items window. For details about how to display the Subject column, see 12.4.3(3)(l) Subject.

(2) Rejecting Items

To reject an Item:

If the Item window provides a field for entering the reasons for rejection, enter the appropriate reasons.

Click the Reject button.

The Select Rejection Destination dialog box is displayed.

To cancel, click the Cancel button.

Select either the immediately preceding worker or the worker who first created the Item.

By default, the immediately preceding worker is selected.

Click the Edit Mail button.

The Edit of Notification Mail dialog box is displayed.

Edit the email subject line and body text to notify the recipient of the Item's arrival.

If you do not wish to send an email, select the Mail is not transmitted check box in the Select Rejection Destination dialog box. If you choose not to send this notification email, you can skip steps 4 and 5.

Click the OK button.

The Edit of Notification Mail dialog box closes, and the rejected Item is saved with the edited email.

Click the OK button.

The Select Rejection Destination dialog box closes and the Item is sent to the selected user.

If you specified to send email notification of the Item's arrival, an email is sent to the recipient. You cannot stop this email from being sent.

The following figure shows the Select Rejection Destination dialog box.

Figure 15‒10: Select Rejection Destination dialog box

15.2.2 Specifying a substitute

If you will not be able to handle a received Item because, for example, you will be away for business or personal reasons, you can designate a substitute who will handle the Item. If you set email notification to be sent to the substitute, you can send a notification email to the substitute when the Item is executed. For details about setting a notification to be sent by email to a substitute for an Item, see 7.3.5 Setting Mail Notification Information.

To specify a substitute:

In the Inbox window, click the Substitute Setup button.

The Substitute Settings dialog box is displayed.

To cancel, click the Cancel button.

From the list of personnel, select a worker to be a substitute worker, and click the Add button.

The selected worker is added to the list of substitute workers. Multiple substitute workers can be registered.

Click the OK button.

The Substitute Settings dialog box closes, and the added substitute worker is registered.

The following figure shows the Substitute Settings dialog box.

Figure 15‒11: Substitute Settings dialog box

Note

It might not be possible to send an email if there are multiple substitutes and the total size of the destination email addresses exceeds one kilobyte. In this situation, you should set the email addresses of the substitutes in a mailing list, for example.

15.2.3 Resending a rejected Item

This subsection explains how to correct and resend an Item that was rejected and returned.

To resend an Item:

From the list of Items in the Inbox window, click the link under Item name of the Item that was rejected.

The corresponding Item window is displayed.

Check the reasons for the rejection, and revise the Item as appropriate.

In the Item window, click the appropriate button to send the Item.

The Select Destination dialog box is displayed.

To cancel, click the Cancel button.

Click the User name link, and then specify a user who has official authority to execute the next processing.

The default send destination user is the user who holds the appropriate official authority and who belongs to the same group (or a superior group) as the user who sends the Item.

To send to a user other than the displayed default user, specify the appropriate user.

Click the Edit Mail button.

The Edit of Notification Mail dialog box is displayed.

Edit the email subject line and body text to notify the recipient of the Item's arrival.

If you do not wish to send an email, select the Mail is not transmitted check box on the Select Destination dialog box, and then skip steps 5 and 6.

Click the Add button.

The Edit of Notification Mail dialog box closes and the edited email is registered.

Click the OK button.

The Select Destination dialog box and the Item window close, and the Item is sent to the user specified as the send destination.

If you specify the setting to receive a notification of the Item's arrival, an arrival confirmation email is sent to you.

15.3 Checking and pulling back sent Items (Outbox)

This section explains how to check the status of a sent Item and, if necessary, how to pull back an Item application. This section also explains how to edit and send an Item that was saved while it was being created.

15.3.1 Checking the status of a sent Item

The status of sent Items can be checked from the Outbox window that is displayed when you click the Outbox job menu. The following figure shows the Outbox window.

Figure 15‒12: Outbox window

A list of the Items sent by the logged-in user and the Items saved during creation is displayed in the Outbox window in descending order of the send dates. To check the progress of an Item, click the link under Status in the list. You can click a link under Item name to display the corresponding Item window.

To also display Items whose processing have completed, select the Display completed items as well check box, and then click the Refresh button.

The following Item icons are displayed in the window:

: Within the processing time limit

Indicates that the Item's processing was within the specified processing time limit or that no processing time limit was set.

: Exceeding the processing time limit

Indicates that the Item's processing exceeded the specified processing time limit. For these Items, everything other than the Item name is displayed in red.

15.3.2 Pulling back sent Items

If it is necessary to revise an Item that has been sent, it might be possible to pull back the Item. You can pull back an Item only while it is still in the send destination's Inbox.

From the list of Items in the Outbox window, select the check box next to the send date of the Item that you wish to pull back, and then click the Pullback button. The Item is returned to you from the recipient's Inbox. The status of a pulled-back Item is reset to its status when you received it. Just as with Items saved during creation, you can revise the Item and resend it.

15.3.3 Sending saved Items

An Item whose status is Creating or an Item that has been pulled back can be edited and sent.

From the list of Items in the Inbox window, click the link under Item name of the desired Item to display its Item window.

To send an Item:

In the Item window, click the appropriate button to send the Item.

The Select Destination dialog box is displayed.

To cancel, click the Cancel button.

Click the User name link, and then specify a user who has official authority to execute the next processing.

The default send destination user is the user who holds the appropriate official authority and who belongs to the same group (or a superior group) as the user who sends the Item.

To send to a user other than the displayed default user, specify the appropriate user.

Click the Edit Mail button.

The Edit of Notification Mail dialog box is displayed.

Edit the email subject line and body text to notify the recipient of the Item's arrival.

If you do not wish to send an email, select the Mail is not transmitted check box on the Select Destination dialog box, and then skip steps 3 and 4.

Click the Add button.

The Edit of Notification Mail dialog box closes and the edited email is registered.

Click the OK button.

The Select Destination dialog box and the Item window close, and the Item is sent to the user specified as the send destination.

If you specify the setting to receive a notification of the Item's arrival, an arrival confirmation email is sent to you.

15.3.4 Checking the progress of Items

You can check the progress of Items, such as when sent Items were processed and the last node processed.

In the Outbox window, clicking the link under Status for a desired Item in the list displays a dialog box showing the progress of the Item. The following figure shows the dialog box showing the progress of an Item.

Figure 15‒13: Dialog box showing the progress of an Item

This dialog box displays the route of the corresponding Item and log information about the processing of the Item at each node. You can use this dialog box to check the progress of an Item and obtain details about the user that processed the Item. Processed activities are displayed in orange.

15.3.5 Deleting Items

An Item whose status is Creating can be deleted.

From the list of Items in the Outbox window, select the check box next to the Send date of the Item to be deleted, and then click the Delete button to delete the Item. Multiple Items can be selected.

Only the administrator can delete Items whose status is anything other than Creating. For details about how to delete such Items, see 15.4 Managing Items (Execution Item Management).

15.3.6 Creating a new Item by copying an Item

You can create a new Item by copying an existing Item. This function enables you to skip the input process because you can use an Item that has already been input.

You can use either of the following methods to copy an Item that has already been created:

From the Outbox window's list of Items, select the check box for the Item that you want to copy and then click the Copy and Create New button.

From the Outbox window's list of Items, click the desired Item's link under Item Name, and then click the Copy and Create New button from the Item window that is displayed.

You edit a copied Item in the same way as when you create a new Item. For details about how to edit a copied Item, see 15.1 Creating Items (New Item).

(1) Notes on creating a new Item by copying an Item

You should note the following about creating a new Item by copying an existing Item:

You cannot copy an Item that was added by another user.

Clicking the Copy and Create New button will not copy an Item whose Item status in Item Definition in the job menu is Not Exhibit.

The content that is copied depends on the object attributes of the objects set for the items in the Item window. The following table describes which object attributes of objects can and cannot be copied.

Table 15‒2: Object attributes of objects that can and cannot be copied

Objects

Object attributes

Data type

Initial value

Read-only

Hide

Text box

--

--

--

--

Image

--

--

--

--

Hyperlink

--

--

--

--

Text field

Any double-byte character string

Y

N

N

Any single-byte character string

Y

N

N

Alphabet

Y

N

N

Alphanumeric

Y

N

N

Group reference

Y#

N

N

Location reference

--

N

N

User reference

Y#

N

N

File reference

--

N

N

Device reference

--

N

N

Software name reference

--

N

N

Software reference

N

N

N

Numeric

Y

N

N

Date (YYYYMMDD)

Y#

N

N

Date (YYYYMM)

Y#

N

N

Date (MMDD)

Y#

N

N

Time (HHMMSS)

Y#

N

N

Time (HHMM)

Y#

N

N

Text area

Any double-byte character string

Y

N

N

Any single-byte character string

Y

N

N

Alphabet

Y

N

N

Alphanumeric

Y

N

N

Pull-down

--

Y

N

N

Button

--

--

N

N

Table

--

--

N

N

Legend:

--: Not applicable

Y: Is copied (value copied is final data).

N: Is not copied.

#

If an initial value has been set, the initial value is copied.

15.4 Managing Items (Execution Item Management)

This section explains how to specify conditions, search for Items in the asset management server, and browse Item contents. This section also explains how to check the contents of Items in the search results and how to delete Items regardless of their status.

By default, only the administrator can manage executing Items.

Item management is executed from the Execution Item Management window, which is displayed by clicking the Execution Item Management job menu. The following figure shows the Execution Item Management window.

Figure 15‒14: Execution Item Management window

If you wish to search for an Item and check an Item's contents, from the search results list, click the link under Item name of the desired Item. The corresponding Item window is displayed in read-only mode. However, the window and items that are displayed depend on the official authority held by the user. An Item's current status window is displayed for users with Item Auditor permissions, and such users can also perform such tasks as viewing attached files. For users that do not have Item Auditor permissions, the Item window in the applied status is displayed.

Clicking the link under Status displays the route of the corresponding Item and log information about the processing of the Item at each node. You can use this information to check the progress of the Item.

The administrator can delete unneeded Items or Items whose time limit has been exceeded. To do this, from the search results list, select the check box next to the Registration date of the Item to be deleted, and then click the Delete button to delete the Item. Multiple Items can be selected.

15.5 FAQ (Creating and processing Items)

This section contains frequently asked questions about problems that can occur during Item creation and processing, and it also contains the answers to those questions, explaining the reasons for the problems and the corrective measures that can be considered.

15.5.1 Why are there no usable Items displayed in the New Item window, or why is it that Items cannot be created?

There might be no exhibit Items, or the user might not have official authority to create new Items. Either publish Items or assign official authority to the user who creates Items.

For details about how to publish Items, see 12.7.2 Setting an Item to Exhibit or Not exhibit. For details about how to assign official authority to users, see 12.2.2(2) Registering and changing the target users.

15.5.2 How can I designate someone to approve Items while I am out?

Specify a substitute from the Inbox window.

For details about how to specify a substitute, see 15.2.2 Specifying a substitute.

15.5.3 How can I determine the status of an Item application?

You can check the status of an Item application from the Outbox window.

For details about checking Item status, see 15.3.1 Checking the status of a sent Item.

15.5.4 How can I delete an Item application?

Pull back the Item from your Outbox window. However, if the Item has already been sent, you can pull it back only if it is still in the Inbox at the send destination. After pulling back the Item, delete it.

For details about pulling back Items, see 15.3.2 Pulling back sent Items. For details about deleting Items, see 15.3.5 Deleting Items.

16 Managing Shared Information

This chapter explains how to execute jobs that manage the shared information used in system operations. These management jobs are executed from the System Management job category. Each section title shows the job menu to be selected, in parentheses.

With the exception of processing executed from the Search Users and Individual Information job menus, only administrators can execute shared information management.

16.1 Changing user and group information (Group and User)

By using the Group and User job menu, you can change information about users and groups, to reflect changes in the organization of groups and personnel. You can also use this job menu to change Managed label, which is used to limit accesses at the group level.

To change information about users and groups, use the Group and User window, which is displayed by clicking the Group and User job menu. The following figure shows the Group and User window.

Figure 16‒1: Group and User window

To change the groups that are displayed, use the Group tab to create a simple search condition. However, even when a division has been assigned to a login user, you cannot display a group by selecting the division from the Group tab in this window.

By default, the asset manager (user ID: admin), which is an administrator user, is registered at the highest level. You cannot delete this administrator user.

When you click a Group name/User name link, you will be able to view and edit detailed information about the group, division, or user.

User for linking to other products

When you link to other products, a user is created for browsing Asset Console's asset information from each product.

The following table describes the user used to link to other products.

Table 16‒1: User used to link to other products

User ID

User name

Role name

Linked product

JP1_IM

Event manager

User

JP1/IM

JP1_IM_SS

Service support manager

User

JP1/Service Support

If a password is set up for the user used to link to other products, when the user browses Asset Console asset information from each product, the user is automatically logged in to Asset Console.

16.1.1 Adding a group

To add a group:

From the simple search conditions, select the group following which a group is to be added.

Click the Add Group button.

The Add Group dialog box is displayed.

Items identified by a star () are mandatory.

Group ID

Specifies a unique ID for each group. Only alphanumeric characters are permitted. Note that the single-byte alphabetic characters are not case-sensitive. Also note that you must specify a value that is not in the range from 1000000001 to 9999999999. For Group ID, specify a group ID other than the ID that is assigned for the Trash that is used to temporarily save users belonging to deleted groups. The group ID for the Trash is set in the Server Setup dialog box, and the default is 99999999.

For details about the settings in the Server Setup dialog box, see 7.3.4(6) Trash group ID for deletions.

Group name (English)

Specifies a group name in English. Do not end the group name with a slash (/). A group that has the same name cannot be created more than once at the same level in the hierarchy.

Group name

Specifies a group name. Do not end the group name with a slash (/). A group that has the same name cannot be created more than once at the same level in the hierarchy.

Managed label

To limit accesses by group level, specify Managed label. For details about how to specify Managed label, see 5.1.3 Assigning access permissions according to organizational hierarchy.

To cancel, click the Close button.

Click the Add button.

The group is added to the simple search condition based on the specified information.

The following figure shows the Add Group dialog box in which information about a group to be added is specified.

Figure 16‒2: Add Group dialog box

16.1.2 Adding a user

To add a user:

From the simple search conditions, select the group to which you want to add a user.

Note that you cannot add a user to the group at the highest level.

Click the Add User button.

The Add User dialog box is displayed.

Items identified by a star () are mandatory.

User ID

Specifies a unique ID for each user. Alphanumeric characters are permitted.

Password

Specify a password for the user (you must specify it twice for confirmation purposes). Alphanumeric characters are permitted.

User name (English)

Specify a user name in English for the user.

User name

Specify a user name for the user.

In Role, select the appropriate user role for the user.

To cancel, click the Close button.

Click the Add button.

The user is added based on the specified information.

The following figure shows the Add User dialog box, in which information about a user to be registered is specified.

Figure 16‒3: Add User dialog box

16.1.3 Deleting groups or users

To delete a group or user, select its check box in the Group and User window, and then click the Delete button.

A deleted group or user is moved to the Trash that has been created in the group tree. If there are groups and users under the deleted group, the group is moved to the Trash with its hierarchical relationship and user information retained as is. Therefore, if you delete a group by mistake, you can restore it to its original location from Trash. However, if the group is deleted from the Trash, it can no longer be restored.

Note

If you use the IP Group job menu to create a group-specific IP group and manage IP addresses, deleting the group also deletes the associated IP groups. However, while the deleted group is in the Trash, the IP group is not deleted.

16.1.4 Moving groups or users

To move a group or a user:

Select the check box for the group or user to be moved, and then click the Move button.

The Browse Groups dialog box is displayed. Note that Trash is not displayed as a destination for the move.

To cancel, click the Close button.

Specify the target location, and then click the OK button.

The group or user is moved to the specified location.

16.1.5 Viewing and editing groups

From the simple search conditions, select the group that is one level higher than the group that you want to view or edit. Click a Local name link shown in Group name/User name to display the Group Details dialog box. On the Group tab of this dialog box, you can view or edit the detailed information about the group.

The following figure shows the Group tab in the Group Details dialog box.

Figure 16‒4: Group Details dialog box (Group tab)

(1) Changing group information

To change group information:

Select the Group tab in the Group Details dialog box.

The items that can be specified are the same as for the Add Group dialog box. For details about the items that can be specified, see step 2 in 16.1.1 Adding a group. However, Group ID cannot be changed.

To cancel, click the Close button.

Click the Update button.

The group information is changed based on the specified information.

(2) Deleting group information

To delete group information:

Select the Group tab in the Group Details dialog box.

Click the Delete button.

The group information for the displayed group is deleted.

Note that deleting a group in the Group Details dialog box is the same as deleting a group in the Group and User window. For details about deleting groups in the Group and User window, see 16.1.3 Deleting groups or users.

16.1.6 Viewing and editing divisions

From the simple search conditions, select the group that is one level higher than the group that you want to view or edit. Click a Local name link shown in Group name/User name to display the Group Details dialog box. On the Divisions tab of this dialog box, you can view or edit the detailed information about the division.

The following figure shows the Divisions tab of the Group Details dialog box.

Figure 16‒5: Group Details dialog box (Divisions tab)

(1) Adding divisions

To add a division:

Select the Divisions tab in the Group Details dialog box.

Click the Add button.

The Register Divisions dialog box is displayed.

Items with item names marked with a star () must be specified.

Division name

Specify a name for the division. Note that you cannot create a division that has the same name as a division that already exists.

Groups

If you select a group from the tree, the groups that belong below that group are shown in Groups. Note that the highest group (at the top of the tree) cannot be selected.

Groups (Division group)

The groups belonging directly below the group that is selected in Groups are displayed.

Division group (Division group)

Groups specified in division groups are displayed. If you select a group displayed in Groups and click the Assign button, the selected group is moved to Division Groups.

To cancel the specified divisions, select a group displayed in Division group and click the Cancel button. This will move the selected group to Groups.

If you click the Assign all button, the groups displayed in Groups are all moved to Division group.

If you click the Unassign all button, all groups displayed in Division group are moved to Groups.

To cancel, click the Cancel button.

Click OK.

The division is added based on the specified information.

The following figure shows the Register Divisions dialog box.

Figure 16‒6: Register Divisions dialog box

(2) Changing division information

To change division information:

Select the Divisions tab in the Group Details dialog box.

Click a division name link to change that division's information.

The Refresh Divisions dialog box is displayed. You can change division information in this dialog box.

The items that can be specified are the same as for the Register Divisions dialog box. For details about the items that can be specified, see step 2 in 16.1.6(1) Adding divisions. Note that groups already specified as divisions are displayed in Division Groups.

To cancel, click the Cancel button.

Click OK.

The division information is changed based on the specified information.

(3) Deleting a division

To delete a division:

Select the Divisions tab in the Group Details dialog box.

Select the check box of the division you want to delete.

Click the Delete button.

The selected division is deleted.

(4) Assigning a division to a user

To assign a division to a user:

Select the Divisions tab in the Group Details dialog box.

Select the check box for the division you want to assign to a user.

You can assign only one division at a time.

Click the Assign button.

The Assign Divisions dialog box is displayed.

Groups

If you select a group in the tree, the user names belonging directly below that group are shown in Personnel. However, it is not possible to select the highest group (at the top of the tree).

Personnel (Supervisor)

The user names belonging directly below the group that is selected in Groups are displayed.

Supervisor (Supervisor)

The user names to which the division is assigned are displayed. If you select a user name displayed in Personnel and click the Assign button, the selected user name is moved to Supervisor.

To release the assignment of a specified user, click the Cancel button. This will move the selected user name to Personnel.

If you click the Assign all button, all user names displayed in Personnel are moved to Supervisor.

If you click the Unassign all button, all user names displayed in Supervisor are moved to Personnel.

To cancel, click the Cancel button.

Click OK.

The division is assigned based on the specified information.

The following figure shows the Assign Divisions dialog box.

Figure 16‒7: Assign Divisions dialog box

(5) Exporting division information to a CSV file

You can export to a CSV file the division information that is set for a group. The following items are exported:

Division name

Division groups

User names

To export division information to a CSV file:

Select the Divisions tab in the Group Details dialog box.

Click the CSV button.

A listing of the information for the division displayed on the Divisions tab of the Group Details dialog box is exported.

16.1.7 Viewing and editing user information

From the simple search conditions, select the group that is one level higher than the group that you want to edit or for which you want to view user information. Click a User name link shown in Group name/User name to display the User Details dialog box. You can view or edit detailed user information in this dialog box.

(1) Changing user information

To change user information:

Select the User name link for the user whose information you want to change.

The User Details dialog box is displayed.

The items that can be specified are the same as for the Add User dialog box. For details about the items that can be specified, see step 2 in 16.1.2 Adding a user. However, User ID cannot be changed.

To cancel, click the Close button.

Click the Update button.

The user information is changed based on the specified information.

(2) Deleting user information

To delete user information:

Select the User name link for the user information that you want to delete.

The User Details dialog box is displayed.

Click the Delete button.

The selected user is deleted. Note that it is not possible to delete a user in the highest group.

Note that deleting a user in the User Details dialog box is the same as deleting a user in the Group and User window. For details about deleting users in the Group and User window, see 16.1.3 Deleting groups or users.

16.2 Searching for users (Search Users)

By using the Search Users job menu, you can search for users without regard to group. Because you can identify a user from information that you have, you can search for users in a role that you want to delete, or you can look up a telephone number from a user name.

To search for users, use the Search Users window, which is displayed by clicking the Search Users job menu. The following figure shows the Search Users window.

Figure 16‒8: Search Users window

When you click a User name link in a search results list, the User Details dialog box is displayed and you can check the detailed information about the user.

16.3 Changing information about asset locations (Location)

By using the Location job menu, you can change information about locations in order to reflect the fact that a workplace has moved or expanded.

By default, only the administrator can execute Location.

To change location information, start from the Location window, which is displayed by clicking the Location job menu. The following figure shows the Location window.

Figure 16‒9: Location window

To change the list of locations to be displayed, select a desired group in the tree in the left-hand frame in the Location tab window.

Clicking a link under Location displays the Location Details dialog box that enables you to view and change details.

16.3.1 Adding a location

To add a location:

From the simple search condition, select the location following which a location is to be added.

No location can be added under Trash.

Click the Add button.

The Add Location dialog box is displayed.

Items identified by a star () are mandatory.

Location ID

Specifies a unique ID for each location. Only alphanumeric characters are permitted. Note that the alphabetic characters are not case-sensitive. Also note that you must specify a value that is not in the range from 1000000001 to 9999999999. This location ID must be different from that of Trash used to temporarily save the deleted locations. The location ID of Trash is set in the Server Setup dialog box. The default is 99999999.

For details about the settings in the Server Setup dialog box, see 7.3.4(7) Trash location ID for deletions.

Local name (English)

Specify a name in English for the location. Do not end the location name with a slash (/). A location that has the same name cannot be created more than once at the same level in the hierarchy.

Local name

Specify a name for the location. Do not end the location name with a slash (/). A location that has the same name cannot be created more than once at the same level in the hierarchy.

To cancel, click the Close button.

Click the Add button.

The location is added to the simple search condition based on the specified information.

The following figure shows the Add Location dialog box in which information about a location to be registered is specified.

Figure 16‒10: Add Location dialog box

16.3.2 Deleting a location

To delete a location, select its check box in the Location window, and then click the Delete button.

Any locations set under that location are also deleted.

The deleted location is moved to the Trash created in the tree for the location. If there are locations under the deleted location, they are moved to the Trash with their hierarchical relationship maintained. Therefore, if you delete a location by mistake, you can restore it by moving it from the Trash back to its original location. Note that locations cannot be restored once they are deleted from the Trash.

Notes

If you use the IP Group job menu to create a location-specific IP group and manage IP addresses, deleting the location also deletes the associated IP groups. However, while the deleted location is in the Trash, the IP group is not deleted.

If the settings in the Customize Job Menu job menu allow a user other than the administrator to use the Location job menu, once a non-administrator user logs out, the Trash is no longer displayed. To restore a location from the Trash to its original location after logging out, the user must contact the administrator.

16.3.3 Moving a location

To move a location:

In the Location window, select the check box for the location that you want to move.

To restore a deleted location, select the check box for the location in the Trash.

Click the Move button.

The Browse Locations dialog box is displayed.

To cancel, click the Cancel button.

Specify the target location, and then click the OK button.

The target location cannot be a location in the Trash.

The Browse Locations dialog box closes, and the location selected in the Location window moves to the specified location.

16.4 Changing IP group information (IP Group)

By using the IP Group job menu, you can group IP addresses by address ranges and manage them as IP groups. You can create groups by department and location, and assign desired names to them to manage IP address usage. IP group management is applicable only to the IP addresses of IPv4.

By default, only the administrator can execute IP Group.

To change IP group information, use the IP Group window, which is displayed by clicking the IP Group job menu. The following figure shows the IP Group window.

Figure 16‒11: IP Group window

By clicking a link under IP group name in a search results list, you can view, change, and delete the details about that IP group.

To manage IP addresses by group, use the Group-Specific IP Group tab to create IP groups, and to manage IP addresses by location, use the Location-Specific IP Group tab to create IP groups. To manage a group by subgroups or manage multiple groups as a single group, use the IP Group tab to create IP groups.

When you create an IP group in the Group-Specific IP Group tab or Location-Specific IP Group tab, it is also possible to automatically register a group and location that correspond to the IP address of each machine at the following times:

Collection of JP1/IT Desktop Management 2 - Manager management information

Execution of a Data maintenance task

Even if information about groups and locations is not collected in JP1/IT Desktop Management 2 - Manager, it is possible to register a group and location by using its IP address.

To automatically register a group and location that correspond to the IP address, you must specify settings in the Server Setup dialog box. For details about how to specify settings in the Server Setup dialog box, see 7.3.4(11) Settings for a group that uses a group-specific IP group and 7.3.4(12) Settings for a location that uses a location-specific IP group. To automatically register a group and location that correspond to the IP address during execution of the Data maintenance task, you must edit the setup file (taskopt.ini). For details about how to edit the setup file, see 7.9.3(3) Changing the tasks to be executed. For details about how to add IP addresses individually, see 14.6.2(1) Adding an IP address.

16.4.1 Adding an IP group

To add an IP group:

Select a tab to which an IP group is to be added.

Click the Add button.

Depending on the selected tab, the Add IP Group, Add Group-Specific IP Group, or Add Location-Specific IP Group dialog box is displayed.

Items identified by a star () are mandatory.

When specifying IP address range, make sure that the number of IP addresses in the range does not exceed 1,024.

To cancel, click the Close button.

Note

In the same tab, no IP group can have an overlapping IP address range. IP groups in different tabs might have overlapping address ranges. If you create IP groups with overlapping address ranges in different tabs, make sure that the same IP address in different tabs has different DHCP server usage settings. IP addresses in an IP group that uses the DHCP server are treated as unused IP addresses, even when they are fixed.

Click the OK button.

The IP group is registered based on the specified information.

The following figure shows the Add Group-Specific IP Group dialog box in which information about the IP group to be registered is specified.

Figure 16‒12: Add Group-Specific IP Group dialog box

16.4.2 Viewing IP address usage

To view information from the IP group search list in each tab, such as IP address usage and to where IP addresses are allocated:

In the IP group search list in each tab, click the IP address range link.

The IP Address Management dialog box is displayed, showing the usage of IP addresses in the group and IP address assignment target.

Narrowing down the list by usage

From the drop-down list, select Unused, Used, or Used (multiple only) and then click the Show button.

Checking the devices sharing the same IP address

Click a link under Used (multiple only) in the Usage condition column.

The IP Address Management - Device List dialog box is displayed, showing a list of devices sharing the same IP address.

To release the assignment, select the Asset No. check box and then click the Cancel button.

Displaying information about devices and users

Clicking a link under Asset No. or User name displays the Device Details dialog box or User Details dialog box.

Click the Close button.

The IP Address Management dialog box closes.

The following figure shows the IP Address Management dialog box.

Figure 16‒13: IP Address Management dialog box

16.4.3 Assigning IP addresses to devices

To assign IP addresses to devices:

In the IP group search list in each tab, click the IP address range link.

The IP Address Management dialog box is displayed.

Click the link for the IP address that you want to assign to a device.

The IP Address Management - Asset Assignment dialog box is displayed.

If necessary, specify the search condition and click the Search button.

Devices matching the search condition are searched for among devices with no IP address assigned.

To cancel, click the Close button.

Select a device from the search result and then click the Assign button.

The IP address is assigned to the selected device.

The following figure shows the IP Address Management - Asset Assignment dialog box with the devices searched.

Figure 16‒14: IP Address Management - Asset Assignment dialog box

16.4.4 Releasing the IP addresses assigned to devices

To release IP addresses assigned to devices:

In the IP group search list in each tab, click the IP address range link.

The IP Address Management dialog box is displayed.

Click the link under Usage condition for the IP address whose assignment you want to release.

The IP Address Management - Device List dialog box is displayed.

To cancel, click the Close button.

Select the Asset No. check box for the device whose assignment is to be released, and then click the Cancel button.

The assignment of IP address to the selected device is released.

The network information that contains the released IP address is deleted as follows:

If DHCP server name has been registered (or at least MAC address, Host name, or Computer name has been registered), the network information is deleted, unless there is a corresponding value when JP1/IT Desktop Management 2 - Manager management information is acquired.

If none of DHCP server name, MAC address, Host name, or Computer name has been registered, the network information is deleted when the assignment is released.

16.4.5 Downloading the IP address usage

To download the IP address usage for each IP group as a CSV file:

In the IP group search list in each tab, click the IP address range link.

The IP Address Management dialog box is displayed.

To cancel, click the Close button.

From the drop-down list, select the IP address usage that you want to download and then click the CSV button.

IP address, Asset No., User name, and Device type of the IP address that matches the selected usage are output to a CSV file.

If the selected usage is blank, Used, or Used (multiple only), a dialog box is displayed, asking whether to output information about all devices assigned to each IP address.

To output information about the IP address and about all devices using the IP address, click the Yes button.

To output information about the IP address and about one device using the IP address, click the No button. If you do not need to output information about all devices, such as when you are only checking whether a particular IP address is in use, click the No button.

To cancel, click the Cancel button.

16.4.6 Deleting an IP group

To delete an IP group in each tab:

On the IP group search list in each tab, select the check box for the IP group that you want to delete.

Click the Delete button.

A confirmation message dialog box is displayed. Clicking the OK button deletes the IP group.

16.5 Managing device catalog information (Device Catalog)

By using the Device Catalog job menu, you can register and edit the device catalog information that is used to register new devices.

Some device information is predefined for each product, such as CPU and memory size. A collection of these items that have already been registered is called a device catalog.

For items that are already registered, you can save time in entering predefined items by selecting the device catalog for the product to be registered.

By default, only the administrator can perform device catalog management.

To manage device catalogs, use the Device Catalog window, which is displayed by clicking the Device Catalog job menu. The following figure shows the Device Catalog window.

Figure 16‒15: Device Catalog window

Clicking a link under Device name in a search results list displays the Device Catalog Details dialog box, which enables you to view the details of the corresponding catalog information. You can also use this dialog box to change and delete catalog information.

16.5.1 Registering a device catalog

To register a device catalog:

Click the Add button.

The Add Device Catalog dialog box is displayed.

Items identified by a star () are mandatory.

To cancel, click the Close button.

Click the OK button.

The device catalog is registered based on the specified information.

The following figure shows the Add Device Catalog dialog box, in which information to be registered is specified.

Figure 16‒16: Add Device Catalog dialog box

Attaching device image files

Image files can be attached to device catalogs. To specify a file for attachment, click the Attach button for Attached files, and then from the displayed Edit Attached Files dialog box, enter the file name in File name.

16.5.2 Deleting a device catalog

To delete a device catalog, select its check box, and then click the Delete button.

You can also delete a device catalog from the Device Catalog Details dialog box, which is displayed by clicking the corresponding link under Device name in a search results list.

16.6 Establishing correspondence between software names (Software Name)

By using the Software Name job menu, you can establish correspondence between the names of installed software assets and the software asset names so that it becomes possible to manage license usage. The names of installed software assets are the names used at the sources of the management information and registered as is by JP1/IT Desktop Management 2 - Manager into the asset management database. Therefore, to manage license usage correctly, you must establish the correspondence between these names and the actual names of the software assets.

You can also change other software information (such as the email notification threshold for exceeded licenses, license information, and downgrade software).

By default, only the administrator can execute Software Name.

To establish correspondence between software names, start from the Software Name window, which is displayed by clicking the Software Name job menu. The following figure shows the Software Name window.

Figure 16‒17: Software Name window

In a search results list, clicking a link under Software name displays the Software Name Details dialog box. This dialog box enables you to execute various tasks, such as changing software names, assigning installed software names, and registering license information and downgrade software assets.

Installed software name displays the installed software name and version. If a file name has been registered, this item also displays the file name, file size, and file date.

16.6.1 Registering a software name

Software names are the names of software that are used for management of assets. To register a license and assign a software name, select a software name from those that are registered here.

To register a new software name:

Click the Add button.

The Add Software dialog box is displayed.

To cancel, click the Close button.

Specify Software name, Software type, Developer, and Threshold, and then click the OK button.

Specification of Software name and Software type is mandatory.

To specify Software type:

By specifying Commercial or Shareware, the software comes under license management and is counted in the totals of the Owned License List job menu. If the number of licenses in use exceeds the number of licenses you own, the Excess License List job menu is displayed and an email notification is sent.

If Freeware is specified, the license is unlimited and the software is not displayed in the number of owned and available licenses in the Owned License List job menu. Also, the Excess License List job menu is not displayed.

The Add Software dialog box closes, and the software name is registered based on the specified information.

The following figure shows the Add Software dialog box in which a software name to be registered is specified.

Figure 16‒18: Add Software dialog box

16.6.2 Consolidating software names

You can consolidate multiple software names into one for management purposes.

To consolidate software names:

In Software name, as the search condition, specify the name to be consolidated, and then click the Search button.

The specified software names are retrieved.

You cannot consolidate names for different types of software.

In Software name, select the check box for the software name to be consolidated and then click the Consolidate button.

The Consolidate Software dialog box is displayed.

To cancel, click the Close button.

Select the radio button for the software to be consolidated and then click the Consolidate button.

The Consolidate Software dialog box closes, and the selected software assets are consolidated into one.

Any installed software name assigned before consolidation is maintained as is after consolidation. Note that no downgrade software is consolidated, if registered. Use the Software Name Details dialog box to re-register downgrade software assets, if necessary. For details about registering downgrade software assets, see 16.6.9 Adding downgrade software assets.

The following figure shows the Consolidate Software dialog box in which the software name to be consolidated is selected.

Figure 16‒19: Consolidate Software dialog box

16.6.3 Deleting a software name

To delete a software name, select its check box in the search results of the Software Name window, and then click the Delete button.

16.6.4 Changing a software name and attributes

Software Name manages the software names and, for each software name, the type, developer, and threshold that has been set.

The threshold is used to monitor license usage status and for determining when to send email notification to the asset manager. If no threshold is set, the value specified in the Server Setup dialog box is assumed (the default is 100%).

For details about specifying the settings in the Server Setup dialog box, see 7.3.4(8) Threshold for license excess.

To change a software name, software type, developer, and threshold:

Specify a search condition, if necessary, and search for the software name to be changed.

The software names satisfying the condition are retrieved.

Click the link of the software name to be changed.

The Software Name Details dialog box is displayed.

To cancel, click the Close button.

In the Name tab, edit Software name, Software type, Developer, and Threshold.

For Threshold, specify a numeric value in the range from 0 to 100 (%).

If the software type is changed from Commercial or Shareware to Freeware, the number of owned licenses is not changed automatically to unlimited. To change the license into unlimited for software for which the software type has been changed to Freeware, you need to take some operation. To do so, delete the number of owned licenses registered in the Software Details dialog box (Asset tab) and select the Unlimited license check box.

Click the Update button.

The Software Name Details dialog box closes, and the information is updated based on the edited information.

16.6.5 Assigning an installed software name

To assign an installed software name to a software name:

Specify a search condition, if necessary, and search for the software name to be changed.

The software names satisfying the condition are retrieved.

Click the link of the software name to be changed.

The Software Name Details dialog box is displayed.

To cancel, click the Close button.

In the Assign tab, click the Add button.

The Add Installed Software dialog box is displayed.

Search for the installed software name to be assigned.

The system searches for the installed software names that have not been assigned to any software name.

To cancel, click the Close button.

In the search results, select the check box of the installed software name to be assigned, and then click the OK button.

The Add Installed Software dialog box closes, and the selected installed software name is added as the assigned installed software name. To add another installed software name, repeat steps 3-5.

Click the Close button.

The Software Name Details dialog box closes.

The following figure shows the procedure for adding an installed software name from the Software Name Details dialog box.

Figure 16‒20: Procedure for adding an installed software name to be assigned

Once an installed software name is assigned, the corresponding software asset information cannot be deleted. To delete such software asset information, you must first release the assigned installed software name.

Assigning multiple installed software names

You can assign multiple installed software names to a single software name. In such a case, the usage count is 1 even when the software asset assigned to the same software name is installed on the same machine.

This makes license management easy, for example, when the same software is not managed by version or when downgrading is applied in the entire company.

16.6.6 Releasing assignment of an installed software name

To release the assignment of an installed software name, select its check box in the Assign tab in the Software Name Details dialog box, and then click the Cancel button.

16.6.7 Registering license information

To register license information:

Specify a search condition, if necessary, and search for the software name for which license information is to be registered.

The software names satisfying the condition are retrieved.

Click the link of the software name for which license information is to be registered.

The Software Name Details dialog box is displayed.

To cancel, click the Close button.

In the License tab, click the Add button.

The Add License dialog box is displayed.

Specify each item as appropriate for the license, and then click the OK button.

Make sure that License name is specified.

The Add License dialog box closes, and the specified license information is registered.

The following figure shows the Add License dialog box in which license information is specified.

Figure 16‒21: Add License dialog box

16.6.8 Changing license information

To change license information:

Specify a search condition, if necessary, and search for the software name for which license information is to be changed.

The software names satisfying the condition are retrieved.

Click the link of the software name to be changed.

The Software Name Details dialog box is displayed.

To cancel, click the Close button.

In the License tab, click the link under License name of the license information to be changed.

The License Information Details dialog box is displayed.

Edit each item, and then click the Update button.

Make sure that License name is specified.

The License Information Details dialog box closes, and the license information is updated based on the edited information.

16.6.9 Adding downgrade software assets

To use an older version with a purchased license (for example, purchasing Windows 8 and using Windows 7), you must register the software name for the older version.

To add a downgrade software asset:

In Software name, specify as the search condition the software name to which a downgrade software asset is to be added, and then click the Search button.

The applicable software names are retrieved.

Click the link of the software name to which the downgrade software asset is to be added.

The Software Name Details dialog box is displayed.

To cancel, click the Close button.

In the Downgrade tab, click the Add button.

The Software dialog box is displayed.

Specify a desired search condition, and then click the Search button.

The software assets satisfying the specified condition are retrieved.

Select the check box of the software name that is to be registered as downgrade software, and then click the OK button.

The Software dialog box closes, and the specified software asset is registered as downgrade software.

In order for the registered downgrade software to be subject to license management totals, Downgrade must be set to Enable when the license is registered. For details about how to register licenses, see 14.4.5(2) How to specify a license name.

16.6.10 Releasing a software name from downgrade software

To release a software name from downgrade software, select its check box in the Downgrade tab in the Software Name Details dialog box, and then click the Cancel button.

16.7 Changing information about installed software (Installed Software)

By using the Installed Software job menu, you can manage the names of installed software assets. This job also manages whether installation and licenses for each such software asset are to be permitted.

By default, only the administrator can execute Installed Software.

To manage installed software assets, use the Installed Software window, which is displayed by clicking the Installed Software job menu. The following figure shows the Installed Software window.

Figure 16‒22: Installed Software window

Installed software name displays the installed software name and version. If a file name has been registered, the file name, file size, and file date are also displayed.

For each installed software, in addition to the name and version, the following information is set in order to manage its licenses:

Permission

Sets whether installation of the software is to be permitted. By specifying this information, you can manage the software to protect against unauthorized installation or usage.

Software type

Sets the type of software. By setting the type to be managed separately from other software assets, you can use this information in user reports, and others.

If management information acquired by JP1/IT Desktop Management 2 - Manager is registered, Normally, Office products, Virus definition, or Operating system is set.

Managed level

Sets the level at which licenses are to be managed. This setting is used to register information when management information is acquired from JP1/IT Desktop Management 2 - Manager.

Managed object

Include the software asset in license usage counts.

Managed object not in license count

Do not include the software asset in license usage counts. Register it as an installed software asset.

Unmanaged object

Do not manage licenses and do not register it as an installed software asset.

16.7.1 Registering an installed software name

The installed software name is the name of the software as it is installed on the device. When an installed software asset is added in the Software tab in the Device Details dialog box, the name registered here is selected as the installed software name.

In each job menu under the job category Software License, to execute software license management, you must not only register an installed software name but also assign a software name to the registered installed software name.

To register a new installed software name and establish its correspondence with a software name:

Click the Add button.

The Add Installed Software dialog box is displayed.

To cancel, click the Close button.

Specify an item.

Items identified by a star () are mandatory.

Click the Browse button for Software name.

The Select Software dialog box is displayed.

If necessary, specify the search condition and click the Search button.

The software names satisfying the condition are retrieved.

Select the name of the software that you want to establish correspondence with the installed software name to be registered, and then click the OK button.

The Select Software dialog box closes, and Software name is specified.

In the Add Installed Software dialog box, click the OK button.

The Add Installed Software dialog box closes, and the installed software name is registered based on the specified information.

The following figure shows the Add Installed Software dialog box in which the software name to be registered is specified.

Figure 16‒23: Add Installed Software dialog box

16.7.2 Changing the installed software information

To change an installed software name, version, permission, type, managed level, and correspondence with software name:

From the search results in the Installed Software window, click the link of the installed software name to be changed.

The Installed Software Details dialog box is displayed.

To cancel, click the Close button.

Edit each item.

To change the correspondence with the software name, use the Select Software dialog box that is displayed by clicking the Browse button.

To release the correspondence with the software name, click the Clear Settings button in the Select Software dialog box.

Click the Update button.

Information about the installed software asset is updated based on the edited information.

To change multiple installed software information items in a batch operation

The values of Permission, Software type, and Managed level can be changed in a batch operation for multiple installed software items.

Select the check boxes for the names of the installed software that you wish to change, click the Batch Update button, and the Batch Update dialog box is displayed.

Specify Permission, Software type, or Managed level in the Batch Update dialog box, and then click the OK button to change the specified values.

Note

Suppose Installed software name, Installed software version, File name, File size, or File date is changed from the installed software information collected from JP1/IT Desktop Management 2 - Manager management information. In such a case, the next time management information is collected, the above changed software item is recognized as different software.

16.7.3 Assigning to a software name

To search for an installed software name that has not been assigned to a software name and assign it to a software name:

In the search condition Assign Software, specify Unassigned, and then click the Search button.

The installed software names that have not been assigned to software names are retrieved.

Click the Installed software name link.

The Installed Software Details dialog box is displayed.

Click the Browse button for Software name.

The Select Software dialog box is displayed.

If necessary, specify conditions and then click the Search button.

The software names satisfying the conditions are listed.

Select the software name to which you want to assign the installed software name, and then click the OK button.

The Select Software dialog box closes and Software name is specified.

In the Installed Software Details dialog box, click the Update button.

The Installed Software Details dialog box closes and the installed software name is assigned to the software name.

16.7.4 Deleting an installed software name

To delete an installed software name, select its check box in the search results of the Installed Software window, and then click the Delete button.

If the specified installed software name has been assigned to a software name, a confirmation message dialog box is displayed. Clicking the OK button releases the assignment to the software name and deletes the installed software name.

To cancel deleting the installed software name, click the Cancel button.

16.8 Adding and changing types and statuses (Code)

Information that is managed by defining its type, such as device and software status, is associated with codes in the asset management database.

By editing the codes and attributes (code display values or whether to display the codes in a window operation), you can add and edit the search conditions specified with each job menu and the output result.

For example, you can add a new device type to the Device type item in the New Device window or Device Details dialog box, or you can hide unneeded CPU types for the Processor item.

For details about the codes managed in the asset management database, see 20.2 Lists of properties for object classes.

By default, only the administrator can execute Code.

To edit codes, start from the Code window, which is displayed by clicking the Code job menu. The following figure shows the Code window.

Figure 16‒24: Code window

16.8.1 Adding codes

To add a code:

In the Managed class list, click the link of the class to which a code is to be added.

The code ID of the selected class is displayed.

Some code information cannot be added. For details about the code information that cannot be added, see 16.8.6 Code information that cannot be added or deleted.

Click the link of the Code ID to which a code is to be added.

The code and the corresponding display value are displayed.

The contract information and company catalog, and the hardware information and device catalog share code information. For details about the shared codes, see 16.8.5 Code IDs shared among multiple classes.

Click the Add button.

The Add Code dialog box is displayed.

Code value and Display value must be specified. You cannot add a code or display value that has already been registered.

Note that the meaning of a code might depend on the numerical range in which it is specified. The code ranges that can be specified have specific code IDs. For details about the code specification ranges, see 16.8.4 Meaning of codes depending on specification range.

To cancel, click the Close button.

Click the OK button.

The code is added based on the specified information, and the Add Code dialog box closes.

The following figure shows the Add Code dialog box in which a code to be registered is specified.

Figure 16‒25: Add Code dialog box

Note

To add a code to CPUType and OSType for items added by JP1/IT Desktop Management 2 - Manager, make sure that the added code matches JP1/IT Desktop Management 2 - Manager's system information CPU type.

Note that CPUType is used with an automatically-added value in the range from 90000 to 90999. If you add a unique code to CPUtype, make sure that the specified value is in the range from 00000 to 89999, or from 91000 to 99999.

16.8.2 Changing a code's display value

To edit a code's display value:

From the list of Managed class, click the link of the class whose code is to be edited.

The code IDs of the selected class are displayed.

Click the link under Code ID of the code to be edited.

The codes and corresponding display values are displayed.

The contract information and company catalog, and the hardware information and device catalog share code information. For details about the shared codes, see 16.8.5 Code IDs shared among multiple classes.

In the Code value list, click the link of the code to be edited.

The Edit Code dialog box is displayed.

To cancel, click the Close button.

Edit Display value, and then click the Update button.

The code information is updated based on the specified information, and the Edit Code dialog box closes.

Specification of Display value is mandatory.

16.8.3 Deleting code information

To delete code information:

From the list of Managed class, click the link of the class whose code is to be deleted.

The code IDs of the selected class are displayed.

Click the link under Code ID of the code to be deleted.

The codes and corresponding display values are displayed.

The contract information and company catalog, and the hardware information and device catalog share code information. For details about the shared codes, see 16.8.5 Code IDs shared among multiple classes.

In the Code value list, click the link of the code to be deleted.

Click the Delete button.

The selected code information is deleted. Note that a code whose check box is disabled cannot be deleted. For details about the code information that cannot be deleted, see 16.8.6 Code information that cannot be added or deleted.

16.8.4 Meaning of codes depending on specification range

Depending on the code specification range, there might be code IDs whose addable codes are limited in range, or code IDs which are treated differently in the asset management system. When adding or changing codes, you must note the appropriate specification range.

The following table describes the code IDs along with the specification ranges in which they can be added.

Table 16‒2: Code IDs whose range of codes that can be added is limited

Managed class (managed class name)

Code ID (display name)

Range for addition

HardwareInfo (hardware information)

ModelKind (composition)

970-998

MonitorKind (monitor type)

970-998

MonitorResolution (monitor resolution)

970-998

InstalledList (installed software list)

InstalledKind (software type)

170-198

LicenseInfo (license information)

LicenseType (license type)

170-199

PurchaseType (licensing method)

170-199

LocationInfo (location information)

Attribute (attribute)

170-198

VolumeContract (volume contract information)

VolumeContractKind (category)

170-199

VolumeContractObject (software asset)

170-199

Others (codes not belonging to any of the above)

MatterCategory (item category)

000-099,

200-299

The following table describes the meanings of the codes depending on their specification ranges.

Table 16‒3: Meanings of codes depending on their specification range

Code ID

Displayed name

Meaning

Code range

Category

Range for addition

Default

AssetStatus

Status

Active#1

000-499

000-299 (Used)

270-299

002: Active

300-499 (Not used)

470-499

301: Stock

Scrap#2, #3, #4

500-719

500-599 (Restore)

570-599

501: Restore

600-699 (Scrap)

670-699

601: Scrap

700-719 (Pre-scrap)

710-719

701: Pre-scrap

Erase#4, #5

999

--

--

999: Erase

SoftwareStatus

Status

Active

000-499

--

470-499

001: Active

Scrap#2, #6

500-699

500-599 (Restore)

570-599

501: Restore

600-699 (Scrap)

670-699

601: Scrap

Erase#5, #6

999

--

--

999: Erase

ContractStatus,

VolumeContractStatus

Status

Under contract

000-499

--

470-499

001: Under contract

Expired#7

500-998

--

570-998

501: Expire

Erase#5, #6

999

--

--

999: Erase

MaintenanceStatus

Status

Being handled

000-899

--

870-899

001: Wrong

002: Informed

003: Under

repair

Solved

900-999

--

970-999

901: Complete

MachineKind

Device type

Computing

100-199

--

170-198

100: PC

101: PC server

102: UNIX

103: UNIX server

150: Smart device

199: Other system device

Accessories

200-299

--

270-298

200: Monitor

201: Hard disk

202: CD-R

203: CD-R/W

204: DVD

205: DAT

206: MO

207: Printer

208: Peripheral device

209: USB device

210: Storage

Networking

300-399

--

370-398

300: HUB

301: Router

302: Network

printer

399: Network

device

ContractKind

Contract type

Maintenance

100-199

--

170-199

100: Maintenance

Lease

200-299

--

270-299

200: Lease

Rental

300-399

--

370-399

300: Rental

SoftwareKind

Software type

Software whose licenses are managed#8

100-199

--

170-199

100: Commercial

101: Shareware

Software whose licenses are not managed#9

200-499

--

470-499

200: Freeware

MaintenanceKind

Problem type

JP1 event

001

--

--

001: JP1 event

SNMP trap

002

--

--

002: SNMP

trap

User-registered

100-199

--

170-199

100: User registered

LicenseCategory

License category

Install license

100-199

--

170-199

100: Install license

User license

200-299

--

270-299

200: User license

Other

300-399

--

370-399

300: Other

Legend:

--: Not applicable

#1

This is subject to the same search and totaling processing as for the default statuses Active and Stock.

#2

When maintenance of the asset management database is executed by the Data maintenance task registered in Windows Task Scheduler, the associated network information (IP address only), installed software information, patch information, and virus definition information are deleted.

Additionally, the license key assigned to assets is released.

#3

When management information is obtained from the JP1/IT Desktop Management 2 - Manager, the information is updated regardless of the code value of AssetStatus.

#4

License totaling does not apply to devices whose device status is Scrap or Erase.

#5

This information is deleted if a maintenance operation is executed on the asset management database by the Data maintenance task registered in Windows Task Scheduler.

#6

This is not subject to search or totaling processing in the windows provided by default.

#7

The target device or software can no longer be added.

#8

This is subject to the same search and totaling processing as for the default types Commercial and Shareware.

#9

This is subject to the same search and totaling processing as for the default type Freeware.

16.8.5 Code IDs shared among multiple classes

Some code IDs are shared among multiple classes. Therefore, if you modify shared code information, the change is also effective for the classes that share the code.

The following table lists the code IDs that are shared among multiple classes.

Table 16‒4: Code IDs shared among multiple classes

Managed items

Shared code ID

Managed class

Property name

Contract (contract information) and ContractCatalog (company catalog)

UserPropertyCode_1

UserPropertyCode_2

ContractProperty1

ContractProperty2

HardwareInfo (hardware information) and MachineCatalog (device catalog)

CPUType

UserPropertyCode_1 to UserPropertyCode_12

MachineKind

ModelKind

MonitorKind

MonitorResolution

CPUType

HardwareProperty1 to HardwareProperty12

MachineKind

ModelKind

MonitorKind

MonitorResolution

16.8.6 Code information that cannot be added or deleted

For the following code IDs, the display value can be changed, but the code information cannot be added or deleted.

Table 16‒5: Code information that cannot be added or deleted

Managed class (managed class name)

Code ID (display name)

AssetInfo (asset information)

AssetKind (asset type)

AssetWorkKind (usage management)

DMStatus (ITDM2 Agent installed status)

Contract (contract information)

ContractObject (subject)

InstalledInfo (installed software information)

InventoryDelType (ITDM2 management information acquisition control)

InstalledList (installed software list)

InstalledInd (managed level)

Permit (permit)

InstalledUpdateRecord (software update log)

UpdateKind (update kind)

InstalledVirusDefInfo (virus definition information)

InventoryDelType (ITDM2 management information acquisition control)

ResidentKind (resident/nonresident)

LicenseAddUpRecord (license total log)

Permit (permit)

LicenseInfo (license information)

DownGrade (downgrade)

UpGrade (upgrade assurance)

Maintenance (maintenance log)

Importance (importance)

NetworkInfo (network information)

InventoryDelType (ITDM2 management information acquisition control)

IPAddressKind (IP address type)

PatchInfo (patch information)

InstalledStatus (applied status)

InventoryDelType (ITDM2 management information acquisition control)

TakeInventoryDef (ITDM2 management information)

InventoryUpType (update type)

UpdateRecord (device change log)

UpdateRecordInd (record indicator)

Others (codes not belonging to any of the above)

HardwareKind (hardware type)

JobKind (installation type)

RecordKind (managed information category)

RelationAsset (relationship)

SelectInstalledSoftwareType (software type)

SelectIPAddressAssign (IP address assignment)

SelectIPAddressType (usage)

UserOwnJobRole (official authority-based condition name)

16.9 Viewing and changing individual information (Individual Information)

By using the Individual Information job menu, you can display and edit information about a login user. You can view and edit such information as the password required for logging in to Asset Console, the user name, and the telephone number.

To view and edit individual information, use the Individual Information window, which is displayed by clicking the Individual Information job menu. The following figure shows the Individual Information window.

Figure 16‒26: Individual Information window

To change individual information, make sure that items with a star () are specified. To register the new information, click the Update button.

16.10 Changing asset information in a batch operation (Import)

By using the Import job menu, you can add, change, and delete asset information in a CSV file in a batch operation. By assigning items in a CSV file as Asset Console managed items, you can choose which items in the CSV file to change.

By default, only the administrator can execute importing.

To import asset information, click the Import job menu, which displays the Import window. The following figure shows the Import window.

Figure 16‒27: Import window

All registered conditions are displayed in a list. To filter the display, specify conditions for the search.

To import, begin by creating conditions, and then execute on the basis of the conditions. Sample import conditions are provided for each type of information. If you are importing previously exported data exactly as before or you are otherwise importing data using the default settings, you can import using sample conditions.

In addition to importing using the Import window, you can also import by executing jamCsvImport.bat or by using the jamimport command. For details about each execution method, see 9.1.1 Import flow.

16.10.1 Creating a CSV file to be imported

Create a CSV file to be imported, such as a CSV file output by another system or a CSV file containing exported data that has been edited.

For import processing, you specify a type of information (asset type), such as Device information or Software information. For details about the items that are imported for each category, see 20.4 Items to be imported or exported using a job menu.

For details about each item, see 20.2 Lists of properties for object classes.

(1) CSV file format

In a CSV file, the first line describes the item names in comma-separated format, and subsequent lines describe the item values.

Item names can be expressed as any character string. Make sure that each specified item name is unique in the CSV file because it is used for assignment with a managed item.

If there is more than one value for a particular information item assigned to the same asset, such as when multiple IP addresses are assigned to one PC, enter the information on separate lines, making sure that information items other than the information for which different values exist remain identical.

Important

If you open a CSV file with Microsoft Excel, the leading zeros are automatically deleted from numeric values, such as codes and IDs, and the contents of the file might be changed from the original information. Therefore, when you use Microsoft Excel, use the Import Text File function, set the column data format to Text, and then import and edit the file.

If a pair of double quotation marks (""), indicating a NULL string, is specified as a value in the CSV file, the pre-existing information in the asset management database is not updated. Note that data cannot be updated by the NULL value.

You must ensure that the number of columns in the CSV file header (first row) matches the number of columns in the data (subsequent rows).

Note

You can also omit the creation of an import condition by setting the item name in the CSV file to the same character string as the managed item. For a condition, specify the provided sample condition. The sample condition is created by the default settings for each category. Either create a condition according to the item name in the CSV file or edit the CSV file using the sample condition, whichever is suitable.

When you edit a CSV file, use the exported data in the following procedure for convenience:

From the Export job menu, select the same category as the information that you want to import, and then export the information using the default settings.

Set the item names in the output CSV file to the item names in the CSV file that is to be imported.

If you are not exporting, see 20.4 Items to be imported or exported using a job menu to match the item names.

(2) Items for which information managed in the asset management database has precedence

When you import information about group, user, role, and official authority, the corresponding Group name, User name, Role name, and Official authority name are registered from the group, user, role, and official authority information in the asset management database on the basis of the values of Group ID, User ID, Role ID, and Official authority ID specified in the CSV file.

If a combination of ID and name does not match the information in the asset management database, information in the asset management database with the matching ID takes precedence over the value in the CSV file.

(3) How to create CSV files

When you create conditions to update data in the asset management database using a CSV file that contains the values to be assigned to the existing data, you must set the correct assignment items.

This subsection describes how to create a CSV file to add or update data for each asset type. Notes about creating import conditions also apply to CSV file creation. When you create import conditions, also set each item according to the CSV file creation method.

How to create conditions for updating existing data

When you update existing data, you must create conditions, paying attention to the items that are assigned to data in the asset management database.

For assignment of data in the imported CSV file and existing data, the values of IDs, such as Asset ID and Group ID, take precedence, followed by the values that correspond to the IDs, such as Asset No. and Group name. Finally, if there is any English name, such as Group name (English), assignment is performed with the English name.

The following figure shows how existing data is updated by assigning data using an example of importing device information.

Figure 16‒28: Example of data assignment and updating during import of CSV files

This example assigns existing data with Asset ID:000001 and uses the value in the CSV file to update Asset No. to 000001.

The value of Group ID:11000000 in the CSV file is assigned to the group information, and Group name that corresponds to Group ID is updated to IT Management Dept.

As demonstrated in this example, if an item is managed by ID, and its ID and name do not match the values in the asset management database, the value in the asset management database that corresponds to that ID is updated.

(a) Device information

If you are updating existing information, make sure that you specify Asset ID or Asset No. Also for the condition, set the assigned item according to the specification in the CSV file. If both are set, Asset ID is used for assignment and Asset No. is updated by the value in the CSV file. If assignment is to be by Asset ID, specify only the new value in Asset No. You can omit any value that remains unchanged.

Information for groups, location, users, managed groups, and administrators is assigned to the corresponding information in the order ID and name. Therefore, if you are assigning existing information, you must specify only one of the values; you do not need to specify the values of all items. When the corresponding information is assigned by ID, the value for the name is updated by the assigned information.

If you are updating the network information, make sure that you specify Network info ID. To check the Network info ID of the information to be updated, export the network information.

If the IP address specified in IP address has not been registered in the asset management database during import operation, IP address is automatically created in the IP address control information. Note that the IP address control information items are not output by export operation.

(b) Installed software information

If you are updating existing information, make sure that you specify Asset ID or Asset No. Also for the condition, set the assigned item according to the specification in the CSV file. If both are set, Asset ID is used for assignment. If assignment is to be by Asset ID, you can omit Asset No.

If Installed software name, Installed software version, File name, File size, or File date that has been specified in the CSV file has not been registered in the installed software list, the value in the CSV file is added to the installed software list.

(c) Installed software list

If pre-existing information is updated, you must specify one of the following:

Installed software ID

Installed software name, Installed software version, File name, File size, and File date

Also for the condition, set the assigned item according to the specification in the CSV file. If both are specified, assignment is by Installed software ID, and Installed software name, Installed software version, File name, File size, and File date are changed by the values in the CSV file. If assignment is to be by Installed software ID, specify only the new values in Installed software name, Installed software version, File name, File size, and File date. You can omit any value that remains unchanged.

If you are specifying a software name, make sure that the specified name has been registered in the asset management database.

(d) Software information

If you are updating pre-existing information, you must specify one of the following:

Asset ID

Asset No. and Group name (or Group ID)

If you are updating software information, you cannot change Software list ID, Software name, Software type, License ID, or License name.

If you specify Group ID and User ID, you can omit Group name and User name.

If you are updating license information, make sure that you specify License ID. For an item with no assignment information, the license information is newly added.

If you are adding software information and also adding license information, make sure that you specify License name.

(e) Software list

If you are updating pre-existing information, you must specify one of the following:

Software list ID

Software name and Software type

Also for the condition, set the assigned item according to the specification in the CSV file. If both are specified, assignment is by Software list ID, and Software name is changed by the value in the CSV file. If assignment is to be by Software list ID, specify only the new value in Software name. You can omit any value that remains unchanged.

(f) Group information

If you are updating existing information, make sure that you specify Group ID. For the condition, set the assigned item according to the specification in the CSV file. If assignment is to be by Group ID, specify only the new value in Group name. You can omit any value that remains unchanged.

In Upper Group ID, you can set either ID or name. However, if the value set as the name matches an existing ID, the group with the matching ID is updated.

If the item cannot be assigned by the group ID set in Upper Group ID, or if null data has been set in Upper Group ID, the null data is set in Upper Group ID.

If a group is deleted, all groups and users under the deleted group are moved to Trash.

Note

If group information is to be deleted during import operation and a group in a higher hierarchy is specified in the CSV file, all the groups and users under that hierarchy are deleted. For example, in Figure 16-29, if a group in a higher hierarchy and its subordinate groups are specified, the information that is moved to the trash is also deleted during a single import operation. In such a case, not only the groups but also the users belonging to those groups are completely deleted and become unrecoverable.

The following figure shows an example in which the groups and users that belong to the deleted group are also deleted from the trash.

Figure 16‒29: Example in which the groups and users that belong to the deleted group are also deleted from the trash

Sales Department is deleted from the asset management database and its subordinate groups and users are moved to the trash.

Sales Division 1 and the users belonging to Sales Division 1 are deleted from the trash.

Sales Division 2 and the users belonging to Sales Division 2 are deleted from the trash.

(g) User information

If you are updating existing information, make sure that you specify User ID. For the condition, set the assigned item for User ID.

For the group to which the user belongs, specify either Group ID or Group name. If both are specified, the information associated with Group ID is assigned. If assignment is to be by Group ID, you can omit Group name.

For the role to which the user belongs, specify either Role ID or Role name. If both are specified, the information associated with Role ID is assigned. If assignment is to be by Role ID, you can omit Role name.

For the official authority to which the user belongs, specify either Official authority ID or Official authority name. If both are specified, the information associated with Official authority ID is assigned. If assignment is to be by Official authority ID, you can omit Official authority name. If assignment cannot be made by Role ID, new role information is added. If assignment is to be by Role name and the same role name has been registered more than once, the first one found in ascending order of Role ID is assigned.

Information about a user that does not belong to the group cannot be deleted. Additionally, group information cannot be updated for a user that does not belong to the group.

If User name (or User name (English)) has not been set, User ID of the user information is registered.

Deleting official authority only or updating official authority is not permitted.

When a new user is registered, a password is not set. Use a window operation to set a password.

(h) Location information

If you are updating existing information, make sure that you specify Location ID. For the condition, set the assigned item according to the specification in the CSV file. If assignment is to be by Location ID, specify only the new value in Location name. You can omit any value that remains unchanged.

In Upper location ID, you can set either ID or name. However, if the value set as the name matches an existing ID, the group with the matching ID is updated.

If the item cannot be assigned by the location ID set in Upper Location ID, or if null data has been set in Upper Location ID, the null data is set in Upper Location ID.

If you delete a location, the locations under the deleted location are moved to Trash.

(i) Maintenance contract information, Rental contract information, Lease contract information, Volume contract information

If you are adding contract information, make sure that you specify Contract No., Contract date, Contract start date, Contract end date, and Contracted company.

If you are updating existing information, make sure that you specify Contract ID or Contract No. For the condition, set the assigned item according to the specification in the CSV file. If assignment is to be by Contract ID, specify only the new value in Contract No. You can omit any value that remains unchanged.

Do not change Subject. When updating, set the value before the change.

You cannot release an asset that is subject to a contract. To release it, use a window operation.

Subject assets are assigned by Asset ID or Asset No. Only those assets that have been registered in the asset management database can be set as subject assets.

To register multiple assets for a single contract information item, set Contract ID on each line.

If the same asset number has been registered more than once, subject software cannot be assigned by Asset No.

Do not change Category.

Do not change the value of Frequency during an update operation.

If the group specified in Group ID is not registered in the asset management database, null data is set in Group ID.

(j) IP group information

When registering an IP group, the IP addresses in the range from the specified start address to end address are registered.

If you are updating existing information, make sure that you specify IP group ID or IP group name. For the condition, set the assigned item according to the specification in the CSV file. If both are specified, assignment is by IP group ID, and IP group name is changed by the value in the CSV file. If assignment is to be by IP group ID, specify only the new value in IP group name. You can omit any value that remains unchanged. If assignment is to be by IP Group name and multiple items having the same IP group name have been registered in the same tab of the IP Group job menu, information cannot be imported.

(k) Device catalog information

If you are adding information, make sure that you specify Device name and Model.

If you are updating pre-existing information, you must specify one of the following:

Catalog ID

Device name and Model

For the condition, set the assigned item according to the specification in the CSV file. If assignment is to be by Catalog ID, Device name is updated with the value in the CSV file.

(l) Problems

If you are adding information, make sure that you specify Overview of problem.

If you are updating existing information, make sure that you specify Maintenance log ID or Managed No. For the condition, set the assigned item according to the specification in the CSV file. If assignment is to be by Maintenance log ID, specify only the new value in Managed No. You can omit any value that remains unchanged.

If the erroneous asset cannot be assigned by Asset No., null data is set in Asset ID and Asset No.

(m) Assigned license information

If you are adding information, make sure that you specify Key ID for the software key information that is used for license assignment. If Key ID is not set, the information assigned by the software information Asset ID is used to register Product ID, License key, and Serial no.

If you are updating pre-existing information, make sure that you specify one of the following items for the software to which licenses are assigned:

Asset ID

Asset No. and Group name

For an installed license, specify Asset ID or Asset No. of the device to which the license is to be assigned in the hardware information Asset ID.

For a user license, specify User ID and User name of the user to which the license is to be assigned in the user information User ID and User name. If assignment is to be by User ID, you can omit User name.

As software key information to be used for assignment, specify Product ID, License key, and Serial no. If there is more than one software key information item that has the same three values, one of them is assigned.

For Asset ID, you can set either Asset ID or Asset No. If the value set as Asset No. matches an existing Asset ID, the software information having the matching Asset ID is assigned.

(n) Patches

If you are updating existing information, make sure that you specify Asset ID or Asset No. For the condition, set the assigned item according to the specification in the CSV file. If both are set, assignment is by Asset ID. If assignment is to be by Asset ID, you can omit Asset No.

(o) Virus definition

If you are updating existing information, make sure that you specify Asset ID or Asset No. For the condition as well, set the assigned item according to the specification in the CSV file. If both are set, assignment is by Asset ID. If assignment is to be by Asset ID, you can omit Asset No.

(p) Related asset information

If you are adding information, make sure that you specify one of the following:

Parent asset ID or Parent asset number

Child asset ID or Child asset number

For the condition as well, set the assigned items according to their specifications in the CSV file. If both Parent asset ID and Parent asset number (or both Child asset ID and Child asset number) are set, assignment is performed based on Parent asset ID (or Child asset ID). When assignment is performed based on Parent asset ID (or Child asset ID), you can omit Parent asset number (or Child asset number).

(q) Division information

If you are adding division information, make sure that you specify one of the following:

Division name and Group ID

Division name and Group

If you are also adding division groups, make sure that you specify Group ID or Group name.

For the condition as well, set the assigned items according to their specifications in the CSV file. Assignment is performed in the order shown above. If both are set and assignment was performed based on Division name and Group ID (item 1 above), assignment by Division name and Group (item 2 above) is not performed.

If you are adding division groups to division information, make sure that you specify one of the following, and then specify the Group ID or Group name setting of the division groups that are being added:

Division ID

Division name and Group ID (or Group)

For the condition as well, set the assigned items according to their specifications in the CSV file. Assignment is performed in the order shown above. If both are set and assignment was performed based on Division ID (item 1 above), assignment by Division name and Group ID (or Group) (item 2 above) is not performed.

If you are updating division information, make sure that you specify Division ID and Division name that is to be updated. The only information that can be updated is the Division name. Other items, even if specified, will not be changed. For the condition as well, set the assigned items according to their specifications in the CSV file. Assignment is performed based on Division ID.

If you are deleting division groups from division information, make sure that you specify one of the following and then specify Group ID or Group name of the division groups that are to be deleted:

Division ID

Division name and Group ID (or Group)

For the condition as well, set the assigned items according to their specifications in the CSV file. Assignment is in the order shown above. If both are set and assignment was performed based on Division ID (item 1 above), assignment by Division name and Group ID (or Group) (item 2 above) is not performed.

If you are deleting division information, make sure that you specify one of the following:

Division ID

Division name and Group ID (or Group)

Note that you should not specify Group ID or Group name. If you do, all corresponding division information and information assigned to divisions will be deleted.

For the condition as well, set the assigned items according to their specifications in the CSV file. Assignment is performed in the order shown above. If both are set and assignment was performed based on Division ID (item 1 above), assignment by Division name and Group ID (or Group) (item 2 above) is not performed.

(r) Division assignment

If you are adding division information, make sure that you specify one of the following:

Division name and Group ID

Division name and Group

If you are adding users that are assigned to division groups, make sure that you specify User ID or User name. Note that if there is already a user with the same name, make sure that you specify User ID.

For the condition as well, set the assigned items according to their specifications in the CSV file. Assignment is performed in the order shown above. If both are set and assignment was performed based on Division name and Group ID (item 1 above), assignment by Division name and Group (item 2 above) is not performed.

If you are adding users that are assigned to divisions, make sure that you specify one of the following and then specify the User ID or User name of the users that are to be added. Note that if there is already a user with the same name, make sure that you specify User ID.

Division ID

Division name and Group ID (or Group)

For the condition as well, set the assigned items according to their specifications in the CSV file. Assignment is performed in the order shown above. If both are set and assignment was performed based on Division ID (item 1 above), assignment by Division name and Group ID (or Group) (item 2 above) is not performed.

If you are updating division information, make sure that you specify the Division ID and Division name setting that is to be updated. The only information that can be updated is the Division name. Other items, even if specified, will not be changed. For the condition as well, set the assigned items according to their specifications in the CSV file. Assignment is performed based on Division ID.

If you are deleting users that were assigned to divisions, make sure that you specify one of the following and then specify the User ID or User name settings of the users that are to be deleted. Note that if there is already a user with the same name, make sure that you specify User ID. Note that if you do not specify User ID or User name, all of the corresponding division information and information assigned to divisions will be deleted.

Division ID

Division name and Group ID (or Group)

For the condition as well, set the assigned items according to their specifications in the CSV file. Assignment is performed in the order shown above. If both are set and assignment was performed based on Division ID (item 1 above), assignment by Division name and Group ID (or Group) (item 2 above) is not performed.

If you are deleting division information, make sure that you specify one of the following. Note that you should not specify User ID or User name. If you do, all corresponding division information and division assignment information will be deleted.

Corresponding Division ID

Corresponding Division name and Group ID (or Group)

For the condition as well, set the assigned items according to their specifications in the CSV file. Assignment is performed in the order shown above. If both are set and assignment was performed based on the corresponding Division ID setting (item 1 above), assignment by the corresponding Division name and Group ID (or Group) settings (item 2 above) is not performed.

16.10.2 Creating import conditions

To change asset information in a CSV file in a batch operation, create import conditions to specify the type of information and the items to be changed.

To create import conditions:

Click the Pattern button.

The Select Category dialog box is displayed.

Use Category to select the type of information you wish to import.

For details about the types of information that can be selected, see 16.10.2(1) Selecting the asset type below.

Click the OK button.

The Import window switches to a window for creating conditions.

Specify the CSV file to import.

For details about the CSV file format, see 16.10.1(1) CSV file format.

Select the processing mode.

Select Add, Update, Add/update, or Delete. For details about processing in each of these modes, see 16.10.2(2) Selecting the processing mode below.

Specify the assigned items.

Specify the assigned item for each managed item. Items identified by a star () are mandatory. For details about how to set assigned items, see 16.10.2(3) Setting assigned items below.

If an asset type with a customized relationship is selected, assigned items cannot be set. In such a case, skip this step and go to step 7.

To cancel, click the Close button.

Click the Add button.

The Save Condition dialog box is displayed.

Specify any name, and then click the OK button.

The import conditions are saved under the specified name.

The following figure shows the window for creating import conditions when Device information is selected for Category.

Figure 16‒30: Import window (for creating conditions)

(1) Selecting the asset type

Asset types that can be selected in Category are listed below. For details about the items to be imported in each asset type, see 20.4 Items to be imported or exported using a job menu.

Device information

Installed software information

Installed software list

Software information

Software list

Group information

User information

Location information

Maintenance contract information

Rental contract information

Lease contract information

Volume contract information

IP group information

Device catalog information

Problems

Assigned license information

Patches

Virus definition

Related asset information

Division information

Assign division

User definition (user report)#

User definition (form)#

Customize (Acquiring ITDM2 management information)#

User definition (import/export)#

User definition (item definition)#

User definition (contract history)#

#

Condition details cannot be specified for the customization information. Asset information exported to a CSV file from the Export window for backup purposes is used principally for restoring.

The version of customized information that has been exported can be determined from the first line of the CSV file.

Note

If you rename managed items using the Customize Managed Items job menu, the conditions provided in the sample become unusable. Therefore, create new import conditions.

(2) Selecting the processing mode

Select Add, Update, Add/update, or Delete as the processing mode. These processing modes are discussed as follows:

Add

New CSV file information is added. If an asset registered in the asset management database already exists and contains the same information and key as in the CSV file, the asset is not added.

Update

A search is made of the information registered in the asset management database for a match with the information in the CSV file. If a match is found, the asset information is changed. Note that Update cannot be selected when the asset type is Related asset information.

Add/update

A search is made of the information registered in the asset management database for a match with the information in the CSV file. If a match is found, the asset information is changed, otherwise it is registered as a new asset. Note that Add/update cannot be selected when the asset type is Related asset information, Division information, or Assign division.

Delete

A search is made of the information registered in the asset management database for a match with the information in the CSV file. If a match is found, the asset information is deleted. However, if any of the following is being used by other information, it is not deleted:

Installed software list

Software list

Group information

User information

Location information

(3) Setting assigned items

The items that are subject to import are displayed in the Managed items column. By clicking the Browse button and displaying the Setting Assignment dialog box, you can set the changes for the managed items that you wish to change.

If you click the Default button, information in the CSV file with the same name as the managed items is assigned automatically. If a previously exported CSV file is to be imported without change, this is convenient because the assigned items do not need to be set. The provided sample conditions are the same as those set by the Default button.

To cancel all settings of assigned items, click the Clear button.

The following figure shows how to set the items in the Setting Assignment dialog box.

Figure 16‒31: Setting Assignment dialog box

Do not set

Select this option to not use the import to change the value. This is selected by default for items that do not require setting.

CSV items

Select this option to assign the value from the CSV file, and specify in the input area the name of the item to be assigned.

Assigned items

Select the check box, and specify a default value for the item. For a coding format, select the default value from the drop-down list. If no value is set for the corresponding item in the CSV file, the default value specified here is set. Therefore, if CSV items is set for the managed item for codes with item names identified by a star (), a default value is mandatory.

Constant value

Select this option if the item is to be set to a constant value, regardless of the contents of the CSV file. Specify the constant value in the input area or select a constant value from the drop-down list.

Select the type of data.

Specify whether the values in the assigned CSV file are to be entered in code or display name form.

Notes

The following are the notes about setting assigned items:

When the Add or Add/update processing mode is selected, an automatically generated number is added for any ID that is part of the key other than User ID or Group ID, regardless of the value set for the assigned item.

Managed items displays the items that are set to be displayed in the Customize Managed Items job menu. An exception is that some of the items in Managed items are not displayed in Customize Managed Items. They are UpperLinkID (upper group ID) in GroupInfo (group information), UpperLinkID (upper location ID) in LocationInfo (location information), and CatalogID (catalog ID) in MachineCatalog (device catalog).

16.10.3 Executing imports

You specify conditions to execute import. You can use previously created conditions or you can use provided sample conditions.

To execute import:

Specify search conditions as appropriate, and then click the Search button.

A search is conducted for import conditions that match the search conditions.

Select the radio button for the name of the desired set of conditions, and then click the Execute button.

The window switches to a window for executing import.

On the Managed items column, those items that are subject to import under the specified conditions are displayed. You can change the assigned items if you wish. However, any contents specified here are not saved.

Click the Import button.

Import is executed.

If multiple values are set for an ID-assigned item, a warning message is displayed. For notes about setting ID-assigned items, see 16.10.2(3) Setting assigned items.

Notes

If you import the following information, take note of the importing order:

When registering Device information

When you want to set the group, location, and user for an asset, Group information, Location information, and User information must already be registered.

When registering User information

Group information must already be registered.

Importing a large volume of data can take a long time to process. If many data items are imported, a heavy load might be placed on the asset management server, which can have a detrimental effect on the performance of other programs running on the machine.

If you specify a customized asset type to import data, make sure that you are using the data that was exported by the same version of Asset Console.

If the items managed by the asset management database increase due to upgrading of Asset Console, the number of items that are imported and exported might also increase. As a result, the data exported using the sample conditions prior to upgrading might no longer be imported.

You can import and export Stocktaking date for software by specifying the Software information category from the Import or Export job menu. However, imported Stocktaking date for software cannot be used for other jobs. If you want to use information corresponding to Stocktaking date for software, use extended properties (user property data) for software information to manage the information separately.

(1) Settings of managed items when a value could not be assigned

Any value set to an assigned item that cannot be obtained during import is set automatically. The following table describes the items and the values that are set.

Asset type

Managed item

Set value

Device information

Asset information.Asset No.

Asset ID

Asset information.Usage management

Used

Asset information.Status

Stock

Asset information.Reg.date

Import date

Asset information.ITDM2 Agent installed status

Not installed

Hardware information.Device type

PC

Network information.ITDM2 management information acquisition control

Do not delete when there is no corresponding information in the ITDM2 management information.

Installed software information

Installed software information.ITDM2 management information acquisition control

Do not delete when there is no corresponding information in the ITDM2 management information.

Installed software list

Installed software list.Permission

Permit

Installed software list.Type

Normally

Installed software list.Management level

Managed object

Software information

Asset information.Asset No.

Asset ID

Asset information.Usage management

Used

Asset information.Software status

Active

Asset information.Reg.date

Import date

Software list.Software type

Commercial

License information.License type

Install license

License information.Upgrade assurance

Yes

License information.Downgrade

Enable

License information.Licensing method

Package

License information.License category

Install license

Software list

Software list.Software type

Commercial

Group information

Group information.Group name (English)

Group ID

User information

User information.User name

User ID

User information.User name (English)

User ID

Role information.Role name

Role ID

Location information

Location information.Location name (English)

Location ID

Location information.Attribute

Region

Maintenance contract information

Contract information.Category

Maintenance

Contract information.Subject

Device

Contract information.Status

Under contract

Rental contract information

Contract information.Category

Rental

Contract information.Subject

Device

Contract information.Status

Under contract

Lease contract information

Contract information.Category

Lease

Contract information.Subject

Device

Contract information.Status

Under contract

Volume contract information

Volume contract information.Status

Under contract

Device catalog information

Device catalog.Device type

PC

Problems

Maintenance log.Status

Wrong

Maintenance log.Reg. date

Import date

Maintenance log.Registrar

Login user name (for command execution, the asset administrator name)

Maintenance log.importance

Emergency

Maintenance log.Problem type

User Registered

Patch information

Patch information.Applied status

Apply

Patch information.ITDM2 management information acquisition control

Do not delete when there is no corresponding information in the ITDM2 management information.

Virus definition information

Virus definition.ITDM2 management information acquisition control

Do not delete when there is no corresponding information in the ITDM2 management information.

Import processing results in an error if no assigned item has been set for the managed item of the following asset type, or if value acquisition fails:

Maintenance contract information, Rental contract information, Lease contract information

Contract information.Contract No., Contract information.Contract date, Contract information.Start date, Contract information.End date, Contract information.Contracted company

Volume contract information

Volume contract information.Contract No.

Device catalog

Device catalog.Name, Device catalog.Model

Problems

Maintenance log.Overview of problem

16.10.4 Deleting import conditions

To delete conditions that are no longer needed:

Specify search conditions as appropriate, and then click the Search button.

A search is conducted for import conditions that match the search conditions.

Select the radio button for the name of the set of conditions that you wish to delete, and then click the Delete button.

The selected set of conditions is deleted.

16.11 Exporting asset information in CSV format (Export)

By using the Export job menu, you can output asset information in the asset management database in CSV format. By selecting the type of information and the managed items that you wish to output, you can output any items in a batch operation.

By default, only the administrator can export asset information.

Export of asset management information is executed by clicking the Export job menu to display the Export window. The following figure shows the Export window.

Figure 16‒32: Export window

All registered conditions are displayed in a list. To filter the display, specify search conditions and then search.

To export asset information, begin by creating conditions, and then execute on the basis of the conditions. Sample export conditions are provided for each type of information. If you use any of the samples, all data is output. CSV files output using the samples can be imported in the same format by using sample conditions available with the Import job menu.

In addition to exporting using the Export window, you can also export by executing jamCsvExport.bat or by using the jamexport command. For details about the differences in their execution methods, see 5.2.2 Collecting from CSV files.

16.11.1 Creating export conditions

To output asset information in the asset management database in CSV format, create export conditions by specifying the items and type of information to be output.

To create export conditions:

Click the Pattern button.

The Select Category dialog box is displayed.

Use Category to select the type of information you wish to export.

For details about the types of information that can be selected, see 16.10.2(1) Selecting the asset type.

Click the OK button.

The Export window switches to a window for creating conditions.

Select Data type.

Select whether information managed by a code is to be output by the display name or by the code.

If you select a customized asset type, skip to step 7.

From Enable items to export, select the items to be output, and then click the Export button.

The selected items are added to Export items.

Use the Up and Down buttons to set the sequence of Export items.

Set the order for output to the CSV file.

Click the OK button.

The Save Conditions dialog box is displayed.

To cancel, click the Close button.

Specify any name, and then click the OK button.

The export conditions are saved under the specified name.

The following figure shows the window for creating export conditions when Device information is selected as the Category.

Figure 16‒33: Export window (for creating conditions)

16.11.2 Executing an export operation

An export operation is executed by specifying conditions. These export conditions must have already been created.

To specify conditions and execute an export operation:

Specify search conditions as appropriate, and then click the Search button.

A search is conducted for export conditions that match the search conditions.

Select the radio button for the name of the desired set of conditions, and then click the Execute button.

The window switches to a window for executing the export operation.

Filter the conditions if necessary.

To filter the output items, use the Set Condition dialog box that is displayed by clicking the Filter link.

The Filter Condition items differ depending on the selected asset type.

For details about specifications of the Set Conditions dialog box, see 16.11.2(1) Setting filtering conditions below.

Click the Export button.

Export is executed.

(1) Setting filtering conditions

When output items specified in Export items are to be filtered, such as by the managing group, for example, filtering conditions are set. To filter the conditions, click the link under Filter to display the Set Condition dialog box.

The following figure shows how to specify conditions in the Set Condition dialog box.

Figure 16‒34: Set Condition dialog box

The items that can be specified as filtering conditions are displayed in a list. For example, in order to output only the information for a particular group, specify the group name.

The specified conditions become enabled when you click the OK button.

If you click the Close button before you click the OK button, the specified conditions are cleared. Therefore, if you adjust the filter conditions while checking them, you must export them so they are displayed in the dialog box.

(2) Format of output CSV files

The following figure shows the format of a CSV file output by exporting.

Figure 16‒35: Format of CSV file output by exporting

If there are multiple pieces of information for the same asset, such as when multiple IP addresses are allocated to one PC, multiple lines are output.

Even if output contents overlap due to the limitation of output items, overlapping lines are not deleted.

Suppose that when you process an output CSV file to edit it to be registered in Asset Console, you use Microsoft Excel to open the CSV file. In such a case, the leading zeros are automatically deleted from numeric values, such as codes and IDs, and the contents of the file might be changed from the original information. Therefore, if you use Microsoft Excel, use the Import Text File function, set the column data format to Text, and then import and edit the file.

16.11.3 Deleting export conditions

To delete conditions that are no longer needed:

Specify search conditions as appropriate, and then click the Search button.

A search is conducted for export conditions that match the search conditions.

Select the radio button for the name of the set of conditions that you wish to delete, and then click the Delete button.

The selected set of conditions is deleted.

16.12 Checking the import results (Result Import)

By using the Result Import job menu, you can check the results of imports executed from the Import job menu. You can also interrupt import processing while it is executing.

By default, only the administrator can obtain an import results list.

You check import results by clicking the Result Import job menu to display the Result Import window. The following figure shows the Result Import window.

Figure 16‒36: Result Import window

Specify conditions for the import results that you wish to check, and then search.

16.12.1 Checking details of import results

Clicking the link under Execution status in the search results displays the Details of Import Result dialog box shown below. In this dialog box, you can check the details and status of import results.

Figure 16‒37: Details of Import Result dialog box

If an error occurs during import processing from the Import job menu, that line is skipped and processing continues. However, if the same error occurs 10 times in succession or if an unexpected error occurs, processing terminates abnormally.

16.12.2 Interrupting import processing

To forcibly terminate import processing:

Specify search conditions as appropriate, and then search the import results.

A search is conducted for import results that match the search conditions, and the retrieved results are displayed in a list.

Select the check box of the import results whose processing you wish to interrupt, and then click the Stop button.

The selected import processing is interrupted.

Interrupt processing is executed every 50 items. Therefore, if fewer than 50 items remain when the Stop button is clicked, the interrupt does not take effect before completion.

16.12.3 Deleting execution results

To delete import results that are no longer needed:

Specify search conditions as appropriate, and then click the Search button.

A search is conducted for import results that match the search conditions.

Select the check box of the name of the set of conditions that you wish to delete, and then click the Delete button.

The selected set of conditions is deleted.

If import using the selected set of conditions is executing, a message that deletion could not be performed is displayed and deletion processing is canceled.

16.13 Viewing log information (Log)

By using the Log job menu, you can view error information, and various logs of information about JP1/IT Desktop Management 2 - Manager imported to the asset management database. This information might include, for example, the start and end of tasks registered in Windows Task Scheduler, or the number of information items imported to the asset management database. Even in an environment where direct manipulation of the asset management server is impossible, you can still check the status of information acquired from JP1/IT Desktop Management 2 - Manager, and check error details.

By default, only the administrator can browse the log.

To browse the log, click the Log job menu to display the Log window. The following figure shows the Log window.

Figure 16‒38: Log window

Clicking the INV folder link displays the link to the log file (ASTINVn.log). Clicking the log file name link displays the contents of the log file (message output time, message type, and message text).

How to interpret the file name

n in ASTINVn.log indicates a file name sequence number, in the range from 1 to 9.

When the maximum amount of log data permitted per file is exceeded, a new log file with the number incremented by 1 is created. If number 9 is used, it is reset to 1. You can identify the most recent log file by the file attributes (date and time).

The Log window displays the folders and files that are stored in asset-management-server's-virtual-directory\log. If you attempt to move to the asset management server's higher-level virtual directory, a message stating that the request window cannot be accessed due to lack of permissions is displayed. By default, the asset management server's virtual directory is Asset-Console-installation-folder/wwwroot.

16.13.1 Checking the acquisition of management information

When you click the INV link, the log file (ASTINVn.log) is displayed. You can use this file to check information, such as the number of management information items in JP1/IT Desktop Management 2 - Manager that are imported to the asset management database.

16.14 Setting assigned items (ITDM2 Management Information Acquisition)

When management information collected by JP1/IT Desktop Management 2 - Manager is imported into the asset management database, this job enables you to relate Asset Console's managed items and JP1/IT Desktop Management 2 - Manager's management items. It also enables you to specify the default values for status and type when management information is imported. For details about the type of management information that is assigned to Asset Console's managed items and the information that is acquired, see 19.1 Management information that can be acquired from JP1/IT Desktop Management 2 - Manager.

To set the items to be assigned, start from the ITDM2 Management Information Acquisition window, which is displayed by clicking the ITDM2 Management Information Acquisition job menu. The following figure shows the ITDM2 Management Information Acquisition window.

Figure 16‒39: ITDM2 Management Information Acquisition window

This window lists Asset Console's managed items and the items that are assigned to them. Managed items lists in the format class-name.property-name the items that have been set to be displayed by Customize Managed Items.

To set an assigned item, click the Browse button for the corresponding managed item.

16.14.1 Setting an assigned item for asset numbers

This subsection describes how to set the asset number of new asset information when JP1/IT Desktop Management 2 - Manager's management information is imported.

To set an assigned item for asset numbers, use the Assigned item dialog box, which is displayed by clicking the Browse button for Asset information.Asset No. in the ITDM2 Management Information Acquisition window.

Figure 16‒40: Assigned item dialog box

In the Assigned item dialog box, select an assigned item.

Auto (default)

Sets a number assigned automatically by the asset management system as the asset number.

Device information

Selects an item to be assigned to the asset number from JP1/IT Desktop Management 2 - Manager's device information. The item selected from the drop-down list is set as the asset number.

System information and hardware information

Selects an item to be assigned to the asset number from JP1/IT Desktop Management 2 - Manager's system information and hardware information. The item selected from the drop-down list is set as the asset number.

Custom field

When you specify a JP1/IT Desktop Management 2 - Manager's custom field, management information is obtained and set as the asset number. If the corresponding item name does not exist, nothing is set.

Set the update method for the value selected to the item to be assigned to Overwrite setting.

Overwrite (default)

Even if a value is already registered in the asset management database, it is overwritten by the value in the collected ITDM2 management information. If the applicable value in the collected ITDM2 management information is NULL or N/A, it is overwritten by the automatically assigned value (asset ID). However, no value is registered if Asset No. is selected for Assignment method of Action settings in the ITDM2 Management Information Acquisition window.

Overwrite (Do not overwrite when there is no data.)

Even if a value is already registered in the asset management database, it is overwritten with the value in the collected ITDM2 management information. However, if the applicable value in the collected ITDM2 management information is NULL or N/A, it is not overwritten.

Not overwritten

If a value is already registered in the asset management database, it is not overwritten.

16.14.2 Setting an assigned item for user names

If user names are managed in JP1/IT Desktop Management 2 - Manager's system information and hardware information, custom field information, or common field information, you can register that information in the asset management database.

Because the user name is registered as User name of hardware assets acquired from the ITDM2 management information, you can save the time for registering the user for each asset.

This subsection describes the registered information that depends on the assigned item when information collected from JP1/IT Desktop Management 2 - Manager's common field information is registered as the user name in asset information. The procedure for setting an assigned item for user names is also explained.

(1) Difference in registered information when items are assigned from the common field information

To register the common field information as asset information User name, select one of the three common field items to assign to the asset information:

E-mail

User name

Account

The selected item is assigned to the corresponding user information, and User name, User ID, and User name (English) are registered in the asset information.

The following table describes the correspondence between the item selected as the assigned item and the actual information that is registered when common field information is assigned to asset information.

Table 16‒6: Correspondence between the item selected as the assigned item and the actual information that is registered

Assigned item

Search item

(User information)

Item to be registered

(Asset information)

Information that is registered

Corresponding value exists in the user information

No corresponding value exists in the user information

E-mail

E-mail

User name

User name

E-mail

User name (English)

User name (English)

--

User ID

User ID

--

User name

User name

User name

User name

User name

User name (English)

User name (English)

--

User ID

User ID

--

Account

(No search item)

User name

(No applicable case)

Account

Legend:

--: Not registered

(2) Setting an assigned item for user names

To set an assigned item for user names, use the Assigned item dialog box, which is displayed by clicking the Browse button for Asset information.User name in the ITDM2 Management Information Acquisition window.

Figure 16‒41: Assigned item dialog box

From the items displayed in the Assigned item dialog box, select the key item to be used to identify the user name:

Do not set

Does not register a user name when JP1/IT Desktop Management 2 - Manager's management information is registered.

Common Fields (default)

Selects an item to be assigned to the user name from JP1/IT Desktop Management 2 - Manager's common field information. The default value is User Name.

Information to be registered as the user name varies depending on the item selected from the drop-down list. For details about information to be registered as the user name, see Table 16-6.

System information and hardware information

Selects an item to be assigned to the user name from JP1/IT Desktop Management 2 - Manager's system information and hardware information. The item selected from the drop-down list is set as the user name.

Custom field

When you specify a JP1/IT Desktop Management 2 - Manager's custom field, management information is obtained and set as the user name. If the corresponding item name does not exist, nothing is set.

Set the update method for the value selected to the item to be assigned to Overwrite setting.

Overwrite (default)

A value (even if already registered in the asset management database) is overwritten by the value in the collected ITDM2 management information. If the applicable value in the collected ITDM2 management information is NULL or N/A, the registered value is deleted.

Overwrite (Do not overwrite when there is no data.)

A value (even if already registered in the asset management database) is overwritten by the value in the collected ITDM2 management information. However, if the applicable value in the collected ITDM2 management information is NULL or N/A, it is not overwritten.

Not overwritten

If a value is already registered in the asset management database, it is not overwritten.

16.14.3 Setting assigned items for group and location

If group and location are managed in JP1/IT Desktop Management 2 - Manager's common field information, you can register that information in the asset management database.

Group and location names are registered as group and location information with the tree structure as well as the asset information. This enables you to save the time for registering group and location names and maintain conformity with the information managed by JP1/IT Desktop Management 2 - Manager.

This subsection describes the registered information that depends on the assigned item when JP1/IT Desktop Management 2 - Manager's common field information is registered as the asset information Group name and Location.

Note

You can also register group names and locations according to the IP groups to which the IP addresses collected as the JP1/IT Desktop Management 2 - Manager management information belongs. By also using the setting for registering according to IP groups, you can register group names and locations of assets not assigned in the JP1/IT Desktop Management 2 - Manager common field information, according to IP groups. For details about how to register group names and locations according to IP groups, see 7.3.4(11) Settings for a group that uses a group-specific IP group and 7.3.4(12) Settings for a location that uses a location-specific IP group.

(1) Difference in registered information depending on the assigned item settings for the group name

To register group names using JP1/IT Desktop Management 2 - Manager's common field information, select either the group information or user name in the common field information as the assigned item.

If you use the group information in the common field information as the assigned item, also specify whether provision is to be made to register new groups that are not in Asset Console.

When using the user name in the common field information as the assigned item

The user name in the common field information is assigned to the user information. If the corresponding user has been registered, that user's group is registered in the asset information Group name.

If the corresponding user has not been registered in the user information, that user is not registered.

This setting enables you to use Asset Console's group information even when the group information is managed by JP1/IT Desktop Management 2 - Manager.

When using the group information in common field information as the assigned item and registering new groups

The group name acquired from the common field information is converted to the representation used by Asset Console according to JP1/IT Desktop Management 2 - Manager's hierarchy. The resulting value is then assigned to the group information and the corresponding group is registered in the asset information Group name.

If there is no corresponding group, a new group is added to the group information, and the information about the added group is registered in the asset information Group name.

When using the group information in common field information as the assigned item and not registering new groups

The group name acquired from the common field information is converted to the representation used by Asset Console according to JP1/IT Desktop Management 2 - Manager's hierarchy. The resulting value is then assigned to the group information, and the corresponding group is registered in the asset information Group name.

If there is no corresponding group, no group is registered.

The following figure shows an example of using the user name in the common field information as the assigned item.

Figure 16‒42: Example of assignment to asset information when the user name is used as the assigned item

The following figure shows an example of registering new groups using the group information in the common field information as the assigned item.

Figure 16‒43: Example of assignment to asset information when the group information is used as the assigned item

(2) Setting an assigned item for groups

To set an assigned item for groups, use the Assigned item dialog box, which is displayed by clicking the Browse button for Group information.Group name in the ITDM2 Management Information Acquisition window.

Figure 16‒44: Assigned item dialog box

From the items displayed in the Assigned item dialog box, select an assigned item:

Do not set (default)

A group name is not registered from the common field information.

If the setting is used in which group names are registered using Group-Specific IP Group, group names specific to IP groups are registered.

IP address group

Assigns a group from the IP address group that contains the IP address, and registers that group. If there is no corresponding IP address group, no group is registered.

User's department

If a user that is managed by Asset Console is assigned to the user name, the group to which that user belongs is assigned and registered.

Common fields

JP1/IT Desktop Management 2 - Manager's management information is assigned to the common field information and the group is registered. Select an item from the drop-down list.

If the Register new information check box is selected and there is no corresponding group in the group information of JP1/IT Desktop Management 2 - Asset Console's management information, a new group is registered.

Set the update method for the value selected to the item to be assigned to Overwrite setting.

Overwrite (default)

A value (even if already registered in the asset management database) is overwritten by the collected value. If the collected value is NULL or N/A, the registered value is deleted.

Overwrite (Do not overwrite when there is no data.)

A value (even if already registered in the asset management database) is overwritten by the collected value. However, if the collected value is NULL or N/A, it is not overwritten.

Not overwritten

If a value is already registered in the asset management database, it is not overwritten.

(3) Setting an assigned item for locations

To set an assigned item for locations, use the Assigned item dialog box, which is displayed by clicking the Browse button for Location information.Location name in the ITDM2 Management Information Acquisition window.

Figure 16‒45: Assigned item dialog box

From the items displayed in the Assigned item dialog box, select an assigned item:

Do not set (default)

A location is not registered from the common field information.

If the setting is used in which locations are registered using Location-Specific IP Group, locations specific to IP groups are registered.

IP address group

Assigns a location from the IP address group that contains the IP address, and registers that location. If there is no corresponding IP address group, no location is registered.

Common fields

JP1/IT Desktop Management 2 - Manager's management information is assigned to the common field information, and the location is registered. Select an item from the drop-down list.

If the Register new information check box is selected and there is no corresponding location in the location information of JP1/IT Desktop Management 2 - Asset Console's management information, a new location is registered.

Set the update method for the value selected to the item to be assigned to Overwrite setting.

Overwrite (default)

A value (even if already registered in the asset management database) is overwritten by the collected value. If the collected value is NULL or N/A, the registered value is deleted.

Overwrite (Do not overwrite when there is no data.)

A value (even if already registered in the asset management database) is overwritten by the collected value. However, if the collected value is NULL or N/A, it is not overwritten.

Not overwritten

If a value is already registered in the asset management database, it is not overwritten.

Note

The Attribute of newly added location information is always Area. After registering the information, you can use the Location window to change it as appropriate to the actual location.

For details about using the Location window, see 16.3 Changing information about asset locations (Location).

16.14.4 Setting assigned items for device types

To set an assigned item for device types, use the Assigned item dialog box, which is displayed by clicking the Browse button for Hardware information.Device type in the ITDM2 Management Information Acquisition window.

Figure 16‒46: Assigned item dialog box

Select an assigned item from among the following items displayed in the Assigned item dialog box:

Constant value

Select this item when you want to register an item with a fixed value. Select an item from the drop-down list.

Device information (default)

JP1/IT Desktop Management 2 - Manager's management information (device type) is assigned to the device information and set as the device type.

Custom field

When you specify a JP1/IT Desktop Management 2 - Manager's custom field, management information is obtained and set as the device type. If the corresponding item name does not exist, nothing is set.

Set the update method for the value selected to the item to be assigned to Overwrite setting.

Overwrite (default)

A value (even if already registered in the asset management database) is overwritten by the value in the collected ITDM2 management information. If the applicable value in the collected ITDM2 management information is NULL or N/A, the registered value is deleted.

This option is not displayed for an item that requires settings.

Overwrite (Do not overwrite when there is no data.)

A value (even if already registered in the asset management database) is overwritten by the value in the collected ITDM2 management information. However, if the applicable value in the collected ITDM2 management information is NULL or N/A, it is not overwritten.

This option becomes the default for an item that requires settings.

Not overwritten

If a value is already registered in the asset management database, it is not overwritten.

16.14.5 Adding items to be acquired from ITDM2 management information

This subsection describes how to set assigned items based on an example of adding the System information and hardware information BIOS version to the managed items for asset information.

To set assigned items:

In the ITDM2 Management Information Acquisition window, which is displayed by selecting the ITDM2 management information acquisition job menu, click the Browse button for Asset information.User property field 128-1.

The Assigned item dialog box appears.

This dialog box displays the items that are assigned to Asset Console's managed items. The items displayed depends on the managed items.

Do not set

Select this option to not assign items acquired from the ITDM2 management information.

Constant value

Select this item when you want to register an item with a fixed value. Select an item from the drop-down list.

Device information

Select this option to register a device information item. Select an item from the drop-down list.

Common Fields

JP1/IT Desktop Management 2 - Manager's management information is assigned to the common field information. Select an item from the drop-down list.

System information and hardware information

Select this option to register a system information and hardware information item and then specify the name of the system information and hardware information item.

Custom field

When you specify a JP1/IT Desktop Management 2 - Manager's custom field, management information is obtained. If the corresponding item name does not exist, nothing is set.

From the items displayed in Assigned items, select System Information and Hardware Information.

From the drop-down list, select BIOS version.

Click the OK button.

The Assigned item dialog box closes, and BIOS version is set in the Assigned items field.

Click the Set button.

The assignment settings take effect.

To view the added information in the window, you must specify applicable settings with Customize Managed Items and Customize Job Windows.

For details about adding the asset information User property field 128-1 to managed items and renaming it, see 11.2 Changing managed items (Customize Managed Items).

For details about the changes to the window that are required in order to view information about the added managed items, see 11.3 Changing a window for a user role (Customize Job Windows).

To add items acquired from ITDM2 management information to user property code

To add the items to be assigned to User property code-1 through User property code-12, add the codes to be assigned to the corresponding class property beforehand. If a code to be assigned is undefined, Code is displayed in inactive mode in the Assigned item dialog box.

For details about adding codes, see 16.8.1 Adding codes.

When ITDM2 management information is registered, if no code corresponds to information acquired from JP1/IT Desktop Management 2 - Manager, null is set. In such a case, any existing information is overwritten.

16.14.6 Changing a default value when ITDM2 management information is registered

This subsection describes the procedure for setting assigned items using an example of changing the default value for Status from Permit to Do not permit in the installed software list.

Changing the Status setting to Do not permit enables email notification to be sent to the asset manager when JP1/IT Desktop Management 2 - Manager's management information contains a software name that has not been registered in Asset Console.

To set assigned items:

In the ITDM2 Management Information Acquisition window, click the Browse button for Installed software list.Permission.

The Assigned item dialog box appears.

Confirm that Constant Value is selected in Assigned items, and then select Do not permit from the drop-down list.

Click the OK button.

The Assigned item dialog box closes, and Do not permit is specified in the Assigned items field.

Click the Set button.

The assignment settings take effect.

To send email notification of unauthorized software installation, you must enable the Notification of unauthorized install task. For details about the tasks, see 7.9 Setting the tasks that are registered in Task Scheduler.

You can change the registered status in the Installed Software window. For details about how to change the setting for whether to permit installation, see 16.7.2 Changing the installed software information.

Part 6: Troubleshooting

17 Troubleshooting

This chapter describes the procedures for handling errors in the asset management system.

17.1 Troubleshooting procedure

This section describes the procedure for handling errors in the asset management system. For details about the principal causes of errors and how to handle them, see sections 17.5 through 17.10.

The following figure shows the recovery procedure starting from the point of error occurrence.

Figure 17‒1: Error handling procedure

Acquiring error information

In the event of an error, first obtain error information. For details about how to acquire error information, see 17.2 Acquiring error information.

Identifying the cause of the error

Identify the cause of the error on the basis of the error message and events.

Eliminating the cause of the error

If it is possible to handle the error, eliminate the cause of the error.

Handling the error by system administrator

If the error cannot be corrected, the system administrator eliminates the cause of the error.

Executing error recovery

Execute error recovery processing, if necessary.

Before handling an error, make sure that no other processing is under execution. For details about transaction processing in the asset management system, see 17.4 Transactions in the asset management system.

17.2 Acquiring error information

For troubleshooting information, view the log file located under Asset-Console-installation-folder\log.

When you contact Hitachi regarding an error in Asset Console, execute the batch file provided with the product and provide the error information collected by the batch operation.

The procedure for executing the batch file to collect error information is described below. Obtain the error information on the machine where the asset management server is running. When executing an Asset Console command, you must execute it using the 32-bit command prompt. For the execution procedure, see Appendix G. Notes on Executing Asset Console Commands and Tasks.

Log in to the asset management server as a user with administrator permissions.

Execute ASTTRBL.BAT.

ASTTRBL.BAT is stored in the following folder:

Asset-Console-installation-folder\exe

The error information available at that point is output to the specified destination folder.

Format of the error information acquisition batch file (ASTTRBL.BAT)

The format of ASTTRBL.BAT is as follows:

ASTTRBL.BAT "output-destination-folder-name"

output-destination-folder-name

Specifies the full or relative path of the folder to which the acquired error information is to be output. Specification of an output destination folder name is mandatory.

Important

Asset-Console-installation-folder\log folder cannot be specified as the output-destination folder.

17.3 Identifying the error cause

This section describes how to identify the cause of an error.

To determine how to handle an error, you need to identify the cause of the error on the basis of the error message and events. This section explains how to identify and interpret messages. It also explains the functions that become restricted when an error occurs in the asset management system.

17.3.1 How to identify the cause of an error

This section explains how to check errors on the asset management server and with a Web browser.

(1) How to identify an error at the asset management server

Check the message log file for error messages.

If an error message has been issued, identify the nature of the error, which will be one of the following:

Error in the asset management database

Error in a program that is linked to Asset Console

Error in Microsoft Internet Information Services

For an access error in the asset management database, check the message log.

For an error in a program that is linked to Asset Console, check the message log file for a program linkage error.

For an error in Microsoft Internet Information Services, check the log of Microsoft Internet Information Services for a communication sequence error.

If there is no error in the communication sequence, an error might have occurred between Microsoft Internet Information Services and the Web browser.

(2) How to identify an error in the Web browser

If a runtime error occurs, an unsupported version of Windows Internet Explorer might be running. Make sure that a supported version of Windows Internet Explorer and all required service packs have been installed. For details about Windows Internet Explorer versions, see 6.1.1(2) Prerequisite programs on the administrator's computer.

17.3.2 Checking messages

In the event of an error, first check the event log, standard output, or the log file created by the asset management server for error messages.

When an error message has been issued, you can identify the program in which the error occurred and the cause of the error from the error message type. For details about error messages, see 17.3.3 How to interpret messages.

The error messages for serious errors in the asset management system are output to the event log file. Check the event log file.

The asset management server outputs error messages to a file. This file is stored at the following location:

Asset-Console-installation-folder\log

The log folder is created automatically when Asset Console is installed. The following table shows the message log files that are output under the log folder by the asset management server.

Table 17‒1: Files created in the log folder

File name

Description

ASTCIMn.LOG

Contains the message log of a database access API.

ASTMESn.LOG

Contains information messages, such as startup and termination of the asset management server, warning messages (such as program, communication, and database errors), and error messages.

Can be used to check the operating status of the asset management system.

Legend:

n is a sequential number (1-9) indicating a file name.

When the current file becomes filled with log data, another log file is created by incrementing the number by 1. When the number reaches 9, it starts at 1 again. To identify the most recent log file, check the file attributes (date and time).

Do not change Asset-Console-installation-folder\log\expdef.

17.3.3 How to interpret messages

This section explains how to interpret the messages that are output to the standard output message log, and to message log files.

(1) How to interpret a standard output message log entry

The message log that is output by the asset management server consists of a message ID and message text that follows.

Message format

KDAM nnnn-m message-text

KDAM

Indicates that the message was issued by the asset management server.

nnnn

Indicates the component code that issued the message (the first n) + a serial number. The following are the component codes:

7: Command

8: Import and export

m

Indicates the type of message:

E (ERROR)

Fatal error that required termination of the program

W (WARNING)

Error that does not require program termination, but that disables some functions

Q (QUESTION)

Message that requires a response from the user

K (WORKING)

Message that processing is in progress

I (INFORMATION)

Message providing information

(2) How to interpret a message log file

The message log file that is output by the asset management server consists of a message output time, a message ID, and message text that follows.

Message format

yyyymmddhhmmss.ttt pid(tid) KDAM nnnn-m message-text

yyyymmddhhmmss.ttt

Indicates the message output date and time.

pid

Indicates the ID of the process that issued the message.

tid

Indicates the ID of the thread that issued the message.

KDAM

Indicates that the message was issued by the asset management server.

nnnn

Indicates the component code that issued the message (the first n) + a serial number. The following are the component codes:

0: Installation and setup

1: Asset management server

2, 3: Extension

4, 5: Database access DLL

6: Asset Console's LIB and DLL files

7: Command

8: Import and export

9: Common DLL

m

Indicates the type of message:

E (ERROR)

Fatal error that required termination of the program

W (WARNING)

Error that does not require program termination, but that disables some functions

Q (QUESTION)

Message that requires a response from the user

K (WORKING)

Message that processing is in progress

I (INFORMATION)

Message providing information

17.3.4 Function restrictions after an error

When an error occurs in the asset management system, the asset management server issues a message of type E. The functions of the asset management system that become restricted by errors are explained below.

(1) When urgent or serious system errors occur

If an urgent or serious system error occurs from which recovery is not possible or which might corrupt information if operations are continued, all services of the asset management system are stopped.

Urgent or serious system errors are as follows:

Invalid settings or read errors in the environment definition file

Detection of damaged meta table

Program exceptions, such as a general protection exception

Internal program errors

(2) When system errors that are not urgent or serious occur

A system error that is not urgent or serious might occur from which recovery is possible over time and which will not corrupt information. When such an error occurs, even if operations continue, the process in which the error was detected will be terminated.

System errors that are not urgent or serious are as follows:

Invalid format of messages from Web browser

Message log output errors

Database connection broken by the DBMS

Notification of errors in a program linked to the asset management system

Access error notification during addition, updating, or deletion of asset information (except when there is no property data that becomes the key)

Internal program errors

(3) When operational errors occur

If either of the following operational errors occurs in the asset management system, no asset management system services will stop:

Login error due to invalid user ID or password

Import errors during asset management system operation and while importing information from JP1/IT Desktop Management 2 - Manager

(4) When temporary errors occur

If a temporary error occurs from which recovery might be possible by re-executing the command at a later time, the executing process in which the error was detected is terminated, releasing the session.

The following are examples of temporary errors:

Memory allocation errors and database connection errors

Database lock errors

Import errors during asset management system operation and while importing information from JP1/IT Desktop Management 2 - Manager

17.4 Transactions in the asset management system

This section describes transaction processing in the asset management system during Web browser execution and during command execution.

17.4.1 Transaction processing during Web browser execution

The asset management system regards each request from the Web browser as one process, but it does not have a function for managing transactions. Using the DBMS's transaction management function, the asset management system treats an output access to the asset management database and an addition or update operation on multiple related tables as a single transaction. This not only prevents lack of conformity between asset management database tables but also enables the asset management system to discard active transactions in the event of an error at the asset management server.

For example, an asset management database transaction is not discarded, even if an error is reported to the Web browser. If a timeout or communication error occurs in the Web browser, re-execute the processing that was underway immediately before the error.

17.4.2 Transaction processing during command execution

The jamimport (import) command does not manage transactions in order to enable a large amount of table data to be input to the asset management database in a batch operation.

Therefore, if an error occurs during command execution, the relationship among the tables might have become inconsistent. In such a case, re-execute the command, register all data, and recover the tables in the asset management database.

17.5 Principal causes of errors in Asset Console and how to handle them

If an error occurs during Asset Console environment setup, check for errors in the settings in the Server Setup dialog box and in the DBMS settings.

The following sections explain the principal causes of errors that might occur during Asset Console environment setup or during an operation following login. They also explain how to handle such errors.

17.5.1 Error during asset management server setup

This section describes the error that might occur during asset management server setup, and its principal cause and action.

(1) A message such as "Not installed" is displayed, and Asset Console does not start

Asset Console might have been installed incorrectly. Re-install Asset Console.

(2) An error with the "0xC0000022 error (application cannot be initialized correctly)" message is output during system startup

An error with the 0xC0000022 error (application cannot be initialized correctly) message might be output during system startup. Such an error might occur if the System Path variable contains a network drive name (the path to another machine) and access permissions have not been provided for that machine. In addition, Service Control Manager might output warning messages with event IDs 7009 and 7000. Make sure that access permissions are provided for the specified machine.

17.5.2 Errors during creation of the asset management database

This subsection describes the errors that might occur during the creation of an asset management database, the main causes of the errors, and the actions to be taken.

(1) A message such as "Invalid value was specified for environment information" is displayed

Settings in the Server Setup dialog box might have not been specified. Specify the necessary settings in the Server Setup dialog box.

(2) Due to a database user authentication failure, a message such as "Failed to create the initial data for the asset management system" is displayed

ASTCIMn.LOG file or ASTMESn.LOG file containing the following messages is output to the log folder:

Invalid password for authorization identifier HiRDB

The Login ID and password that are set under Database Information in the Server Setup dialog box might be invalid. In the Server Setup dialog box, specify the correct Login ID and password under Database Information.

(3) A message such as "Unable to add due to existing key" is displayed

The database might have already been created.

This message is displayed if the creation of the asset management database is executed once and then is re-executed, but there is no effect on the database. To re-create a table, delete the table and all views, and then execute the creation of the asset management database.

(4) An error occurs and the setup process terminates

The database might be full (reached the capacity specified during database creation).

Uninstall Asset Console, and then re-install it. The target disk must have enough space for both the database capacity set during installation and for the management area that is automatically allocated by the database. For details about the space required for the management area, see Release Notes.

17.5.3 Error during login to Asset Console

This section describes the errors that might occur during login to Asset Console. It also explains principal causes of those errors and what actions to take.

(1) No login window is displayed

The following are the possible causes:

Microsoft Internet Information Services was installed after Asset Console was installed.

After installing Microsoft Internet Information Services, re-install Asset Console.

World Wide Web Publishing Service or World Wide Web Publishing is not running.

Make sure World Wide Web Publishing Service or World Wide Web Publishing is active.

In the Windows Internet Explorer settings, Active scripting is set to Disable.

From Internet Options, on the Security tab, open the Security Settings dialog box by clicking the Custom Level button, and then check the settings for Active scripting.

The Web service extension with the name jp1asset that is created when Asset Console is installed was mistakenly deleted.

If you cannot find jp1asset, re-create it. For details about how to create a Web service extension, see 17.5.5 Re-creating the jp1asset Web service extension.

(2) A message such as "Server is starting up. Wait a while and then log in again" is displayed, and the status remains the same for a while

The following are the possible causes:

Cannot connect to the DBMS.

Check the DBMS operating status.

The settings for Microsoft Internet Information Services are invalid.

Check the virtual directory settings using Internet Information Service Manager.

An ODBC data source does not exist.

Create an ODBC data source for connecting to a database. For details about how to create an ODBC data source, see 7.5 Creating a data source.

The asset management database has not been created.

Confirm that the asset management database was created.

The asset management database cannot be connected.

Determine whether the user ID or password specified during connection is correct.

(3) The login window opens but you cannot log in

The following are the possible causes:

The asset management server cannot connect to the asset management database.

For details about the creation of the data source that is required for database connection, see 7.5 Creating a data source.

In the settings for Windows Internet Explorer, Allow per-session cookies or Submit nonencrypted form data is set to Disable.

Check the settings for Allow per-session cookies or Submit nonencrypted form data under Internet Options.

No asset management database was created.

First, you must open the Server Setup dialog box. Enter values in Login ID and Password under Database Information and click the OK button. Avoid reserved words for the login ID and service name. For the reserved words, see RESWORDS.TXT stored in the Asset Console installation folder. After that, create the asset management database.

If the World Wide Web Publishing Service service is stopped due to a change in the system environment settings, you might not be able to log in to the asset management system after the World Wide Web Publishing Service service has started. In such a case, restart the system, and restart the World Wide Web Publishing Service service.

(4) User authentication failed

The following are the possible causes:

Cannot connect to the DBMS.

Check the DBMS operating status.

The user ID and password were not registered.

Register the user ID and password.

The entered user ID and password are invalid.

Enter the correct user ID and password.

(5) Message "Login failed because the product version does not match the database version" is issued

It is possible that the asset management database has not been moved. Upgrade the asset management database.

(6) A message such as "The maximum number of users has been reached" is displayed

Login failed because the maximum number of logged-in Asset Console users was exceeded. Log out any user that is not using Asset Console, or change the value of Number of concurrent user logins in Session Information in the Server Setup dialog box.

17.5.4 Error during Asset Console operation

This section describes the errors that might occur after you have logged in to Asset Console. It also explains principal causes of those errors and what actions to take.

(1) Nothing is output even when the CSV button or PDF button is clicked in a window operation

The following are the possible causes:

When the Lockdown Tool of Microsoft Internet Information Services was applied, the permission to access the folder for creating an intermediate file had been changed.

Check the access permission for asset-management-server's-virtual-directory\csv, and then grant write permission to Web Anonymous Users. The default virtual directory of the asset management server is Asset-Console-installation-folder\wwwroot.

The extension of the file to be downloaded was not registered in MIME.

Register the extension of the file to be downloaded in MIME.

(2) Nothing is displayed when the file name link is clicked from the Log job menu

The extension .log might not be registered in MIME. Set the virtual directory of Asset Console again in Microsoft Internet Information Services. For details about how to set a virtual directory, see 7.6 Setting a virtual directory.

(3) During Log job operation, the downloaded file content becomes empty, or an empty file is displayed as a new file

When a file is downloaded or a file is opened while the file is being downloaded, the downloaded file content might become empty or an empty file might be displayed as a new file. This problem possibly occurs if the Internet Explorer cache was cleared before the operation. In such a case, log out from Asset Console. Then, start another browser, log in again to Asset Console, and download the file.

(4) Nothing is displayed in a window

The response from the server might not be received due to a network failure or other reasons. Close the Web browser, and then log in again.

17.5.5 Re-creating the jp1asset Web service extension

Installing Asset Console automatically registers Web service extensions under the name jp1asset. If this Web service extension has been deleted by mistake, first re-create the jp1asset Web service extension, and then create an application pool.

For details about how to create the jp1asset Web service extension, see 7.8.1(5) Setting ISAPI restrictions.

For details about how to create an application pool, see 7.8.1(3) Creating application pools.

17.5.6 Resetting the virtual directory

When you re-install Microsoft Internet Information Services, you must reset the virtual directory. For details about how to reset the virtual directory, see 7.6 Setting a virtual directory.

17.6 Principal causes of errors in the Web server and how to handle them

In the event of an error, make sure that there are sufficient system resources and that there has not been any event log information indicating an error in Microsoft Internet Information Services.

If another program whose application security setting is Low (IIS process) or Medium (pooled) is running on the same Microsoft Internet Information Services, the problem might be in that program.

Also, make sure that neither a network error nor an error in Microsoft Internet Information Services has occurred. See 7.8 Settings for using Microsoft Internet Information Services, and check to make sure that the Web server settings are correct.

17.7 Principal causes of errors in the DBMS and how to handle them

In the event of an error, make sure that no error has occurred in the DBMS client library that is used by the asset management system.

17.7.1 DBMS errors

The possible causes and troubleshooting methods for each type of DBMS error are described below.

(1) The DBMS environment is invalid or has been damaged

The following are the possible causes:

A DLL of the DBMS client could not be loaded.

If the asset management server and the asset management database server are distributed, make sure that the client environment of the DBMS is installed correctly.

No DBMS driver exists.

Make sure that the client environment of the DBMS is installed correctly.

The number of concurrent connections to the DBMS has exceeded the limit.

Check the setting details to make sure that the number of concurrent connections to the DBMS has not exceeded the limit.

The network is set so that the DBMS server or the network containing it cannot be reached.

Check the communication route settings for the network in which the DBMS server exists and determine whether the DBMS server can be recognized.

(2) Connection to the asset management database results in an error

The following are the possible causes:

The DBMS server is inactive, shut down, or in the process of stopping.

Ensure that the DBMS is operating normally.

The network is set so that the DBMS server or the network containing it cannot be reached.

Check the communication route to the DBMS server.

The user ID or password specified for connection is invalid.

Make sure that the user ID and password are correct.

A DBMS server error caused a timeout or resource shortage.

Check the operating status of the DBMS.

(3) Script execution results in an error

The following are the possible causes:

Disk access failed.

Make sure that the disk is not full, there is no access problem, and no I/O error has occurred.

The transaction log is full.

If a message indicating a full transaction log has been output to the Asset Console log, check the setting for the DBMS transaction log. In this case, it is recommended that you either stop collecting transaction logs or collect backups on a regular basis.

Locking control caused a lock error or database connection timeout.

Check the operating status of the DBMS.

Script buffer overflow

Invalid script syntax

Nonexistent target table

If the environment was customized, make sure that the customization details are valid.

(4) An error occurs during the creation of the asset management database and execution stops

The disk at the database storage destination or the database that was specified when creating the database might have reached its capacity.

Re-create the asset management database on a disk that has enough space for Size, Management area, and Operation area, according to the settings specified in the Detailed Database Settings dialog box that was displayed during database creation.

(5) The login window opens, but a message "Page cannot be displayed" is displayed, and you cannot log in

It is possible that no asset management database has been created.

First, you must open the Server Setup dialog box. Enter values in Login ID and Password under Database Information and click the OK button.

Avoid reserved words for the login ID and service name. For the reserved words, see RESWORDS.TXT stored in the Asset Console installation folder.

After that, create the asset management database.

(6) Database connection authentication fails

An error message beginning with the following character string is output to the log:

KDAM5001-E[HY000] (character-string-that-is-output-according-to-the-situation) KFPA11561-E

Either Login ID or Password in Database Information might have been changed after Asset Console operations started.

Start the Server Setup dialog box and then reset Login ID and Password under Database Information to the status existing when the asset management database was created.

You cannot change Login ID and Password under Database Information while the database is running.

(7) A database communication error occurred or an error occurred inside the database

An error message beginning with the following character string is output to the log:

KDAM5001-E[HY000] (character-string-that-is-output-according-to-the-situation) KFPA11723-E

KDAM5001-E[HY000] (character-string-that-is-output-according-to-the-situation) KFPA11728-E

The DBMS server might be starting up, shut down, or stopped. Check the following:

Make sure that the HiRDB/EmbeddedEdition _AM1 service is running. If it has stopped, start it by executing jamemb_dbstart.bat as a user with administrator permission. After this service has started completely, re-start World Wide Web Publishing Service.

For details about logs, see the manual HiRDB Version 8 Messages.

Ensure that the network cable is securely connected to the Asset Console server. If the network cable is disconnected from the server, the database and Asset Console cannot communicate with each other.

(8) A database capacity shortage occurred

An error message beginning with the following character string is output to the log:

KDAM5001-E[HY000] (character-string-that-is-output-according-to-the-situation) KFPA11756-E

A page shortage might have occurred in the database area.

Reorganize the asset management database. If the same error message is displayed again after reorganization, re-create the asset management database and change the size.

For details about how to reorganize the asset management database, see 18.2.1 Reorganizing the asset management database from the Database Manager dialog box or 18.2.2 Reorganizing the asset management database using commands. For details about how to change the size of the asset management database, see F.2 Changing the size of a database.

(9) Available space has been reduced on the drive where the asset management database was created

The capacity of the work file of the database (a file for storing the temporary information necessary for executing SQL statements) might have been expanded automatically, causing a shortage of disk space.

The work file capacity is automatically expanded when a large amount of search results are output. If there is not enough space on the drive where the asset management database was created, you can release the automatically expanded area for the work file by executing jamemb_workcomp.exe.

This subsection describes the function, format, and return values of jamemb_workcomp.exe, which releases the automatically expanded area for a database work file. This subsection also provides notes on the command's execution.

jamemb_workcomp.exe is stored in the following folder:

Asset-Console-installation-folder\exe

(a) Function

jamemb_workcomp.exe releases the automatically expanded area for an database work file.

(b) Format

jamemb_workcomp.exe

(c) Return value

The command returns one of the following return values.

Return value

Description

0

Normal termination

11

Invalid option format

101 or greater

Terminated with another error

(d) Notes on command execution

Execute jamemb_workcomp.exe as a user with administrator permissions.

Before executing jamemb_workcomp.exe, stop Asset Console services, commands, and tasks on the asset management server in the following order:

World Wide Web Publishing Service or World Wide Web Publishing

Asset Console commands and tasks

To run Asset Console after executing jamemb_workcomp.exe, start the services in the reverse order of the order in which they were stopped.

If you execute jamemb_workcomp.exe when the services have not been stopped, jamemb_workcomp.exe might exit abnormally with the return value 105. When jamemb_workcomp.exe exited abnormally, an intermediate file "jamemb_workcomp.bat" is left under Asset-Console-installation-folder\exe and subsequent execution of jamemb_workcomp.exe might become error. When "jamemb_workcomp.bat" is being left, delete the file and then execute "jamemb_workcomp.exe".

(10) The KFPO00107-E message is output

If the KFPO00107-E message is output during a Database Manager operation, a work file has possibly been corrupted due to memory shortage, or the database service has possibly started before the related process finishes completely. In such a case, re-execute the operation in Database Manager. After that, if the problem has not been solved, delete all files listed in (a) and (b) below to recover the environment, and then re-execute the operation. As for the files listed in (b), you do not have to delete them if they do not exist. After the recovery processing, make sure to re-execute the operation only when no other applications (for example, Windows Explorer) are accessing Asset-Console-installation-folder\aimdb\tmp.

(a)

Asset-Console-installation-folder\aimdb\uxpldir\spool\system\filmng.dat

Asset-Console-installation-folder\aimdb\uxpldir\spool\system\flg.dat

Asset-Console-installation-folder\aimdb\uxpldir\spool\system\shmmng.dat

(b)

Asset-Console-installation-folder\aimdb\spool\~pdatmode

Asset-Console-installation-folder\aimdb\spool\~pdipcid

Asset-Console-installation-folder\aimdb\spool\oslmqid

Asset-Console-installation-folder\aimdb\spool\oslsmid

Asset-Console-installation-folder\aimdb\spool\pdprcsts

Asset-Console-installation-folder\aimdb\spool\scdqid1

Asset-Console-installation-folder\aimdb\spool\scdqid2

Asset-Console-installation-folder\aimdb\spool\pdommenv

Asset-Console-installation-folder\aimdb\tmp\pdommenv

All files under Asset-Console-installation-folder\aimdb\uxpldir\spool\shm

Asset-Console-installation-folder\aimdb\uxpldir\spool\system\semmng.dat

Asset-Console-installation-folder\aimdb\uxpldir\spool\system\msgmng.dat

17.8 Principal causes of errors in the Web browser and how to handle them

In the event of an error, make sure that there is no problem in the execution environment of the Web browser that is used by the asset management system.

The possible causes and troubleshooting methods for each type of Web browser error are described below.

17.8.1 The Web browser terminated abnormally or hung up

The following are the possible causes:

The execution environment of the Web browser is invalid, or the registry or the prerequisite DLL was corrupted.

Correct the environment or re-install the Web browser.

There is a problem with the Web browser version.

Use Windows Internet Explorer 9, Windows Internet Explorer 10, or Windows Internet Explorer 11.

An error occurred in the plug-in, or there is a problem in the plug-in.

If a corrected version has been released, install the corrected version of the Web browser.

An error occurred in the control contained in the contents, or there is a problem in the control contained in the contents.

If a corrected version has been released, install the corrected version of the Web browser.

An error occurred in the script, or there is a problem in the script.

Check the operating status. Also, if a corrected version has been released, install the corrected version of the Web browser.

There is a problem in the Web browser.

If a corrected version has been released, install the corrected version of the Web browser.

The following problems might occur depending on the GPU on the machine running that Windows Internet Explorer program (KB article 2618117):

- A Windows Internet Explorer window freezes.

- A blank page is displayed.

- Window components are not displayed in the correct positions.

If such a problem occurs, see the corresponding KB article and correct the Windows Internet Explorer settings.

17.8.2 A communication error occurred

The following are the possible causes:

The routing table was corrupted, or a network error was caused by a communication port conflict with other software.

Restore the routing table to the undamaged state, or reset the communication ports so that there is no contention with other software.

Microsoft Internet Information Services or the proxy server stopped, or an error occurred.

Check whether correct operation is taking place.

17.8.3 The GUI is not correctly displayed

The following are the possible causes:

The asset management database was corrupted by information rewriting through invalid access to the asset management database or by corruption of the logical database structure.

If backup data has been collected, use it to restore the asset management database to its original state.

If backup data has not been collected, initialize and re-create the asset management database.

Active scripting is set to Disable.

In Windows Internet Explorer, open the Internet Options dialog box. On the Security tab, click the Custom Level button to open the Security Settings dialog box. In this dialog box, set Active scripting to Enable.

Binary and script behaviors is set to Disable.

In Windows Internet Explorer, open the Internet Options dialog box. On the Security tab, click the Custom Level button to open the Security Settings dialog box. In this dialog box, set Binary and script behaviors to Enable.

The website that Windows Internet Explorer connects to is not registered in Local intranet or Trusted sites.

To register a site in Local intranet:

From the Tools menu, select Internet Options.

On the Security tab, select the Local intranet icon, and then click the Sites button.

Click the Advanced button.

Add an Asset Console site.

To register a site in Trusted sites:

From the Tools menu, select Internet Options.

On the Security tab, select the Trusted sites icon, and then click the Sites button.

Add an Asset Console site.

The option settings below are required for the security zones for the Windows Internet Explorer programs that connect to Asset Console. Specify the settings on the Security tab in the Internet Options dialog box of Windows Internet Explorer.

Enable Allow websites to open windows without address or status bars.

Enable Prompt for information using scripted windows.

Enable Automatic prompting for file downloads.

17.8.4 The login window cannot be displayed

The following are the possible causes:

World Wide Web Publishing Service is not running.

Check whether World Wide Web Publishing Service is active.

Active scripting is set to Disable.

In Windows Internet Explorer, open the Internet Options dialog box. On the Security tab, click the Custom Level button to open the Security Settings dialog box. In this dialog box, set Active scripting to Enable.

17.8.5 Cannot log in

The following are the possible causes:

Allow per-session cookies is set to Disable.

Set Allow per-session cookies to Enable.

Submit nonencrypted form data is set to Disable.

Set Submit nonencrypted form data to Enable.

Allow META REFRESH is set to Disable.

Set Meta Refresh setting to Enable.

The asset management server cannot connect to the asset management database.

Check whether the asset management server is connected to the asset management database.

17.8.6 Cannot download files

The following are the possible causes:

The extension of the file to be downloaded was not registered in MIME.

Register the extension of the file to be downloaded in MIME.

In the Windows Internet Explorer settings, File download is set to Disable.

Set File download to Enable.

17.8.7 Cannot display search results

The Web browser might have timed out. For details, visit Microsoft's website.

Additionally, when performing a search, shorten the search time by specifying a search condition that will not produce a large number of search results.

17.8.8 Clicking a link or button displays a blank window

When Windows Internet Explorer 11 is used, clicking a link or button might display a blank window (KB article 2909974). If this problem occurs, see the corresponding KB article, and correct the Windows Internet Explorer settings.

17.8.9 PDF is not output

If a cumulative update or service pack is applied to Windows Internet Explorer, the ActiveX processing might be changed and PDF might not be output. In that case, enable ActiveX control.

17.8.10 Windows Internet Explorer times out

A GUI operation during import processing for customized information might cause Windows Internet Explorer to time out. Import customized information only when Asset Console is not running.

17.8.11 A session is shared between processes

If you start multiple Windows Internet Explorer processes on a PC and then use Asset Console, a session might be shared between the processes.

This problem can be avoided by one of the following methods:

In Windows Internet Explorer, from the File menu, select New session to start another browser.

Execute iexplore.exe with the -nomerge option specified to start Windows Internet Explorer.

Set the registry values for FrameMerging and SessionMerging (DWORD value) in HKCU\Software\Microsoft\Internet Explorer\Main to 0 (disable).

17.9  Principal causes of errors during linkage to JP1/IT Desktop Management 2 - Manager and how to handle them

The following table describes the errors that might occur during linkage to JP1/IT Desktop Management 2 - Manager. It also explains principal causes of those errors and what actions to take.

Table 17‒2: Errors that might occur during linkage to JP1/IT Desktop Management 2 - Manager, and their principal causes and actions to take

No.

Error

Principal cause

Action

1

Database access error (connection target: JP1/IT Desktop Management 2 - Asset Console).

Under Database Information in the Server Setup dialog box, the specified ID (for Login ID) and password might not be set correctly.

Specify the correct ID and password.

2

Under Database Information in the Server Setup dialog box, the service name specified for Service name might not be set correctly.

Use ODBC Data Source Administrator to check the data source, and set the correct service name.

If no data source has been created, from Products for connection in the Create Data Source dialog box, select JP1/IT Desktop Management 2 - Asset Console to create a data source.

3

Database access error (connection target: JP1/IT Desktop Management 2 - Manager).

Under ITDM2 linkage in the Server Setup dialog box, the specified ID (for JP1/ITDM2-Manager database login ID) and password might not be set correctly.

Specify the correct ID and password.

4

Under ITDM2 linkage in the Server Setup dialog box, the service name specified for Name of the service connecting to the JP1/ITDM2-Manager database might not be set correctly.

Use ODBC Data Source Administrator to check the data source, and set the correct service name.

If no data source has been created, from Products for connection in the Create Data Source dialog box, select JP1/IT Desktop Management 2 - Manager to create a data source.

5

The connection target of the data source might not be set correctly.

For the connection target, specify the IP address that was set for database access in JP1/IT Desktop Management 2 - Manager setup.

6

JP1/IT Desktop Management 2 - Manager might not be running.

Check the operating status of JP1/IT Desktop Management 2 - Manager.

7

The network might be temporarily unstable.

Wait a while, and then re-execute the operation.

8

Some devices are not registered or updated.

Multiple assets might be assigned to the same asset information set because the values for the item specified as the assigned key are the same for different assets.

For the assigned key, specify an item whose value is different for every asset.

9

Device information might be already acquired.

Update JP1/IT Desktop Management 2 - Manager's device information, or acquire management information by specifying the -ALL option.

10

The time might not match in JP1/IT Desktop Management 2 - Manager and in JP1/IT Desktop Management 2 - Asset Console.

Check the OS time, and match the time in JP1/IT Desktop Management 2 - Manager and in JP1/IT Desktop Management 2 - Asset Console.

After the time matches, acquire management information by specifying the -ALL option.

11

Device information in JP1/IT Desktop Management 2 - Manager is not deleted.

JP1/IT Desktop Management 2 - Manager might not be running.

Check the operating status of JP1/IT Desktop Management 2 - Manager.

12

The network might be temporarily unstable.

Wait a while, and then check the JP1/IT Desktop Management 2 - Manager's device information.

17.10 Principal causes of errors during linkage to JP1/IT products and how to handle them

This section describes the errors that might occur during linkage to JP1/IM products. It also explains principal causes of those errors and what actions to take.

17.10.1 Errors during linkage to JP1/IT

This subsection describes the errors that might occur during linkage to JP1/IM. It also explains principal causes of those errors and what actions to take.

(1) An event is registered in JP1/IM - Manager, but error information is not imported to Asset Console

The settings for the automated action function in JP1/IM - Manager are incorrect. Specify the correct settings. For details about how to specify the settings, see 8.1.1 Setting automatic action by JP1/IM - Manager.

(2) Handling for the error information acquired from JP1/IM is completed, but the information in JP1/IM is not updated

The following are the possible causes:

The JP1 event for handling completion was not issued.

In the settings for the automated action that reports completion of error handling, make sure that 00005581 is specified for Event ID.

The event was not forwarded from JP1/Base to JP1/IM when they are running on different servers.

Set to forward events. For details about how to specify the settings, see the JP1/Base User's Guide.

The automated action settings in JP1/IM - Manager are incorrect.

Specify the correct settings. For details about how to specify the settings, see 8.1.1 Setting automatic action by JP1/IM - Manager.

JP1/Base has not been installed on the asset management server, or installation of JP1/Base failed.

Check whether JP1/Base has been correctly installed.

17.10.2 Errors during linkage to JP1/Service Support

This subsection describes the errors that might occur during linkage to JP1/Service Support. It also explains principal causes of those errors and what actions to take.

(1) The window for Asset Console is not displayed in the Main or View Item window of JP1/Service Support

The following are the possible causes:

The settings for the Asset Console host are incorrect.

For details about how to set up an Asset Console host, see the JP1/Service Support Configuration and Administration Guide.

Asset Console is not running (the World Wide Web Publishing Service service has stopped).

Start the World Wide Web Publishing Service service, and make sure that you can log in to Asset Console.

17.11 Error recovery

This section explains how to recover the asset management system from errors. For details about how to obtain error information, see 17.2 Acquiring error information.

17.11.1 Recovering Asset Console from errors

Make sure that the obtained error log information is correct. If there is an error, correct it. If the asset management server is shut down, restart Microsoft Internet Information Services.

17.11.2 How to recover the asset management server from errors

This section explains the recovery method in the event of an error in Microsoft Internet Information Services.

(1) When an error occurs in the Web server

Make sure that the obtained error log information is correct. Correct the error, and then restart Microsoft Internet Information Services. If the problem occurs again, the database might have been corrupted. Restore the backup data of the database, and then restart Microsoft Internet Information Services.

(2) When the Web server stops responding

Stop Microsoft Internet Information Services, and then make sure that the obtained error log information is correct. After correcting any error, restart Microsoft Internet Information Services. If the Web server stops responding again, the database might have been corrupted. Restore the backup data of the database, and then restart Microsoft Internet Information Services.

17.11.3  How to recover from DBMS errors

This section explains how to recover the DBMS from errors.

(1) DBMS errors

Make sure that the obtained error log information is correct. Eliminate the cause of the error and then restart the DBMS.

If DBMS starts, check the database for any damage, and restore the database from a backup if necessary.

If DBMS does not start, re-construct the DBMS environment.

(2) The DBMS is damaged

Stop Microsoft Internet Information Services and rebuild the DBMS environment. Restart the DBMS and restore the database from the backup data. Then, restart Microsoft Internet Information Services.

17.11.4 How to recover from Web browser errors

This subsection describes how to recover from Web browser errors.

(1) When the Web browser terminates abnormally

Restart the Web browser and log in again to check the status of the immediately preceding job. If it has not been completed, re-execute the job.

If the Web browser does not respond, obtain a hardcopy of the Web browser window. At the same time, contact the system administrator for investigation and provide the information about the immediately preceding operation and input data.

(2) When the Web browser display is invalid

Log out from the Web browser, and then log in again to re-execute the job that resulted in the error. If the same event recurs, contact the system administrator for investigation.

17.11.5 How to recover from errors during command execution

Make sure that the obtained error log information is correct, and then correct the errors.

18 Maintaining the Asset Management Database

This chapter describes how to maintain the asset management database.

When executing an Asset Console command, you must use the 32-bit command prompt. For the execution procedure, see Appendix G. Notes on Executing Asset Console Commands and Tasks.

18.1 Backing up and restoring

To be prepared for the possibility of errors that require re-creation of the environment, Hitachi recommends that you periodically make backups of the asset management database, uploaded files, and the registry.

There are two ways to obtain a backup:

By obtaining a backup in CSV format

By obtaining a backup in the DBMS-specific format

18.1.1 Backing up and restoring the asset management database in CSV format

This subsection describes how to back up data in the asset management database in CSV format and restore the data in CSV format.

Notes

Before you start the procedure, stop all Asset Console services, commands, and tasks.

Stop the Asset Console services in the following order:

World Wide Web Publishing Service or World Wide Web Publishing

Asset Console commands and tasks

When you run Asset Console after having backed up or restored the asset management database, start the services in the reverse of the order in which they were stopped.

Do not execute other programs while Database Manager is running.

There are two ways to obtain a backup copy of the asset management database in CSV format:

By using the Database Manager dialog box

By executing jamdbexport.bat from the command line

(1) Backing up the asset management database from the Database Manager dialog box

To back up the asset management database from the Database Manager dialog box:

Click the Start button and point to Programs, then to JP1_IT Desktop Management 2 - Asset Console, and then select Setup.

The Setup dialog box appears.

Click the Database Manager icon.

The Database Manager dialog box appears.

Select Back up the database to CSV files and then click the Next button.

The dialog box for obtaining a database backup is displayed as shown below. Logs displays a maximum of 10 backup logs.

Figure 18‒1: Dialog box for obtaining a database backup

Specify the backup folder.

In Backup folder name, specify the backup folder. Allocate sufficient free space to the drive that is specified for the backup folder. Clicking the ... button displays a dialog box in which you can browse folders and specify a desired folder. Specify 1 to 223 bytes of characters. Note that ", |, *, <, >, ?, &, ^, and / are not permitted. By default, Asset-Console-installation-folder\backup is specified.

By clicking a backup log displayed in Logs, you can specify the folder path of the selected backup log.

Enter a command, if necessary.

If there is additional information for the backup folder, enter it in Comment, expressed as a maximum of 64 bytes of characters.

Click the Execute button.

The asset management database is backed up. When the data is backed up, the contents of the asset management database are stored in the backup folder.

Note

Do not change the name of the acquired CSV file or its contents. If such a change is made, the asset management database can no longer be restored.

(2) Backing up the asset management database using the command

This subsection describes the function, format, and options for jamdbexport.bat, and provides notes on command execution. This command executes the same backup as the method that uses the Database Manager dialog box, but it does so from the command line on the asset management server.

jamdbexport.bat is stored in the following folder:

Asset-Console-installation-folder\exe

(a) Function

jamdbexport.bat obtains a backup of the asset management database and outputs the data to CSV files. When jamdbexport.bat is executed, the contents of the asset management database are stored in the backup folder.

(b) Format

jamdbexport.bat backup-folder-path [-rp]

(c) Options

backup-folder-path

Specifies the full path of the backup folder. Allocate sufficient free space to the drive that is specified for the backup folder. When you specify a path, note the following:

Do not include any spaces in a folder name.

Do not enclose a folder name in double-quotation marks (").

Do not specify an existing folder name.

If the path is omitted, Asset-Console-installation-folder\backup is set.

-rp

If this option is specified, the command starts the backup processing without waiting for a key response.

If this option is omitted, the command waits for a key response. To cancel execution, press the Ctrl + C keys.

(d) Notes on command execution

If you specify the -rp option, the command prompt closes after the processing terminates, making it impossible to determine whether an error has occurred.

Do not change the name or contents of the CSV files acquired by jamdbexport.bat. If such a change is made, the asset management database can no longer be restored.

(3) Restoring the asset management database from the Database Manager dialog box

Before you start the restore processing, make sure that the asset management database has been created. If no asset management database has been created, use the Database Manager dialog box to create a new asset management database, and then execute the restore processing.

To restore a backup of the asset management database from the Database Manager dialog box:

Click the Start button and point to Programs, then to JP1_IT Desktop Management 2 - Asset Console, and then select Setup.

The Setup dialog box appears.

Click the Database Manager icon.

The Database Manager dialog box appears.

Select Restore the database from CSV files and then click the Next button.

The dialog box for restoring the database is displayed as shown below. Logs displays a maximum of 10 backup logs.

Figure 18‒2: Dialog box for restoring the database

Specify the backup folder that is to be restored.

In Backup folder name, specify the backup folder. Clicking the ... button displays a dialog box in which you can browse folders and specify a desired folder. Specify 1 to 223 bytes of characters. Note that ", |, *, <, >, ?, &, ^, and / are not permitted. By default, Asset-Console-installation-folder\backup is specified.

By clicking a backup log displayed in Logs, you can specify the folder path of the selected backup log.

Note

Do not change the names or contents of the files created during the backup processing.

Click the Execute button.

The asset management database is restored.

18.1.2 Backing up and restoring the asset management database

This subsection describes how to back up and restore the asset management database.

Notes

Before you start this procedure, stop all Asset Console services, commands, and tasks.

Stop the Asset Console services in the following order:

World Wide Web Publishing Service or World Wide Web Publishing

Asset Console commands and tasks

When you run Asset Console after having backed up or restored the asset management database, start the services in the reverse of the order in which they were stopped.

Before you execute the operation, log in as a user with administrator permissions.

After the restore processing is completed, execute the command for acquiring JP1/IT Desktop Management 2 - Manager management information (jamTakeITDM2Info.exe -ALL) if necessary. If you do not perform this, the data in the database might not match the data in JP1/IT Desktop Management 2 - Manager.

There are two ways to back up the asset management database:

By using the Database Manager dialog box

By executing jamemb_backup.bat from the command line

To back up and restore the asset management database using the Database Manager dialog box:

Click the Start button and point to Programs, then to JP1_IT Desktop Management 2 - Asset Console, and then select Setup.

The Setup dialog box appears.

Click the Database Manager icon.

The following Database Manager dialog box appears.

Figure 18‒3: Database Manager dialog box

Select the task that you want to execute and then click the Next button.

For details about how to back up and restore the asset management database, see (1) and (3).

The method for backing up the asset management database using the command is described in (2).

(1) Backing up the asset management database from the Database Manager dialog box

To back up the asset management database:

In the Database Manager dialog box, select Back up Embedded RDB and then click the Next button.

The dialog box for acquiring a backup of the database is displayed as shown below. Logs displays a maximum of 10 backup logs.

Figure 18‒4: Dialog box for acquiring a backup of the database

Specify the name of the backup file.

In Backup file name, specify the name of the backup file. Clicking the ... button displays a dialog box in which you can browse files and specify a desired file. Specify 1 to 255 bytes of characters. Note that ", |, *, <, >, ?, &, ^, and / are not permitted. By default, Asset-Console-installation-folder\db\backup.dat is specified.

By clicking a backup log displayed in Logs, you can specify the file path of the selected backup log.

Note

When data backup is executed, the contents of the asset management database are stored in the backup file. Therefore, specify a file in a folder on the drive that has sufficient free space.

Enter a comment, if necessary.

If there is additional information about the backup file, enter a maximum of 64 bytes of characters in Comment.

Click the Execute button.

The asset management database is backed up. When the backup processing is completed, a message to that effect is displayed and the database manager is terminated.

If the backup processing fails, a message to that effect is displayed. Click the Show Maintenance Information button to check the execution result.

(2) Backing up the asset management database using commands

This subsection gives the function, format, options, return value, notes about command execution, and an execution example of jamemb_backup.bat, which is used to acquire a backup file of the asset management database.

jamemb_backup.bat is stored in the following folder:

Asset-Console-installation-folder\exe

(a) Function

This command backs up the asset management database.

(b) Format

jamemb_backup.bat -b backup-file-path -o result-file-path [-y]

(c) Options

-b backup-file-path

Specifies the full path of the file for which the backup is to be acquired. Specification of this option is mandatory.

-o result-file-path

Specifies the full path of the file to which the execution results are to be output. Specification of this option is mandatory.

-y

If this option is specified, the command starts the backup processing without waiting for a key response.

If this option is omitted, the command waits for a key response. To cancel execution, press the Ctrl + C keys.

(d) Return value

Returns one of the following return values:

Return value

Description

0

Normal termination. You can check the result file for the backup details.

11

Invalid option format.

101 or greater

Terminated with another error.

(e) Notes on command execution

Execute jamemb_backup.bat as a user with administrator permissions.

(f) Execution example

jamemb_backup.bat -b C:\temp\backup\Backup.dat -o C:\temp\backup\kekka.log -y

(3) Restoring the asset management database from the Database Manager dialog box

To restore the asset management database from a backup file:

In the Database Manager dialog box, select Restore Embedded RDB and then click the Next button.

The dialog box for restoring the database from its backup file is displayed as shown below. Logs displays a maximum of 10 backup logs.

Figure 18‒5: Dialog box for restoring the database from its backup file

Specify the name of the backup file.

In Backup file name, specify the name of the backup file that is to be restored. Clicking the ... button displays a dialog box in which you can browse files and specify a desired file. Specify 1 to 255 bytes of characters. Note that ", |, *, <, >, ?, &, ^, and / are not permitted. By default, the file name specified in Backup file name during backup acquisition is specified. If you have changed the location of the backup file after backup processing, use the ... button to specify the correct file name.

By clicking a backup log displayed in Logs, you can specify the file path of the selected backup log.

Click the Execute button.

The asset management database is restored from its backup file. When the restore processing is completed, a message to that effect is displayed and the database manager is terminated.

If the restore processing fails, a message to that effect is displayed. Click the Show Maintenance Information button to check the execution result.

Note

To restore a backup file, Asset Console must have been installed at the same path as when its backup was acquired. Before starting the restore processing, make sure that the installation folder has the same path as when the backup was acquired.

18.1.3  Backing up and restoring uploaded files

This subsection describes how to back up and restore uploaded files.

(1) Backing up uploaded files

Copy the following files:

Files under asset-management-server's-virtual-directory\data

Files under asset-management-server's-virtual-directory\csv

By default, asset-management-server's-virtual-directory is Asset-Console-installation-folder\wwwroot.

(2) Restoring uploaded files

Restore copied files to their original folders.

Note

For the backup file to be restored, specify a file that was acquired from the same version of Asset Console. Also restore the file to the path of the same installation folder as when backup was acquired.

18.1.4  Backing up and restoring the registry

This subsection describes how to back up and restore the registry.

(1) Backing up the registry

To back up the registry:

Right-click on the Start button and then select Run.

The Run dialog box appears.

In the input field, enter regedit and then click the OK button.

Registry Editor starts.

From the tree view, select HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\HITACHI\JP1/Asset Information Manager.

From the menu, select File and then Export.

The Export Registry File dialog box appears.

Specify the storage location and file name, then click the Save button.

The backup file is created at the specified location.

(2) Restoring the registry

To restore the registry:

Right-click on the Start button and then select Run.

The Run dialog box appears.

In the input field, enter regedit and then click the OK button.

Registry Editor starts.

From the tree view, select HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\HITACHI\JP1/Asset Information Manager.

From the menu, select File and then Import.

The Import Registry File dialog box appears.

Specify the obtained backup file and then click the Open button.

The specified backup file is restored.

Note

To use a backup file for restoration, you must specify the same Asset Console version and path as when the backup was made.

18.2 Reorganizing the asset management database

Hitachi recommends that you periodically reorganize the asset management database. When records are deleted from a database, the corresponding areas remain unused. When such unused areas increase in the database area, a space shortage might occur in the database.

If the database area usage rate reaches 80% or greater, messages with the following message IDs are displayed in the event log:

KFPA12300-I

KFPH00211-I

In such a case, you might be able to improve the database area usage rate by reorganizing the asset management database.

For details about the messages, see the manual HiRDB Version 8 Messages.

There are two ways to reorganize the asset management database:

By using the Database Manager dialog box

By executing jamemb_reorganization.bat from the command line

If a message indicating a shortage of database capacity is still displayed after the asset management database has been reorganized, you must extend the size of the asset management database. For details about how to change the size of the asset management database, see F.2 Changing the size of a database.

Notes

Before you reorganize the asset management database, stop all Asset Console services, commands, and tasks.

Stop the Asset Console services in the following order:

World Wide Web Publishing Service or World Wide Web Publishing

Asset Console commands and tasks

When you run Asset Console after having reorganized the asset management database, start the services in the reverse of the order in which they were stopped.

18.2.1 Reorganizing the asset management database from the Database Manager dialog box

Notes

Before you reorganize the asset management database using the Database Manager dialog box, stop all Asset Console services, commands, and tasks.

Stop the Asset Console services in the following order:

World Wide Web Publishing Service or World Wide Web Publishing

Asset Console commands and tasks

When you run Asset Console after having reorganized the asset management database, start the services in the reverse of the order in which they were stopped.

When you use Database Manager to reorganize the database, if the new value for Storage folder name or Connection user ID is different from the old one, the old database file remains. After reorganization finishes, delete the old database file.

To use the Database Manager dialog box to reorganize the asset management database:

In the Database Manager dialog box, select Reorganize Embedded RDB and then click the Next button.

The following dialog box is displayed.

Figure 18‒6: Dialog box for reorganizing the database

Click the Execute button.

The asset management database is reorganized. When the reorganization processing is completed, a message to that effect is displayed and the database manager is terminated.

If the reorganization processing fails, a message to that effect is displayed. Click the Show Maintenance Information button to check the execution results.

18.2.2 Reorganizing the asset management database using commands

This subsection describes the function, format, options, and return values of jamemb_reorganization.bat, which reorganizes the restored asset management database. It also provides notes on its execution, followed by an execution example.

jamemb_reorganization.bat is stored in the following folder:

Asset-Console-installation-folder\exe

If reorganization fails, the asset management database can no longer be used. In such a case, restore the backup data of the asset management database.

(1) Function

jamemb_reorganization.bat reorganizes the asset management database.

(2) Format

jamemb_reorganization.bat port-number user-ID password -o result-file-path [-y]

(3) Options

port-number

Specifies the database connection port number that was specified when Asset Console was installed. To identify the port number that was set, check PDNAMEPORT in the HiRDB.ini file, which is stored in Asset-Console-installation-folder\aimdb\conf\emb. Specification of this option is mandatory.

user-ID, password

Specifies the values that were set in Login ID in Database Information in the Server Setup dialog box. Specification of this option is mandatory.

-o result-file-path

Specifies the full path of the file to which the execution results are to be output. Specification of this option is mandatory.

-y

If this option is specified, the command starts the reorganization processing without waiting for a key response.

If this option is omitted, the command waits for a key response. To cancel execution, press the Ctrl + C keys.

(4) Return value

Returns one of the following return values:

Return value

Description

0

Normal termination. You can check the result file for the details of reorganization.

11

Invalid option format.

101 or greater

Terminated with another error.

(5) Notes on command execution

Before you execute jamemb_reorganization.bat, stop all Asset Console services, commands, and tasks.

Stop the Asset Console services in the following order:

World Wide Web Publishing Service or World Wide Web Publishing

Asset Console commands and tasks

When you use Asset Console after having executed jamemb_reorganization.bat, start the services in the reverse of the order in which they were stopped.

Execute jamemb_reorganization.bat as a user with administrator permissions.

(6) Execution example

jamemb_reorganization.bat 31022 admin admin -o C:\temp\backup\kekka.log -y

18.2.3 Setting execution monitoring time limit for database reorganization processing

If an error (such as, communication error or disk error) occurs while a database is being reorganized, the reorganization process might stop responding. In some cases (for example, when reorganization is automatically executed by a Windows task function or JP1/AJS), the non-responding process cannot be forcibly terminated by manual operation. This subsection describes how to set an execution monitoring time limit for database reorganization processing, and how to stop a reorganization process that does not respond.

Notes

Before you set execution monitoring time limit for database reorganization processing, on the asset management server, stop all Asset Console services, commands, and tasks.

Stop the Asset Console services in the following order:

World Wide Web Publishing Service or World Wide Web Publishing

Asset Console commands and tasks

When you run Asset Console after having changed the execution monitoring time limit for database reorganization processing, start the services in the reverse of the order in which they were stopped.

Stop the database. (For details about how to stop the database, see F.4(2) Stopping the database.)

Use a text editor to open the pdsys file stored in Asset-Console-installation-folder\aimdb\conf.

Add the following line:

set pd_utl_exec_time = execution-monitoring-time-limit-for-reorganization-processing#

Start the database. (For details about how to start the database, see F.4(1) Starting the database.)

#

To monitor the execution time of a database access command, set the monitoring time limit in the range from 0 to 35791394 (minutes). If nothing is specified or 0 is specified, the execution time of a command will not be monitored. If the monitoring time limit specified here expires, an executing command will terminate abnormally. For this operand, specify a value that is a little larger than the maximum value of the actual command execution time. For example, if the maximum execution time for reorganizing a database is about 90 minutes, you may need to specify pd_utl_exec_time=120. This setting is based on the consideration that, if a process that usually takes about 90 minutes does not complete within 120 minutes, a no-response error has probably occurred.

Coding example:

   #
   #------------------------------------------------------------------
   # set form
   #
   :
   (Omitted)
   :
   set pd_utl_exec_time = 120
   #
   #------------------------------------------------------------------
   # putenv form
   #

18.3 Notes on restoring the JP1/IT Desktop Management 2 - Manager database

Before restoring the JP1/IT Desktop Management 2 - Manager database, perform the following operations:

Stop the World Wide Web Publishing Service or World Wide Web Publishing service.

Stop the command for acquiring JP1/IT Desktop Management 2 - Manager management information (jamTakeITDM2Info.exe) if it is running.

If the Acquisition of ITDM2 - Manager management information (Asset Console) task has been registered in Windows Task Scheduler, disable the task.

After you finish restoring the JP1/IT Desktop Management 2 - Manager database, make sure that you execute the command for acquiring JP1/IT Desktop Management 2 - Manager management information (jamTakeITDM2Info.exe). Then, after the acquisition of information finishes, restart the stopped services, commands, and tasks.

Part 7: Reference

19 Details of Information That Can Be Acquired from Linked Products and Details of JP1 Events That Are Issued

This chapter provides the details of management information for JP1/IT Desktop Management 2 - Manager that can be loaded to the asset management database for use in jobs.

It also provides the details of JP1 events that are issued from Asset Console in order to link with JP1/IM.

19.1 Management information that can be acquired from JP1/IT Desktop Management 2 - Manager

Based on the management information of JP1/IT Desktop Management 2 - Manager, information is registered or updated in each corresponding class of Asset Console.

The following table shows the information to be registered or updated and the correspondence to the assigned management information.

Table 19‒1: Information to be registered or updated and the correspondence to the assigned management information

Asset Console class

JP1/IT Desktop Management 2 - Manager management information

Device information

Software information

Common fields

Custom fields

Status

System information and hardware information

Security information

Installed software information

Asset information

Y

Y

N

N

Y

Y

Hardware information

Y

Y

N

N

Y

Y

IP address management information

N

Y

N

N

N

N

Network information

Y

Y

N

N

Y

Y

Installed software information

N

N

N

Y

N

N

Installed software list

N

N

N

Y

N

N

Patch information

N

N

Y#

N

N

N

Patch list

N

N

Y

N

N

N

Virus definition information

N

N

Y

N

N

N

Group information

N

N

N

N

Y

N

Location information

N

N

N

N

Y

N

Legend:

Y: Can be assigned

N: Cannot be assigned

#: This information is only assigned when the OS of a managed computer is Windows.

The table below shows the JP1/IT Desktop Management 2 - Manager management information that can be assigned. For details about each management item, see the JP1/IT Desktop Management 2 Overview and System Design Guide.

Managed class name

Management name

Device information

Status

Host identifier

Device type

Management type

Agent version

Connection settings

Device status

System information and hardware information

Computer information

BIOS manufacturer

BIOS name

BIOS release date

BIOS serial #

BIOS version (SMBIOS)

BIOS version

Manufacturer of the computer

Computer model

{0} Core(s)

Computer serial #

Computer UUID

Logical drive letter#1

Logical drive type#1

Logical drive file system#1

Logical drive free space#1, #2

Logical drive capacity#1, #2

Computer name

Computer description

Monitor turn off time (AC)

Monitor turn off time (DC)

Hard disk turn off time (AC)

Hard disk turn off time (DC)

System standby (AC)

System standby (DC)

System hibernate (AC)

System hibernate (DC)

Processor control (AC)

Processor control (DC)

AMT firmware version

User information

Time zone

Account name of the last-logged on user

Locale

Last logged on user description

User name of the last-logged on user

Operating system

Operating system

OS service pack

OS kernel version

Company that owns the OS

OS languages

OS owner

OS serial #

OS last startup date/time

Windows directory

Windows installer version

Windows update (Agent version)

IE version

IE service pack

Network information

Domain (Work group)

Domain role

Default gateway#1

DHCP#1

DHCP lease expiration date/time#1

DHCP lease acquisition date/time#1

DHCP server address#1

DNS server address#1

IP address#1

Subnet mask#1

MAC address#1

Primary WINS server address#1

Secondary WINS server address#1

Smart devices information

IMEI of the smart device

UDID of the smart device

ICCID of the smart device

IMSI of the smart device

Contract phone number of the smart device

Email address of the smart device

Smart device carrier

Bar code setup status of the smart device

RAM of the smart device#2

Free space of the smart device RAM#2

Capacity of the smart device internal storage#2

Free space of the smart device internal storage#2

Capacity of the smart device external storage#2

Free space of the smart device external storage#2

CPU information

Processor name#1

Memory information

Total memory capacity#1, #2

Virtual memory capacity#2

Hard disk information

Hard disk interface#1

Hard disk model#1

Hard disk capacity#1, #2

CD-ROM drive information

CD-ROM drive model#1

Printer information

Printer type#1

Printer driver#1

Printer name#1

Port of the printer server#1

Name of the printer server#1

Printer shared name#1

Video controller information

Video card VRAM capacity#1

Video driver#1

Video chip#1

Sound card information

Manufacturer of the sound card#1

Name of the sound card#1

Monitor information

Monitor#1

Keyboard information

Keyboard#1

Mouse information

Mouse#1

Security information

Update program information

Document number (applied date)

Anti-virus product information

Product name

Version

Installed date

Engine version

Virus definition file version

Auto Protect

Software information

Installed software information

Software name

Version

Software vendor

Support URL

Product ID

Registered date/time

Installation date

Common fields

Group name

Location name

User name

Account

E-mail

Phone

Custom Field

Information about custom field created by JP1/IT Desktop Management 2 - Manager

#1: There might be more than one information item for a single device managed by JP1/IT Desktop Management 2. When an item with multiple pieces of information is assigned to a user property of Asset Console, item values separated by semicolons (;) are stored in the asset management database. This applies to the following items:

asset information.user property area_1 to 2

asset information.user property code 1 to 6

asset information.user property field128_1 to 2

asset information.user property field255_1 to 2

asset information.user property field32_1 to 6

asset information.user property field64_1 to 2

hardware information.user property area_1 to 4

hardware information.user property code-1 to 12

hardware information.user property field128_1 to 8

hardware information.user property field255_1 to 8

hardware information.user property field32_1 to 8

hardware information.user property field64_1 to 8

#2: There might be several byte errors depending on the method of displaying data for JP1/IT Desktop Management 2 and Asset Console.

Important

If you specify the following items for the assigned items of JP1/IT Desktop Management 2 - Manager management information acquisition and then collect the management information of ITDM2, the display content might differ between JP1/IT Desktop Management 2 - Asset Console and JP1/IT Desktop Management 2 - Manager.

Memory Capacity

Hard Disk Capacity

Total Free Space on Logical Drive

Total Capacity of Logical Drive

Virtual Memory Capacity

VRAM Capacity of Video Card

RAM of Smart Device

Total Free Space on RAM of Smart Device

Internal storage of Smart Device

Internal storage of Smart Device (Free)

External storage of Smart Device

External storage of Smart Device (Free)

For details about how to register JP1/IT Desktop Management 2 - Manager management information in the asset management database, see 5.2.1 Collecting from JP1/IT Desktop Management 2 - Manager.

The details of each class of information to be registered or updated are described below.

19.1.1 Information that can be acquired as asset information

The table below shows the details of Asset Console's asset information that is registered or updated based on the management information of JP1/IT Desktop Management 2 - Manager.

For details about the settings for assigning JP1/IT Desktop Management 2 - Manager management information, see 16.14 Setting assigned items (ITDM2 Management Information Acquisition).

Table 19‒2: Details of the asset information that is registered or updated based on the management information of JP1/IT Desktop Management 2 - Manager

Item name

Value to be set

Whether the value is updated when there is existing data

Asset ID

The value is assigned automatically.

N

Asset type

Hardware

N

Asset number

One of the following assigned items selected by ITDM2 management information acquisition:

Auto

Host identifier (Device information)

Custom Field

Computer Serial # (System information and hardware information)

Computer Name (System information and hardware information)

The default is Auto.

Y#

Status

Among the values of the AssetStatus code ID, the item selected by ITDM2 management information acquisition is set.

The default is Active.

Y#

Usage management

Among the values of the AssetWorkKind code ID, the item selected by ITDM2 management information acquisition is set.

The default is Used.

Y#

Last updated date of ITDM2

Last updated date for Device information or deletion history information of Last updated date is set, whichever is more recent.

Y

ITDM2 Agent installed status

Acquired from Management Type for Device information.

Y

Group ID

ID corresponding to the group specified in Group

Y

Group

One of the following assigned items selected by ITDM2 management information acquisition:

Do not set

IP address group

User's department

Group name (Common fields)

The default is Do not set.

Y#

Group name

The group name corresponding to the group information set for Group name is set.

Y

Host identifier

Acquired from Host identifier for Device information.

Y

Location ID

ID corresponding to the location set in Location name is set.

Y

Location name

One of the following assigned items selected by ITDM2 management information acquisition is set:

Do not set

IP address group

Location name (Common fields)

The default is Do not set.

Y#

Location name

The location name corresponding to the location name information set for Location name is set.

Y

Registration date

By acquiring management information of JP1/IT Desktop Management 2 - Manager, the new date and time created for asset information is set.

N

Stocktaking date

One of the following assigned items selected by ITDM2 management information acquisition is set:

Do not set

Custom Field

The default is Do not set.

Y#

User ID

The ID corresponding to the user information set in User name is set.

Y

User name

One of the following assigned items selected by ITDM2 management information acquisition is set:

Do not set

User Name (Common fields)

Account (Common fields)

E-mail (Common fields)

Custom Field

OS owner (System information and hardware information)

The default is User Name.

Y#

User name (English)

The user name corresponding to user information set for User name (English) is set.

Y

User property

One of the following assigned items selected by ITDM2 management information acquisition is set:

Do not set

Device information

Common fields

Custom Field

System information and hardware information

Constant value

The default is Do not set.

Y#

Legend:

Y: Updated

N: Not updated

#: Follow the settings for assigned items of ITDM2 management information acquisition.

Notes

If you select Assigned key for Assignment method, and an item other than Auto as the asset number in the ITDM2 management information acquisition window, the value for the management information of JP1/IT Desktop Management 2 - Manager corresponding to the assigned item changes. When this happens, the asset number also changes. However, the asset number does not change in the following cases:

The new value is the same as the asset number that has already been registered in the asset management database.

Duplication of values might occur if host name, IP address, MAC address, or Computer name is selected as the assigned item for the asset number.

19.1.2 Information that can be acquired as hardware information

The following table shows the details of Asset Console's hardware information that is registered or updated based on the management information of JP1/IT Desktop Management 2 - Manager.

Table 19‒3: Details of the hardware information that is registered or updated based on the management information of JP1/IT Desktop Management 2 - Manager

Item name

Value to be set

Whether the value is updated when there is existing data

Asset ID

Asset ID of the corresponding asset information is set.

N

Processor speed

Acquired from Processor Name of System information and hardware information.

Y

Number of processors

Acquired from {0} Core(s) of System information and hardware information.

Y

Processor

Acquired from Processor Name of System information and hardware information.

Y

Developer

One of the following assigned items selected by ITDM2 management information acquisition is set:

Do not set

Custom Field

Manufacturer of the computer (System information and hardware information)

The default is Manufacturer of the computer.

Y#

Host name

Acquired from Host name of System information and hardware information.

Y

IP address

Acquired from IP address of System information and hardware information.

Y

MAC address

Acquired from MAC address of System information and hardware information.

Y

Device type

One of the following assigned items selected by ITDM2 management information acquisition is set:

Device type (Device information)

Custom Field

Constant value

The default is Device type.

Y#

Memory

Acquired from Total Memory Capacity of System information and hardware information.

Y

Model

Acquired from Computer model of System information and hardware information.

Y

Device name

One of the following assigned items selected by ITDM2 management information acquisition is set:

Do not set

Computer model (System information and hardware information)

Computer Name (System information and hardware information)

Constant value

The default is Computer model.

Y#

OS

Acquired from OS of System information and hardware information.

Y

OS version

Acquired from OS service pack of System information and hardware information.

Y

Hard disk free space

The total amount of Logical Drive Free Space for System information and hardware information is set.

Y

Serial number

Acquired from Computer Serial # of System information and hardware information.

Y

Hard disk size

The total amount of Logical Drive Capacity for System information and hardware information is set.

Y

User property

One of the following assigned items selected by ITDM2 management information acquisition is set:

Do not set

Device information

Common fields

Custom Field

System information and hardware information

Constant value

The default is Do not set.

Y#

Legend:

Y: Updated

N: Not updated

#: Follow the settings for assigned items of ITDM2 management information acquisition.

19.1.3 Information that can be acquired as IP address management information

The following table shows the details of Asset Console's IP address management information that is registered based on the management information of JP1/IT Desktop Management 2 - Manager.

Table 19‒4: Details of the IP address management information that is registered based on the management information of JP1/IT Desktop Management 2 - Manager

Item name

Value to be set

Whether the value is updated when there is existing data

IP address

Acquired from IP address of System information and hardware information.

N

Legend:

N: Not updated

19.1.4 Information that can be acquired as network information

The following table shows the details of Asset Console's network information that is registered or updated based on the management information of JP1/IT Desktop Management 2 - Manager.

Table 19‒5: Details of the network information that is registered or updated based on the management information of JP1/IT Desktop Management 2 - Manager

Item name

Value to be set

Whether the value is updated when there is existing data

Asset ID

Asset ID of the corresponding asset information is set.

N

Computer name

Acquired from Computer Name of System information and hardware information.

Y

Default gateway

Acquired from Default Gateway of System information and hardware information.

Y

DHCP server name

Acquired from DHCP server address of System information and hardware information.

Y

ITDM2 management information acquisition control

Delete when there is no corresponding information in the ITDM2 management information. is set.

Y

IP address

Acquired from IP address of System information and hardware information.

Y

IP address type

When the acquired value for IP address of System information and hardware information is in xxx.xxx.xxx.xxx (where xxx is a value from 0 to 255) format, IPv4 is set. For values in another format, IPv6 is set.

Y

MAC address

Acquired from MAC address of System information and hardware information.

Y

Network info ID

Numbered automatically.

N

Node name (host name)

Acquired from Host name of System information and hardware information.

Y

Subnet mask

Acquired from Subnet mask of System information and hardware information.

Y

User property

One of the following assigned items selected by ITDM2 management information acquisition is set:

Do not set

Device information

Common fields

Custom Field

System information and hardware information

Constant value

The default is Do not set.

Y#

Legend:

Y: Updated

N: Not updated

#: Follow the settings for assigned items of ITDM2 management information acquisition.

19.1.5 Information that can be acquired as installed software information

The following table shows the details of Asset Console's installed software information that is registered or updated based on the management information of JP1/IT Desktop Management 2 - Manager.

Table 19‒6: Details of the installed software information that is registered or updated based on the management information of JP1/IT Desktop Management 2 - Manager

Item name

Value to be set

Whether the value is updated when there is existing data

Asset ID

Asset ID of the corresponding asset information is set.

N

ITDM2 management information acquisition control

Delete when there is no corresponding information in the ITDM2 management information. is set.

Y

Installed date

Acquired from Installed date of Installed software information.

Y

Installed software ID

Installed software ID in Installed software list is registered.

N

Product ID

Acquired from Product ID of Installed software information (Only information for Microsoft Office products is acquired).

Y

User property

One of the following assigned items selected by ITDM2 management information acquisition is set:

Do not set

Installed software information

Constant value

The default is Do not set.

Y#

Legend:

Y: Updated

N: Not updated

#: Follow the settings for assigned items of ITDM2 management information acquisition.

19.1.6 Information that can be acquired as installed software list

The installed software list is searched for the corresponding software name and software version. If there is no applicable information, it is added to the list. If the list contains no corresponding information, the information is added to the installed software list.

The table below shows the details of Asset Console's installed software list that is registered or updated based on the management information of JP1/IT Desktop Management 2 - Manager.

Table 19‒7: Details of the installed software list that is registered or updated based on the management information of JP1/IT Desktop Management 2 - Manager

Item name

Value to be set

Whether the value is updated when there is existing data

Installed software ID

Numbered automatically.

N

Managed level

Among the values of the InstalledInd code ID, the item specified for Assigned items of ITDM2 management information acquisition is set.

The default is Managed object.

Y

Software type

Among the values of the InstalledKind code ID, the item specified for Assigned items of ITDM2 management information acquisition is set.

The default is Normally.

Y

Installed software name

Acquired from Software name of Installed software information.

N

Permission

Among the values of the Permit code ID, the item specified for Assigned items of ITDM2 management information acquisition is set.

The default is Permit.

Y

Version

Acquired from Version of Installed software information.

N

Software list ID

Software list ID assigned through automatic assignment of software names is registered.

N

Legend:

Y: Updated

N: Not updated

19.1.7 Information that can be acquired as patch information

The following table shows the details of Asset Console's patch information that is registered or updated based on the management information of JP1/IT Desktop Management 2 - Manager.

Table 19‒8: Details of patch information that is registered or updated based on the management information of JP1/IT Desktop Management 2 - Manager

Item name

Value to be set

Whether the value is updated when there is existing data

Asset ID

Asset ID of the corresponding asset information is set.

N

ITDM2 management information acquisition control

Delete when there is no corresponding information in the ITDM2 management information. is set.

Y

Installed date

Acquired from Document number (applied-date) of security information.

Y

Applied status

Apply is set.

Y

Patch ID

Patch ID in the patch list is registered.

N

Legend:

Y: Updated

N: Not updated

19.1.8 Information that can be acquired as a patch list

The following table shows the details of Asset Console's patch list that is registered or updated based on the management information of JP1/IT Desktop Management 2 - Manager.

Table 19‒9: Details of the patch list that is registered or updated based on the management information of JP1/IT Desktop Management 2 - Manager

Item name

Value to be set

Whether the value is updated when there is existing data

Patch ID

Numbered automatically.

N

Patch name

Acquired from Document number (applied-date) of security information.

N

Version

Acquired from Document number (applied-date) of security information.

N

Legend:

N: Not updated

19.1.9 Information that can be acquired as virus definition information

The following table shows the details of Asset Console's virus definition information that is registered or updated based on the management information of JP1/IT Desktop Management 2 - Manager.

Table 19‒10: Details of the virus definition information that is registered or updated based on the management information of JP1/IT Desktop Management 2 - Manager

Item name

Value to be set

Whether the value is updated when there is existing data

Asset ID

Asset ID of the corresponding asset information is set.

N

Engine version

Acquired from Engine version in security information.

Y

ITDM2 management information acquisition control

Delete when there is no corresponding information in the ITDM2 management information. is set.

Y

Installed date

Acquired from Installed date of security information.

Y

Resident/nonresident

Acquired from Automatic Protection (Resident Setting) of security information.

When the acquired value for Automatic Protection (Resident Setting) is AutoProtectEnabled, Resident is set. Otherwise, Nonresident is set.

Y

Anti-virus product version

Acquired from Version in security information.

Y

Anti-virus product name

Acquired from Software Name in security information.

N

Virus definition version

Acquired from Anti-virus definition file version in security information.

Y

Legend:

Y: Updated

N: Not updated

19.1.10 Information that can be registered as group information

If no corresponding group has been registered in the management information of JP1/IT Desktop Management 2 - Manager, the information is added to the group information. You can use Assigned items in the ITDM2 management information acquisition window to specify whether to add information to group information. For details about the settings of Assigned items in the ITDM2 management information acquisition window, see 16.14 Setting assigned items (ITDM2 Management Information Acquisition).

The following table shows the details of Asset Console's group information that is registered based on the management information of JP1/IT Desktop Management 2 - Manager.

Table 19‒11: Details of the group information that is registered based on the management information of JP1/IT Desktop Management 2 - Manager

Item name

Value to be set

Whether the value is updated when there is existing data

Group name

Registered from hierarchy path of Group information.

N

Group name (English)

Set from Local name (English).

N

Group ID

Numbered automatically.

N

Local name

Registered from hierarchical level name of Group information.

N

Local name (English)

Group ID is set.

N

Upper Group ID

If there is an upper group, Group ID of the upper group is set.

N

Legend:

N: Not updated

19.1.11 Information that can be registered as location information

If no location corresponding location has been registered in the management information of JP1/IT Desktop Management 2 - Manager, the information is added to the location information. You can use Assigned items in the ITDM2 management information acquisition window to specify whether to add information to location information. For details about the settings of Assigned items in the ITDM2 management information acquisition window, see 16.14 Setting assigned items (ITDM2 Management Information Acquisition).

The following table shows the details of Asset Console's location information that is registered based on the management information of JP1/IT Desktop Management 2 - Manager.

Table 19‒12: Details of the location information that is registered based on the management information of JP1/IT Desktop Management 2 - Manager

Item name

Value to be set

Whether the value is updated when there is existing data

Location

Registered from hierarchy path of Location information.

N

Location

Set from Location name (English).

N

Location ID

Numbered automatically.

N

Location name

Registered from hierarchical level name of Location information.

N

Location name (English)

Location ID is set.

N

Upper location ID

If there is an upper location, Location ID of the upper location is set.

N

Legend:

N: Not updated

19.2 Details of JP1 events issued from Asset Console

The table below lists and describes the types of JP1 events that are issued from Asset Console.

Table 19‒13: JP1 events issued from Asset Console

Event ID

Event name

Description

00005531

Filter start event

Reports that the asset management server has started.

00005532

Filter start error event

(abnormal termination)

Reports that startup of the asset management server failed.

00005533

Filter termination event

Reports that monitoring of the asset management server session was terminated.

00005541

Item transition event

Reports that an item has transitioned to the next node. This event is issued only when the JP1 event notification task is defined as the activity.

00005542

Item status change event

Reports that an Item was rejected or pulled back. This event is issued when an Item for which an Item transition event was issued is pulled back or rejected.

00005543

Item deletion event

Reports that an Item was deleted. This event is issued when an Item for which an Item transition event was issued is deleted.

00005581

Handling completion event

Reports to JP1/IM that handling of the problem imported from JP1/IM was completed.

00005582

Problem status change event

Reports that a problem was registered or changed.

00005583

Problem deletion event

Reports that a problem was deleted.

19.2.1 Event attributes

This section explains the attribute types, items, attribute names, and attribute details of the various JP1 events issued from Asset Console.

(1) Attributes of the filter start event

This event reports that the asset management server has started.

The table below shows the attributes of the filter start event.

Table 19‒14: Attributes of the filter start event

Attribute type

Item

Attribute name

Description

Issue timing

--

--

Start of filter

Basic attribute

Event ID

--

00005531

Message

--

The session filter was started.

Extended

Common information

Importance

SEVERITY

Information

Product name

PRODUCT_NAME

/HITACHI/JP1/AC

Object type

OBJECT_TYPE

SERVICE

Object name

OBJECT_NAME

ASSET_SESS

Occurrence

OCCURRENCE

START

Start time

START_TIME

Start time

Legend:

--: Not applicable

(2) Attributes of the filter start error event (abnormal termination)

This event reports that the asset management server failed to start.

The table below shows the attributes of the filter start error event (abnormal termination).

Table 19‒15: Attributes of the filter start error event (abnormal termination)

Attribute type

Item

Attribute name

Description

Issue timing

--

--

Filter start error

Basic attribute

Event ID

--

00005532

Message

--

The session filter was abended.

Extended

Common information

Importance

SEVERITY

Error

Product name

PRODUCT_NAME

/HITACHI/JP1/AC

Object type

OBJECT_TYPE

SERVICE

Object name

OBJECT_NAME

ASSET_SESS

Occurrence

OCCURRENCE

END

End time

END_TIME

End time

Return code

RESULT_CODE

Return code

Legend:

--: Not applicable

(3) Attributes of the filter termination event

This event reports that the asset management server session monitoring terminated.

The table below shows the attributes of the filter termination event.

Table 19‒16: Attributes of the filter termination event

Attribute type

Item

Attribute name

Description

Issue timing

--

--

Stop of filter

Basic attribute

Event ID

--

00005533

Message

--

The session filter was stopped.

Extended

Common information

Importance

SEVERITY

Information

Product name

PRODUCT_NAME

/HITACHI/JP1/AC

Object type

OBJECT_TYPE

SERVICE

Object name

OBJECT_NAME

ASSET_SESS

Occurrence

OCCURRENCE

END

End time

END_TIME

End time

Return code

RESULT_CODE

Return code

Legend:

--: Not applicable

(4) Attributes of the Item transition event

This event reports that the Item transitioned to the node.

You can specify any desired information in the user extension area of event information 0 to 31 using the managed item settings of the JP1 event notification task. For details about the JP1 event notification task, see 12.5.2 Selecting tasks to be executed.

The table below shows the attributes of the Item transition event.

Table 19‒17: Attributes of the Item transition event

Attribute type

Item

Attribute name

Description

Issue timing

--

--

Transition of Item

Basic attribute

Event ID

--

00005541

Message

--

The item transitioned.

Extended

Common information

Importance

SEVERITY

Notice

Product name

PRODUCT_NAME

/HITACHI/JP1/AC

Object type

OBJECT_TYPE

INCIDENT

Object name

OBJECT_NAME

Incident

Object ID

OBJECT_ID

Target item ID

Occurrence

OCCURRENCE

ACTIVITY

User property

Version

A10

Asset Console version

Item name

C11

Target Item name

Item definition ID

C12

Target Item definition ID

Status

C13

State after transition

Registrar user ID

C14

User ID of the Item registrar

Final transactor user ID

C15

User ID of the final transactor

Processing target user ID

C16

User ID of the Item transition destination

Event information 0 to 31

U00 to U31

User extension area

Legend:

--: Not applicable

(5) Attributes of the Item status change event

This event reports that the Item was rejected or pulled back.

The table below shows the attributes of the Item status change event.

Table 19‒18: Attributes of the Item status change event

Attribute type

Item

Attribute name

Description

Issue timing

--

--

Rejection or pullback of an Item

Basic attribute

Event ID

--

00005542

Message

--

The item status was changed.

Extended

Common information

Importance

SEVERITY

Notice

Product name

PRODUCT_NAME

/HITACHI/JP1/AC

Object type

OBJECT_TYPE

INCIDENT

Object name

OBJECT_NAME

Incident

Object ID

OBJECT_ID

Target item ID

Occurrence

OCCURRENCE

Rejection: REJECT

Pullback: PULLBACK

User property

Version

A10

Asset Console version

Item name

C11

Target Item name

Item definition ID

C12

Target Item definition ID

Status

C13

State after transition

Registrar user ID

C14

User ID of the Item registrar

Final transactor user ID

C15

User ID of the final transactor

Processing target user ID

C16

User ID of the Item transition destination

Legend:

--: Not applicable

(6) Attributes of the Item deletion event

This event reports that the Item was deleted.

The table below shows the attributes of the Item deletion event.

Table 19‒19: Attributes of the Item deletion event

Attribute type

Item

Attribute name

Description

Issue timing

--

--

Deletion of an Item

Basic attribute

Event ID

--

00005543

Message

--

The item was deleted.

Extended

Common information

Importance

SEVERITY

Notice

Product name

PRODUCT_NAME

/HITACHI/JP1/AC

Object type

OBJECT_TYPE

INCIDENT

Object name

OBJECT_NAME

Incident

Object ID

OBJECT_ID

Target item ID

Occurrence

OCCURRENCE

DELETE

User property

Version

A10

Asset Console version

Item name

C11

Target Item name

Item definition ID

C12

Target Item definition ID

Legend:

--: Not applicable

(7) Attributes of the handling completion event

This event reports to JP1/IM that the handling of the problem loaded from JP1/IM was completed. From the JP1/IM's Event Console window, you can open the Problem Details dialog box for this event and view the handling details.

The table below shows the attributes of the handling completion event.

Table 19‒20: Attributes of the handling completion event

Attribute type

Item

Attribute name

Description

Issue timing

--

--

Clicking of the Complete button in the Edit Problem dialog box

Basic attribute

Event ID

--

00005581

Message

--

The problem was handled.

Extended

Common information

Importance

SEVERITY

Notice

Product name

PRODUCT_NAME

/HITACHI/JP1/AC

Object type

OBJECT_TYPE

ACTION

Object name

OBJECT_NAME

Problem

Object ID

OBJECT_ID

Problem ID of the target

Occurrence

OCCURRENCE

NOTICE

User property

Completed asset No.

ASSET_NO

Asset number of the target

Completed serial No.

EVENT_SEQNO

Event serial number of the target

Legend:

--: Not applicable

(8) Attributes of the problem status change event

This event reports that the problem was registered or changed. From JP1/IM's Event Console window, you can open the Problem Details dialog box for this event and view the change details.

You can also add the information to be reported in the user extension area of event information 0 to 31. For details about how to set managed items in the user extension area, see 19.2.2 Setting the user extension area of the problem status change event.

The table below shows the attributes of the problem status change event.

Table 19‒21: Attributes of the problem status change event

Attribute type

Item

Attribute name

Description

Issue timing

--

--

Problem registration

Basic attribute

Event ID

--

00005582

Message

--

The problem status was changed

Extended

Common information

Importance

SEVERITY

Notice

Product name

PRODUCT_NAME

/HITACHI/JP1/AC

Object type

OBJECT_TYPE

MAINTENANCE

Object name

OBJECT_NAME

Maintenance

Object ID

OBJECT_ID

Problem ID of the target

Occurrence

OCCURRENCE

New registration: ADD

Update: MODIFY

User property

Version

A10

Asset Console version

Managed No.

M11

Target managed No.

Event information 0 to 31

U00 to U31

User extension area

Legend:

--: Not applicable

(9) Attributes of the problem deletion event

This event reports that the problem was deleted.

The table below shows the attributes of the problem deletion event.

Table 19‒22: Attributes of the problem deletion event

Attribute type

Item

Attribute name

Description

Issue timing

--

--

Problem change

Basic attribute

Event ID

--

00005583

Message

--

The problem was deleted.

Extended

Common information

Importance

SEVERITY

Notice

Product name

PRODUCT_NAME

/HITACHI/JP1/AC

Object type

OBJECT_TYPE

MAINTENANCE

Object name

OBJECT_NAME

Maintenance

Object ID

OBJECT_ID

Problem ID of the target

Occurrence

OCCURRENCE

DELETE

User property

Version

A10

Asset Console version

Managed No.

M11

Target managed No.

Legend:

--: Not applicable

19.2.2 Setting the user extension area of the problem status change event

You can set managed items in the user extension area of the problem status change event and add the description of the report to be sent when the problem status changes.

Define the managed items to be set in the user extension area in the event attribute composition file (eventmap.ini).

The storage destination of the event attribute composition file and the method of setting the managed items are described below.

Storage destination for the event attribute composition file

Asset-Console-installation-folder\env

For use as a reference when creating an event attribute composition file, a sample file (eventmap.ini.org) that describes the default content of the event attribute composition file is provided in the aforementioned storage destination. Create an event attribute composition file by referencing this sample.

Managed item specification method

The following is the procedure for setting managed items by using the sample file (eventmap.ini.org) for an event attribute composition file:

Use a text editor to open eventmap.ini.org.

Describe in U12 to U31 the managed items to report, using the class.property format.

The only type of problem status change event you can define is the managed item in the maintenance history (Maintenance). If you define an item other than the managed item in the maintenance history, an error occurs during event issuance, and the event cannot be issued.

Change the file name to eventmap.ini and save it in Asset-Information-Manager-installation-folder\env.

The content to be reported in the problem status change event has now been set.

The figure below shows the content of the eventmap.ini.org file.

Figure 19‒1: eventmap.ini.org file

20 Management Information Details

This chapter presents the properties of the object classes provided by Asset Console and the details of properties.

It also describes import processing from the Import job menu, export processing from the Export job menu, the items to be imported by jamCsvImport.bat, and the items to be exported by jamCsvExport.bat.

20.1 Organization of classes

This section lists the classes provided by Asset Console and explains their relationships.

Details of the object classes and properties are provided in alphabetical order.

20.1.1 Object classes

The table below presents the class names and provides an overview of the object classes. It also indicates whether each object class is used for import/export processing and for user report creation.

Table 20‒1: List of object classes

Class name

Overview

Import/export

User reports

Job menu

jamCsvImport

jamCsvExport

#1

jamimport

jamexport#2

AddressGroup

IP group information

Y

Y

Y

AssetInfo

Asset information

Y

Y

Y

AssetUpdateRecord

Transfer log

N

Y

Y

Contract

Contract information

Y

Y

Y

ContractAssetHistory

Contract asset history

Y

J

Y

ContractCatalog

Company catalog

N

Y

N

ContractHistory

Contract history

Y

J

Y

DivisionInfo

Division information

Y

Y

N

GroupInfo

Group information

Y

Y

Y

HardwareInfo

Hardware information

Y

Y

Y

InstalledInfo

Installed software information

Y

Y

Y

InstalledList

Installed software list

Y

Y

Y

InstalledUpdateRecord

Software update log

N

J

Y

InstalledVirusDefInfo

Virus definition information

Y

Y

Y

IPAddress

IP address control information

Y

Y

Y

JobRoleInfo

Official authority

Y

Y

Y

LicenseInfo

License information

Y

Y

Y

LocationInfo

Location information

Y

Y

Y

MachineCatalog

Device catalog

Y

Y

N

Maintenance

Maintenance log

Y

Y

Y

NetworkInfo

Network information

Y

Y

Y

PatchInfo

Patch information

Y

Y

Y

PatchList

Patch name list

Y

Y

Y

RelationAssetInfo

Related asset information

N

J

N

RoleInfo

Role information

Y

Y

Y

SoftwareInfo

Software information

Y

Y

Y

SoftwareKeyInfo

Software key information

Y

Y

Y

SoftwareList

Software list

Y

Y

Y

UpdateRecord

Device change log

N

J

Y

UserInfo

User information

Y

Y

Y

VolumeContract

Volume contract information

Y

Y

Y

Legend:

Y: Used

N: Not used

J: Can only be exported with the jamexport command. (Importing with the jamimport command is not supported.)

#1

The following import and export methods are used:

Import by the Import job menu and jamCsvImport.bat command

Export by the Export job menu and jamCsvExport.bat command

#2

The following import and export methods are used:

Import by the jamimport command

Export by the jamexport command

20.1.2 Association classes

The table below presents the class names and provides an overview of the association classes. It also indicates whether each association class is used for import/export processing and for user report creation.

Table 20‒2: List of association classes

Class name

Overview

Import/export

User reports

Job menu

jamCsvImport

jamCsvExport

#1

jamimport

jamexport#2

AssetUpdateRecLink

Change log

N

J

Y

AuthorityLink

User and authority link

Y

Y

Y

ContractAssetHistoryLink

Contract history and contract asset history

N

J

Y

ContractHistoryLink

Contract information and contract history

N

J

Y

ContractLeaseLink

Lease contract link

Y

Y

Y

ContractMaintenanceLink

Maintenance contract link

Y

Y

Y

ContractRentalLink

Rental contract link

Y

Y

Y

DivisionLink

Division information and group information

Y

Y

N

DivisionUserLink

Division information and user information

Y

Y

N

HardwareLink

Hardware link

N

J

Y

InstalledLink

Installed software link

N

J

Y

InstalledListLink

Installed software list link

N

J

Y

InstalledVirusDefLink

Installed virus definition information link

N

J

Y

IPAddressLink

IP address link

Y

Y

Y

JobRoleInfo

User and official authority link

Y

Y

Y

LicenseLink

License link

N

J

Y

MachinePermitLink

Device and key link

Y

Y

Y

MemberLink

User and member link

Y

Y

Y

NetworkLink

Network link

N

J

Y

PatchLink

Patch information link

N

J

Y

PatchListLink

Patch name list link

N

J

Y

RelationAssetLink

Asset information and related asset information

N

J

N

SoftwareKeyLink

Software key link

N

J

Y

SoftwareLicenseLink

Software license link

N

J

Y

SoftwareLink

Software assets link

N

J

Y

SoftwareListLink

Software list and asset link

N

J

Y

SoftwareMapLink

Software list and installed software link

N

J

Y

UserPermitLink

User and key link

Y

Y

Y

VolumeContractLink

Volume contract link

Y

Y

Y

Legend:

Y: Used

N: Not used

J: Can only be exported with the jamexport command. (Importing with the jamimport command is not supported.)

#1

The following import and export methods are used:

Import by the Import job menu and jamCsvImport.bat command

Export by the Export job menu and jamCsvExport.bat command

#2

The following import and export methods are used:

Import by the jamimport command

Export by the jamexport command

20.1.3 Relationships between classes

The following figure shows the relationships between object classes and the association classes that represent the relationships between classes:

Figure 20‒1: Relationships between classes

20.1.4 Data types indicating property values

When a property is added or changed in a class, the value of the property is represented by the data type shown below. This table presents the correspondence between the value permitted for a property and the data type.

Table 20‒3: Correspondence of data types

Data type

Permitted value

uint8

Unsigned 8-bit integer in the range 0-255

uint16

Unsigned 16-bit integer in the range 0 to 65,535

uint32

Unsigned 32-bit integer in the range 0 to 4,294,967,295

uint64

Unsigned 64-bit integer in the range 0 to 18,446,744,073,709,551,615

string[n]

Character string (n: maximum length of character string)

date

Date YYYY-MM-DD or YYYY/MM/DD

20.2 Lists of properties for object classes

This section presents the details, data type, maximum length, and assigned codes of each property that belongs to an object class provided by Asset Console.

It also describes the following:

Notes about specifying property values when items are imported by the Import job menu, jamCsvImport.bat, and the jamimport command

Values that are automatically set when items are imported by the Import job menu and jamCsvImport.bat

Items that must be specified when the jamimport command is used for import processing

For details about the items that must be specified when the Import job menu and jamCsvImport.bat are used for import processing, see 20.4 Items to be imported or exported using a job menu.

20.2.1 AddressGroup (IP group information)

This class manages IP address groups.

You can import and export this class.

You can also specify this class as a search condition when creating a user report.

The following table lists the properties of AddressGroup.

Table 20‒4: Properties of AddressGroup

Property

Key

Description

Type [maximum length (bytes)]

Remarks

Specification in jamimport

CreationClassName

K

CCN

string[32]

This is AddressGroup.

M

DHCPServerName

N

DHCP server name

string[255]

This is the DHCP server name.

O

EndIPAddress

N

End IP address

string[70]

This is the end address in the IP group.

M

Gateway

N

Gateway address

string[70]

This is the gateway of the IP group.

O

GroupID

N

Group ID

string[64]

This is a corresponding group ID for a group-specific IP group.

O

IPGroupID

K

IP group ID

uint32

This is a unique ID for identifying the IP group. When new information is imported, assign a unique value in the range from 10001 to 1000000000.

M

IPGroupName

N

IP group name

string[255]

This is the name of the IP group.

M

LocationID

N

Location ID

string[64]

This is a corresponding location ID for a location-specific IP group.

O

ManagerialUserID

N

User ID of administrator

string[64]

This is the user ID of the administrator of the IP group.

O

Purpose

N

Purpose

string[255]

This is the purpose of the IP group.

O

StartIPAddress

N

Start IP address

string[70]

This is the start address of the address of the

IP group.

M

SubnetMask

N

Subnet mask

string[70]

This is the subnet mask of the IP group.

M

UpdateTime

N

Update control

string[20]

This information is used to control concurrent updating of information.

O

UserPropertyArea_1#

N

User property area-1

string[255]

This item can manage a maximum of 255 bytes of information.

With a window operation, multiple character string lines can be specified.

O

UserPropertyArea_2#

N

User property area-2

string[255]

O

UserPropertyCode_1#

N

User property code-1

string[64]

This item can control code information.

O

UserPropertyCode_2#

N

User property code-2

string[64]

O

UserPropertyField128_1#

N

User property field 128-1

string[128]

This item can control a maximum of 128 bytes of information.

O

UserPropertyField128_2#

N

User property field 128-2

string[128]

O

UserPropertyField255_1#

N

User property field 255-1

string[255]

This item can manage a maximum of 255 bytes of information.

O

UserPropertyField255_2#

N

User property field 255-2

string[255]

O

Legend:

K: Key property

N: Non-key property

M: Mandatory property during registration

O: Optional property

#

This is an extended property. You can add managed items by editing the display name of this property and setting it to be displayed using the Customize Managed Items job menu.

20.2.2 AssetInfo (asset information)

This class manages information such as the users and groups of software assets and devices, such as system, network, and accessories.

You can import and export this class. For details about importing by jamCsvImport.bat, see the section describing import processing by the Import job menu.

You can also specify this class as a search condition when creating a user report.

The following table lists the properties of AssetInfo.

Table 20‒5: Properties of AssetInfo

Property

Key

Description

Type [maximum length (bytes)]

Remarks

Specification in jamimport

AssetBranchNo

N

Branch number

uint32

This is a branch number when a license is partitioned.

When new information is imported, assign a unique value in the range from 10001 to 1000000000.

If the Import job menu is used for importing, 0 is always set in Device information.

M

AssetID

K

Asset ID

uint32

This is a unique ID for identifying the asset.

When new information is imported, assign a unique value in the range from 10001 to 1000000000.

If the Import job menu is used for importing and this property is omitted, the ID is assigned automatically.

M

AssetKind

N

Asset type

string[3]

See Asset type.

For 001, make sure that the object class HardwareInfo is imported.

For 002, make sure that the object class SoftwareInfo is imported.

M

AssetNo

N

Asset No.

string[512]

This is a unique asset number managed by the user.

If the Import job menu is used for importing and this property is omitted, the ID is assigned automatically.

M

AssetStatus

N

Status

string[3]

See Status.

This property can be registered if AssetKind is 001.

If the Import job menu is used for importing and this property is omitted, Stock is set.

R

AssetWorkKind

N

Usage management

string[3]

See Usage management.

If the Import job menu is used for importing, the default value must be set.

M

CreationClassName

K

CCN

string[32]

This is AssetInfo.

M

DMLastUpdateTime

N

Last updated date of ITDM2

date

This is the last update date of the deletion history information, the information about a machine on which JP1/IT Desktop Management 2 - Manager is not installed, or the system configuration information acquired from JP1/IT Desktop Management 2 - Manager, whichever is the most recent.

O

DMStatus

N

ITDM2 Agent installation status

string[3]

See ITDM2 Agent installed status.

R

EndDate

N

End date of use

date

This is the expiration date, such as for a trial-usage software asset.

O

GroupID

N

Group ID

string[64]

This is the group ID corresponding to the group name.

If you are specifying this information for an import operation, specify the same value as for the corresponding object class GroupInfo.

O

GroupName

N

Group name

string[1024]

This is the group information that represents the entire hierarchy from the top, such as Head Office/Sales Dept./Section1.

If you are specifying this information for an import operation, specify the same value as for the corresponding object class GroupInfo.

O

GroupName_EN

N

Group name (English)

string[1024]

This is the group information that represents the entire hierarchy from the top, such as Head Office/Sales Dept./Section1.

If you are specifying this information for an import operation, specify the same value as for the corresponding object class GroupInfo.

O

InventoryKey

N

Host identifier

string[128]

This is the ID key for assigning asset information from JP1/IT Desktop Management 2 - Manager.

Specify an assigned key that is appropriate to JP1/IT Desktop Management 2 - Manager's working key.

If the Import job menu is used for importing, this property is

applicable only when Device information is selected for

Category.

O

LocationID

N

Location ID

string[64]

This is the location ID

corresponding to the location name.

If you are specifying this

information for an import

operation, specify the same

value as for the corresponding

object class LocationInfo.

O

LocationName

N

Location

string[1024]

This is the location information that represents the entire hierarchy from the top, such as New York/A building/First floor.

If you are specifying this information for an import operation, specify the same value as for the corresponding object class LocationInfo.

O

LocationName_EN

N

Location

string[1024]

This is the location information in English that represents the entire hierarchy from the top, such as New York/A building/First floor.

If you are specifying this information for an import operation, specify the same value as for the corresponding object class LocationInfo.

O

ManagerialGroup

N

Managed group

string[1024]

This is the managerial group for the asset.

O

ManagerialGroup_EN

N

Managed group

string[1024]

This is the managerial group for the asset in English.

O

ManagerialGroupID

N

Managed group ID

string[64]

This is the ID for the managerial group.

If you are specifying this information for an import operation, specify the same value as for the corresponding object class GroupInfo.

O

ManagerialUser

N

Administrator

string[255]

This is the asset manager. You can specify a user name that is not found in user management information.

O

ManagerialUser_EN

N

Administrator

string[255]

This is the asset manage in English.

O

ManagerialUserID

N

User ID of administrator

string[64]

This is the ID for the administrator.

If you are specifying this information for an import operation, specify the same value as for the corresponding object class UserInfo.

O

Note

N

Notes

string[255]

This is notes on asset information.

O

PurchasePrice

N

Purchase price

string[15]

This is the purchase price of the asset.

O

Purpose

N

Purpose

string[255]

This is the purpose of the asset.

O

RegistrationDate

N

Registration date

date

This is the date the asset was registered.

If the Import job menu is used for importing and this property is omitted, the date the import processing was executed is set.

R

SoftwareStatus

N

Software status

string[3]

See Software status.

This property can be registered if AssetKind is 002.

If the Import job menu is used for importing, this property is applicable only when Software information is selected for Category. If this property is omitted, Active is set.

R

StartDate

N

Start date of use

date

This is the date use of the asset began.

O

StocktakingDate

N

Stocktaking date

date

This is the date stocktaking was performed.

O

UpdateTime

N

Update control

string[20]

This information is used to control concurrent updating of information.

O

UpdateUser

N

Update user name

string[255]

This is a user ID of the user who updates the asset information. It is used when Asset Console updates data, and a user ID is set when information is changed in the Device Details dialog box. However, the user ID of the update user is not set in the following cases:

When software information is updated

When data importing is executed

When ITDM2 management information is acquired from JP1/IT Desktop Management 2 - Manager

When an Item is used to update information

O

UserID

N

User ID

string[64]

This is the user ID for the user name.

If you are specifying this information for an import operation, specify the same value as for the corresponding object class UserInfo.

O

UserName

N

User name

string[512]

This the user name.

If you are specifying this information for an import operation, specify the same value as for the corresponding object class UserInfo.

O

UserName_EN

N

User name (English)

string[512]

This the user name in English.

If you are specifying this information for an import operation, specify the same value as for the corresponding object class UserInfo.

O

UserPropertyArea_1#

N

User property area-1

string[255]

This item can manage a maximum of 255 bytes of information.

With a window operation, multiple character string lines can be specified.

O

UserPropertyArea_2#

N

User property area-2

string[255]

O

UserPropertyCode_1#

N

User property code-1

string[64]

This item can control code information.

O

UserPropertyCode_2#

N

User property code-2

string[64]

O

UserPropertyCode_3#

N

User property code-3

string[64]

O

UserPropertyCode_4#

N

User property code-4

string[64]

O

UserPropertyCode_5#

N

User property code-5

string[64]

O

UserPropertyCode_6#

N

User property code-6

string[64]

O

UserPropertyDate_1#

N

User property date-1

date

Each of these items manages date information.

O

UserPropertyDate_2#

N

User property date-2

date

O

UserPropertyDate_3#

N

User property date-3

date

O

UserPropertyDate_4#

N

User property date-4

date

O

UserPropertyDate_5#

N

User property date-5

date

O

UserPropertyDate_6#

N

User property date-6

date

O

UserPropertyField128_1#

N

User property field 128-1

string[128]

This item can control a maximum of 128 bytes of information.

O

UserPropertyField128_2#

N

User property field 128-2

string[128]

O

UserPropertyField255_1#

N

User property field 255-1

string[255]

This item can manage a maximum of 255 bytes of information.

O

UserPropertyField255_2#

N

User property field 255-2

string[255]

O

UserPropertyField32_1#

N

User property field 32-1

string[32]

Each of these items can manage a maximum of 32 bytes of information.

O

UserPropertyField32_2#

N

User property field 32-2

string[32]

O

UserPropertyField32_3#

N

User property field 32-3

string[32]

O

UserPropertyField32_4#

N

User property field 32-4

string[32]

O

UserPropertyField32_5#

N

User property field 32-5

string[32]

O

UserPropertyField32_6#

N

User property field 32-6

string[32]

O

UserPropertyField64_1#

N

User property field 64-1

string[64]

Each of these items can manage a maximum of 64 bytes of information.

O

UserPropertyField64_2#

N

User property field 64-2

string[64]

O

UserPropertyUint_1#

N

User property unit-1

uint32

Each of these items can manage numeric information.

O

UserPropertyUint_2#

N

User property unit-2

uint32

O

UserPropertyUint_3#

N

User property unit-3

uint32

O

UserPropertyUint_4#

N

User property unit-4

uint32

O

UserPropertyUint_5#

N

User property unit-5

uint32

O

UserPropertyUint_6#

N

User property unit-6

uint32

O

Legend:

K: Key property

N: Non-key property

M: Mandatory property during registration (omitting this property results in an error)

R: Property whose specification is recommended during new registration (omitting this property does not result in an error)

O: Optional property

#

This is an extended property. You can add managed items by editing the display name of this property and setting it to be displayed using the Customize Managed Items job menu.

The tables below provide details of the property codes.

Table 20‒6: Asset type

Code

Display value

001

Hardware

002

Software

Table 20‒7: Status

Code

Display value

002

Active

301

Stock

501

Restore

601

Scrap

701

Pre-Scrap

999

Erase

Table 20‒8: Usage management

Code

Display value

001

Used

002

Unused

Table 20‒9: ITDM2 Agent installed status

Code

Display value

001

Installed

002

Not installed

Table 20‒10: Software status

Code

Display value

001

Active

501

Restore

601

Scrap

999

Erase

20.2.3 AssetUpdateRecord (transfer log)

This class manages historical information about assets' management groups and locations.

You can import and export this class with the jamimport and jamexport commands, respectively.

You can also specify this class as a search condition when creating a user report.

The following table lists the properties of AssetUpdateRecord.

Table 20‒11: Properties of AssetUpdateRecord

Property

Key

Description

Type [maximum length (bytes)]

Remarks

Specification in jamimport

AssetID

K

Asset ID

uint32

This is the ID of the asset.

If you are specifying this information for an import operation, specify the same value as for the corresponding object class AssetInfo.

M

BaseCreationClassName

N

BaseCCN

string[32]

This is the name of the source class, which is AssetInfo.

M

CreationClassName

K

CCN

string[32]

This is AssetUpdateRecord.

M

GroupName

N

Group name

string[1024]

This is the group information that represents the entire hierarchy from the top, such as Head Office/Sales Dept./Section1.

O

GroupName_EN

N

Group name (English)

string[1024]

This is the group information in English that represents the entire hierarchy from the top, such as Head Office/Sales Dept./Section1.

O

HistoryUpdateDate

K

Update date/time

date

This is the date the group information was updated.

M

LocationName

N

Location

string[1024]

This is the location information that represents the entire hierarchy from the top, such as New York/A building/First floor.

O

LocationName_EN

N

Location

string[1024]

This is the location information in English that represents the entire hierarchy from the top, such as New York/A building/First floor.

O

UserName

N

User name

string[512]

This the user name.

O

UserName_EN

N

User name (English)

string[512]

This the user name in English.

O

Legend:

K: Key property

N: Non-key property

M: Mandatory property during registration

O: Optional property

20.2.4 Contract (contract information)

This class manages a device for a maintenance or lease contract.

You can import and export this class. For details about importing by jamCsvImport.bat, see the section describing import processing by the Import job menu.

You can also specify this class as a search condition when creating a user report.

To import this class and associate it with a contracted asset, also import the association class ContractLeaseLink (lease contract link), ContractMaintenanceLink (maintenance contract link), or ContractRentalLink (rental contract link).

The following table lists the properties of Contract.

Table 20‒12: Properties of Contract

Property

Key

Description

Type [maximum length (bytes)]

Remarks

Specification in jamimport

Address

N

Contact post address

string[255]

This is the contracted company's address.

O

Company

N

Contracted company

string[255]

This is the name of the contracted company.

R

ContactInfo

N

Contact phone/e-mail

string[255]

This is contact information at the contracted company.

O

ContactInfo_2#

N

Contact phone/e-mail 2

string[255]

O

ContactInfo_3#

N

Contact phone/e-mail 3

string[255]

O

ContactName

N

Contact person

string[512]

These are the contact people at the contracted company.

O

ContactName_2#

N

Contact person 2

string[512]

O

ContactName_3#

N

Contact person 3

string[512]

O

Contents

N

Contents

string[255]

This is the contents of the contract.

O

ContractDate

N

Contract date

date

This is the date of the contract.

R

ContractID

K

Contract ID

uint32

This is a unique ID that identifies the contract.

When new information is imported, assign a unique value in the range from 10001 to 1000000000.

M

ContractKind

N

Category

string[3]

See Category.

M

ContractNo

N

Contract No.

string[60]

This is the contract number.

R

ContractObject

N

Subject

string[3]

See Subject.

If the Import job menu is used for importing and this property is omitted, Device is set.

M

ContractStatus

N

Status

string[3]

See Status.

If the Import job menu is used for importing and this property is omitted, Under contract is set.

M

CreationClassName

K

CCN

string[32]

This is Contract.

M

EndDate

N

Contract end date

date

This is the contract termination date.

R

Explanation

N

Description

string[255]

This is a description of the contract.

O

GroupID

N

Group ID

string[64]

This is a unique ID that identifies the group name.

O

MonthlyPrice

N

Monthly

string[15]

This is the monthly charge.

O

RenewalTimes

N

Frequency

uint32

This is the number of times the contract was renewed.

R

StartDate

N

Contract start date

date

This is the start date of the contract.

R

TotalPrice

N

Total

string[15]

This is the total contract cost.

O

UpdateTime

N

Update control

string[20]

This information is used to control concurrent updating of information.

O

UserPropertyArea_1#

N

User property area-1

string[255]

This item can manage a maximum of 255 bytes of information.

With a window operation, multiple character string lines can be specified.

O

UserPropertyArea_2#

N

User property area-2

string[255]

O

UserPropertyCode_1#

N

User property code-1

string[64]

This item can control code information.

O

UserPropertyCode_2#

N

User property code-2

string[64]

O

UserPropertyField128_1#

N

User property field 128-1

string[128]

This item can control a maximum of 128 bytes of information.

O

UserPropertyField128_2#

N

User property field 128-2

string[128]

O

UserPropertyField255_1#

N

User property field 255-1

string[255]

This item can manage a maximum of 255 bytes of information.

O

UserPropertyField255_2#

N

User property field 255-2

string[255]

O

Legend:

K: Key property

N: Non-key property

M: Mandatory property during registration (omitting this property results in an error)

R: Property whose specification is recommended during new registration (omitting this property does not result in an error)

O: Optional property

#

This is an extended property. You can add managed items by editing the display name of this property and setting it to be displayed using the Customize Managed Items job menu.

The tables below provide details of the property codes.

Table 20‒13: Category

Code

Display value

100

Maintenance

200

Lease

300

Rental

Table 20‒14: Subject

Code

Display value

001

Device

002

Software

Table 20‒15: Status

Code

Display value

001

Under contract

501

Expire

999

Erase

20.2.5 ContractAssetHistory (contract asset history)

This class manages contract asset history.

You can import or export this class.

You can also specify this class as a search condition when creating a user report.

The following table lists the properties of ContractAssetHistory.

Table 20‒16: Properties of ContractAssetHistory

Property

Key

Description

Type [maximum length (bytes)]

Remarks

AssetID

K

Asset ID

uint32

This is the asset ID of the asset covered by the contract.

AssetNo

N

Asset No.

string[60]

This is the asset number of the asset covered by the contract.

ContractID

K

Contract ID

uint32

This is the contract ID of the corresponding contract.

CreationClassName

K

CCN

string[32]

This is ContractAssetHistory.

RenewalDate

N

Update date/time

date

This is the contract renewal date.

Frequency

K

Frequency

uint32

This is the number of times the corresponding contract has been renewed.

Legend:

K: Key property

N: Non-key property

20.2.6 ContractCatalog (company catalog)

This class manages information about a contracted company.

You can import and export this class with the jamimport and jamexport commands, respectively.

The following table lists the properties of ContractCatalog.

Table 20‒17: Properties of ContractCatalog

Property

Key

Description

Type [maximum length (bytes)]

Remarks

Specification in jamimport

Address

N

Contact post address

string[255]

This is the contracted company's address.

O

Company

N

Contracted company

string[255]

This is the name of the contracted company.

R

ContactInfo

N

Contact phone/e-mail

string[255]

This is contact information at the contracted company.

O

ContactInfo_2#

N

Contact phone/e-mail 2

string[255]

O

ContactInfo_3#

N

Contact phone/e-mail 3

string[255]

O

ContactName

N

Contact person

string[512]

These are the contact people at the contracted company.

O

ContactName_2#

N

Contact person 2

string[512]

O

ContactName_3#

N

Contact person 3

string[512]

O

CreationClassName

K

CCN

string[32]

This is ContractCatalog.

M

HistoryUpdateDate

K

Update date/time

date

This is the date the contract information was updated.

M

UpdateTime

N

Update control

string[20]

This information is used to control concurrent updating of information.

O

UserPropertyArea_1#

N

User property area-1

string[255]

This item can manage a maximum of 255 bytes of information.

With a window operation, multiple character string lines can be specified.

O

UserPropertyArea_2#

N

User property area-2

string[255]

O

UserPropertyCode_1#

N

User property code-1

string[64]

This item can control code information.

O

UserPropertyCode_2#

N

User property code-2

string[64]

O

UserPropertyField128_1#

N

User property field 128-1

string[128]

This item can control a maximum of 128 bytes of information.

O

UserPropertyField128_2#

N

User property field 128-2

string[128]

O

UserPropertyField255_1#

N

User property field 255-1

string[255]

This item can manage a maximum of 255 bytes of information.

O

UserPropertyField255_2#

N

User property field 255-2

string[255]

O

Legend:

K: Key property

N: Non-key property

M: Mandatory property during registration (omitting this property results in an error)

R: Property whose specification is recommended during new registration (omitting this property does not result in an error)

O: Optional property

#

This is an extended property. You can add managed items by editing the display name of this property and setting it to be displayed using the Customize Managed Items job menu.

20.2.7 ContractHistory (contract history)

This class manages contract history. It manages the updated content of the corresponding contract information as history.

You can import or export this class.

You can also specify this class as a search condition when creating a user report.

The following table lists the properties of ContractHistory.

Table 20‒18: Properties of ContractHistory

Property

Key

Description

Type [maximum length (bytes)]

Remarks

Address

N

Contact post address

string[255]

This is the address for the corresponding contract information after renewal.

Company

N

Contracted company

string[255]

This is the contracted company for the corresponding contract information after renewal.

ContactInfo

N

Contact phone/e-mail

string[255]

This is the contact phone/e-mail for the corresponding contract information after renewal.

ContactInfo_2

N

Contact phone/e-mail 2

string[255]

This is contact phone/e-mail 2 for the corresponding contract information after renewal.

ContactInfo_3

N

Contact phone/e-mail 3

string[255]

This is contact phone/e-mail 3 for the corresponding contract information after renewal.

ContactName

N

Contact person

string[512]

This is the contact person for the corresponding contract information after renewal.

ContactName_2

N

Contact person 2

string[512]

This is contact person 2 for the corresponding contract information after renewal.

ContactName_3

N

Contact person 3

string[512]

This is contact person 3 for the corresponding contract information after renewal.

Contents

N

Contents

string[255]

This is the contract contents for the corresponding contract information after renewal.

ContractDate

N

Contract date

date

This is the contract date for the corresponding contract information after renewal.

ContractID

K

Contract ID

uint32

This is the contract ID for the corresponding contract information after renewal.

ContractKind

N

Category

string[255]

This is the category for the corresponding contract information after renewal.

ContractNo

N

Contract No.

string[60]

This is the contract number for the corresponding contract information after renewal.

ContractObject

N

Subject

string[255]

This is the subject for the corresponding contract information after renewal.

ContractStatus

N

Status

string[255]

This is the status for the corresponding contract information after renewal.

CreationClassName

K

CCN

string[32]

This is the CCN for the corresponding contract information after renewal.

EndDate

N

Contract end date

date

This is the contract end date for the corresponding contract information after renewal.

Explanation

N

Description

string[255]

This is the description for the corresponding contract information after renewal.

GroupName

N

Group name

string[1024]

This is the group name for the corresponding contract information after renewal.

MonthlyPrice

N

Monthly

string[15]

This is the contract amount (monthly) for the corresponding contract information after renewal.

RenewalDate

N

Update date/time

date

This is the update date and time for the corresponding contract information after renewal.

RenewalTimes

K

Frequency

uint32

This is the number of times the corresponding contract information has been renewed.

StartDate

N

Contract start date

date

This is the contract start date for the corresponding contract information after renewal.

TotalPrice

N

Total

string[15]

This is the contract amount (total) for the corresponding contract information after renewal.

UserID

N

Update user ID

string[64]

This is the user ID of the user who updated the contract information.

UserPropertyArea_1

N

User property area-1

string[255]

This is the user property area-1 for the corresponding contract information after renewal.

UserPropertyArea_2

N

User property area-2

string[255]

This is the user property area-2 for the corresponding contract information after renewal.

UserPropertyCode_1

N

User property code-1

string[255]

This is the user property code-1 for the corresponding contract information after renewal.

UserPropertyCode_2

N

User property code-2

string[255]

This is the user property code-2 for the corresponding contract information after renewal.

UserPropertyField128_1

N

User property field 128-1

string[128]

This is the user property field 128-1 for the corresponding contract information after renewal.

UserPropertyField128_2

N

User property field 128-2

string[128]

This is the user property field 128-2 for the corresponding contract information after renewal.

UserPropertyField255_1

N

User property field 255-1

string[255]

This is the user property field 255-1 for the corresponding contract information after renewal.

UserPropertyField255_2

N

User property field 255-2

string[255]

This is the user property field 255-2 for the corresponding contract information after renewal.

Legend:

K: Key property

N: Non-key property

20.2.8 DivisionInfo (division information)

This class manages the division information registered in a group.

You can import or export this class. For details about importing by jamCsvImport.bat, see the section describing import processing by the Import job menu.

The following table lists the properties of DivisionInfo.

Table 20‒19: Properties of DivisionInfo

Property

Key

Description

Type [maximum length (bytes)]

Remarks

Specification in jamimport

CreationClassName

K

CCN

string[32]

This is DivisionInfo.

M

DivisionID

K

Division ID

string[64]

This is a unique ID for identifying a division.

O

DivisionName

N

Division name

string[128]

This is the name of the division.

M

GroupID

N

Group ID

string[64]

This is the group ID to which the division belongs.

M

Legend:

K: Key property

N: Non-key property

M: Mandatory property during registration (omitting this property results in an error)

O: Optional property

20.2.9 GroupInfo (group information)

This class manages information about groups.

You can import or export this class. For details about importing by jamCsvImport.bat, see the section describing import processing by the Import job menu.

You can also specify this class as a search condition when creating a user report.

The following table lists the properties of GroupInfo.

Table 20‒20: Properties of GroupInfo

Property

Key

Description

Type [maximum length (bytes)]

Remarks

Specification in jamimport

AdGuid

N

ADGUID

string[32]

This is the identifier of JP1/IT Desktop Management 2 - Manager directory information.

O

CostPriceCode

N

Cost group code

string[10]

This is the cost's price code.

O

CreationClassName

K

CCN

string[32]

This is GroupInfo.

M

Explanation

N

Description

string[255]

This is a description of the group.

O

FullPathName

N

Group name

string[1024]

This is the group information that represents the entire hierarchy from the top, such as Head Office/Sales Dept./Section1.

M

FullPathName_EN

N

Group name (English)

string[1024]

This is the group information in English that represents the entire hierarchy from the top, such as Head Office/Sales Dept./Section1.

O

GroupCode

N

Group code

string[10]

This is the code for the group.

O

GroupID

K

Group ID

string[64]

This is a unique ID that identifies the group.

To perform registration by importing new IDs from a file, make sure that unique IDs not in the range from 1000000001 to 9999999999 are assigned.

M

GroupName

N

Local name

string[256]

This is the name of the group.

M

GroupName_EN

N

Local name

string[256]

This is the name of the group in English.

If the Import job menu is used for importing and this property is omitted, the value for Group ID is set.

R

ManagedLabel

N

Managed label

string[20]

This is the managed label.

O

UpdateInd

N

Update indicator

uint32

This information is used by the asset management system. Do not update it.

O

UpdateTime

N

Update control

string[20]

This information is used to control concurrent updating of information.

O

UpperLinkID

N

Upper Group ID

string[64]

This is the ID of the upper group.

O

UserPropertyArea_1#

N

User property area-1

string[255]

This item can manage a maximum of 255 bytes of information.

With a window operation, multiple character string lines can be specified.

O

UserPropertyArea_2#

N

User property area-2

string[255]

O

UserPropertyCode_1#

N

User property code-1

string[64]

This item can control code information.

O

UserPropertyCode_2#

N

User property code-2

string[64]

O

UserPropertyField128_1#

N

User property field 128-1

string[128]

This item can control a maximum of 128 bytes of information.

O

UserPropertyField128_2#

N

User property field 128-2

string[128]

O

UserPropertyField255_1#

N

User property field 255-1

string[255]

This item can manage a maximum of 255 bytes of information.

O

UserPropertyField255_2#

N

User property field 255-2

string[255]

O

Legend:

K: Key property

N: Non-key property

M: Mandatory property during registration (omitting this property results in an error)

R: Property whose specification is recommended during new registration (omitting this property does not result in an error)

O: Optional property

#

This is an extended property. You can add managed items by editing the display name of this property and setting it to be displayed using the Customize Managed Items job menu.

20.2.10 HardwareInfo (hardware information)

This class manages information about all hardware assets used in the asset management system, such as system, network, and accessories.

You can import or export this class. You can import and export this class. For details about importing by jamCsvImport.bat, see the section describing import processing by the Import job menu.

You can also specify this class as a search condition when creating a user report.

The following table lists the properties of HardwareInfo.

Table 20‒21: Properties of HardwareInfo

Property

Key

Description

Type [maximum length (bytes)]

Remarks

Specification in jamimport

AssetID

K

Asset ID

uint32

This is the ID of the asset.

If you are specifying this information for an import operation, specify the same value as for the corresponding object class AssetInfo.

M

CircuitSpeed

N

Line speed

uint32

The value is in kbps.

O

ComputerID

N

Computer ID

string[200]

This is JP1/IT Desktop Management 2 - Manager management information. When importing the class, do not specify this property during new registration.

O

CPUClock

N

Processor speed

uint32

The value is in MHz.

O

CPUNumber

N

Number of processors

uint16

This is the number of CPUs.

O

CPUType

N

CPU

string[5]

See CPU type.

O

CreationClassName

K

CCN

string[32]

This is HardwareInfo.

M

Developer

N

Developer

string[512]

This is the developer of the device.

O

HostName

N

Host name

string[512]

This is the host name of the device.

It is converted into lower-case letters.

O

IPAddress

N

IP address

string[15]

This is the IP address of the device.

IP address management using IP address control is not applicable to this property.

O

MACAddress

N

MAC address

string[17]

This is the MAC address of the device.

It is converted into lower-case letters and normalized.

O

MachineKind

N

Device type

string[5]

See Device type.

If the Import job menu is used for importing and this property is omitted, PC is set.

R

MBSAVersion

N

MBSA version

string[200]

This is the MBSA version installed on the device.

O

MemorySize

N

Memory

uint64

The value is in megabytes.

O

Model

N

Model

string[512]

This is the device model.

O

ModelKind

N

Composition

string[3]

See Composition.

O

MonitorKind

N

Monitor type

string[3]

See Monitor type.

O

MonitorResolution

N

Monitor resolution

string[3]

See Monitor resolution.

O

MonitorSize

N

Monitor size

uint16

This is the monitor size.

O

Name

N

Device name

string[512]

This is the name of the device.

O

NumberOFPort

N

Number of ports

uint32

This is the number of ports on the device.

O

OSInfo

N

OS

string[512]

This is the OS information for the device.

O

OSVersion

N

OS version

string[200]

This is the OS version of the device.

O

RemainHDSize

N

Hard disk free space

uint64

The value is in megabytes.

O

SerialNo

N

Serial No.

string[1024]

This is the serial number of the device.

O

Specification

N

Specification

string[255]

This is the device's specifications.

O

TotalHDSize

N

Hard disk sizes

uint64

The value is in megabytes.

O

UpdateTime

N

Update control

string[20]

This information is used to control concurrent updating of information.

O

UserPropertyArea_1#

N

User property area-1

string[255]

This item can manage a maximum of 255 bytes of information.

With a window operation, multiple character string lines can be specified.

O

UserPropertyArea_2#

N

User property area-2

string[255]

O

UserPropertyArea_3#

N

User property area-3

string[255]

O

UserPropertyArea_4#

N

User property area-4

string[255]

O

UserPropertyCode_1#

N

User property code-1

string[64]

This item can control code information.

O

UserPropertyCode_2#

N

User property code-2

string[64]

O

UserPropertyCode_3#

N

User property code-3

string[64]

O

UserPropertyCode_4#

N

User property code-4

string[64]

O

UserPropertyCode_5#

N

User property code-5

string[64]

O

UserPropertyCode_6#

N

User property code-6

string[64]

O

UserPropertyCode_7#

N

User property code-7

string[64]

O

UserPropertyCode_8#

N

User property code-8

string[64]

O

UserPropertyCode_9#

N

User property code-9

string[64]

O

UserPropertyCode_10#

N

User property code-10

string[64]

O

UserPropertyCode_11#

N

User property code-11

string[64]

O

UserPropertyCode_12#

N

User property code-12

string[64]

O

UserPropertyDate_1#

N

User property date-1

date

Each of these items manages date information.

O

UserPropertyDate_2#

N

User property date-2

date

O

UserPropertyDate_3#

N

User property date-3

date

O

UserPropertyDate_4#

N

User property date-4

date

O

UserPropertyDate_5#

N

User property date-5

date

O

UserPropertyDate_6#

N

User property date-6

date

O

UserPropertyField128_1#

N

User property field 128-1

string[128]

This item can control a maximum of 128 bytes of information.

O

UserPropertyField128_2#

N

User property field 128-2

string[128]

O

UserPropertyField128_3#

N

User property field 128-3

string[128]

O

UserPropertyField128_4#

N

User property field 128-4

string[128]

O

UserPropertyField128_5#

N

User property field 128-5

string[128]

O

UserPropertyField128_6#

N

User property field 128-6

string[128]

O

UserPropertyField128_7#

N

User property field 128-7

string[128]

O

UserPropertyField128_8#

N

User property field 128-8

string[128]

O

UserPropertyField255_1#

N

User property field 255-1

string[255]

This item can manage a maximum of 255 bytes of information.

O

UserPropertyField255_2#

N

User property field 255-2

string[255]

O

UserPropertyField255_3#

N

User property field 255-3

string[255]

O

UserPropertyField255_4#

N

User property field 255-4

string[255]

O

UserPropertyField255_5#

N

User property field 255-5

string[255]

O

UserPropertyField255_6#

N

User property field 255-6

string[255]

O

UserPropertyField255_7#

N

User property field 255-7

string[255]

O

UserPropertyField255_8#

N

User property field 255-8

string[255]

O

UserPropertyField32_1#

N

User property field 32-1

string[32]

Each of these items can manage a maximum of 32 bytes of information.

O

UserPropertyField32_2#

N

User property field 32-2

string[32]

O

UserPropertyField32_3#

N

User property field 32-3

string[32]

O

UserPropertyField32_4#

N

User property field 32-4

string[32]

O

UserPropertyField32_5#

N

User property field 32-5

string[32]

O

UserPropertyField32_6#

N

User property field 32-6

string[32]

O

UserPropertyField32_7#

N

User property field 32-7

string[32]

O

UserPropertyField32_8#

N

User property field 32-8

string[32]

O

UserPropertyField64_1#

N

User property field 64-1

string[64]

Each of these items can manage a maximum of 64 bytes of information.

O

UserPropertyField64_2#

N

User property field 64-2

string[64]

O

UserPropertyField64_3#

N

User property field 64-3

string[64]

O

UserPropertyField64_4#

N

User property field 64-4

string[64]

O

UserPropertyField64_5#

N

User property field 64-5

string[64]

O

UserPropertyField64_6#

N

User property field 64-6

string[64]

O

UserPropertyField64_7#

N

User property field 64-7

string[64]

O

UserPropertyField64_8#

N

User property field 64-8

string[64]

O

UserPropertyUint_1#

N

User property unit-1

uint32

Each of these items can manage numeric information.

O

UserPropertyUint_2#

N

User property unit-2

uint32

O

UserPropertyUint_3#

N

User property unit-3

uint32

O

UserPropertyUint_4#

N

User property unit-4

uint32

O

UserPropertyUint_5#

N

User property unit-5

uint32

O

UserPropertyUint_6#

N

User property unit-6

uint32

O

Legend:

K: Key property

N: Non-key property

M: Mandatory property during registration (omitting this property results in an error)

R: Property whose specification is recommended during new registration (omitting this property does not result in an error)

O: Optional property

#

This is an extended property. You can add managed items by editing the display name of this property and setting it to be displayed using the Customize Managed Items job menu.

The tables below provide details of the property codes.

Table 20‒22: CPU type

Code

Display value

00646

Intel 80286

00902

Intel 80386

01158

Intel 80486

01414

Intel Pentium compatible CPU

04097

Alpha

08193

MIPS

12289

PowerPC

20481

PA-RISC

24577

SPARC

28672

Intel Pentium series

28673

Intel Pentium

28674

Intel Pentium MMX

28675

Intel Pentium Pro

28676

Intel Pentium II

28677

Intel Pentium II Xeon

28678

Intel Pentium III

28679

Intel Pentium III Xeon

28680

Intel Celeron

28681

Intel Pentium 4

28682

Intel Pentium III-S

28683

Mobile Intel Celeron

28684

Mobile Intel Pentium 4

28685

Intel Xeon

28686

Intel Xeon MP

28687

Mobile Intel Pentium III-M

28688

Intel Genuine

28689

Mobile Genuine Intel

28690

Intel Celeron M

28691

Intel Pentium M

28692

Intel Pentium D

28693

Intel Celeron D

28694

Intel Core2

28695

Intel Core

28696

Intel Core i7

28697

Intel Atom

28698

Intel Pentium Dual

28699

Intel Core i3

28700

Intel Core i5

32768

Intel Pentium compatible CPU

33025

AMD K6

33026

AMD K6-2

33027

AMD K6-2 3D Now!

33028

AMD K6-III

33029

AMD Athlon

33030

AMD Duron

33031

AMD Athlon MP

33032

AMD Athlon XP

33033

Mobile AMD Athlon 4

33034

Mobile AMD Duron

33035

AMD Duron MP

33036

Mobile AMD Athlon XP-M

33037

AMD Sempron

33038

Mobile AMD Sempron

33039

AMD Turion

33281

Cyrix MediaGX

33282

Cyrix MII

33283

Cyrix MediaGXm

33537

IDT WinChip

33793

RISE mP6

34049

Crusoe TM5600

36864

for Windows CE

37120

for Windows CE (HITACHI)

37121

Hitachi SH-3

37122

Hitachi SH-4

37376

for Windows CE (MIPS)

37377

MIPS R3000 family

37378

MIPS R4000 family

37632

for Windows CE (ARM)

37633

ARM720

40960

Intel IA-64 CPU

40961

Intel Itanium

40962

Intel Itanium 2

45056

AMD64 compatible CPU

45057

AMD Opteron

45058

AMD Athlon 64

45059

AMD Athlon 64 FX

45060

Mobile AMD Athlon 64

45061

AMD Athlon 64 X2

45062

AMD Turion 64

45063

AMD Athlon II

45064

AMD Turion II

45065

AMD Phenom

45066

AMD Phenom II

45067

AMD V Series

45068

AMD FX

45069

AMD A Series

45070

AMD C Series

45071

AMD E Series

45311

AMD

99999

Other processor

Table 20‒23: Device type

Code

Display value

Computing

100

PC

101

PC server

102

UNIX

103

UNIX server

150

Smart device

199

Other system device

Accessories

200

Monitor

201

HD

202

CD-R

203

CD-R/W

204

DVD

205

DAT

206

MO

207

Printer

208

Peripheral Device

209

USB Device

210

Storage

Networking

300

HUB

301

Router

302

Network printer

399

Network Device

Table 20‒24: Composition

Code

Display value

002

Desktop

003

Notebook

Table 20‒25: Monitor type

Code

Display value

002

CRT

003

Flat panel

Table 20‒26: Monitor resolution

Code

Display value

002

640 x 480

003

800 x 600

004

1024 x 768

005

1280 x 1024

006

1600 x 1200

007

1920 x 1440

20.2.11 InstalledInfo (installed software information)

This class manages the software assets installed on a device. It imports installed software information collected by JP1/IT Desktop Management 2 - Manager.

You can import and export this class. For details about importing by jamCsvImport.bat, see the section describing import processing by the Import job menu.

You can also specify this class as a search condition when creating a user report.

The following table lists the properties of InstalledInfo.

Table 20‒27: Properties of InstalledInfo

Property

Key

Description

Type [maximum length (bytes)]

Remarks

Specification in jamimport

AssetID

K

Asset ID

uint32

This is the ID of the asset.

If you are specifying this information for an import operation, specify the same value as for the corresponding object class AssetInfo.

M

CreationClassName

K

CCN

string[32]

This is InstalledInfo.

M

InfoInd

N

ITDM2 management information acquisition control

string[3]

This is Asset Console management information.

If the Import job menu is used for importing, 1 is always set.

R

InstalledDate

N

Installed date

date

This is the date when the software was installed.

O

InstalledID

K

Installed software ID

uint32

This is the installed software ID of the corresponding object class InstalledList.

If you are specifying this information for an import operation, specify the same value as for the corresponding object class InstalledList.

M

ProductID

N

Product ID

string[255]

This is the product ID of the software asset.

O

RecordInd

N

Log ind.

uint32

This information is used to identify the log information. See Log ind.

O

UpdateTime

N

Update control

string[20]

This information is used to control concurrent updating of information.

O

UserPropertyArea_1#

N

User property area-1

string[255]

This item can manage a maximum of 255 bytes of information.

With a window operation, multiple character string lines can be specified.

O

UserPropertyArea_2#

N

User property area-2

string[255]

O

UserPropertyCode_1#

N

User property code-1

string[64]

This item can control code information.

O

UserPropertyCode_2#

N

User property code-2

string[64]

O

UserPropertyField128_1#

N

User property field 128-1

string[128]

This item can control a maximum of 128 bytes of information.

O

UserPropertyField128_2#

N

User property field 128-2

string[128]

O

UserPropertyField255_1#

N

User property field 255-1

string[255]

This item can manage a maximum of 255 bytes of information.

O

UserPropertyField255_2#

N

User property field 255-2

string[255]

O

Legend:

K: Key property

N: Non-key property

M: Mandatory property during registration (omitting this property results in an error)

R: Property whose specification is recommended during new registration (omitting this property does not result in an error)

O: Optional property

#

This is an extended property. You can add managed items by editing the display name of this property and setting it to be displayed using the Customize Managed Items job menu.

The tables below provide details of the property codes.

Table 20‒28: Log ind

Code

Description

1

Information updated by loading JP1/IT Desktop Management 2 - Manager's management information

2

Information updated by an Asset Console window operation

(None)

Information updated by transferring or importing the asset management database

20.2.12 InstalledList (installed software list)

This class manages the correspondence between the names of purchased software assets and the names of installed software assets that are collected by JP1/IT Desktop Management 2 - Manager.

You can import or export this class. For details about importing by jamCsvImport.bat, see the section describing import processing by the Import job menu.

You can also specify this class as a search condition when creating a user report.

The following table lists the properties of InstalledList.

Table 20‒29: Properties of InstalledList

Property

Key

Description

Type [maximum length (bytes)]

Remarks

Specification in jamimport

CreationClassName

K

CCN

string[32]

This is InstalledList.

M

FileDate

N

File date

string[19]

This is the date of the executable file for the installed software asset.

O

FileName

N

File name

string[255]

This is the name of the executable file for the installed software asset.

O

FileSize

N

File size

string[10]

This is the size of the executable file for the installed software asset. The value is in bytes.

O

InstalledID

K

Installed software ID

uint32

This is a unique ID that identifies the installed software asset.

When new information is imported, assign a unique value in the range from 10001 to 1000000000.

M

InstalledInd

N

Managed level

string[3]

See Managed level.

This specifies whether to manage the number of licenses of this software asset.

If the Import job menu is used for importing and this property is omitted, Managed object is set.

M

InstalledKind

N

Software type

string[3]

See Software type.

If the Import job menu is used for importing and this property is omitted, Normally is set.

M

InstalledName

N

Installed software name

string[1024]

This is the name of the software asset managed by JP1/IT Desktop Management 2 - Manager.

O

InstalledPermit

N

Permission

string[3]

See Permission.

If the Import job menu is used for importing and this property is omitted, Permit is set.

M

InstalledVersion

N

Installed software version

string[256]

This is the software version managed by JP1/IT Desktop Management 2 - Manager.

O

SoftwareListID

N

Software list ID

uint32

This is the software list ID of the corresponding software when the software name is assigned.

O

UpdateTime

N

Update control

string[20]

This information is used to control concurrent updating of information.

O

UserPropertyArea_1#

N

User property area-1

string[255]

This item can manage a maximum of 255 bytes of information.

With a window operation, multiple character string lines can be specified.

O

UserPropertyArea_2#

N

User property area-2

string[255]

O

UserPropertyCode_1#

N

User property code-1

string[64]

This item can control code information.

O

UserPropertyCode_2#

N

User property code-2

string[64]

O

UserPropertyField128_1#

N

User property field 128-1

string[128]

This item can control a maximum of 128 bytes of information.

O

UserPropertyField128_2#

N

User property field 128-2

string[128]

O

UserPropertyField255_1#

N

User property field 255-1

string[255]

This item can manage a maximum of 255 bytes of information.

O

UserPropertyField255_2#

N

User property field 255-2

string[255]

O

Legend:

K: Key property

N: Non-key property

M: Mandatory property during registration

O: Optional property

#

This is an extended property. You can add managed items by editing the display name of this property and setting it to be displayed using the Customize Managed Items job menu.

The tables below provide details of the property codes.

Table 20‒30: Managed level

Code

Display value

1

Managed object

2

Managed object not in license count

3

Unmanaged object

If 2 is specified for an import operation, this asset is not included in the usage count when licenses are summed up. However, the information about the installed software asset can be referenced.

If 3 is specified, the corresponding software information is not overwritten when the ITDM2 management information is updated.

Table 20‒31: Software type

Code

Display value

1

Normally

2

Office

3

Virus definition

4

Operating system

Table 20‒32: Permission

Code

Display value

1

Permit

2

Do not permit

20.2.13 InstalledUpdateRecord (software update log)

This class manages updating of the software installed on the device.

You cannot import or export this class.

You can also specify this class as a search condition when creating a user report.

The following table lists the properties of InstalledUpdateRecord.

Table 20‒33: Properties of InstalledUpdateRecord

Property

Key

Description

Type [maximum length (bytes)]

Remarks

CreationClassName

K

CCN

string[32]

This is InstalledUpdateRecord.

Executor

N

Executer

string[512]

This is the user who edited the installed software information with window operations.

FileDate

N

File date

string[19]

This is the date of the executable file for the installed software asset.

FileName

N

File name

string[255]

This is the name of the executable file for the installed software asset.

FileSize

N

File size

string[10]

This is the size (in bytes) of the executable file for the installed software asset.

HistoryUpdateDate

K

Update date

date

This is the date the information was changed.

InstalledID

K

Installed software ID

uint32

This is the unique ID for identifying the installed software asset.

InstalledName

N

Installed software name

string[1024]

This is the name of the installed software asset.

InstalledVersion

N

Installed software version

string[255]

This is the version of the installed software asset.

LinkKey

K

Link key

string[32]

This is the key value for the changed object class.

UpdateKind

N

Update type

uint8

See Update type.

Legend:

K: Key property

N: Non-key property

The tables below provide details of the property codes.

Table 20‒34: Update type

Code

Display value

1

Addition

2

Deletion

20.2.14 InstalledVirusDefInfo (virus definition information)

This class manages virus definition information.

You can import and export this class. For details about importing by jamCsvImport.bat, see the section describing import processing by the Import job menu.

You can also specify this class as a search condition when creating a user report.

The following table lists the properties of InstalledVirusDefInfo.

Table 20‒35: Properties of InstalledVirusDefInfo

Property

Key

Description

Type [maximum length (bytes)]

Remarks

Specification in jamimport

AssetID

K

Asset ID

uint32

This is the ID of the asset.

If you are specifying this information for an import operation, specify the same value as for the corresponding object class AssetInfo.

M

CreationClassName

K

CCN

string[32]

This is InstalledVirusDefInfo.

M

EngineVersion

N

Version of virus detection engine

string[1024]

This is the scanning engine version of the installed anti-virus software.

R

InfoInd

N

ITDM2 management information acquisition control

string[3]

If the Import job menu is used for importing, 1 is always set.

R

InstalledDate

N

Installed date

date

This is the date the software was installed.

O

ResidentKind

N

Resident/nonresident

string[3]

See Resident/nonresident.

O

SoftwareVersion

N

Anti-virus product version

string[1024]

This is the version of the anti-virus software installed on the device.

R

UpdateInd

N

Update indicator

uint32

This information is used by the asset management system. Do not update it.

O

VirusDefName

K

Anti-virus product name

string[1024]

This is the name of the anti-virus software product installed on the device.

M

VirusDefVersion

N

Virus definition version

string[1024]

This is the version of the virus definition information installed on the device.

R

Legend:

K: Key property

N: Non-key property

M: Mandatory property during registration (omitting this property results in an error)

R: Property whose specification is recommended during new registration (omitting this property does not result in an error)

O: Optional property

The tables below provide details of the property codes.

Table 20‒36: Resident/nonresident

Code

Display value

1

Resident

0

Nonresident

20.2.15 IPAddress (IP address control information)

This class manages the available IP addresses. When acquiring IP addresses, you can manage the available IP addresses by associating them with those registered in this class.

You can import or export this class.

You can also specify this class as a search condition when creating a user report.

The following table lists the properties of IPAddress.

Table 20‒37: Properties of IPAddress

Property

Key

Description

Type [maximum length (bytes)]

Remarks

Specification in jamimport

CreationClassName

K

CCN

string[32]

This is IPAddress.

M

IPAddress

K

IP address

string[70]

This is the IP address.

M

Purpose

N

Purpose

string[255]

This is the purpose of the IP address.

O

UpdateTime

N

Update control

string[20]

This information is used to control concurrent updating of information.

O

Legend:

K: Key property

N: Non-key property

M: Mandatory property during registration

O: Optional property

20.2.16 JobRoleInfo (official authority)

This class manages official authority.

You can import and export this class with the jamimport and jamexport commands, respectively.

You can also specify this class as a search condition when creating a user report.

The following table lists the properties of JobRoleInfo.

Table 20‒38: Properties of JobRoleInfo

Property

Key

Description

Type [maximum length (bytes)]

Remarks

Specification in jamimport

CreationClassName

K

CCN

string[32]

This is JobRoleInfo.

M

Description

N

Description

string[255]

This is a description of the official authority.

O

JobRoleID

K

Official authority ID

string[64]

This is a unique ID for identifying the official authority.

M

JobRoleName

N

Official authority name

string[128]

This is name of the official authority.

M

JobRoleName_EN

N

Official authority name

string[128]

This is name of the official authority in English.

M

UpdateTime

N

Update control

string[20]

This information is used to control concurrent updating of information.

O

Legend:

K: Key property

N: Non-key property

M: Mandatory property during registration

O: Optional property

20.2.17 LicenseInfo (license information)

This class manages detailed information about software licenses. Licenses are assigned to devices and users on the basis of this license information.

You can import and export this class. For details about importing by jamCsvImport.bat, see the section describing import processing by the Import job menu.

You can also specify this class as a search condition when creating a user report.

The following table lists the properties of LicenseInfo.

Table 20‒39: Properties of LicenseInfo

Property

Key

Description

Type [maximum length (bytes)]

Remarks

Specification in jamimport

CreationClassName

K

CCN

string[32]

This is LicenseInfo.

M

Description

N

Description

string[255]

This is a description of the license.

O

DownGrade

N

Downgrade

string[3]

See Downgrade.

This indicates whether licenses are to be applied to downgrade software assets.

If the Import job menu is used for importing and this property is omitted, Enable is set.

R

LicenseCategory

N

License category

string[3]

See License category.

If the Import job menu is used for importing and this property is omitted, Install license is set.

R

LicenseID

K

License ID

uint32

This is a unique ID that identifies the license information.

When new information is imported, assign a unique value in the range from 10001 to 1000000000.

M

LicenseName

N

License name

string[255]

This is the name of the license information.

M

LicenseType

N

License type

string[3]

See License type.

If the Import job menu is used for importing and this property is omitted, Install license is set.

R

Note

N

Notes

string[255]

These are notes on the license information.

O

PurchaseType

N

Licensing method

string[3]

See Licensing method.

If the Import job menu is used for importing and this property is omitted, Package is set.

R

SoftwareListID

N

Software list ID

uint32

This is the ID of the corresponding software name.

If you are specifying this information for an import operation, specify the same value as for the corresponding object class SoftwareList

M

UpdateTime

N

Update control

string[20]

This information is used to control concurrent updating of information.

O

UpGrade

N

Upgrade assurance

string[3]

See Upgrade assurance.

This indicates whether the software asset can be upgraded to the most recent version during the contract period.

If the Import job menu is used for importing and this property is omitted, Yes is set.

R

UserPropertyArea_1#

N

User property area-1

string[255]

This item can manage a maximum of 255 bytes of information.

With a window operation, multiple character string lines can be specified.

O

UserPropertyArea_2#

N

User property area-2

string[255]

O

UserPropertyCode_1#

N

User property code-1

string[64]

This item can control code information.

O

UserPropertyCode_2#

N

User property code-2

string[64]

O

UserPropertyField128_1#

N

User property field 128-1

string[128]

This item can control a maximum of 128 bytes of information.

O

UserPropertyField128_2#

N

User property field 128-2

string[128]

O

UserPropertyField255_1#

N

User property field 255-1

string[255]

This item can manage a maximum of 255 bytes of information.

O

UserPropertyField255_2#

N

User property field 255-2

string[255]

O

Legend:

K: Key property

N: Non-key property

M: Mandatory property during registration (omitting this property results in an error)

R: Property whose specification is recommended during new registration (omitting this property does not result in an error)

O: Optional property

#

This is an extended property. You can add managed items by editing the display name of this property and setting it to be displayed using the Customize Managed Items job menu.

The tables below provide details of the property codes.

Table 20‒40: Downgrade

Code

Display value

001

Enable

002

Disable

Table 20‒41: License category

Code

Display value

100

Install license

200

User license

300

Other

Table 20‒42: License type

Code

Display value

001

Install license

002

User license

003

Server license

004

Client access license

005

Managed node license

006

CPU license

007

Second license

008

Concurrent execution license

Table 20‒43: Licensing method

Code

Display value

001

Package

002

Pre-installed

003

Volume license

Table 20‒44: Upgrade assurance

Code

Display value

001

Yes

002

No

20.2.18 LocationInfo (location information)

This class manages the locations of assets.

You can import or export this class. For details about importing by jamCsvImport.bat, see the section describing import processing by the Import job menu.

You can also specify this class as a search condition when creating a user report.

The following table lists the properties of LocationInfo.

Table 20‒45: Properties of LocationInfo

Property

Key

Description

Type [maximum length (bytes)]

Remarks

Specification in jamimport

Address

N

Contact post address

string[255]

This is the address of the location.

O

AreaSize

N

Area size

string[255]

The value is in square meters.

O

Attribute

N

Attribute

string[3]

See Attribute.

M

CreationClassName

K

CCN

string[32]

This is LocationInfo.

M

Explanation

N

Description

string[255]

This is a description of the location.

O

FullPathName

N

Location

string[1024]

This is the location information that represents the entire hierarchy from the top, such as New York/A building/First floor.

M

FullPathName_EN

N

Location

string[1024]

This is the location information in English that represents the entire hierarchy from the top, such as New York/A building/First floor.

If the Import job menu is used for importing and this property is omitted, the value for the Location ID is set.

O

LocationID

K

Location ID

string[64]

This is a unique ID that identifies the location.

To perform registration by importing new IDs from a file, make sure that unique IDs not in the range from 1000000001 to 9999999999 are assigned.

M

LocationName

N

Location

string[512]

This is the name of the location.

M

LocationName_EN

N

Location name (English)

string[512]

This is the name of the location in English.

R

UpdateInd

N

Update indicator

uint32

This information is used by the asset management system. Do not update it.

O

UpdateTime

N

Update control

string[20]

This information is used to control concurrent updating of information.

O

UpperLinkID

N

Upper location ID

string[64]

This is the ID of the upper-level location name.

O

UserPropertyArea_1#

N

User property area-1

string[255]

This item can manage a maximum of 255 bytes of information.

With a window operation, multiple character string lines can be specified.

O

UserPropertyArea_2#

N

User property area-2

string[255]

O

UserPropertyCode_1#

N

User property code-1

string[64]

This item can control code information.

O

UserPropertyCode_2#

N

User property code-2

string[64]

O

UserPropertyField128_1#

N

User property field 128-1

string[128]

This item can control a maximum of 128 bytes of information.

O

UserPropertyField128_2#

N

User property field 128-2

string[128]

O

UserPropertyField255_1#

N

User property field 255-1

string[255]

This item can manage a maximum of 255 bytes of information.

O

UserPropertyField255_2#

N

User property field 255-2

string[255]

O

Legend:

K: Key property

N: Non-key property

M: Mandatory property during registration (omitting this property results in an error)

R: Property whose specification is recommended during new registration (omitting this property does not result in an error)

O: Optional property

#

This is an extended property. You can add managed items by editing the display name of this property and setting it to be displayed using the Customize Managed Items job menu.

The tables below provide details of the property codes.

Table 20‒46: Attribute

Code

Display value

001

Region

002

Building

003

Floor

004

Area

199

Other

20.2.19 MachineCatalog (device catalog)

This class manages hardware information as a catalog, such as a name, model, and device type in the asset information.

You can import or export this class. For details about importing by jamCsvImport.bat, see the section describing import processing by the Import job menu.

The following table lists the properties of MachineCatalog.

Table 20‒47: Properties of MachineCatalog

Property

Key

Description

Type [maximum length (bytes)]

Remarks

Specification in jamimport

CatalogID

K

Catalog ID

uint32

ID that identifies the device catalog.

This is a unique

When new information is imported, assign a unique value in the range from 10001 to 1000000000.

M

CircuitSpeed

N

Line speed

uint32

The value is in kbps.

O

CPUClock

N

Processor speed

uint32

The value is in MHz.

O

CPUNumber

N

Number of processors

uint16

This is the number of CPUs.

O

CPUType

N

Processor

string[5]

See CPU type in 20.2.10 HardwareInfo (hardware information).

O

CreationClassName

K

CCN

string[32]

This is MachineCatalog.

M

Developer

N

Developer

string[512]

This is the developer of the device.

O

MachineKind

N

Device type

string[5]

See Device type in 20.2.10 HardwareInfo (hardware information).

If the Import job menu is used for importing and this property is omitted, PC is set.

O

MemorySize

N

Memory

uint64

The value is in megabytes.

O

Model

N

Model

string[512]

This is the device model.

If the Import job menu is used for importing and this property is omitted, Desktop is set.

M

ModelKind

N

Composition

string[3]

See Composition in 20.2.10 HardwareInfo (hardware information).

O

MonitorKind

N

Monitor type

string[3]

See Monitor type in 20.2.10 HardwareInfo (hardware information).

O

MonitorResolution

N

Monitor resolution

string[3]

See Monitor resolution in 20.2.10 HardwareInfo (hardware information).

O

MonitorSize

N

Monitor size

uint16

This is the monitor size.

O

Name

N

Device name

string[512]

This is the name of the device.

M

NumberOFPort

N

Number of ports

uint32

This is the number of ports on the device.

O

PurchasePrice

N

Purchase price

string[15]

This is the purchase price

O

Specification

N

Specification

string[255]

This is the device's specifications.

O

TotalHDSize

N

Hard disk sizes

uint64

The value is in megabytes.

O

UpdateTime

N

Update control

string[20]

This information is used to control concurrent updating of information.

O

UserPropertyArea_1#

N

User property area-1

string[255]

This item can manage a maximum of 255 bytes of information.

With a window operation, multiple character string lines can be specified.

O

UserPropertyArea_2#

N

User property area-2

string[255]

O

UserPropertyArea_3#

N

User property area-3

string[255]

O

UserPropertyArea_4#

N

User property area-4

string[255]

O

UserPropertyCode_1#

N

User property code-1

string[64]

This item can control code information.

O

UserPropertyCode_2#

N

User property code-2

string[64]

O

UserPropertyCode_3#

N

User property code-3

string[64]

O

UserPropertyCode_4#

N

User property code-4

string[64]

O

UserPropertyCode_5#

N

User property code-5

string[64]

O

UserPropertyCode_6#

N

User property code-6

string[64]

O

UserPropertyCode_7#

N

User property code-7

string[64]

O

UserPropertyCode_8#

N

User property code-8

string[64]

O

UserPropertyCode_9#

N

User property code-9

string[64]

O

UserPropertyCode_10#

N

User property code-10

string[64]

O

UserPropertyCode_11#

N

User property code-11

string[64]

O

UserPropertyCode_12#

N

User property code-12

string[64]

O

UserPropertyDate_1#

N

User property date-1

date

Each of these items manages date information.

O

UserPropertyDate_2#

N

User property date-2

date

O

UserPropertyDate_3#

N

User property date-3

date

O

UserPropertyDate_4#

N

User property date-4

date

O

UserPropertyDate_5#

N

User property date-5

date

O

UserPropertyDate_6#

N

User property date-6

date

O

UserPropertyField128_1#

N

User property field 128-1

string[128]

This item can control a maximum of 128 bytes of information.

O

UserPropertyField128_2#

N

User property field 128-2

string[128]

O

UserPropertyField128_3#

N

User property field 128-3

string[128]

O

UserPropertyField128_4#

N

User property field 128-4

string[128]

O

UserPropertyField128_5#

N

User property field 128-5

string[128]

O

UserPropertyField128_6#

N

User property field 128-6

string[128]

O

UserPropertyField128_7#

N

User property field 128-7

string[128]

O

UserPropertyField128_8#

N

User property field 128-8

string[128]

O

UserPropertyField255_1#

N

User property field 255-1

string[255]

This item can manage a maximum of 255 bytes of information.

O

UserPropertyField255_2#

N

User property field 255-2

string[255]

O

UserPropertyField255_3#

N

User property field 255-3

string[255]

O

UserPropertyField255_4#

N

User property field 255-4

string[255]

O

UserPropertyField255_5#

N

User property field 255-5

string[255]

O

UserPropertyField255_6#

N

User property field 255-6

string[255]

O

UserPropertyField255_7#

N

User property field 255-7

string[255]

O

UserPropertyField255_8#

N

User property field 255-8

string[255]

O

UserPropertyField32_1#

N

User property field 32-1

string[32]

Each of these items can manage a maximum of 32 bytes of information.

O

UserPropertyField32_2#

N

User property field 32-2

string[32]

O

UserPropertyField32_3#

N

User property field 32-3

string[32]

O

UserPropertyField32_4#

N

User property field 32-4

string[32]

O

UserPropertyField32_5#

N

User property field 32-5

string[32]

O

UserPropertyField32_6#

N

User property field 32-6

string[32]

O

UserPropertyField32_7#

N

User property field 32-7

string[32]

O

UserPropertyField32_8#

N

User property field 32-8

string[32]

O

UserPropertyField64_1#

N

User property field 64-1

string[64]

Each of these items can manage a maximum of 64 bytes of information.

O

UserPropertyField64_2#

N

User property field 64-2

string[64]

O

UserPropertyField64_3#

N

User property field 64-3

string[64]

O

UserPropertyField64_4#

N

User property field 64-4

string[64]

O

UserPropertyField64_5#

N

User property field 64-5

string[64]

O

UserPropertyField64_6#

N

User property field 64-6

string[64]

O

UserPropertyField64_7#

N

User property field 64-7

string[64]

O

UserPropertyField64_8#

N

User property field 64-8

string[64]

O

UserPropertyUint_1#

N

User property unit-1

uint32

Each of these items can manage numeric information.

O

UserPropertyUint_2#

N

User property unit-2

uint32

O

UserPropertyUint_3#

N

User property unit-3

uint32

O

UserPropertyUint_4#

N

User property unit-4

uint32

O

UserPropertyUint_5#

N

User property unit-5

uint32

O

UserPropertyUint_6#

N

User property unit-6

uint32

O

Legend:

K: Key property

N: Non-key property

M: Mandatory property during registration

O: Optional property

#

This is an extended property. You can add managed items by editing the display name of this property and setting it to be displayed using the Customize Managed Items job menu.

20.2.20 Maintenance (maintenance log)

This class manages the maintenance log for assets.

You can import or export this class. For details about importing by jamCsvImport.bat, see the section describing import processing by the Import job menu.

You can also specify this class as a search condition when creating a user report.

The following table lists the properties of Maintenance.

Table 20‒48: Properties of Maintenance

Property

Key

Description

Type [maximum length (bytes)]

Remarks

Specification in jamimport

AssetID

N

Asset ID

uint32

This is the ID of the asset.

If you are specifying this information for an import operation, specify the same value as for the corresponding object class AssetInfo.

O

AssetNo

N

Asset No.

string[60]

This is the asset number of the corresponding asset.

O

CompletingDate

N

Completion date

date

This is the date on which maintenance of the asset was completed.

O

CreationClassName

K

CCN

string[32]

This is Maintenance.

M

EventHost

N

Event-issuing host

string[255]

This is the name of the host that issued the event.

O

EventNo

N

Event serial number

string[255]

This is a serial number in the event database that is assigned by JP1/Base to a JP1 event.

O

ExecutionHost

N

JP1/IM execution host

string[255]

This is the name of the host that executed JP1/IM.

O

Expense

N

Expense

string[15]

This is the maintenance expenses for the asset.

O

Importance

N

Importance

string[3]

See Importance.

If the Import job menu is used for importing and this property is omitted, Emergency is set.

R

MaintenanceDate

N

Registration date

date

This is the date the maintenance log was registered.

R

MaintenanceHost

N

Host where problem occurred

string[255]

This is the IP address or name of the host where the problem occurred.

O

MaintenanceID

K

Maintenance log ID

uint32

This is a unique ID that identifies the maintenance log.

When new information is imported, assign a unique value in the range from 10001 to 1000000000.

M

MaintenanceKind

N

Problem type

string[3]

See Problem type.

R

MaintenanceStatus

N

Status

string[3]

See Status.

If the Import job menu is used for importing and this property is omitted, Wrong is set.

M

ManagedNo

N

Managed No.

string[60]

This is the managed number of the maintenance log

M

MeasureContents

N

Overview of solution

string[1024]

This is an overview of the problem with the asset

O

Note

N

Notes

string[255]

These are notes on the maintenance log.

O

ObstacleContents

N

Overview of problem

string[1024]

This is an overview of the problem with the asset.

R

ReferenceData

N

Reference materials (URL)

string[1024]

These are reference materials for maintenance of the asset.

O

UpdateTime

N

Update control

string[20]

This information is used to control concurrent updating of information.

O

UserName

N

Registrar

string[512]

This is the name of the user who registered the error information.

If the Import job menu is used for importing and this property is omitted, the login user name (asset

management name during execution of jamCsvImport.bat) is set.

R

UserPropertyArea_1#

N

User property area-1

string[255]

This item can manage a maximum of 255 bytes of information.

With a window operation, multiple character string lines can be specified.

O

UserPropertyArea_2#

N

User property area-2

string[255]

O

UserPropertyCode_1#

N

User property code-1

string[64]

This item can control code information.

O

UserPropertyCode_2#

N

User property code-2

string[64]

O

UserPropertyField128_1#

N

User property field 128-1

string[128]

This item can control a maximum of 128 bytes of information.

O

UserPropertyField128_2#

N

User property field 128-2

string[128]

O

UserPropertyField255_1#

N

User property field 255-1

string[255]

This item can manage a maximum of 255 bytes of information.

O

UserPropertyField255_2#

N

User property field 255-2

string[255]

O

Worker

N

Worker

string[512]

This is the name of the maintenance person.

O

Legend:

K: Key property

N: Non-key property

M: Mandatory property during registration (omitting this property results in an error)

R: Property whose specification is recommended during new registration (omitting this property does not result in an error)

O: Optional property

#

This is an extended property. You can add managed items by editing the display name of this property and setting it to be displayed using the Customize Managed Items job menu.

The tables below provide details of the property codes.

Table 20‒49: Importance

Code

Display value

001

Emergency

002

Caution

003

Fatal

004

Error

005

Warning

006

Notice

007

Information

008

Debug

Table 20‒50: Problem type

Code

Display value

001

JP1 event

002

SNMP trap

100

User Registered

Table 20‒51: Status

Code

Display value

001

Wrong

002

Informed

003

Under repair

901

Complete

20.2.21 NetworkInfo (network information)

This class manages the location of a device in the network.

You can import or export this class. For details about importing by jamCsvImport.bat, see the section describing import processing by the Import job menu.

You can also specify this class as a search condition when creating a user report.

The following table lists the properties of NetworkInfo.

Table 20‒52: Properties of NetworkInfo

Property

Key

Description

Type [maximum length (bytes)]

Remarks

Specification in jamimport

AssetID

K

Asset ID

uint32

This is the ID of the asset.

If you are specifying this information for an import operation, specify the same value as for the corresponding object class AssetInfo.

M

ComputerName

N

Computer name

string[512]

This is the name of the computer.

It is converted into upper-case letters.

O

CreationClassName

K

CCN

string[32]

This is NetworkInfo.

M

DefaultGateway

N

Default Gateway

string[70]

This is the default gateway.

O

DHCPServerName

N

DHCP server name

string[255]

This is the DHCP server name.

O

GlobalIPAddress

N

Global IP address

string[70]

This is the global IP address.

O

InfoInd

N

ITDM2 management information acquisition control

string[3]

If the Import job menu is used for importing, 1 is always set.

R

IPAddress

N

IP address

string[70]

This is the IP address.

If you are updating this information for an import operation, delete the existing IP address from the association class IPAddressLink and then register the new IP address and also update the association.

O

IPAddressKind

N

IP address type

string[3]

See IP address type.

If you are registering the asset as IPv4, you must import the association class IPAddressLink (IP address link).

O

MACAddress

N

MAC address

string[17]

This is the MAC address.

O

NetworkID

K

Network info ID

uint32

This is a unique ID that identifies the network information.

When new information is imported, assign a unique value in the range 10001 to 1000000000.

M

NodeName

N

Node name (host name)

string[512]

This is the node name (host name).

It is converted into lower-case letters.

O

PortInfo

N

Port information

string[255]

This is the port information.

O

SubnetMask

N

Subnet mask

string[70]

This is the subnet mask of the IP address

O

UpdateInd

N

Update indicator

uint32

This information is used by the asset management system. Do not update it.

O

UpdateTime

N

Update control

string[20]

This information is used to control concurrent updating of information.

O

UserPropertyArea_1#

N

User property area-1

string[255]

This item can manage a maximum of 255 bytes of information.

With a window operation, multiple character string lines can be specified.

O

UserPropertyArea_2#

N

User property area-2

string[255]

O

UserPropertyCode_1#

N

User property code-1

string[64]

This item can control code information.

O

UserPropertyCode_2#

N

User property code-2

string[64]

O

UserPropertyField128_1#

N

User property field 128-1

string[128]

This item can control a maximum of 128 bytes of information.

O

UserPropertyField128_2#

N

User property field 128-2

string[128]

O

UserPropertyField255_1#

N

User property field 255-1

string[255]

This item can manage a maximum of 255 bytes of information.

O

UserPropertyField255_2#

N

User property field 255-2

string[255]

O

Legend:

K: Key property

N: Non-key property

M: Mandatory property during registration (omitting this property results in an error)

R: Property whose specification is recommended during new registration (omitting this property does not result in an error)

O: Optional property

#

This is an extended property. You can add managed items by editing the display name of this property and setting it to be displayed using the Customize Managed Items job menu.

The tables below provide details of the property codes.

Table 20‒53: IP address type

Code

Display value

001

IPv4

002

IPv6

20.2.22 PatchInfo (managing patch information)

This class manages patch information.

You can import or export this class. For details about importing by jamCsvImport.bat, see the section describing import processing by the Import job menu.

You can also specify this class as a search condition when creating a user report.

The following table lists the properties of PatchInfo.

Table 20‒54: Properties of PatchInfo

Property

Key

Description

Type [maximum length (bytes)]

Remarks

Specification in jamimport

AssetID

K

Asset ID

uint32

This is the ID of the asset.

If you are specifying this information for an import operation, specify the same value as for the corresponding object class AssetInfo.

M

CreationClassName

K

CCN

string[32]

This is PatchInfo.

M

InfoInd

N

ITDM2 management information acquisition control

string[3]

If the Import job menu is used for importing, 1 is always set.

R

InstalledDate

N

Installed date

date

This is the date the patch was installed.

O

InstalledStatus

N

Applied status

string[3]

See Applied status.

If the Import job menu is used for importing and this property is omitted, Apply is set.

R

PatchID

K

Patch ID

uint32

This is a unique ID for identifying a search condition.

If you are adding a new patch ID by importing, assign a unique ID in the range from 10001 to 1000000000.

M

UpdateInd

N

Update indicator

uint32

This information is used by the asset management system. Do not update it.

O

Legend:

K: Key property

N: Non-key property

M: Mandatory property during registration (omitting this property results in an error)

R: Property whose specification is recommended during new registration (omitting this property does not result in an error)

O: Optional property

The tables below provide details of the property codes.

Table 20‒55: Applied status

Code

Display value

101

Applied

102

Unapplied

20.2.23 PatchList (patch name list)

This class manages the information that corresponds to patch names.

You can import or export this class.

You can also specify this class as a search condition when creating a user report.

The following table lists the properties of PatchList.

Table 20‒56: Properties of PatchList

Property

Key

Description

Type [maximum length (bytes)]

Remarks

Specification in jamimport

CreationClassName

K

CCN

string[32]

This is PatchList.

M

PatchID

K

Patch ID

uint32

This is the patch ID.

M

PatchName

N

Patch name

string[512]

This is the name of the patch.

R

PatchVersion

N

Patch version

string[60]

This is the version of the patch.

R

UpdateTime

N

Update control

string[20]

This information is used to control concurrent updating of information.

O

Legend:

K: Key property

N: Non-key property

M: Mandatory property during registration (omitting this property results in an error)

R: Property whose specification is recommended during new registration (omitting this property does not result in an error)

O: Optional property

20.2.24 RelationAssetInfo (program execution history)

This class manages the program execution history.

You can import or export this class. For details about importing by jamCsvImport.bat, see the section describing import processing by the Import job menu.

The following table lists the properties of RelationAssetInfo.

Table 20‒57: Properties of RelationAssetInfo

Property

Key

Description

Type [maximum length (bytes)]

Remarks

Specification in jamimport

ChildAssetID

K

Child asset ID

uint32

This is the asset ID of the child asset. If you are specifying this information for an import operation, specify the same value as for the corresponding object class AssetInfo.

M

CreationClass

Name

K

CCN

string[32]

This is RelationAssetInfo.

M

ParentAssetID

K

Parent asset ID

uint32

This is the asset ID of the parent asset. If you are specifying this information for an import operation, specify the same value as for the corresponding object class AssetInfo.

M

Legend:

K: Key property

M: Mandatory property during registration (omitting this property results in an error)

20.2.25 RoleInfo (role information)

This class manages the user roles in the asset management system.

You can import or export this class.

You can also specify this class as a search condition when creating a user report.

The following table lists the properties of RoleInfo.

Table 20‒58: Properties of RoleInfo

Property

Key

Description

Type [maximum length (bytes)]

Remarks

Specification in jamimport

CreationClassName

K

CCN

string[32]

This is RoleInfo.

M

Link

N

HTML file name for link

string[255]

This is the URL of the window that is displayed after login.

M

ManagedLabel

N

Managed label

string[20]

This is a character string set for both the group and the user role when access permissions are set for a group hierarchy.

O

RoleID

K

Role ID

string[64]

This is a unique ID that identifies the role.

M

RoleName

N

Role name

string[128]

This is the name of the role.

M

RoleName_EN

N

Role name

string[128]

This is the name of the role in English.

O

SystemInd

N

System indicator

uint8

See System indicator.

M

UpdateTime

N

Update control

string[20]

This information is used to control concurrent updating of information.

O

Legend:

K: Key property

N: Non-key property

M: Mandatory property during registration

O: Optional property

The tables below provide details of the property codes.

Table 20‒59: System indicator

Code

Display value

0

User information (deletable)

1

System information (Not deletable)

When new information is imported, specify 0.

For an import operation, do not delete information for which 1 is set.

20.2.26 SoftwareInfo (software information)

This class manages information about all software assets handled in the asset management system, such as commercial software, shareware, and freeware.

You can import or export this class.

You can also specify this class as a search condition when creating a user report.

The following table lists the properties of SoftwareInfo.

Table 20‒60: Properties of SoftwareInfo

Property

Key

Description

Type [maximum length (bytes)]

Remarks

Specification in jamimport

AssetID

K

Asset ID

uint32

This is the ID of the asset.

If you are specifying this information for an import operation, specify the same value as for the corresponding object class AssetInfo.

M

CreationClassName

K

CCN

string[32]

This is SoftwareInfo.

M

LicenseID

N

License ID

uint32

This is the license ID of the corresponding object class LicenseInfo.

If you are specifying this information for an import operation, specify the same value as for the corresponding LicenseInfo.

O

NumberOFLicense

N

Number of licenses

uint32

This is the number of software licenses.

For an unlimited license, specify null for an import operation.

R

NumberOFPoint

N

Purchase point

uint32

This is the number of points accrued for each software asset when a volume license is purchased.

O

SoftwareListID

N

Software list ID

uint32

This is the software list ID of the corresponding software asset.

If you are specifying this information for an import operation, specify the same value as for the corresponding object class SoftwareList.

M

UpdateTime

N

Update control

string[20]

This information is used to control concurrent updating of information.

O

UserPropertyArea_1#

N

User property area-1

string[255]

This item can manage a maximum of 255 bytes of information.

With a window operation, multiple character string lines can be specified.

O

UserPropertyArea_2#

N

User property area-2

string[255]

O

UserPropertyCode_1#

N

User property code-1

string[64]

This item can control code information.

O

UserPropertyCode_2#

N

User property code-2

string[64]

O

UserPropertyField128_1#

N

User property field 128-1

string[128]

This item can control a maximum of 128 bytes of information.

O

UserPropertyField128_2#

N

User property field 128-2

string[128]

O

UserPropertyField255_1#

N

User property field 255-1

string[255]

This item can manage a maximum of 255 bytes of information.

O

UserPropertyField255_2#

N

User property field 255-2

string[255]

O

Legend:

K: Key property

N: Non-key property

M: Mandatory property during registration (omitting this property results in an error)

R: Property whose specification is recommended during new registration (omitting this property does not result in an error)

O: Optional property

#

This is an extended property. You can add managed items by editing the display name of this property and setting it to be displayed using the Customize Managed Items job menu.

20.2.27 SoftwareKeyInfo (software key information)

This class manages the key information when software licenses are assigned to devices or users.

You can import or export this class.

You can also specify this class as a search condition when creating a user report.

The following table lists the properties of SoftwareKeyInfo.

Table 20‒61: Properties of SoftwareKeyInfo

Property

Key

Description

Type [maximum length (bytes)]

Remarks

Specification in jamimport

CreationClassName

K

CCN

string[32]

This is SoftwareKeyInfo.

M

KeyID

K

Key ID

uint32

This is a unique ID that identifies the software key information.

When new information is imported, assign a unique value in the range from 10001 to 1000000000.

M

LicenseKey

N

License key

string[255]

This is the license key.

R

Note

N

Notes

string[255]

These are notes on the software key information.

R

ProductID

N

Product ID

string[255]

This is the product ID.

O

SerialNo

N

Serial No.

string[255]

This is the serial number.

R

SoftAssetID

N

Asset ID

uint32

This is the ID of the corresponding software asset.

If you are specifying this information for an import operation, specify the same value as for the corresponding object class AssetInfo.

M

UpdateTime

N

Update control

string[20]

This information is used to control concurrent updating of information.

O

UserPropertyArea_1#

N

User property area-1

string[255]

This item can manage a maximum of 255 bytes of information.

With a window operation, multiple character string lines can be specified.

O

UserPropertyArea_2#

N

User property area-2

string[255]

O

UserPropertyCode_1#

N

User property code-1

string[64]

This item can control code information.

O

UserPropertyCode_2#

N

User property code-2

string[64]

O

UserPropertyField128_1#

N

User property field 128-1

string[128]

This item can control a maximum of 128 bytes of information.

O

UserPropertyField128_2#

N

User property field 128-2

string[128]

O

UserPropertyField255_1#

N

User property field 255-1

string[255]

This item can manage a maximum of 255 bytes of information.

O

UserPropertyField255_2#

N

User property field 255-2

string[255]

O

Legend:

K: Key property

N: Non-key property

M: Mandatory property during registration (omitting this property results in an error)

R: Property whose specification is recommended during new registration (omitting this property does not result in an error)

O: Optional property

#

This is an extended property. You can add managed items by editing the display name of this property and setting it to be displayed using the Customize Managed Items job menu.

20.2.28 SoftwareList (software list)

This class manages the names of purchased software assets in list format.

You can import or export this class. For details about importing by jamCsvImport.bat, see the section describing import processing by the Import job menu.

You can also specify this class as a search condition when creating a user report.

The following table lists the properties of SoftwareList.

Table 20‒62: Properties of SoftwareList

Property

Key

Description

Type [maximum length (bytes)]

Remarks

Specification in jamimport

CreationClassName

K

CCN

string[32]

This is SoftwareList.

M

Developer

N

Developer

string[60]

This is the developer of the software asset.

O

DownSoftwareListID1

N

Downgrade software name 01

uint32

These are the IDs of downgrade software that were registered.

If you are specifying this information for an import operation, specify the same value as for the corresponding object class SoftwareList.

O

DownSoftwareListID2

N

Downgrade software name 02

uint32

O

DownSoftwareListID3

N

Downgrade software name 03

uint32

O

DownSoftwareListID4

N

Downgrade software name 04

uint32

O

DownSoftwareListID5

N

Downgrade software name 05

uint32

O

DownSoftwareListID6

N

Downgrade software name 06

uint32

O

DownSoftwareListID7

N

Downgrade software name 07

uint32

O

DownSoftwareListID8

N

Downgrade software name 08

uint32

O

DownSoftwareListID9

N

Downgrade software name 09

uint32

O

DownSoftwareListID10

N

Downgrade software name 10

uint32

O

DownSoftwareListID11

N

Downgrade software name 11

uint32

O

DownSoftwareListID12

N

Downgrade software name 12

uint32

O

DownSoftwareListID13

N

Downgrade software name 13

uint32

O

DownSoftwareListID14

N

Downgrade software name 14

uint32

O

DownSoftwareListID15

N

Downgrade software name 15

uint32

O

DownSoftwareListID16

N

Downgrade software name 16

uint32

O

DownSoftwareListID17

N

Downgrade software name 17

uint32

O

DownSoftwareListID18

N

Downgrade software name 18

uint32

O

DownSoftwareListID19

N

Downgrade software name 19

uint32

O

DownSoftwareListID20

N

Downgrade software name 20

uint32

O

SoftwareKind

N

Software type

string[3]

See Software type.

If the Import job menu is used for importing and this property is omitted, Commercial is set.

M

SoftwareListID

K

Software list ID

uint32

This is a unique ID that identifies the software name.

When new information is imported, assign a unique value in the range from 10001 to 1000000000.

M

SoftwareName

N

Software name

string[1024]

This is the name of the software asset.

M

Threshold

N

Threshold

uint8

This is the threshold at which the Notice of license excess task issues an excess license notice.

The value is in percent (%).

O

UpdateTime

N

Update control

string[20]

This information is used to control concurrent updating of information.

O

UserPropertyArea_1#

N

User property area-1

string[255]

This item can manage a maximum of 255 bytes of information.

With a window operation, multiple character string lines can be specified.

O

UserPropertyArea_2#

N

User property area-2

string[255]

O

UserPropertyCode_1#

N

User property code-1

string[64]

This item can control code information.

O

UserPropertyCode_2#

N

User property code-2

string[64]

O

UserPropertyField128_1#

N

User property field 128-1

string[128]

This item can control a maximum of 128 bytes of information.

O

UserPropertyField128_2#

N

User property field 128-2

string[128]

O

UserPropertyField255_1#

N

User property field 255-1

string[255]

This item can manage a maximum of 255 bytes of information.

O

UserPropertyField255_2#

N

User property field 255-2

string[255]

O

Legend:

K: Key property

N: Non-key property

M: Mandatory property during registration

O: Optional property

#

This is an extended property. You can add managed items by editing the display name of this property and setting it to be displayed using the Customize Managed Items job menu.

The tables below provide details of the property codes.

Table 20‒63: Software type

Code

Display value

100

Commercial

101

Shareware

200

Freeware

20.2.29 UpdateRecord (device change log)

This class manages changes to a device's memory size or disk capacity.

You cannot import or export this class.

You can also specify this class as a search condition when creating a user report.

The following table lists the properties of UpdateRecord.

Table 20‒64: Properties of UpdateRecord

Property

Key

Description

Type [maximum length (bytes)]

Remarks

Specification in jamimport

AfterValue

N

After update

string[512]

This is the value after the change.

O

BeforeValue

N

Before update

string[512]

This is the value before the change.

O

CreationClassName

K

CCN

string[32]

This is UpdateRecord.

M

HistoryUpdateDate

K

Update date

date

This is the date the information was changed.

M

IndicationItemKey

K

Show item key

string[255]

This is the key value of the changed item.

M

LinkClass

N

Class for link

string[32]

This is the object class of the changed item.

M

LinkKey

K

Link key

string[32]

This is the key value for the changed object class.

M

SubLinkKey

K

Sub link key

string[32]

If the changed object class contains two keys, this is the value for the second key.

M

UpdateRecordInd

N

Record indicator

uint8

See Record indicator.

This indicates the type of updating.

M

Legend:

K: Key property

N: Non-key property

M: Mandatory property during registration

O: Optional property

The tables below provide details of the property codes.

Table 20‒65: Record indicator

Code

Display value

1

Add

2

Update

3

Delete

20.2.30 UserInfo (user information)

This class manages the users of the asset management system.

You can import or export this class. For details about importing by jamCsvImport.bat, see the section describing import processing by the Import job menu.

You can also specify this class as a search condition when creating a user report.

To import this class and register a user role for the user, also import the association class AuthorityLink (user and authority link). Once a role is granted, that user can log in to Asset Console.

To register a group to which the user belongs, import the association class MemberLink (user and member link).

The following table lists the properties of UserInfo,

Table 20‒66: Properties of UserInfo

Property

Key

Description

Type [maximum length (bytes)]

Remarks

Specification in jamimport

CreationClassName

K

CCN

string[32]

This is UserInfo.

M

ExecutiveName

N

Official title

string[255]

This is the user's position.

O

Explanation

N

Description

string[255]

This is a description of the user.

O

Mail

N

E-mail

string[255]

This is the user's email address.

O

Password

N

Password

string[64]

This is the user's password.

M

Telephonenumber

N

Phone

string[255]

This is user's phone number.

O

UpdateInd

N

Update indicator

uint32

This information is used by the asset management system. Do not update it.

O

UpdateTime

N

Update control

string[20]

This information is used to control concurrent updating of information.

O

UserID

K

User ID

string[64]

This is a unique ID that identifies the user.

M

UserName

N

User name

string[512]

This is the user name.

M

UserName_EN

N

User name (English)

string[512]

This the user name in English.

If the Import job menu is used for importing and this property is omitted, the value for User ID is set.

O

UserPropertyArea_1#

N

User property area-1

string[255]

This item can manage a maximum of 255 bytes of information.

With a window operation, multiple character string lines can be specified.

O

UserPropertyArea_2#

N

User property area-2

string[255]

O

UserPropertyCode_1#

N

User property code-1

string[64]

This item can control code information.

O

UserPropertyCode_2#

N

User property code-2

string[64]

O

UserPropertyField128_1#

N

User property field 128-1

string[128]

This item can control a maximum of 128 bytes of information.

O

UserPropertyField128_2#

N

User property field 128-2

string[128]

O

UserPropertyField255_1#

N

User property field 255-1

string[255]

This item can manage a maximum of 255 bytes of information.

O

UserPropertyField255_2#

N

User property field 255-2

string[255]

O

Legend:

K: Key property

N: Non-key property

M: Mandatory property during registration

O: Optional property

#

This is an extended property. You can add managed items by editing the display name of this property and setting it to be displayed using the Customize Managed Items job menu.

20.2.31 VolumeContract (volume contract information)

This class manages volume license information for software assets.

You can import or export this class. For details about importing by jamCsvImport.bat, see the section describing import processing by the Import job menu.

You can also specify this class as a search condition when creating a user report.

The following table lists the properties of VolumeContract.

Table 20‒67: Properties of VolumeContract

Property

Key

Description

Type [maximum length (bytes)]

Remarks

Specification in jamimport

Address

N

Contact post address

string[255]

This is the address on the contract.

O

Company

N

Contracted company

string[255]

This is the name of the contracted company.

O

ContactInfo

N

Contact phone/e-mail

string[255]

This is contact information at the contracted company.

O

ContactName

N

Contact person

string[512]

These are the contact people at the contracted company.

O

Contents

N

Contents

string[255]

This is the contents of the contract.

O

ContractDate

N

Contract date

date

This is the date of the contract.

O

ContractID

K

Contract ID

uint32

This is a unique ID that identifies the contract.

When new information is imported, assign a unique value in the range from 10001 to 1000000000.

M

ContractKind

N

Category

string[3]

See Category.

O

ContractNo

N

Contract No.

string[30]

This is the contract number.

R

ContractObject

N

Software asset

string[3]

See Software asset.

O

ContractStatus

N

Status

string[3]

See Status.

If the Import job menu is used for importing and this property is omitted, Under contract is set.

M

CreationClassName

K

CCN

string[32]

This is VolumeContract.

M

EndDate

N

Contract end date

date

This is the contract termination date.

O

Explanation

N

Description

string[255]

This is a description of the contract.

O

GroupID

N

Group ID

string[64]

This is a unique ID that identifies the group name.

O

MonthlyPrice

N

Monthly

string[15]

This is the monthly charge.

O

StartDate

N

Contract start date

date

This is the start date of the contract.

O

TargetPoint

N

Target point

uint32

This is the number of target points determined when the volume license was signed.

O

TotalPrice

N

Total

string[15]

This is the total contract cost.

O

UpdateTime

N

Update control

string[20]

This information is used to control concurrent updating of information.

O

UserPropertyArea_1#

N

User property area-1

string[255]

This item can manage a maximum of 255 bytes of information.

With a window operation, multiple character string lines can be specified.

O

UserPropertyArea_2#

N

User property area-2

string[255]

O

UserPropertyCode_1#

N

User property code-1

string[64]

This item can control code information.

O

UserPropertyCode_2#

N

User property code-2

string[64]

O

UserPropertyField128_1#

N

User property field 128-1

string[128]

This item can control a maximum of 128 bytes of information.

O

UserPropertyField128_2#

N

User property field 128-2

string[128]

O

UserPropertyField255_1#

N

User property field 255-1

string[255]

This item can manage a maximum of 255 bytes of information.

O

UserPropertyField255_2#

N

User property field 255-2

string[255]

O

Legend:

K: Key property

N: Non-key property

M: Mandatory property during registration (omitting this property results in an error)

R: Property whose specification is recommended during new registration (omitting this property does not result in an error)

O: Optional property

#

This is an extended property. You can add managed items by editing the display name of this property and setting it to be displayed using the Customize Managed Items job menu.

The tables below provide details of the property codes.

Table 20‒68: Category

Code

Display value

001

Select

002

OpenVolume

Table 20‒69: Software asset

Code

Display value

001

Application

002

Server

003

System

Table 20‒70: Status

Code

Display value

001

Under contract

501

Expire

999

Erase

20.3 List of properties of association classes

This section describes the association classes that can be imported and exported. It describes the associations between classes that are represented by association classes that are specific to Asset Console.

1 under Multiplex means that there is always one association, while 0..n (n: 0 or a greater integer) means that there can be no associations or one or more associations.

Each association class can be imported and exported by the jamimport and jamexport commands, respectively. For details about importing association classes, see 9.1 Registering CSV data (importing). For details about exporting association classes, see 9.2 Outputting CSV data (exporting).

In creating user reports, you can specify each association class as a search condition. For details about creating user reports, see 11.5 Adding windows for routine jobs (Create User Report).

20.3.1 AuthorityLink (user and authority link)

This class associates a user and a group.

Table 20‒71: List of classes associated by AuthorityLink

Class to be associated

Key property

Multiplex

UserInfo

UserID

0..n

RoleInfo

RoleID

1

20.3.2 ContractLeaseLink (lease contract link)

This class associates a device and lease contract information.

Table 20‒72: List of classes associated by ContractLeaseLink

Class to be associated

Key property

Multiplex

Contract

ContractID

1

AssetInfo

AssetID

0..n

20.3.3 ContractMaintenanceLink (maintenance contract link)

This class associates a device and a maintenance contract.

Table 20‒73: List of classes associated by ContractMaintenanceLink

Class to be associated

Key property

Multiplex

Contract

ContractID

1

AssetInfo

AssetID

0..n

20.3.4 ContractRentalLink (rental contract link)

This class associates a device and a rental contract.

Table 20‒74: List of classes associated by ContractRentalLink

Class to be associated

Key property

Multiplex

Contract

ContractID

1

AssetInfo

AssetID

0..n

20.3.5 DivisionLink (division information and group information)

This class associates a division and a group.

Table 20‒75: List of classes associated by DivisionLink

Class to be associated

Key property

Multiplex

DivisionInfo

DivisionID

0..n

GroupInfo

GroupID

0..n

20.3.6 DivisionUserLink (division information and user information)

This class associates a division and a user.

Table 20‒76: List of classes associated by DivisionUserLink

Class to be associated

Key property

Multiplex

DivisionInfo

DivisionID

0..n

UserInfo

UserID

0..n

20.3.7 IPAddressLink (IP address link)

This class associates network information and an IP address.

Table 20‒77: List of classes associated by IPAddressLink

Class to be associated

Key property

Multiplex

IPAddress

IPAddress

1

NetworkInfo

AssetID

0..n

NetworkInfo

NetworkID

0..n

20.3.8 JobRoleLink (User and official authority link)

This class associates user and official authority.

Table 20‒78: Classes associated by JobRoleLink

Class to be associated

Key property

Multiplex

JobRoleInfo

JobRoleID

0..n

UserInfo

UserID

0..n

20.3.9 MachinePermitLink (device and key link)

This class associates a license and a device to which the license was assigned.

Table 20‒79: List of classes associated by MachinePermitLink

Class to be associated

Key property

Multiplex

AssetInfo

AssetID

1

SoftwareKeyInfo

KeyID

0..n

SoftwareKeyInfo

SoftAssetID

0..n

20.3.10 MemberLink (user and member link)

This class associates a user and a group to which the user belongs. This association class can perform import processing from the Import job menu and export processing from the Export job menu. When you import or export the class and create conditions, GroupID and UserID are both optional.

Table 20‒80: List of classes associated by MemberLink

Class to be associated

Key property

Multiplex

GroupInfo

GroupID

1

UserInfo

UserID

0..n

20.3.11 RelationAssetLink (asset information and related asset information)

This class associates a device and another device.

Table 20‒81: List of classes associated by RelationAssetLink

Class to be associated

Key property

Multiplex

RelationAssetInfo

ParentAssetID

0..n

AssetInfo

AssetID

0..n

20.3.12 UserPermitLink (user and key link)

This class associates a license and a user to which the license was assigned.

Table 20‒82: List of classes associated by UserPermitLink

Class to be associated

Key property

Multiplex

SoftwareKeyInfo

KeyID

0..n

SoftwareKeyInfo

SoftAssetID

0..n

UserInfo

UserID

1

20.3.13 VolumeContractLink (volume contract link)

This class associates a volume contract and a software.

Table 20‒83: List of classes associated by VolumeContractLink

Class to be associated

Key property

Multiplex

AssetInfo

AssetID

0..n

VolumeContract

ContractID

1

20.4 Items to be imported or exported using a job menu

In the Import and Export job menus, the desired asset type is selected from Category. Therefore, the target item depends on the asset type selected in Category. The same applies to the target item for import by jamCsvImport.bat and export by jamCsvExport.bat.

The following table shows the asset types that can be selected in Category and the target classes:

Table 20‒84: Category types and target classes

Asset type

Asset information

Class

Device information

Asset information

AssetInfo

Hardware information

HardwareInfo

Network information

NetworkInfo

IP address control information

IPAddress

IP address link

IPAddressLink

Installed software information

Asset information

AssetInfo

Installed software information

InstalledInfo

Installed software list

InstalledList

Installed software list

Installed software list

InstalledList

Software information

Asset information

AssetInfo

Software information

SoftwareInfo

Software key information

SoftwareKeyInfo

Software list

SoftwareList

License information

LicenseInfo

Software list

Software list

SoftwareList

Group information

Group information

GroupInfo

User information

User information

UserInfo

Role information

RoleInfo

User and member link

MemberLink

User and authority link

AuthorityLink

User and official authority link

JobRoleLink

Location information

Location information

LocationInfo

Contract information

Contract information

Contract

Asset information

AssetInfo

Maintenance contract link

ContractMaintenanceLink

Rental contract information

Contract information

Contract

Asset information

AssetInfo

Rental contract link

ContractRentalLink

Lease contract information

Contract information

Contract

Asset information

AssetInfo

Lease contract link

ContractLeaseLink

Volume contract information

Volume contract information

VolumeContract

Asset information

AssetInfo

Volume contract link

VolumeContractLink

IP group information

IP group information

AddressGroup

Device catalog information

Device catalog

MachineCatalog

Problems

Maintenance log

Maintenance

Assigned license

information

Asset information

AssetInfo

User information

UserInfo

Software information

SoftwareInfo

Software key information

SoftwareKeyInfo

Software list

SoftwareList

Software key link

MachinePermitLink

User and key link

UserPermitLink

Patches

Asset information

AssetInfo

Patch information

PatchInfo

Patch name list

PatchList

Virus definition

Asset information

AssetInfo

Virus definition information

InstalledVirusDefInfo

Related asset information

Related asset information

RelationAssetInfo

Division information

Division information

DivisionInfo

Division information and group information

DivisionLink

Assign Divisions

Division information

DivisionInfo

Division information and user information

DivisionUserLink

User definition (user report)#

--

--

User definition (form)#

--

--

Customize (Acquire ITDM2 management information.)#

--

--

User definition (import/export)#

--

--

User definition (item definition)#

--

--

User definition (contract history)#

--

--

Legend:

--: Not applicable

#

The set information is imported or exported in a batch operation. The contents cannot be edited.

If all the conditions are met for the information to be imported, association class information is created without having to set the assigned items.

For the information to be imported, specify detailed items for each Category when creating the importing condition. The tables below show the import target items by Category. Note that the managed items that are hidden by the Customize Managed Items job menu are not displayed in Managed items of the Import menu or Enable items to export of the Export menu.

20.4.1 Items targeted by the Device information asset type

The following table lists the items that are targeted by the Device information asset type.

Table 20‒85: Items targeted by the Device information asset type

CSV file item name

Class

Property

Specification

Asset ID (Asset information)

AssetInfo

AssetID

O

Asset No. (Asset information)

AssetNo

O

Group ID (Asset information)

GroupID

O

Group name (Asset information)

GroupName

O

Group name (Asset information)

GroupName_EN

O

User ID (Asset information)

UserID

O

User name (Asset information)

UserName

O

User name (English)(Asset information)

UserName_EN

O

Location ID (Asset information)

LocationID

O

Location (Asset information)

LocationName

O

Location (Asset information)

LocationName_EN

O

Usage management (Asset information)

AssetWorkKind

M

Status (Asset information)

AssetStatus

M

Purchase price (Asset information)

PurchasePrice

O

Registration date (Asset information)

RegistrationDate

M

Purpose (Asset information)

Purpose

O

Notes (Asset information)

Note

O

ITDM2 Agent installed status (Asset information)

DMStatus

O

Update user name (Asset information)

UpdateUser

O

Stocktaking date (Asset information)

StocktakingDate

O

Start date of use (Asset information)

StartDate

O

End date of use (Asset information)

EndDate

O

Host identifier (Asset information)

InventoryKey

O

Last updated date of ITDM2 (Asset information)

DMLastUpdateTime

O

Managed group ID (Asset information)

ManagerialGroupID

O

Managed group (Asset information)

ManagerialGroup

O

Managed group (Asset information)

ManagerialGroup_EN

O

User ID of administrator (Asset information)

ManagerialUserID

O

Administrator (Asset information)

ManagerialUser

O

Administrator (Asset information)

ManagerialUser_EN

O

User property field 32-1 (Asset information)

UserPropertyField32_1

O

User property field 32-2 (Asset information)

UserPropertyField32_2

O

User property field 32-3 (Asset information)

UserPropertyField32_3

O

User property field 32-4 (Asset information)

UserPropertyField32_4

O

User property field 32-5 (Asset information)

UserPropertyField32_5

O

User property field 32-6 (Asset information)

UserPropertyField32_6

O

User property field 64-1 (Asset information)

UserPropertyField64_1

O

User property field 64-2 (Asset information)

UserPropertyField64_2

O

User property field 128-1 (Asset information)

UserPropertyField128_1

O

User property field 128-2 (Asset information)

UserPropertyField128_2

O

User property field 255-1 (Asset information)

UserPropertyField255_1

O

User property field 255-2 (Asset information)

UserPropertyField255_2

O

User property area-1 (Asset information)

UserPropertyArea_1

O

User property area-2 (Asset information)

UserPropertyArea_2

O

User property code-1 (Asset information)

UserPropertyCode_1

O

User property code-2 (Asset information)

UserPropertyCode_2

O

User property code-3 (Asset information)

UserPropertyCode_3

O

User property code-4 (Asset information)

UserPropertyCode_4

O

User property code-5 (Asset information)

UserPropertyCode_5

O

User property code-6 (Asset information)

UserPropertyCode_6

O

User property date-1 (Asset information)

UserPropertyDate_1

O

User property date-2 (Asset information)

UserPropertyDate_2

O

User property date-3 (Asset information)

UserPropertyDate_3

O

User property date-4 (Asset information)

UserPropertyDate_4

O

User property date-5 (Asset information)

UserPropertyDate_5

O

User property date-6 (Asset information)

UserPropertyDate_6

O

User property unit-1 (Asset information)

UserPropertyUint_1

O

User property unit-2 (Asset information)

UserPropertyUint_2

O

User property unit-3 (Asset information)

UserPropertyUint_3

O

User property unit-4 (Asset information)

UserPropertyUint_4

O

User property unit-5 (Asset information)

UserPropertyUint_5

O

User property unit-6 (Asset information)

UserPropertyUint_6

O

Device type (Hardware information)

HardwareInfo

MachineKind

O

Developer (Hardware information)

Developer

O

Model (Hardware information)

Model

O

Serial No. (Hardware information)

SerialNo

O

Device name (Hardware information)

Name

O

CPU (Hardware information)

CPUType

O

Processor speed (Hardware information)

CPUClock

O

Number of processors (Hardware information)

CPUNumber

O

Memory (Hardware information)

MemorySize

O

Hard disk sizes (Hardware information)

TotalHDSize

O

Hard disk free space (Hardware information)

RemainHDSize

O

Composition (Hardware information)

ModelKind

O

Specification (Hardware information)

Specification

O

Monitor type (Hardware information)

MonitorKind

O

Monitor resolution (Hardware information)

MonitorResolution

O

Monitor size (Hardware information)

MonitorSize

O

Number of ports (Hardware information)

NumberOFPort

O

Line speed (Hardware information)

CircuitSpeed

O

IP address (Hardware information)

IPAddress

O

MAC address (Hardware information)

MACAddress

O

Host name (Hardware information)

HostName

O

MBSA version (Hardware information)

MBSAVersion

O

OS (Hardware information)

OSInfo

O

OS version (Hardware information)

OSVersion

O

Computer ID (Hardware information)

ComputerID

O

User property field 32-1 (Hardware information)

UserPropertyField32_1

O

User property field 32-2 (Hardware information)

UserPropertyField32_2

O

User property field 32-3 (Hardware information)

UserPropertyField32_3

O

User property field 32-4 (Hardware information)

UserPropertyField32_4

O

User property field 32-5 (Hardware information)

UserPropertyField32_5

O

User property field 32-6 (Hardware information)

UserPropertyField32_6

O

User property field 32-7 (Hardware information)

UserPropertyField32_7

O

User property field 32-8 (Hardware information)

UserPropertyField32_8

O

User property field 64-1 (Hardware information)

UserPropertyField64_1

O

User property field 64-2 (Hardware information)

UserPropertyField64_2

O

User property field 64-3 (Hardware information)

UserPropertyField64_3

O

User property field 64-4 (Hardware information)

UserPropertyField64_4

O

User property field 64-5 (Hardware information)

UserPropertyField64_5

O

User property field 64-6 (Hardware information)

UserPropertyField64_6

O

User property field 64-7 (Hardware information)

UserPropertyField64_7

O

User property field 64-8 (Hardware information)

UserPropertyField64_8

O

User property field 128-1 (Hardware information)

UserPropertyField128_1

O

User property field 128-2 (Hardware information)

UserPropertyField128_2

O

User property field 128-3 (Hardware information)

UserPropertyField128_3

O

User property field 128-4 (Hardware information)

UserPropertyField128_4

O

User property field 128-5 (Hardware information)

UserPropertyField128_5

O

User property field 128-6 (Hardware information)

UserPropertyField128_6

O

User property field 128-7 (Hardware information)

UserPropertyField128_7

O

User property field 128-8 (Hardware information)

UserPropertyField128_8

O

User property field 255-1 (Hardware information)

UserPropertyField255_1

O

User property field 255-2 (Hardware information)

UserPropertyField255_2

O

User property field 255-3 (Hardware information)

UserPropertyField255_3

O

User property field 255-4 (Hardware information)

UserPropertyField255_4

O

User property field 255-5 (Hardware information)

UserPropertyField255_5

O

User property field 255-6 (Hardware information)

UserPropertyField255_6

O

User property field 255-7 (Hardware information)

UserPropertyField255_7

O

User property field 255-8 (Hardware information)

UserPropertyField255_8

O

User property area-1 (Hardware information)

UserPropertyArea_1

O

User property area-2 (Hardware information)

UserPropertyArea_2

O

User property area-3 (Hardware information)

UserPropertyArea_3

O

User property area-4 (Hardware information)

UserPropertyArea_4

O

User property code-1 (Hardware information)

UserPropertyCode_1

O

User property code-2 (Hardware information)

UserPropertyCode_2

O

User property code-3 (Hardware information)

UserPropertyCode_3

O

User property code-4 (Hardware information)

UserPropertyCode_4

O

User property code-5 (Hardware information)

UserPropertyCode_5

O

User property code-6 (Hardware information)

UserPropertyCode_6

O

User property code-7 (Hardware information)

UserPropertyCode_7

O

User property code-8 (Hardware information)

UserPropertyCode_8

O

User property code-9 (Hardware information)

UserPropertyCode_9

O

User property code-10 (Hardware information)

UserPropertyCode_10

O

User property code-11 (Hardware information)

UserPropertyCode_11

O

User property code-12 (Hardware information)

UserPropertyCode_12

O

User property date-1 (Hardware information)

UserPropertyDate_1

O

User property date-2 (Hardware information)

UserPropertyDate_2

O

User property date-3 (Hardware information)

UserPropertyDate_3

O

User property date-4 (Hardware information)

UserPropertyDate_4

O

User property date-5 (Hardware information)

UserPropertyDate_5

O

User property date-6 (Hardware information)

UserPropertyDate_6

O

User property unit-1 (Hardware information)

UserPropertyUint_1

O

User property unit-2 (Hardware information)

UserPropertyUint_2

O

User property unit-3 (Hardware information)

UserPropertyUint_3

O

User property unit-4 (Hardware information)

UserPropertyUint_4

O

User property unit-5(Hardware information)

UserPropertyUint_5

O

User property unit-6 (Hardware information)

UserPropertyUint_6

O

Network info ID (Network information)

NetworkInfo

NetworkID

O

MAC address (Network information)

MACAddress

O

Node name (host name) (Network information)

NodeName

O

Computer name (Network information)

ComputerName

O

DHCP server name (Network information)

DHCPServerName

O

IP address (Network information)

IPAddress

O

Global IP address (Network information)

GlobalIPAddress

O

Default Gateway (Network information)

DefaultGateway

O

Subnet mask (Network information)

SubnetMask

O

Port information (Network information)

PortInfo

O

IP address type (Network information)

IPAddressKind

O

ITDM2 management information acquisition control (Network information)

InfoInd

O

User property field 128-1 (Network information)

UserPropertyField128_1

O

User property field 128-2 (Network information)

UserPropertyField128_2

O

User property field 255-1 (Network information)

UserPropertyField255_1

O

User property field 255-2 (Network information)

UserPropertyField255_2

O

User property area-1 (Network information)

UserPropertyArea_1

O

User property area-2 (Network information)

UserPropertyArea_2

O

User property code-1 (Network information)

UserPropertyCode_1

O

User property code-2 (Network information)

UserPropertyCode_2

O

Legend:

M: Mandatory item during new registration

O: Optional item

20.4.2 Items targeted by the Installed software information asset type

The following table lists the items that are targeted by the Installed software information asset type.

Table 20‒86: Items targeted by the Installed software information asset type

CSV file item name

Class

Property

Specification

Asset ID (Asset information)

AssetInfo

AssetID

O

Asset No. (Asset information)

AssetNo

O

Installed software ID (Installed software list)

InstalledList

InstalledID

O

Installed software name (Installed software list)

InstalledName

O

Installed software version (Installed software list)

InstalledVersion

O

File name (Installed software list)

FileName

O

File size (Installed software list)

FileSize

O

File date (Installed software list)

FileDate

O

Product ID (Installed software information)

InstalledInfo

ProductID

O

Installed date (Installed software information)

InstalledDate

O

ITDM2 management information acquisition control (Installed software information)

InfoInd

O

User property field 128-1 (Installed software information)

UserPropertyField128_1

O

User property field 128-2 (Installed software information)

UserPropertyField128_2

O

User property field 255-1 (Installed software information)

UserPropertyField255_1

O

User property field 255-2 (Installed software information)

UserPropertyField255_2

O

User property area-1 (Installed software information)

UserPropertyArea_1

O

User property area-2 (Installed software information)

UserPropertyArea_2

O

User property code-1 (Installed software information)

UserPropertyCode_1

O

User property code-2 (Installed software information)

UserPropertyCode_2

O

Legend:

O: Optional item

20.4.3 Items targeted by the Installed software list asset type

The following table lists the items that are targeted by the Installed software list asset type.

Table 20‒87: Items targeted by the Installed software list asset type

CSV file item name

Class

Property

Specification

Installed software ID (Installed software list)

InstalledList

InstalledID

O

Installed software name (Installed software list)

InstalledName

O

Installed software version (Installed software list)

InstalledVersion

O

Permission (Installed software list)

InstalledPermit

M

Software type (Installed software list)

InstalledKind

M

Managed level (Installed software list)

InstalledInd

M

File name (Installed software list)

FileName

O

File size (Installed software list)

FileSize

O

File date (Installed software list)

FileDate

O

User property field 128-1 (Installed software list)

UserPropertyField128_1

O

User property field 128-2 (Installed software list)

UserPropertyField128_2

O

User property field 255-1 (Installed software list)

UserPropertyField255_1

O

User property field 255-2 (Installed software list)

UserPropertyField255_2

O

User property area-1 (Installed software list)

UserPropertyArea_1

O

User property area-2 (Installed software list)

UserPropertyArea_2

O

User property code-1 (Installed software list)

UserPropertyCode_1

O

User property code-2 (Installed software list)

UserPropertyCode_2

O

Software list ID (Software list)

SoftwareList

SoftwareListID

O

Software name (Software list)

SoftwareName

O

Software type (Software list)

SoftwareKind

O

Legend:

M: Mandatory item during new registration

O: Optional item

20.4.4 Items targeted by the Software information asset type

The following table lists the items that are targeted by the Software information asset type.

Table 20‒88: Items targeted by the Software information asset type

CSV file item name

Class

Property

Specification

Asset ID (Asset information)

AssetInfo

AssetID

O

Asset No. (Asset information)

AssetNo

O

Group ID (Asset information)

GroupID

O

Group name (Asset information)

GroupName

O

Group name (Asset information)

GroupName_EN

O

User ID (Asset information)

UserID

O

User name (Asset information)

UserName

O

User name (English)(Asset information)

UserName_EN

O

Usage management (Asset information)

AssetWorkKind

M

Software status (Asset information)

SoftwareStatus

M

Purchase price (Asset information)

PurchasePrice

O

Registration date (Asset information)

RegistrationDate

M

Purpose (Asset information)

Purpose

O

Notes (Asset information)

Note

O

Asset type (Asset information)

AssetKind

O

Update user name (Asset information)

UpdateUser

O

Stocktaking date (Asset information)

StocktakingDate

O

Start date of use (Asset information)

StartDate

O

End date of use (Asset information)

EndDate

O

Managed group ID (Asset information)

ManagerialGroupID

O

Managed group (Asset information)

ManagerialGroup

O

Managed group (Asset information)

ManagerialGroup_EN

O

User ID of administrator (Asset information)

ManagerialUserID

O

Administrator (Asset information)

ManagerialUser

O

Administrator (Asset information)

ManagerialUser_EN

O

User property field 32-1 (Asset information)

UserPropertyField32_1

O

User property field 32-2 (Asset information)

UserPropertyField32_2

O

User property field 32-3 (Asset information)

UserPropertyField32_3

O

User property field 32-4 (Asset information)

UserPropertyField32_4

O

User property field 32-5 (Asset information)

UserPropertyField32_5

O

User property field 32-6 (Asset information)

UserPropertyField32_6

O

User property field 64-1 (Asset information)

UserPropertyField64_1

O

User property field 64-2 (Asset information)

UserPropertyField64_2

O

User property field 128-1 (Asset information)

UserPropertyField128_1

O

User property field 128-2 (Asset information)

UserPropertyField128_2

O

User property field 255-1 (Asset information)

UserPropertyField255_1

O

User property field 255-2 (Asset information)

UserPropertyField255_2

O

User property area-1 (Asset information)

UserPropertyArea_1

O

User property area-2 (Asset information)

UserPropertyArea_2

O

User property code-1 (Asset information)

UserPropertyCode_1

O

User property code-2 (Asset information)

UserPropertyCode_2

O

User property code-3 (Asset information)

UserPropertyCode_3

O

User property code-4 (Asset information)

UserPropertyCode_4

O

User property code-5 (Asset information)

UserPropertyCode_5

O

User property code-6 (Asset information)

UserPropertyCode_6

O

User property date-1 (Asset information)

UserPropertyDate_1

O

User property date-2 (Asset information)

UserPropertyDate_2

O

User property date-3 (Asset information)

UserPropertyDate_3

O

User property date-4 (Asset information)

UserPropertyDate_4

O

User property date-5 (Asset information)

UserPropertyDate_5

O

User property date-6 (Asset information)

UserPropertyDate_6

O

User property unit-1 (Asset information)

UserPropertyUint_1

O

User property unit-2 (Asset information)

UserPropertyUint_2

O

User property unit-3 (Asset information)

UserPropertyUint_3

O

User property unit-4 (Asset information)

UserPropertyUint_4

O

User property unit-5 (Asset information)

UserPropertyUint_5

O

User property unit-6 (Asset information)

UserPropertyUint_6

O

Number of licenses (Software information)

SoftwareInfo

NumberOFLicense

O

Purchase point (Software information)

NumberOFPoint

O

User property field 128-1 (Software information)

UserPropertyField128_1

O

User property field 128-2 (Software information)

UserPropertyField128_2

O

User property field 255-1 (Software information)

UserPropertyField255_1

O

User property field 255-2 (Software information)

UserPropertyField255_2

O

User property area-1 (Software information)

UserPropertyArea_1

O

User property area-2 (Software information)

UserPropertyArea_2

O

User property code-1 (Software information)

UserPropertyCode_1

O

User property code-2 (Software information)

UserPropertyCode_2

O

Key ID (Software key information)

SoftwareKeyInfo

KeyID

O

Product ID (Software key information)

ProductID

O

License key (Software key information)

LicenseKey

O

Serial No. (Software key information)

SerialNo

O

Notes (Software key information)

Note

O

User property field 128-1 (Software key information)

UserPropertyField128_1

O

User property field 128-2 (Software key information)

UserPropertyField128_2

O

User property field 255-1 (Software key information)

UserPropertyField255_1

O

User property field 255-2 (Software key information)

UserPropertyField255_2

O

User property area-1 (Software key information)

UserPropertyArea_1

O

User property area-2 (Software key information)

UserPropertyArea_2

O

User property code-1 (Software key information)

UserPropertyCode_1

O

User property code-2 (Software key information)

UserPropertyCode_2

O

Software list ID (Software list)

SoftwareList

SoftwareListID

O

Software name (Software list)

SoftwareName

M

Software type (Software list)

SoftwareKind

O

License ID (License information)

LicenseInfo

LicenseID

O

License name (License information)

LicenseName

O

License type (License information)

LicenseType

O

Upgrade assurance (License information)

UpGrade

O

Downgrade (License information)

DownGrade

O

Licensing method (License information)

PurchaseType

O

License category (License information)

LicenseCategory

O

Description (License information)

Description

O

Notes (License information)

Note

O

User property field 128-1 (License information)

UserPropertyField128_1

O

User property field 128-2 (License information)

UserPropertyField128_2

O

User property field 255-1 (License information)

UserPropertyField255_1

O

User property field 255-2 (License information)

UserPropertyField255_2

O

User property area-1 (License information)

UserPropertyArea_1

O

User property area-2 (License information)

UserPropertyArea_2

O

User property code-1 (License information)

UserPropertyCode_1

O

User property code-2 (License information)

UserPropertyCode_2

O

Legend:

M: Mandatory item during new registration

O: Optional item

20.4.5 Items targeted by the Software list asset type

The following table lists the items that are targeted by the Software list asset type.

Table 20‒89: Items targeted by the Software list asset type

CSV file item name

Class

Property

Specification

Software list ID (Software list)

SoftwareList

SoftwareListID

O

Software name (Software list)

SoftwareName

M

Developer (Software list)

Developer

O

Software type (Software list)

SoftwareKind

M

Threshold (Software list)

Threshold

O

User property field 128-1 (Software list)

UserPropertyField128_1

O

User property field 128-2 (Software list)

UserPropertyField128_2

O

User property field 255-1 (Software list)

UserPropertyField255_1

O

User property field 255-2 (Software list)

UserPropertyField255_2

O

User property area-1 (Software list)

UserPropertyArea_1

O

User property area-2 (Software list)

UserPropertyArea_2

O

User property code-1 (Software list)

UserPropertyCode_1

O

User property code-2 (Software list)

UserPropertyCode_2

O

Legend:

M: Mandatory item during new registration

O: Optional item

20.4.6 Items targeted by the Group information asset type

The following table lists the items that are targeted by the Group information asset type.

Table 20‒90: Items targeted by the Group information asset type

CSV file item name

Class

Property

Specification

Group ID (Group information)

GroupInfo

GroupID

M

Upper Group ID (Group information)

UpperLinkID

O

Group name (Group information)

GroupName

M

Group name (English)(Group information)

GroupName_EN

O

Group code (Group information)

GroupCode

O

Cost group code (Group information)

CostPriceCode

O

Managed label (Group information)

ManagedLabel

O

Description (Group information)

Explanation

O

ADGUID (Group information)

AdGuid

O

User property field 128-1 (Group information)

UserPropertyField128_1

O

User property field 128-2 (Group information)

UserPropertyField128_2

O

User property field 255-1 (Group information)

UserPropertyField255_1

O

User property field 255-2 (Group information)

UserPropertyField255_2

O

User property area-1 (Group information)

UserPropertyArea_1

O

User property area-2 (Group information)

UserPropertyArea_2

O

User property code-1 (Group information)

UserPropertyCode_1

O

User property code-2 (Group information)

UserPropertyCode_2

O

Legend:

M: Mandatory item during new registration

O: Optional item

20.4.7 Items targeted by the User information asset type

The following table lists the items that are targeted by the User information asset type.

Table 20‒91: Items targeted by the User information asset type

CSV file item name

Class

Property

Specification

User ID (User information)

UserInfo

UserID

M

User name (User information)

UserName

M

User name (English)(User information)

UserName_EN

O

Phone (User information)

Telephonenumber

O

E-mail (User information)

Mail

O

Official title (User information)

ExecutiveName

O

Description (User information)

Explanation

O

User property field 128-1 (User information)

UserPropertyField128_1

O

User property field 128-2 (User information)

UserPropertyField128_2

O

User property field 255-1 (User information)

UserPropertyField255_1

O

User property field 255-2 (User information)

UserPropertyField255_2

O

User property area-1 (User information)

UserPropertyArea_1

O

User property area-2 (User information)

UserPropertyArea_2

O

User property code-1 (User information)

UserPropertyCode_1

O

User property code-2 (User information)

UserPropertyCode_2

O

Group ID (Group information)

GroupInfo

GroupID

O

Group name (Group information)

FullPathName

O

Role ID (Role information)

RoleInfo

RoleID

O

Role name (Role information)

RoleName

O

Role name (Role information)

RoleName_EN

O

Managed label (Role information)

ManagedLabel

O

Official authority ID (Official authority)

JobRoleInfo

JobRoleID

O

Official authority name (Official authority)

JobRoleName

O

Legend:

M: Mandatory item during new registration

O: Optional item

20.4.8 Items targeted by the Location information asset type

The following table lists the items that are targeted by the Location information asset type.

Table 20‒92: Items targeted by the Location information asset type

CSV file item name

Class

Property

Specification

Location ID (Location information)

LocationInfo

LocationID

O

Upper location ID (Location information)

UpperLinkID

O

Location (Location information)

LocationName

M

Location name (English)(Location information)

LocationName_EN

O

Contact post address (Location information)

Address

O

Area size (Location information)

AreaSize

O

Attribute (Location information)

Attribute

M

Description (Location information)

Explanation

O

User property field 128-1 (Location information)

UserPropertyField128_1

O

User property field 128-2 (Location information)

UserPropertyField128_2

O

User property field 255-1 (Location information)

UserPropertyField255_1

O

User property field 255-2 (Location information)

UserPropertyField255_2

O

User property area-1 (Location information)

UserPropertyArea_1

O

User property area-2 (Location information)

UserPropertyArea_2

O

User property code-1 (Location information)

UserPropertyCode_1

O

User property code-2 (Location information)

UserPropertyCode_2

O

Legend:

M: Mandatory item during new registration

O: Optional item

20.4.9 Items targeted by the Maintenance contract information asset type

The following table lists the items that are targeted by the Maintenance contract information asset type.

Table 20‒93: Items targeted by the Maintenance contract information asset type

CSV file item name

Class

Property

Specification

Asset ID (Asset information)

AssetInfo

AssetID

O

Asset No. (Asset information)

AssetNo

O

Contract ID (Contract information)

Contract

ContractID

O

Contract No. (Contract information)

ContractNo

M

Frequency (Contract information)

RenewalTimes

O

Category (Contract information)

ContractKind

O

Subject (Contract information)

ContractObject

M

Contract date (Contract information)

ContractDate

M

Contract start date (Contract information)

StartDate

M

Contract end date (Contract information)

EndDate

M

Contracted company (Contract information)

Company

M

Contact post address (Contract information)

Address

O

Contact phone/e-mail (Contract information)

ContactInfo

O

Contact person (Contract information)

ContactName

O

Contents (Contract information)

Contents

O

Total (Contract information)

TotalPrice

O

Monthly (Contract information)

MonthlyPrice

O

Description (Contract information)

Explanation

O

Status (Contract information)

ContractStatus

M

Contact person 2 (Contract information)

ContactName_2

O

Contact phone/e-mail 2 (Contract information)

ContactInfo_2

O

Contact person 3 (Contract information)

ContactName_3

O

Contact phone/e-mail 3 (Contract information)

ContactInfo_3

O

User property field 128-1 (Contract information)

UserPropertyField128_1

O

User property field 128-2 (Contract information)

UserPropertyField128_2

O

User property field 255-1 (Contract information)

UserPropertyField255_1

O

User property field 255-2 (Contract information)

UserPropertyField255_2

O

User property area-1 (Contract information)

UserPropertyArea_1

O

User property area-2 (Contract information)

UserPropertyArea_2

O

User property code-1 (Contract information)

UserPropertyCode_1

O

User property code-2 (Contract information)

UserPropertyCode_2

O

Group name (Group information)

GroupInfo

FullPathName

O

Legend:

M: Mandatory item during new registration

O: Optional item

20.4.10 Items targeted by the Rental contract information asset type

The following table lists the items that are targeted by the Rental contract information asset type.

Table 20‒94: Items targeted by the Rental contract information asset type

CSV file item name

Class

Property

Specification

Asset ID (Asset information)

AssetInfo

AssetID

O

Asset No. (Asset information)

AssetNo

O

Contract ID (Contract information)

Contract

ContractID

O

Contract No. (Contract information)

ContractNo

M

Frequency (Contract information)

RenewalTimes

O

Category (Contract information)

ContractKind

O

Subject (Contract information)

ContractObject

M

Contract date (Contract information)

ContractDate

M

Contract start date (Contract information)

StartDate

M

Contract end date (Contract information)

EndDate

M

Contracted company (Contract information)

Company

M

Contact post address (Contract information)

Address

O

Contact phone/e-mail (Contract information)

ContactInfo

O

Contact person (Contract information)

ContactName

O

Contents (Contract information)

Contents

O

Total (Contract information)

TotalPrice

O

Monthly (Contract information)

MonthlyPrice

O

Description (Contract information)

Explanation

O

Status (Contract information)

ContractStatus

M

Contact person 2 (Contract information)

ContactName_2

O

Contact phone/e-mail 2 (Contract information)

ContactInfo_2

O

Contact person 3 (Contract information)

ContactName_3

O

Contact phone/e-mail 3 (Contract information)

ContactInfo_3

O

User property field 128-1 (Contract information)

UserPropertyField128_1

O

User property field 128-2 (Contract information)

UserPropertyField128_2

O

User property field 255-1 (Contract information)

UserPropertyField255_1

O

User property field 255-2 (Contract information)

UserPropertyField255_2

O

User property area-1 (Contract information)

UserPropertyArea_1

O

User property area-2 (Contract information)

UserPropertyArea_2

O

User property code-1 (Contract information)

UserPropertyCode_1

O

User property code-2 (Contract information)

UserPropertyCode_2

O

Group name (Group information)

GroupInfo

FullPathName

O

Legend:

M: Mandatory item during new registration

O: Optional item

20.4.11 Items targeted by the Lease contract information asset type

The following table lists the items that are targeted by the Lease contract information asset type.

Table 20‒95: Items targeted by the Lease contract information asset type

CSV file item name

Class

Property

Specification

Asset ID (Asset information)

AssetInfo

AssetID

O

Asset No. (Asset information)

AssetNo

O

Contract ID (Contract information)

Contract

ContractID

O

Contract No. (Contract information)

ContractNo

M

Frequency (Contract information)

RenewalTimes

O

Category (Contract information)

ContractKind

O

Subject (Contract information)

ContractObject

M

Contract date (Contract information)

ContractDate

M

Contract start date (Contract information)

StartDate

M

Contract end date (Contract information)

EndDate

M

Contracted company (Contract information)

Company

M

Contact post address (Contract information)

Address

O

Contact phone/e-mail (Contract information)

ContactInfo

O

Contact person (Contract information)

ContactName

O

Contents (Contract information)

Contents

O

Total (Contract information)

TotalPrice

O

Monthly (Contract information)

MonthlyPrice

O

Description (Contract information)

Explanation

O

Status (Contract information)

ContractStatus

M

Contact person 2 (Contract information)

ContactName_2

O

Contact phone/e-mail 2 (Contract information)

ContactInfo_2

O

Contact person 3 (Contract information)

ContactName_3

O

Contact phone/e-mail 3 (Contract information)

ContactInfo_3

O

User property field 128-1 (Contract information)

UserPropertyField128_1

O

User property field 128-2 (Contract information)

UserPropertyField128_2

O

User property field 255-1 (Contract information)

UserPropertyField255_1

O

User property field 255-2 (Contract information)

UserPropertyField255_2

O

User property area-1 (Contract information)

UserPropertyArea_1

O

User property area-2 (Contract information)

UserPropertyArea_2

O

User property code-1 (Contract information)

UserPropertyCode_1

O

User property code-2 (Contract information)

UserPropertyCode_2

O

Group name (Group information)

GroupInfo

FullPathName

O

Legend:

M: Mandatory item during new registration

O: Optional item

20.4.12 Items targeted by the Volume contract information asset type

The following table lists the items that are targeted by the Volume contract information asset type.

Table 20‒96: Items targeted by the Volume contract information asset type

CSV file item name

Class

Property

Specification

Asset ID (Asset information)

AssetInfo

AssetID

O

Asset No. (Asset information)

AssetNo

O

Contract ID (Volume contract information)

VolumeContract

ContractID

O

Contract No. (Volume contract information)

ContractNo

M

Category (Volume contract information)

ContractKind

O

Software asset (Volume contract information)

ContractObject

O

Target point (Volume contract information)

TargetPoint

O

Contract date (Volume contract information)

ContractDate

O

Contract start date (Volume contract information)

StartDate

O

Contract end date (Volume contract information)

EndDate

O

Contracted company (Volume contract information)

Company

O

Contact post address (Volume contract information)

Address

O

Contact phone/e-mail (Volume contract information)

ContactInfo

O

Contact person (Volume contract information)

ContactName

O

Contents (Volume contract information)

Contents

O

Total (Volume contract information)

TotalPrice

O

Monthly (Volume contract information)

MonthlyPrice

O

Description (Volume contract information)

Explanation

O

Status (Volume contract information)

ContractStatus

M

User property field 128-1 (Volume contract information)

UserPropertyField128_1

O

User property field 128-2 (Volume contract information)

UserPropertyField128_2

O

User property field 255-1 (Volume contract information)

UserPropertyField255_1

O

User property field 255-2 (Volume contract information)

UserPropertyField255_2

O

User property area-1 (Volume contract information)

UserPropertyArea_1

O

User property area-2 (Volume contract information)

UserPropertyArea_2

O

User property code-1 (Volume contract information)

UserPropertyCode_1

O

User property code-2 (Volume contract information)

UserPropertyCode_2

O

Group name (Group information)

GroupInfo

FullPathName

O

Legend:

M: Mandatory item during new registration

O: Optional item

20.4.13 Items targeted by the IP group information asset type

The following table lists the items that are targeted by the IP group information asset type.

Table 20‒97: Items targeted by the IP group information asset type

CSV file item name

Class

Property

Specification

IP group ID (IP group information)

AddressGroup

IPGroupID

O

IP group name (IP group information)

IPGroupName

M

Start IP address(IP group information)

StartIPAddress

M

End IP address(IP group information)

EndIPAddress

M

Gateway address (IP group information)

Gateway

O

Subnet mask (IP group information)

SubnetMask

M

DHCP server name (IP group information)

DHCPServerName

O

Purpose (IP group information)

Purpose

O

User ID of administrator (IP group information)

ManagerialUserID

O

Group ID (IP group information)

GroupID

O

Location ID (IP group information)

LocationID

O

User property field 128-1 (IP group information)

UserPropertyField128_1

O

User property field 128-2 (IP group information)

UserPropertyField128_2

O

User property field 255-1 (IP group information)

UserPropertyField255_1

O

User property field 255-2 (IP group information)

UserPropertyField255_2

O

User property area-1 (IP group information)

UserPropertyArea_1

O

User property area-2 (IP group information)

UserPropertyArea_2

O

User property code-1 (IP group information)

UserPropertyCode_1

O

User property code-2 (IP group information)

UserPropertyCode_2

O

Legend:

M: Mandatory item during new registration

O: Optional item

20.4.14 Items targeted by the Device catalog information asset type

The following table lists the items that are targeted by the Device catalog information asset type.

Table 20‒98: Items targeted by the Device catalog information asset type

CSV file item name

Class

Property

Specification

Catalog ID (Device catalog)

MachineCatalog

CatalogID

O

Device type (Device catalog)

MachineKind

O

Device name (Device catalog)

Name

M

Model (Device catalog)

Model

M

Developer (Device catalog)

Developer

O

Purchase price (Device catalog)

PurchasePrice

O

CPU (Device catalog)

CPUType

O

Processor speed (Device catalog)

CPUClock

O

Number of processors (Device catalog)

CPUNumber

O

Monitor type (Device catalog)

MonitorKind

O

Monitor resolution (Device catalog)

MonitorResolution

O

Monitor size (Device catalog)

MonitorSize

O

Memory (Device catalog)

MemorySize

O

Hard disk sizes (Device catalog)

TotalHDSize

O

Composition (Device catalog)

ModelKind

O

Specification (Device catalog)

Specification

O

Number of ports (Device catalog)

NumberOFPort

O

Line speed (Device catalog)

CircuitSpeed

O

User property field 32-1 (Device catalog)

UserPropertyField32_1

O

User property field 32-2 (Device catalog)

UserPropertyField32_2

O

User property field 32-3 (Device catalog)

UserPropertyField32_3

O

User property field 32-4 (Device catalog)

UserPropertyField32_4

O

User property field 32-5 (Device catalog)

UserPropertyField32_5

O

User property field 32-6 (Device catalog)

UserPropertyField32_6

O

User property field 32-7 (Device catalog)

UserPropertyField32_7

O

User property field 32-8 (Device catalog)

UserPropertyField32_8

O

User property field 64-1 (Device catalog)

UserPropertyField64_1

O

User property field 64-2 (Device catalog)

UserPropertyField64_2

O

User property field 64-3 (Device catalog)

UserPropertyField64_3

O

User property field 64-4 (Device catalog)

UserPropertyField64_4

O

User property field 64-5 (Device catalog)

UserPropertyField64_5

O

User property field 64-6 (Device catalog)

UserPropertyField64_6

O

User property field 64-7 (Device catalog)

UserPropertyField64_7

O

User property field 64-8 (Device catalog)

UserPropertyField64_8

O

User property field 128-1 (Device catalog)

UserPropertyField128_1

O

User property field 128-2 (Device catalog)

UserPropertyField128_2

O

User property field 128-3 (Device catalog)

UserPropertyField128_3

O

User property field 128-4 (Device catalog)

UserPropertyField128_4

O

User property field 128-5 (Device catalog)

UserPropertyField128_5

O

User property field 128-6 (Device catalog)

UserPropertyField128_6

O

User property field 128-7 (Device catalog)

UserPropertyField128_7

O

User property field 128-8 (Device catalog)

UserPropertyField128_8

O

User property field 255-1 (Device catalog)

UserPropertyField255_1

O

User property field 255-2 (Device catalog)

UserPropertyField255_2

O

User property field 255-3 (Device catalog)

UserPropertyField255_3

O

User property field 255-4 (Device catalog)

UserPropertyField255_4

O

User property field 255-5 (Device catalog)

UserPropertyField255_5

O

User property field 255-6 (Device catalog)

UserPropertyField255_6

O

User property field 255-7 (Device catalog)

UserPropertyField255_7

O

User property field 255-8 (Device catalog)

UserPropertyField255_8

O

User property area-1 (Device catalog)

UserPropertyArea_1

O

User property area-2 (Device catalog)

UserPropertyArea_2

O

User property area-3 (Device catalog)

UserPropertyArea_3

O

User property area-4 (Device catalog)

UserPropertyArea_4

O

User property code-1 (Device catalog)

UserPropertyCode_1

O

User property code-2 (Device catalog)

UserPropertyCode_2

O

User property code-3 (Device catalog)

UserPropertyCode_3

O

User property code-4 (Device catalog)

UserPropertyCode_4

O

User property code-5 (Device catalog)

UserPropertyCode_5

O

User property code-6 (Device catalog)

UserPropertyCode_6

O

User property code-7 (Device catalog)

UserPropertyCode_7

O

User property code-8 (Device catalog)

UserPropertyCode_8

O

User property code-9 (Device catalog)

UserPropertyCode_9

O

User property code-10 (Device catalog)

UserPropertyCode_10

O

User property code-11 (Device catalog)

UserPropertyCode_11

O

User property code-12 (Device catalog)

UserPropertyCode_12

O

User property date-1 (Device catalog)

UserPropertyDate_1

O

User property date-2 (Device catalog)

UserPropertyDate_2

O

User property date-3 (Device catalog)

UserPropertyDate_3

O

User property date-4 (Device catalog)

UserPropertyDate_4

O

User property date-5 (Device catalog)

UserPropertyDate_5

O

User property date-6 (Device catalog)

UserPropertyDate_6

O

User property unit-1 (Device catalog)

UserPropertyUint_1

O

User property unit-2 (Device catalog)

UserPropertyUint_2

O

User property unit-3 (Device catalog)

UserPropertyUint_3

O

User property unit-4 (Device catalog)

UserPropertyUint_4

O

User property unit-5 (Device catalog)

UserPropertyUint_5

O

User property unit-6 (Device catalog)

UserPropertyUint_6

O

Legend:

M: Mandatory item during new registration

O: Optional item

20.4.15 Items targeted by the Problems asset type

The following table lists the items that are targeted by the Problems asset type.

Table 20‒99: Items targeted by the Problems asset type

CSV file item name

Class

Property

Specification

Maintenance log ID (Maintenance log)

Maintenance

MaintenanceID

O

Managed No. (Maintenance log)

ManagedNo

M

Asset No. (Maintenance log)

AssetNo

O

Status (Maintenance log)

MaintenanceStatus

M

Registration date (Maintenance log)

MaintenanceDate

M

Overview of problem (Maintenance log)

ObstacleContents

M

Completion date (Maintenance log)

CompletingDate

O

Overview of solution (Maintenance log)

MeasureContents

O

Expense (Maintenance log)

Expense

O

Reference materials (URL) (Maintenance log)

ReferenceData

O

Worker (Maintenance log)

Worker

O

Registrar (Maintenance log)

UserName

M

Event-issuing host (Maintenance log)

EventHost

O

Host where problem occurred (Maintenance log)

MaintenanceHost

O

Importance (Maintenance log)

Importance

O

Event serial number (Maintenance log)

EventNo

O

JP1/IM execute host (Maintenance log)

ExecutionHost

O

Notes (Maintenance log)

Note

O

Problem type (Maintenance log)

MaintenanceKind

M

User property field 128-1 (Maintenance log)

UserPropertyField128_1

O

User property field 128-2 (Maintenance log)

UserPropertyField128_2

O

User property field 255-1 (Maintenance log)

UserPropertyField255_1

O

User property field 255-2 (Maintenance log)

UserPropertyField255_2

O

User property area-1 (Maintenance log)

UserPropertyArea_1

O

User property area-2 (Maintenance log)

UserPropertyArea_2

O

User property code-1 (Maintenance log)

UserPropertyCode_1

O

User property code-2 (Maintenance log)

UserPropertyCode_2

O

Legend:

M: Mandatory item during new registration

O: Optional item

20.4.16 Items targeted by the Assigned license information asset type

The following table lists the items that are targeted by the Assigned license information asset type.

Table 20‒100: Items targeted by the Assigned license information asset type

CSV file item name

Class

Property

Specification

Asset No. (Asset information)

AssetInfo

AssetNo

O

Group name (Asset information)

GroupName

M

Asset ID (Hardware information)

HardwareInfo

AssetID

O

Asset ID (Software information)

SoftwareInfo

AssetID

M

User ID (User information)

UserInfo

UserID

O

User name (User information)

UserName

O

Key ID (Software key information)

SoftwareKeyInfo

KeyID

O

Product ID (Software key information)

ProductID

M

License key (Software key information)

LicenseKey

M

Serial No. (Software key information)

SerialNo

M

Legend:

M: Mandatory item during new registration

O: Optional item

20.4.17 Items targeted by the Patches asset type

The following table lists the items that are targeted by the Patches asset type.

Table 20‒101: Items targeted by the Patches asset type

CSV file item name

Class

Property

Specification

Asset ID (Asset information)

AssetInfo

AssetID

O

Asset No. (Asset information)

AssetNo

O

Patch ID (Patch name list)

PatchList

PatchID

O

Patch name (Patch name list)

PatchName

O

Patch version (Patch name list)

PatchVersion

O

Applied status (Patch information)

PatchInfo

InstalledStatus

M

Installed date (Patch information)

InstalledDate

O

ITDM2 management information acquisition control (Patch information)

InfoInd

O

Legend:

M: Mandatory item during new registration

O: Optional item

20.4.18 Items targeted by the Virus definition asset type

The following table lists the items that are targeted by the Virus definition asset type.

Table 20‒102: Items targeted by the Virus definition asset type

CSV file item name

Class

Property

Specification

Asset ID (Asset information)

AssetInfo

AssetID

O

Asset No. (Asset information)

AssetNo

O

Anti-virus product name (Virus definition information)

InstalledVirusDefInfo

VirusDefName

M

Anti-virus product version (Virus definition information)

SoftwareVersion

O

Version of virus detection engine (Virus definition information)

EngineVersion

O

Resident/nonresident (Virus definition information)

ResidentKind

O

Installed date (Virus definition information)

InstalledDate

O

Virus definition version (Virus definition information)

VirusDefVersion

O

ITDM2 management information acquisition control (Virus definition information)

InfoInd

O

Legend:

M: Mandatory item during new registration

O: Optional item

20.4.19 Items targeted by the Related asset information asset type

The following table lists the items that are targeted by the Related asset information asset type.

Table 20‒103: Items targeted by the Related asset information asset type

CSV file item name

Class

Property

Specification

Parent asset ID (Related asset information)

RelationAssetInfo

ParentAssetID

O

Child asset ID (Related asset information)

ChildAssetID

O

Parent asset number (Related asset information)

ParentAssetNo

O

Child asset number (Related asset information)

ChildAssetNo

O

Legend:

O: Optional item

20.4.20 Items targeted by the Division information asset type

The following table lists the items that are targeted by the Division information asset type.

Table 20‒104: Items targeted by the Division information asset type

CSV file item name

Class

Property

Specification

Division ID (Division information)

DivisionInfo

DivisionID

O

Group ID (Division information)

GroupID

E

Group name (Division information)

FullPathName

Division name (Division information)

DivisionName

M

Group ID (Group information)

GroupInfo

GroupID

O

Group name (Group information)

FullPathName

O

Legend:

M: Mandatory item during new registration

E: Either property must be specified during new registration.

O: Optional item

20.4.21 Items targeted by the Assign Divisions asset type

The following table lists the items that are targeted by the Assign Divisions asset type.

Table 20‒105: Items targeted by the Assign Divisions asset type

CSV file item name

Class

Property

Specification

Division ID (Division information)

DivisionInfo

DivisionID

O

Group ID (Division information)

GroupID

E

Group name (Division information)

FullPathName

Division name (Division information)

DivisionName

M

User ID (User information)

UserInfo

UserID

O

User name (User information)

UserName

O

Legend:

M: Mandatory item during new registration

E: Either property must be specified during new registration.

O: Optional item

Appendixes

A. Differences Between the Asset Management Functions in Asset Console and in JP1/IT Desktop Management 2 Windows

The table below summarizes the differences between the asset management functions in Asset Console and in JP1/IT Desktop Management 2 windows.

More detailed information about these functional differences is provided by JP1/IT Desktop Management 2 manuals and JP1/IT Desktop Management 2 - Asset Console manuals.

Table A‒1: Summary of the functional differences in asset management

No.

Function

Summary

AC

ITDM2

Features of AC

1

Device management

Searches a specific organizational group or location, or the entire organization, to count the number of owned devices from a viewpoint of a specific managed item.

This function can be used to change the managed information for multiple devices at the same time or to register the asset management database with device stocktaking results.

Y

Y

The number of owned devices can be checked from the viewpoint of the CPU clock speed or memory size.

Note that Asset Console does not support the following operations:

Launching the Inventory module from the Assets module

Controlling USB devices

Automatically registering IP addresses or MAC addresses in the network control list

2

History management

Manages the change histories of hardware and installed software.

The items to be collected can be selected according to the purpose of management.

Y

Y

Fine-grained settings, such as those related to change history data collection, in a DHCP environment can be specified. For example, if the number of installed hardware devices or software programs has been changed, the change can be reported by email.

3

Contract management

Manages the information about the contracts of devices and software programs.

Y

Y

--

4

Problem management

Manages the problems occurring in the asset management system, and the response statuses for the problems.

Y

N

Information about the JP1 events and SNMP traps managed by JP1/IM can be shared through Asset Console.

5

License management

Manages the software license usage statuses.

This function can be used to check the excess licenses and manage volume licenses.

Y

Y

Volume licenses can be managed.

6

Item management

Manages the application and approval jobs as a workflow by associating asset information.

Y

N

Jobs related to asset management can be managed as a workflow. The application and approval jobs can be performed by using asset information managed by Asset Console.

7

User group management

Limits the area that can be accessed on an organizational level basis.

Y

Y

The access scope from the group that the logged-in user belongs to can be limited.

8

Installation location management

Manages installation locations.

Y

Y

--

9

IP group management

Manages IP addresses based on IP groups, each of which consists of IP addresses in a specific range. This function can be used to manage the usage status of IP addresses by groups created for each department or location with easy-to-understand names.

Y

N

By registering an IP address range for each department or location, the usage and availability of IP addresses can be checked.

10

Device catalog management

Allows users to add or edit the device catalog information that is used when devices are added.

Y

N

By creating a template for devices to be added, the time and effort required to add devices can be reduced.

11

Software name management

Maps installed-software names and software names.

Y

Y

Software names can be automatically registered from the installed-software information. Software names can also be manually registered or imported.

12

Installed software management

Manages the software that is installed.

Y

Y

--

13

Code management

Allows users to edit the managed codes, including their attributes. This function can be used to add or edit search conditions specified with job menus or output results of job menus.

Y

N

Code management allows comparison of values based on the magnitude. This is useful when export data is automatically processed.

For example, the operating statuses can be managed as follows:

101: Running, 201: Failed, 301: Discarded

14

Import

Updates (adds, changes, or deletes) the asset information based on the information provided by a CSV file.

Y

Y

Almost all information managed by Asset Console can be imported, including the hardware asset information, license information, and contract information.

15

Export

Outputs the asset information in the asset management database to a file in CSV format.

Y

Y

Almost all information managed by Asset Console can be exported, including the hardware asset information, license information, and contract information.

16

Role management

Limits the available functions and information according to the user's purpose, by changing the accessible range according to the user role or by adding user roles.

Y

Y

Executable jobs can be limited according to the role assigned to the logged-in user.

17

Customize managed items

Allows users to select the items to be displayed in windows, and to change the names of display items.

Y

Y

The operations explained on the left can be performed for almost all display items.

18

Customize Job Windows

Changes the window components (such as search conditions and editable items) according to the user role.

Y

N

The components of windows can be changed according to the role assigned to the logged-in user.

19

Customize Job Menu

Changes executable jobs according to the user role.

Y

Y

Executable jobs can be limited according to the role assigned to the logged-in user.

20

Create User Report

Allows users to create their own search windows (user reports) for specific purposes if there are no default windows for those purposes.

Y

N

You can create a window that executes a search with any search conditions for classes that are combined under specific conditions and are managed by Asset Console using a database. The search results can also be exported to a CSV file based on the created conditions. This is useful when data is passed to another system.

21

software dictionary linkage

Determines whether the software is free or non-free based on the software information collected from terminals.

N

Y

Asset Console does not support this function.

22

Graphical report creation

Creates graphical reports.

N

Y

Asset Console does not support this function.

23

Viewing status by window operation

Displays the statuses of assets in a window.

N

Y

Asset Console does not support this function.

24

Custom group

Allows an administrator to create any groups according to purposes so that assets can be managed by group.

Y

Y

Asset Console supports only management on a department basis.

Legend:

AC: Asset management using Asset Console

ITDM2: Asset management using JP1/IT Desktop Management 2 windows

Y: The function is supported.

N: The function is not supported.

--: None in particular

B. Organization of Folders

This appendix describes the organization of the folders for Asset Console and the asset management server's virtual directory.

B.1 Folder organization of Asset Console

The following table describes the organization of the folders that are created when Asset Console is installed.

Table B‒1: Organization of the folders for Asset Console

Folder name

Description

Asset-Console-installation-folder (jp1asset)

\aimdb

--

Folder storing the database

\bin

--

Folder storing DLL files

\conf

--

Folder storing linkage setting files

\event

Folder storing event issuance setup files

\imcc

Folder storing event extended definition files

\infoView

Folder storing automatic authentication setting files

\db

--

Folder storing data files, log files, and other files related to the database

\env

--

Folder storing environment settings information

\eur

--

Folder storing form definition files, user definition files, and option description files

\exe

--

Folder storing executable files

\help

--

Folder storing the files constituting operation windows

\log

--

Folder storing log files

\map

--

Folder storing table definition information

\patch

--

Folder storing executable files of patches when Asset Console patches are installed

\plug-in

--

Folder storing plug-ins

\sample

--

Folder storing sample files

\AD

Folder storing the sample script for updating the asset management database based on the user organization information of Active Directory, as well as a document summarizing the sample script explanation and usage

\scriptbatch

--

Folder storing the definition files for executing batch processing on the asset information by tasks

\scriptwork

--

Folder storing temporary files and template files for command execution

\template

--

Folder storing search template files

\work

--

Work folder

Legend:

--: Not applicable

B.2 Folder organization of the asset management server's virtual directory

The table below describes the folder organization of the asset management server after it has been installed.

The default virtual directory for the asset management server is Asset-Console-installation-folder\wwwroot.

Table B‒2: Organization of the folders for the asset management server's virtual directory

Folder name

Description

asset-management-server's-virtual-directory

\bin

Folder storing the executable files of the asset management server

\csv

Asset management server's work folder

\data

Folder storing upload files

\gif

Folder storing image data files

\log

Folder storing log files

\script

Folder storing definition files

\template

Folder storing the template files used for window operation

C. List of Processes

The table below lists the name of each Asset Console process and describes its function. The processes are listed in alphabetical order of the process names. Each process name is followed in parentheses by the number of instances of the process that may execute concurrently, where n indicates a positive integer.

Table C‒1: Name and function of each process

Process name

Function

jamdbsetup.exe(1)

Process for creating a table space to which a meta table information is to be imported (started at setup)

jamdeur.exe(n)

Process used during output of PDF files

jamclasstbl.exe(1)

Process for creating in the database a table area required for the asset management server (started at setup)

jamconvdats.exe(1)

Process used during database conversion

jamexport.exe(n)

Process for the export command

jamimport.exe(n)

Process for the import command

jamscript.exe(n)

Process for manipulating the asset management database, such as search and update operations (also used during task execution and for summing)

jamsetup.exe(n)

Process for setting the environment information needed for operation of the asset management server

jamTakeITDM2Info.exe(1)

Process used for acquiring data from JP1/IT Desktop Management 2 - Manager

jamztrbl.exe(1)

Process used for collecting log information (started by the user to acquire log information in the event of an error)

Note

Because Asset Console runs on Microsoft Internet Information Services, the Microsoft Internet Information Services process inetinfo.exe is resident.

D. System Requirements and Estimates

This appendix describes the memory, disk space, and CPU performance required for the asset management server.

D.1 Memory requirements

The following is the amount of memory required to run the asset management server.

To manage up to 5,000 computers:

Allocate 1.0 gigabyte or more.

To manage from 5,001 to 30,000 computers:

Allocate 8.0 gigabytes or more.

D.2 Disk space requirements

The amount of disk space required to run the asset management system is derived from the total disk space required for the asset management database and for the asset management server.

This appendix provides formulas for estimating the required disk space.

(1) Disk space required for the asset management database

Size of database

= ( (size of information to be used x number of registered items) + (amount of data for license total) + (amount of Item data) + (amount of definition data)) x 1.4 x 1.5

Note

The disk area (containing both management area and operation area) required for database operation is automatically allocated. The size that is automatically allocated depends on the size of the asset management database as shown below.

Table D‒1: Disk area required for asset management database operation

Database size

Management area

Operation area

100 (MB)

+ 637 (MB)

+ 81 (MB)

101 to 500 (MB)

+ 1,757 (MB)

+ 404 (MB)

501 more (MB)

+ 7,147 (MB)

+ 404 (MB)

Size of information to be used

The following table provides guidelines for size of information to be used.

Table D‒2: Size of each information item

Information to be used

Size per item (kilobytes)

Hardware information#1

51.4

Software information#2

28.2

Device catalog

0.5

Maintenance contract information

1.3

Lease contract information

1.3

Rental contract information

1.3

Company catalog

0.9

Software list

0.4

Installed software list

0.4

Patch list

0.2

IP group information

0.8

IP address control information#3

0.3

Location information

1.2

user information

0.8

Group information

1.0

Role information

0.4

Official authority

0.3

Device change log

0.8

Software update log

0.4

Volume contract information

0.8

Maintenance log

2.6

#1

This estimate assumes that the following information is included:

One asset information item (2.7 kilobytes per item)

One hardware information item (1.4 kilobytes per item)

Three network information items (0.6 kilobytes per item)

20 transfer log entries (1.2 kilobytes per item)

60 installed software information items (0.3 kilobytes per item)

10 patch information items (0.1 kilobytes per item)

One virus definition information item (0.5 kilobytes per item)

One ITDM2 management information item (2.0 kilobytes per item)

#2

This estimate assumes that the following information is included:

One asset information item (2.7 kilobytes per item)

One software information item (0.1 kilobytes per item)

50 software key information items (0.5 kilobytes per item)

One license information item (0.4 kilobytes per item)

#3

As many IP address control information items as the total number of IP addresses available within the address range registered for the IP group information are required.

Note

The size of each information item to be used is based on the following conditions:

Data is set only for items (including user properties) that can be set by GUI operations or when ITDM2 management information is imported. The average size of the values to be set is assumed to be 30 bytes. If the data size is less than 30 bytes, the size of the managed area is assumed.

For items that cannot be set by GUI operations or when ITDM2 management information is imported, only the size of the managed area is assumed.

The asset information and maintenance contract information associate one or more device information items.

Amount of data for license total

= (α + β) x number of times licenses totaled (kilobytes)

α = average number of software assets owned by one group x number of groups x 0.5

β = average number of software assets that have been installed on a device x number of devices x 0.5

This formula assumes that one software product requires 0.5 kilobytes of space.

Amount of Item data

= (size of defined Item x number of defined Items registered) + (amount of data required for Item management x number of Items requested)

Size of defined Item: 150.0 kilobytes

Amount of data required for Item management: 4.0 kilobytes

The size of a defined Item shown here is an average over the provided four Item templates. The actual size of a defined Item depends on the numbers of activities and Items that are to be defined.

Amount of definition data

= 30.0 megabytes

The index area requires about 40% of the table size. For details about how to determine the size of the index area, see the DBMS documentation.

To achieve efficient access to the asset management database, a free space of about 50% of the table size is required.

(2) Disk space required for the asset management server

Size required for server

= size of data obtained as search results x average number of searches per login x average number of concurrent logins

Size of data obtained as search results

= (size of information to be used x expected number of hits by search)

For reference values of the size of information to be used, see Table D-2 Size of each information item in D.2(1) Disk space required for the asset management database.

To upload a file as an attached file using a window operation, treat the size of the attached file as part of the disk capacity.

(3) Asset Console installation size

The Asset Console installation size is 180 megabytes.

D.3 CPU performance

The following shows the minimum and recommended CPU performance required to run Asset Console.

Minimum required

1.4-GHz or faster processor

Recommended performance

To manage up to 5,000 computers: 1.5-GHz or faster processor

To manage from 5,001 to 30,001 computers: 3-GHz or faster 4-core processor

E. Section and Key Names for Environment Setup Information

The table below provides the section and key names corresponding to the environment setup information that is specified in the $ENVIRONMENT built-in function (get environment information) in access definition files.

Table E‒1: Section and key names corresponding to the environment setup information

Category

Section name

Environment setting

Key name

Database Information

DATABASE

Login ID

USER

Service name

SERVICE_NAME

Number of concurrent connections

COUNT

Number of connections for search

LONGTIME_COUNT

Case sensitivity in LIKE searches

YES:

Case sensitive

NO:

Case insensitive

SEARCH_CASE_SENSITIVE

Session Information

SERVER

Communication-less monitoring time

SESSTION_TIME

Number of concurrent user logins

COUNT

Basic Information

BASE

Show PDF button

YES:

Show

NO:

Hide

EUR

Time-out time for PDF file creation

EUR_TIMEOUT

Number of result lines to display

REFERENCE_NUM

Show number column

YES:

Show

NO:

Hide

REFERENCE_FIELD

Number of search results displayed on a page

REFERENCE_NUMONPAGE

Trash group ID for deletions

UNDEF_GROUP

Trash location ID for deletions

UNDEF_LOCATION

Threshold for license excess

LICENSE_LIMIT

Automatic login settings

YES:

Show

NO:

Hide

COMPO_AUTOLOGIN

Number of days that cookies are effective

COMPO_EXPIRES

Settings for a group that uses a group-specific IP group

NO:

Do not set

OVERWRITE:

Set

YES:

To only set a group that has not been set

GROUP_AUTO

Settings for a locations that uses a location-specific IP group

NO:

Do not set

OVERWRITE:

Set

YES:

To only set a location that has not been set

LOCATION_AUTO

Acquisition of DHCP address update log

YES:

Acquire

NO:

Do not acquire

DHCP_HISTORY

Sort key for the group-specific tree display

GroupInfo.GroupID:

Group ID

GroupInfo.GroupName:

Local name

GroupInfo.GroupName_EN:

Group name (English)

GroupInfo.FullPathName:

Group name

GroupInfo.UserPropertyField128_1:

User property field 128-1

GroupInfo.UserPropertyField128_2:

User property field 128-2

GroupInfo.UserPropertyField255_1:

User property field 255-1

GroupInfo.UserPropertyField255_2:

User property field 255-2

GROUP_ORDERKEY

Acquisition of contract history

YES:

Acquire

NO:

Do not acquire

CONTRACT_HISTORY

Display substitute items by default

YES:

Show

NO:

Hide

SURROGATE

Create new Item from Item outbox

ENABLE:

Create

DISABLE:

Do not create

INCIDENT_COPY

Status to display in device search windows

USE:

Display only active codes

ALL:

Display all codes

ASSET_STATUS

Device log management

YES:

Manage

NO:

Do not manage

UPDATE_RECORD

Audit log entry output

0:

Do not output audit log entries

1:

Output audit log entries

AUDITLOG_LEVEL

Audit log entry output folder

AUDITLOG_PATH

Mail Notification Information

MAIL

Notification by e-mail

YES:

Notify

NO:

Do not notify

EXPIRATION_NOTICE

Email notification to Item agents

YES:

Email

NO:

Do not email

SURROGATE_MAIL_NOTICE

Address to e-mail

NOTICE_MAILTO

Sender's e-mail address

NOTICE_MAILFROM

Link with Directory Server

BASE

Directory server usage

YES:

Use

CTF:

Use for authentication only

NO:

Do not use

DIRECTORY

LDAP

Encoding

SHIFT-JIS

Shift JIS

UTF-8

UTF-8

CHAR_CODESET

Server name

HOST_NAME

Port number

PORT_NO

Access user

ACCESS_UID

Response monitoring time

TIMELIMIT

User information DN

PEOPLE_DN

User ID attribute name

USER_ATTR

User name attribute name

USER_NAME_ATTR

ITDM2 Linkage

ITDM2

JP1/ITDM2-Manager database login ID

USER

Name of the service connecting to the JP1/ITDM2-Manager database

SERVICE_NAME

Multiplex

MULTIOLICITY

F. Replacing the Asset Management Server and Changing Its Settings

This appendix describes how to replace the asset management server, and how to change its settings. This appendix also describes how to change the database size and rename the host.

Note

Use the following procedure to change the date and time on the asset management server:

Obtain a backup of the database in CSV format.

Execute jamemb_dbstop.bat to stop the database.

Change the date and time.

Re-create the database.

Recover the database from the backup (CSV file).

F.1 Replacing the asset management server

This appendix explains the procedure for replacing the asset management server machine. This procedure can be used also when converting the DBMS during the replacement.

On the machine existing before migration, obtain a backup of the asset management database in CSV format.

For details about how to obtain a backup of the asset management database in CSV format, see 18.1.1 Backing up and restoring the asset management database in CSV format.

Install Asset Console on the conversion-destination machine.

For the procedure for installing Asset Console, see 7.2.2 Installing Asset Console.

In the Server Setup dialog box, set Login ID and Service name in Database Information.

From the Database Manager dialog box, create an asset management database.

For details about how to create an asset management database, see 7.4 Creating an asset management database.

Copy the uploaded files to the conversion-destination machine.

For details about the storage destination of the uploaded files, see 18.1.3(1) Backing up uploaded files.

From the Database Manager dialog box, restore the asset management database.

For details about how to restore the asset management database, see 18.1.1(3) Restoring the asset management database from the Database Manager dialog box.

F.2 Changing the size of a database

You can change the size of a database by re-creating the asset management database as described below. The following procedure applies when the existing data is inherited to the re-created database. If you do not want to inherit the data after the asset management database is re-created, perform only step 2.

Obtain a backup of the asset management database in CSV format.

For details about how to obtain a backup of the asset management database in CSV format, see 18.1.1 Backing up and restoring the asset management database in CSV format.

Create an asset management database.

Specify a desired size and create the asset management database. For details about how to create an asset management database, see 7.4.1 How to create an asset management database.

Restore the asset management database.

Restore the backup file in CSV format that was acquired in step 1. In Backup folder name, specify the path to the backup file. For details about how to restore the asset management database, see 18.1.1(3) Restoring the asset management database from the Database Manager dialog box.

F.3 Renaming the host

This section describes how to rename the host. You can use the same procedure to rename a logical host in a cluster environment.

Note

Before you rename the host, stop all Asset Console services, commands, and tasks on the asset management server in the following order:

World Wide Web Publishing Service or World Wide Web Publishing

Asset Console commands and tasks

When you run Asset Console after having changed the host name, start the services in the reverse order of the order in which they were stopped.

Stop the database.

For details about how to stop the database, see F.4(2) Stopping the database.

Use a text editor to open the pdsys file that is stored in Asset-Console-installation-folder\aimdb\conf.

In the pdsys file, change host-name in pdunit -x host-name -u unt1 -d "Asset-Console-installation-folder\aimdb".

If the above entry is longer than 80 bytes, specify it on multiple lines by adding \ at the end of each line other than the last line so that each line has 80 or fewer bytes. The following shows an example:

pdunit -x host-name -u unt1\
-d "Asset-Console-installation-folder\aimdb"

Use a text editor to open the following files that are stored in Asset-Console-installation-folder\aimdb\conf\emb:

HiRDB.ini

reorganization_al.bat

reorganization_tb.bat

In each file, change host-name in PDHOST=host-name.

Rename the OS host.

Restart the OS.

F.4 Starting and stopping the database

This appendix describes how to start and stop the database. When executing an Asset Console command, you must use the 32-bit command prompt. For the execution procedure, see Appendix G. Notes on Executing Asset Console Commands and Tasks.

(1) Starting the database

You can start the database by executing jamemb_dbstart.bat as a user with administrator permissions.

The function, format, and return values of jamemb_dbstart.bat are explained below.

jamemb_dbstart.bat is stored in the following folder:

Asset-Console-installation-folder\exe

(a) Function

Starts the database.

(b) Format

jamemb_dbstart.bat

(c) Return values

Returns the following return values:

Return value

Description

0

Normal termination

101

Error occurred during processing.

(d) Note on command execution

While the database is being started, executing an import or export command might cause the startup to fail. Wait until the startup is complete, and then execute the import or export command.

(2) Stopping the database

You can stop the database by executing jamemb_dbstop.bat as a user with administrator permissions.

The function, format, and return values of jamemb_dbstop.bat along with notes on command execution, are explained below.

jamemb_dbstop.bat is stored in the following folder:

Asset-Console-installation-folder\exe

(a) Function

Stops the database.

(b) Format

jamemb_dbstop.bat

(c) Return values

Returns the following return values:

Return value

Description

0

Normal termination

101

Error occurred during processing.

(d) Notes on command execution

Before stopping the database, stop Asset Console services, commands, and tasks on the asset management server in the following order:

World Wide Web Publishing Service or World Wide Web Publishing

Asset Console commands and tasks

To run Asset Console after having stopped the database by executing jamemb_dbstop.bat, start the services in the reverse order of the order in which they were stopped.

G. Notes on Executing Asset Console Commands and Tasks

To execute Asset Console commands and tasks in a 64-bit OS, follow the procedure described below.

To execute a batch operation or VBScript

Execute the following command:

%windir%\syswow64\cmd.exe

The 32-bit mode command prompt appears.

At the 32-bit mode command prompt, execute Asset Console's batch operation or VBScript.

To register a task

Register the task in the following format:

%windir%\syswow64\cmd.exe /c "program-to-be-executed"

Specification examples follow:

%windir%\syswow64\cmd.exe /c "cscript.exe "C:\Program Files (x86)\HITACHI\jp1asset\exe\jamSoftwareAddUp.vbs" GENERATION=1"

H. Audit Log Output

Asset Console can record the registration, updating, or deletion of data in or from the management information as database traceability records in the audit log file. Because the audit log file does not have a transaction management mechanism, the contents of the audit log do not match the contents of the database. To record the operations performed on the management information to the fullest extent, an audit log is output immediately before the database is accessed. In this way, both completed operations on the management information and attempted operations can be detected.

Note

The audit log is also output from the Asset Console, JP1 products, and the OS (Windows event log). You can use the audit log for evaluation and audit of the internal control and organization by collecting and managing the audit log for JP1/Audit Management - Manager#. When the OS language of a management server is Japanese or English, the Asset Console can be linked with the JP1/Audit Management - Manager.

#: JP1/Audit Management - Manager is a program that collects and manages the audit log to support evaluation and audit of the internal control of the entire system. Note that the name of version 9 or earlier products is JP1/NETM/Audit - Manager.

The information that is output to Asset Console's audit log is explained below.

H.1 Types of events that are output to the audit log

The table below shows the types of events for which audit log data is output and the triggers for Asset Console to output audit log data. A trigger type is an identifier for classifying the events that are output to the audit log.

Table H‒1: Types of events that are output to the audit log

Event type

Description

Output trigger for Asset Console

ConfigurationAccess

This event indicates updating of configuration information.

Outputs the records of addition, updating, and deletion in the following operations and job categories:

Server Setup

System Management

Group and User

Search Users

Location

IP Group

Software Name

Installed Software

System Management

Role

Customize Managed Items

Customize Job Windows

Customize Job Menu

Authentication

This event indicates that authentication failed or succeeded.

Outputs the records of login to or logout from Asset Console.

ContentAccess

This event indicates that the asset information managed by Asset Console was accessed.

Outputs the records of addition, updating, and deletion in the following job categories:

Device Management

Device Totals

Device List

Unused Device List

New Device

Batch Update

Totals of Stocktaking-Unexecuted Devices

Device Change Log

Software License

Owned License List

Excess License List

Unauthorized Usage List

Unknown Usage List

New Software

Software List

Transfer License

New Volume License

Volume License List

Update History

H.2 Audit log storage format

This appendix explains the format used to store audit log data.

Audit log data is output to ASTAUDIT0n.LOG. When the size of this log file reaches 1 megabyte, 1 is added to the ending number of the file name and audit log data is output to this new file. In other words, when ASTAUDIT01.LOG reaches the specified size and must be switched, log data is written to ASTAUDIT02.LOG. When ASTAUDIT02.LOG reaches the specified size, log data is written to ASTAUDIT03.LOG.

A maximum of nine generations of log files can be used. When ASTAUDIT09.LOG reaches the specified size, ASTAUDIT01.LOG is initialized and log data is written to it. When ASTAUDIT01.LOG reaches the specified size, ASTAUDIT02.LOG is initialized and log data is written to it.

H.3 Audit log output format

This appendix explains the output format and output destination of audit log data, and the items that are output in the auditlog. This appendix also provides an audit log output example.

(1) Audit log data output format

Each audit log entry begins with CALFHM, which indicates the audit log format, followed by an audit log revision number and the applicable output item.

The following figure shows the format of each audit log entry.

Figure H‒1: Audit log data output format

(2) Audit log data output destination

Audit log data is output to the folder that was specified for Audit log entry output folder in the Server Setup dialog box. The default folder is the following:

Asset-Console-installation-folder\auditlog

For details about how to specify the audit log data output destination in the Server Setup dialog box, see the explanation of the audit log entry output folder in 7.3.4 Setting Basic Information.

(3) Items output in the audit log

There are two types of items that are output in the audit log: common output items and fixed output items. Each type is explained below.

Common output items

These are common items that are output for all JP1 products for which audit log data is output.

Fixed output items

These items are output individually for each JP1 product for which audit log data is output.

(a) Common output items

The following table shows the values that are output for the common output items and their description.

Table H‒2: Common output items in the audit log

No.

Output item

Value

Description

Item name

Output attribute name

1

Common specification identifier

--

CALFHM

Identifier that indicates the audit log format

2

Common specification revision number

--

X.X

Revision number for managing the audit log

3

Sequence number

seqnum

Sequence number

Audit log sequence number

4

Message ID

msgid

KDAMxxxx-x

Message ID for each product

5

Date/time

date

YYYY-MM-DDThh:mm:ss.sssTZD#

Audit log acquisition date/time and time zone

6

Generated program name

progid

JP1ITDM2

Name of the program in which the event occurred

7

Generated component name

compid

ac-stu

Server setup component

ac-w3c

Asset Console's job component that is executed on IIS by a browser or other product-related program

Name of the component in which the event occurred

8

Generated process ID

pid

Process ID

ID of the process in which the event occurred

9

Generated location

ocp:host

Host name

Name of the host in which the event occurred

If the host name cannot be acquired, no value is displayed.

10

Event type

ctgry

ConfigurationAccess

Authentication

ContentAccess

Identifiers for classifying the events that are output to the audit log

11

Event result

result

Success

Success

Failure

Failure

Occurrence

Occurrence of an event that does not have success or failure classification

Result of the event that occurred

12

Subject identification information

subj:euid

Windows account

Information about the user who caused the event

subj:uid

Asset Console user ID

Legend:

--: Attribute name is not output.

#

YYYY indicates the year; MM, the month; DD, the day; hh, the hour; mm, the minute; ss, the second; and sss, the millisecond.

T separates the date from the time.

TZD is the time zone identifier. One of the following is output:

+hh:mm: Indicates that the local time is ahead of GMT by hh:mm.

-hh:mm: Indicates that the local time is behind GMT by hh:mm.

Z: Indicates that the local time is the same as GMT.

(b) Fixed output items

The following table shows the values that are output for the fixed output items and their description.

Table H‒3: Fixed output items in the audit log

No.

Output item

Value

Description

Item name

Output attribute name

1

Object information

obj

acJOB

Setup (batch system)

acAuth

Authentication (login)

acClass

Asset Console's job processing

Information about the file or database that caused the event

2

Action information

op#

Login

Login

Logout

Logout

Add

Addition

Update

Update

Delete

Deletion

Information about the user operation that caused the event

3

Table name

obj:table#

Device

Software

Group

User

Location

Software name

License name

Installed software name

Role

Managed item

Customize Job Windows

Customize Job Menu

Managed class name

4

Free description

msg#

Arbitrary message

Message indicating the event contents

#

For details about the messages that are output and the related items that are set in correspondence to these messages, see H.4 Audit log messages and related output items.

(4) Audit log output example

The following example shows the audit log output when a user logs in to Asset Console and executes server setup.

The following operations are executed in this case:

Executing server setup.

Logging in to Asset Console.

Registering device information.

Logging out of Asset Console.

The following figure shows an example of the audit log output.

Figure H‒2: Example of audit log output

H.4 Audit log messages and related output items

The following table shows the messages that are output to the audit log and the related items that are set in correspondence to these messages.

Table H‒4: Audit log messages and related output items

Message

Related output item

Remarks

ctgry

result

op

obj:table

Setup was executed.

ConfigurationAccess

Occurrence

Update

N/A

Setup dialog box

Logged in.

Authentication

Success

Login

N/A

Login

Login failed.

Authentication

Failure

Login

N/A

Login

Logged out.

Authentication

Success

Logout

N/A

Logout

Registration was successful. (AssetInfo.AssetNo)

ContentAccess

Success

Add

Device

New Device

Updating was successful. (AssetInfo.AssetNo)

ContentAccess

Success

Update

Device

Device Details dialog box → Device tab

The network was added. (AssetInfo.AssetNo;NetworkInfo.NetworkID;NetworkInfo.IPAddress;NetworkInfo.NodeName)

ContentAccess

Success

Update

Device

Device Details dialog box → Network tab

The installed software was added. (AssetInfo.AssetNo;InstalledList.InstalledID;InstalledList.InstalledName)

ContentAccess

Success

Update

Device

Device Details dialog box → Software tab

The patch was added. (AssetInfo.AssetNo;PatchInfo.PatchID;PatchList.PatchName;PatchInfo.InstalledStatus)

ContentAccess

Success

Update

Device

Device Details dialog box → Patch tab

The anti-virus software was added. (AssetInfo.AssetNo;InstalledVirusDefInfo.VirusDefName)

ContentAccess

Success

Update

Device

Device Details dialog box → Anti-Virus tab

A related device was added. (AssetInfo.AssetNo)

ContentAccess

Success

Update

Device

Device Details dialog box → Related Devices tab

The subject of a contract was registered. (AssetInfo.AssetNo;Contract.ContractNo)

ContentAccess

Success

Update

Device

Device Details dialog box → Contract tab

The maintenance log was registered. (AssetInfo.AssetNo;Maintenance.ManagedNo)

ContentAccess

Success

Update

Device

Device Details dialog box → Maintenance tab

The network was deleted. (AssetInfo.AssetNo;NetworkInfo.NetworkID;NetworkInfo.IPAddress;NetworkInfo.NodeName)

ContentAccess

Success

Update

Device

Device Details dialog box → Network tab

ContentAccess

Success

Update

Device

Device Details dialog box → Network tab → Network Details dialog box

The network was updated. (AssetInfo.AssetNo;NetworkInfo.NetworkID;NetworkInfo.IPAddress;NetworkInfo.NodeName)

ContentAccess

Success

Update

Device

Device Details dialog box → Network tab → Network Details dialog box

The installed software was deleted. (AssetInfo.AssetNo;InstalledList.InstalledID;InstalledList.InstalledName)

ContentAccess

Success

Update

Device

Device Details dialog box → Software tab

The installed software was updated. (AssetInfo.AssetNo;InstalledList.InstalledID;InstalledList.InstalledName)

ContentAccess

Success

Update

Device

Device Details dialog box → Software tab → Installed Software dialog box

The patch was deleted. (AssetInfo.AssetNo;PatchInfo.PatchID;PatchList.PatchName;PatchInfo.InstalledStatus)

ContentAccess

Success

Update

Device

Device Details dialog box → Patch tab

The anti-virus software was deleted. (AssetInfo.AssetNo;InstalledVirusDefInfo.VirusDefName)

ContentAccess

Success

Update

Device

Device Details dialog box → Anti-Virus tab

The related device was removed. (AssetInfo.AssetNo)

ContentAccess

Success

Update

Device

Device Details dialog box → Related Devices tab

The subject of a contract was removed.(AssetInfo.AssetNo;Contract.ContractNo)

ContentAccess

Success

Update

Device

Device Details dialog box → Contract tab

The maintenance log was updated. (AssetInfo.AssetNo;Maintenance.ManagedNo)

ContentAccess

Success

Update

Device

Device Details dialog box → Maintenance Log Details dialog box → Edit Maintenance Log dialog box

The maintenance log was deleted. (AssetInfo.AssetNo;Maintenance.ManagedNo)

ContentAccess

Success

Update

Device

Device Details dialog box → Maintenance tab

ContentAccess

Success

Update

Device

Device Details dialog box → Maintenance tab → Maintenance Log Details dialog box

Updating via a batch change operation was successful. (AssetInfo.AssetNo)

ContentAccess

Success

Update

Device

Batch Update → Set Changes dialog box

Deletion was successful. (AssetInfo.AssetNo)

ContentAccess

Success

Delete

Device

Device Details dialog box → Device tab

Registration was successful. (AssetInfo.AssetNo;SoftwareList.SoftwareName)

ContentAccess

Success

Add

Software

New Software

The license was assigned. (AssetInfo.AssetNo;SoftwareList.SoftwareName)

ContentAccess

Success

Update

Software

Device Details dialog box → License tab → Assign License dialog box

Updating was successful. (AssetInfo.AssetNo;SoftwareList.SoftwareName)

ContentAccess

Success

Update

Software

Software Details dialog box → Asset tab

Software Details dialog box → Key tab → Add License Key dialog box

Software Details dialog box → Key tab → Key Details dialog box

Software Details dialog box → Key tab

The license was transferred. (AssetInfo.AssetNo;SoftwareList.SoftwareName)

ContentAccess

Success

Update

Software

Transfer License → Set Destination dialog box → Destination Group tab

Transfer License → Set Destination dialog box → Transfer Key tab

The volume contract was registered. (VolumeContract.ContractNo)

ContentAccess

Success

Update

Software

New Volume License

The volume contract was deleted. (VolumeContract.ContractNo)

ContentAccess

Success

Update

Software

Volume License List

Volume License Details dialog box → Contract tab

The volume contract was updated. (VolumeContract.ContractNo)

ContentAccess

Success

Update

Software

Volume License Details dialog box → Contract tab

Volume License Details dialog box → Software tab

The license was removed. (AssetInfo.AssetNo;SoftwareList.SoftwareName)

ContentAccess

Success

Update

Software

Device Details dialog box → License tab

Deletion was successful. (AssetInfo.AssetNo;SoftwareList.SoftwareName)

ContentAccess

Success

Delete

Software

Software List

Registration was successful. (GroupInfo.GroupID;GroupInfo.FullPathName)

ConfigurationAccess

Success

Add

Group

Group and User → Add Group dialog box

Updating was successful. (GroupInfo.GroupID;GroupInfo.FullPathName)

ConfigurationAccess

Success

Update

Group

Group and User → Browse Groups dialog box

Group and User → Group Details dialog box

Group and User → Group Details dialog box → Division tab → Register Division dialog box

Group and User → Group Details dialog box → Division tab → Refresh Division dialog box

Group and User → Group Details dialog box → Division tab

Group and User → Group Details dialog box → Division tab → Assign Division dialog box

Deletion was successful. (GroupInfo.GroupID;GroupInfo.FullPathName)

ConfigurationAccess

Success

Delete

Group

Group and User

Group and User → Group Details dialog box

Registration was successful. (UserInfo.UserID;UserInfo.UserName)

ConfigurationAccess

Success

Add

User

Group and User

Updating was successful. (UserInfo.UserID;UserInfo.UserName)

ConfigurationAccess

Success

Update

User

Group and User → Browse Groups dialog box

Group and User → User Details dialog box

Deletion was successful. (UserInfo.UserID;UserInfo.UserName)

ConfigurationAccess

Success

Delete

User

Group and User

Group and User → User Details dialog box

Registration was successful. (LocationInfo.LocationID;LocationInfo.FullPathName)

ConfigurationAccess

Success

Add

Location

Location → Add Location dialog box

Updating was successful. (LocationInfo.LocationID;LocationInfo.FullPathName)

ConfigurationAccess

Success

Update

Location

Location → Browse Locations dialog box

Location → Location Details dialog box

Deletion was successful. (LocationInfo.LocationID;LocationInfo.FullPathName)

ConfigurationAccess

Success

Delete

Location

Location

Location → Location Details dialog box

Registration was successful. (SoftwareList.SoftwareListID;SoftwareList.SoftwareName)

ConfigurationAccess

Success

Add

Software name

New Software → Browse Software dialog box → Add Software dialog box

Software Name Details → Add Software dialog box

Updating was successful. (SoftwareList.SoftwareListID;SoftwareList.SoftwareName)

ConfigurationAccess

Success

Update

Software name

Software Name Details → Integrate Software dialog box

Software Name → Software Name Details dialog box

Software Name → Software Name Details dialog box → Assign tab → Add Installed Software dialog box

Software Name → Software Name Details dialog box → Assign tab

Software Name → Software Name Details dialog box → License tab → Add License dialog box

Software Name → Software Name Details dialog box → License tab

Software Name → Software Name Details dialog box → Downgrade tab → Browse Software dialog box

Software Name → Software Name Details dialog box → Downgrade tab

New Software → Browse License dialog box → Add License dialog box

License Information Details dialog box

Deletion was successful. (SoftwareList.SoftwareListID;SoftwareList.SoftwareName)

ConfigurationAccess

Success

Delete

Software name

Software Name

Registration was successful. (SoftwareList.SoftwareListID;SoftwareList.SoftwareName;LicenseInfo.LicenseID;LicenseInfo.LicenseName)

ConfigurationAccess

Success

Add

License name

New Software → Browse License dialog box → Add License dialog box

Software Name Details dialog box → License tab → Add License dialog box

Updating was successful. (SoftwareList.SoftwareListID;SoftwareList.SoftwareName;LicenseInfo.LicenseID;LicenseInfo.LicenseName)

ConfigurationAccess

Success

Update

License name

License Information Details dialog box

Deletion was successful. (SoftwareList.SoftwareListID;SoftwareList.SoftwareName;LicenseInfo.LicenseID;LicenseInfo.LicenseName)

ConfigurationAccess

Success

Delete

License name

License Information Details dialog box

Software Name Details dialog box → License tab

Updating was successful. (InstalledList.InstalledID;InstalledList.InstalledName)

ConfigurationAccess

Success

Update

Installed software name

Installed Software → Batch Update dialog box

Installed Software → Installed Software Details dialog box

Deletion was successful. (InstalledList.InstalledID;InstalledList.InstalledName)

ConfigurationAccess

Success

Delete

Installed software name

Installed Software

Registration was successful. (RoleInfo.RoleID;RoleInfo.RoleName)

ConfigurationAccess

Success

Add

Role

Role → Add Role dialog box

Updating was successful. (RoleInfo.RoleID;RoleInfo.RoleName)

ConfigurationAccess

Success

Update

Role

Role → Role Details dialog box

Deletion was successful. (RoleInfo.RoleID;RoleInfo.RoleName)

ConfigurationAccess

Success

Delete

Role

Role → Role Details dialog box

Updating was successful. (Class name)

ConfigurationAccess

Success

Update

Managed item

Customize Managed Items

Initialization was successful.

ConfigurationAccess

Success

Update

Customize Job Windows

Customize Job Windows

Updating was successful. (Window name)

ConfigurationAccess

Success

Update

Customize Job Windows

Customize Job Windows → Edit of Window name dialog box

Updating was successful.

ConfigurationAccess

Success

Update

Customize Job Menu

Customize Job Menu

Legend:

N/A: Not applicable

#

Values are output inside the parentheses.

Note

Even when registration to or updating of the asset management server fails, a Success audit log is output as an event indicating that an operation was performed.

H.5 Settings for outputting audit log data

To specify the settings for outputting audit log data, use the Server Setup dialog box. For details, see Audit log entry output and Audit log entry output folder under 7.3.4 Setting Basic Information.

I. Applying Information Updated in Asset Console to JP1/IT Desktop Management 2 - Manager

I.1 Deleting JP1/IT Desktop Management 2 - Manager device information corresponding to the device information deleted from Asset Console

If you discard managed devices and then delete their device information from Asset Console, you also need to delete the corresponding device information from JP1/IT Desktop Management 2 - Manager. This maintains the integrity of device information between Asset Console and JP1/IT Desktop Management 2 - Manager. To delete device information from JP1/IT Desktop Management 2 - Manager, use the jamDeleteITDM2Info.exe command, which is stored in the following folder:

Asset-Console-installation-folder\exe

Note that an agent must be installed on the asset management server to execute the jamDeleteITDM2Info.exe command.

The following describes the function, format, and return values of the jamDeleteITDM2Info.exe command, and provides notes on command execution.

(1) Function

This command sends a notification to JP1/IT Desktop Management 2 - Manager to delete JP1/IT Desktop Management 2 - Manager's device information corresponding to the device information deleted from Asset Console. Device information on the asset management server will not be deleted.

If a notification to JP1/IT Desktop Management 2 - Manager fails, it is retried according to Settings to perform retries when an error occurs in the agent configuration for the agent installed on the asset management server.

(2) Format

jamDeleteITDM2Info.exe

(3) Return values

This command returns the following values:

Return value

Description

0

Normal termination

31

No agent is installed on the asset management server.

51

The jamDeleteITDM2Info.exe command or jamTakeITDM2Info.exe command is being executed.

52

An attempt to access the asset management database failed.

53

A file I/O error occurred.

101

The command terminated due to an error other than the above.

(4) Notes on command execution

Depending on the network status and whether the JP1/IT Desktop Management 2 - Manager service is running, it might take some time to delete JP1/IT Desktop Management 2 - Manager device information after a command is executed.

After executing the jamDeleteITDM2Info.exe command, wait several hours before executing the jamTakeITDM2Info.exe command.

Even if a device for which the management relay server and Network Monitor are enabled is deleted from Asset Console, JP1/IT Desktop Management 2 - Manager does not delete the device.

I.2 Applying asset information updated in Asset Console to JP1/IT Desktop Management 2 - Manager

If groups of users or device locations are changed for a reason such as reconfiguration, you (the system administrator) must change all information about groups and locations. In this case, you can apply information set in Asset Console to JP1/IT Desktop Management 2 - Manager to match their information.

This subsection describes how to update asset information in Asset Console and then apply the information to JP1/IT Desktop Management 2 - Manager. By importing a CSV file, you can apply the following management items of asset information (necessary for device management in JP1/IT Desktop Management 2 - Manager) updated in Asset Console to JP1/IT Desktop Management 2 - Manager:

Shared management items of asset information and device information

Added management items of hardware information

(1) Procedure for updating asset information in Asset Console and then applying the information to JP1/IT Desktop Management 2 - Manager

Note

In order to prevent unnecessary information from being applied, execute the following tasks in advance:

Acquisition of ITDM2 - Manager management information (Asset Console) task

Data maintenance (Asset Console) task

For details about how to set the tasks, see 7.9 Setting the tasks that are registered in Task Scheduler.

To update asset information in Asset Console and then apply the information to JP1/IT Desktop Management 2 - Manager:

Create a user report containing the asset information you want to update.

The user report created here can be reused for the same subsequent operation.

For details about how to create user reports, see 11.5 Adding windows for routine jobs (Create User Report).

From the window of the user report created in step 1, download the CSV file.

Edit the asset information in the downloaded CSV file.

For details about how to edit and update asset information by using a CSV file, see 16.10 Changing asset information in a batch operation (Import).

Import the edited CSV file to Asset Console.

This completes the update of the asset information in Asset Console. Next, apply the updated asset information to JP1/IT Desktop Management 2 - Manager.

If the definition of asset information is also changed (for example, groups are changed due to reorganization), perform steps 5 and 6. If the definition is not updated, you can skip steps 5 and 6.

Based on the CSV file created in step 3, create an import file (CSV file) containing the definitions of shared management items and added management items.

For details about the import file containing the definitions of shared management items and added management items, see the JP1/IT Desktop Management 2 Administration Guide.

Execute the ioassetsfieldutil import command on the management server to import the file created in step 5 to JP1/IT Desktop Management 2 - Manager.

For details about the ioassetsfieldutil import command, see the JP1/IT Desktop Management 2 Administration Guide.

In the JP1/IT Desktop Management 2 - Manager window, run the Import Assets wizard.

For details about the Import Assets wizard, see the description of how to import hardware information in the JP1/IT Desktop Management 2 Administration Guide.

In the Upload CSV file view, specify CSV File Name and Encoding, and then click the Next button.

In CSV File Name, specify the CSV file edited in step 3. In Encoding, specify the encoding of the CSV file output by Asset Console. The encoding of the CSV file output by Asset Console varies depending on an OS language of the asset management server.

OS language is Japanese: MS932

OS language is English: ASCII

OS language is Chinese: GBK

If the above encoding options do not appear in the Upload CSV file view, change the encoding of the CSV file to an encoding supported in JP1/IT Desktop Management 2 - Manager by using a text editor before importing the CSV file from the operation window of JP1/IT Desktop Management 2 - Manager.

In the Map Fields view, associate the items in the CSV file you edited in step 3 with the asset information items in JP1/IT Desktop Management 2 - Manager. Then, click the Next button.

If you save a template that defines the association of items in the dialog box that appears, you no longer have to associate items from the next time you import a CSV file of the same format.

Follow the instructions given by the wizard to import the CSV file.

This completes the application of the asset information updated in Asset Console to JP1/IT Desktop Management 2 - Manager.

Tip

You can reuse the user report (created in step 1) and the template (created in step 9) for subsequent export and import of CSV files. Use the jamUserReport command of Asset Console to export CSV files, and use the ioutils importasset command of JP1/IT Desktop Management 2 - Manager to import CSV files.

For details about the jamUserReport command, see the example of execution from the command line in 11.5.13 Example of executing a user report. For details about the ioutils importasset command, see the command descriptions in the JP1/IT Desktop Management 2 - Administration Guide.

(2) Example of settings to update Group and Location information, and CSV file output example

The following provides an example of user report settings to update (for reasons of reorganization) Group and Location information in Asset Console and JP1/IT Desktop Management 2 - Manager. A CSV file output example is also provided.

Example of user report settings (step 1)

Search method: Joined class search

Class join method: Specify class

Class name join and Class name join to

Class

Key property

Join type

Class name join

Asset information

Asset ID

INNER

Class name join to

Hardware information

Asset ID

Search conditions

Column

Condition code

Value

Condition

Hardware information.MAC address

!=

--

AND

Asset information.Host ID

!=

--

AND

Legend:

--: Blank

Output items and sort order

Class

Item

How to display properties

Sort order

Asset information

Asset No.

Hide details

1

Status

[Display name]

7

Usage management

[Display name]

6

Group

--

4

Location

--

5

Reg. date

--

8

Hardware information

Host name

--

2

MAC address

--

3

Legend:

--: Nothing is set.

Whether to include duplicated data in search results: Duplicated data is not output.

Output example of a CSV file downloaded from the user report window (step 2)

Example of template settings (that define the association of items) used to import asset information to JP1/IT Desktop Management 2 - Manager (step 9)

Template name: Any name

Header Line: 1

Import Starting Line: 2

Data item allocation

Asset information item name

Header line of the CSV file

--

Asset No.

--

Host name

MAC address#

MAC address

Group

Group

Location

Location

--

Usage management

--

Status

--

Reg. date

Legend:

--: Not applied to JP1/IT Desktop Management 2 - Manager

#: Item specified for Mapping Key

J. Version Changes

J.1 Changes in 12-60

A procedure for auto-assigning a software name with the definition file was added.

J.2 Changes in 12-10

Windows Server 2019 was added as an applicable operating system for the following products:

JP1/IT Desktop Management 2 - Manager

JP1/IT Desktop Management 2 - Agent

JP1/IT Desktop Management 2 - Network Monitor

JP1/IT Desktop Management 2 - Asset Console

JP1/IT Desktop Management 2 - Internet Gateway

Remote Install Manager

J.3 Changes in 12-00

Windows Server 2008 R2 is no longer applicable OSs for the following products:

JP1/IT Desktop Management 2 - Manager

JP1/IT Desktop Management 2 - Network Monitor

JP1/IT Desktop Management 2 - Asset Console

Remote Install Manager

J.4 Changes in 11-50

None.

J.5 Changes in 11-10

Windows Server 2016 was added as an applicable operating system for the following products:

JP1/IT Desktop Management 2 - Manager

JP1/IT Desktop Management 2 - Agent

JP1/IT Desktop Management 2 - Network Monitor

JP1/IT Desktop Management 2 - Asset Console

Remote Install Manager

J.6 Changes in 11-01

Windows 10 was added as an applicable operating system for JP1/IT Desktop Management 2 - Network Monitor.

The procedure for uninstalling Asset Console in a cluster system was added.

J.7 Changes in 11-00

A description for when JP1/IT Desktop Management 2 - Manager is in a multi-server configuration was added.

Windows 10 was added as an applicable OS for the following products:

JP1/IT Desktop Management 2 - Agent

JP1/IT Desktop Management 2 - RC Manager

Remote Install Manager

Windows Server 2003 and Windows Server 2008 (except Windows Server 2008 R2) are no longer applicable OSs for the following products:

JP1/IT Desktop Management 2 - Manager

JP1/IT Desktop Management 2 - Agent

JP1/IT Desktop Management 2 - Network Monitor

JP1/IT Desktop Management 2 - RC Manager

Microsoft Internet Information Services 6.0 and Microsoft Internet Information Services 7.0 are no longer supported. Additionally, the descriptions of Dr. Watson and Userdmp were deleted.

K. Reference Material for This Manual

K.1 Related publications

This manual is part of a related set of manuals. The manuals in the set are listed below (with the manual numbers):

Note that, in this manual, the titles of the below manuals are indicated with the abbreviated form, in which JP1 Version 12 or JP1 Version 11 is omitted. When you encounter abbreviated manual titles, replace them with the complete titles, adding the omitted part.

JP1 Version 12 Asset and Distribution Management: Getting Started (3021-3-E11(E))

JP1 Version 12 JP1/IT Desktop Management 2 Overview and System Design Guide (3021-3-E12(E))

JP1 Version 12 JP1/IT Desktop Management 2 Configuration Guide (3021-3-E13(E))

JP1 Version 12 JP1/IT Desktop Management 2 Administration Guide (3021-3-E14(E))

JP1 Version 12 JP1/IT Desktop Management 2 Distribution Function Administration Guide (3021-3-E15(E))

JP1 Version 12 JP1/IT Desktop Management 2 - Asset Console Creating an Access Definition File Guide (3021-3-E17(E))

JP1 Version 12 JP1/IT Desktop Management 2 Messages (3021-3-E18(E))

JP1 Version 12 JP1/Base User's Guide (3021-3-D65(E))

JP1 Version 12 JP1/Integrated Management 2 - Manager Overview and System Design Guide (3021-3-D51(E))

JP1 Version 12 JP1/Integrated Management 2 - Manager GUI Reference (3021-3-D54(E))

JP1 Version 12 JP1/Service Support Configuration and Administration Guide (3021-3-D71(E))

JP1 Version 11 JP1/Integrated Management - Manager Overview and System Design Guide (3021-3-A07(E))

JP1 Version 11 JP1/Integrated Management - Manager GUI Reference (3021-3-A10(E))

HiRDB Version 8 Messages (3020-6-358(E))

K.2 Conventions: Abbreviations for product names

This manual uses the following abbreviations for product names:

Abbreviation

Full name or meaning

ActiveX

ActiveX(R)

Asset Console or AC

JP1/IT Desktop Management 2 - Asset Console

EUR

uCosminexus EUR Server Enterprise 09-00 or later

JP1/Base

JP1/Base 10-00 or later

JP1/IM

JP1/Integrated Management - Manager

JP1/Integrated Management 2 - Manager

JP1/Integrated Management - Rule Operation

JP1/Integrated Management - View

JP1/Integrated Management 2 - View

JP1/Integrated Manager - Central Console

JP1/Integrated Manager - Central Scope

JP1/Integrated Manager - View

JP1/IM - Manager

JP1/Integrated Management - Manager

JP1/Integrated Management 2 - Manager

JP1/Integrated Manager - Central Console

JP1/ITDM2 - Manager

JP1/IT Desktop Management 2 - Manager

JP1/Service Support

JP1/Integrated Management - Service Support 10-10 or later

JP1/Service Support

Linux

Linux(R)

Pentium

Pentium(R)

This manual uses the following abbreviations for Microsoft product names:

Abbreviation

Full name or meaning

MBSA

Microsoft(R) Baseline Security Analyzer

Microsoft Internet Information Services or IIS

Microsoft(R) Internet Information Services 7.5

Microsoft(R) Internet Information Services 8.0

Microsoft(R) Internet Information Services 8.5

Microsoft Windows Script Host

Microsoft(R) Windows(R) Script Host

Windows 7#1

Windows 7 Enterprise

Microsoft(R) Windows(R) 7 Enterprise

Windows 7 Home Basic

Microsoft(R) Windows(R) 7 Home Basic

Windows 7 Home Premium

Microsoft(R) Windows(R) 7 Home Premium

Windows 7 Professional

Microsoft(R) Windows(R) 7 Professional

Windows 7 Starter

Microsoft(R) Windows(R) 7 Starter

Windows 7 Ultimate

Microsoft(R) Windows(R) 7 Ultimate

Windows 8#1

Windows 8

Windows(R) 8

Windows 8 Enterprise

Windows(R) 8 Enterprise

Windows 8 Pro

Windows(R) 8 Pro

Windows 8.1#1

Windows 8.1

Windows(R) 8.1

Windows 8.1 Enterprise

Windows(R) 8.1 Enterprise

Windows 8.1 Pro

Windows(R) 8.1 Pro

Windows 10#1

Windows 10 Enterprise

Windows(R) 10 Enterprise

Windows 10 Pro

Windows(R) 10 Pro

Windows Internet Explorer or IE

Windows(R) Internet Explorer(R) 9

Windows(R) Internet Explorer(R) 10

Windows(R) Internet Explorer(R) 11

Windows Server 2003#1

Windows Server 2003 (x86)

Microsoft(R) Windows Server(R) 2003 R2, Enterprise Edition

Microsoft(R) Windows Server(R) 2003, Enterprise Edition

Microsoft(R) Windows Server(R) 2003 R2, Standard Edition

Microsoft(R) Windows Server(R) 2003, Standard Edition

Windows Server 2003 (x64)

Microsoft(R) Windows Server(R) 2003 R2, Enterprise x64 Edition

Microsoft(R) Windows Server(R) 2003 R2, Standard x64 Edition

Microsoft(R) Windows Server(R) 2003, Enterprise x64 Edition

Microsoft(R) Windows Server(R) 2003, Standard x64 Edition

Windows Server 2008#1, #2

Windows Server 2008#3

Windows Server 2008 Enterprise

Microsoft(R) Windows Server(R) 2008 Enterprise

Microsoft(R) Windows Server(R) 2008 Enterprise without Hyper-V(R)

Windows Server 2008 Standard

Microsoft(R) Windows Server(R) 2008 Standard

Microsoft(R) Windows Server(R) 2008 Standard without Hyper-V(R)

Windows Server 2008 R2

Windows Server 2008 R2 Datacenter

Microsoft(R) Windows Server(R) 2008 R2 Datacenter

Windows Server 2008 R2 Enterprise

Microsoft(R) Windows Server(R) 2008 R2 Enterprise

Windows Server 2008 R2 Standard

Microsoft(R) Windows Server(R) 2008 R2 Standard

Windows Server 2012#1, #5

Windows Server 2012#4

Windows Server 2012 Datacenter

Microsoft(R) Windows Server(R) 2012 Datacenter

Windows Server 2012 Standard

Microsoft(R) Windows Server(R) 2012 Standard

Windows Server 2012 R2

Microsoft(R) Windows Server(R) 2012 R2 Datacenter

Microsoft(R) Windows Server(R) 2012 R2 Standard

Windows Server 2016#1, #5

Windows Server 2016 Datacenter

Microsoft(R) Windows Server(R) 2016 Datacenter

Windows Server 2016 Standard

Microsoft(R) Windows Server(R) 2016 Standard

Windows Server 2019#1, #5

Windows Server 2019 Datacenter

Microsoft(R) Windows Server(R) 2019 Datacenter

Windows Server 2019 Standard

Microsoft(R) Windows Server(R) 2019 Standard

Windows Vista#1

Microsoft(R) Windows Vista(R) Business

Microsoft(R) Windows Vista(R) Enterprise

Microsoft(R) Windows Vista(R) Home Basic

Microsoft(R) Windows Vista(R) Home Premium

Microsoft(R) Windows Vista(R) Ultimate

Windows XP#1

Microsoft(R) Windows(R) XP Home Edition Operating System

Microsoft(R) Windows(R) XP Professional Operating System

#1

If there are no functional differences between OSs, Windows is used generically when referring to Windows 7, Windows 8, Windows 8.1, Windows 10, Windows Server 2003, Windows Server 2008, Windows Server 2012, Windows Server 2016, Windows Server 2019, Windows Vista, or Windows XP.

#2

Does not include Server Core installation.

#3

If Windows Server 2008 R2 is noted alongside Windows Server 2008, the description for Windows Server 2008 does not apply to Windows Server 2008 R2.

#4

If Windows Server 2012 R2 is noted alongside Windows Server 2012, the description for Windows Server 2012 does not apply to Windows Server 2012 R2.

#5

If there are no functional differences between OSs, Windows Server is used generically when referring to Windows Server 2012, Windows Server 2016, or Windows Server 2019.

K.3 Conventions: Acronyms

This manual also uses the following acronyms:

Acronym

Full name or meaning

AMD

Advanced Micro Devices

API

Application Programming Interface

ASP

Active Server Pages

BIOS

Basic Input/Output System

CD

Compact Disc

CD-R

Compact Disc Recordable

CD-R/W

Compact Disc Read/Write

CN

Common Name

CPU

Central Processing Unit

CSV

Comma Separated Value

DAT

Digital Audio Tape

DBMS

Data Base Management System

DC

Domain Component

DHCP

Dynamic Host Configuration Protocol

DLL

Dynamic Linking Library

DN

Distinguished Name

DVD

Digital Versatile Disk

FAQ

Frequently Asked Question

FD

Floppy Disk

GUI

Graphical User Interface

HD

Hard Disk

HTML

Hyper Text Markup Language

HTTP

Hyper Text Transfer Protocol

ID

IDentification

IP

Internet Protocol

ISAPI

Internet Server Application Programming Interface

IT

Information Technology

ITIL

IT Infrastructure Library

ITU

International Telecommunication Union

JIS

Japanese Industrial Standards

LDAP

Lightweight Directory Access Protocol

MAC

Media Access Control

MIB

Management Information Base

MIME

Multipurpose Internet Mail Extensions

MO

Magneto-Optical disk

ODBC

Open Data Base Connectivity

OS

Operating System

OU

Organization Unit

PC

Personal Computer

PDF

Portable Document Format

RDB

Relational Database

SMTP

Simple Mail Transfer Protocol

SNMP

Simple Network Management Protocol

SSL

Secure Socket Layer

URL

Uniform Resource Locator

USB

Universal Serial Bus

UTF

UCS Transformation Format

WS

Work Station

K.4 Conventions: Fonts and symbols

The following table explains the text formatting conventions used in this manual:

Text formatting

Convention

Bold

Bold characters indicate text in a window, other than the window title. Such text includes menus, menu options, buttons, radio box options, or explanatory labels. For example:

From the File menu, choose Open.

Click the Cancel button.

In the Enter name entry box, type your name.

Italic

Italic characters indicate a placeholder for some actual text to be provided by the user or system. For example:

Write the command as follows:

copy source-file target-file

The following message appears:

A file was not found. (file = file-name)

Italic characters are also used for emphasis. For example:

Do not delete the configuration file.

Monospace

Monospace characters indicate text that the user enters without change, or text (such as messages) output by the system. For example:

At the prompt, enter dir.

Use the send command to send mail.

The following message is displayed:

The password is incorrect.

The following table explains the symbols used in this manual:

Symbol

Convention

|

In syntax explanations, a vertical bar separates multiple items, and has the meaning of OR. For example:

A|B|C means A, or B, or C.

{ }

In syntax explanations, curly brackets indicate that only one of the enclosed items is to be selected. For example:

{A|B|C} means only one of A, or B, or C.

[ ]

In syntax explanations, square brackets indicate that the enclosed item or items are optional. For example:

[A] means that you can specify A or nothing.

[B|C] means that you can specify B, or C, or nothing.

...

In coding, an ellipsis (...) indicates that one or more lines of coding have been omitted.

In syntax explanations, an ellipsis indicates that the immediately preceding item can be repeated as many times as necessary. For example:

A, B, B, ... means that, after you specify A, B, you can specify B as many times as necessary.

K.5 Conventions: Version numbers

The version numbers of Hitachi program products are usually written as two sets of two digits each, separated by a hyphen. For example:

Version 1.00 (or 1.0) is written as 01-00.

Version 2.05 is written as 02-05.

Version 2.50 (or 2.5) is written as 02-50.

Version 12.25 is written as 12-25.

The version number might be shown on the spine of a manual as Ver. 2.00, but the same version number would be written in the program as 02-00.

K.6 About online help

JP1/IT Desktop Management 2 provides online help in relation to the following subjects:

Window descriptions

This help describes how to use the screen that is currently displayed. You can view these help topics by clicking the Help button in the user interface.

K.7 Conventions: KB, MB, GB, and TB

This manual uses the following conventions:

1 KB (kilobyte) is 1,024 bytes.

1 MB (megabyte) is 1,024² bytes.

1 GB (gigabyte) is 1,024³ bytes.

1 TB (terabyte) is 1,024⁴ bytes.

L. Glossary

A

access permission

Restrictions set for some of the asset information managed in an asset management system so that the users who can access the information are limited. Examples of such information are information about tax returns or maintenance contract fees.

Access permissions that can be set in an asset management system include restrictions on the following:

User authentication based on user ID and password

Availability of the system by user role

Role-based limitations on the functionality that can be executed from windows

Role-based limitations on the menus

accessory (device type)

A type of hardware asset, including Monitor, Hard disk, CD-R, CD-R/W, DVD, DAT, MO, Printer, Peripheral Device, USB Device, and Storage. In the asset management system, hardware is classified into three device types: computing, accessories, and networking.

Active Directory services

Windows main component that manages information on objects comprising a Windows network environment and the relationships between these objects. The following generic names also exist:

Active Directory Rights Management Service (AD RMS)

Active Directory Domain Service (AD DS)

Active Directory Lightweight Directory Service (AD LDS)

Active Directory Certificate Service (AD CS)

Active Directory Federation Service (AD FS)

activity

Processing that is a component of an Item definition and which is executed when the Item is sent to the next worker. Examples of such processing are Apply and Approve.

Flow Designer is used to define activities, and Activity Designer is used to set activity details.

administrator

A network manager or device administrator in the group that handles company IT asset management tasks (an information systems management department). The administrator can handle all asset information.

asset

A unit of managing assets by user.

Assets include device-related, software-related, and user-specific assets. The device-related assets consist of one or more devices, and software-related assets consist of one or more software items. User-specific assets consist of user-specific information.

Asset Console

A product that can reduce management costs and can streamline IT asset management jobs required for tasks such as installing assets, managing software licenses, and performing device maintenance. The product helps achieve these goals by using a database to implement integrated management of asset information such as hardware information (including network devices), software information, and contract information. Additionally, integrated management of IT assets can be achieved by linking Asset Console to JP1 products such as JP1/IM.

asset information

Information used to manage the hardware and software assets in a company. The asset information is represented by data such as Asset No., Group name, User name, Location name, and is not the hardware or software asset itself.

Asset No. is used to identify each asset and can be assigned by the user. In an asset management system, Asset No. is the most basic unit of asset management.

asset management database

A database that stores asset information.

asset management server

A server that manages asset information and provides services related to asset information.

asset management system

A system that manages asset information. An asset management system consists of the following programs:

Asset management server

Web browser

association class

A class defining the relationship between object classes.

An association represents a relationship between multiple classes. Specifically, an association defines a multiplex level between two classes and how the two classes are processed when data is added or deleted.

audit log

Log data that is output as a trace record of internal control. Audit log contains information about who executed what, when, and where.

C

class

A set of management information classified by asset information category. An asset management system handles object classes and association classes.

CN (Common Name)

Entry name attribute in Active Directory. For example, the name of a person (user) is a CN.

code ID

A unique ID assigned to an item managed by code in the asset management database. When codes are edited, codes are added or deleted based on this code ID.

computing (device type)

A type of hardware asset, including PC, PC server, UNIX, UNIX server, Smart Device, and Other system device. In the asset management system, hardware is classified into three device types: computing, accessories, and networking.

contract information

Information used to manage device and software assets under maintenance, lease, or rental contracts.

By grouping multiple devices and software assets with the same contract and then assigning a contract number to the group, the user can manage the devices and software assets by contract.

Customize Job Windows

A function for limiting the operations available from windows by user role.

This functionality allows the components of each window (such as buttons, search conditions, and editable items) to be changed according to the user role.

D

data file

A CSV file required for importing or exporting data. A data file consists of item title lines and data lines.

For an import operation, asset information (asset data) is specified for each association class.

For an export operation, the output destination of asset information is specified for each association class.

data files definition file

A text file that is needed in order to import or export multiple data files in a batch operation.

A data files definition file defines the names of all data files to be imported or exported, and defines the display names of the association classes that correspond to the data files.

DC (Domain Component)

The element that constitutes a domain name in Active Directory.

device catalog

Registration information that is predetermined for a product, such as CPU and memory size.

When registering a new device, the user can select a product from the device catalog and thereby save the time needed to enter the items predetermined for the product.

device change log

Information used to manage changes to devices, such as memory size and disk space. This information can be used to check for any illegitimate physical changes to a CPU, memory, or disk.

The device change log data is organized into fields such as Update date, Hard disk sizes, Memory, and Processor.

division

Information for managing other groups as group jobs. Multiple divisions can be set up for each group. Assigning a division to a user allows that user to manage the information about the group (division group) that is set up as a division group for the division.

division group

Information about the group that is set to a division.

DN (Distinguished Name)

Identifier for uniquely identifying each entry in the Active Directory's directory tree. A distinguished name consists of a character string made up by linking entry attributes using commas (,).

E

EUR

A program that inputs table data and print forms. EUR provides the functionality that allows the user to design various forms without the need for complicated programming, and without having to know the format of the data source.

event manager

A user assigned to check Asset Console asset information from JP1/IM. If a password is set up for this user in advance, the user can automatically be logged into Asset Console when the user checks asset information from the Event Console window.

export

Output of information from the asset management database to a CSV file, in a batch operation.

There are three export methods:

Export by using the Export job menu

The user creates export conditions for selecting the asset information to be output and, in a batch operation, outputs the information to a CSV file. This method can be used at any location where the user can log in to Asset Console.

Export by using jamCsvExport.bat

By executing this from the command line on the asset management server, the user can perform the same export processing as can be performed from the Export window.

Export by using the jamexport command

This method outputs data, in a batch operation, from the asset management database to CSV files as is. A CSV file is output for each class. This export function is implemented by a command provided by Asset Console.

F

form

Settings of each window customized by the Customize Job Windows function. For example, the settings can specify whether to show or hide buttons and search conditions.

A form is set for each window, and multiple forms can be set for the same window.

G

group

A unit for handling user information. If user information is handled according to the groups to which users belong, access to the information can be controlled for each group.

group information

Information required for managing groups, such as the departments using the asset management system. Group information is represented by fields such as Local name, Group code, and Cost group code.

H

hardware information

Information used to manage hardware assets. Hardware information includes information about all hardware assets handled in an asset management system that uses Asset Console. Hardware information is about the devices themselves, and includes fields such as Device type and Device name.

I

import

The loading of information, in a batch operation, from a CSV file into the asset management database.

There are three import methods:

Import by using the Import job menu

The user creates import conditions and updates asset information in the CSV file in a batch operation.

This method can be used at any location where the user can log in to Asset Console. The user can update asset management database information without having to know the CSV file format, classes, or the relationships between classes.

Import by using jamCsvImport.bat

By executing this from the command line at the asset management server, the user can perform the same import processing as can be performed from the Import job menu. This method is useful for automating operations because the user can update asset management database information without having to know the CSV file format, classes, or the relationships between classes. Compared to the jamimport command, however, the processing takes more time.

Import by using the jamimport command

This method loads, in a batch operation, all data from a CSV file into the asset management database as is. The CSV file contains information about data in the asset management database that is to be added, changed, or deleted. This import function is implemented by a command provided by Asset Console.

incident

A unit of error events that degrade IT service quality or prevent normal system operation.

installed software information

Information used to manage the software assets installed on each device.

Installed software information is used by importing information from a program such as JP1/IT Desktop Management 2 - Manager into an asset management database.

Therefore, the names and versions of software assets depend on the source system (such as JP1/IT Desktop Management 2 - Manager) from which the information is imported.

installed software list

Information used to manage the names of software assets installed on each device. It is also used to manage various settings for installed software assets.

IP group information

Information used to manage IP addresses in groups. IP addresses can be managed under easy-to-understand names assigned to the groups.

IT assets

IT devices, such as PCs and printers, existing in a company, software assets, and the network environment for using them.

IT service

A service that satisfies the needs of customers by using an IT system to support implementation of businesses and services.

Item

Work with a defined route, such as Equipment Deployment Request Form or Error Report Form.

Item auditor

The official authority for auditing execution Items.

A user who has this official authority can view the latest Item statuses and attached files in the Execution Item Management window.

Item category

A category of Items classified by the nature of the work.

In the New Item window used to select a new Item, each Item category is displayed on a separate tab.

ITIL

A framework that systematizes IT system setup and operations. Setting up an IT system based on this framework is expected to enable the user to optimize IT services and continually improve day-to-day processes.

J

JP1 event

JP1-specific management information generated for detecting and reporting events (such as job execution results and service errors) that occur in a system managed by JP1.

Asset Console can acquire these JP1 events via JP1/IM.

JP1/Base

The product that provides the basic functionality of JP1/IM. This product includes functionality for sending and receiving JP1 events, managing users, and controlling startup. The product also functions as an agent of a JP1/IM system.

JP1/Base is a prerequisite for JP1/IM.

JP1/IM

A product that achieves integrated management of an entire corporate information system. By collaborating with JP1-series products that manage system operations in various ways, JP1/IM uses JP1 events to implement integrated management of the events that occur in the system. If an error occurs, JP1/IM promptly notifies the administrator and provides the infrastructure for operations needed to identify the location of the error and investigate its cause.

JP1/IT Desktop Management 2 - Manager management information

Information that includes the status of hardware utilization and the types of software assets installed on a managed device. This management information is acquired from JP1/IT Desktop Management 2 - Manager.

In an asset management system, the management information acquired from JP1/IT Desktop Management 2 - Manager can be registered as asset information.

JP1/IT Desktop Management 2 window

A window used for JP1/IT Desktop Management 2 - Manager operations. This term is used in contrast to Asset Console windows, which are simply called windows.

JP1/Service Support

A product that provides the functionality for quickly investigating the cause (and taking action for) an Item that requires a solution (due to, for example, an inquiry or a system error).

L

LDAP (Lightweight Directory Access Protocol)

A subset of the Directory Access Protocol used for accessing directories that support the ITU-recommended X.500 model. Active Directory is compatible with LDAP.

license category

The license categories for a purchased license are Install license and User license. Licenses are totaled for each license category.

license information

Information used to manage the details of software licenses.

License information includes fields such as License name, Upgrade assurance, Downgrade, License type, Licensing method, and License category.

license type

The type of a purchased license. The license types are listed below:

Install license

User license

Server license

Client access license

Managed node license

CPU license

Second license

Concurrent execution license

License type is used to manage the details of licenses and has no effect on the results of license totaling.

location information

Information used to manage asset locations. The location information includes fields such as Local name, Address, Area size, and Attribute.

M

maintenance log

Information used to manage details about device errors and remedial actions. If JP1/IM is linked, JP1 events can be acquired as maintenance log information.

The maintenance log data is organized into fields such as Reg. date, Overview of problem, Importance, Host where problem occurred, Completion date, Overview of solution, Expense, and Reference materials (URL).

managed item

An individual piece of information managed by Asset Console. It corresponds to a class property managed in the asset management database.

managed label

A label set to limit accesses by group. If the same managed label (any character string) is set for both a group and a user role, the users with the corresponding role can handle only the information belonging to the group and subgroups for which that managed label is set.

managed level

A level for managing licenses. A managed level is set for installed software assets. The managed level is set in the Installed Software window, or in the settings for assigning information acquired from JP1/IT Desktop Management 2 - Manager.

There are three managed levels:

Managed object

Includes software assets in the number of used licenses.

Managed object not in license count

Does not include software assets in the number of used licenses. Information is registered as installed software assets.

Unmanaged object

Does not manage licenses nor register information as installed software assets.

management name

A name used to identify the value for a text field, text area, or drop-down list defined by Form Designer when an Item is defined. The user can specify any character string without having to know the class properties.

This name is used with Activity Designer to specify how to update the asset management database.

management relay server

A management server that is located under the primary management server in a multi-server configuration. A management relay server can also be located under a management relay server.

management server

A computer where JP1/IT Desktop Management 2 - Manager is installed. The term management server collectively refers to management servers with a single-server configuration, primary management servers with a multi-server configuration, and site management servers with a multi-server configuration.

meta table

A table required to establish correspondence between class and table in the asset management database. When Asset Console is set up, importing the meta table to the asset management database defines the data structure of the database.

N

network information

Information used to manage the location of each device in the network. Network information includes fields such as IP address, MAC address, Node name, and Computer name.

networking (device type)

A type of hardware asset, including HUB, Router, Network printer, and Networking. In an asset management system, hardware is classified into three device types: computing, accessories, and networking.

node

A component of an Item definition that represents a worker (or group) on the route of the Item. For example, an Applicant or Approval user is a node.

Flow Designer is used to define the nodes.

O

object

A collective name for components placed on the Item window, such as text fields and buttons. Form Designer is used to set objects.

object class

A class is a unit for managing asset information. An object class is the information representing each item managed by the asset management system. The information is represented by tables that correspond to classes and properties, or represented in the format used to input date to or output data from the asset management database.

official authority

Authority to limit the workers that can execute processing, such as to approve an Item.

To execute work for which an official authority is defined, the user must have that official authority separately from the permissions needed to log in to Asset Console.

OU (Organization Unit)

The name attribute of organization entries in Active Directory. An organization unit corresponds to a group name.

P

patch information

Information used to manage each device's patch application status, such as Installation date and Applied status.

patch name list

Information, such as Patch name and Patch version, used to manage patch names.

property

An attribute of a class.

R

role information

Information used to manage the user roles in the asset management system. Administrator and User are set as the default user roles.

route

The order of workers that handle an Item.

An Item is processed sequentially along the defined route. Flow Designer is used to define an Item's route.

S

shared management item

Information that can be optionally set by the user, such as user name and asset number. Shared management item information is acquired from JP1/IT Desktop Management 2 - Manager.

In an asset management system, shared management item information acquired by JP1/IT Desktop Management 2 - Manager can be registered as asset information.

SNMP trap

Asset Console can acquire SNMP traps from JP1/IM as JP1 events.

software information

Information about the software assets registered in an asset management system, such as commercial software, shareware, and freeware. Software information includes fields such as Asset ID, Software name, and Number of licenses.

software key information

Key information used to assign licenses to target devices and users. Software key information includes fields such as Product ID, License key, and Serial No.

T

task

The processing contents that are combined when defining an activity, which is the processing executed when an Item is sent to the next worker.

For example, an activity for registering information about a newly installed device is defined by combining the Add new device and Add network information tasks.

Activity Designer is used to set the tasks for each activity.

U

user information

Information used to manage the users of the asset management system. User information includes fields such as User name, Phone, E-mail, and Official title.

user library

A library for sharing images among Items by uploading the images to the asset management server. Images must be added to the user library before they can be inserted in an Item window by Form Designer.

user report

Work (job) added by the user, and the window used to execute that work. Asset Console not only provides predefined job menus, but also enables the user to add user-specific jobs (user reports).

V

virtual directory

Asset Console must set a virtual directory to make Web contents accessible on IIS.

virus definition information

Information about the anti-virus software product installed on a device and about the virus definition files. The information includes fields such as Anti-virus product name, Anti-virus product version, and Virus definition version.

volume contract information

Information used to manage details about software volume licenses.

The volume license information includes fields such as Software assets, Number of Target points, Contract date, Contract start date, Contract end date, Contracted company, Overview of contract, and Status.

W

window

A window used for Asset Console operations. This term is used in contrast to JP1/IT Desktop Management 2 - Manager windows.

worker

A user who executes an Item. An Item is sent to individual workers according to a defined route.

Index

A

abbreviations for products[1]

ACCESS_UID[1]

access definition file[1]

access permissions[1]

assigning, according to organizational hierarchy[1]

by group level[1]

access permissions for users

types[1]

Access user[1]

acquiring

error information[1]

user organization information[1]

Acquisition of contract history[1]

Acquisition of DHCP address update log[1]

acronyms[1]

Active Directory

importing information into asset management database[1]

linking[1]

login authentication via linkage with[1]

Active Directory linkage

system configuration[1]

active-standby configuration[1]

activity[1]

Activity Designer[1], [2]

name of component and how to use[1]

task[1]

actual stocktaking data, registering[1]

adding

anti-virus software[1]

code[1]

contract[1]

division[1]

downgrade software asset[1]

group[1]

IP address[1]

IP group[1]

items to be acquired from ITDM2 management information[1]

job category[1]

license[1]

location[1]

patch information[1]

remote domain[1]

site[1]

type or status[1]

user[1]

user role[1]

adding asset information statuses, managed items, and windows[1]

adding windows for

routine job[1]

AddressGroup

managing IP address group[1]

Address to e-mail[1]

administrator[1]

property description[1], [2]

after update

property description[1]

anti-virus product name

property description[1]

anti-virus product version

property description[1]

anti-virus software

browsing and adding[1]

application pools

creating[1]

applications

setting[1]

applied status

property description[1]

area size

property description[1]

ASSET_STATUS[1]

Asset Console[1]

asset management database[1]

basic knowledge needed to use[1]

basic operating procedure[1]

features[1]

folder organization[1]

logging in[1]

logging in and out[1]

logging out[1]

managing asset status[1]

names of window components of[1]

notes on executing commands and tasks[1]

purpose[1]

uninstalling [1]

Asset Console login

availability[1]

Asset Console operation

error[1]

AssetInfo

managing asset information[1]

asset information[1]

applying to JP1/IT Desktop Management 2 - Manager (after update in Asset Console)[1]

changing in batch operation[1]

collecting[1]

displaying from JP1/IM[1]

displaying from JP1/Service Support[1]

exporting in CSV format[1]

hints on searching[1]

managing[1]

asset information and related asset information

associating[1]

asset information status, adding[1]

asset location

how to specify[1]

asset management

achieving by linking to other products[1]

differences between asset management functions in Asset Console and in JP1/IT Desktop Management 2 windows[1]

asset management database[1]

association class[1]

association class concept[1]

backing up and restoring[1]

backing up and restoring in CSV format[1]

characters supported[1]

classes managed by[1]

creating[1]

how to create[1]

importing Active Directory information[1]

importing data from another system[1]

maintaining[1]

master-slave relationship[1]

notes on handling[1]

object class[1]

object class concept[1]

property managed by[1]

types of associations[1]

weak association[1]

asset management jobs

executing[1]

asset management server

changing settings[1]

folder organization of virtual directory[1]

identifying error[1]

recovering from errors[1]

replacing[1], [2]

setting up[1]

asset management server setup

error[1]

asset management system[1]

jobs to be executed[1]

linked to other program products[1]

transactions[1]

asset manager

email notification[1]

asset No.

property description[1], [2], [3]

asset type

property description[1]

selecting[1]

asset type codes[1]

AssetUpdateRecord

managing history information[1]

assigned item

setting[1], [2]

setting assigned item for asset number[1]

setting for device type[1]

setting for group and location[1]

setting for user name[1]

assigned license information

browsing and changing[1]

assigning

access permissions according to organizational hierarchy[1]

division to user[1]

installed software name[1]

IP address to device[1]

license to device[1]

software name[1]

assignment-exclusion MAC list

defining[1]

association class

details[1]

list of properties[1]

ASTTRBL.BAT[1]

attached file

how to specify[1]

attribute

changing[1]

filter start event[1]

property description[1]

audit log

messages and related output items[1]

settings for outputting data[1]

storage format[1]

types of events that are output to[1]

audit log

output format[1]

AUDITLOG_LEVEL[1]

AUDITLOG_PATH[1]

Audit log entry output[1]

Audit log entry output folder[1]

AuthorityLink

associating user and group[1]

automatic action

setting by JP1/IM - Manager[1]

Automatic login settings[1]

automatic registration

problems[1]

availability

Asset Console login[1]

available menus

limiting[1]

B

backing up[1]

asset management database[1]

registry[1]

uploaded files[1]

backing up in CSV format

asset management database[1]

BASE[1], [2]

BaseCCN

property description[1]

Basic Information[1]

setting[1]

basic system configuration[1]

Batch Update window[1]

before update

property description[1]

Branch number

property description[1]

browsing

anti-virus software[1]

assigned license information[1]

patch information[1]

update history[1]

button

changing name for[1]

changing view/hide setting for[1]

hidden by default, displaying[1]

setting[1]

C

Case sensitivity in LIKE searches[1]

catalog ID

property description[1]

category

property description[1], [2], [3]

changing

asset information in batch operation[1]

asset management server settings[1]

assigned license information[1]

attribute[1]

code's display value[1]

contract information[1], [2]

database size[1]

default value when ITDM2 management information is registered[1]

device details[1]

device information[1]

device status[1]

division information[1]

executable job[1], [2]

group information[1]

host name[1]

individual information[1]

information about asset locations[1]

information about installed software[1]

installed software assets[1]

installed software information[1]

IP group information[1]

issued JP1 events[1]

Item definition[1]

license information[1]

maintenance log[1]

managed item[1], [2]

managerial group of license[1]

multiple installed software information items in batch operation[1]

network information[1]

related asset information[1]

software name[1]

status[1]

task schedule[1]

type[1]

user and group information[1]

user information[1]

user role[1]

volume contract information[1]

window for user role[1]

window operation[1]

CHAR_CODESET[1]

characters supported

asset management database[1]

checking

acquisition of management information[1]

details of import result[1]

for exceeded licenses[1]

for expired licenses[1]

for unauthorized software installations[1]

import result[1]

license usage status[1]

messages[1]

number of devices that require stocktaking[1]

progress of Items[1]

status of sent Item[1]

usage status of unregistered software[1]

class

INNER[1]

inner join[1]

join type[1]

organization[1]

OUTER[1]

outer join[1]

relationship[1]

classes with ID

importing[1]

class for link

property description[1]

class join method

specifying[1]

class to be searched

specifying[1]

cluster software's cluster administrator

group resource creation[1]

cluster system

installation[1]

notes[1]

system configuration[1]

cluster system configurations

examples[1]

cluster system environment

procedure for creating[1]

code

adding[1]

meaning depending on specification range[1]

code's display value

changing[1]

code IDs shared among multiple classes[1]

code IDs whose range of codes that can be added is limited[1]

code information

deleting[1]

code information that cannot be added or deleted[1]

Code set[1]

collecting

asset information[1]

from CSV files[1]

collecting from JP1/IT Desktop Management 2 - Manager[1]

communication-less monitoring time[1]

company catalog

managing[1]

completion date

property description[1]

COMPO_AUTOLOGIN[1]

COMPO_EXPIRES[1]

composition

property description[1], [2]

computer ID

property description[1]

computer name

property description[1]

concurrent execution license

example of managing[1]

managing[1]

consolidating

software names[1]

contact person

property description[1], [2], [3], [4]

contact person 2

property description[1], [2], [3]

contact person 3

property description[1], [2], [3]

contact phone/e-mail

property description[1], [2], [3]

contact phone/e-mail 2

property description[1], [2]

contact phone/e-mail 3

property description[1], [2]

contact phone and e-mail

property description[1]

contact phone and e-mail 2

property description[1]

contact phone and e-mail 3

property description[1]

contents

property description[1], [2], [3]

contract

adding[1]

Contract

managing contract information[1]

CONTRACT_HISTORY[1]

ContractAssetHistory

managing contract asset history[1]

contract asset history

importing[1]

managing[1]

ContractCatalog

managing contracted company information[1]

contract date

property description[1], [2], [3]

contracted company

property description[1], [2], [3], [4]

contract end date

property description[1], [2], [3]

ContractHistory

managing contract history[1]

contract history

importing[1]

managing[1]

contract ID

property description[1], [2], [3], [4]

contract information

changing[1]

importing[1]

managing[1]

registering[1]

viewing and changing[1]

ContractLeaseLink

associating device and lease contract information[1]

ContractMaintenanceLink

associating device and maintenance contract[1]

Contract Management[1]

contract number

property description[1], [2], [3]

ContractRentalLink

associating device and rental contract[1]

contract start date

property description[1], [2], [3]

conventions

abbreviations for products[1]

acronyms[1]

fonts and symbols[1]

KB, MB, GB, and TB[1]

version numbers[1]

copying

form[1]

correspondence

between information to be imported using jamimport command and classes[1]

cost group code

property description[1]

COUNT[1], [2]

CPU

property description[1]

CPU performance[1]

Create new Item from Item outbox[1]

Create User Report

window[1]

creating

application pools[1]

asset management database[1]

cluster system environment[1]

CSV file to be imported[1]

data files[1]

data files definition file[1], [2]

data source[1], [2]

export condition[1]

import condition[1]

Items[1]

new Item by copying[1]

new Items[1]

Problem Report Form, example[1]

user report[1]

CreationClassName

specification[1]

creation of asset management database

errors[1]

CSV data

output[1]

outputting[1]

registering[1]

registration[1]

CSV file

format of, stocktaking data file[1]

CSV file format[1]

CSV files

editing[1]

CSV file to be imported

creating[1]

Customize Job Menu

window[1]

Customize Job Windows[1]

setting form[1]

Customize Job Windows window

form[1]

D

database

changing size[1]

starting[1]

starting and stopping[1]

stopping[1]

DATABASE[1]

database capacity

estimating[1]

database information

setting[1]

Database Information[1]

database maintenance

notes[1]

data files[1]

creating[1]

output format[1]

data files definition file[1]

creating[1], [2]

data source

creating[1], [2]

DBMS errors

recovering[1]

default gateway

property description[1]

default value

changing when ITDM2 management information is registered[1]

defining

assignment-exclusion MAC list[1]

Item[1]

Item window[1]

search condition[1]

window[1]

Definition of Official Authority dialog box

canceling official authority setting[1]

Item is to be returned for completion to user who submitted it[1]

deleting

code information[1]

device catalog[1]

device information corresponding to device information deleted from Asset Console, from JP1/IT Desktop Management 2 - Manager[1]

division[1]

export condition[1]

form[1]

group information[1]

group or user[1]

import condition[1]

import execution results[1]

installed software name[1]

IP group[1]

Items[1]

location[1]

software name[1]

task[1]

user information[1]

user report[1]

user role[1]

design

flow[1]

overview[1]

designing

job[1]

developer

property description[1], [2], [3]

device

assigning license to[1]

types[1]

device and key link

associating[1]

device catalog[1]

deleting[1]

managing hardware information[1]

registering[1]

device catalog information

managing[1]

device change log

managing[1], [2]

selecting item to be acquired[1]

device details

changing[1]

managing[1]

viewing and changing[1]

device information

changing[1]

registering[1]

device information, importing and exporting [1]

device information change

notification[1]

device information corresponding to device information deleted from Asset Console

deleting from JP1/IT Desktop Management 2 - Manager[1]

Device log management[1]

Device Management[1]

device name

property description[1], [2]

devices

managing[1]

owned, checking number of[1]

searching for[1]

that require stocktaking, checking number of[1]

devices and information about devices

importing[1]

device status

changing[1]

device type

property description[1], [2]

DHCP_HISTORY[1]

DHCP server name

property description[1], [2]

DIRECTORY[1]

directory browse settings

specifying[1]

Directory server usage[1]

disk space requirements[1]

displaying

asset information from JP1/IM[1]

asset information from JP1/Service Support[1]

button, hidden by default[1]

PDF files[1]

property[1]

Display substitute items by default[1]

division

adding[1]

assigning to user[1]

deleting[1]

editing[1]

job menus specifying, as search conditions and values to be registered[1]

viewing[1]

Division ID

property description[1]

DivisionInfo

managing division information[1]

division information

changing[1]

exporting to CSV file[1]

importing[1]

managing[1]

division information and group information

associating[1]

division information and user information

associating[1]

DivisionLink

associating division and group[1]

division name

property description[1]

DivisionUserLink

associating division and user[1]

downgrade

property description[1]

downgrade software asset

adding[1]

downgrade software name 01

property description[1]

downloading

IP address usage[1]

during linkage to JP1/IT Desktop Management 2 - Manager

handling[1]

E

editable item

setting, to read-only[1]

setting display order of[1]

view/hide settings[1]

Edit Code dialog box

Code[1]

editing

CSV files[1]

division[1]

group[1]

network information[1]

user information[1]

email

property description[1]

email notification

to asset manager[1]

Email notification to Item agents[1]

enabling

task[1]

end date of use

property description[1]

end IP address

property description[1]

environment setup information

key names corresponding to[1]

section names corresponding to[1]

error cause

identifying[1], [2]

error information

acquiring[1]

error information acquisition[1]

errors

during Asset Console operation[1]

during asset management server setup[1]

during creation of asset management database[1]

during linkage to JP1/IT[1]

during linkage to JP1/Service Support[1]

during login to Asset Console[1]

recovery[1]

errors during command execution

recovering[1]

errors during linkage to JP1/IT Desktop Management 2 - Manager

principal causes[1]

errors during linkage to JP1/IT products

handling[1]

principal causes[1]

errors in DBMS

handling[1]

principal causes[1]

errors in Web browser

handling[1]

principal causes[1]

errors in Web server

handling[1]

principal causes[1]

establishing correspondence

between software names[1]

estimating

database capacity[1]

EUR[1]

EUR_TIMEOUT[1]

EUR linkage

system configuration[1]

evaluating

managed target[1]

operation methods[1]

system configuration[1], [2]

event attribute composition file

eventmap.ini[1]

managed item set in use extension area[1]

event-issuing host

property description[1]

event serial number

property description[1]

examples

cluster system configurations[1]

system configuration[1]

exceeded licenses

checking for[1]

executable job

changing[1], [2]

executer

property description[1]

executing

asset management jobs[1]

export operation[1]

import[1]

jamCsvExport.bat[1]

jamCsvImport.bat[1]

jamexport (export) command[1]

jamimport (import) command[1]

SMTP virtual server[1]

user report[1]

execution results

task[1]

expense

property description[1]

EXPIRATION_NOTICE[1]

expired licenses

checking for[1]

export

format of output CSV file[1]

procedure[1]

export condition

creating[1]

deleting[1]

exporting[1]

asset information in CSV format[1]

division information to CSV file[1]

exporting device information[1]

export operation

executing[1]

extensions of files to be uploaded

registering[1]

F

FAQ

creating and processing Items[1]

file date

property description[1], [2]

file format

for importing with jamimport command[1]

file name

property description[1], [2]

files

created in log folder[1]

file size

property description[1], [2]

filtering condition

setting[1]

filter start error event (abnormal termination)

attribute[1]

filter termination event

attribute[1]

flow

design[1]

Flow Designer

Add Activity[1]

Add Completion Activity[1]

Add Node button[1]

Add Notification Email[1]

defining route[1]

Item category[1]

placing worker and processing[1]

setting official authority for node[1]

using[1]

window[1]

flow of import

using jamimport command[1]

folder organization[1]

asset management server's virtual directory[1]

font conventions[1]

form

adding[1]

copying[1]

deleting[1]

renaming[1]

setting, for breakdown window displayed from summation result[1]

setting, for registration or edit window[1]

setting, for search or summation window[1]

format

CSV stocktaking data file[1]

Form Designer

defining worker's window[1]

Editing area[1]

inserting object[1]

names of components and how to use them[1]

object[1]

Object attributes[1]

Style attributes[1]

window[1]

Window menu (Background color)[1]

Window menu (Image)[1]

Window menu (size)[1]

forward settings

JP1 events[1]

frequency

property description[1], [2], [3]

from CSV files

collecting [1]

function restrictions after error[1]

G

gateway address

property description[1]

GB meaning[1]

global IP address

property description[1]

glossary[1]

accessory (device type)[1]

access permission[1]

Active Directory services[1]

activity[1]

administrator[1]

asset[1]

Asset Console[1]

asset information[1]

asset management database[1]

asset management server[1]

asset management system[1]

association class[1]

audit log[1]

class[1]

CN (Common Name)[1]

code ID[1]

computing (device type)[1]

contract information[1]

Customize Job Windows[1]

data file[1]

data files definition file[1]

DC (Domain Component)[1]

device catalog[1]

device change log[1]

division[1]

division group[1]

DN (Distinguished Name)[1]

EUR[1]

event manager[1]

export[1]

form[1]

group[1]

group information[1]

hardware information[1]

import[1]

incident[1]

installed software information[1]

installed software list[1]

IP group information[1]

IT assets[1]

Item[1]

Item auditor[1]

Item category[1]

ITIL[1]

IT service[1]

JP1/Base[1]

JP1/IM[1]

JP1/IT Desktop Management 2 - Manager management information[1]

JP1/IT Desktop Management 2 window[1]

JP1/Service Support[1]

JP1 event[1]

LDAP (Lightweight Directory Access Protocol)[1]

license category[1]

license information[1]

license type[1]

location information[1]

maintenance log[1]

managed item[1]

managed label[1]

managed level[1]

management name[1]

meta table[1]

network information[1]

networking (device type)[1]

node[1]

object[1]

object class[1]

official authority[1]

OU (Organization Unit)[1]

patch information[1]

patch name list[1]

property[1]

role information[1]

route[1]

shared management item[1]

SNMP trap[1]

software information[1]

software key information[1]

task[1]

user information[1]

user library[1]

user report[1]

virtual directory[1]

virus definition information[1]

volume contract information[1]

window[1]

worker[1]

group

adding[1]

deleting[1]

editing[1]

how to specify[1]

moving[1]

viewing[1]

GROUP_AUTO[1]

GROUP_ORDERKEY[1]

group code

property description[1]

group ID

property description[1]

GroupInfo

managing group information[1]

group information

changing[1]

deleting[1]

importing[1]

managing[1]

group name

property description[1], [2], [3], [4], [5], [6]

group name (English)

property description[1]

group resource creation

cluster software's cluster administrator[1]

H

handler mappings

setting[1]

handling completion event

attribute[1]

hard disk free space

property description[1]

hard disk size

property description[1], [2]

hardware change

notification[1]

HardwareInfo

managing hardware information[1]

hardware information

managing[1]

HOST_NAME[1]

host identifier

property description[1]

host name

property description[1]

host name, changing[1]

host where problem occurred

property description[1]

HTML file name for link

property description[1]

I

identifying

error cause[1], [2]

identifying error

at asset management server[1]

in Web browser[1]

import

deleting execution results[1]

executing[1]

interrupting[1]

importance

property description[1]

import condition

creating[1]

deleting[1]

import flow[1]

importing[1]

classes with ID[1]

contract asset history[1]

contract history[1]

contract information[1]

devices[1]

division information[1]

group information[1]

information about devices[1]

IP group information[1]

maintenance log[1]

official authority information[1]

patch information[1]

related asset information[1]

role information[1]

transfer log[1]

user information[1]

virus definition information[1]

importing data from another system into asset management database[1]

importing device information[1]

importing information regarding devices managed by another system[1]

import operation

notes[1]

import result

checking[1]

checking details[1]

INCIDENT_COPY[1]

individual information

viewing and changing[1]

information

acquired as asset information[1]

acquired as group information[1]

acquired as hardware information[1]

acquired as installed software information[1]

acquired as installed software list[1]

acquired as IP address management information[1]

acquired as network information[1]

acquired as patch information[1]

acquired as patch list[1]

acquired as virus definition information[1]

registered as location information[1]

information about asset locations

changing[1]

information about installed software

changing[1]

information associated with devices[1]

information that can be acquired from linked product

details[1]

information to be managed[1]

information updated in Asset Console

applying to JP1/IT Desktop Management 2 - Manager[1]

installation

in cluster system[1]

setup[1]

installation procedure[1]

installed date

property description[1], [2], [3]

InstalledInfo

managing software asset[1]

InstalledList

managing installed software list[1]

installed software assets

viewing and changing[1]

installed software ID

property description[1], [2], [3]

installed software information

changing[1]

changing multiple installed software information items in batch operation[1]

managing[1]

installed software list

managing[1]

installed software name[1]

assigning[1]

defined[1]

deleting[1]

property description[1], [2]

registering[1]

releasing assignment[1]

installed software version

property description[1], [2]

InstalledUpdateRecord

managing software update log[1]

InstalledVirusDefInfo

managing virus definition information[1]

installing

Asset Console[1], [2]

prerequisite programs[1]

role services[1]

Install license

example of managing[1]

interpreting

message log file[1]

messages[1]

standard output message log entry[1]

interrupting

import processing[1]

invalid contract information

notification[1]

IPAddress

managing IP address[1]

IP address

adding[1]

assigning to device[1]

property description[1], [2], [3]

releasing[1]

IP address assigned to device

releasing[1]

IP address control information

property description[1]

IP addresses

managing usage statuses[1]

IP addresses, associating group with[1]

IPAddressLink

associating network information and IP address[1]

IP address link

associating with network information[1]

IP address type

property description[1]

IP address usage

downloading[1]

viewing[1]

IP group

adding[1]

deleting[1]

IP group ID

property description[1]

IP group information

changing[1]

importing[1]

managing[1]

IP group name

property description[1]

IP groups, managing[1]

ISAPI filters

setting[1]

ISAPI restrictions

setting[1]

ITDM2[1]

ITDM2 Agent installed status

property description[1]

ITDM2 Linkage[1]

ITDM2 management information

adding items to be acquired from[1]

ITDM2 management information acquisition control

property description[1], [2], [3], [4]

item

defining authority for processing[1]

how to define[1]

official authority[1], [2]

setting, to be displayed as editable item[1]

setting, to be displayed as search condition[1]

Item

defining[1]

Items

checking progress of[1]

rejecting[1]

Item arrival

notification[1]

Item category[1]

Item definition

Activity Designer[1]

adjusting object's style and position[1]

changing[1]

changing registered Item[1]

copying style attribute[1]

cross-reference of data types and object types[1]

defining each node's task[1]

defining table (Table Designer)[1]

deleting Items[1]

displaying read-only object (Read-only)[1]

Execution item[1]

FAQ[1]

Flow Designer[1]

hiding items (Non-display)[1]

inserting button[1]

inserting drop-down list[1]

inserting image[1]

inserting input field[1]

inserting object defined for another node[1]

overview[1]

renaming Item[1]

selecting email transmission[1]

selecting task to be executed[1]

setting deadline[1]

setting details of loop processing[1]

setting display order[1]

setting hyperlink[1]

setting hyperlink target (URL)[1]

setting information to be assigned to managed item[1]

setting Item option[1]

setting Item to Exhibit or Not exhibit[1]

setting management name[1]

setting mandatory item (Required)[1]

setting object attribute[1]

setting object style[1]

setting order of tasks to be executed[1]

specifying data type[1]

Subject[1]

text area[1]

Textbox[1]

text field[1]

types of objects that can be inserted[1]

Item definition elements[1]

Item deletion event

attribute[1]

Item icon

exceeding processing time limit[1]

normal processing[1]

rejection[1]

within processing time limit[1]

Item option[1]

Items[1]

approving[1]

creating[1]

creating new[1]

creating new Item by copying[1]

deleting[1]

executing asset management jobs that use[1]

FAQ on creating and processing Items[1]

managing[1]

processing received[1]

rejected, resending[1]

saved, sending[1]

sent, checking and pulling back[1]

sent, checking status of[1]

sent, pulling back[1]

Item status change event

attribute[1]

items to be imported or exported

from job menu[1]

items to consider

list of[1]

Item transition event

attribute[1]

Item window[1]

defining[1]

definition example[1]

J

jamCsvExport.bat

executing[1]

jamCsvImport.bat

executing[1]

jamdbexport.bat[1]

jamemb_backup.bat[1]

jamemb_dbstart.bat[1]

jamemb_dbstop.bat[1]

jamemb_reorganization.bat[1]

jamemb_workcomp.exe[1]

jamexport (export) command

executing[1]

jamimport (import) command

executing[1]

jamimport command

file format for importing with[1]

flow of import[1]

job

designing[1]

menu[1]

job category

adding[1]

job menu

renaming[1]

job menus

differences by user role[1]

that can be used to specify divisions as search conditions and values to be registered[1]

usage[1]

JobRoleInfo

managing official authority[1]

JobRoleLink

associating user and official authority[1]

jobs to be executed

in asset management system[1]

selecting[1]

JP1/Base[1]

JP1/IM

displaying asset information[1]

JP1/IM execute host

property description[1]

JP1/IM - Manager[1]

setting automatic action[1]

JP1/IM - Manager linkage

system configuration[1]

JP1/IT Desktop Management 2[1]

JP1/IT Desktop Management 2 - Manager management information

workflow necessary for acquisition[1]

JP1/IT Desktop Management 2 - Manager management information acquisition

setting[1]

JP1/ITDM2-Manager database login ID[1]

JP1/Service Support[1]

displaying asset information[1]

JP1/Service Support linkage

system configuration[1]

JP1 event[1]

attribute[1]

issued from Asset Console[1]

settings to forward[1]

JP1 event issued

changing[1]

details[1]

JP1 event issued from Asset Console

details[1]

K

KB meaning[1]

key ID

property description[1]

L

Last updated date of ITDM2

property description[1]

LDAP[1]

lease contract link

associating with device[1]

license

adding[1]

assigning to device[1]

changing managerial group of[1]

determining whether licenses are handled legally[1]

LICENSE_LIMIT[1]

license category

property description[1]

license excess

notice[1]

license ID

property description[1], [2]

LicenseInfo

managing license information[1]

license information

changing[1]

property description[1]

registering[1]

license key

property description[1]

license management

by assigning licenses to devices[1]

by assigning licenses to users[1]

concurrent execution license[1]

second license[1]

license management examples[1]

concurrent execution license[1]

Install license[1]

pre-installed license[1]

second license[1]

server license[1]

User license[1]

license management via Asset Console[1]

license name

property description[1]

licenses

totaling[1]

license type

property description[1]

license usage status

checking[1]

licensing method

property description[1]

limiting

available menus[1]

limiting items to be exported for regular backups[1]

line speed

property description[1], [2]

linkage to JP1/IT

errors[1]

linkage to JP1/Service Support

errors[1]

linking

to Active Directory[1]

linking to EUR

outputting search results in pdf format[1]

settings[1]

linking to JP1/IM

managing problems[1]

linking to JP1/Service Support

settings[1]

linking to other products

achieving asset management[1]

link key

property description[1], [2]

link to JP1/IM

settings[1]

Link with Directory Server[1]

setting[1]

list

of items to consider[1]

local name

property description[1], [2]

location

adding[1]

deleting[1]

moving[1]

property description[1], [2], [3], [4], [5], [6], [7]

LOCATION_AUTO[1]

location ID

property description[1], [2], [3]

LocationInfo

managing location information[1]

location information

managing[1]

LocationName_EN[1]

location name (English)

property description[1]

log folder

files created[1]

logging in to

Asset Console[1]

logging out of

Asset Console[1]

login authentication[1]

login authentication via linkage with Active Directory[1]

log information

viewing[1]

Login ID[1]

login to Asset Console

error[1]

LONGTIME_COUNT[1]

M

MAC address

property description[1], [2]

MachineCatalog

managing hardware information[1]

MachinePermitLink

associating license and device[1]

MAIL[1]

Mail Notification Information[1]

setting[1]

maintaining

asset management database[1]

Maintenance

managing maintenance log[1]

maintenance contract link

associating with device[1]

maintenance log

importing[1]

managing[1]

viewing and changing[1]

maintenance log ID

property description[1]

maintenance log information

registering[1]

managed by asset management database

property[1]

managed group

property description[1], [2]

managed group ID

property description[1]

managed item

adding[1]

changing[1], [2]

Customize Managed Items window[1]

renaming[1]

ScreenItemList.pdf[1]

managed item, adding[1]

Managed label[1]

managed level

property description[1]

Managed level[1]

managed number

property description[1]

managed target

evaluating[1]

management information[1]

acquired from JP1/IT Desktop Management 2 - Manager[1]

checking acquisition of[1]

details[1]

management information assignment method

setting[1]

management relay server[1]

management server[1]

management targets[1]

managing

device catalog information[1]

device change log[1]

device details[1]

devices[1]

installed software update history[1]

Items[1]

shared information[1]

software[1]

system problems[1]

managing licenses

by assigning licenses to users[1]

examples of[1]

managing licenses by assigning to devices[1]

managing patch information

managing[1]

managing problems

linking to JP1/IM[1]

managing volume license points[1]

MB meaning[1]

MBSA version

property description[1]

MemberLink

associating user and group[1]

memory

property description[1], [2]

memory requirements[1]

message log file

interpreting[1]

messages

audit log[1]

checking[1]

interpreting[1]

method for outputting CSV data

selecting[1]

model

property description[1], [2]

monitor resolution

property description[1], [2]

monitor size

property description[1], [2]

monitor type

property description[1], [2]

monthly

property description[1]

monthly contract amount

property description[1]

moving

group or user[1]

location[1]

MULTIOLICITY[1]

Multiplex[1]

multi-server configuration[1]

N

Name of the service connecting to the JP1/ITDM2-Manager database[1]

NetworkInfo

managing device location in network[1]

network info ID

property description[1]

network information

editing[1]

managing[1]

viewing and changing[1]

node[1]

node name (host name)

property description[1]

non-editable

property[1]

note

property description[1], [2]

notes

database maintenance[1]

executing Asset Console commands and tasks[1]

handling asset management database[1]

import operation[1]

property description[1], [2]

using a cluster system[1]

notice

license excess[1]

NOTICE_MAILFROM[1]

NOTICE_MAILTO[1]

notification

device information change[1]

hardware change[1]

invalid contract information[1]

Item arrival[1]

unauthorized install[1]

Notification by e-mail[1]

Number of concurrent connections[1]

number of concurrent user logins[1]

Number of connections for search[1]

Number of days that cookies are effective[1]

number of licenses

property description[1]

number of ports

property description[1], [2]

number of processors

property description[1], [2]

Number of result lines to display[1]

Number of search results displayed on a page[1]

O

object class

details[1]

property list[1]

object role

setting[1]

official authority[1], [2]

adding new[1]

changing detail[1]

deleting[1]

managing[1]

official authority ID

property description[1]

official authority information

importing[1]

official authority name

property description[1], [2]

official title

property description[1]

online help[1]

operating method[1]

operation code[1]

operation management, enabling[1]

operation methods

evaluating[1]

operations on asset information

suppressing[1]

organization

programs[1]

OS

property description[1]

OS version

property description[1]

Outbox window[1]

output

CSV data[1]

output format

data files[1]

output item

setting[1]

setting sort order and display width[1]

outputting

CSV data[1]

outputting search results in pdf format

linking to EUR[1]

overview[1]

design[1]

overview of Asset Console[1]

overview of problem

property description[1]

overview of solution

property description[1]

P

password

property description[1]

patch ID

property description[1], [2]

PatchInfo

managing patch information[1]

patch information

browsing and adding[1]

importing[1]

PatchList

managing patch name list[1]

patch name

property description[1]

patch name list

managing[1]

patch version

property description[1]

PDF files

displaying and printing[1]

PEOPLE_DN[1]

per-license management[1]

permission

property description[1]

phone

property decryption[1]

PORT_NO[1]

port information

property description[1]

Port number[1]

pre-installation work[1]

pre-installed licenses, example of managing[1]

prerequisite programs[1]

installing[1]

preview window

checking result[1]

printing

PDF files[1]

problem deletion event

attribute[1]

Problem Report Form

example of creating[1]

problems[1]

automatic registration[1]

referencing previous error handling procedures[1]

searching for serious errors[1]

problem status change event

attribute[1]

problem type

property description[1]

procedure

export[1]

registration[1]

search[1]

troubleshooting[1]

processes

list of[1]

processing

received Items[1]

processing mode

selecting[1]

processor

property description[1]

processor speed

property description[1], [2]

product ID

property description[1], [2]

program execution history

managing[1]

programs

organization[1]

property

AfterValue[1]

AreaSize[1]

AssetBranchNo[1]

AssetKind[1]

AssetNo[1], [2], [3]

AssetStatus[1]

AssetWorkKind[1]

Attribute[1]

BaseCreationClassName[1]

BeforeValue[1]

CatalogID[1]

ChildAssetID[1]

CircuitSpeed[1], [2]

Company[1], [2], [3], [4]

CompletingDate[1]

ComputerID[1]

ComputerName[1]

ContactInfo[1], [2], [3]

ContactInfo_2[1], [2], [3]

ContactInfo_3[1], [2], [3]

ContactName[1], [2], [3], [4]

ContactName_2[1], [2], [3]

ContactName_3[1], [2], [3]

Contents[1], [2], [3]

ContractDate[1], [2]

ContractID[1], [2], [3], [4]

ContractKind[1], [2], [3]

ContractNo[1], [2], [3]

ContractObject[1], [2], [3]

ContractStatus[1], [2], [3]

CostPriceCode[1]

CPUClock[1], [2]

CPUNumber[1], [2]

CPUType[1], [2]

DefaultGateway[1]

Description[1]

Developer[1], [2], [3]

DHCPServerName[1], [2]

displaying[1]

DivisionID[1]

DivisionName[1]

DMLastUpdateTime[1]

DMStatus[1]

DownGrade[1]

DownSoftwareListID1[1]

EndDate[1], [2], [3], [4]

EndIPAddress[1]

EngineVersion[1]

EventHost[1]

EventNo[1]

ExecutionHost[1]

ExecutiveName[1]

Executor[1]

Expense[1]

FileDate[1], [2]

FileName[1], [2]

FileSize[1], [2]

Frequency[1]

FullPathName[1], [2]

FullPathName_EN[1], [2]

Gateway[1]

GlobalIPAddress[1]

GroupCode[1]

GroupID[1], [2]

GroupName[1], [2], [3], [4]

GroupName_EN[1], [2], [3]

HistoryUpdateDate[1], [2], [3], [4]

HostName[1]

Importance[1]

IndicationItemKey[1]

InstalledDate[1], [2]

InstalledID[1], [2], [3]

InstalledInd[1]

InstalledKind[1]

InstalledName[1], [2]

InstalledPermit[1]

InstalledStatus[1]

InstalledVersion[1], [2]

InventoryKey[1]

IPAddress[1], [2], [3]

IPAddressKind[1]

IPGroupID[1]

IPGroupName[1]

JobRoleID[1]

JobRoleName[1]

JobRoleName_EN[1]

KeyID[1]

LicenseCategory[1]

LicenseID[1], [2]

LicenseKey[1]

LicenseName[1]

LicenseType[1]

Link[1]

LinkClass[1]

LinkKey[1], [2]

LocationID[1], [2], [3]

LocationName[1], [2], [3]

LocationName_EN[1], [2]

MACAddress[1], [2]

MachineKind[1], [2]

Mail[1]

MaintenanceDate[1]

MaintenanceHost[1]

MaintenanceID[1]

MaintenanceKind[1]

MaintenanceStatus[1]

ManagedLabel[1], [2]

ManagedNo[1]

ManagerialGroup[1]

ManagerialGroup_EN[1]

ManagerialGroupID[1]

ManagerialUser[1]

ManagerialUser_EN[1]

ManagerialUserID[1], [2]

MBSAVersion[1]

MeasureContents[1]

MemorySize[1], [2]

Model[1], [2]

ModelKind[1], [2]

MonitorKind[1], [2]

MonitorResolution[1], [2]

MonitorSize[1], [2]

MonthlyPrice[1], [2], [3]

Name[1], [2]

NetworkID[1]

NodeName[1]

non-editable[1]

Note[1], [2], [3], [4]

NumberOFLicense[1]

NumberOFPoint[1]

NumberOFPort[1], [2]

ObstacleContents[1]

OSInfo[1]

OSVersion[1]

ParentAssetID[1]

Password[1]

PatchID[1], [2]

PatchName[1]

PatchVersion[1]

PortInfo[1]

ProductID[1], [2]

PurchasePrice[1], [2]

PurchaseType[1]

Purpose[1], [2], [3]

RecordInd[1]

ReferenceData[1]

RegistrationDate[1]

RemainHDSize[1]

RenewalDate[1], [2]

RenewalTimes[1], [2]

ResidentKind[1]

RoleID[1]

RoleName[1]

SerialNo[1], [2]

SoftAssetID[1]

SoftwareKind[1]

SoftwareListID[1], [2], [3], [4]

SoftwareName[1]

SoftwareStatus[1]

SoftwareVersion[1]

Specification[1], [2]

StartDate[1], [2], [3], [4]

StartIPAddress[1]

StocktakingDate[1]

SubLinkKey[1]

SubnetMask[1], [2]

SystemInd[1]

TargetPoint[1]

Telephonenumber[1]

Threshold[1]

TotalHDSize[1], [2]

TotalPrice[1], [2], [3]

UpdateKind[1]

UpdateRecordInd[1]

UpdateUser[1]

UpGrade[1]

UpperLinkID[1], [2]

UserID[1], [2]

UserName[1], [2], [3], [4]

UserName_EN[1], [2], [3]

VirusDefName[1]

VirusDefVersion[1]

Worker[1]

property description

ContactInfo[1]

ContractDate[1]

property information

UserID[1]

purchase point

property description[1]

purchase price

property description[1], [2]

purpose

property description[1], [2], [3]

R

record indicator

property description[1]

recovering

DBMS errors[1]

errors during command execution[1]

Web browser errors[1]

recovering from errors

asset management server[1]

recovery

error[1]

REFERENCE_FIELD[1]

REFERENCE_NUM[1]

REFERENCE_NUMONPAGE[1]

reference material[1]

reference materials (URL)

property description[1]

Reference Software dialog box

Initial value[1]

Maximum[1]

Maximum length[1]

Minimum[1]

Reference range[1]

registering

actual stocktaking data[1]

contract information[1]

CSV data[1]

device catalog[1]

device information[1]

extensions of files to be uploaded[1]

installed software name[1]

license information[1]

maintenance log information[1]

software name[1]

user report[1]

volume contract information[1]

registrar

property description[1]

registration

CSV data[1]

procedure[1]

specifying asset location[1]

specifying attached file[1]

specifying group[1]

specifying user name[1]

registration date

property description[1], [2]

registry

backing up and restoring[1]

rejecting

Items[1]

related asset information

importing[1]

viewing or changing[1]

related programs[1]

related publications[1]

RelationAssetInfo

managing program execution history[1]

RelationAssetLink

associating device and another device[1]

releasing

assignment of installed software name[1]

IP address[1]

IP address assigned to device[1]

software name from downgrade software[1]

remote domain

adding[1]

renaming

managed items[1]

renaming host[1]

rental contract link

associating with device[1]

replacing

asset management server[1], [2]

resetting

virtual directories[1]

resident/nonresident

property description[1]

Response monitoring time[1]

restoring[1]

asset management database[1]

registry[1]

uploaded files[1]

restoring in CSV format

asset management database[1]

role ID

property description[1]

RoleInfo

managing user role[1]

role information

importing[1]

managing[1]

role name

property description[1], [2]

RoleName_EN[1]

role services

installing[1]

route

defining[1]

S

ScreenWithPage.pdf[1]

search

executing from command line[1]

procedure[1]

SEARCH_CASE_SENSITIVE[1]

search condition

defining[1]

setting display order[1]

setting view/hide setting[1]

searching for

devices[1]

software[1]

unused devices[1]

users[1]

search method

selecting[1]

search method type

associated class search[1]

class search[1]

joined class search[1]

search result

setting display order of[1]

setting display widths for item in[1]

setting items to be displayed[1]

setting view/hide setting[1]

specifying whether to include duplicated data[1]

search result list

setting for displaying details from[1]

second license

example of managing[1]

managing[1]

selecting

asset type[1]

jobs to be executed[1]

method for outputting CSV data[1]

processing mode[1]

search method[1]

Sender's e-mail address[1]

serial number

property description[1], [2]

SERVER[1]

server license

example of managing[1]

Server name[1]

Server Setup dialog box

settings[1]

SERVICE_NAME[1], [2]

Service name [1]

services to be used by asset management server

setting up[1]

Session Information[1]

setting[1]

SESSTION_TIME[1]

setting

applications[1]

assigned item[1], [2]

assigned item for asset number[1]

assigned item for device type[1]

assigned item for group and location[1]

assigned item for user name[1]

Basic Information[1]

button[1]

database information[1]

handler mappings[1]

ISAPI filters[1]

ISAPI restrictions[1]

JP1/IT Desktop Management 2 - Manager management information acquisition[1]

linking to EUR[1]

Mail Notification Information[1]

management information assignment method[1]

object role[1]

output item[1]

Session Information[1]

software name assignment method[1]

tasks that are registered in Task Scheduler[1]

virtual directories[1], [2]

setting

filtering condition[1]

settings

linking to JP1/Service Support[1]

link to JP1/IM[1]

Link with Directory Server[1]

Server Setup dialog box[1]

Settings for a group that uses a group-specific IP group[1]

Settings for a location that uses a location-specific IP group[1]

setting up

asset management server[1]

services to be used by asset management server[1]

setup

installation[1]

setup procedure

for Asset Console[1]

task[1]

shared information

managing[1]

show item key

property description[1]

Show number column[1]

Show PDF button[1]

simple search condition[1]

site

adding[1]

SMTP virtual server

executing[1]

software

managing[1]

searching for[1]

types[1]

software asset

property description[1]

software assets

viewing and changing[1]

SoftwareInfo

managing software information[1]

software information

managing[1]

SoftwareKeyInfo

managing software key information[1]

software key information

property description[1]

Software License[1]

SoftwareList

managing software list[1]

software list

property description[1]

software list ID

property description[1], [2], [3], [4]

software name[1]

assigning[1]

changing[1]

defined[1]

deleting[1]

property description[1]

registering[1]

releasing from downgrade software[1]

software name assignment method

setting[1]

software names

consolidating[1]

establishing correspondence[1]

software status

property description[1]

software type

property description[1], [2]

software update log

managing[1]

software usage management[1]

Sort key for the group-specific tree display[1]

specification

CreationClassName[1]

property description[1], [2]

specifying

asset location[1]

attached file[1]

class join method[1]

directory browse settings[1]

group[1]

substitute[1]

user name[1]

standard output message log entry

interpreting[1]

start date of use

property description[1]

starting

database[1]

database[1]

Start IP address

property description[1]

status

adding or changing[1]

property description[1], [2], [3], [4], [5]

Status to display in device search windows[1]

stocktaking[1]

checking number of devices that require[1]

format of CSV data file[1]

registering actual data[1]

stocktaking date

property description[1]

stocktaking job, procedure for[1]

stopping

database[1], [2]

subject

property description[1], [2]

sub link key

property description[1]

subnet mask

property description[1], [2]

substitute

specifying[1]

suppressing

operations on asset information from JP1/IT Desktop Management 2 operation windows[1]

SURROGATE[1]

SURROGATE_MAIL_NOTICE[1]

symbol conventions[1]

system configuration

cluster system[1]

evaluating[1], [2]

example[1]

linked to Active Directory[1]

linked to EUR[1]

linked to JP1/IM - Manager[1]

linked to JP1/Service Support[1]

system indicator

property description[1]

system problems

managing[1]

system requirements and estimates[1]

T

tab

changing name for[1]

changing view/hide setting for[1]

Table Designer

Cross-reference of object types and object attributes[1]

target point

property description[1]

task

deleting[1]

enabling[1]

execution results[1]

setup procedure[1]

types[1]

taskopt.ini[1]

task schedule

changing[1]

tasks that are registered in Task Scheduler

setting[1]

TB meaning[1]

threshold

property description[1]

Threshold for license excess[1]

TIMELIMIT[1]

Time-out time for PDF file creation[1]

total

property description[1], [2]

total contract amount

property description[1]

total count management[1]

totaling

licenses[1]

transaction processing

Web browser execution[1]

transaction processing during command execution[1]

transactions

asset management system[1]

transfer log

importing[1]

importing and exporting[1]

Trash group ID for deletions[1]

Trash location ID for deletions[1]

troubleshooting[1]

procedure[1]

type

adding or changing[1]

types

access permissions for users[1]

device[1]

software[1]

task[1]

user role[1]

typical uses[1]

U

unauthorized install

notification[1]

unauthorized software installations

checking for[1]

UNDEF_GROUP[1]

UNDEF_LOCATION[1]

uninstalling

Asset Console[1], [2]

unregistered software

checking usage status of[1]

unused devices

searching for[1]

UPDATE_RECORD[1]

update control

property description[1]

Update control[1]

update date

property description[1], [2]

update date/time

property description[1], [2], [3]

update date and time

property description[1]

update history

browsing[1]

managing, of installed software[1]

UpdateRecord

managing device memory size, disk capacity[1]

UpdateTime[1]

update type

property description[1]

update user ID

property description[1]

update user name

property description[1]

upgrade assurance

property description[1]

uploaded files

backing up and restoring[1]

upper group ID

property description[1]

upper location ID

property description[1]

usage management

property description[1]

user[1]

adding[1]

deleting[1]

for linking to other products[1]

moving[1]

searching[1]

USER[1], [2]

USER_ATTR[1]

USER_NAME_ATTR[1]

user and authority link

associating[1]

user and group information

changing[1]

user and key link

associating[1]

user and member link

associating[1]

user and official authority link

associating[1]

user extension area of problem status change event

setting[1]

user ID

property description[1], [2]

User ID attribute name[1]

user ID of administrator

parameter description[1]

property description[1]

UserInfo

managing asset management system user[1]

user information

changing[1]

deleting[1]

editing[1]

importing[1]

managing[1]

viewing[1]

User information DN[1]

User license, example of managing [1]

user name

event manager[1]

how to specify[1]

property description[1], [2], [3]

service support manager[1]

user name (English)

property description[1], [2], [3]

User name attribute name[1]

user organization information

acquiring[1]

UserPermitLink

associating license and user[1]

user property

area[1]

code[1]

date[1]

field[1]

uint[1]

user report

creating[1]

deleting[1]

executing[1]

registering[1]

user role

adding[1]

changing[1], [2]

changing setting for[1]

changing window for[1]

deleting[1]

differences in accessible asset information by[1]

differences in job menus by[1]

differences in window functions by[1]

Managed label[1]

Role window[1]

user roles

types[1]

using

Flow Designer[1]

V

version number conventions[1]

version of virus detection engine

property description[1]

viewing

contract information[1]

device details[1]

division[1]

group[1]

individual information[1]

installed software assets[1]

IP address usage[1]

log information[1]

maintenance log[1]

network information[1]

related asset information[1]

user information[1]

virtual directories

resetting[1]

setting[1], [2]

virus definition information

importing[1]

managing[1]

virus definition version

property description[1]

VolumeContract

managing volume license information[1]

volume contract information

changing[1]

managing[1]

registering[1]

VolumeContractLink

associating volume contract and software[1]

volume contract link

associating with software[1]

volume license points, managing[1]

W

Web browser

identifying error[1]

when terminating abnormally[1]

Web browser [1]

Web browser errors

recovering[1]

Web browser execution

transaction processing[1]

Web server

when error occurs[1]

when error occurs

in Web server[1]

when operational errors occur[1]

when system errors that are not urgent or serious occur[1]

when temporary errors occur[1]

when terminating abnormally

Web browser[1]

when urgent or serious system errors occur[1]

when Web browser display is invalid[1]

when Web server stops responding[1]

window

Acquire Device Update Record Items[1]

Code[1]

Confirm Stocktaking Device[1]

Contract List[1]

defining[1]

Device Catalog[1]

Device Change Log[1]

Device List[1]

Device Totals[1]

Excess License List[1]

Execution Item Management[1]

Export[1]

Group and User[1]

Import[1]

Inbox[1]

Individual Information[1]

Installed Software[1]

IP Group[1]

ITDM2 Management Information Acquisition[1]

Location[1]

Log[1]

New Contract[1]

New Device[1]

New Item[1]

New Software[1]

New Volume License[1]

Owned License List[1]

Problems[1]

Result Import[1]

Search Users[1]

Software List[1]

Software Name[1]

Totals List & Execution[1]

Totals of Stocktaking-Unexecuted Devices[1]

Transfer License[1]

Unauthorized Install List[1]

Unauthorized Usage List[1]

Unknown Usage List[1]

Unused Device List[1]

Update History[1]

Volume License List[1]

window, adding[1]

window operation

changing[1]

worker

property description[1]

workflow

acquiring JP1/IT Desktop Management 2 - Manager management information[1]