You must configure the application server for the clustered environment.
By configuring Java Messaging Service (JMS) and the service integration bus,
you will enable multiple servers to communicate.
Before you begin
Before you begin, the following software should be installed:
WebSphere® Application Server
Network Deployment,
Version 7.0.0.7
In addition, you should have completed the following items:
Created a deployment manager profile
Created a federated node
Created the cluster
Defined the proxy server
About this task
Complete the following steps to configure WebSphere Application Server
Network Deployment for the IBM® WebSphere Presence
Server Component installation:
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 the service integration
bus:
In the navigation panel, click Service integration > Buses.
Click New.
Type PS_bus for the name
of the new bus.
Deselect Bus security.
Click Next.
Click Finish.
Click Save to save
changes to the master configuration.
Click OK when node
synchronization has completed.
Add bus members:
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,
and click Next.
Click Next.
Click Finish.
Repeat steps 3.c through 3.h for each server in the cluster.
Click Save to save
changes to the master configuration.
Click OK when node
synchronization has completed.
Define the JMS factories:
In the navigation panel, click Resources > JMS > JMS providers.
In the Scope drop-down list, select Cluster=WPS_cluster where WPS_cluster is the name of the cluster you created.
Click Default messaging provider.
Under Additional Properties, click Topic
connection factories.
Click New.
Type PresenceTCF in the Name field.
Type jms/presenceTCF in the JNDI
name field.
Select PS_bus for the Bus
name.
Click Apply.
Click Save to save
changes to the master configuration.
Click OK when node
synchronization has completed.
Define the JMS topic:
In the navigation panel, click Resources > JMS > JMS providers.
In the Scope drop-down list, select Cluster=WPS_cluster where WPS_cluster is the name of the cluster you created.
Click Default messaging provider.
Under Additional Properties, click Topics.
Click New.
Type PresencePublishT in
the Name field.
Type jms/presencePublishT in
the JNDI name field.
Select PS_bus for the Bus
name.
Select Default.Topic.Space for
the Topic space.
Click Apply.
Click Save to save
changes to the master configuration.
Click OK when node
synchronization has completed.
Define the JMS activation specifications:
In the navigation panel, click Resources > JMS > JMS providers.
Click Default messaging provider for
the cell where you plan to install Presence Server.
Under Additional Properties, click Activation
specifications.
Click New.
Type TAS in the Name field.
Type jms/tas in the JNDI
name field.
Select Topic for
the Destination type.
Type jms/presencePublishT in
the Destination JNDI name field.
Select PS_bus for the Bus
name.
Select Auto-acknowledge for
the Acknowledge mode.
Select Nondurable for
the Subscription durability.
Click Apply.
Click Save to save
changes to the master configuration.
Click OK when node
synchronization has completed.
Verify that the message engines are all created.
In the navigation panel, click Service integration > Buses.
In the Buses list, click PS_bus.
Under Topology (on the Configuration tab), click Messaging
engines. For each server in the cluster, verify
that the corresponding messaging engine is in the table.
Review the SIP ports assigned to the
proxy server:
In the navigation panel, click Servers > Proxy Servers.
Click WPS_proxy.
Under Communications, click Ports.
Verify that PROXY_SIP_ADDRESS appears in the list. Remember
this port number; you will need it later.
Verify that PROXY_SIPS_ADDRESS appears in the list. Remember
this port number; you will need it later.
Review the SIP ports assigned to
each application server in the cluster:
In the navigation panel, click Servers > Application servers.
Click the server name, for example WPS_server1.
Under Communications, click Ports.
Verify that SIP_DEFAULTHOST appears in
the list. Remember this port number; you will need it later.
Verify that SIP_DEFAULTHOST_SECURE
appears in the list. Remember this port number; you will need it
later.
Repeat steps 9.b through 9.e for each server in
the cluster.
Review the default virtual aliases:
In the navigation panel, click Environment > Virtual Hosts.
Click default_host.
Under Additional Properties, click Host Aliases to
display a list of port numbers.
Verify that the port numbers associated with the following port
names appear in the list:
PROXY_SIP_ADDRESS
PROXY_SIPS_ADDRESS
SIP_DEFAULTHOST
SIP_DEFAULTHOST_SECURE
You obtained these port numbers in steps 8 and 9. If
some or all of the port numbers are not listed, continue with step 10.e.
If all of the port numbers are listed, skip to step 11.
Click New to create
the missing port.
Type the port number in the Port field.
Click Apply.
Click Save to save
changes to the master configuration.
Click OK when node
synchronization has completed.
Repeat steps 10.e through 10.i until all port numbers are
listed.
Start the cluster:
In the navigation panel, click Servers > Clusters.
Select the check box corresponding to WPS_cluster.
Click Start.
In the Status column, verify that WPS_cluster has
started.
Restart the deployment manager and node agents where you plan to
deploy Presence Server:
Stop each node agent. Click System
administration > Node agents,
select all nodes, and click Stop.
Stop the deployment manager. Click System administration > Deployment manager and click Stop.
Start the deployment manager. Run
the following command:
was_profile_root/bin/startManager.sh
was_profile_root/bin/startManager.sh
Where:
The was_profile_root path
contains the name of the deployment manager profile (for example,
Dmgr01).
Start each node agent. Run
the following command:
was_profile_root/bin/startNode.sh
was_profile_root/bin/startNode.sh
Where:
The was_profile_root path
contains the name of a federated node profile (for example, Custom01).