3.1.2 Setting up user information

Before performing import and export with JP1/AJS3 - Definition Assistant, you need to set up the user information. This subsection explains the necessary settings for user information when performing import and export with JP1/AJS3 - Definition Assistant as well as the permissions for execution that are necessary for the JP1 users to be used with JP1/AJS3 - Definition Assistant.

Note that since JP1/AJS3 - Definition Assistant uses JP1/AJS commands internally, the settings for performing import and export are the same as those for executing commands on the manager host. However, the JP1_USERNAME environment variable that can be used with JP1/AJS is not enabled.

Organization of this subsection

(1) When the user authentication function is not used
(2) When the user authentication function is used
(3) Permissions for execution that are necessary for JP1 users

(1) When the user authentication function is not used

This subsection describes how to set the user information of a JP1 user for the following types of operations:

When JP1/AJS3 - Definition Assistant is used as the default setting
When the automatic import function is used
When the automatic export function is used

In this subsection, the following user names and host names are used as examples.

Table 3‒1: User names and host names used in the explanation
The host on which JP1/AJS3 - Definition Assistant is installed	`HostD`
The OS user that uses JP1/AJS3 - Definition Assistant on `HostD`	`UserD`
The host on which JP1/AJS3 - Manager is installed	`HostM`
The OS user actually executing commands on `HostM`	`UserM`
The authentication server that `HostM` views	`HostA`

The following figure gives an overview of setup for user information.

Figure 3‒2: Overview of setup for user information (When the user authentication function is not used)

Note that user information is specified on JP1/Base on the authentication server and on the manager host. The following gives an outline of the settings for using JP1/AJS3 - Definition Assistant. For details about how to perform these settings, see the manual JP1/Base User's Guide.

(a) Setting up the authentication server

JP1 user registration

Register a JP1 user with the same name as an OS user of the host on which JP1/AJS3 - Definition Assistant is installed. In this case, UserD is registered as a JP1 user.

Note that only lower-case alphabetic characters can be used in JP1 user names. When the OS user name contains upper-case letters, it can be used as a JP1 user name without problems if it is registered in lower case.

Example:

OS user name: UserD

JP1 user name: userd
Settings for the JP1 permissions level

Grant the appropriate permissions so that the OS user of the manager host (UserM) can operate the resource groups of units to be imported or exported.

(b) Setting up the manager host

User mapping

Map the JP1 user connecting to the manager host (UserD) to the OS user of the manager host (UserM).

To perform import and export, user mapping needs to be performed to both establish a connection from JP1/AJS3 - Definition Assistant, and to execute commands on the manager host.

To establish a connection from the JP1/AJS3 - Definition Assistant host, map UserM to UserD by specifying HostD for the connection source server host, and UserD for the JP1 user.

To execute commands on the manager host, map UserM by specifying HostM for the server host, and UserD for the JP1 user.

To Page Top

(2) When the user authentication function is used

This subsection describes how to set the user information of a JP1 user for the following types of operations:

When JP1/AJS3 - Definition Assistant uses the same JP1 user settings that are used in JP1/AJS3 - View
When JP1/AJS3 - Definition Assistant is used without changing the JP1 user settings that are already being used in JP1/AJS3 - View

In this subsection, the following user names and host names are used as examples.

Table 3‒2: User names and host names used in the explanation
The host on which JP1/AJS3 - Definition Assistant and either JP1/AJS3 - View is installed	`HostD`
The JP1 user that accesses JP1/AJS3 - Manager	`jp1a`
The host on which JP1/AJS3 - Manager is installed	`HostM`
The OS user actually executing commands on `HostM`	`UserM`

The following figure gives an overview of setup for user information.

Figure 3‒3: Overview of setup for user information (When the user authentication function is used)

When the JP1 user (jp1a) has been already registered on the authentication server, and the user mapping settings (jp1a:HostM:UserM) for the JP1 user (jp1a) have been specified on the manager host, setup for user information is not needed.

Note that when you upgrade JP1/AJS3 - Definition Assistant and you want to use the user information settings of the JP1 user that were used in JP1/AJS3 - Definition Assistant before upgrade without change, specify N for the AJS-SET-SERVERHOST environment settings parameter.

The following table shows how to set user mapping when setting the AJS-SET-SERVERHOST environment settings parameter.

Table 3‒3: How to set user mapping when setting the AJS-SET-SERVERHOST environment settings parameter
No.	Value of AJS-SET-SERVERHOST	Program	Required user mapping
1	`Y`	JP1/AJS3 - Definition Assistant	jp1a:HostM:UserM
2	`Y`	JP1/AJS3 - View	jp1a:HostM:UserM
3	`N`	JP1/AJS3 - Definition Assistant	jp1a:HostD:UserM
4		JP1/AJS3 - Definition Assistant	jp1a:HostM:UserM
5		JP1/AJS3 - View	jp1a:HostM:UserM

For details about the AJS-SET-SERVERHOST environment settings parameter, see 3.2.1 Settings for environment settings parameters.

To Page Top

(3) Permissions for execution that are necessary for JP1 users

The table below lists the permissions for execution that are necessary for the JP1 users used with JP1/AJS3 - Definition Assistant.

The permissions for execution shown in this table are determined by the JP1 permissions level that is held by the JP1 users (users used with JP1/AJS3 - Definition Assistant) with respect to the JP1 resource group specified as the attribute of the target unit. However, if no JP1 resource group is specified for the target unit, or if the OS user mapped to the JP1 user to be used has either administrator permissions (in the case of Windows) or superuser permissions (in the case of UNIX), the permissions for execution shown in this table are not necessarily necessary.

Table 3‒4: Permissions for execution necessary for the JP1 users used with JP1/AJS3 - Definition Assistant
Function		Necessary permissions for execution^#1
The import function		JP1_AJS_Admin JP1_AJS_Manager JP1_AJS_Editor
The export function	The individual definition function
	The batch definition function
	The modification function^#2
	The delete function

#1

JP1 users having any one of the permissions for execution shown in the table above are entitled to execute each function.

#2

JP1 users changing the following items need either the JP1_AJS_Admin permissions for execution or the unit ownership permissions:

- Owner and JP1 resource group belonging to the unit common attribute information

- Executed by belonging to the job common attribute information

To Page Top