OSB 11.1.1.4 is a separate installation and it doesn't get installed on top of earlier version.
You can download the software from OTN
Software required are
1>Weblogic SErver 10.3.4
2>SOA Suite 11.1.1.4
3>Oracle Service Bus 11.1.1.4
4>RCU 11.1.1.4
5>Database 10.2.0.3+
In my case i am setting up SOA Suite also hence SOA Suite is also required.
The installation step for SOA Suite 11.1.1.4 i have already mentioned in my previous post.
This is basically a continuation of that post.
We will first see how to install OSB 11.1.1.4 and then how to create a domain for OSB.Instead of extending the existing SOA domain,I have created a all new domain containing both SOA and OSB,however we can also extend an existing SOA domain to include osb in it.
Further in my installation i have installed SOA Suite first and then OSB however it is recommended to install OSB first If you are planning to install OSB along with other SOA Suite components.
So here goes the installation screenshots for OSB on top of weblogic server 10.3.4
Download and exxtract the software.Once extracted run the .exe file to start installation.
Once this command prompt will come,Provide the JAVA_HOME For the weblogic server you have installed earlier and enter
Now to create a domain
Go to MIddleware_home\Oracle_SOA1\common\bin
and click on config.cmd a gui will come up like this
Now here is one important step you need to take care of ,The OSB JMS Reporting Provider by default uses its own DBMS/Services port ans Schema Owner,
Also the database vendor it uses is Derby and you need to change it manually so if you will proceed with default values only you may end up with error like this.
and if you will proceed with this you will get further more error
Component Schema=OSB JMS Reporting Provider
Driver=oracle.jdbc.OracleDriver
URL=jdbc:oracle:thin:@localhost:1521:orcl.idc.abc.com
User=FMW_SOAINFRA
Password=********
SQL Test=SELECT 1 FROM DUAL
Listener refused the connection with the following error:
ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
CFGFWK-60850: Test Failed!
Though the same SID Was working fine for other schemas,don’t know the exact reason for this issue
A bit of idea on Derby,It is an evaluation database included in weblogic server.
It has been mentioned properly in the Oracle document
http://download.oracle.com/docs/cd/E14571_01/doc.1111/e15017/before.htm#BABCJHDJ
In a development environment, you can use Derby, an evaluation database included in your Oracle WebLogic Server installation. In this case, you are not required to use RCU to create and load schemas if the Oracle Web Services Manager functionality for Oracle Service Bus is not required. Be sure to select Evaluation Database if you are using the Custom installation option to install Oracle WebLogic Server. If you are using the Typical installation option, the Evaluation Database is installed, by default. Reporting tables for Oracle Service Bus are created in the Evaluation Database when the server starts up for the first time. If you are using Oracle Fusion Middleware Configuration Wizard to create the Oracle Service Bus domain, configure the database type reporting as Derby, and set the password appropriately. You can ignore the Test Connections action in the wizard because the Evaluation Database starts only when Oracle WebLogic Server is started.
But since we are not using development environment we will go ahead with the RCU.So we will make some changes in the JDBC Schema connection to point it to RCU and Oracle driver as shown
Please make sure the sid you have provided is correct,As for my case it was strange other schemas were working fine with domain name however OSB JMS reporting provider was not wokring fine with domain name in SID as you can see at my end.
Just in case If you would have proceeded with the default set up(Derby) finally you would have received the following error in your console while starting up admin server as shown.
2 comments:
Now I know why Oracle recommends to install OSB before SOA. If you do that, than RCU automatically uses the SOA infra and not Derby. Thanks for these steps (and daring to install OSB after SOA)
Also, regarding why you got the error in one of the screens, its not becaues of the schema, but becoz of the port number, which is 1527.
Yes Arun you are correct.
Post a Comment