JP1 Version 12 JP1/Base User's Guide

R. Glossary


A program that is managed by another program on the system, or a host that is managed by another host on the system.

For example, JP1/Base is the agent for JP1/IM, and JP1/AJS - Agent and JP1/Base are the agents for JP1/AJS.

ANY binding method

A communication protocol that permits reception of data sent to all the IP addresses assigned to the hosts. The communication wait process ensures that data sent to all the hosts by using port numbers is received. The connection process ensures that data is sent to all the hosts on the subnetworks even if each host uses multiple subnetworks. If JP1/Base is used for a physical host alone, JP1/Base typically operates by this ANY binding method (without the need to make settings).

authentication server

A server that manages the access permissions of JP1 users. One authentication server is required in each user authentication block. The administrator can centrally manage all JP1 users on this server. When JP1/IM or JP1/AJS is installed in the system, the administrator must register JP1 user names on this server.

basic attribute

An attribute held by all JP1 events.

blocked status

Status where the system does not attempt to reconnect the authentication server after a connection failure. This status might occur when two authentication servers are installed in a single user authentication block.


A host that issues instructions for process execution to another host (or program), and receives the execution results from that host (or program). JP1/IM - View acts as a client in a JP1/IM system, and JP1/AJS - View acts as a client in a JP1/AJS system.

cluster system

A system configured with multiple server systems that work together so that job processing can continue if a failure occurs. The process of one system taking over from a failed system is called failover. If the active server (primary node) fails, the standby server (secondary node) takes over. Because the job processing is switched from the active to the standby node, a cluster system is also called a node switching system.

Cluster systems include load-sharing systems with multiple servers that perform parallel processing. In this manual, however, cluster system refers only to failover functionality for preventing interruption of job processing.

common definition information

A set of definitions relating to JP1/Base, JP1/IM, JP1/AJS, and JP1/Power Monitor. This information is managed by JP1/Base. The database containing this information is on a local disk of each server, and the definition parameters are stored on each of the physical hosts and logical hosts to which they apply.

When JP1 is used in a cluster system, the logical hosts definitions in the common definition information stored on the servers must be identical on both the primary and secondary nodes. For this reason, after completing the setup and environment settings on the primary server, you must copy the parameters to the secondary server.

configuration definition

Information defining the configuration of a system run and managed by JP1/IM.

A configuration definition defines the hierarchy of managers and agents in JP1/IM. You can define managers at different levels. For example, you can define a higher-level integrated manager and a lower-level site manager.

The information about host relationships defined in a configuration definition can be utilized in various ways. For example, in JP1/IM, it indicates the manager hosts to which important JP1 events should be forwarded and defines the hosts on which commands can be executed as automated actions.

directory server

A server that provides services required to centrally manage various resources on the network and their respective attributes.

DS group

A security group of the Active Directory to which JP1 operating permission is assigned. JP1 operating permission can be easily assigned because assigning JP1 operating permission to a security group also gives JP1 operating permission to accounts to belong to the security group.

DS user

A JP1 user on which user authentication is performed through linking with a directory server. JP1 authentication information (JP1 user authentication information and JP1 operating permission) is managed on the directory server.

event ID

One of the attributes of a JP1 event. An event ID is an identifier indicating the program that issued the event and the nature of the JP1 event. It is a basic attribute and has the attribute name B.ID.

Event IDs are hexadecimal values, such as 7FFF8000.

Event IDs are uniquely assigned by each of the programs in the JP1 series. For details on the JP1 events issued by a specific program, see the manual for that program.

The values from 0 to 1FFF, and from 7FFF8000 to 7FFFFFFF, are available as user-specifiable event IDs.

A JP1 event is an 8-byte number consisting of a basic code (upper four bytes) and extended code (lower four bytes). Usually only the basic code is used, representing a 4-byte event ID. The extended code is 0, except in special cases, as when set by the user in the API. When both the basic and extended codes need to be included, they are joined with a colon (:) and appear as 7FFF8000:0, for example.

event log trapping

The event log trapping functionality converts Windows event log data into JP1 events.

event server

A program that has functionality for managing JP1 events under JP1/Base. When the event server is active, JP1 events can be collected and distributed.

event service

Functionality for registering and managing the events generated in the system as JP1 events.

extended attribute

An attribute of a JP1 event, optionally set by a source program when issuing a JP1 event. An extended attribute consists of common information and program-specific information. The common information is shared by all JP1 programs. The program-specific information is additional information set by the particular program.


Uninterrupted JP1 processing by transferring JP1 operations to another server when a failure occurs on the active server. Or, switching by the system administrator of the server that is currently executing JP1 processing.

Because the server on a secondary node takes over from the server on the primary node, failover is also known as node switching.

information-search user

A user who can search for the users linked to a directory server on the directory server. An information-search user is a directory server user who has view permission for the search-origin container object and the underlying container objects.

IP binding method

A communication protocol that permits reception of data sent to a particular IP address. The communication wait process ensures that data sent to a particular IP address only is received. The connection process ensures that data is sent via a NIC that uses a particular IP address only.

If JP1/Base is used in a cluster system, JP1/Base typically operates by this IP binding method. (Making the settings for the cluster system changes the communication protocol to the IP binding method.)


A program for running jobs automatically. You can execute a sequence of processes according to a predefined schedule, or initiate processing when a specific event occurs.

JP1 administrators group

A user group that allows users other than the system administrator (users with superuser permission) to operate JP1/Base. Permission to operate JP1/Base is granted to OS users whose primary group is the JP1 administrators group.


A program that provides event services. Using JP1/Base, you can send and receive JP1 events, and control the sequence in which services are activated.

JP1/Base is a prerequisite program for JP1/IM, JP1/AJS, and JP1/Power Monitor. When JP1/IM or JP1/AJS are configured in the system, JP1/Base enables the administrator to restrict the operations that JP1 users can perform.

JP1/Base administrator

A user who has been given permission to operate JP1/Base. In a UNIX environment, a JP1/Base administrator is an OS user whose primary group is the JP1 administrators group. Enable this feature when you want OS users other than those with JP1/Base system administrator permission to be able to use JP1/Base.

JP1 event

Information for managing events occurring in the system within the JP1 framework.

The information recorded in a JP1 event is categorized by attribute as follows:

Basic attribute

Held by all JP1 events.

Basic attribute names are expressed as, for example, B.ID (or simply ID) for the event ID.

Extended attribute

Attributes that are optionally set by the program that issued the JP1 event. An extended attribute consists of the following common information and program-specific information:

1. Common information (extended attribute information in a format shared by all programs)

2. Program-specific information (other information in a format specific to the program issuing the event)

Extended attribute names are expressed as, for example, E.SEVERITY (or simply SEVERITY) for the severity level.

JP1 events are managed by the JP1/Base event service. Events generated in the system are recorded in a database as JP1 events.

jp1hosts information

JP1-specific hosts information. If jp1hosts information is defined, JP1/Base has two or more IP addresses assigned to each host, and thus can resolve two or more IP addresses from each host name even when the OS can resolve only one IP address from each host name. jp1hosts information is valid when it is registered as a common definition.

jp1hosts2 information

JP1-specific hosts information. jp1hosts2 information allows JP1/Base to resolve multiple IP addresses from one host name, even in environments where the operating system can only resolve one IP address from a given host name. jp1hosts2 information takes effect when registered on a host.

JP1/IM - Manager

JP1/IM - Manager (JP1/Integrated Management 2 - Manager) is a program that provides integrated system management through centralized monitoring and operation across the entire system.

JP1/IM - Manager provides two core features: central console and central scope.

JP1/IM - View

A program that provides the view functionality for integrated system management in JP1/IM.

JP1/IM - View provides a common graphical user interface for JP1/IM - Manager and JP1/IM - Rule Operation. The user can link JP1/IM - View to these programs as required, and perform system monitoring and management suited to the system's purpose.

JP1 permission level

A level that indicates the types of operations that a JP1 user is allowed to perform on a management target (that is, on a resource). Permissible operations depend on whether the management targets (the resources) are jobs, jobnets, events, or other entities. JP1 users' access permissions are managed as combinations of different permissions set for specific types of resources.

JP1/Power Monitor

A program that starts and stops hosts automatically.

Using JP1/Power Monitor, you can start and stop hosts according to a set schedule, and start and stop hosts remotely.

JP1 resource group

A set of management targets (that is, resources), such as jobs, jobnets, or events, that are managed together in JP1. Each set of resources is a JP1 resource group.


A program in Version 5 and earlier versions of the JP1 series. JP1/SES provides functionality (System Event Service) for managing events issued by applications.

JP1/SES compatibility

Functionality to maintain compatibility with the event service provided by the pre-Version 6 programs, JP1/SES and JP1/AJS.

JP1 user

An identifier for accessing JP1/IM or JP1/AJS. This name is registered on the authentication server, which controls the user's access permissions to a remote host. The JP1 user name might differ from the user account registered on the OS.

JP1 users can be classified into the following JP1 user types according to their method of user authentication:

  • Standard user

  • DS user

  • Linked user

key definition file

A file that contains the correspondence between data files and key files.

key file

A file that contains the index information in a hierarchical tree structure for retrieving keys. This file also contains keys for retrieving data file records. There are two types of key files: a main key file and a subkey file.

large numbers of events

Many unexpected JP1 events that occur over a short period.

linked user

A JP1 user on which user authentication is performed through linking with a directory server. Only JP1 user authentication information of JP1 authentication information (JP1 user authentication information and JP1 operating permission) is managed by the directory server. This allows JP1 users to be registered in an authentication server without entering a password.

local action

A function that automatically executes a command on the local host when a specific JP1 event occurs.

log file trapping function

Functionality that converts log data that was output to a log file by an application program. The log data is converted to JP1 events.

logical host

A logical server that executes JP1 in a cluster system. If a failure occurs, a failover between logical hosts takes place.

Each logical host has a separate IP address and a shared disk. In the event of a failover, a logical host starts operating by inheriting the IP address and shared disk of the failed logical host. Thus, after a physical server is switched into service because of a failure, other hosts can access the server by using the same IP address as that of the failed server. To the host, it seems as if one server is always active.


A program that manages other programs (agents) on the system, or a host that manages other hosts on the system.

For example, JP1/IM - Manager, JP1/IM - Rule Operation, and JP1/AJS - Manager manage either JP1/IM or JP1/AJS. These program manage other programs (agents) on the system.

multi-LAN connectivity

JP1 functionality for a system composed of multiple LANs.

Using this functionality, you can set a JP1 communication LAN on a host connected to multiple hosts. You can also make communication settings specific to JP1, regardless of the system or any other applications. This provides flexibility to adapt to various network configurations and operation methods.

In some cases, a host connected to multiple LANs is called a multi-home host or multi-NIC host.

JP1/Base can operate in the following multi-LAN connectivity environment:

  • Environment divided into multiple networks


A generic name for the integrated network management programs designed for network configuration, performance, and trouble management.

node switching system

See cluster system.

operating information

Definition information loaded by JP1/Base services. This information can be used to check the currently valid definition for JP1/Base.

physical host

A unique environment given to each of the servers that make up a cluster system. The environment for a physical host is not inherited by other servers when a failover takes place.

primary authentication server

One of two authentication servers installed in a single user authentication block. The primary authentication server is the server that is usually used.


A Windows service program or UNIX daemon program.

regular expression

A list of characters and special characters corresponding to one or more specific text strings.

secondary authentication server

One of two authentication servers installed in a single user authentication block. The secondary authentication server is used as a backup.

SNMP trap converter

A function that converts SNMP traps issued by NNM into JP1 events.

sparse character

Any character that is specified not to be used as a key. Specify sparse characters for creating a key definition file or for adding a key.

When you add a record, any key that only contains sparse characters will not be added to the key file. This key is called a sparse key. Using the sparse key reduces the size of the key file and the time required for processing a duplicate key. This key helps to reduce the time it might take to process duplicate keys.

standard user

A JP1 user whose login is authenticated by an authentication server. JP1 authentication information (JP1 user authentication information and JP1 operating permission) is managed by the authentication server.

user authentication block

The range of hosts managed by one authentication server in a system. JP1 users can run jobs, execute commands, and perform automated actions and other operations on the hosts within an authentication block. When JP1/IM or JP1/AJS is installed in the system, the administrator must decide the configuration of user authentication blocks.

user mapping

Functionality that grants to JP1 users the rights of one or more users registered in the OS.

When user mapping is defined, a user who is registered as a JP1 user on an authentication server is allowed to perform operations on a host using the privileges of a user registered in the OS of that host.

variable binding

A variable binding of an SNMP trap. When a SNMP trap is converted into a JP1 event in JP1/Base, the variable bindings are read into the program-specific information contained in the extended attributes of the JP1 event.

As basic information, an SNMP trap indicates the source program (enterprise name) and the trap type (generic or specific). In addition, when detailed trap-specific information needs to be included, variable bindings (also written as VarBind) are appended to the SNMP trap when it is issued.

A variable binding contains an object identifier (OID) and data. For example, if JP1/SSO detects an error while monitoring an application, the application name can be appended in a variable binding as detailed information when the error is trapped.

For details on SNMP traps, see RFC1157 and other network-related documentation. For details on the information contained in the variable bindings, see the manual for the specific program that issues SNMP traps.


A program that provides windows used to operate managers and agents, and to confirm the information they manage. A host that executes a viewer is also called a process.

For example, JP1/IM - View is the viewer for JP1/IM, and JP1/AJS - View is the viewer for JP1/AJS.