Extend Pre-built Virtual Machine for SOA Suite with Oracle Service Bus

PeterPaul already showed us in his blog how to install a new wls server in the image and install the Oracle Service Bus in the new server.
In my blog i will use the wls of the SOA Suite and extend the domain with the Oracle Service Bus application.

Install OEPE

In the WebLogic home of the SOA Suite there isn’t an OEPE installed.
This will be needed for the OSB installation.

Download oepe-galileo-all-in-one-11.1.1.6.0.201007221355-linux-gtk.zip

Connect to the vm box as ‘oracle’ user and create a dir in the fusion middlware home

  cd /oracle/fmwhome
  mkdir oepe-galileo-all-in-one-11.1.1.6.0

Unzip the oepe zip in this directory

  cd oepe-galileo-all-in-one-11.1.1.6.0
  unzip /oracle/tmp/oepe-galileo-all-in-one-11.1.1.6.0.201007221355-linux-gtk.zip

Installation of the oepe in the weblogic home is done.

Oracle Service Bus

Download ofm_osb_generic_11.1.1.3.0_disk1_1of1.zip

Unzip the file and run the installer.
By default the middleware home which is selected at step1 is : /home/oracle/bea_default

Change this location to

/oracle/fmwhome

Now the installer will also see the correct location of the OEPE home.

Next, next and we’re done.

Extend Domain

Start the configuration wizard

  /oracle/fmwhome/oracle_common/common/bin and start config.sh

Choose to extend and existing Weblogic domain

Browse to the domain1 directory

Select the OSB components to include in the domain

When testing the db connection for the OSB JMS Reporting Provider use the xe connectstring.
Default password for all db schemas (soa_infra etc) is : welcome1

Start the server again by use of the ´Start/Stop WebLogic Server´ icon on the desktop.
Check the console urls to see if everything is still working

• http://localhost:7001/em
• http://localhost:7001/console
• http://localhost:7001/sbconsole

Eclipse

When you try to start Eclipse from the virtual box itself without parameters it will give some warning like

GC Warning: Repeated allocation of very large block (appr. size 638976):
        May lead to memory leak and poor performance.

Use : ./eclipse -vm /oracle/fmwhome/jdk160_18/bin/java

Updated

The first version of the blog showed steps on how to extend the domain so the osb server would run in his own managed server (All Domain topolgies)
On deployment of a composite it would fail with the next error

  Caused By: oracle.fabric.common.FabricDeploymentException: Unable to register service. {rootCauses=[]}

Lateron i will try to investigate this error. For now i updated the blog to make use of the ‘Single Server Domain Topology’, and now deployment of the composite still works and i can add resources in the OSB Console.