Configuring the IBM Sametime plug-in

IBM® Sametime® integration does not require a thick client installation on the user desktop. Chat services are connected through a single sign-on (SSO) configuration in WebSphere® Application Server.

To configure the IBM Sametime plug-in:

1. Install the AjaxProxy.war file as a web application on the WebSphere Application Server that is running IBM Content Navigator services. Use AjaxProxy as the context root. The AjaxProxy.war file is in the directory WAS_installdir\AppServer\installableApps.
2. Edit the proxy-config.xml file that is included in the AjaxProxy.war with the following changes. The proxy-config.xml file is in the directory: WAS_installdir\Appserver\profiles\AppSrv01\installedApps\WASNode01Cell\AjaxProxy_war.ear\AjaxProxy.war\WEB-INF.
   1. For security, remove the default mapping for any URL by removing or commenting out the following two lines:

      <proxy:mapping contextpath="/http/*"/>
      <proxy:mapping contextpath="/https/*"/>

   2. Add the following proxy mapping to the Sametime server URL. Replace 9082 with the port number of your Sametime server.

      <proxy:mapping contextpath="/http/SametimeServer.yourCompany.com:9082/*">

   3. Add the following lines of code to allow forwarding only for the Sametime server. Replace the URL with the URL of your Sametime server. This code sets the proxy mapping to pass cookies and headers, and to maintain states.

      <proxy:policy acf="none" basic-auth-support="true" url=
      "http://SametimeServer.yourCompany.com:9082*">
          <proxy:actions>
              <proxy:method>GET</proxy:method>
              <proxy:method>HEAD</proxy:method>
              <proxy:method>POST</proxy:method>
              <proxy:method>PUT</proxy:method>
              <proxy:method>DELETE</proxy:method>
          </proxy:actions>
          <proxy:cookies>
              <proxy:cookie>LtpaToken</proxy:cookie>
              <proxy:cookie>LtpaToken2</proxy:cookie>
              <proxy:cookie>loginName</proxy:cookie>
              <proxy:cookie>sid</proxy:cookie>
              <proxy:cookie>selectorMap</proxy:cookie>
              <proxy:cookie>headUpdaterWindowName</proxy:cookie>
              <proxy:cookie>UnicaNIODID</proxy:cookie>
              <proxy:cookie>x-Q-App-Context</proxy:cookie>
              <proxy:cookie>flushedId</proxy:cookie>
              <proxy:cookie>JSESSIONID</proxy:cookie>
          </proxy:cookies>
          <proxy:headers>
              <proxy:header>User-Agent</proxy:header>
              <proxy:header>Accept*</proxy:header>
              <proxy:header>Content*</proxy:header>
              <proxy:header>Authorization*</proxy:header>
              <proxy:header>X-Method-Override</proxy:header>
              <proxy:header>Set-Cookie</proxy:header>
              <proxy:header>If-Modified-Since</proxy:header>
              <proxy:header>If-None-Match</proxy:header>
              <proxy:header>Rtc4web-Nonce</proxy:header>
              <proxy:header>Host</proxy:header>
              <proxy:header>Accept</proxy:header>
              <proxy:header>Keep-Alive</proxy:header>
              <proxy:header>Connection</proxy:header>
              <proxy:header>X-Requested-With</proxy:header>
              <proxy:header>Referer</proxy:header>
              <proxy:header>Cookie</proxy:header>
          </proxy:headers>
      </proxy:policy>

   4. If the IP address of the Sametime server is required, add another copy of the preceding code and replace SametimeServer.yourCompany.com:9082 with the IP address of your Sametime server and its port number.
3. Use the same single-sign-on (SSO) setting for both the IBM Content Navigator server and the Content Engine or Content Platform Engine server. You can find the setting on the Content Engine or Content Platform Engine server under Global security/Single sign-on (SSO).
4. In the IBM Content Navigator administration tool, click Plug-ins > New Plug-in.
5. Load the Profile plug-in in one of the following ways.
   • Enter the URL in the following sample format: http://host_name:port_number/ECMClient_installdir/plugins/ProfilePlugin.jar.
   • Enter the path to the file that is installed on the server, for example:
     • Microsoft Windows: C:\Program Files\IBM\ECMClient\plugins\ProfilePlugin.jar
     • Linux or AIX®: /opt/IBM/ECMClient/plugins/ProfilePlugin.jar
     The ECMClient folder is the IBM Content Navigator installation directory.
6. After the ProfilePlugin.jar file is loaded, configure the following settings:
   • Set the IBM Sametime Proxy Server URL to your IBM Sametime server URL. Specify the fully qualified URL.
   • Set the Context root for the Ajax proxy server to the IBM Ajax proxy service URL.
   • Click Test to verify that the proxy-config.xml file is correctly configured. The profile plug-in tests the configuration by fetching a JavaScript source on the IBM Sametime server through the Ajax proxy. If the test is successful, the proxy server is set up correctly. If the test fails, ensure that you are using a fully qualified URL, not an IP address, or non-qualified URL.
   • Select one of the following options for Sametime proxy server polling:
     • Disabled
     • Display Sametime status automatically
     • Display Sametime status after a click action. This option displays the user's status only when you click the user's name.
   • Select the Display Name check box to show the display name instead of the login name.
7. Click Save and Close.
8. Refresh your web browser.