For using a database from a SOA composite, a database connection is required. The configuration has remained the same through the 11g lifetime, but the configuration tools have changed with Fusion Middleware Control 12c in SOA Suite 12.2. This tutorial guides through the creation of a database connection in 12.2.
This is, for example, how your Database Adapter configuration might look like. In the top half is the connection information for the JDeveloper IDE. But after deployment, the Composite will not connect directly via the JDBC connect string, but via the database connection identified by the JNDI name below (here: eis/DB/soadb). That connection needs to be created on the server, or the composite will not deploy.
To create it, we need a JDBC Data Source first. To create it, in FMW Control browse to JDBC Data Sources
Choose Create|Generic Data Source
On the first page of the Wizard, click Select... and chose the Thin XA driver for Service connections.
Give it a name (SOAe2e Data Source) and a JNDI Name (jdbc/soae2eds), then click Next.
Click on 'Generate URL and Properties' and enter your database connection information
Click Test Database Connection. If that fails, check your parameters
On the targets tab, check your SOA server and save.
Now that we have a JDBC connection, we need a DB connection. Click on WebLogic Domain|Deployments
Check Show All and click on the DbAdapter.
In Modules and Components, click on DbAdapter.rar.
Here you will learn, that the DB-Adapter configuration hasn't been ported to FMW Control yet. So click on the link to get directed to good old WLS Console.
Navigate to Deployments|Configuration|Outbound Connection Pools and click on New.
Choose java.resource.cci.ConnectionFactory and click Next.
Accept the Deployment Plan and click OK.
Give it a name. This must exactly be the same as in JDeveloper, or it will not be found at deployment time.
Back in the list, click on the new Connection Pool to configure it.
For the XADataSourceName enter the JNDI name of the JDBC connection created above. Press RETURN before clicking on Save.
You should get the confirmation shown above.
Back in FMW Control, the new DB adapter should be visible in the JNDI Browser. If it is not, try restarting the DB Adapter or the domain.
Having the DB connection set up properly, the deployment should work.
This is, for example, how your Database Adapter configuration might look like. In the top half is the connection information for the JDeveloper IDE. But after deployment, the Composite will not connect directly via the JDBC connect string, but via the database connection identified by the JNDI name below (here: eis/DB/soadb). That connection needs to be created on the server, or the composite will not deploy.
To create it, we need a JDBC Data Source first. To create it, in FMW Control browse to JDBC Data Sources
Choose Create|Generic Data Source
On the first page of the Wizard, click Select... and chose the Thin XA driver for Service connections.
Give it a name (SOAe2e Data Source) and a JNDI Name (jdbc/soae2eds), then click Next.
Click on 'Generate URL and Properties' and enter your database connection information
Click Test Database Connection. If that fails, check your parameters
In the list of JDBC Data Sources, click on the newly created DS.
On the targets tab, check your SOA server and save.
Now that we have a JDBC connection, we need a DB connection. Click on WebLogic Domain|Deployments
Check Show All and click on the DbAdapter.
Here you will learn, that the DB-Adapter configuration hasn't been ported to FMW Control yet. So click on the link to get directed to good old WLS Console.
Navigate to Deployments|Configuration|Outbound Connection Pools and click on New.
Choose java.resource.cci.ConnectionFactory and click Next.
Give it a name. This must exactly be the same as in JDeveloper, or it will not be found at deployment time.
Back in the list, click on the new Connection Pool to configure it.
For the XADataSourceName enter the JNDI name of the JDBC connection created above. Press RETURN before clicking on Save.
Back in FMW Control, the new DB adapter should be visible in the JNDI Browser. If it is not, try restarting the DB Adapter or the domain.
