Home

Troubleshooting inter-server communication

 

+

Search Tips   |   Advanced Search

If you are having problems establishing communication between servers in your deployment, this might be because a server's URL is not configured correctly in the LotusConnections-config.xml file.

To edit configuration files, use the IBM WebSphere Application Server wsadmin client. See Start the wsadmin client for details.

If an inter-service URL identifies a target server resource secured by SSL (when a URL uses HTTPS as the protocol or redirects you to a HTTPS URL) and the host name differs from the subject of the self-signed certificate used by the target server, then attempts by the source service to authenticate against that URL will fail. For example, this might happen when an IBM Lotus Connections search indexing task is executing and it attempts to crawl the specified target services' secured seedlists. To address this issue, you need to specify the fully-qualified DNS name of the host server in the LotusConnections-config.xml file. The host name must also be the same as the subject of the self-signed certificate used by the target server for that URL.

To configure an inter-service URL for one of the Lotus Connections feature servers:

1. Use the wsadmin client to access and check out the IBM Lotus Connections configuration files:

   1. Access the Lotus Connections configuration file:

      • Stand-alone deployment: execfile("connectionsConfig.py")

      • Network deployment: execfile("WAS_HOME/profiles/Dmgr01/config/bin_lc_admin/connectionsConfig.py")If you are prompted to specify which server to connect to, type 1.

        This information is not used by the wsadmin client when you are making configuration changes.

   2. Check out the Lotus Connections configuration files...

      LCConfigService.checkOutConfig("<working_directory>","cell_name") where:

      • <working_directory> is the temporary working directory to which the configuration XML and XSD files are copied and are stored while you make changes to them. Use forward slashes to separate directories in the file path, even if you are using the Microsoft Windows operating system.

      • cell_name is the name of the WebSphere Application Server cell hosting the Lotus Connections feature. This argument is required even in stand-alone deployments. This argument is also case-sensitive, so type it with care. If you do not know the cell name, do one of the following to determine it:

        • Stand-alone deployment: From the file system...

          WAS_HOME\profiles\profile_name\config\cells\
          

      • Network deployment: Type the following command while in the wsadmin command processor:

        print AdminControl.getCell()
        

      For example:

      • AIX/Linux:

        LCConfigService.checkOutConfig("/opt/temp","foo01Cell01")
        

   3. Microsoft Windows:

      LCConfigService.checkOutConfig("c:/temp","foo01Cell01")
      

2. Optional: To find out the current value of a property, you can list the current configuration settings and values...

   LCConfigService.showConfig()
   

3. Replace the IP address for the specified host server with the fully-qualified DNS name or short DNS name for the server.

   LCConfigService.updateConfig("<property>","<value>")
   

   where <property> is one of the following:

   • feature_name.href

   • feature_name.ssl.href

   • feature_name.interService.href

   and <value> is the full DNS name for the specified host server. For example:

   LCConfigService.updateConfig("dogear.ssl.href", "https://connwin1.dyn.example.com:9443")
   

   See Common configuration properties for a complete list of editable properties.

4. Save your changes and then check the configuration files back in...

   LCConfigService.checkInConfig()

   You must run the checkin during the same wsadmin session in which you ran the checkout command.

5. To exit the wsadmin client, type

   exit

   at the prompt.

6. Stop and restart all of the Lotus Connections feature servers.

Resolving a problem

 

Related reference

Common configuration properties

---