WebSphere Extended Deployment, Version 6.0.x
             Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS


Securing the long-running scheduler

This topic describes how to secure the long-running scheduler.

Before you begin

Users who are assigned the lradmin role have the authority to perform all long-running 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.

About this task

This sample task assumes that the job scheduler is configured. From the administrative console:

Procedure

  1. [Version 6.0.1 and later] Click Security > Secure administration, applications, and infrastructure.
  2. [Version 6.0.1 only] Click Applications > Enterprise Applications > LongRunningScheduler.
  3. [Version 6.0.1 only] Click Map security roles to users/groups.
  4. Check the box for the role to be configured.
  5. 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.
  6. Select the user or group to be assigned to the target role.
  7. Click OK, then Save.
  8. [Version 6.0.1 only] Click Security > Global Security.
  9. [Version 6.0.1 only] Enable global security and Java 2 security. This supports any of the WebSphere Application Server supported user registries such as Local OS, Lightweight Directory Access Protocol (LDAP), or custom.
  10. Restart the server.

What to do next

With security enabled, provide a valid user ID and password for job actions that are 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 exaple:
<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 on demand router (ODR) host name or the long-running scheduler server host name. If not specified, the default is localhost.
  • <port> is the ODR HTTP(s) proxy address or the long-running scheduler server HTTP(s) port. If not specified, the default is 80.
See the following:
D:\IBM\WebSphere\AppServer\bin\lrcmd 
-cmd=submit -xJCL=D:\IBM\WebSphere\AppServer\longRunning\
postingSampleXJCL.xml -port=9445 -host=wasxd01.ibm.com 
-userid=mylradmin -password=w2g0u1tf



Related concepts
Roles and privileges for securing the long-running scheduler
The command line interface
Task topic    

Terms of Use | Feedback

Last updated: Nov 30, 2007 4:00:35 PM EST
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r0/index.jsp?topic=/com.ibm.websphere.xd.doc/info/scheduler/tbgsecur.html