WebSphere brand IBM WebSphere Presence Server, Version 7.0

Configuring WebSphere Application Server

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:
  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 the service integration bus:
    1. In the navigation panel, click Service integration > Buses.
    2. Click New.
    3. Type PS_bus for the name of the new bus.
    4. Deselect Bus security.
    5. Click Next.
    6. Click Finish.
    7. Click Save to save changes to the master configuration.
    8. Click OK when node synchronization has completed.
  3. Add bus members:
    1. In the Buses list, click PS_bus.
    2. Under Topology (on the Configuration tab), click Bus members.
    3. Click Add.
    4. Click Server.
    5. 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.
    6. Click File store, and click Next.
    7. Click Next.
    8. Click Finish.
    9. Repeat steps 3.c through 3.h for each server in the cluster.
    10. Click Save to save changes to the master configuration.
    11. Click OK when node synchronization has completed.
  4. Define the JMS factories:
    1. In the navigation panel, click Resources > JMS > JMS providers.
    2. In the Scope drop-down list, select Cluster=WPS_cluster where WPS_cluster is the name of the cluster you created.
    3. Click Default messaging provider.
    4. Under Additional Properties, click Topic connection factories.
    5. Click New.
    6. Type PresenceTCF in the Name field.
    7. Type jms/presenceTCF in the JNDI name field.
    8. Select PS_bus for the Bus name.
    9. Click Apply.
    10. Click Save to save changes to the master configuration.
    11. Click OK when node synchronization has completed.
  5. Define the JMS topic:
    1. In the navigation panel, click Resources > JMS > JMS providers.
    2. In the Scope drop-down list, select Cluster=WPS_cluster where WPS_cluster is the name of the cluster you created.
    3. Click Default messaging provider.
    4. Under Additional Properties, click Topics.
    5. Click New.
    6. Type PresencePublishT in the Name field.
    7. Type jms/presencePublishT in the JNDI name field.
    8. Select PS_bus for the Bus name.
    9. Select Default.Topic.Space for the Topic space.
    10. Click Apply.
    11. Click Save to save changes to the master configuration.
    12. Click OK when node synchronization has completed.
  6. Define the JMS activation specifications:
    1. In the navigation panel, click Resources > JMS > JMS providers.
    2. Click Default messaging provider for the cell where you plan to install Presence Server.
    3. Under Additional Properties, click Activation specifications.
    4. Click New.
    5. Type TAS in the Name field.
    6. Type jms/tas in the JNDI name field.
    7. Select Topic for the Destination type.
    8. Type jms/presencePublishT in the Destination JNDI name field.
    9. Select PS_bus for the Bus name.
    10. Select Auto-acknowledge for the Acknowledge mode.
    11. Select Nondurable for the Subscription durability.
    12. Click Apply.
    13. Click Save to save changes to the master configuration.
    14. Click OK when node synchronization has completed.
  7. Verify that the message engines are all created.
    1. In the navigation panel, click Service integration > Buses.
    2. In the Buses list, click PS_bus.
    3. 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.
  8. Review the SIP ports assigned to the proxy server:
    1. In the navigation panel, click Servers > Proxy Servers.
    2. Click WPS_proxy.
    3. Under Communications, click Ports.
    4. Verify that PROXY_SIP_ADDRESS appears in the list. Remember this port number; you will need it later.
    5. Verify that PROXY_SIPS_ADDRESS appears in the list. Remember this port number; you will need it later.
  9. Review the SIP ports assigned to each application server in the cluster:
    1. In the navigation panel, click Servers > Application servers.
    2. Click the server name, for example WPS_server1.
    3. Under Communications, click Ports.
    4. Verify that SIP_DEFAULTHOST appears in the list. Remember this port number; you will need it later.
    5. Verify that SIP_DEFAULTHOST_SECURE appears in the list. Remember this port number; you will need it later.
    6. Repeat steps 9.b through 9.e for each server in the cluster.
  10. Review the default virtual aliases:
    1. In 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 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.
    5. Click New to create the missing port.
    6. Type the port number in the Port field.
    7. Click Apply.
    8. Click Save to save changes to the master configuration.
    9. Click OK when node synchronization has completed.
    10. Repeat steps 10.e through 10.i until all port numbers are listed.
  11. Start the cluster:
    1. In the navigation panel, click Servers > Clusters.
    2. Select the check box corresponding to WPS_cluster.
    3. Click Start.
    4. In the Status column, verify that WPS_cluster has started.
  12. Restart the deployment manager and node agents where you plan to deploy Presence Server:
    1. Stop each node agent. Click System administration > Node agents, select all nodes, and click Stop.
    2. Stop the deployment manager. Click System administration > Deployment manager and click Stop.
    3. Start the deployment manager. Run the following command:
      • AIX was_profile_root/bin/startManager.sh
      • Linux was_profile_root/bin/startManager.sh

      Where:

      • The was_profile_root path contains the name of the deployment manager profile (for example, Dmgr01).
    4. Start each node agent. Run the following command:
      • AIX was_profile_root/bin/startNode.sh
      • Linux was_profile_root/bin/startNode.sh

      Where:

      • The was_profile_root path contains the name of a federated node profile (for example, Custom01).



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