The Common database configurations contain information about supported database types; scripts and their locations; profile creation configuration actions; installation parameters; types of created tables and user ID privileges.
The Common database is optionally created when you create a WebSphere® ESB profile. This database acts as a repository for various components.
Database Types | Considerations |
---|---|
Derby Embedded | Used as the default database type for standalone profile. |
Derby Network Server | Used as the default database type in network deployment environment. |
DB2 Universal | Used as the database in network deployment configurations. Optionally, can be used as the database in stand-alone server configurations. |
DB2 for z/OS v8 |
Important: When creating a profile
for a server that uses DB2 for z/OS v9,
the server must be able to connect to the DB2® database.
Used
as the database in network deployment configurations. Optionally,
can be used as the database in stand-alone server configurations. |
DB2 UDB for iSeries (Native) |
Used as a local database for standalone profile. |
DB2 UDB for iSeries (Toolbox) |
Used as a remote database for network deployment environment or as a local database for a standalone profile.Used as the database in network deployment configurations. Optionally, can be used as the database in stand-alone server configurations. |
DB2 Universal Runtime Client | Used as the database in network deployment configurations. Optionally, can be used as the database in stand-alone server configurations. |
Informix Dynamic Server | |
Microsoft SQL Server (Embedded) | |
Microsoft SQL Server (DataDirect) | |
Microsoft SQL Server (Microsoft) - Support for the Microsoft SQL Server JDBC Driver, version 1.2 was added in WebSphere Process Server, version 6.2.0.1 | |
Oracle 9i |
You need sysdba privilege to create the database, tables and schemas. Failure to have the correct sysdba privilege can result in errors creating and accessing the tables and schemas. |
There is one set of common database tables per cell.
Installer
Use the Installer if you are going to create your profiles when you install your software. You can install your database products during installation but you are limited in the types of database products you can install. If you want to use another supported database product not in Table 2, you must create your deployment manager using the Profile Management Tool.
Option | Databases you can use |
---|---|
Typical: Stand-alone profile | Derby Embedded only |
Typical: all other profiles | Derby Network Server only |
Customized: Stand-alone profile |
|
Customized: all other profiles |
|
Profile Management Tool
Use the Profile Management Tool to create profiles after you install your software. The Profile Management Tool allows you the options of installing your database before, during or after profile creation. See "Creating the Common database and tables manually after profile creation or augmentation" for more information. For the locations of the database scripts, see "Scripts and their locations".
Table 3 lists the databases supported by typical (default) profiles and customized profiles. The Profile Management Tool typical installation has default values for the database and configuration parameters that cannot be changed. The Profile Management Tool customized installation allows you to change the configuration parameters and to choose a supported database. See "Creating profiles" for more information on creating customized profiles.
Options | Databases you can use |
---|---|
Typical: Stand-alone profile | Derby Embedded only |
Typical: all other profiles | Derby Network Server only |
Customized: Stand-alone profile | Any of the Supported database types |
Customized: all other profiles | Any of the Supported database types |
Silent Installations
When you install the product silently, you can specify the common database configuration by editing the template response file. See "Installing silently" for more information.
Scripts
There are two location where you can find the default profile scripts. You can locate one set of default scripts on your product media in the following directory media_root/dbscripts.
The other profile default scripts are located in the following directory after installation of WebSphere ESB install_root/dbscripts/CommonDB/dbType.
You can create your common database using scripts before you install WebSphere ESB or during profile creation. See "Creating the Common database manually before product installation" for more information.
If you choose to configure your database with scripts during profile creation, you first need to install WebSphere ESB and select the option to defer database creation. Profile creation collects your database parameters, which are added to default scripts. After you complete your profile creation, you can find the updated scripts in the following location:
profile_root/dbscripts/CommonDB/dbType/dbName
You can then give these scripts to the person who will create your Common database. The scripts are ready to execute, but you can edit them to include any specific requirements. If you try to start WebSphere ESB before creating the database you will receive an error message.
SQL scripts allow you to configure your database before or after profile creation. Tables are created with a deployment manager profile and so there are no SQL scripts executed as part of managed node creation.
If you choose to defer creation of the database after you have created the profile, the updated scripts will be found in:
profile_root/dbscripts/feature/dbType/dbName
A new JDBC provider is created depending on the database type. The provider is created in the node scope in a stand-alone profile and at cell level in network deployment environment. JDBC Provider refers to variable JDBC_DRIVER_PATH to locate local JDBC drivers. The variable is specified in cell level and each node level to point to correct local path.
There are several restrictions on the database commands that are available to the user during profile creation.
Component | Table names | Scripts |
---|---|---|
Relationship | Dynamic table, created at runtime | createTable_RelationshipMetadataTable.sql |
Common database | SchemaVersionInfo | createTable_CommonDB.sql |
ESB Logger Mediation | MSGLOG | createTable_ESBLoggerMediation.sql |
All the above SQL scripts are executed by commonDBUtility.ant from each component script, such as configRecovery > commonDBUtility > execute createTable_Recovery.sql. When the value delayConfig=true is in the response file, the SQL files are created, but are not run. When this is the case, you will need to run the SQL manually after the configuration.
Scripts are created for any option chosen on the Profile Management Tool panel to configure the Common database. The scripts contain only basic creation statements for databases, tables, and indexes. The database administrator must use database native commands to execute these scripts. See "Configuring the Common database using the Profile Management Tool" for more information.
The scripts are called configCommonDB.bat or configCommonDB.sh for Windows® and UNIX-based operating systems, respectively.
profile_root/dbscripts/CommonDB/dbType/dbName