This is the second of a 5 part series that explains how to expose a database to an Oracle BPM 12c Process using the Oracle SOA Database Adapter and a Mediator.
Part 2 - Configure the Database Adapter's Outbound Connection Pool
In the first part of this series, the JNDI connection to the database schema was configured. Because the Database Adapter will be used to access the information from the database, it needs to become aware that the schema exists. Here you will add the JNDI connection information to the Database Adapter.
To configure the Database Adapter to use the “jdbc/hr” JNDI name you created from the instructions in the previous blog, click Deployments -> click DBAdapter.
Next the connection pool will now be configured. WebLogic communicates with the database through a connection pool. This pool allows WebLogic to use a fixed number of connections to databases rather than incurring the overhead of constantly creating and disposing of connections. Each data source has a connection pool assigned to it, which it uses for connecting to the actual data provider (the Database in this case). Recall that when creating the datasource, a JNDI name was provided. This same JNDI name will be used when configuring the connection pool’s call the datasource. Click the Configuration tab (1 below) -> click the Outbound Connection Pools tab (2) -> Expand javax.resource.... (3) -> click New (4).
Click the radio button beside the connection factory -> click Next.
In the JNDI Name field, enter the same JNDI name you used when creating the database connection in JDeveloper eis/DB/HR (this is case sensitive) -> click Finish.
Click.OK. This should be displayed:
In the next blog in this series (part 3) you will see how to configure the Database Adapter's JNDI connection to the datasource.