Preventing duplicate configuration session or workspace ID generation

To prevent different processes from generating duplicate configuration session or workspace IDs within the same millisecond, you must set a JVM custom property.

Before you begin

Expected state:
  • Single server: the Sametime® Gateway Server is started.
  • Cluster: the deployment manager is started.

About this task

In a single-server environment, apply this property to the JVM on the Sametime Gateway server.
In a clustered environment, apply this property to the following servers, proxies, nodes and the cell's deployment manager in the Gateway cell:
  • Sametime Gateway Servers
  • WebSphere SIP Proxy Servers
  • Deployment manager for the cluster
  • All nodes in the cluster

Procedure

  1. Log in to the WebSphere Integrated Solutions Console as the administrator.
  2. In the navigation tree, click Servers > Server Types > WebSphere application servers.
  3. In the table of application servers, click the name of the server you want to modify.
  4. On the Configuration tab, locate the Server Infrastructure section, and click Java and Process Management > Process definition.
  5. In the Additional properties section, click Java Virtual Machine.
  6. A new Configuration tab displays. In the Additional properties section, click Custom properties.
  7. Click New and enter the following information:
    • Name: com.ibm.websphere.management.configservice.sessionIdUniqueness. This property is case sensitive, enter it exactly as shown.
    • Value: random
    Note: If this property already exists, make sure the value is set to random.
  8. Click OK.
  9. In the "Messages" box at the beginning of the page, click Save.
  10. Complete one of the following steps:
    • Single server -- Restart the Sametime Gateway Server. This task is complete.
    • Cluster -- Restart the cluster and then continue to the next step to set this property for the cluster.
  11. Repeat this process for all application servers and node agents in the cluster. In the navigation tree, select a server or node agent:
    • Application servers -- Click Servers > Server Types > WebSphere application servers.
    • Proxy servers -- Click Servers > Server Types > WebSphere application servers.
    • Node agents -- Click System Administration > Node Agent.
    • Deployment manager -- Click System Administration > Deployment Manager.
  12. Create the new custom property or update an existing one as you did in Step 7.
  13. In the "Messages" box at the beginning of the page, click Save.
  14. Synchronize the nodes and restart the cluster:
    1. In the navigation tree, click System Administration > Nodes.
    2. Select all nodes in the cluster, and then click the Full Resynchronize at the beginning of the table.
    3. In the navigation tree, click System Administration > Node Agents.
    4. Select a node agent, and then click Restart all servers on Node.
    5. Restart the deployment manager.