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


Users and schemas for databases

During the installation of WebSphere® ESB, you have the option of using the default schema name and user ID privileges when installing your databases. However, your database design may require separate user ID and schema name privileges. You can review the three provided scenarios to determine when and how to configure different schema name and user ID privileges when installing WebSphere ESB.

Single user ID or schema name privileges for default configuration

If you chose a default installation for your databases, WebSphere ESB requires a minimum of one user ID or schema name with the ability to create tables and to select, insert, update, and delete rows in those tables. You can use Profile Management Tool or Installer to create your databases. Table 1 shows the default database configuration properties using DB2® as your database vendor. Other database vendors have different default database configuration properties.
Table 1. Default user ID and schema name privileges using DB2
Database tables Default database name with DB2 User ID or schema name
Common database tables WPRCSDB WebSphere ESB provides a user ID during installation
Messaging tables MEDB WebSphere ESB provides a schema name during installation

Multiple user ID or schema name privileges

If your database design has different properties, you may need multiple user ID and schema name privileges. Provided are three scenarios along with tables to show you how to apply the configuration to achieve your desired design. If your particular design is not in the three provided scenarios, a review of these scenarios should help you implement your particular design.

Scenario 1

In this scenario you use a schema name that is the same as the user ID privileges, but you are not using the default schema name or user ID privileges. This single user ID can access all the database and also create all needed tables. The following are examples of scenario 1 privileges:
  • Schema name: dog
  • Schema name for SCA.SYSTEM ME : dogSYS
  • Schema name for SCA.APP ME: dogAPP
  • Schema name for Event ME: dogEvent
  • User ID to create schemas: dog
  • User ID to select, insert, update, and delete schemas: dog
Table 2 is a list of how to set up the schema name and user ID privileges using DB2 as your database vendor. If you choose a different databases vendor, see their documentation for setting up schema names and user ID privileges.
Table 2. Scenario 1
Database tables Database name with DB2 Schema name User ID to create tables User ID to select, insert, update, and delete rows
Common database tables
You supply this value in the
  • Installation wizard
  • Profile Management Tool
  • Silent install
  • Silent profile creation
This schema name is the same as the user ID used to select, insert, update, and delete rows. This value is the same as the user ID used to select, insert, update, and delete rows.
You supply this value in the
  • Installation wizard
  • Profile Management Tool
  • Silent install
  • Silent profile creation

Scenario 2

In this scenario you use the same the schema name and user ID to select, insert, update, and delete schemas. However, you use a different user ID to create the schemas. The following are examples of scenario 2 privileges:
  • Schema name: snow
  • Schema name for SCA.SYSTEM ME: snowSYS
  • Schema name for SCA.APP ME: snowAPP
  • Schema name for Event ME: snowEvent
  • User ID to create the schemas: rock
  • User ID to select, insert, update, and delete schemas: snow
Table 3 is a list of how to set up the schema name and user ID privileges using DB2 as your database vendor. If you choose a different databases vendor, see their documentation for setting up schema names and user ID privileges.
Table 3. Scenario 2
Database tables Database name with DB2 Schema name User ID to create tables User ID to select, insert, update, and delete rows Additional configuration values
Common database tables
You supply this value twice:
  1. In table creation scripts
  2. During the WebSphere ESB configuration using one of the following:
    • Administrative console
    • Installation wizard
    • Profile Management Tool
    • Silent install
    • Silent profile creation
Note: If you execute the Installer first, then you supply the value once because the generated scripts already contain the correct schema name and user ID values.
The table creation scripts need to be modified with the schema name that allows reading and writing rows. The table creation script needs to be modified with the user ID that allows table creation.
You supply the user ID during profile creation through one of the following:
  • Installation wizard
  • Profile Management Tool
  • Silent install
  • Silent profile creation
While using the installer or Profile Management Tool, you need to select existing database tables or delay tables creation.

Scenario 3

In this scenario you use the same user ID to create all schemas. However, each schema has a different user ID to select, insert, update, and delete rows. The following are examples of scenario 3 privileges:
  • Schema name: waterCom
  • Schema name for common tables: waterCom
  • Schema name for SCA.SYSTEM ME: waterSYSME
  • Schema name for SCA.APP ME: waterAPPME
  • Schema name for Event ME: waterEventME
  • Schema name for ESBMessaging tables: waterESB
  • User ID to create schemas: milk
  • User ID to select, insert, update, and delete schemas:
    Schema name User ID to select, insert, update, and delete schemas
    waterCom waterCom
    waterSYSME waterSYSME
    waterAPPME waterAPPME
    waterEventME waterEventME
    waterESB waterESB
Table 4 is a list of how to set up the schema name and user ID privileges using DB2 as your database vendor. If you choose a different databases vendor, see their documentation for setting up schema names and user ID privileges.
Table 4. Scenario 3
Database tables Database name with DB2 Schema name User ID to create tables User ID to select, insert, update, and delete rows Additional configuration values
Common database tables
You supply this value in the
  • Installation wizard
  • Profile Management Tool
  • Silent install
  • Silent profile creation
This schema name is the same as the user ID used to select, insert, update, and delete rows. This value is the same as the user ID used to select, insert, update, and delete rows.
You supply the user ID during profile creation through one of the following:
  • Installation wizard
  • Profile Management Tool
  • Silent install
  • Silent profile creation
After you create the data sources, you modify the DB2 value to use the schema name.
Messaging tables You supply this value with the definition of each messaging engine. The table creation scripts need to include the schema name that is used to select, insert, update, and delete rows. This value is the same as the user ID used to select, insert, update, and delete rows. You supply this value during the creation of the messaging engine. Select the create table option during the messaging engine configuration.  

reference Reference 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/rpln_userid_privilege_db.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).