Troubleshooting inter-server communication

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.

Before you begin

To edit configuration files, you must use the IBM® WebSphere® Application Server wsadmin client. See Starting the wsadmin client# for details.

About this task

You must ensure that the LotusConnections-config.xml file contains the fully qualified DNS name of the host server for each of the IBM Connections applications, and that it matches the domain name in the self-signed certificate used by the host server. This information is particularly important for inter-service processing tasks. For example, if a server's domain name is not configured correctly, problems might occur when a Search indexing task is executing and it attempts to crawl the specified target application's' secured seedlists. For more information, see the following web page:
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/rsec_troublesso.html

Procedure

To configure an inter-service URL for one of the IBM Connections application servers:

  1. Use the wsadmin client to access and check out the IBM Connections configuration files:
    1. Enter the following command to load the IBM Connections configuration file: execfile("connectionsConfig.py")

      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.

    2. Enter the following command to check out IBM Connections configuration files:

      LCConfigService.checkOutConfig("working_directory","cell_name")

      where:
      • working_directory is the temporary working directory to which configuration files are copied. The files are kept in this working directory while you edit them.
        Notes:
        • When you specify a path to the working directory on a system that is running Microsoft Windows, use a forward slash for the directory. For example: "C:/temp".
        • AIX®, and Linux only: The directory must grant write permissions or the command fails.
      • cell_name is the name of the WebSphere Application Server cell that hosts the IBM Connections application. If you do not know the cell name, display it by typing the following command in the wsadmin client: print AdminControl.getCell()
        Note: This input parameter is case-sensitive.
  2. Optional: If you want to find out the current value of a property, you can list the current configuration settings and values by using the following command: LCConfigService.showConfig()
  3. Use the following command to 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:
    • application_name.href
    • application_name.ssl.href
    • application_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 using the following command:
    LCConfigService.checkInConfig()
    Note: 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 IBM Connections application servers.