Configuring the IEP Database to Use Oracle

By default, the IEP database is configured to use Java DB. Java DB is Sun's supported distribution of the open source Apache Derby database. After installation, you can configure the IEP database to use Oracle instead.

The first task is to create an IEP user in the Oracle database. You can run a provided SQL script that creates the IEP user and grants the appropriate privileges. The default version of the script contains the following SQL statements:

CREATE TABLESPACE "IEPSEDB_DB"
 DATAFILE
  'IEPSEDB_DB1.dat' SIZE 2000M,
  'IEPSEDB_DB2.dat' SIZE 2000M;

CREATE USER IEPSEDB IDENTIFIED BY IEPSEDB
DEFAULT TABLESPACE IEPSEDB_DB
QUOTA UNLIMITED ON IEPSEDB_DB
TEMPORARY TABLESPACE temp
QUOTA 0M ON system;

GRANT CONNECT TO IEPSEDB;
GRANT RESOURCE TO IEPSEDB;
GRANT CREATE VIEW TO IEPSEDB;

grant select on sys.dba_pending_transactions to IEPSEDB;
grant select on sys.pending_trans$ to IEPSEDB;
grant select on sys.dba_2pc_pending to IEPSEDB;
grant execute on sys.dbms_system to IEPSEDB;
grant select on SYS.dba_2pc_neighbors to IEPSEDB;
grant force any transaction to IEPSEDB;

You need to create two sets of connection pools and JDBC resources. A connection pool is a group of reusable connections for a particular database. The server maintains a pool of available connections to increase performance. A JDBC resource provides applications with a means of connecting to a database. Additional configuration of the service engine is also required.

To configure the IEP Service Engine to use Oracle, perform the following steps:

• To Create the IEP User in the Oracle Database

• To Install the Oracle Database Driver in the Application Server

• To Create the Non-XA Connection Pool

• To Create the Non-XA JDBC Resource

• To Create the XA Connection Pool

• To Create the XA JDBC Resource

• To Enable Automatic Recovery of XA Transactions

• To Configure the IEP Service Engine to Use the JDBC Resources

• To Restart the IEP Service Engine and Create the Database Tables

To Create the IEP User in the Oracle Database

1. In a web browser, enter the following URL: http://wiki.open-esb.java.net/Wiki.jsp?page=HowToRunIEPOnOracle.

2. Download the create_iepse_user.sql script.

3. Open the create_iepse_user.sql script and review the instructions.

4. The names of the tablespace, data files, user, and password include the string IEPSEDB. If you want to change this string to a different string, then replace all occurrences of IEPSEDB with the new string.

5. Connect to the Oracle database as a user with the SYSDBA privilege.

6. Run the create_iepse_user.sql script against the database.

To Install the Oracle Database Driver in the Application Server

1. Go to the computer where the application server is installed.

2. Copy and paste the Oracle database driver (for example, ojdbc14.jar) to the glassfish-home/lib directory.

3. Restart the application server.

To Create the Non-XA Connection Pool

1. Log in to the GlassFish Admin Console.

2. In the left navigation panel, expand Resources and JDBC, and then select Connection Pools.

3. Click New.

   The New JDBC Connection Pool page appears.

4. Do the following:

   1. In the Name field, specify a name for the non-XA connection pool (for example, iepseOraclePoolNonXA).

   2. In the Resource Type field, select javax.sql.DataSource.

   3. In the Database Vendor field, select Oracle.

   4. Click Next.

5. Scroll down to the Additional Properties table, and then do the following:

   1. In the User row, enter the user name of the IEP user (for example, IEPSEDB).

   2. In the Password row, enter the password of the IEP user (for example, IEPSEDB).

   3. In the URL row, enter the string for connecting to the database (for example, jdbc:oracle:thin:@myserver:1521:orcl).

6. Click Finish.

   The connection pool is created.

7. Click the connection pool that you just created.

   The Edit Connection Pool page appears.

8. Click Ping.

   The Admin Console attempts to connect to the database. If the connection does not succeed, check to see whether the database is running and verify the database connectivity properties, such as the URL string.

To Create the Non-XA JDBC Resource

1. In the left navigation panel of the Admin Console, expand Resources and JDBC, and then select JDBC Resources.

2. Click New.

   The New JDBC Resource page appears.

3. In the JNDI Name field, specify a unique name for the non-XA JDBC resource. By convention, the name begins with the jdbc/ string. For example:

   jdbc/iepseOracleNonXA

   You will use the JNDI name in a later procedure.

4. In the Pool Name field, select the non-XA connection pool that you created in the previous procedure.

5. Click OK.

   The JDBC resource is created.

To Create the XA Connection Pool

1. In the left navigation panel of the Admin Console, expand Resources and JDBC, and then select Connection Pools.

2. Click New.

   The New JDBC Connection Pool page appears.

3. For step 1 of the connection pool, do the following:

   1. In the Name field, specify a name for the XA connection pool (for example, iepseOraclePoolXA).

   2. In the Resource Type field, select javax.sql.XADataSource.

   3. In the Database Vendor field, select Oracle.

   4. Click Next.

4. For step 2 of the connection pool, do the following:

   1. Scroll down to the Connection Validation section.

   2. Select the Enabled check box that appears to the right of the Allow Non Component Callers label.

   3. Scroll down to the Additional Properties table.

   4. In the User row, enter the user name of the IEP user (for example, IEPSEDB).

   5. In the Password row, enter the password of the IEP user (for example, IEPSEDB).

   6. In the URL row, enter the string for connecting to the database (for example, jdbc:oracle:thin:@myserver:1521:orcl).

5. Click Finish.

   The connection pool is created.

6. Click the connection pool that you just created.

   The Edit Connection Pool page appears.

7. Click Ping.

   The Admin Console attempts to connect to the database. If the connection does not succeed, check to see whether the database is running, and verify the connectivity parameters, such as the URL string.

To Create the XA JDBC Resource

1. In the left navigation panel of the Admin Console, expand Resources and JDBC, and then select JDBC Resources.

2. Click New.

   The New JDBC Resource page appears.

3. In the JNDI Name field, specify a unique name for the XA JDBC resource. By convention, the name begins with the jdbc/ string. For example:

   jdbc/iepseOracleXA

   You use the JNDI name in a later procedure.

4. In the Pool Name drop-down menu, select the XA connection pool that you created.

5. Click OK.

   The JDBC resource is created.

To Enable Automatic Recovery of XA Transactions

1. In the left navigation panel of the Admin Console, expand Configuration and then select Transaction Service.

2. Select the Enabled check box that appears to the right of the On Restart label.

3. Click Save.

To Configure the IEP Service Engine to Use the JDBC Resources

1. Log in to the NetBeans IDE.

2. In the Services window, expand Servers > GlassFish V2 > JBI > Service Engines.

3. If the IEP Service Engine is not started, right-click sun-iep-engine and select Start.

4. Right-click sun-iep-engine and select Properties.

   The Properties dialog box appears.

5. In the Non XA Data Source Name property, enter the non-XA JDBC resource that you created (for example, jdbc/iepseOracleNonXA).

6. In the XA Data Source Name property, enter the XA JDBC resource that you created (for example, jdbc/iepseOracleXA).

7. In the Database Schema Name property, enter the user name of the IEP user (for example, IEPSEDB).

   In an Oracle database, the database schema name is identical to the user name.

8. Click OK.

To Restart the IEP Service Engine and Create the Database Tables

When you restart the IEP Service Engine, the database tables are automatically created in the database you specified through the connection pools and runtime properties.

1. If any Composite Application projects that contain event processes are currently deployed, undeploy the projects.

2. In the Services window, expand Servers > GlassFish V2 > JBI > Service Engines.

3. Right-click sun-iep-engine and select Stop.

4. Right-click sun-iep-engine and select Start.

5. If you undeployed any Composite Application projects, you can now redeploy the projects.