Adding Sametime awareness through the Sametime server
If an HCL Sametime® server is configured in your enterprise and the Profiles application is deployed, you can enable presence awareness and simple chats in HCL Connections.
The following software must be enabled before you add presence awareness to HCL Connections:
- Sametime 12.0 server or later, with Web client integration enabled.
- See the HCL Sametime article on Integrating with other applications for more information on enabling the web client interface.
Complete the following procedures before enabling awareness.
- Enable single sign-on between the Sametime server environment and the HCL Connections server using Lightweight Third Party Authentication. For more information, see the Sametime 12 article Setting up SSO using LTPA.
When you enable presence awareness by using the Sametime Proxy server, a person's online status is indicated by a set of icons and an associated status message that is available from the person's profile and business card. Presence awareness tells you whether the person is available to chat, busy in a meeting, or away from their computer. In addition to seeing a person's availability, you can carry on a chat with that person even when no Sametime client is installed.
Start the wsadmin client from the following directory of the system where you installed the deployment manager:
Find more information about app_server_root and dm_profile_root in Directory path conventions.
You must start the client from this directory or subsequent commands that you try to run will not execute properly. For more information, see the Starting the wsadmin client topic.
Use the wsadmin client to access and check out the HCL Connections extension configuration files.
Enter the following command to load the HCL Connections configuration file:
If you are prompted to specify a service to connect to, type 1 to select the first node in the list. Most commands can run on any node. If the command writes or reads information to or from a file by using a local file path, you must select the node where the file is stored. This information is not used by the wsadmin client when you are making configuration changes.
Enter the following command to check out the LotusConnections-config.xml file:
working_directory is the temporary working directory to which the configuration XML and XSD files are copied and are stored while you change them. Use forward slashes to separate directories in the file path, even if you are using the Microsoft Windows operating system.
Linux: The directory must grant write permissions or the command does not run successfully.
cell_name is the name of the WebSphere® Application Server cell that hosts the IBM Connections application. This argument is case-sensitive, so type it with care. If you do not know the cell name, type the following command while in the wsadmin command processor:print AdminControl.getCell() For example:
- Microsoft Windows: LCConfigService.checkOutConfig("c:/temp","foo01Cell01")
From the directory you specified as the working directory in the previous step, open the LotusConnections-config.xml file in a text editor, and then find the
<sloc:serviceReference enabled="false" isConnectClient="false" serviceName="sametimeProxy" ssl_enabled="false"> <sloc:href><sloc:hrefPathPrefix/> <sloc:static href="admin_replace" ssl_href="admin_replace"/> <sloc:interService href="admin_replace"/> </sloc:href> </sloc:serviceReference>
Specify the attributes according to the following example:
<sloc:serviceReference enabled="true" isConnectClient="false" serviceName="sametimeProxy" ssl_enabled="true"> <sloc:href><sloc:hrefPathPrefix/> <sloc:static href="http://sametimeProxyServer.enterprise.example.com" ssl_href="https://sametimeProxyServer.enterprise.example.com:443"/> <sloc:interService href="https://sametimeProxyServer.enterprise.example.com:443"/> </sloc:href> </sloc:serviceReference>
sloc:serviceReference enabled="true"displays the Sametime action bar in Connections and connects to Sametime using the specified Sametime Proxy server.
ssl_enabled="true"connects to the Sametime proxy server on the secure port.
isConnectClient="false"leave this as false, it forces the use of the Sametime Proxy Server.
If your Connections environment is configured to a reverse proxy but the Sametime server is not, or if
dynamicHostsis enabled in the LotusConnections-config.xml, add the isExternal attribute to the configuration as shown in following example. The isExternal attribute is set so that the Sametime proxy server URLs are not overwritten by the dynamic host URLs.
<sloc:serviceReference enabled="true" isConnectClient="false" serviceName="sametimeProxy" ssl_enabled="true"> <sloc:href> <sloc:hrefPathPrefix/> <sloc:static href="http://sametimeProxyServer.enterprise.example.com" ssl_href="https://sametimeProxyServer.enterprise.example.com:443" isExternal="true"/> <sloc:interService href="https://sametimeProxyServer.enterprise.example.com:443"/> </sloc:href> </sloc:serviceReference>
Save and close the LotusConnections-config.xml file.
To check in the changed configuration files, use the following command:
Type the following command to deploy the changes:
To exit the wsadmin client, type
exitat the prompt.
Stop and restart all of the HCL Connections application servers.
Confirm that this procedure worked by accessing one of the Connections applications, and then opening a person's business card. It might take a few seconds for the person's presence information to display the first time. If you can start a chat with the person, then enabling awareness through the proxy server was successfully completed.
- If you are using the HCL Connections Component pack, then you can also enable an Appregistry Extension which will include a chat icon for all people that have been added to your Important To Me navigation bar. For more information, see the Connections Sametime chat extension.
- You can ignore the following configuration in
profiles-config.xml, as it is not used for Sametime 12.Make sure to leave enabled as
<sametimeAwareness enabled="false" href="http://localhost:59449/stwebapi/" ssl_href="http://localhost:59449/stwebapi/" sametimeInputType="uid" />
Parent topic: Customizing the deployment