Show TOC

 Configuring Thread Settings for RTC Application Sharing ServerLocate this document in the navigation structure

Use

To optimize performance of the Real-Time Collaboration (RTC) Application Sharing Server, you need to optimize the application thread settings (for ICM and server) of AS Java using the Config Tool (refer to Config Tool ). This topic also discusses additional parameters in the Config Tool on AS Java and Application Sharing Server descriptor file ( web.xml ) that need to be considered.

 

In addition to the optimization settings described in this topic, you can also specify the maximum number of concurrent application sharing sessions (and instant messaging sessions) allowed and also the maximum number of users allowed per session. For more information, see Configuring Maximum Numbers of Sessions and Users Allowed .

Before a new participant can join an existing application sharing session or start a new session, the system first verifies if the maximum number of concurrent sessions or the maximum number of users for that particular session has been reached. If the user is allowed to join the session or start a new one, only then are the thread setting limitations verified. When a session cannot be started or a user cannot participate in an existing session because of the defined limitations, a notification appears on the screen.

 

Procedure

Configure System and Application Thread Settings in AS Java

The number of threads that each machine is capable of supporting depends on the amount of available memory, CPU, and other system resources. You need to conduct a number of performance tests to obtain the correct settings for a specific machine.

To run the RTC Application Sharing Server in an optimal manner, you need to optimize the application following parameters in the Config Tool on AS Java:

  • System thread parameters (under ThreadManager on server only)
  • Application thread parameters (under ApplicationThreadManager on server only)
  • Request queue (RQ) parameters (on server only)
  • Connection manipulator parameters (on dispatcher) only)

 

Note

When optimizing the thread count settings in the AS Java, take into consideration that an individual thread is dedicated to each user running an RTC Application Sharing session. Each thread is maintained for the entire duration of the session; a thread is released when the user ends their participation in the session. For a dedicated machine, we recommend allocating the majority of the application threads to the RTC Application Sharing Server.

For more information about this parameter, see the following documentation:

Configure the RTC Application Sharing Descriptor File (web.xml)

The web.xml file is located at:

Platform Path

UNIX

/usr/sap/<SAP AS Java instance name>/JC<instance_number>/j2ee/cluster/server0/apps/sap.com/com.sap.netweaver.coll.appl.rtc.streamsrv/servlet_jsp/streamingserver/root/WEB-INF/

Windows

\usr\sap\<SAP AS Java instance name>\JC<instance_number>\j2ee\cluster\apps\sap.com\com.sap.netweaver.coll.appl.rtc.streamsrv\servlet_jsp\streamingserver\root\WEB-INF\

 

To specify the runtime allocation and thread count usage, you need to configure the following parameters in the RTC Application Sharing descriptor file, web.xml :

Parameter Default Value Description

ServerMaxSystemThreads

200

Specifies the maximum number of Java EE system threads that can be allocated to the RTC Application Sharing Server.

This number should not be larger than the maximum system thread count defined in the ThreadManager within the Config Tool on AS Java.

ServerMaxSytemThreadsInPercent

50

Specifies the percentage of the maximum system thread count (defined in the ThreadManager within the AS Java) that is allocated to the RTC Application Sharing Server.

ServerMaxClientThreads

200

Specifies the maximum number of Java EE application threads that can be allocated to the RTC Application Sharing Server.

This number should not be larger than the maximum application thread count defined in the ApplicationThreadManager within the Config Tool on AS Java.

ServerMaxClientThreadsInPercent

50

Specifies the percentage of the maximum application thread count (defined in the ApplicationThreadManager within the Config Tool on AS Java) that is allocated to the RTC Application Sharing Server.

Based on the above values, the RTC Application Sharing Server at runtime calculates the actual percentage values ( ServerMaxSystemThreadsInPercent and ServerMaxClientThreadsInPercent ), compares them to one another and then to the fixed values ( ServerMaxSystemThreads and ServerMaxClientThreads ). The lowest number of threads by four-way comparison is then defined as the overall maximum number of threads used by the RTC Application Sharing Server for a given session (the same value is used for both system and applications threads).

For example, if the values in the following table are defined in the RTC Application Sharing web.xml file and the Config Tool on AS Java, the maximum number of system and application threads used by the RTC Application Sharing Server is 100, since this is the lowest value by comparison:

  Max Thread Count in AS Java Max Thread Count in RTC Application Sharing Descriptor File (web.xml)
Fixed value Percentage value

Application thread count

400

400 threads

80% (=320 threads)

System thread count

200

100 threads

80% (=160 threads)