Portal, V6.1

---

 

Configure WebSphere Portal to use DB2

This section provides information on how to manually transfer data to the DB2 database you have installed and set up. Follow these steps to transfer WebSphere Portal, and Java Content Repository databases to DB2

Before you begin:
Ensure that the following prerequisites are met:

• Supported database software is installed.

• Databases and users are set up.

Prerequisites

Installing DB2

Create users

Creating remote databases

Modifying database properties

Installing DB2

Create users

Creating remote databases

Modifying database properties

Tips:

• The steps for transferring data to another supported database section provides instructions for manually transferring data. Instead of performing the following steps, use the configuration wizard, which is a graphical user interface, to transfer data to another supported database.

• To run these tasks as a non-root user, first run the task chown -R non-root_user WebSphereDir.

• If you are transferring from Oracle, the open_cursors setting should be set to 1500 by default. If you are using Java Content Repository, this value might need to be increased based on the table count in the Java Content Repository schema.

Steps for transferring data to another supported database

1. If you are running a type 2 connection, before transferring data edit the db2cli.ini file. Failure to follow these steps will cause the database transfer to hang at the task action-process-constraints.

   1. Locate the file C:\Program Files\ibm\SQLLIB\db2cli

   2. Add the following to the end of the file. Leave an empty line after ReturnAliases=0.

      [COMMON] DYNAMIC=1 ReturnAliases=0
      
      

2. Perform this step only if you are installing multiple instances of WebSphere Portal. Change the maximum number of databases MAX_NETBIOS_CONNECTIONS to increase the default configured number of databases. For example, enter the following command at the database prompt: set client MAX_NETBIOS_CONNECTIONS 254 A message indicates success if the number was increased.

3. Open a command prompt and change to the directory WP_PROFILE/ConfigEngine.

4. Use a JDBC Type 2 driver only, export the DB2 user profile that you created when installing DB2 onto the administrative user using the following command. This command gives that administrative user rights over DB2.

   . /home/db2inst1/sqllib/db2profile
   

   where db2inst1 represents your database instance

   You must complete this step before running database tasks and before enabling security to create a suitable JDBC driver.

5. Validate configuration properties.

   • ./ConfigEngine.sh validate-database-driver -DTransferDomainList=release,customization,community,jcr,feedback,likeminds

   • ./ConfigEngine.sh validate-database-connection -DTransferDomainList=release,customization,community,jcr,feedback,likeminds

6. From the same command prompt as the previous steps, change to the directory WP_PROFILE/bin.

7. Stop both WAS and the WebSphere Portal server:

   Option	Description
   WAS	./stopServer.sh server1 -username adminid -password passwd
   WebSphere Portal	./stopServer.sh WebSphere_Portal -username adminid -password passwd

8. Transfer the database:

   1. Change to the directory WP_PROFILE/ConfigEngine.

   2. Enter the following commands:

      ./ConfigEngine.sh database-transfer -DTransferDomainList=release,customization,community,jcr,feedback,likeminds

   3. After running this task, a message is added to the log files to verify that this task was successful. Check the log files. If the configuration fails, verify the values in the wkplc.properties, wkplc_comp.properties, and wkplc_dbtype.properties files and then repeat this step.

9. After transferring the database tables, perform a reorg check to improve performance.

   Perform this step for each database alias in the property file.

   1. Connect to a database with the following command:

      db2 connect to database_alias user db2adminid using password
      

      Additional options might be required if additional security has been installed. Refer to DB2 Universal Database commands by example for links to the command reference.

   2. After it is connected, run the following commands from the DB2 prompt: db2 reorgchk update statistics on table all > xyz.out

   3. Look in the reorg column for entries marked with a * (star or asterisk) in the file xyz.out. For each line with a *, note the tablename and run the following command for each tablename:

      db2 reorg table tablename db2 terminate c:\> db2rbind database_name -l db2rbind.out -u db2_admin -p password
      

   4. The output file db2rbind.out is only created when there is an error for the db2rbind command.

10. Change to the directory WP_PROFILE/bin.

11. Start the WebSphere Portal server: ./startServer.sh WebSphere_Portal

 

Parent topic

Preparing DB2 on AIX for a stand-alone production server

 

Previous topic:

Modifying database properties

Next topic:

Change driver types

 

Parent topic

Configure WebSphere Portal to use DB2

 

Previous topic:

Modifying database properties

Next topic:

Change driver types

 

Related tasks

SQL0443N with SYSIBM:CLI:-805 when invoking a CLI catalog function after upgrading to DB2 UDB V8.1 FixPak 10

 

Related information

http://www-106.ibm.com/developerworks/db2/library/techarticle/dm-0406dang/index.html

---