Create Oracle databases before installing IBM Business Automation Studio.
About this task
You must create a database for
Application
Engine playback server as well as for
IBM Business Automation Studio before you can
run
Business Automation
Studio.
Restriction: You cannot use the same database user for Business Automation
Studio and any other component, such
as Application
Engine playback server or
IBM Business Automation Workflow. You can use the
same database user for Business Automation
Studio
if the schema of all the databases created are the same. You can use a shared database but you must
use a different database user for each component.
Tip: If you need to know which
database versions are supported for your installation, use this
IBM Support page to generate a software compatibility
report.
Procedure
-
Connect to your local or remote database server by running the following command:
sqlplus oracle_user_ID/oracle_password@oracle_instance_name as sysdba
- To create the Application
Engine
playback server database, run the following command on your local or remote database
server:
-- create a new user
CREATE USER APP_ENGINE_DB_USER_NAME IDENTIFIED BY APP_ENGINE_DB_PASSWORD ;
-- grant privileges to system and objects
grant create session to APP_ENGINE_DB_USER_NAME;
grant alter session to APP_ENGINE_DB_USER_NAME;
grant create table to APP_ENGINE_DB_USER_NAME;
grant unlimited tablespace to APP_ENGINE_DB_USER_NAME;
grant select any table to APP_ENGINE_DB_USER_NAME;
grant update any table to APP_ENGINE_DB_USER_NAME;
grant insert any table to APP_ENGINE_DB_USER_NAME;
grant drop any table to APP_ENGINE_DB_USER_NAME;
where
APP_ENGINE_DB_USER_NAME is the username that the Application
Engine playback server uses to connect to the
database.
APP_ENGINE_DB_PASSWORD is the password that the Application
Engine playback server uses to connect to the
database.
- To create the Business Automation
Studio database,
run the following command on your local or remote database
server:
-- create a new user
CREATE USER STUDIO_USER_NAME IDENTIFIED BY STUDIO_USER_PASSW0RD;
-- allow the user to connect to the database
grant connect to STUDIO_USER_NAME;
-- provide quota on all tablespaces with BPM tables
grant unlimited tablespace to STUDIO_USER_NAME;
-- grant privileges to create database objects:
grant resource to STUDIO_USER_NAME;
grant create view to STUDIO_USER_NAME;
-- grant access rights to resolve lock issues
grant execute on dbms_lock to STUDIO_USER_NAME;
-- grant access rights to resolve XA related issues:
grant select on pending_trans$ to STUDIO_USER_NAME;
grant select on dba_2pc_pending to STUDIO_USER_NAME;
grant select on dba_pending_transactions to STUDIO_USER_NAME;
-- If using Oracle 10.2.0.3 or lower JDBC driver, un-comment the following statement:
-- grant execute on dbms_system to STUDIO_USER_NAME;
-- If not using Oracle 10.2.0.4 or higher JDBC driver, comment the following statement:
grant execute on dbms_xa to STUDIO_USER_NAME;
where
- Optional: To use your own JDBC driver, complete the
following steps.
What to do next
To protect the configuration data you're going to enter, see Creating secrets to protect sensitive configuration
data.