Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer the batch environment > Administer the batch environment > Configure the job scheduler

Secure the job scheduler using roles

We can secure the job scheduler by mapping users and groups to specific security roles.

Users who are assigned the lradmin role have the authority to perform all job scheduler application actions on all jobs regardless of job ownership, while users who are assigned with the lrsubmitter role can only act on jobs that are owned by the submitters themselves.

To start lrcmd.sh | .bat on an HTTPS port, configure SSL on the scheduler server. Following the steps in part three of the series, location in the following DeveloperWorks topic, Build Web services with transport-level security using Rational Application Developer V7, Part 3: Configure HTTPS. In order to access topics, be a registered user for DeveloperWorks. If we have not registered as a user for DeveloperWorks, follow the instructions on the IBM registration page. This sample task assumes that the job scheduler is configured. From the admin console:

Procedure

1. Click Security > Secure administration, applications, and infrastructure.

2. Select administrative security and application security.

3. Configure User account repository by specifying one of the available realm definitions.

4. After we have configured WAS Security, click Apply to save the configuration.
5. Expand System administration > Job scheduler > Security role to user/group mapping.

6. Select the roles to be configured.

7. Click Look up users if one or more users are to be assigned the target role, or click Look up groups if role assignment is at the group level.

8. Select the user or group to be assigned to the target role.

9. Click OK and save the configuration.

10. Restart the cell.

What to do next

With security enabled, provide a valid user ID and password for job actions performed through the command- line interface. Submit a job action through the command-line interface with the user name and password information. See the following example:

<install_root>/bin/lrcmd.[bat|sh]
-cmd=
<name_of_command>
<command_arguments> [-host=
<host> -port=
<port>]
-userid=
<user_ID> -password=
<password> 

where:

• <host> is the job scheduler server host name. If not specified, the default is localhost.
• <port> is the scheduler server HTTP (HTTPS) port. If not specified, the default is 80.

See the following example:New feature:

D:\IBM\WebSphere\AppServer\bin\lrcmd
-cmd=submit -xJCL=D:\IBM\WebSphere\AppServer\samples\Batch\
postingSampleXJCL.xml -port=9445 -host=wasxd01.ibm.com
-userid=mylradmin -password=w2g0u1tf

Roles and privileges for securing the job scheduler
Command-line interface
Run batch jobs under user credentials

+

Search Tips   |   Advanced Search