WebSphere Enterprise Service Bus, Version 6.2.0 Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows


Configuring the Common database and the Common Event Infrastructure database using the Profile Management Tool

Selected WebSphere® ESB components require a database, called the Common database, and a Common Event Infrastructure local database to operate. Using values you provide on the Database Configuration panels, the Profile Management Tool automatically creates these databases and the required tables on a local system. You must configure these databases to have a working installation.

Before you begin

For i5/OS operating system Note: The reference to database refers to a database collection.
This procedure assumes that you have started the Profile Management Tool and have chosen to create or augment a profile through either the Advanced or Deployment environment profile creation or augmentation option. You are performing the procedure in one of the following topics: In the topic, you are at the step in the procedure that asks you to configure the Common database by completing the Database Configuration panel.

About this task

The following WebSphere ESB components use the Common database:
  • Relationship service
  • Enterprise Service Bus Logger Mediation Primitive
  • Messaging Engines (if you selected the Use this database for Messaging Engines (MEs) check box detailed in step 5).

For more information on the various databases and database tables the WebSphere ESB product uses, see Choosing a database.

Important: If you choose Derby Network Server as your database product, ensure that the server is running on the host and port you specified during profile creation or augmentation, even if the database host is local. You can make sure that the server is running only after the profile is created or augmented.
Procedure
  1. In the Choose a database product field, select the database product you want to use, or accept the default value of Derby Embedded (for stand-alone server profiles) or Derby Network Server (for deployment manager profiles).
    Restrictions:
    • Informix® Dynamic Server, and Microsoft® SQL Server are not supported on deployment managers using the deployment environment configuration.
    • For i5/OS operating system DB2® UDB for iSeries® (Native), DB2 for i5/OS® (Native), and Derby Embedded can be used only locally as a database on i5/OS. Derby Network Server, DB2 UDB for iSeries (Toolbox), and DB2 for i5/OS (Toolbox) can be used both locally and remotely on i5/OS. All other databases listed can be used with i5/OS only as remote databases provided the proper remote database driver is used.
  2. To store the database creation and configuration scripts that the Profile Management Tool will create in a location other than the default location in the Database script output directory field, select the Override the destination directory for generated scripts check box and designate your new location in the Database script output directory field. The default root directory for both the CommonDB and Common Event Infrastructure scripts is <WPS home>/profiles/<profile name>/dbscripts/.

    For example:

    Common Event Infrastructure: <WPS home>/profiles/<profile name>/dbscripts/CEI_<ceiDbName>

    CommonDB: <WPS home>/profiles/<profile name>/dbscripts/CommonDB/<dbType>/<dbName>

    The profile creation or augmentation process will create scripts that you or the database administrator can run manually to create a new database and its required tables, if you choose not to have the Profile Management Tool do this automatically. (You prevent automatic creation and configuration of this database by selecting the Delay execution of database scripts (must select if using a remote database) check box in this panel, described in step 4.)

  3. Enter your database name or accept the default value.

    For i5/OS operating system On i5/OS platforms: The name of the database on i5/OS using Independent Auxiliary Storage Pools (IASPs) can be the name of the IASP.

    Default common database names differ based on the database product:
    • For i5/OS operating system *LOCAL for DB2 UDB for iSeries (Native) and DB2 for i5/OS (Native)
    • For i5/OS operating system *SYSBAS for DB2 UDB for iSeries (Toolbox) and DB2 for i5/OS (Toolbox)
    • WPRCSDB for all other database products
    Default Common Event Infrastructure database names differ based on the database product:
    • For i5/OS operating system *LOCAL for DB2 UDB for iSeries (Native) and DB2 for i5/OS (Native)
    • For i5/OS operating system *SYSBAS for DB2 UDB for iSeries (Toolbox) and DB2 for i5/OS (Toolbox)
    • EVENT for all other database products
    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 you specify is already associated with another WebSphere ESB profile, you must use a different database name.
    For i5/OS operating system Note: This does not apply to i5/OS. All profiles on i5/OS will use the same database name.
    Note: Note: The Oracle database name (dbName) is actually the Oracle Identifier (SID) and must exist in order to create tables. It can be shared between the common database and the Common Event Infrastructure database. It is recommended that you remove all Oracle database resources before creating a new profile, as the Common Event Infrastructure database creates unique database resources, such as table spaces, which will fail if it is already exists in the Oracle server.
  4. Select the Delay execution of database scripts (must select if using a remote database) check box if you do not want the Profile Management Tool to create and configure a local database automatically or create tables in an existing one during profile creation or augmentation. A local database will be created if this check box is not selected. If you select this option, you or the database administrator must manually run the scripts that the Profile Management Tool creates and stores in the location specified in the Database script output directory field on this panel. For instructions on manually creating and configuring a new Common database or creating tables in an existing one, see Creating the Common database and tables after profile creation or augmentation or Creating tables on an existing Common database after profile creation or augmentation.
    Important: Do not use the scripts located in the following directories (where the variable db_type represents the supported database product):
    • For Linux operating systemFor UNIX operating system install_root/dbscripts/CommonDB/db_type
    • For Windows operating system install_root\dbscripts\CommonDB\db_type
    These default scripts have not been updated by the Profile Management Tool.
    Restriction: The Delay execution of database scripts (must select if using a remote database) option is not available for the following configurations:
    • If you chose the Derby Embedded or Derby Network Server product.
    • In a network deployment environment.
    The next step depends on whether you are creating or augmenting a stand-alone server or deployment manager profile.
    Type of profile you are creating or augmenting Next step
    Stand-alone server Proceed to step 5.
    Deployment manager Proceed to step 7.
  5. For stand-alone server profiles only: Select the Use a file store for Messaging Engines (MEs) check box to use a file store for messaging engines. If you select this check box, the messaging engines are created and configured on a file store (except for the Common Event Infrastructure messaging engine, which uses a Derby Embedded local database even if this option is selected). If you do not select this check box, and do not select the Use this database for Messaging Engines (MEs) check box detailed in step 6, the messaging engines are created and configured on the default Derby Embedded database. Derby Embedded databases cannot be created on remote workstations. For more information on file stores, see File stores in the WebSphere Application Server Network Deployment, version 6.1 information center.
  6. For stand-alone server profiles only: Select the Use this database for Messaging Engines (MEs) check box to use the Common database for messaging engines. If you do not select this check box, and do not select the Use a file store for Messaging Engines (MEs) check box detailed in step 5, the messaging engines are created and configured on the default Derby Embedded database. Derby Embedded databases cannot be created on remote workstations. For more information on data stores, see Data stores in the WebSphere Application Server Network Deployment, version 6.1 information center.
    Restriction: This option is not available if you chose the Derby Embedded product.
  7. Click Next. The next step depends on the type of profile you are creating or augmenting and on the database product you chose.
    Type of profile you are creating or augmenting Next step
    Stand-alone server profile with the default value of Derby Embedded selected. The Profile summary panel is displayed. Return to step 12 in the topic Configuring stand-alone server profiles using customized values.
    Stand-alone server profile with any database product other than Derby Embedded selected.

    Deployment manager profile with any database product selected.

    The Database configuration (Part 2) panel is displayed with fields specific to the database product you selected. Review the topic Database configuration (Part 2) panel for Common database configuration for information on how to complete this panel. When you have completed entering information on this panel, click Next. The tool checks that a valid database connection exists. If the database connection does not exist, you need to correct the problem either by starting up the database or altering the specified parameters before continuing. The Profile summary panel is displayed. Depending on the topic from which you accessed this one, return to one of the following steps:

task Task topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.doc/doc/tins_config_common_db.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).