Solaris stand-alone: Prepare DB2 for z/OS

Set up the DB2 for z/OS database includes creating user IDs, databases, and table spaceson a remote server.

1. Solaris stand-alone: Install DB2 for z/OS
   View information on how to install DB2 for z/OS for use with IBM WebSphere Portal.
2. Solaris stand-alone: Modify properties for DB2 for z/OS
   This section provides information on how to modify the wkplc.properties, wkplc_dbdomain.properties, and wkplc_dbtype.properties files to work with the database. Modify these property files before running tasks to create databases, create users, or transfer data.
3. Solaris stand-alone: Use JCL templates to set up DB2 for z/OS
   To use a DB2 for z/OS database, we can use JCL template files to help customize the database based on the configuration prior to using the DB2 for z/OS database.
4. Solaris stand-alone: Create users for DB2 for z/OS
   Create users for IBM DB2 Universal Database™ for z/OS to work with IBM WebSphere Portal. The Customization Dialog generates job EJPSRACthat we use to create users. Review the generated job and update it as appropriate for the installation requirements. If we use a security product such as Top Secret or ACF2 instead of RACF, modify the job as appropriate. After you run the job, grant the necessary access rights to all users who require them. Depending on the architecture that you choose, these users might include Java Content Repository and Feedback users.
5. Solaris stand-alone: Create a remote database on DB2 for z/OS
   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.
6. Solaris stand-alone: Grant privileges to DB2 for z/OS users
   Configuration and runtime database users are granted a different set of privileges, depending on whether these users are schema owners or not. We can create a copy of the SQL scripts and edit this copy to manually grant permissions to configuration and runtime database users.

7. Optional: Solaris stand-alone: Assign custom tablespaces for DB2 on z/OS
   The repository of WebSphere Portal consists of many tables and indicecreated in default table spaces. When using an existing set of table spaces for the objects of the repository, specify this when executing the database transfer to the target database system.
8. Solaris stand-alone: Configure the portal to use DB2 for z/OS
   View information on manually transferring data to theDB2 for z/OS you have installed and set up. Follow these steps to transfer WebSphere Portal, and Java Content Repository to DB2 for z/OS. As an alternative to the manual database transfer procedure described here, we can use the configuration wizard to complete the database transfer task. However, we cannot specify all settings through the configuration wizard.

   For example, regardless of the method used to transfer data, you must run a configuration task to create JMS resources as described in this topic.

Parent: Solaris stand-alone: Configure Portal to use a database