Windows clustered server: Install DB2

View information on installing DB2 for use with WebSphere Portal.

Before you begin:

• When you install DB2 using the DB2 installation program, it automatically creates a DB2 administrative user with the correct OS rights.

• Ensure that you have enough disk space for the DB2 instance home directory to be able to create the required databases.

• If you are using DB2 Version 9.1 use the db2jcc.jar file. You will need to replace references to db2jcc4.jar with db2jcc.jar in this topic. If you are not using this specific version of DB2, use the db2jcc4.jar file.

• If you are using DB2 for z/OSVersion 8, use the db2jcc.jar file. You will need to replace references to db2jcc4.jar with db2jcc.jar in this topic. If you are not using this specific version of DB2 for z/OS, use the db2jcc4.jar file.

• If you plan to transfer data from multiple portals sharing the same DB2 database, you should increase the default value for the number of concurrently active databases (NUMDB). The value for NUMDB depends on how many databases are concurrently used on the DB2 instance which also maintains the databases for WebSphere Portal. For example, to change the default number (NUMDB) to 30, enter the following command at the database prompt: UPDATE DATABASE MANAGER CONFIGURATION USING NUMDB 30. You will receive a message that confirms a successful completion of the update.

1. If you are using the JDBC driver in type 2 mode, configure DB2 client with the following commands.
   If you are using a remote database, complete this step separately from the WebSphere Portal installation.

   • db2 update dbm cfg using tp_mon_name WAS

   • db2 update dbm cfg using spm_name hostname, where hostname is the host name of WebSphere Portal.

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

2. Before installing DB2, log in with a user ID that has administrative authority.
   This user should have the following specifications:

   • Belong to the local Administrator group

   • Act as part of the OS

   • Have permissions to create a token object

   • Windows™ 2003 only: Have permissions to adjust memory quotas for a process

   • Have permissions to replace a process level token

   To edit user rights:

   • For the first two specifications: Click Start -> Programs -> Administrative Tools -> Computer Management -> Local Users and Groups.

   • For the last four specifications: Click Start -> Programs -> Administrative Tools -> Local Security Policy. Then, click Local Policies -> User Rights Assignment.

3. To install DB2 or the DB2 client and the required fix pack, follow the instructions that are provided with the DB2 documentation.

4. If DB2 is installed on another system than WebSphere Portal, perform the following instructions:

   • For JDBC Type 2 drivers only: The appropriate DB2 client must be installed on the same system as WebSphere Portal and have the same name as the server profile name.

   • For JDBC Type 4 drivers only: Copy the driver jar files to the Portal server. It is recommended that you place these driver files within the WP_PROFILE directory; for example:
     WP_PROFILE/PortalServer/dbdrivers/db2jcc4.jar
     WP_PROFILE/PortalServer/dbdrivers/db2jcc_license_cu.jar

Parent

Windows clustered server: Set up a remote DB2 database

Next topic

Windows clustered server: Modify DB2 database properties

 

+

Search Tips   |   Advanced Search