The Real-Time Collaboration (RTC) Application Sharing Server handles the flow of data between portal users collaborating through the RTC-based application sharing feature.
RTC application sharing allows users to share their Windows desktop or individual applications with other portal users in real time. Remote users can interact directly with the shared desktop or application as if they were sitting at the host's machine.
This topic describes the one-time and periodical administrative tasks for fully implementing application sharing functionality in the portal while running the RTC Application Sharing Server as a standalone engine.
These steps are valid if you installed RTC Application Sharing Server as a standalone engine or are using the default server installed on the portal host.
The RTC Application Sharing Server is automatically installed with usage type EP on the portal host. In a cluster environment, the load generated by the RTC Application Sharing Server is replicated to all instances of the cluster, thus generating load on the hosts of the dialog instances.
If you do
not intend to use the installed RTC Application Sharing Server, you can
disable it. See Enabling /
Disabling the Application Sharing Server (RTC).
For test or demo purposes, you can run the standard RTC Application Sharing Server on the portal machine; however, for productive use it is recommended that you install server as standalone engine on a dedicated host using SAPinst. By removing RTC Application Sharing Server traffic from the portal host, you reduce the networking and J2EE demands that it would generate on that machine; thus improving the overall performance of the portal.
You use the following tools to administer the RTC Application Sharing Server:
· Application Sharing configuration component (portal-based)
· J2EE Engine Config Tool
· J2EE Engine Visual Administrator
· Application Sharing Server Monitor
Details for launching these tools are described in the relevant documentation references for each applicable task mentioned below.
· You have installed usage type EP.
· You have installed RTC Application Sharing Server as standalone engine.
The Java Application Server (AS-Java) is also installed when you install RTC Application Sharing Server as a standalone engine.
The table below lists the most important administration tasks:
Task |
Detailed Information |
Define the connection on the portal host to the new standalone RTC Application Sharing Server. |
|
Define general parameters for the Application Sharing Server.* |
|
Define specific parameters for running Application Sharing Server in a clustered environment* (optional). |
See |
Configure J2EE Engine system and application thread settings.* |
See |
Configure browser settings on client machines to accept the RTC ActiveX control. |
See |
*As part of your long-term maintenance process, you should periodically check the settings and adjust them, if necessary.
The following tasks must be done periodically:
Task |
Detailed Information |
Monitor the Application Sharing Server to verify the Application Sharing Server configuration at setup, and to subsequently troubleshoot any problems that may occur during application sharing. |