Configuring the Common database using the Profile wizard

The information requested on the Database configuration panel and the Additional database configuration information panel (if it is displayed) correctly configure a new local or existing database for use with selected WebSphere Process Server components, or generate scripts so you or your database administrator can perform configuration later. (Database configuration for the Common Event Infrastructure and Business Process Choreographer components is performed separately.)

Before you begin

This procedure assumes you are Configuring a stand-alone server profile or Configuring a deployment manager. As a result, you have started the Profile wizard and have selected to create or augment a stand-alone process server or deployment manager profile. You are at the step in the procedure which asks you to configure the Common database.

Why and when to perform this task

Several WebSphere Process Server components use the Common database, including: You need to configure this database to have a working installation. In most cases, you configure this database through specific Profile wizard panels during the profile creation or augmentation process. Configure it by doing the following on the Database configuration panel.

Steps for this task

  1. Choose one of the following actions by selecting the appropriate radio button:
    • Create a new (local) database – the profile creation or augmentation process will create a new database and the required tables on the local machine. No other database by the same name can exist or the procedure will fail.
    • Use an existing database – the profile creation or augmentation process will create the required tables in an existing database on either the local or a remote machine.
    • Set up a new or existing database separately (apart from the profile creation or augmentation process) – the profile creation or augmentation process will create scripts that you or the database administrator must run manually to create a new database and its required tables, or just required tables on an existing database. The scripts must be run after the profile creation or augmentation process completes to correctly configure the database. The database can exist on either the local or a remote machine depending on the database type selected.
  2. Choose the database you want to use, or accept the default value of Cloudscape V5.1 (for stand-alone process server profiles) or DB2 Universal (for deployment manager profiles).
    Select from the following entries (each entry is followed by the database it represents):
    • Cloudscape V5.1 (Cloudscape) – supported for stand-alone server profiles only
    • DB2 Universal (DB2 Universal Database)
    • DB2 UDB for z/OS and OS/390 V7 (DB2 UDB for z/OS and OS/390 V7)
    • DB2 UDB for z/OS V8 (DB2 UDB for z/OS V8)
    • DB2 CLI (DB2 Call Level Interface)
    • Informix (Informix Dynamic Server)
    • MSSQL Server Embedded (Microsoft SQL Server Embedded)
    • MSSQL Server Data Direct (Microsoft SQL Server DataDirect)
    • Oracle OCI (Oracle OCI client)
    • Oracle Thin (Oracle Thin)
    Restriction: You cannot create a new database if you are using DB2 UDB for z/OS and OS/390 V7, DB2 UDB for z/OS V8, Oracle OCI, or Oracle Thin. If you select one of these databases and the option Create a new (local) database, a message panel prompts you to either use an existing database or select a different database product. Select OK to close this message panel, and make different selections on the Database configuration panel.
  3. Enter your database name or accept the default WPRCSDB. If you plan to use an existing database, this name must match the name of that database. If you plan to create a new database and the name WPRCSDB is already associated with another WebSphere Process Server profile, you must use a different database name.
  4. Select Next. One of the following panels is displayed:
    • If you are creating a stand-alone process server profile, selected the default value of Cloudscape V5.1, and elected to create a new local database or use an existing database, the Profile summary panel is displayed. Return to step 12 in the topic Configuring a stand-alone server profile.
      Restriction: The Setting up a new or existing database separately option is not supported for Cloudscape V5.1. If you select this combination, a message panel prompts you to select another database option. Select OK to close this message panel, and make different selections on the Database configuration panel.
    • If you are creating a stand-alone process server profile and you selected any database other than Cloudscape V5.1, the Additional database configuration information panel is displayed with fields specific to the database you selected. Review the topic Additional database configuration information panel for information on how to complete this panel. When you've completed entering information on the Additional database configuration information panel, select Next. The Profile summary panel is displayed. Return to step 12 in the topic Configuring a stand-alone server profile.
    • If you are creating a deployment manager profile and selected any value for the database, the Additional database configuration information panel is displayed with fields specific to the database you selected. Review the topic Additional database configuration information panel for information on how to complete this panel. When you've completed entering information on the Additional database configuration information panel, select Next. The Profile summary panel is displayed. Return to step 9 in Configuring a deployment manager.

Last updated: Wed 01 Nov 2006 07:47:12

(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)