Standalone server: 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 beginning, 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, we 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 the environment. For CREATE TABLESPACE we can specify a specific BUFFERPOOL. Refer to the DB2 for z/OS SQL Reference for a description of these options.

• Ensure that the tablespace ts_name is available in either DSNDB07 or a WORKFILE DATABASE. Availability depends on whether or not we are using a data-sharing environment.

• 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 containing such data. With LOB logging disabled, we 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

Standalone server: Install DB2 for z/OS

Standalone server: Create users on DB2 for z/OS

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 we 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 we are setting up.

1. CREATE DATABASE releasenameonzos CCSID UNICODE;
   

2. CREATE DATABASE communitynameonzos CCSID UNICODE;
   

3. CREATE DATABASE customizationnameonzos CCSID UNICODE;
   

4. CREATE DATABASE fdbkdbnameonzos CCSID UNICODE;
   

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

6. CREATE DATABASE lmdbnameonzos CCSID UNICODE;
   

7. CREATE TABLESPACE lmdbts IN lmdbnameonzos USING STOGROUP SYSDEFLT PRIQTY 5000 SECQTY 500 DEFINE NO;
   

Parent: Standalone server: Prepare DB2 for z/OS
Previous: Standalone server: Create users on DB2 for z/OS
Next: Standalone server: Assign custom table spaces