A remote database resides on a different machine than WebSphere® Portal Express®. You must manually
create the required databases before configuring WebSphere Portal Express 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 WebSphere Application Server, 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 the tablespace ts_name is available
in either DSNDB07 or a WORKFILE DATABASE. Availability depends on
whether or not you 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 Express databases for WebSphere Portal Express 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, you must enable LOB logging. For detailed instructions,
see Technote 1306637, Managing LOB logging in DB2 for z/OS.
- Prerequisites
- Linux idle standby: Installing DB2 for z/OS
- Linux idle standby: Modifying DB2 for z/OS database properties
- Linux idle standby: Creating DB2 for z/OS users
Use the following steps to set up WebSphere Portal Express 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 Express instances
to use a single DB2 subsystem,
be sure to use the database and table space names associated with
the WebSphere Portal Express instance
you are setting up.
- CREATE DATABASE releasenameonzos CCSID
UNICODE;
- CREATE DATABASE communitynameonzos CCSID
UNICODE;
- CREATE DATABASE customizationnameonzos CCSID
UNICODE;
- CREATE DATABASE fdbkdbnameonzos CCSID
UNICODE;
- CREATE TABLESPACE fdbkdbts IN fdbkdbnameonzos USING
STOGROUP SYSDEFLT PRIQTY 5000 SECQTY 500 LOCKSIZE ROW DEFINE
NO;
- CREATE DATABASE lmdbnameonzos CCSID
UNICODE;
- CREATE TABLESPACE lmdbts IN lmdbnameonzos USING
STOGROUP SYSDEFLT PRIQTY 5000 SECQTY 500 DEFINE
NO;