Use database privileges to determine the authority required to create or access your data store tables for each supported database management system.
When you create your schemas using Installer, Profile Management Tool or scripts, you need a user ID with enough authority to create your tables. Once the tables are created, the applications need enough authority to select, insert, update, and delete information in the tables.
Database management system | Minimum privilege required to use the data store tables | Additional privilege required to create the data store tables |
---|---|---|
DB2® | The user ID needs SELECT, INSERT, UPDATE, and DELETE privileges on the tables. | The user ID needs CREATETAB authority on the database and USE privilege on the table space as well as CREATEIN privilege on the schema. |
Oracle | The user ID needs at least SESSION privilege to connect to the database. If the same user ID owns both the data store schema and the component that is connecting to the database, the user ID has sufficient privilege to manipulate the tables. Otherwise, the user ID needs SELECT, INSERT, UPDATE and DELETE object privileges on the tables that comprise the data store, and DROP ANY TABLE system privilege to enable use of the TRUNCATE TABLE statement. | The user ID requires sufficient privilege to create relational tables and indexes in the data store schema. The database also requires a space quota in the default table space of the owner of that schema. Refer to Table 2 for additional Oracle database privileges for WebSphere® Process Server and WebSphere Enterprise Service Bus components. |
SQL Server | Configure the SQL Server for SQL Server and Windows® authentication. This allows authentication to be based on an SQL server login ID and password. The user ID can be the owner of the tables, or be a member of a group that has sufficient authority to issue TRUNCATE TABLE statements. | The user ID needs CREATE TABLE statement privilege. |
Informix® | The user ID must have CONNECT privilege on the database. It must also have SELECT, INSERT, UPDATE and DELETE authority on the tables. | The user ID must have RESOURCE privilege on the database. |
Derby | If user authentication is enabled, you must authorize the user ID to access the database. | You need no additional privileges. |
Component | Configuration privileges | Runtime privileges |
---|---|---|
Common DB | CREATE TABLE, CREATE INDEXTYPE, ALTER TABLE, INSERT, CREATE SEQUENCE, CREATE USER, ALTER USER, CREATE TABLESPACE | SELECT, UPDATE, DELETE, INSERT, CREATE VIEW, CREATE PROCEDURE |
Business Process Choreographer | CREATE TABLE, ALTER TABLE, CREATE VIEW, CREATE TABLESPACE, CREATE USER, CREATE PROCEDURE | SELECT, UPDATE, DELETE, INSERT |
Common Event Infrastructure (CEI) | CREATE TABLE, CREATE INDEXTYPE, ALTER TABLE, CREATE VIEW, ALTER SESSION, SELECT, UPDATE, DELETE, INSERT, CREATE TABLESPACE, CREATE PROFILE CREATE ROLE, CREATE PROCEDURE, CREATE TEMPORARY TABLESPACE | SELECT, UPDATE, DELETE, INSERT, CREATE PROCEDURE |
Messaging Engines | CREATE TABLE, CREATE INDEXTYPE | SELECT, UPDATE, DELETE, INSERT, DROP ANY TABLE |
For additional assistance when configuring WebSphere Process Server to work with an Oracle database, refer to the following tutorial: http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic/com.ibm.websphere.wps.620.doc/doc/tins_oracleincorp.html.