WebSphere brand IBM WebSphere Presence Server, Version 7.0

Creating the usage records database for DB2

You must create a usage records database before proceeding with the installation. It is not necessary to define the database tables at this time: they will be defined later, when you run the Presence Server interactive installation or silent installation.

Before you begin
Before you begin, the following software should be installed:
  • IBM® DB2® Enterprise Server Edition, version 9.5 FixPak 1
  1. Log in to the DB2 server as a database administrator.
  2. Create a directory that has write and execute permission, for example DB_dir.
  3. Copy the installation .tar file, IBMPresenceServerDbPackage_7.0.tar, from the installation medium to the new directory.
  4. Switch to the new directory.
  5. Unpack the installation .tar file using the following command:
    tar -xvf IBMPresenceServerDbPackage_7.0.tar
  6. Switch to the following directory: was_root/installableApps/presence/scripts/dbScripts/usageRecords.
  7. Verify that the following files exist in /usageRecords:
    • crtsrvDB2.sh
    • UsageDbDB2.ddl
  8. Run the following command to ensure that the database configuration script will run properly:
    • chmod 755 crtsrvDB2.sh
  9. Launch the crtsrvDb2 script by issuing the following command:
    ./crtsrvDb2.sh options
    where: options corresponds to the following values.
    Table 1. crtsrvDb2 configuration values
    Parameter Description Recommended Value
    dbServer Fully qualified hostname for the database server. myhost.example.com
    dbPort Number for the listening port on the database server. 50000
    dbLocal Boolean value specifying whether the database should be created in the local catalog (TRUE) or on a different server (FALSE). TRUE
    dbNodeName Remote database server node name, when dbLocal is FALSE. This value is used for reference purposes and it is not the host name. RDBSRV
    dbName Name of the database. PSUR
    dbAlias Alias by which the database is known. PSUR
    dbLocale Database locale or territory code, for example US or JP. US
    dbAdmin Administrator user ID for the database instance. db2inst1
    dbAdminPW Password for the administrator user ID. <pw>
    dbUser User ID for accessing the database. db2inst1
    dbUserPW Password for the database user ID. <pw>
    INITorDDLFile One of the following:
    • INIT to initialize the database instance
    • Path to the DDL file that is used to define the database's attributes
    INIT
    infoflag TRUE to display informational messages while the database is being initialized.

    FALSE to suppress informational messages.

    TRUE
    For example:
    ./crtsrvDb2.sh myhost.example.com 50000 TRUE RDBSRV PSUR PSUR US db2inst1 password db2inst1 password INIT TRUE
  10. Verify that the database was created properly by typing the following command:
    • db2 connect to database_alias user database_administrator_ID
    Where:
    • database_alias is the alias you provided when running the crtsrvDB2.sh script
    • database_administrator_ID represents the administrator user ID
    For example:
    db2 connect to PSUR user db2inst
    If the script ran properly, the following results display:
    Database Connection Information
    
     Database server        = DB2/LINUX 9.5.1
     SQL authorization ID   = database_administrator_ID
     Local database alias   = database_alias
Results
Note: If errors occur when you run the database preparation script, refer to the topic Troubleshooting the database script.
What to do next
The required DB2 database tables will be created for you when you run the Presence Server interactive installation or silent installation.



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