!--a11y-->
Configuration of Real-Time
Collaboration 
Before you can offer Real-Time Collaboration (RTC) services to portal end users, you need to first perform a number of configuration tasks specific to the RTC components.
These tasks are documented in the Configuring Real-Time Collaboration section.

As part of your long-term maintenance process, you should check these settings over time and adjust them, if necessary.
· You have installed the SAP NetWeaver Collaboration component.
· You have authorization to make modifications in the J2EE Engine settings.
· The portal is operational and you have administrative access to the RTC configuration services.
You need to perform the following configurations activities in order to prepare the RTC services for runtime usage by portal end users:
Activity |
Description |
Configuring J2EE Engine thread settings and Application Sharing server descriptor file |
You need to configure the system and application thread settings in the J2EE Engine to optimize performance of the RTC-based Application Sharing server. You also need to configure additional parameters in the Application Sharing server descriptor file (web.xml) to specify how the total thread count is used and allocated. For detailed information, see Configuring Thread Settings for Application Sharing Server (RTC). |
Configuring the Application sharing settings |
You need to configure the Application Sharing server settings before you can activate the runtime application sharing capabilities of RTC in the portal. This set of configuration tasks is performed directly in the portal. For detailed information, see Configuring the Application Sharing Server. |
Configuring the polling mechanism |
You can configure the polling policy of the Real-Time Messaging Framework (RTMF) to best suit your environment. The polling policy determines at which frequency (the polling interval) the RTMF sends polling requests between portal server and portal client. The ability to adjust the polling interval dynamically, based on the number of concurrent users logged on to the portal at any given time, enables you to limit the load generated by the polling mechanism. Thus, giving you more control over factors that affect overall system performance. This set of configuration tasks is performed directly in the portal. For detailed information, see Configuring the Polling Mechanism. |
Configuring the maximum number of concurrent sessions allowed and the maximum number users allowed per session |
Another way of improving system performance by limiting load generated by RTC collaborative sessions is to do the following: · Limit the maximum number of instant messaging and application sharing session that can run concurrently. · Limit the maximum number of users that are allowed per instant messaging and application sharing session. For detailed
information, see |
