Use the configuration file to assign different Presence Server clusters
for handling requests from specified groups of users, and to specify
the mode in which the Presence Server application
should operate (RLS stand-alone mode, Presence Server stand-alone
mode, or both modes simultaneously.
Before you begin
You will need the following files to complete
this task. After you install the
Presence Server product,
these files are found in the directory
was_root/installableApps/presence/scripts/config.
- SystemConfiguration.xml
- ConfigurationParams.txt
- UpdateConfiguration.jar
Before you can make changes to your configuration, the file
UpdateConfiguration.jar must
be in the class path.
About this task
To route requests to specific Presence Server clusters,
and to configure for Presence Server stand-alone
mode or RLS stand-alone mode, complete the following steps.
When
you enable the routing service, you should also configure Presence Server to
run in RLS mode. Do not enable Presence Server stand-alone
mode.
Refer to the topic The Presence Server entry
point for additional information about these product features.
- Open SystemConfiguration.xml with
a text editor.
- Modify the attributes on the routingService tag
to configure routing.
- Set enable="true" to enable the routing
service. By default, the routing service is disabled.
- Use the class attribute to specify
the Java routing class implementation. This class should
implement com.ibm.presence.api.routingRoutingService.
The Presence Server product
includes a default implementation for the routing service: com.ibm.presence.routing.DefaultRoutingService.
When you use this default routing implementation, you will need to
configure the Presence Server standalone
address.
- Code presenceServerCluster tags inside
the routingService tag. Include a presenceServerCluster tag
for each stand-alone instance of Presence Server.
The presenceServerCluster tag
must have an address attribute containing a valid
SIP URI for the specific Presence Server cluster
to which requests are to be forwarded.
For example: - <routingService enable="true" class="com.ibm.presence.routing.DefaultRoutingService">
- <presenceServerCluster address="sip:pshostname.example.com:7010"/>
- </routingService>
- Modify the attributes on the standaloneRLS tag
to specify that the Presence Server application
should run in RLS stand-alone mode.
You can set the
following attributes.
- enable=""
- true to run in RLS mode; false otherwise.
The default value is false.
Note: When you enable
RLS mode, the routing component (
routingService)
must also be enabled as described in step
2.
- entryAddress
- A valid SIP URI representing the Presence Server deployment
entry point. For example, this address can be the SIP address for
the S-CSCF server.
- assertedIdentity
- A valid SIP URI representing the RLS SIP user ID to use when sending
back-end subscriptions to clusters that are running in Presence Server stand-alone
mode.
For example: - <standaloneRLS enable="true" entryAddress="sip:scscfhostname.example.com:7010;transport=TCP"
assertedIdentity="sip:superadmin@example.com"/>
- Modify the attributes on the standalonePresenceServer tag
to specify that the Presence Server application
should run in Presence Server stand-alone
mode.
You can set the following attributes.
- enable=""
- true to run in Presence Server stand-alone
mode; false otherwise. If you enabled the routing
service in step 2,
you must specify false. The default value is false.
- RLSAssertedIdentity
- A valid SIP URI to be used as the asserted identity for the stand-alone Presence Server and
as a "From" header in the back-end subscription that is created by
the RLS and forwarded to Presence Server.
Should be the same as assertedIdentity in the standaloneRLS tag.
For example: - <standalonePresenceServer enable="true" RLSAssertedIdentity="sip:superadmin@example.com"/>
- Save and close the file.
- Open ConfigurationParams.txt with
a text editor.
- Update
the following parameters for your environment:
- cfg.system = xml_path (where xml_path is
the directory location for SystemConfiguration.xml)
- username = database_administrator_user_name
- password = database_administrator_password
dbDriver =
com.ibm.db2.jcc.DB2Driver
dbDriver =
oracle.jdbc.driver.OracleDriver
dbConnectionString =
jdbc:db2://database_host_name:database_port/database_name
dbConnectionString =
jdbc:oracle:thin:@database_host_name:database_port:database_name
- Run the java command
that is appropriate for your operating system:
Important: Enter the following
parameters on a single line.

java
-classpath UpdateConfiguration.jar: jdbc_path CmdConfig config_path/ConfigurationParams.txt
(where jdbc_path is the directory location
for your JDBC drivers and config_path is the directory
location for ConfigurationParams.txt)Important: JDBC drivers must be separated by a colon.
For example:
/usr/IBM/WebSphere/AppServer/java/bin/java -classpath UpdateConfiguration.jar:/opt/IBM/db2/V9.5/java/db2jcc.jar:/opt/IBM/db2/V9.5/java/db2jcc_license_cu.jar CmdConfig ConfigurationParams.txt
/opt/IBM/WebSphere/AppServer/java/bin/java -classpath UpdateConfiguration.jar:/opt/IBM/db2/V9.5/java/db2jcc.jar:/opt/IBM/db2/V9.5/java/db2jcc_license_cu.jar CmdConfig ConfigurationParams.txt
- Restart the application:
- 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 Presence Server.
- Click Stop. The Application
Status column should indicate a Stopped status.
- Click Start. The Application
Status column should indicate a Started status.