Create remote databases

A remote database resides on a different machine than WebSphere Portal. You must manually create the required databases before configuring WebSphere Portal to work with DB2 for z/OS. Before you begin, complete the following prerequisites:

• These instructions assume that you will use a local IBM DB2 Universal Database™ Enterprise Server Edition Connect to connect to a remote IBM DB2 Universal Database for z/OS server, and that IBM WAS, WebSphere Portal, and DB2 Connect will be installed on the same machine.

• To run SQL statements, you can use a tool like SPUFI. The specified statements include CREATE STOGROUP, CREATE DATABASE and CREATE TABLESPACE.

  For CREATE STOGROUP you have to replace the icmvolumes and icmvcat variables with volume serial numbers and a catalog name for your environment.

  For CREATE TABLESPACE you can specify a specific BUFFERPOOL. Refer to the DB2 for z/OS SQL Reference for a description of these options.

• Ensure that a TEMP database is created for your subsystem. You can use the following statements to create a TEMP database:

  CREATE DATABASE db_name AS TEMP; CREATE TABLESPACE ts_name IN db_name;
  
  

• Log on to the DB2 subsystem on the host server. DB2 system administrator rights are needed to create the databases.

• Replace variables as follows:

  • releasenameonzos, communitynameonzos, and customizationnameonzos are the WebSphere Portal databases for WebSphere Portal and Member Manager data.

  • fdbkdbnameonzos and fdbkdbts are the database and table space, respectively, for Feedback data.

  • lmdbnameonzos and lmdbts are the database and table space, respectively, for LikeMinds data.

• Because large objects are stored in columns that can become very large, logging changes to these columns requires a huge amount of log space. For this reason, large object (LOB) logging is disabled by default for tablespaces that contain such data. With LOB logging disabled, you can recover full backups, but not incremental backups that can be used for point in time recovery. To recover point in time backups, enable LOB logging. For detailed instructions, see Technote 1306637, Manage LOB logging in DB2 for z/OS.

Prerequisites

Installing DB2 for z/OS

Creating users

Use the following steps to set up WebSphere Portal with a remote instance of DB2 for z/OS. Refer to Planning for DB2 for z/OS for a list of databases and table space names. If you are configuring multiple WebSphere Portal instances to use a single DB2 subsystem, be sure to use the database and table space names associated with the WebSphere Portal instance you are setting up.

1. CREATE DATABASE releasenameonzos CCSID UNICODE;

2. CREATE DATABASE communitynameonzos CCSID UNICODE;

3. CREATE DATABASE customizationnameonzos CCSID UNICODE;

4. Execute the steps in the topic Creating the Java Content Repository database.

5. CREATE DATABASE fdbkdbnameonzos CCSID UNICODE;

6. CREATE TABLESPACE fdbkdbts IN fdbkdbnameonzos USING STOGROUP SYSDEFLT PRIQTY 5000 SECQTY 500 LOCKSIZE ROW;

7. CREATE DATABASE lmdbnameonzos CCSID UNICODE;

8. CREATE TABLESPACE lmdbts IN lmdbnameonzos USING STOGROUP SYSDEFLT PRIQTY 5000 SECQTY 500;

Parent topic:

Configure WebSphere Portal to use DB2 for z/OS

Previous topic:

Creating users

Next topic:

Creating the Java Content Repository database

Related information

Manage LOB logging in DB2 for z/OS

---