Skip to content

The Ordeal of Installing Oracle Service Bus on a Windows-based developer workstation

This is a genuine installation procedure which I wrote, but you might want to read it for its other values.


OSB installation in a development environment consists of a completely separate Weblogic instance and yet another ‘special installation’ of Eclipse. You can’t use existing Eclipse installations. Nor is it recommend to use one of the five other existing Weblogic instances that Oracle products thoughtfully demand their own copy thereof (SOA Suite, I am looking at you).

Installation process

This is the procedure for installing OSB development environment.

As network firewall policy prevents the downloading of files, you will need to use installation media located within <companyname> network. Take the files conveniently stored on network server <location redacted> and copy them into a directory on your local computer. This directory is hereafter referred to as ‘installation files directory’ below.

Install Weblogic

  1. Go to the installation files directory.
  2. Run the executable file wls1033_oepe111150_win32.exe
  3. This action launches the Oracle Installer for the Weblogic instance. It takes some time to run so contemplate the meaning of your life for a few minutes while it does. Maybe get a cup of tea. Stretch your legs. Think about lunch or your next holiday. File a support request for more memory. You should get at least 8GB.
  4. Okay that’s it, you’ll finally see the Oracle Weblogic installer. Think about the fact that Oracle sees fit to put “instructions” on the first screen telling you what the “Next” button does. This is advanced JEE server technology you’re installing, and potentially, Oracle think you don’t know what the “Next” button does. Maybe this reflects the level of experience inside Oracle, or perhaps it is indicative of the depth of respect in which Oracle holds their customers.
  5. Press the “Next” button. The next screen you will see  is very important. If you fsck it up you’ll have to uninstall and start over. It does not have any instructions, but that’s OK, we’ve done it here in this wiki page for you. Pay attention.
  6. DO. NOT. ACCEPT. THE. DEFAULT. Especially if you installed SOA Suite or some other Oracle product before you installed this one. Double especially if you still want that product to work.
  7. SELECT “Create a new Middleware Home” (THIS IS VERY IMPORTANT)
  8. TYPE a name of an Appropriate Directory. I used “C:\Oracle\OSB_Middleware”
  9. PRESS The “Next” button. Use the “Back” button if you need to see the instructions about how to use the “Next” button that Oracle conveniently provided for you on the first Screen. No, don’t do that. If you do that you’ll probably have to do this proceedure again and it will just make this entire experience last longer than it needs to. This is not a recommended practice.
  10. The next screen demands that you give Oracle your Email Address to get “security updates”. It also wants a thing called your “My Oracle Support Password” (I suspect this is what might have been known as Oracle TechNet). As we both know, the best possible security measure is not to give out your password to strange programs that demand it.
  11. As I planned on giving them my <workcompany> email, and as my Technet sub doesn’t use that Email address, I also unchecked the “I wish to receive security updated via My Oracle Support” check box.
  12. Are you Sure? YES I’M VERY SURE. I would like to be “ignorant of security updates” and also Oracle spam. Ignorance is Bliss.
  13. Look at that, I can’t give them my email address after all, what they really meant was “type your Oracle Support user id”. Press “Next”.
  14. Now you have to choose whether you want a “Typical” installation or a “Custom” one. I chose “Typical”, which, being an Oracle installation, I expect to require an 8-core 64GB RAM 2TB SAN SSD -based supercomputer with a external 4-way Oracle RAC for configuration (“infrastructure”) DB in order to have enough grunt to service about 3 requests a minute. Press “Next”.
  15. There’s a lot of choices here about the various subdirectories under the Middleware Home Directory that you created further back. I recommend accepting the defaults, but you can probably cause yourself countless of fun trolling on the My Oracle Support forums as you get ever-more-desparate for a solution to a very obscure problem that the phone support have no idea about and that was likely caused by you mucking about these defaults, causing the support personel to simply recommend you to reinstall the product, if you really feel the need to change them here.
  16. If you can remember the instruction about the use of the “Next” button at step 4, then Press “Next”.
  17. Now you can choose whether you want to put the shortcuts for “All users” or just you (“Local user”). If you are the BOFH I recommend “All Users”. As this is the default, we can all safely assume that the BOFH works for Oracle and is now responsible for designing their installation processes. Accept the default, and press “Next”.
  18. The next screen is a summary of what you’ll be installing. You can also select each item and see a summary of what it does. Ponder the mystery of Oracle, and press “Next”.
  19. Keep pondering that mystery while Oracle Weblogic Server 11g Release 1 ( is installed. It takes a little bit of time. While it does that, you might to book that Holiday, get another cup of tea, or chase up that support request for the additional RAM you’ll be soon needing.
  20. Congratulations! Installation is complete.
  21. I opted to leave the “Run Quickstart” option checked.
  22. Press “Done”. There are no onscreen instructions for this button.
  23. Quickstart will run. It’s just a link farm.

Install Oracle Enterprise Pack for Eclipse (OEPE aka “Special Eclipse”)

  1. Go to the installation files directory
  2. Extract the file … I used 7zip and made sure to put it into a subdirectory of the installation files directory.
  3. It’s kind of pretty big, takes a cople of minutes.
  4. Just like a regular version of Eclipse, once this is unzipped, it’s installed. However it’s not a regular version of Eclipse. It is a “special” Eclipse that went to “special” school.
  5. Although this directory can probably live anywhere, it’s a good idea to copy this directory into the new Oracle Middleware Home that you created when you installed Weblogic. Look I really have no idea why this is the case, however, it’s not good to anger the Oracle by using you regular development directories. ORACLE_HOME sweet ORACLE_HOME it is then.

Install OSB and OSB Dev Tools

  1. Go to the installation files directory.
  2. Extract the file … again I used 7zip and made sure to put it into a directory underneath the installation files directory.
  3. Enter this directory. Enter the directory “osb” that will be created underneath it. Note that even though the file said “disk1_1of1″ in the file name that underneath here there’s two directories, Disk1 and Disk2.
  4. Go into the directory “Disk1″
  5. Run the executable file “setup.exe”
  6. A DOS window opens which asks you for the location of a JRE in order to use Oracle Universal Installer. Probably. Exactly why the Weblogic installer didn’t need to know where the JDK was, I do not know. Probably it used a sensible installer rather then the Oracle Universal Installer. I don’t ever think I’ve ever seen an machine with two Oracle installations on it that didn’t also have two or more installations of the Oracle Universal Installer also installed on it. Its name perhaps means that it installs itself universally, rather than it is a product which has a universal use for installing other software. Ponder the mystery of the Oracle.
  7. A JRE will be located in the original Oracle Middleware Home that you created when you installed Weblogic. In fact there’s at least two (Sun JDK and JRockit). Use the Sun JDK. For example, my value for the JDK was “C:\Oracle\OSB_Middleware\jdk160_18″. Press Enter.
  8. Now the Universal Installer will actually attempt to install something. It says “You are about to install the Oracle Service Bus (OSB) and may install the Oracle Service Bus IDE and Oracle Service Bus Examples (OSBE). Before proceeding, make sure that you have installed and configured Oracle WebLogic Server 11g. If you want to design OSB applications in Eclipse, make sure Oracle Enterprise Package for Eclipse (OEPE) is installed.” Which is all true if you’ve been following this guide.
  9. Press “Next”. There’s no instructions in this program for the use of the “Next” button. Someone ought to file a change request for that.
  10. Now you can choose whether you want a “Typical” installation or a “Custom” one. Typically, choose “Typical”.
  11. Press “Next”. I tried looking for online help here about the use of the “Next” button but I did not find anything.
  12. It does a prerequisite check. It should pass, and if it doesn’t, you are probably screwed. If it does, you will be able to Press “Next”
  13. At this next screen DO NOT ACCEPT THE DEFAULTS.
  14. Choose the Oracle Middleware Home that you installed the Weblogic into at the first part of this installation procedure. E.g. I chose “C:\Oracle\OSB_Middleware”.
  15. Once you do the previous step, ff you followed the instructions for the Special Eclipse (OEPE), it will have found it automatically. If not, choose the location where you installed the Special Eclipse (OEPE Location). For example, my value was “C:\Oracle\OSB_Middleware\oepe-galileo-all-in-one-″
  16. Press “Next”. Did you know that the Oracle at Delphi was a priestess called the ‘Pythoness’ who answered your question using gibberish verse. A Male Attendant of the Pythoness interpreted her raving mad gibberings and told you what they meant. For a fee. Does this sound familiar?
  17. Review the installation details. When you are sure they are correct, press “Install”.
  18. OSB will now install. It takes a little time so run those errands, go to lunch, get a coffee, dream of the Holiday you just Booked. I’d tell you to install the new 8GB of memory that you ordered before which surely has arrived by now, but that would mean turning your computer off. Best to wait until it’s finished then.


  1. Jim Nicolson wrote:

    Excuse the long comment. I wasn’t sure of your email aaddress.

    I read your Oracle 11G installation experiences with sadness, agreement and amusement :)

    After returning to Brisbane after some time off overseas, and as a way of refreshing my Oracle product knowledge, I just did my version of the OSB 11G OSB install process. I have spent a long time with BEA products including a good two plus years with ALSB/OSB. BEA products used to be such a straight-forward install.

    Of course, I did something slightly different from one of the large number of sanctioned install paths described in ugly detail in the documentation. I used the separate Helios version of OEPE. (oepe-helios-all-in-one- It is installed in the correct location in Oracle/Middleware.

    In the version that you installed, have you successfully tested creating an OSB Business Service (end-point) using the new EJB 3 transport? I’m getting an error within Eclipse on the EJB Transport Configuration. So,Mr Google has lead me to your blog.

    The error I’m getting is reported at the top for the EJB Configuration Tab (and hence not a ‘normal’ error) as ‘Generate: Error during generation of the WSDL. Cannot run program “null//modules/org.apache.ant_1.7.1/bin/ant.bat”: CreateProcess error=2, The system cannot find the file specified.’

    The ant.bat file is present in the listed location.

    In normal circumstances I would treat this as either an installation bug or that I’m using incompatible software components. e.g. In this case, the fact that the version of Eclipse Helios/ OEPE is more recent than OSB is a candidate for incompatibility.

    Since a) I’m just Joe IT Architect, and not currently a customer and hence not of interest to Oracle Support, and b) have been through the install process twice with the same result, AND c) the install of OSB seems to apply updates to both OEPE and WLS installs, which implies I’d have to do it all again using

    Regardless, to extend your observations on the ordeal of the OSB install process, this set of interdependencies and the overlapping of installs is going to be a major problem moving forward.

    Now I know Oracle would like Eclipse to disappear and be replaced by JDeveloper but… I can’t see any way that the current Eclipse OEPE can be updated to a later version of Eclipse without a re-install of both WLS and OSB.

    i.e. How would one migrate from the Galileo OEPE to the Helios OEPE. So I test some options.

    I first tried to see if I could manually adjust with the Galileo Eclipse configuration to match Helios. The necessary plug-ins are actually installed into the OSB sub directory. I found it just too complicated to find the necessary bits to update.

    Next, I tried the Oracle Universal Installer from the Start Manu item hoping that maybe it had an update existing install option. It started a command session and then exited with a helpful dialog along the lines of “Command line argument invalid”

    Ok, I decide to execute the Oracle Uninstall Service Bus from the Start Menu, also hoping that it might have an update install. But no, what the first tab (Uninstall Oracle Home !) tells me is that if I remove Oracle Service Bus, this will render the Application Server in this home unusable. Since Oracle proudly proclaims the virtues of this central Middleware Home, it probably implies that installs of other products like (say) JDeveloper and SOA Suite are probably also rendered unusable.

    So some serious testing of how this software environment will be managed in the real world would need to be carried out before attempting to migrate from an earlier version of WLS/OSB. Currently, this doesn’t look workable from my perspective.

    Tuesday, August 24, 2010 at 13:45 | Permalink
  2. Scot Mcphee wrote:


    Thanks for your comment and illumination of your experiences. No I’ve never used the EJB3 transport for an OSB business service. I’m currently working on what is basically a messaging solution with OSB components to do some transformation of messages read off topics. So our deployment looks like some JMS queues and topics with a couple of components putting messages into them, a big chunk of Java – several EJB3 MDBs with a bunch of POJO in the middle – and another OSB component getting the result off a JMS topic and using Xpath transforms to send the message onto an external web service.

    We’ve found you have to have installations of OSB and even SOA Suite in separate middleware homes in a Dev environment. There’s so many moving parts and potential conflicts of sub-components it can just drive you crazy at times. Best to just make sure you’ve got the versions that Oracle says to use.

    Tuesday, August 24, 2010 at 18:56 | Permalink