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.
- Log in to the Integrated Solutions Console:
- 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.
- Enter an administrator user ID and password.
- Click Log in.
- Create a new server in a cluster:
- In the Integrated Solutions Console,
click .
Note: If you are using WebSphere® Application Server version 6.1.0.x, reach
this window by clicking .
- Select the check box associated with the name of the
cluster.
- Click Start.
- Click the existing cluster name.
- Under Additional Properties, click Cluster
members.
- Click New.
- Specify the new server name.
- From the drop-down list, select the node on which you
want to create the new server.
- Click Add Member.
- Click Next.
- Click Finish.
- Add a new bus member:
- Under Service integration, click Buses.
- In the Buses list, click PS_bus.
- Under Topology (on the Configuration tab), click Bus
members.
- Click Add.
- Click Server.
- 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.
- Click File store or Data
store (according to your configuration), and click Next.
- Click Next.
- Click Finish.
- Repeat the preceding steps, to add each server in the
cluster.
- Click Save to save changes to
the master configuration.
- Click OK when the node synchronization
has completed.
- Review the Session Initiation Protocol (SIP)
and HTTP ports assigned to the new server in the cluster:
- In the navigation pane, click .
Note: If you are using WebSphere Application Server version 6.1.0.x, reach
this window by clicking .
- Click the server name, for example WPS_server1.
- Under Communications, click Ports.
- Verify that SIP_DEFAULTHOST, SIP_DEFAULTHOST_SECURE,
and WC_defaulthost appear in the list. Remember these port
numbers, you will need them later.
- Also verify these values for the other new servers added
to the cluster.
- Add definitions for virtual hosts:
- On the navigation panel, click .
- Click default_host.
- Under Additional Properties, click Host Aliases to
display a list of port numbers.
- Verify that the port numbers collected in step 4 are specified in the list
of ports.
- Click New to create the missing
port.
- Type the port number in the Port field.
- Click OK.
- Add additional ports until all port numbers are listed.
- Create a thread pool for the SIP container:
- In the navigation pane, click .
Note: If you are using WebSphere Application Server version 6.1.0.x, reach
this window by clicking .
- Click new_server_name.
- Under Additional Properties, click Thread
pools.
- 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.
- Click OK and then Save,
to save the values.
- Update the default thread pool:
- In the navigation pane, click .
Note: If you are using WebSphere Application Server version 6.1.0.x, reach
this window by clicking .
- Click new_server_name.
- Under Additional Properties, click Thread
pools.
- Click Default, and update the
following values:
- Minimum Size: 60
- Maximum Size: 60
- Click OK and then Save,
to save the values.
- Set the SIP container settings:
- In the navigation pane, click .
Note: If you are using WebSphere Application Server version 6.1.0.x, reach
this window by clicking .
- Click new_server_name.
- Under Container Settings, click .
- 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)
- Click Apply.
- Click Custom properties.
- 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
- Click Save, to save your changes.
- Set the EJB timer threads settings:
- In the navigation pane, click .
Note: If you are using WebSphere Application Server version 6.1.0.x, reach
this window by clicking .
- Click new_server_name.
- Under Container Settings, click
- Change the number of timer threads to 20.
- Click OK and then Save,
to save the values.
- Set the ORB SERVICES settings:
- In the navigation pane, click .
Note: If you are using WebSphere Application Server version 6.1.0.x, reach
this window by clicking .
- Click new_server_name.
- Under Container Settings, click Container
Services.
- Click ORB Service and select Pass
by reference.
- Click Apply and then Save,
to save the values.
- Set the JVM settings:
- In the navigation pane, click .
Note: If you are using WebSphere Application Server version 6.1.0.x, reach
this window by clicking .
- Click new_server_name.
- Under Server Infrastructure, click .
- Under Additional Properties, click Java Virtual
Machine, and set the following properties:
- Click Apply and then Save,
to save the values.
- Stop and restart the application
server, nodes, and deployment manager.