Linking applicationsYou can manually link IBM Connections applications, allowing them to share information and inter-application navigation.
Before you beginA built-in script can detect IBM Connections applications that are already installed, and modify the LotusConnections-config.xml file in each WAS profile where the application is installed to keep them all in sync. You might need to manually link applications in any of the following circumstances:
- If any of the URLs for the applications change, the URLs in the LotusConnections-config.xml file must be updated
- If you install a reverse proxy, the URLs in the LotusConnections-config.xml file must be updated to include the proxy
- After installation, if you enable or disable components such as the business card, Common directory services, or virus scanning, you might need to modify the LotusConnections-config.xml
- If you decide to use a customized header, footer, or CSS files, update the Style element
About this taskIBM Connections applications use a WAS cell-level configuration file, called LotusConnections-config.xml, to retrieve information about available applications.
When the applications are deployed within a single WAS cell, they share the same configuration file. However, when applications are deployed in different cells, they need their own configuration files. The installation wizard automatically creates the necessary configuration. However, you can also do this manually by editing each configuration file.
The LotusConnections-config.xml file is stored in the following directory:
where <profile_name> is the name of the WAS profile and <cell_name> is the WAS cell in which you installed the application.
During the installation of applications, the installer uses the information you provide to populate the <sloc:serviceReference serviceName="<application_name>"/> element in the LotusConnections-config.xml file. When you install a second application on a separate profile, a second LotusConnections-config.xml file is created and are automatically federated into a single cell by the wizard. To manually link the applications, you can edit their respective configuration files.
Note: Every WAS cell has its own copy of the LotusConnections-config.xml file for the components installed in that cell. You can have different cells on a single system, in multiple profiles in a non-Network Deployment configuration, or on multiple systems that have not been federated into a single cell.
To link applications, perform the following steps:
- Stop the WebSphere Server process in which you have installed the first application.
- Stop the WebSphere Server process in which you have installed the second application.
- On the server hosting the first application, use the wsadmin tool to edit the LotusConnections-config.xml file to include information about the second application.
For more information about editing configuration files, see the Edit configuration files topic.
- Now make the second application aware of the first by using the wsadmin tool to edit the LotusConnections-config.xml file on the server hosting the second application.
- Restart the WAS processes for both applications.
- Open a web browser and start the first application to check to see if you can now access the second application.
For example, if the first application is Activities and the second Dogear, open a web browser and go to: http://appserver.enterprise.acme.com:9081/activities.
Note: Your port numbers may be different. You can look up the assigned ports in the WAS wsadmin client. (Home Page doesn't use port numbers because it is mapped to IHS.) For more information, see Starting the wsadmin client in the Administering section of the information center.
Note: On some web browsers, you might need to clear the browser cache to see this effect.
- Repeat these steps for each application you have installed, linking and testing one extran application each time.
- If you are enabling the Profiles application, edit both the profiles and personTag sloc:serviceReference elements.
Edit configuration files
Starting the wsadmin client
IBM Connections configuration files