WebSphere brand IBM WebSphere Presence Server, Version 7.0

Configuring watcher information

Presence Server has configuration options that determine the way in which watcher information is handled.

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.

Be sure that the database is running before you make changes to the configuration.

About this task

Watcher information consists of the current state for all subscriptions to a particular resource. Monitoring watcher information helps you control access to a resource because it provides the raw data you need to create and deploy presence authorization rules.

For more information about watcher information, refer to IETF RFC 3857 and RFC 3858.

To configure the monitoring of watcher information, complete the following steps:

  1. Open SystemConfiguration.xml with a text editor.
  2. Modify the attributes on the watcherInfo tag to configure the way in which watcher information is monitored.
    You can set the following attributes. Default values are shown.
    enable="false"
    true to enable monitoring of watcher information; false to disable it.
    waitingDays="4"
    Number of days to monitor subscriptions that are in the waiting state.
    waitingCheckInterval="60"
    Time, in minutes, between cleanup operations for waiting subscriptions that should no longer be monitored. A waiting subscription should not be monitored when it is older than the value specified in waitingDays. The cleanup operation checks for waiting subscriptions that should not be monitored and removes any that are found.
    For example:
    • <watcherInfo enable="true" waitingDays="4" waitingCheckInterval="60"/>
  3. Save and close the file.
  4. Open ConfigurationParams.txt with a text editor.
  5. 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
    • DB2 dbDriver = com.ibm.db2.jcc.DB2Driver
    • Oracle dbDriver = oracle.jdbc.driver.OracleDriver
    • DB2 dbConnectionString = jdbc:db2://database_host_name:database_port/database_name
    • Oracle dbConnectionString = jdbc:oracle:thin:@database_host_name:database_port:database_name
  6. Run the java command that is appropriate for your operating system:
    Important: Enter the following parameters on a single line.
    • AIXLinux 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:
    • AIX /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
    • Linux /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
  7. Restart the application:
    1. Click Applications > Application types > WebSphere Enterprise Applications.
      Note: If you are using WebSphere® Application Server version 6.1.0.x, reach this window by clicking Applications > Enterprise Applications.
    2. Select the check box associated with the Presence Server.
    3. Click Stop. The Application Status column should indicate a Stopped status.
    4. Click Start. The Application Status column should indicate a Started status.



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