Configure the web address after an update 

Update the web address that IBM HTTP Server uses to access applications that have been modified after a product update.

Before starting

If you plan to use a reverse proxy, update the web addresses in the LotusConnections-config.xml file to use the proxy URLs. Go to the IBM Connections wiki for more information about deployment scenarios, including how to configure a reverse proxy.

About this task

After updating to IBM Connections 3.0.1 from version 3.0, you need to update the web address for applications that were modified by the update.

By default, the web addresses that you enter to access IBM Connections applications include the application server host plus port number for each application. These are the internal addresses of the applications.

For example, when a webserver is configured, you could access Profiles at webserver.example.com. Without a webserver, you could access the application directly at node1.example.com:9080/profiles or node2.example.com:9080/profiles, and so on. However, such addresses are not practical for customers. Instead, it is standard practice to configure a webserver to handle requests, balance loads, and protect the back end from users.

Once you configure addresses by editing the LotusConnections-config.xml file, the webserver redirects requests to the appropriate port for each application. For more information about editing configuration files, see the Edit configuration files topic.

To update the web address...

Procedure

1. Stop WAS.

2. Check out the LotusConnections-config.xml file. The file is stored by default in the following directory:
   

   • AIX : /usr/IBM/WebSphere/AppServer/profiles/<profile_name>/config/cells/<cell_name>/LotusConnections-config

   • Linux™: /opt/IBM/WebSphere/AppServer/profiles/<profile_name>/config/cells/<cell_name>/LotusConnections-config

   • Windows™: C:\IBM\WebSphere\AppServer\profiles\<profile_name>\config\cells\<cell_name>\LotusConnections-config
     
   Note: Each href attribute in the LotusConnections-config.xml file is case-sensitive and must specify a fully-qualified domain name.
   

3. Update the web address for the Moderation application:
   

   <sloc:serviceReference enabled="true"
   serviceName="moderation" ssl_enabled="true">
   <sloc:static href="http://<webserver>" 
   ssl_href="https://<webserver>">
   <sloc:interService href="https://<webserver>">

   where <webserver> is the address of your IBM HTTP Server.
   

4. Update the web address for the media gallery widget:
   

   <sloc:serviceReference enabled="true"
   serviceName="mediaGallery" ssl_enabled="true">
   <sloc:hrefPathPrefix>/news/widgets/lw
   </sloc:hrefPathPrefix>
   <sloc:static href="http://<webserver>"
   ssl_href="https://<webserver>"/>
   <sloc:interService href="https://<webserver>"/>

   where <webserver> is the address of your IBM HTTP Server.
   

5. Save and check in the LotusConnections-config.xml file.

6. Synchronize the nodes in your deployment.

7. Restart the dmgr.

8. Log into each application to ensure that the web address links in the navigation bar have been updated.
   

Parent topic

Post-update tasks

   

 

});

+

Search Tips   |   Advanced Search