Job Management Partner 1/Asset Information Manager Planning and Setup Guide

[Contents][Glossary][Index][Back][Next]

Appendix I. Glossary

accessory (device type)
A type of hardware asset, including Monitor, Hard disk, CD-R, DAT, MO, or Printer. In the asset management system, hardware is classified into three device types: computing, accessories, and networking.
access permission
Restrictions set for some of the asset information managed in an asset management system so that the users who can access it 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
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 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 Information Manager
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 Information Manager to JP1 products such as JP1/Software Distribution, HP NNM Version 7.5 or earlier, and JP1/IM.
asset management database
A database that stores asset information. The asset management system supports Microsoft SQL Server, Embedded RDB, and Oracle as its database systems.
asset management database server
A server containing the 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
  • Asset management database 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.
cabinet
An area for storing packages; the area is located in JP1/Software Distribution's managing server.
Asset Information Manager can distribute packages stored in JP1/Software Distribution cabinets.
class
  1. A set of management information classified by asset information category. An asset management system handles object classes and association classes.
  2. WSUS updates categories, such as security updates and critical updates.
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, and UNIX server. 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.
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.
destination
A client subject to execution when a job is executed from JP1/Software Distribution's managing server.
Asset Information Manager enables software assets to be distributed to devices that are found by searches in operation windows. The user can also distribute software by specifying a host group created by JP1/Software Distribution.
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 (,).
Embedded RDB
A database that is built into Asset Information Manager and JP1/Software Distribution Manager. By using Embedded RDB, you can install Asset Information Manager and JP1/Software Distribution without having to install a DBMS product.
event manager
A user assigned to check Asset Information Manager asset information from JP1/IM. If a password is set up for this user in advance, the user can automatically be logged into Asset Information Manager 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 Information Manager.
  • 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 Information Manager.
file operation log
An operation log that collects folder and file operation events, such as when a file or folder is created or copied. These logs are collected by JP1/Software Distribution.
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.
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.
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 Information Manager. Hardware information is about the devices themselves, and includes fields such as Device type and Device name.
HP NNM
A product that provides functionality for managing multiple applications and multiple systems connected by a network, from a single network graphics window.
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
    This 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 Information Manager. It enables the user to 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 Information Manager.
installed software information
Information used to manage the software assets installed on each device.
Installed software information is used by importing information (such as JP1/Software Distribution's inventory information) into an asset management database.
Therefore, the names and versions of software assets depend on the source system (such as JP1/Software Distribution) 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.
inventory information
Information such as the status of hardware utilization and the types of software assets installed at a client. Clients are managed based on this information. Inventory information is acquired from JP1/Software Distribution's managing server by executing jobs.
The asset management system can register inventory information acquired from JP1/Software Distribution as asset information.
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.
Item
Work with a defined route: such as Equipment Deployment Request Form or Software Distribution Application Form.
(Note: To avoid confusing this term with the everyday meaning of item, this manual uses upper-case "I" (Item). Other manuals, messages, or windows might not use this convention.)
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.
job
An execution unit of JP1/Software Distribution functionality.
Two types of jobs can be executed from Asset Information Manager windows:
  • Install package
  • Install by client user
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 Information Manager 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/CSC
A product that uses asset information managed by Asset Information Manager to take security measures for a system. A security management system that has JP1/CSC installed uses policies set by the administrator as a base to automatically evaluate the danger level for devices, and then takes appropriate actions (countermeasures).
Administrators can use the windows under the Client Security Management job category to monitor clients and perform actions as necessary.
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/Software Distribution
The collective name for a system that achieves software distribution and client management by batch operation over a network.
JP1/Software Distribution not installed, machine on which
See machine on which JP1/Software Distribution is not installed.
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.
machine on which JP1/Software Distribution is not installed
A device in the network on which JP1/Software Distribution Client has not been installed.
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 items
An individual piece of information managed by Asset Information Manager. 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. When a managed level is set for each software asset, JP1/Software Distribution's inventory information is registered according to this setting. The managed level is set in the Installed Software window.
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.
meta table
A table required to establish correspondence between class and table in the asset management database. When Asset Information Manager is set up, importing the meta table to the asset management database defines the data structure of the database.
network information
Information used to manage the location of each device in the network. Network information includes IP address, MAC address, Node name, and Computer name.
networking (device type)
A type of hardware asset, including HUB, Router, and Network printer. In an asset management system, hardware is classified into three device types: computing, accessories, and networking.
network manager
A user who references Asset Information Manager asset information obtained from HP NNM Version 7.5 or earlier. If a password is set up for this user in advance, this user can automatically be logged into Asset Information Manager when checking asset information from the Network Presenter or Submap window.
Network Presenter
A map of network devices detected by HP NNM Version 7.5 or earlier. It enables the user to reference network device connections and network problems.
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.
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 Information Manager.
operation log
User operation information acquired by JP1/Software Distribution. Asset Information Manager can directly access the JP1/Software Distribution database, and can search and check the operation log data stored in the databases.
Operation logs enable you to determine the time and location of executed operations, such as the copying and renaming of files, and enable the execution of time-series tracking. By totaling the operation log data, you can also understand the status of each group from the totaled results.
OU (Organization Unit)
The name attribute of organization entries in Active Directory. An organization unit corresponds to a group name.
package
Software that has been registered in JP1/Software Distribution's managing server and is ready to be distributed. It is stored in a cabinet in the managing server.
To distribute software from Asset Information Manager, a package must be created for it by using JP1/Software Distribution beforehand.
packaging
Creating a package by using JP1/Software Distribution.
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.
PC startup log
An operation log in which information about PC startup, termination, logon, and logoff events is collected. These operation logs are collected by JP1/Software Distribution.
program execution history
The history of the start and termination of the programs used on a managed device. The program execution history can be accessed from the Program Execution History job menu. If the system is linked with JP1/Software Distribution 07-50 or later, this information can be acquired from the operation history obtained by JP1/Software Distribution.
Program execution history data is organized into fields such as login user, program name, program version, and issue date/time.
program start log
An operation log in which data about program startup, program termination, and events that prevented program startup is collected. These operation logs are collected by JP1/Software Distribution.
property
An attribute of a class.
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.
search pattern
Stored search conditions that are used to search operation logs in the Operation Log List window. Frequently used search patterns are registered as default patterns. You can edit the default search patterns that have been registered as well as register new search patterns.
SNMP trap
A message sent from an SNMP agent to an SNMP manager, such as HP NNM version 7.5 or earlier, in response to a specific trigger.
Asset Information Manager 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 key information
Key information used to assign licenses to target devices and users. Software key information includes Product ID, License key, and Serial No.
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.
updates
Programs provided by Microsoft Update to fix specific system problems. Asset Information Manager links with a WSUS server to manage updates.
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 inventory information
Information that can be optionally set by the user, such as user name and asset number. User inventory information is acquired by executing a job from the JP1/Software Distribution managing server.
In an asset management system, the user inventory information acquired by JP1/Software Distribution can be registered as asset information.
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 Information Manager not only provides predefined job menus, but also enables the user to add user-specific jobs (user reports).
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.
window title update history
Management information that summarizes historical data collected about window title changes performed on managed devices. The window title update history can be accessed from the Window Title Update History job menu. When the system is linked with JP1/Software Distribution 07-50 or later, this information can be obtained from the operation history acquired by JP1/Software Distribution.
Window title update history data is organized into fields such as login user, program name, program version, issue date/time, and window title.
window title update log
An operation log in which window title changes of updated windows are collected. These operation logs are collected by JP1/Software Distribution.
worker
A user who executes an Item. An Item is sent to individual workers according to a defined route.
WSUS server
The server that manages updates from Microsoft Update.