WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile

244 WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile

7.3 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.

7.3.1 Starting and stopping the job manager

To view the status of the jobmgr, run the following command:

<profile_root_path>/bin/serverStatus.sh(bat) -all

To start a job manager, run the following command:

<profile_root_path>/bin/startServer.sh(bat) jobmgr

To stop a job manager, run the following command:

<profile_root_path>/bin/stopServer.sh(bat) jobmgr

7.3.2 Job manager configuration settings

To view the job manager from the administrative console, click System administration 

Job manager. You have two pages available, the Runtime tab and the Configuration tab.

Figure 7-7 shows the Configuration tab.

Figure 7-7 Job manager configuration tab

Chapter 7. Administration of WebSphere processes 245

Job manager Configuration tab

You 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

This option lets you view and chose the required version of SDKs for your deployment

manager process. WebSphere Application Server 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, you must install both versions first. The

default version that is selected when installing is Java SDK 1.6. If both versions are

installed on your system, you 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 that the job manager uses.

Job manager Runtime tab

The administrative 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. Figure 7-8 shows the Runtime tab.

Figure 7-8 Job manager Runtime tab

The state is Started because otherwise you cannot access the administrative console. You

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 the install_root/properties/version/ folder

and can be viewed with the administrative console, as shown in Figure 7-9 on page 246.

246 WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile

Figure 7-9 Product information

Monitoring your job manager environment

To monitor the state of your job manager environment, use the information provided by logs

and traces. You can use either the basic mode for logging and tracing or the High

Performance Extensible Logging (HPEL) mode. To find more information about the

differences between these two modes refer to the information center at the following website:

http://pic.dhe.ibm.com/infocenter/wasinfo/v8r5/topic/com.ibm.websphere.nd.multipla

tform.doc/ae/ctrb_HPELCompat.html?resultof=%22%48%50%45%4c%22%20%22%68%70%65%6c%22

%20

Basic mode for logging and tracing

This logging and tracing mode lets you monitor your environment using the following logs:

 JVM logs (SystemOut.log and Systemerr.log): To access these logs, use the

administrative console, and click Troubleshooting  Logs and trace  jobmgr  JVM

Logs. Click the Runtime tab, and click the View button beside the System.out or

System.err file paths. Use the Configuration tab to configure the file paths, file names, file

formatting, log rotation, and size.

 Diagnostic trace service log (trace.log): To access this log, use the administrative

console, and click Troubleshooting  Logs and trace  jobmgr  Diagnostic trace

service. Click the Runtime tab, and click the View button beside the trace.log file path.

Use the Configuration tab to configure the file paths, file names, file formatting, and size.

 Process logs (native_stdout.log and native_stderr.log): To access this log, use the

administrative console, and click Troubleshooting  Logs and trace  jobmgr 

Process logs. Click the Runtime tab, and click the View button beside the Stdout or

Stderr file paths.

 IBM service Logs (activity.log), which has to be enabled first: To access this log, use

the administrative console, and click Troubleshooting  Logs and trace  jobmgr 

IBM Service Logs and then click the Configuration tab.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.