WebSphere brand IBM WebSphere Presence Server, Version 7.0

Adding a server to an existing Presence Server node

If you have a running system with a Presence Server node that was defined during installation, you can add a new server instance by performing the configuration using the WebSphere Integrated Solutions Console.

Before you begin

You must have an existing node that was created as part of a full installation of the Presence Server product, using the Presence Server installer.

Note: For a complete, up-to-date list of recommended WebSphere customization settings, consult the document Tuning IBM WebSphere Presence Server component. You can download this document from the IBM Support Web site.
  1. Log in to the Integrated Solutions Console:
    1. Open a browser and navigate to the following URL: https://host_name:port/ibm/console.
      Where:
      • host_name is the fully qualified host name of the server where the application or the network deployment manager is deployed.
      • port is the secured port used to access the console. The default port is 9043.
      Note: The default unsecured port is 9060. If you use 9060, you must have "http" instead of "https" in the URL.
    2. Enter an administrator user ID and password.
    3. Click Log in.
  2. Create a new server in a cluster:
    1. In the Integrated Solutions Console, click Servers > Clusters > WebSphere application server clusters.
      Note: If you are using WebSphere® Application Server version 6.1.0.x, reach this window by clicking Servers > Clusters.
    2. Select the check box associated with the name of the cluster.
    3. Click Start.
    4. Click the existing cluster name.
    5. Under Additional Properties, click Cluster members.
    6. Click New.
    7. Specify the new server name.
    8. From the drop-down list, select the node on which you want to create the new server.
    9. Click Add Member.
    10. Click Next.
    11. Click Finish.
  3. Add a new bus member:
    1. Under Service integration, click Buses.
    2. In the Buses list, click PS_bus.
    3. Under Topology (on the Configuration tab), click Bus members.
    4. Click Add.
    5. Click Server.
    6. From the drop-down list, select the server in the cluster you defined for the Presence Server application, for example WPS_server1. Then, click Next.
    7. Click File store or Data store (according to your configuration), and click Next.
    8. Click Next.
    9. Click Finish.
    10. Repeat the preceding steps, to add each server in the cluster.
    11. Click Save to save changes to the master configuration.
    12. Click OK when the node synchronization has completed.
  4. Review the Session Initiation Protocol (SIP) and HTTP ports assigned to the new server in the cluster:
    1. In the navigation pane, click Servers > Server Types > WebSphere application servers.
      Note: If you are using WebSphere Application Server version 6.1.0.x, reach this window by clicking Servers > Application servers.
    2. Click the server name, for example WPS_server1.
    3. Under Communications, click Ports.
    4. Verify that SIP_DEFAULTHOST, SIP_DEFAULTHOST_SECURE, and WC_defaulthost appear in the list. Remember these port numbers, you will need them later.
    5. Also verify these values for the other new servers added to the cluster.
  5. Add definitions for virtual hosts:
    1. On the navigation panel, click Environment > Virtual Hosts.
    2. Click default_host.
    3. Under Additional Properties, click Host Aliases to display a list of port numbers.
    4. Verify that the port numbers collected in step 4 are specified in the list of ports.
    5. Click New to create the missing port.
    6. Type the port number in the Port field.
    7. Click OK.
    8. Add additional ports until all port numbers are listed.
  6. Create a thread pool for the SIP container:
    1. In the navigation pane, click Servers > Server Types > WebSphere application servers.
      Note: If you are using WebSphere Application Server version 6.1.0.x, reach this window by clicking Servers > Application servers.
    2. Click new_server_name.
    3. Under Additional Properties, click Thread pools.
    4. Click New, to create a thread pool for the SIP container:
      • Name: SipContainer
      • Minimum Size: 60
      • Maximum Size: 60
      • Thread inactivity timeout: 5000 (default value)
      Note: You can modify these values according to your needs. The Presence Server Performance Tuning Guide, available as a technote on the IBM Support Web site, offers recommended values.
    5. Click OK and then Save, to save the values.
  7. Update the default thread pool:
    1. In the navigation pane, click Servers > Server Types > WebSphere application servers.
      Note: If you are using WebSphere Application Server version 6.1.0.x, reach this window by clicking Servers > Application servers.
    2. Click new_server_name.
    3. Under Additional Properties, click Thread pools.
    4. Click Default, and update the following values:
      • Minimum Size: 60
      • Maximum Size: 60
    5. Click OK and then Save, to save the values.
  8. Set the SIP container settings:
    1. In the navigation pane, click Servers > Server Types > WebSphere application servers.
      Note: If you are using WebSphere Application Server version 6.1.0.x, reach this window by clicking Servers > Application servers.
    2. Click new_server_name.
    3. Under Container Settings, click SIP Container Settings > SIP container.
    4. Set the SIP container's general properties as the following:
      • Maximum application sessions: 200000
      • Maximum messages per averaging: 200000
      • Maximum dispatch queue size: 5000
      • Thread pool: SipContainer (created in step 7)
    5. Click Apply.
    6. Click Custom properties.
    7. Add the following custom properties:
      • app.composition.enabled = false
      • com.ibm.ws.sip.security.enable.digest.tai = false
      • end.of.service.replication = true
      • immediate.replication = false
    8. Click Save, to save your changes.
  9. Set the EJB timer threads settings:
    1. In the navigation pane, click Servers > Server Types > WebSphere application servers.
      Note: If you are using WebSphere Application Server version 6.1.0.x, reach this window by clicking Servers > Application servers.
    2. Click new_server_name.
    3. Under Container Settings, click EJB Container Settings > EJB timer service settings
    4. Change the number of timer threads to 20.
    5. Click OK and then Save, to save the values.
  10. Set the ORB SERVICES settings:
    1. In the navigation pane, click Servers > Server Types > WebSphere application servers.
      Note: If you are using WebSphere Application Server version 6.1.0.x, reach this window by clicking Servers > Application servers.
    2. Click new_server_name.
    3. Under Container Settings, click Container Services.
    4. Click ORB Service and select Pass by reference.
    5. Click Apply and then Save, to save the values.
  11. Set the JVM settings:
    1. In the navigation pane, click Servers > Server Types > WebSphere application servers.
      Note: If you are using WebSphere Application Server version 6.1.0.x, reach this window by clicking Servers > Application servers.
    2. Click new_server_name.
    3. Under Server Infrastructure, click Java and Process Management > Process Definition.
    4. Under Additional Properties, click Java Virtual Machine, and set the following properties:
      • Initial Heap Size = 1600
      • Maximum Heap Size = 1600
      • Generic JVM arguments = -Xgcpolicy:gencon -Xgc:scvnoAdaptiveTenure,scvTenureAge=3,stdGlobalCompactToSatisfyAllocate -Xconcurrentlevel1 -Xmn400m -Xmo1200m -Xtgc:parallel -Xdump:heap:events=user,request=exclusive+prepwalk+compact
        Note: You can copy and paste the generic JVM arguments above into the Generic JVM arguments field.
    5. Click Apply and then Save, to save the values.
  12. Stop and restart the application server, nodes, and deployment manager.



Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.