Use the interactive installer to install the IBM® WebSphere® Presence
Server Component.
Before you begin
- The Presence Server databases
must be created on your database server.
- The database client for your database server must be installed
in the same path on each Presence Server computer
(each node).
- The WebSphere Application Server
Network Deployment version
should be 7.0.0.1 or 6.1.0.21.
- The WebSphere Application Server topology
should be configured. For example, nodes should be created and configured
in each cluster. A proxy server should also be created.
- WebSphere Application Server security
should be configured with the preferred user repository.
- If you are using the WebSphere IMS™ Connector Trust Association Interceptor (TAI),
the TAI JAR
file should be installed on each Presence Server server.
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:
- 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.
- Set the proper file permissions on the setup.bin file
by typing chmod 755 setup.bin from the command prompt.
- Launch the interactive installer. Run the following command: ./setup.bin
- Click Next at the
introduction panel.
- 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.
- Select a WebSphere Application Server installation
and click Next.
- Select the WebSphere Application Server profile
to be used for the installation, and click Next. Example: opt/IBM/WebSphere/AppServer/profiles/Dmgr01
- Select Install, and click Next.
- Type the administrative user's name and password, and click Next. Example:
- WebSphere Administrator Name: was_admin
- WebSphere Administrator Password: waspass
- Select the WebSphere scope where you are installing, and
click Next. (For clustered installations,
select the cluster you created during the prerequisite steps.)
- Select a proxy server.
- 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;*.*.*.*
- 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.
- Click Next.
- 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
- Click Next.
- Configure SIBus information by selecting Data
Store or File Store and clicking Next.
- Configure the database parameters
- Select DB2 or Oracle.
- 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.
- Click Next.
- 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 |
- 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.
- 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 |
- Click Next
- 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 |
- 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.
- 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.
- Click Next.
- Review the pre-installation summary, and click Install.
- Review the installation summary.
- 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:
/usr/IBM/WebSphere/AppServer
/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.