SAP WAS Thread Types Test

For each type of thread executing on the target SAP WAS Application Server, this test reports the number of threads that were created and the number of threads that were in Processing and Waiting state. By closely analyzing the threads in each state, administrators can figure out which type of thread is frequently in the Processing and Waiting state and identify those resources/applications that are extensively used.

Target of the test : A SAP NetWeaver Application Server

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for each of the Dispatchers and each of the configured server processes of the SAP Web AS.

Configurable parameters for the test
Parameter	Description
Test period	How often should the test be executed
Host	Specify the server for which the test is to be configured.
Port	The port number at which the specified server listens.
WSDL Port	This test uses the SAPControl web service to pull metrics on application and service status. To enable the test to communicate with the web service, you need to configure the test with the port number of the web service. Therefore, specify the port number of the SAPControl web service against WSDL Port. To determine the exact port number of the SAPControl web service, you can look up the etc/services file on the SAP WAS being monitored. If the port number is not declared in the etc/services file, you can specify the default port number of the web service against WSDL Port. If the web service is not SSL-enabled, then the default port number of the web service will be: 5<NR>13. Similarly, if the web service is SSL-enabled, then the default port number of the web service will be: 5<NR>14. <NR> in the port number refers to the system number of the SAP server being monitored. The system number is an indicator of the TCP/IP port at which the SAP server listens. For example, for a server that listens at port 3200, the system number will be ‘00’. Similarly, if the SAP server port is 3201, the system number will have to be specified as ‘01’. Accordingly, the default port number of an SSL-enabled SAPControl web service will be 50014 , if the system number is 00, or 50114, if the system number is 01.
OS Username and OS Password	To enable the test to access the SAPControl web service and determine component state, you need to configure the OS Username and OS Password parameters of the test with the credentials (i.e., name and password) of an OS user, who fulfills one of the following conditions: The name of the OS user should be declared using the service\admin_users profile parameter; (OR) The name of the user group to which the OS user belongs should be declared using the service\admin_groups profile parameter; (OR) The OS user should have the permission to execute the sapstartsrv executable
Confirm Password	Confirm the OS Password by retyping it here.
SSL	Set this flag to Yes, if the SAPControl web service is SSL-enabled. Set this flag to No, if the SAPControl web service is not SSL-enabled.
Maximum Parallel Threads Per Resource	Specify a list of maximum threads for each resource or application that can be available in parallel for each thread type that is auto-discovered by this test separated by a forward slash (/). This parameter should be specified in the following format: Thread type1 = <Pattern>1/Threadtype2 = <Pattern2>/... where Pattern should be specified as a comma-separated list of threads that can be processed on each server instance or the count of threads that are common to all server instances in the target environment. If there are 4 server instances, then, your Pattern specification can be 10,20,20,5. For example, you can sepcify this parameter as: HTTP Worker=10,20,20,5/Application=10
Maximum Parallel Resources Per Thread Type	Specify a list of maximum resources or applications that can be available in parallel for each thread type that is auto-discovered by this test separated by a forward slash (/).This parameter should be specified in the following format: Thread type1 = <Pattern>1/Threaddtype2 = <Pattern2>/... where Pattern should be specified as a comma-separated list of threads that can be processed on each server instance or the count of threads that are commin to all server instances in the target environment. If there are 4 server instances, then, your Pattern specification can be 10, 20,20,5. For example, you can sepcify this parameter as: HTTP Worker=10,20,20,5/Application=10
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Created threads	Indicates the number of threads that were created with this thread type.	Number	Compare the value of this measure across thread types to identify the thread type for which maximum number of threads were created. If there are multiple threads created for a thread type, then, the threads for other services/components may not be readily available and hence the performance of the system will be affected. Administrators may therefore fine-tune the threads and optimize the performance of the system.
Processing threads	Indicates the number of threads that are in Processing state for this thread type.	Number
Waiting threads	Indicates the number of threads that are in Waiting state for this thread type.	Number	Compare the value of this measure across thread types to identify the threads of which thread type are waiting frequently for a task or I/O operation.
Not-set threads	Indicates the threads that are in Not set state for this thread type.	Number	Compare the value of this measure to figure out the threads of which thread type are created but not yet used to the maximum.
Percentage processing threads	Indicates the percentage of threads that are in Processing state for this thread type.	Percent	Use the detailed diagnosis of this measure to identify the threads that are in Processing state for a prolonged duration.
Percentage waiting threads	Indicates the percentage of threads that are in Waiting state for this thread type.	Percent
Maximum threads	Indicates the maximum number of threads of this type that are available for all resources.	Number	This measure will appear only if the Maximum Parallel Threads Per Resource and Maximum Parallel Resources Per Thread Type parameters are configured.
Percentage created threads	Indicates the percentage of threads that can be created with this thread type.		This measure will appear only if the Maximum Parallel Threads Per Resource and Maximum Parallel Resources Per Thread Type parameters are configured. A consistent/gradual increase in the value of this measure may indicate that several threads are hanging on a resource or the application resources are being extensively used. To maintian the value of this measure optimally, administrators can increase the count specified against the FCAServerThreadCount parameter. Note that increasing this value may impact the performance of the system.