Previous | Home | Next


Job manager console

The job manager console has many of the basic options that you find in the deployment manager's dmgr console, including global security settings, the option to add users and groups to the federated user repository, WebSphere variable settings, and others that are common to any administrative environment. What is unique to the job manager dmgr console is the ability to submit jobs to nodes registered to it.

Starting with WAS V8, we can complete job manager actions and run jobs from the deployment managers dmgr console. The deployment manager dmgr console has a Jobs navigation tree option similar to that in the job manager console. The Jobs navigation tree in the job manager console has the following options:

The option selected in the Navigation tree is...


Groups of nodes

We can create groups of nodes containing the nodes you will work with from the job manager (click Jobs | Groups of nodes). A group of nodes can be used as the target of administrative jobs.

When you submit a job, we can select one or more groups from a drop-down menu. The alternative is to type in the name of the node, or use the Find feature to select each node.

Using the Find feature takes several steps. So, even if we do not plan to use multiple nodes as the target of a job, creating a group for each node allows you to select a node rather than typing it in or searching for it.

If you include multiple nodes in the group, beware that all of the nodes must have a common user ID and password. When you submit a job, you only have one place where we can enter the user ID and password.


Submitting a job with the job manager

The job manager provides the following job types:


Example of submitting a job

  1. Start the job manager, and log into the job manager console:

      http://<job_manager_host>:9960/ibm/console

  2. To submit jobs, nodes must already be registered with the job manager. To verify which nodes are registered, expand Jobs in the navigation window, and click Targets. If this is the first time you are using the job manager, you might not see all the nodes displayed. To refresh the view, enter * as the value for Node name, and click Find.

  3. Click Jobs | Submit to select the type of job to submit and then click Next

  4. Select the node on which to run the job.

    We can select the node from a node group using the drop-down menu next to the Groups of nodes option, or we can select specific nodes using the Node names option. Enter the user ID and password for the node that you will run the job against

    To use a specific node, select Target names and either enter the node name and click Add, or click Find.

    Using the Find option opens a new window where we can search and select nodes

    The simplest method of searching is to enter an * in the Node name field, and click Find.

    The list of nodes is shown in the Excluded nodes box. Select the nodes you want, and use the arrow button to move them to the Chosen nodes box. Hold the Shift key down to select multiple nodes, or move them one at a time.

    Click OK. This action returns you to step 2 of the wizard with the node name entered. Click Next to continue the job submit process.

  5. Specify the job parameters.

    The parameters provide the additional information the job needs to perform the task. For example, if you are running a job to start a server, you selected the node in the previous step, but the server name must be entered as a parameter. We can also click Find to search for parameter.

  6. The next step contains fields that specify how and when the job runs and if a notification email is to be sent.

    The fields are:

    Notification The email address specified receives a notification when the job is finished. To use this field, configure a mail provider and mail session.
    Initial availability We can make the job available now (it will run immediately after we have finished with the job submission process), or we can specify a date and time it will be available.
    Expiration Specify an expiration date for the job.
    Job availability interval Repeat job submission at intervals.

    Depending on the selection, you will have an additional field displayed that allows you to choose the days, start and stop time, and so on |

    If you select Make this job available now and Run once, the job runs immediately and the Expiration settings have no meaning. The alternative is to set an Initial availability, Expiration date or duration, and select an interval at which the job will run.

  7. Review the summary and submit the job.

    When a job is submitted from the job manager, the job details are saved in a database local to the job manager. The endpoint (deployment manager or administrative agent) pings the job manager at a predefined interval and fetches jobs that are to be executed. If the job submitted is a wsadmin job, the wsadmin script is executed. Otherwise, a corresponding job handler will execute the necessary admin code.

  8. We can monitor the results through the Job status window.

    Click the Refresh button, in the Status summary column ( ), to update the status. The color in the Status summary field indicates the success or failure of the job.

  9. Click the Job ID to see more information about the job.

The job status is always sent back to the job manager. Clicking the message in the Status column (Succeeded in this case) shows you additional information.

In the event of an error, you will see any messages produced by the job. Additional messages might be available in the logs for the server where the administrative action was to take place.

When you execute a configuration type job (for example, create server) from the job manager to a deployment manager, the configuration is saved if the job is successful. A job that submits a wsadmin script, however, does not save the configuration (the wsadmin script needs to do that).


Windows operating systems

Commands in Windows operating systems have an extension of .bat. It is not necessary to use the extension. Commands are not case sensitive, but parameters and names are case sensitive.

To use a command:

When running command-line tools on Microsoft Windows Vista or later Microsoft operating systems, on Windows Vista, Windows Server 2008, and Windows 7 operating systems, we can install WAS as either Administrator or non-administrator. When it is installed as Administrator, certain operations (such as those involving Windows Services) require Administrator privileges.

To ensure that command-line tools have sufficient privileges, run them as Administrator. When you run these command-line tools from a command prompt, run them from a command prompt window launched by performing the following actions:

  1. Right-click a command prompt shortcut.

  2. Click Run As Administrator.

  3. When you open the command-prompt window as Administrator, an operating-system dialog appears that asks you to continue. Click Continue to proceed.

If we are using a Windows Server Core installation of Windows Server 2008, any WAS commands that require a graphical interface are not supported because a Windows Server Core system does not have a graphical user interface.

Therefore, commands, such as pmt.bat or ifgui.bat, are not supported on that type of Windows Server 2008 installation.


UNIX operating systems

Commands in UNIX operating systems have an extension of .sh and are case sensitive.

To use a command for UNIX operating systems:

  1. Open a command prompt or terminal window.

  2. Change to the directory where the command is, for example, for root users... is:

      /usr/WAS/AppServer/profiles/profile_name/bin

    For non-root users, the directory is:

      user_home/WAS/AppServer/profiles/bin

  3. Enter the command, for example:

      serverStatus.sh -all -username <username> -password <password>


IBM i operating systems

For an IBM i operating system:

  1. From the IBM i command line, start a Qshell session by issuing the STRQSH CL command.

  2. Change to the directory where the command is, for example:

      /QIBM/ProdData/WebSphere/AppServer/V8/ND/profiles/profile_name/bin

  3. Enter the command, for example:

      serverStatus.sh -all -username <username> -password <password>


z/OS operating systems

We can manage application servers on a z/OS system from a UNIX System Services environment:

  1. Enter uss (to switch to the UNIX System Services environment).

  2. Change to the directory where the command is. On z/OS, this directory is always...

      app_server_root/profiles/default

    ...because only the profile name "default" is used in WAS for z/OS.

  3. Enter the command, for example:

      serverStatus.sh -all -username <username> -password <password>


Backup an application server profile

Stop the appserver, and then run... 

$ PROFILE_HOME/bin/manageprofiles.sh -backupProfile  \
                                   -profileName MyServer01  \
                                   -backupFile /opt/WAS/MyServer01_backup.zip


Enable SDK V1.7 64 bit to all profiles of an environment

$ PROFILE_HOME/bin/managesdk.sh -enableProfileAll \
                              -sdkname 1.7_64 \
                              -enableServers 

CWSDK1017I: Profile dmgr_85_01 now enabled to use SDK 1.7_64.  
CWSDK1024I: The node default SDK setting for federated profile MyServer01 has been saved in the master configuration repository.
CWSDK1025I: A synchronization operation is required before configuration changes to federated profile MyServer01 can be used.
CWSDK1017I: Profile MyServer01 now enabled to use SDK 1.7_64.
CWSDK1001I: Successfully performed the requested managesdk task


Synchronize a node using the deployment manager host and SOAP port parameters

$ PROFILE_HOME/bin/syncNode.sh nodename

ADMU0116I: Tool information is being logged in file PROFILE_HOME/logs/syncNode.log
ADMU0128I: Starting tool with the MyServer01 profile ADMU0401I: Begin syncNode operation for node nodename with Deployment Manager dmgrname: 8884
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0402I: The configuration for node nodename has been synchronized with Deployment Manager dmgrname: 8884


Backup the entire configuration of a node

$ PROFILE_HOME/bin/backupConfig.sh /opt/WAS/backup_config.zip 

ADMU0116I: Tool information is being logged in file PROFILE_HOME/logs/backupConfig.log
ADMU0128I: Starting tool with the MyServer01 profile ADMU5001I: Backing up config directory PROFILE_HOME/config to file /opt/WAS/backup_config.zip
ADMU0505I: Servers found in configuration:
ADMU0506I: Server name: nodeagent
ADMU0506I: Server name: MyServer01
ADMU0506I: Server name: MY_ODR_1
ADMU0506I: Server name: MyServer02
ADMU2010I: Stopping all server processes for node nodename
ADMU0512I: Server MyServer01 cannot be reached. It appears to be stopped.
ADMU0512I: Server MY_ODR_1 cannot be reached. It appears to be stopped.
ADMU0512I: Server MyServer02 cannot be reached. It appears to be stopped.
ADMU0512I: Server nodeagent cannot be reached. It appears to be stopped.
.......................................................................
ADMU5002I: 2,014 files successfully backed up