Hitachi

JP1 Version 12 JP1/Automatic Job Management System 3 Configuration Guide


13.2.1 Setting up JP1/Base

This subsection describes how to set up JP1/Base.

The subsection contains an overview of setup and brief setup procedures. For details about the setup procedures, items to be set, and commands, see the JP1/Base User's Guide.

The following is an overview of JP1/Base setup:

  1. Set user information.

    JP1/Base user management is used to specify user mapping settings.

    The user mapping settings are required when another host sends a job execution request to the local host. JP1 users are mapped to OS users who have been registered on hosts.

    For details about how to specify these settings, see (1) Setting user information.

  2. Specify the event service environment settings.

    The event service environment settings are required to send and receive JP1 events.

    In the JP1/Base event service environment settings, specify keep-alive as the communication type for the server parameter in the API settings file. If close is specified, the following problems might occur:

    • The JP1 event issued by JP1/AJS3 at startup cannot be issued.

    • The KAVT1040-E message is output to the integrated trace log, and the JP1 event reception monitoring job, log file monitoring job, and Windows event log monitoring job cannot detect events.

    • The JP1 event sending job terminates abnormally (Ended abnormally status).

    For details about how to specify settings and about the API settings file, see the JP1/Base User's Guide.

The following describes the JP1/Base setup procedure and definitions.

Organization of this subsection

(1) Setting user information

In the UNIX version of JP1/Base, user information can be set by using commands.

The following describes the steps required to set user information.

Note that JP1/AJS3 - Agent and JP1/AJS2 - Agent 07-00-/C and later versions no longer access the authentication server when they start.

In JP1/AJS3 - Agent and JP1/AJS2 - Agent 07-00-/C and later versions, you do not need to specify the authentication server.

(a) Map the JP1 users

Map the JP1 users registered on the authentication server to OS users.

To map a JP1 user:

  1. Use a text editor to create a new file.

    This file will be used as the user mapping definition file.

  2. Specify user mapping entries, each in JP1-user-name:host-name:OS-user-name format.

    The following shows an example of the definition in the file.

    [Figure]

  3. When you have completed the definition, close the file, and then execute the following command:

    jbsmkumap -f user-mapping-definition-file

    The definition in the file takes effect.

Supplementary note:

The following table describes the items that can be specified in the user mapping definition file.

Table 13‒5: Items that can be specified in the user mapping definition file (JP1/AJS3 - Agent)

Permitted operation

JP1 user

Host

OS user

Executing a job on a host other than the JP1/AJS3 - Manager host

User who logs in to the OS of the JP1/AJS3 - Manager host

JP1/AJS3 - Manager host

User registered in the OS of the host on which the job will be executed

Cautionary note:

Make sure that the user ID and group ID have been set correctly for any OS user to whom you map a JP1 user.

For a JP1 user to be able to log in from JP1/AJS3 - View, the home directory must be set correctly for the OS user to whom the JP1 user is mapped.

The OS users to which you map JP1 users must be able to log in to the OS normally.

If the OS user to whom you map a JP1 user satisfies either of the following conditions, the job might fail to start:

  • The home directory specified in /etc/passwd does not exist.

  • The login shell specified in /etc/passwd does not exist.