Setting up workload management (WLM)

Why and when to perform this task

WebSphere Application Server for z/OS uses the workload management (WLM) function in z/OS to manage workloads. This section helps you get started and is sufficient to get a functioning WebSphere Application Server for z/OS system.

WebSphere Application Server for z/OS requires that z/OS run workload management in goal mode. If your system runs in compatibility mode, you must implement goal mode. For details on workload management, see z/OS MVS Planning: Workload Management, which is available on the z/OS Internet Library Web site.

In addition to setting up workload management in goal mode, you need to define workload management policies for WebSphere Application Server for z/OS servers and your business application servers. This section discusses specifics for the run-time servers. For details on workload management and business applications, see the assembling applications information in the z/OS view of the WebSphere Application Server information center, which you can access via the WebSphere Application Server for z/OS library Web site.

To get started, you do not need to define special classification rules and work qualifiers, but you might want to do this for your production system.

Note: After you apply service level W500104 (PTF UQ79825), you might want to set up a rule to combat performance problems related to post-install. See Workload management (WLM) tuning tips for z/OS for more information.

Each J2EE Application Server must have a WLM application environment so it can start servant regions. The application environment name is specified as the "cluster transition name" in the Customization Dialog.

WebSphere Application Server for z/OS servers (with the exception of the location service daemon and node agent) have a controller and one or more servants. The regions are started by the respective start procedures.

Tip: If you are running z/OS V1.2 or above with the WLM-DAE support PTF (APAR OW54622), you do not need to continue.

You have to start the controllers for the WebSphere Application Server for z/OS servers yourself. This in turn starts the location service daemon. Workload manager dynamically starts the servants as work requests arrive. Thus, you must create WLM application environments that name servant start procedures to start. For example, specify BBO5ASR as the start procedure name that workload management starts for the server.

Each new server that you create for a business application also must be defined to workload management. For more information, see the assembling applications information in the z/OS view of the WebSphere Application Server information center, which you can access via the WebSphere Application Server for z/OS library Web site.

Steps for this task

  1. Use the ISPF application IWMARIN0 to define WLM application environments.

    Tip: If you are running z/OS V1.2 or above with the WLM-DAE support PTF (APAR OW54622), you can skip this step.

    During the customization process, you will be instructed to create a WLM application environment. This section shows how to use the WLM ISPF Dialog to accomplish this.

    You must have access to the IWMARIN0 application and be able to update the workload management policies to complete this process.

    Use the ISPF application IWMARIN0 to define WLM application environments according to Default server values for WebSphere Application Server for z/OS V5.


Related concepts
Workload management (WLM)
Related reference
Workload management (WLM) tuning tips for z/OS
Default server values for WebSphere Application Server for z/OS V5



Searchable topic ID:   tinswlm
Last updated: Jun 21, 2007 9:56:50 PM CDT    WebSphere Application Server for z/OS, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/tins_wlm.html

Library | Support | Terms of Use | Feedback