2.1.5 Mapping users
A JP1 user who wants to execute a job or command for another host requires the OS user permissions for that host. This means that you must associate JP1 users with OS users on the host where you want to execute a job or command. This is called user mapping.
User mapping associates the following:
-
The JP1 user who can execute instructions
-
The server host from which the users can execute instructions
-
The OS user permissions required for executing a job or command
- Note
-
-
In UNIX, only the OS user name is required for execution by an OS user. In Windows, however, since both an OS user name and a password are required, JP1/Base also manages OS passwords. Therefore, if you need to change the password of an OS user in Windows, you must also change the JP1/Base password information.
-
- Organization of this subsection
(1) Example of user mapping (in JP1/AJS)
The following is an example of user mapping in JP1/AJS.
|
|
![[Figure]](GRAPHICS/ZU010600.GIF)
If you log in from JP1/AJS - View to JP1/AJS - Manager, mapping of JP1 users to OS users is also required on the host running JP1/AJS - Manager. Therefore, you must set up user mapping on HostA (the manager host) and HostB (an agent host that executes jobs). For details, see the manuals JP1/Automatic Job Management System 3 Configuration Guide.
(2) Example of user mapping (in JP1/IM)
The following diagram shows an example of user mapping in JP1/IM.
|
|
![[Figure]](GRAPHICS/ZU010601.GIF)
You must set up user mapping on HostD (an agent host), because commands are executed from HostD for operations from JP1/IM - View. Also, you must set up user mapping on HostE, because automated actions are executed from HostE.
The users that can execute automated actions are defined in JP1/IM - Manager.