Oracle Service Bus 11gR1 (OSB) Installation

This document talks about the OSB 11g installation that I implemented in our Windows 64 bit Dev ENV. Oracle has got this product into their kitty after BEA acquisition, which was known as Aqua Logic Service Bus (ALSB) earlier. After the acquisition of BEA, Oracle had rebranded ALSB as Oracle Service Bus (OSB).

The following are the prerequisites for OSB11g installation:

• WebLogic Server 10.3.6

• 64-bit Jrockit JDK – If we are using generic installer for WLS

• Oracle Enterprise Pack for Eclipse (OEPE)

• Repository Creation Utility (RCU) – If we want to create domain with OWSM extension

Note: To select the compatible version of OEPE follow the below chart.

OSB Weblogic

Server OEPE

11.1.1.6.0 10.3.6 11.1.1.8.0

11.1.1.5.0 10.3.5 11.1.1.7.2

11.1.1.4.0 10.3.4 11.1.1.6.1

11.1.1.3.0 10.3.3 11.1.1.5

WebLogic Server (WLS) Installation: The WLS 10.3.6 can be downloaded from https://edelivery.oracle.com/ .In that link, we can see the installers for 64-bit JVM for both windows and Linux and also a generic weblogic installer. Since we are using 64-bit machines download OEPE and the generic weblogic installer.

We will go through the installation with the use of some screenshots:

1) Click on the jar/executable file download that brings up the following screen.

2) Click on Next to create a new middleware home by entering the location

3) Click on Next twice and choose the install type as Typical and proceed to JDK selection screen.

4) The generic installer does not ship with any JDK as you see in above screenshot, so install the 64 bit JDK and select that location for local JDK. Click

on Next till the final screen of the installation process and you will see the following screen once the installation is completed.

OEPE Installation: Since generic installer of WLS does not have the OEPE, we have to install the OEPE separately. Download OEPE of Galileo version from oracle for 64-bit platform and unzip this in the same location as middleware home as shown below:

OSB 11g Installation: Locate the Downloaded OSB 11g, unzip it and click setup.exe in Disk folder that brings up the following screen and enter the 64-bit JDK location.

1) Click on Next that brings up the following screen. Here you can observe that WLS and OEPE are prerequisites for OSB development. Since we already installed these, proceed to next step by clicking on the Next.

2) In the next screen, Select the install type as ‘Typical’ and click on Next twice that brings up the following screen, where we need to specify the Middleware home along with the locations of WLS and OEPE. These locations will be defaulted on choosing the middleware home, otherwise browse the locations manually.

3) Click on Next to review the install summary and click on Install. The following Installation Completed screen will come up once the installation is done successfully.

With this, we are finished with the OSB installation.

The development platform for OSB is Eclipse. To verify the OSB related plug-ins installation, open Eclipse and select Help –> About Eclipse Platform. The last two icons as shown in the below screenshot indicates that OSB related plug-ins are installed and Eclipse is ready for the OSB services development.

Notes:

Though OSB is installed successfully, sometimes the OSB related plug-ins will not be visible in Eclipse IDE. To resolve this issue, try reinstalling OSB again and also make sure that the file ‘oracle.osb.ide.link’ has the entry pointing to your OSB installation directory like path=M:/Oracle/Middleware/Oracle_OSB1 and the file can be found in the location $MW_HOME/<<OEPE Install dir.

Using Repository Creation Utility (RCU) This section is in continuation to the previous section that talked out the OSB installation and setup of Dev environment in Eclipse IDE. In this section, we will see the database dependency of OSB.

Much of the functionality provided with Oracle Service Bus (OSB) does not have any database dependency. Refer to the oracle blog post here that talks about the same. But there are 2 reasons why we need to look into database as well: • OSB Reporting functionality which is provided as one of the service

monitoring features needs database tables to store reporting data. By default, derby internal database is used for this purpose or we can configure to use any other schema during WLS domain creation.

• And one of the major features included in OSB11g is integration with the Oracle Web Services Manager (OWSM). OWSM provides policy based security solution to secure the proxy services. These out of the box OWSM policies are provided in the metadata store (MDS) that requires a database. Refer to this link for more information on OWSM and FAQs at this link.

These required schemas can be installed into database using repository creation utility provided by oracle. Since we are using OSB11g (11.1.1.6) download the RCU 11.1.1.8.0 from think link. Different schemas that can be created using RCU can be found here. If we are planning to use OWSM with our OSB installation, we will see how to install this MDS using RCU.

If we want to use Oracle XE as a database, then we should update the database parameters once after the installation. Set the processes parameter to >=200 using the following instructions. sqlplus sys/<your password>@XE as sysdba SQL> show parameter session SQL> show parameter processes SQL> alter system reset sessions scope=spfile sid=’*'; SQL> alter system set processes=200 scope=spfile; SQL> shutdown immediate SQL> startup SQL> show parameter session SQL> show parameter processes

Unzip the downloaded RCU zip file to any folder in the file system and call this as $RCUHOME. Run the file $RCUHOME/rcuHome/rcu.bat that brings up the below screen with options Create and Drop. We can use same utility to drop the existing schemas as well.

Click on Next to bring up the next screen and give the installed database details.

Click on Next. At this stage the database compatibility check will happen and the following error will be shown if the database is incompatible.

If the compatibility check is successful, we will get the following screen with successful message after checking the prerequisites.

Click OK on check prerequisites and proceed to next screen where different schema components can be selected. Give the new prefix as DEV (or some other value you are comfortable with) and select metadata services if we just want OWSM. And select SOA Infrastructure component if you are planning to

install SOA Suite as well. So select all these and observe the schema owner column.

Click Next and click on OK, once another prerequisites step is also over. Proceed to the next screen where we can mention the password for each schema that we want to create. Based on preference, we can give the same password to all the schemas or different password for each different schema.

Once everything is successfully completed, we can see the following screen with completion details.

To verify the successful schema installation, we can go to mgmt. sql screen and login with the respective schema user name and password.

Helpful Links:

OSB

http://docs.oracle.com/cd/E14571_01/doc.1111/e15017/apm.htm

Creating WebLogic Domains Using WLST Offline

http://docs.oracle.com/cd/E23943_01/web.1111/e13715/domains.htm