WebSphere Portal v6 Install DB2

 

+
Search Tips   |   Advanced Search

 

You are here

  1. Planning for DB2

  2. Installing DB2 (Current task)

  3. Creating databases and users for DB2

  4. Transferring DB2 manually or Transferring between databases manually

  5. Verifying database connections

This section explains how to install DB2 for use with WebSphere Portal.

Before you begin

  • You should have completed reviewing the Planning for DB2 section.

  • If using a remote database, the following prerequisites must be completed separately from the WebSphere Portal installation.

    • Configure the DB2 Connect client with the following commands:

      • db2 update dbm cfg using tp_mon_name WAS

      • db2 update dbm cfg using spm_name hostname, where hostnameis the host name for the portal

        Because the default for spm_name is the host.name itself, specifying the hostname parameter is optional. If the hostname is more than eight (8) characters, use empty double quotes (" "). For example, db2 update dbm cfg using spm_name " ".

    • Make sure DB2 is set up with updated kernel parameters according to the recommendations in the DB2 Quick Beginnings guide.

    • DB2 Connect, part of IBM DB2 Universal Database Enterprise Server Edition, must be installed on the same machine as WebSphere Portal.

      If you are installing DB2 Connect for use with a DB2 for z/OS server, refer to the Installing DB2 for z/OS topic.

 

Installing

    If you install DB2 using the DB2 installation program, it will automatically create a DB2 administrative user with the correct operating system rights.

    Before you begin installing WebSphere Portal, also install the client software, DB2 Connect, on the same machine as WebSphere Portal and WebSphere Application Server. Installing DB2 Connect enables the WebSphere Portal to use the required JDBC drivers. You must also ensure that the DB2 Connect installation is the same name as the server profile name.

    1. Before installing DB2, log in with a user ID that has administrative authority.

      Windows only:

      This user should have the following specifications:

      • Be defined locally
      • Belong to the local Administrator group
      • Act as part of the operating system
      • Have permissions to create a token object
      • (Windows 2000) Have permissions to increase quotas
      • (Windows 2003) Have permissions to adjust memory quotas for a process
      • Have permissions to replace a process level token

      To edit user rights, do following:

      • For the first two specifications:

        Start | Programs | Administrative Tools | Computer Management | Local Users and Groups.

      • For the last four specifications:

        Start | Programs | Administrative Tools | Local Security Policy | Local Policies | User Rights Assignment

      Linux only:

      The system user ID and password must match the database user ID and password for the WebSphere Portal databases. If you do not use the default DB2 database user ID, or if access a remote database, create the system user ID before installing DB2.

      To set up the environment for the database access, the initialization script for this user (for example, user-home/.profile) must contain a call to...

      $DB_HOME/sqllib/db2profile

      After you create the system user ID and password for the DB2 installation, add the user ID to the DB2 administration group (such as db2adm) for that system. To ensure that the user is set up correctly, login with this user ID, and start the DB2 command line processor by executing the command: db2. If the command line processor for is displayed, the user ID is set up correctly.

    2. To install DB2, follow the instructions that are provided with the DB2 documentation to install DB2 and the required fix pack.

    Because WebSphere Portal does not use the OLAP Starter Kit, you do not need to install the OLAP Starter Kit. If you have an existing DB2 installation with OLAP Starter Kit, it will not affect the WebSphere Portal installation or operation.

     

    Next steps

    You have completed this step. Continue to the next step:

     

    Parent topic:

    Installing databases