WebSphere brand IBM WebSphere Presence Server, Version 7.0

Installing Presence Server using the interactive installer

Use the interactive installer to install the IBM® WebSphere® Presence Server Component.

Before you begin
About this task

For standalone configurations (one Presence Server instance in a cluster) this installation needs to be run only once on the standalone server. For clusters with managed nodes, the installation must be run on the deployment manager and each managed node. The installation is abbreviated when run on the managed nodes.

To install Presence Server, locate the installation setup file on the Presence Server CD ROM and follow these instructions:

  1. Copy the setup.bin file from the CD-ROM to a directory on your system, and copy the IBMPresenceServerDbPackage_7.0.tar file to a directory on your database server.
  2. Set the proper file permissions on the setup.bin file by typing chmod 755 setup.bin from the command prompt.
  3. Launch the interactive installer. Run the following command: ./setup.bin
  4. Click Next at the introduction panel.
  5. Select I accept the terms of the License Agreement, and click Next. The installer checks to verify that the correct version of WebSphere Application Server is installed and returns a list of qualified WebSphere Application Server installations.
  6. Select a WebSphere Application Server installation and click Next.
  7. Select the WebSphere Application Server profile to be used for the installation, and click Next. Example: opt/IBM/WebSphere/AppServer/profiles/Dmgr01
  8. Select Install, and click Next.
  9. Type the administrative user's name and password, and click Next. Example:
    • WebSphere Administrator Name: was_admin
    • WebSphere Administrator Password: waspass
  10. Select the WebSphere scope where you are installing, and click Next. (For clustered installations, select the cluster you created during the prerequisite steps.)
  11. Select a proxy server.
  12. In a clustered installation, click Configure CSCF Address and type the address for the CSCF server. This is a semicolon-delimited list of hosts (IP addresses or host names) for which the proxy server will not remove the P-asserted identity headers that are added by the CSCF. The use of a mask (*) is permitted. Do not include spaces in the input string.

    This step is required is when you are installing or modifying a deployment manager on a cluster scope. It ensures that P-asserted identity headers that are added by the CSCF will not be removed by the proxy server.

    Examples of valid addresses: 192.0.2.21;*.*.*.*
  13. Click Next. The installer looks for previously installed versions of Presence Server and returns with the choice to modify or install. The instructions in the window apply whether you choose Modify or Install.
  14. Click Next.
  15. Optional: Select the Configure TAI check box, and type the list of allowed senders. This is a comma-delimited list of hosts (IP addresses or host names) that the interceptor considers to be trusted. Do not include spaces in the input string.

    If the IMS Trust Association Interceptor (TAI) is configured, this variable is used to set the allowed senders configuration parameter for the TAI. This step is required when you are installing or modifying a deployment manager. Additionally, the TAI JAR files must be installed on all nodes. The use of a mask (x for the TAI) is permitted.

    For information about allowed senders for the TAI, refer to the topic Configuring the Trust Association Interceptor in the IMS Connector portion of this information center.

    Examples of valid addresses: x@us.example.com,x.example.com,192.2.x.x,x.x.x.x,2002:92A:8F7A:0:0:20:0:1
  16. Click Next.
  17. Configure SIBus information by selecting Data Store or File Store and clicking Next.
  18. Configure the database parameters
    1. Select DB2 or Oracle.
    2. Click Choose and navigate to the directory where the JDBC JAR files are located. The JDBC JAR files should be installed in the location on all nodes.
    3. Click Next.
    4. Type the following information into the corresponding fields for the Presence Server database (PSDB):
      Configuration parameter Example
      Database Host Name db2_server1
      Database Name PSDB
      Database Port Number 5000
      Database Administrator Name db2inst
      Database Administrator Password db2password
    5. Select the Update Configuration Table check box, and click Next.
      Note: Selecting this is necessary only if a previous configuration exists in the database. If the database is not already configured the configuration table will be updated anyway.
    6. Type the following information into the corresponding fields for the Presence Server content indirection database (PSCIDB), and click Next:
      Configuration parameter Example
      Database Host Name db2_server1
      Database Name PSCIDB
      Database Port Number 5000
      Database Administrator Name db2inst
      Database Administrator Password db2password
    7. Click Next
    8. Type the following information into the corresponding fields for the Presence Server usage record database (PSURDB):
      Configuration parameter Example
      Database Host Name db2_server1
      Database Name PSURDB
      Database Port Number 5000
      Database Administrator Name db2inst
      Database Administrator Password db2password
    9. Select the Create Usage Record Tables check box, and click Next.
      Important: Select this check box only if you are using a new usage record database. Any previous information in the database will be removed if this is selected.
    10. Optional: If you selected to use Data Store earlier, type the following information into the corresponding fields for the Presence Server SIBUS data store database (PSSIBUS):
      Configuration parameter Example
      Database Host Name db2_server1
      Database Name PSSIBUS
      Database Port Number 5000
      Database Administrator Name db2inst
      Database Administrator Password db2password
      Note: If you selected to use the File Store option, no additional configuration is required and this step is skipped.
    11. Click Next.
  19. Review the pre-installation summary, and click Install.
  20. Review the installation summary.
  21. Optional: To review the installation logs, navigate to was_root/logs.
    Note: was_root is the installation root directory for WebSphere Application Server Network Deployment. By default, this directory is:
    • AIX /usr/IBM/WebSphere/AppServer
    • Linux /opt/IBM/WebSphere/AppServer
Results
The Presence Server application is ready to deploy. Use the primary configuration file, SystemConfiguration.xml, if you would like to modify the default configuration before deployment. This file is found in the directory was_root/installableApps/presence/scripts/config. (There is also a backup copy in was_root/logs.) For more information, refer to the Configuring IBM WebSphere Presence Server Component section of this information center.



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