Setting Application Sharing Server Parameters
(RTC) 
Use
Before activating the runtime application sharing capabilities of Real-Time Collaboration in the portal, you need to configure the Application Sharing Server settings.
This procedure is mandatory only if you intend to integrate the application sharing capabilities of RTC. If you intend to integrate only the instant messaging capabilities of RTC, then you may skip this procedure.
If you are not
integrating the application sharing capabilities of RTC,
you may disable the Application Sharing Server. See 
Enabling / Disabling
the Application Sharing Server (RTC).
Prerequisites
· You have installed the SAP NetWeaver Collaboration component.
· You have access to the Collaboration Launch Pad Configuration component in the portal. By default, this component is assigned to the Content Administration role.
Procedure
...
...
1. In the portal, navigate to Content Administration ® Collaboration Content ® Collaboration Launch Pad Configuration. Then, under Related Links, choose Configure Real-Time Collaboration ® Application Sharing.
Alternatively, you can navigate to System Administration ® System Configuration ® Knowledge Management ® Configuration. Then, under Folders, navigate to Collaboration ® Real-Time Collaboration ® Application Sharing.
2. Configure the following configuration objects, as needed. To edit an existing configuration object, select its checkbox, and then click Edit.
§ If the following configuration objects do not exist, you need to create them. The name of each configuration object must be defined exactly as shown in the table below; names are case-sensitive. To create a configuration object, click New.
§
Certain parameters
are tagged as advanced parameters. To display advanced parameters with the
basic parameters, you need to switch the view of the configuration editor. See
Normal and
Advanced View in the Configuration iView.
Configuration object (name) |
Description (value) |
ServerName |
Enter the full qualified host name of the Application Sharing Server. If Application Sharing Server is running in a clustered environment, enter the full qualified host name of the server acting as the entry point to the cluster. For example: pluto.sap.com. |
ServerPath |
This configuration object specifies the path to the host servlet providing application sharing capabilities. Enter the following value: streamingserver/servlet/streamingserver
Do NOT change this value. |
ServerPort |
Specify the port number of the Application Sharing Server. If the Application Sharing Server is running in a clustered environment, enter the port number of the server acting as the entry point to the cluster. |
SecureMode |
Specify the secure mode in which the Application Sharing Server sends data. RTC uses a binary format that is compressed when sending streamed data during application sharing sessions. Data streaming through the Application Sharing Server is possible in SSL or non-SSL mode. The secure mode of the portal itself does not require that the Application Sharing Server runs in the same mode—if the portal is running in SSL mode (https) the RTC can stream data in non-SSL mode (http) or vice versa.
Generally, if your portal is running in SSL mode, you should set RTC to stream data in the secure SSL mode, as well. Note that the usage of the SSL may downgrade performance of a collaborative session with application sharing. Enter one of the following values to specify the appropriate secure mode: · 1 (for non-SSL mode) · 3 (for SSL mode) |
Version |
Specify the version number of the Real-Time Collaboration ActiveX control that should be running on portal client machines. This ActiveX control is required for all portal users intending to run application sharing in a collaboration session. This property ensures that all portal clients use the same and most up-to-date ActiveX version when they participate in an application sharing session. If they do not have the same version defined by this property they will automatically be given the current version. To determine the version of the current RTC ActiveX control: ... 1. On the portal machine, locate the exp.cab file in the following folder: \usr\sap\<SAP Web AS Java instance name>\JC<instance_number>j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\portalapps\com.sap.netweaver.coll.appl.ui.rtc\activeX 2. Open the CAB file and locate the exp.inf file within it. 3. Open this file in any text editor. 4. Locate the FileVersion attribute. The last set of digits denotes the ActiveX version. For example: If the attribute is FileVersion=1, 0, 0, 1730, then the version you enter for the Version value should be 1730. 5. Close the exp.inf file. |
ClusterLogonGroupName |
For more
information, see |
ClusterGroupSeparator |
For more
information, see |
