Adding OSB to Pre-built SOA OSB BPM (PS5) VM - WC_Spaces template

Question

Hi,
I have downloaded and setup the pre-built developer VM for SOA/OSB/BPM using the Webcenter Spaces template. Everything works fine, I am just trying to add OSB to extend the existing domain but getting stuck at the wizard where it asks for the OSB JMS Reporting Provider JDBC connection properties. The steps to get there are as follows:
Extend SOA domain
* Start Configuration Wizard:
cd /opt/oracle/Middleware/home_11gr1/Oracle_OSB1/common/bin
./config.sh
* Select Extend an existing WebLogic domain, click Next
* On Select a WebLogic Domain Directory screen, select soa_domain
* On Select Extension Source screen,
- Select: Oracle Service Bus [Oracle_OSB1]
- Select: Oracle Service Bus OWSM Extenstion [Oracle_OSB1]
- WebLogic Advanced Web Services for JAX-RPC Extension [wlserver_10.3] option is also automatically selected.
- Click Next
* On Configure JDBC Data Sources screen, select soademoDatabase which was created at SOA Suite install. Click Next.
* Test JDBC Data Sources, click Next when successful
* On Configure JDBC Component Schema, select the checkbox for OSB JMS Reporting Provider and enter
- Vendor: Oracle
- Driver: *Oracle's Driver (Thin) for Service connections; Versions:9.0.1 and later
- Schema Owner: DEV_SOAINFRA
- Schema Password: welcome1
- DBMS/Service: orcl.world
- Host Name: localhost
- Port: 1521
- Click Next ======> Can't get past here since OSB JMS Reporting Provider database cannot be found!!
Wondering if there is a way to use the initial setup script to add OSB JMS Reporting Provider DB? I also couldn't find RCU Home so that I could add the OSB JMS Reporting Provider DB to the XE Instance. Any help is much appreciated..
Thanks
Z.
Edited by: 956060 on Aug 30, 2012 8:18 AM

Answer 1

* On Configure JDBC Data Sources screen, select soademoDatabase which was created at SOA Suite install. Click Next.You may skip this step by not selecting anything. Later on when you need to work with Reporting, you may create a data-source and tables manually.
And at the next startup of the Admin Server it complains about the JDBC connection not available and fails to initialize it.To avoid this problem, you may follow below steps -
1. Navigate to directory $Domain_Home/config
2. Search for string "wlsbjmsrpDataSource" in file config.xml
3. You will find an entry like below -
<jdbc-system-resource>
<name>wlsbjmsrpDataSource</name>
<target>AdminServer</target>
<descriptor-file-name>jdbc/wlsbjmsrpDataSource-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
Replace the above entry with below -
<jdbc-system-resource>
<name>wlsbjmsrpDataSource</name>
<target></target>
<descriptor-file-name>jdbc/wlsbjmsrpDataSource-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
Basically you need to remove the targeting of this DS. Once done, save the config.xml and try to start your admin server now.
When (in future) you want to use Reporting feature of OSB, just provide the details of DB in the connection pool of datasource "wlsbjmsrpDataSource" and target it to the OSB servers and you will be good to go.
Regards,
Anuj