Technotes: Cognos BI for z/os with WebSphere Application Serverfor z/os worker threads

Size: px

Start display at page:

Download "Technotes: Cognos BI for z/os with WebSphere Application Serverfor z/os worker threads"

Augustine Turner
5 years ago
Views:

1 Technotes: Cognos BI for z/os with WebSphere Application Serverfor z/os worker threads Cognos BI for z/os and WebSphere for z/os worker thread utilization Cognos for z/os will utilize a single WebSphere Application Server for z/os servant region per control region in its z/os configuration. Total WebSphere Application Server worker threads available in this application server configuration will be limited by the maximum number of worker threads allowed for a single servant region. APAR PM24633 documents a change in WebSphere Application Server for z/os which increases the limit for the variable servant_region_custom_thread_count from 100 to 500. This is for customer applications that run in 64-bit mode and will allow up to 500 worker threads to be created in a single servant region. Customers should consider the total number of worker threads a Cognos application may require. A suggested planning value is 2.5 threads per concurrent Cognos user or 500. Overview WebSphere Application Server worker thread: Worker threads are regular WebSphere Application Server threads that specially register with z/os Workload Management (WLM) as work receivers. The worker thread pool is installation defined, but static for each WebSphere Application Server startup. The number of worker threads governs the maximum number of concurrent requests that z/os Workload Management (WLM) receives from a WebSphere Application Server servant. The number of threads allocated to this pool is governed by an external object known as the Object Request Broker (ORB) Workload profile which may have one of five possible values: ISOLATE - number of threads is 1. Specifies that the servants are restricted to a single application thread. Use ISOLATE to ensure that concurrently dispatched applications do not run in the same servant. Two requests processed in the same servant can cause one request to corrupt another. IOBOUND - MIN(30, MAX(5,(Number of CPUs*3))) This is the default value. Specifies more threads in applications that perform I/O-intensive processing on the z/os operating system. The calculation of the thread number is based on the number of CPUs. IOBOUND is used by most applications that have a balance of CPU intensive and remote operation calls. A batch like application is an example that uses the IOBOUND profile. CPUBOUND - MAX((Number of CPUs-1),3) Specifies that the application performs processor-intensive operations on the z/os operating system, and therefore, would not benefit from more threads than 1

2 the number of CPUs. The calculation of the thread number is based on the number of CPUs. Use the CPUBOUND profile setting in CPU intensive applications, like compute-intensive (CI) jobs, XML parsing and XML document construction, where the vast majority of the application response time is spent using the CPU. LONGWAIT - Number of threads is 40 Specifies more threads than IOBOUND for application processing. LONGWAIT spends most of its time waiting for network or remote operations to complete. Use this setting when the application makes frequent calls to another application system, like Customer Information Control System (CICS) screen scraper applications, but does not do much of its own processing CUSTOM - User defined Specifies that the number of servant application threads is determined by the value that is specified for the servant_region_custom_thread_count server custom property. The minimum number of application threads that can be defined for this custom property is 1. The maximum number of application threads that can be specified is 500 with APAR PM

Procedure to configure the worker threads: Configuring or changing the worker threads may be done via the WebSphere Application Server administrative console. 1.

3 Procedure to configure the worker threads: Configuring or changing the worker threads may be done via the WebSphere Application Server administrative console. 1. To select CUSTOM worker threads After login to the console, in the left most panel, click Servers > Server Types > WebSphere application servers > click your_server_name (middle panel) --> Container services (middle panel, top right) > ORB service --> z/os additional settings --> select CUSTOM under Workload profile > click Apply at the bottom of the screen > click Save at the top of the screen. 3

4 4

type servant_region_custom_thread_count > type number for Value

5 2. To initially define the custom worker thread value Select Environment > WebSphere variables > select New (near Preferences) --> type servant_region_custom_thread_count > type number for Value (example: 500) > click Apply at the bottom of the screen > click Save at the top screen. 5

6 3. To change worker thread value Select Environment > WebSphere variables > click (not check) variable servant_region_custom_thread_count --> type number (example: 200) > click Apply at the bottom of the screen > click Save at the top of the screen. 6

Documents references: 1) http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r1m1/index.jsp? topic=/com.ibm.websphere.gridmgr.

7 Documents references: 1) topic=/com.ibm.websphere.gridmgr.doc/scheduler/tzosthreads.html 2) 3) 7

Workload Classification in WebSphere XD Compute Grid on z/os V.8

Workload Classification in WebSphere XD Compute Grid on z/os V.8 This document describes the mechanisms for classifying batch jobs running in WebSphere XD Compute Grid Version 8 on z/os. There are actually