Oracle service bus 11g r1 installation


Published on

1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Oracle service bus 11g r1 installation

  1. 1. Oracle Service Bus 11gR1(OSB) InstallationThis document talks about the OSB 11g installation that I implemented in ourWindows 64 bit Dev ENV. Oracle has got this product into their kitty after BEAacquisition, which was known as Aqua Logic Service Bus (ALSB) earlier. Afterthe 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 extensionNote: To select the compatible version of OEPE follow the below chart. Weblogic OSB OEPE Server 10.3.6 10.3.5 10.3.4 10.3.3 Server (WLS) Installation:The WLS 10.3.6 can be downloaded from .In thatlink, we can see the installers for 64-bit JVM for both windows and Linux andalso a generic weblogic installer. Since we are using 64-bit machines downloadOEPE and the generic weblogic installer.
  2. 2. 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 location3) Click on Next twice and choose the install type as Typical and proceed toJDK selection screen.4) The generic installer does not ship with any JDK as you see in abovescreenshot, so install the 64 bit JDK and select that location for local JDK. Click
  3. 3. on Next till the final screen of the installation process and you will see thefollowing screen once the installation is completed.OEPE Installation:Since generic installer of WLS does not have the OEPE, we have to install theOEPE separately. Download OEPE of Galileo version from oracle for 64-bitplatform and unzip this in the same location as middleware home as shownbelow:OSB 11g Installation:Locate the Downloaded OSB 11g, unzip it and click setup.exe in Disk folderthat 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 thatWLS and OEPE are prerequisites for OSB development. Since we alreadyinstalled these, proceed to next step by clicking on the Next.
  4. 4. 2) In the next screen, Select the install type as ‘Typical’ and click on Next twicethat brings up the following screen, where we need to specify the Middlewarehome along with the locations of WLS and OEPE. These locations will bedefaulted on choosing the middleware home, otherwise browse the locationsmanually.3) Click on Next to review the install summary and click on Install. Thefollowing Installation Completed screen will come up once the installation isdone successfully.
  5. 5. 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. Thelast 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 willnot be visible in Eclipse IDE. To resolve this issue, try reinstalling OSB againand also make sure that the file ‘’ has the entry pointing toyour OSB installation directory like path=M:/Oracle/Middleware/Oracle_OSB1and the file can be found in the location $MW_HOME/<<OEPE Install dir.
  6. 6. Using Repository CreationUtility (RCU)This section is in continuation to the previous section that talked out the OSBinstallation and setup of Dev environment in Eclipse IDE. In this section, wewill see the database dependency of OSB.Much of the functionality provided with Oracle Service Bus (OSB) does nothave any database dependency. Refer to the oracle blog post here that talksabout the same. But there are 2 reasons why we need to look into database aswell: • 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 creationutility provided by oracle. Since we are using OSB11g ( download theRCU from think link. Different schemas that can be created using RCUcan be found here. If we are planning to use OWSM with our OSB installation,we will see how to install this MDS using RCU.
  7. 7. If we want to use Oracle XE as a database, then we should update the databaseparameters once after the installation. Set the processes parameter to >=200using the following instructions.sqlplus sys/<your password>@XE as sysdbaSQL> show parameter sessionSQL> show parameter processesSQL> alter system reset sessions scope=spfile sid=’*;SQL> alter system set processes=200 scope=spfile;SQL> shutdown immediateSQL> startupSQL> show parameter sessionSQL> show parameter processesUnzip the downloaded RCU zip file to any folder in the file system and call thisas $RCUHOME. Run the file $RCUHOME/rcuHome/rcu.bat that brings up thebelow screen with options Create and Drop. We can use same utility to drop theexisting schemas as well.Click on Next to bring up the next screen and give the installed database details.
  8. 8. Click on Next. At this stage the database compatibility check will happen andthe following error will be shown if the database is incompatible.If the compatibility check is successful, we will get the following screen withsuccessful message after checking the prerequisites.Click OK on check prerequisites and proceed to next screen where differentschema components can be selected. Give the new prefix as DEV (or someother value you are comfortable with) and select metadata services if we justwant OWSM. And select SOA Infrastructure component if you are planning to
  9. 9. install SOA Suite as well. So select all these and observe the schema ownercolumn.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 schemathat we want to create. Based on preference, we can give the same password toall the schemas or different password for each different schema.Once everything is successfully completed, we can see the following screenwith completion details.
  10. 10. To verify the successful schema installation, we can go to mgmt. sql screen andlogin with the respective schema user name and password.Helpful Links:OSB WebLogic Domains Using WLST Offline