S2: Editing the configuration file 

You must update the LotusConnections-config.xml with the href and ssl_href values of the components on the HTTP server so that the correct links appear on the Connections UI for all components. To do so, on the deployment manager node, check out the Lotus Connections config file, make the described changes and then check in the file using the wsadmin client as described in the following link:

http://publib.boulder.ibm.com/infocenter/ltscnnct/v2r0/topic/com.ibm.connections.25.help/t_admin_common_checkout_config_file.html

This is a Connections-wide change so the following command is used to check out the file:

LCConfigService.checkOutConfig("/tmp/”,"dmgrCell01")

This file is then checked out to this directory. It is recommended to copy this file and store it as a backup in the /opt/IBM/Backups directory. From the /tmp/ directory, open the lotusConnections-config.xml with a text editor and make the following changes.

For each component within this file, update the href, ssl_href and interservice href to that of the Web server as shown:

All entries in this file should be updated to the Web server URL with the exception of the three bootstrap entries – two of which should not be modified. The only bootstrap entry that must be modified is that for search. Leave the host and port blank as shown: The final change that is required in this config file is to find the forceConfidentialCommunications flag and set it to true as below: This forces all communications on the Connections server to be over HTTPS. More details on securing can be found in the info center and at this link: http://publib.boulder.ibm.com/infocenter/ltscnnct/v2r0/topic/com.ibm.connections.25.help/t_admin_common_forcing_ssl.html After you have completed editing this file, save it, and check in again using the wsadmin client, the following command will achieve this on the wsadmin client: LCConfigService.checkInConfig() After checking this file in the following command can be used to deploy these changes: synchAllNodes() Go to the next topic: S2: Scenario environment S2: Prerequisites   S2: Configuration diagrams S2: Machine details S2: Installing Lotus Connections in an Enterprise level deployment S2: Preinstallation tasks S2: Installing Lotus Connections on node 1 S2: Adding nodes 2 and 3 to the cluster S2: Post installation tasks S2: Setting up the Web server S2: Configuring SSL and adding features to the SSL trust store S2: Editing the configuration file S2: Scheduling Activities tasks S2: Tuning WebSphere Application Server for optimal performance S2: Starting Lotus Connections S2: Configuring an administrative user for Blogs S2: Integrating Lotus Connections with Lotus Quickr for WebSphere Portal S2: Enabling Sametime awareness on Lotus Connections S2: Troubleshooting Table of Contents: Lotus Connections 2.5 Enterprise level deployment scenario