Updating the stavconfig.xml file on Conference Managers

In an IBM® Sametime® deployment, the stavconfig.xml file hosted on each Sametime Conference Manager contains the FQDN/IP address and port information of each Sametime SIP Proxy/Registrar and Conference Manager.

About this task

Update this file on the deployment manager that is used for administering each Conference Manager. For a cluster of Conference Managers, only update the file once because the change is pushed out to all cluster members when you synchronize the nodes.

Procedure

  1. On the server hosting the Conference Manager's deployment manager, locate the stavconfig.xml file in the deployment manager's profile.

    The Sametime System Console is typically used as the deployment manager but is not required; your deployment may use a different server for that purpose. The stavconfig.xml file is typically stored in the following location for the deployment manager:

    Dmgr_install_root/config/cells/Cell_name/nodes/Node_name/servers/Server_name
    Note: There are several instances of the stavconfig.xml file, and all instances must be updated.
  2. Open the file for editing.
  3. Locate the following settings and modify them as needed to reference the SIP Proxy/Registrar and Conference Manager clusters:
    Note: If you have updated the server, verify that the NotificationServerPort and NotificationServerHost settings reside in the STAVconfig.xml file. If the settings are not in the STAVconfig.xml file, add the settings to the file.
    Table 1. stavconfig.xml file settings and their values
    Setting Value
    ConferenceServerHost The virtual IP address (cluster address) that is configured on the Load Balancer used by the Conference Manager cluster. This is the same IP address you obtain when resolving the SIP Proxy/Registrar host name. Alternatively, you can specify a host name if needed.
    ConferenceServerPort The SIP port that is configured on the Load Balancer for the Conference Manager cluster's SIP port should be configured according to the SIPProxyServerTransportProtocol attribute.
    • TLS - Use the secured SIP port configured on the Load Balancer.
    • TCP - Use the non-secured SIP port configured on the Load Balancer.
    SIPProxyServerHost The virtual IP address (cluster address) that is configured on the Load Balancer used by the SIP Proxy/Registrar cluster. This is the same IP address you obtain when resolving the SIP Proxy/Registrar host name. Alternatively, you can specify a host name if needed.
    SIPProxyServerPort The SIP port that is configured on the Load Balancer for the SIP Proxy/Registrar cluster's SIP port should be configured according to the SIPProxyServerTransportProtocol attribute.
    • TLS - Use the secured SIP port configured on the Load Balancer.
    • TCP - Use the non-secured SIP port configured on the Load Balancer.
    SIPProxyServerTransportProtocol TCP or TLS, depending on your configuration.
    NotificationServerHost The local host name of the Conference Manager Node. If you have updated the server, verify that the NotificationServerHost setting is in the STAVconfig.xml file. If the setting is not in the STAVconfig.xml file, add the setting to the file.
    Note: Use the fully qualified domain name of the Conference Manager node itself, NOT the domain name of the WebSphere proxy server that fronts the node and NOT the load balancer's cluster address that points to the node.

    Use the lastUpdated setting as shown in this example:

    <configuration value="server.domain.com" name="NotificationServerHost" lastUpdated="1226425838277"/>
    NotificationServerPort The https port of the Conference Manager Node. The port value can be found in the Ports list on Configuration page for the STMediaServer. (In the Integrated Solutions Console, click Server Type > WebSphere Application Servers > STMediaServer > Ports > WC_defaulthost_secure.)

    If you have updated the server, verify that the NotificationServerPort setting is in the STAVconfig.xml file. If the setting is not in the STAVconfig.xml file, add the setting to the file. Use the lastUpdated setting as shown in this example:

    <configuration value="9443" name="NotificationServerPort" lastUpdated="1226425838277"/>

  4. Save and close the file.
  5. Synchronize all nodes in the cluster as follows:
    1. In the deployment manager's Integrated Solutions Console, click System Administration > Nodes.
    2. In the nodes table, select all nodes in the cluster.
    3. Click Full Resynchronize.