Working with the job manager
A job manager process is managed in the same manner as an application server process.
The process name is jobmgr.
Start and stop the job manager
To view the status of the jobmgr...
-
PROFILE_ROOT/bin/serverStatus.sh -all
To start a job manager...
-
PROFILE_ROOT/bin/startServer.sh jobmgr
To stop a job manager...
-
PROFILE_ROOT/bin/stopServer.sh jobmgr
Job manager configuration settings
To view the job manager from the dmgr console, click System administration | Job manager. You have two pages available, the Runtime tab and the Configuration tab.
Job manager Configuration tab
We can stop your job manager process from this window by clicking the Stop button.
The two options in this window to note are:
- Java SDKs
View and chose the required version of SDKs for the deployment manager process. WAS V8.5 lets you select between Java SDK versions 1.6 and 1.7, both of them available for 32 and 64-bits systems. To be able to select between Java SDK versions 1.6 and 1.7, install both versions first. The default version selected when installing is Java SDK 1.6. If both versions are installed on your system, we can chose one of them and set it as default by clicking the Make Default button. Save your changes and restart the deployment manager process to use the newly selected JAVA SDK version.
- Ports
Select the Ports link to view and manage the ports the job manager uses.
Job manager Runtime tab
The dmgr console contains a Runtime tab for the job manager. To view the Runtime tab, click System administration | Job manager and then click the Runtime tab at the top of the page.
The state is Started because otherwise we cannot access the dmgr console. We can use the Process ID information to monitor the job manager process from your operating system.
The Product Information link is the only link in the window panel. Selecting Product Information opens a new page that provides information about the level of code running on the job manager system. This page provides links for more detailed information, including the installation history for the product and maintenance.
Product information is stored as XML files in...
-
INSTALL_ROOT/properties/version/
...and can be viewed with the dmgr console.
To monitor the state of your job manager environment, use the information provided by logs and traces. We can use either the basic mode for logging and tracing or the HPEL mode.
Basic mode for logging and tracing
This logging and tracing mode lets you monitor the environment using the following logs:
| JVM logs | SystemOut.log
Systemerr.log | Troubleshooting | Logs and trace | jobmgr | JVM Logs | Runtime tab | View
Use the Configuration tab to configure the file paths, file names, file formatting, log rotation, and size. |
| Diagnostic trace service log | trace.log | Troubleshooting | Logs and trace | jobmgr | Diagnostic trace service | Runtime tab | View
Use the Configuration tab to configure the file paths, file names, file formatting, and size. |
| Process logs | native_stdout.log
native_stderr.log | Troubleshooting | Logs and trace | jobmgr | Process logs | Runtime tab | View |
| IBM service Logs | activity.log. | Troubleshooting | Logs and trace | jobmgr | IBM Service Logs | Configuration tab
Has be enabled first. You have the option to enable the correlation ID that can be used to correlate activity to a particular client request or to correlate activities on multiple application servers, if applicable. |
| NCSA access and HTTP error logs | http_access.log
http_error.log | Both have to be enabled first. To enable these logs...
|
High Performance Extensible Logging mode for logging and tracing
If the environment allows, IBM recommends switching to HPEL.To enable HPEL mode:
- Click...
-
Troubleshooting | Logs and trace | jobmgr | Switch to HPEL Mode button.
- Save the changes and then restart the job manager server process.
- Log back into the dmgr console.
- Click Troubleshooting | Logs and trace | jobmgr
The window for logging and tracing the jobmgr process in HPEL mode is different from the basic mode. The HPEL mode includes two sections:
- General Properties that allow you to configure the HPEL logging, trace, and text log.
- Related Items that allow you to work with the logs.