Overview

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 10.3.3.0 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 (10.3.3.0) 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 oepe-galileo-all-in-one-11.1.1.5.0.201003170852-win32.zip … 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 ofm_osb_generic_11.1.1.3.0_disk1_1of1.zip … 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-11.1.1.5.0.201003170852-win32″
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.

The problem for Glassfish, as the second sentence of this ServerSide article states (see it straight from Oracle’s mouth here, and see also here) is that Oracle view it as being used for “non-mission critical department apps”. Glassfish’s superior technology (or otherwise) just doesn’t come into it. It’s not a factor (as it rarely every is).

Not so long ago Oracle spent a big wad of money acquiring an app server (Weblogic) and then a stack of more money porting all its other products into it and branding the resulting mess platform “Oracle Fusion Middleware 11g”. Now not only do they have their third app server (OC4J/OAS, Weblogic and Glassfish), but the Sun product suite includes products that compete with various Fusion Middleware 11g products (portals, ESBs, and so on). So on one hand you’ve got a “departmental” application server, which you can either licence for free by downloading the open-source version, or buy support for the fancier ‘Enterprise’ version, and on the other, an expensive, full-stack-integrated (all the way to the IDE), fully-branded strategic platform that Oracle just invested a vast amount of money into, and have been pushing like crazy onto customers the past six months. And it is the same sales team that will sell both this licensed “departmental” Glassfish. Therefore if you say the magic words like “need a cluster” or maybe “we might build a portal”, or “we are considering adopting a service-orientated architecture”, lo and behold you’ll find the molto-dinero “Fusion Middleware” based solution installed all over your sorry arse quicker than you can say “can you please explain this per-core with special CPU-architecture-loading-factor licencing schema to me once again and why is it a different price if I upgrade my hardware without adding any additional cores???“.

Let’s dissect those “key points” of Oracle’s strategy announcement:

Key Point	What they meant to say
GlassFish continues as the Java EE reference implementation and as an open source project.	We see it as the way to dominate the direction of Java EE for at least two years, but for Larry’s sake don’t try to use it in production.
Oracle’s strategic application server, Oracle WebLogic Server, together with GlassFish, provide world class Java EE infrastructure.	Oracle’s strategic application server, Oracle WebLogic Server something something something provide world-class something something infrastructure.
GlassFish Enterprise Server and WebLogic Server expected to share core components.	We are the Borg. Resistance is futile. You will be assimilated.
Oracle plans to add GlassFish Enterprise Server all WebLogic offerings.	Hey, look at this cute free “reference implementation” thingy that comes free with Weblogic! You could use that to run your departmental Wiki instead of having to pay us another fortune for more Weblogic licences. Did you say “WIKI”? Did we tell you all about the great wiki-like Enterprise 2.0 features available in the Oracle Fusion Middleware 11g offering? How many test environments did you say you needed licences for?
GlassFish Web Stack maintained for existing customers.	Not available for sale.
GlassFish Message Queue remains as the GlassFish messaging infrastructure.	We’re not expecting to sell any licences of this. Just use Oracle Fusion Middleware’s SOA Suite 11g already. We’re fairly sure that’s got a message queue in it.
Oracle plans to license GlassFish Enterprise Server and Java System Web Server with all WebLogic Server offerings.	See above.
GlassFish also available as standalone offering.	Are you sure you didn’t mean to say “Weblogic”? No? Can you call back next Thursday at 2pm and ask for Fred? We’re reasonably certain he might know something about that Glassthingy.
GlassFish will continue to be supported and maintained for an extended time period for customers current on support.	Well, the lawyers said we had to. We know how to do this. Ask any 10g customer.
GlassFish open source projects thrive	As long as we will let them.

I know I’m a completely cynical bastard about these things, but I will wager within a few months that even if you deliberately ask for Glassfish Enterprise directly that you’ll have to fight off the Weblogic borg absolutely tooth and nail to the last man as they repeatedly try to board your IT department brandishing their integrated-wizard-driven Red Stack. I predict that, basically, after a year of not even trying to sell any Glassfish licences – because if you ask for any of the features that are in the licenced version and not the open-source one, you’ll be pushed to Weblogic (and anyway, at ten times the price they’ll prefer to sell you Weblogic as a default position, after all “Glassfish comes free with Weblogic”) – Oracle will announce, “there’s no sales in it”, then probably ditch the licenced Glassfish version completely, leaving only the open source version. Finally sometime after that they’ll cut the open source funding off and it will have to limp along without hardly any of the resources it formerly had. Maybe they’ll donate it to the ghetto of an Apache incubator project where it can die unnoticed a couple of years after that. It’s a pity because IMHO Glassfish is ten thousand times a better app server than anything Oracle ever produced, or even bought before this.

My case-in-point du jour is Oracle’s new Rich Enterprise Applications site and the associated technology. On that site you will find a flash presentation of their technology around delivering and I quote:

multi-channel capable applications that deliver desktop quality, highly interactive user experiences that are pre-integrated to enterprise class server technology.

That sounds pretty good, might be of interest to me. Lets investigate further. Now, a lot this technology is built on top of standards, like JSF, and other commonly used technology like AJAX. The earlier version of the ADF component technology was donated to Apache where it lives as the Apache Myfaces Trinidad project. The new components are built on top of these open sourced components. So far, so much is OK.

But, the kick in the tail can be seen in even just in the quoted sentence above: “pre-integrated to enterprise class server technology” – they certainly don’t mean Tomcat, right? The point of the presentation is induce lock in. However I’m still willing to cut them some slack on this particular point. Of course, if you are thinking about using Oracle’s JSF technology, you probably are already committed to Oracle’s middleware technology anyway – and Weblogic is a perfectly good application server, if you need such advanced capabilities (and whether you actually do is another question for another day).

But what absolutely does my head in, is the insistence the only way to develop for this technology is to write it using their proprietary, non-standard developer technology, aka JDeveloper. This is the point where I have to say, I’m sorry Oracle, but … FAIL. I actually don’t even care if your IDE is even the world’s best! Or even if it comes as an Eclipse plugin. My beef with this sort of IDE integration is the total mind-set that it embodies. The IDE might have all the drag-and-drop interface-building mojo in all the world, but the code it produces will never, ever, stand up to a hand coded model driven off the target domain, using modern agile development techniques that are designed to ensure the most cost-effective, best-quality development delivering timely business process transformation (aka value) that the enterprise prioritises and chooses. Just look at the ADF FAQ on the Oracle Wiki. Half the questions are related to the IDE. Here’s a tutorial style introduction that just assumes JDeveloper as the default way to get access to the Oracle JDF components.

No, no a thousand times NO!

The biggest insult is the way that developers are treated as mere commodities in this whole process. They are just the warm bodies occupying the chair driving the interface. Much like the continually failed dream of developerless development, their primary skill is seen as not “being a programmer” but “being a driver of a software package”. If I said, my financial skills and experience include 10 years Excel and 5 years MYOB – I can haz CFO jobz now? NO?! Why not? It’s insulting, that’s why not.

Software development is a profession, or at the very least a craft, and software developers should be able to choose their own tools. Obviously, some agreement has to be made organisationally, or at least across a single team or a whole project, to use a certain common toolset. Here’s one possible checklist:

We’re writing a Java app, check. Deploying onto Weblogic, check. Database is Oracle 11g, check. We have Scrum as our process framework, check. TDD is in our list of favoured engineering disciplines, check. Maven is our chosen build tool, check. Using Subversion for version control, check. Hudson for a continuous integration server, check. Writing the interface with Oracle ADF, check. Using Crossfire to deliver our web services, check. Spring for application wiring, check. Hibernate for persistence, check.

Each of these things has to be agreed upon at an architectural and organisational level (and obviously I don’t mean to say that each of the above is the only choice for each type of item, I’m just giving examples).

You should note one very deliberate omission from that list, the IDE. Architects might impose a certain application server, a particular approach to application layering, and so on. The developers – at least the senior ones – have to choose and agree, for example, on whether to use Ant or Maven, CVS or SVN, Cruisecontrol or Hudson. But what they do not do, is force developers to favour Eclipse or IntelliJ or Netbeans or JDeveloper. What is the point of taking someone who is super-productive with a particular IDE’s keystrokes and then forcing them to spend six months learning a whole new set, a new environment? That’s not productive! A developer needs to have the IDE get out of the way, become second nature – they need to be thinking about code, not where the menu is for the rename-method refactoring because they are unfamiliar with the keystrokes of the unfamiliar IDE. Keystrokes are muscle memory. You just think, rename this method and your fingers are already on the keys you need to press, without breaking your all-important flow. That’s how a developer is as productive as they can be. A productive development team should have a mix of IDEs (I’d propose that this would be statistically in proportion to the usage patterns of the common IDEs). Then we have the specific example of JDeveloper. I won’t even go into it except to say I’ve never heard a developer do anything but curse it, or maybe laugh at it. But it’s the laughter of the condemned man.

It’s something that vendors really need to get serious about. Rather than presenting me with a seamlessly integrated vision, from developer’s screen, through application server, to user’s screen, their technology presentations ought to think discrete. Each piece of technology ought to live and die on it’s own merits, something I’m sure Oracle’s ADF is perfectly capable of – without JDeveloper. If it’s not capable of being developed productively without JDeveloper, it’s already in the reject pile as far as I am concerned.

This essential information needs to be right up front. Don’t bury the information a thousand web sites deep in your developer portal. Put it right there in the first presentation! Separate the selling of the developer tooling from the selling of the user presentation frameworks and the server technology. Show me how I integrate Oracle ADF into TDD, into continuous integration, into the IDE of the developer’s choice. Because if you don’t, you’ve already lost me as a potential customer. This is the real future of software development. Look at where the major thought leaders of software development are taking development – open source frameworks, inversion of control, TDD, Domain Driven Design, Domain Specific Languages, Agile Methods, delivering real process transformation and business capability as early as possible – not drag and drop with wizards. FFS.

I’ve worked on a successful (JSR168) portal implementation, just last year. I truly don’t see what the concept of ‘portal’ brings to a web application beyond what could be simply programmed into a customised web application. We used Spring MVC Portal running under Websphere Portal and calling back-end services deployed on a BEA Weblogic server using Spring remoting (note: not WSRP which would have probably massively increased complexity). The reason this mix of platforms (Websphere and Weblogic) was used was political, not technical. I believe the whole use of portals in general tends to follow organisation’s political and not technical needs.

Despite all that, overall the custom portlets and the project as a whole was quite successful and the customer satisfied with the result. However I felt the most difficult aspects of the project were the parts of the deployment that were left to the portal container to provide. These are the things that are touted as the ‘advantage’ using a portal container over a simple custom-built web application. Content management features caused the team members delivering these enormous headaches (and late nights) and the same can be said of the authentication and authorisation mechanisms employed. I felt we could have easily delivered these components using known JEE development APIs with all the customisation required by the customer in at least an equal amount of time.

As a contrast, we used Tapestry 5 to develop (actually, completely rewrite from an earlier phase one version in dire need of improvement) an administration component as a straight web application deployed into the Weblogic server. This took a pair of us less than two weeks to write using a functional-test-driven approach and delivered a very nice web app.

The issue of portal containers and standards being a political rather than a technical concern is particularly pertinent to me at the moment because it looks likely in the near future I’ll be working on another portal implementation for another client. I can’t be more specific regarding this but this particular client had already bought the portal server from a vendor and then approached consultants in order to get an actual implementation completed. Of course, no requirements gathering or analysis was done to determine if the portal solution was indeed the right one – the vendor’s sales team effectively provided the assurances of product suitability. Because the money is already spent and reputations already staked on the portal platform there’s no possible way a better solution can be suggested by any technical expert at this stage.

In my view, that’s the “relevance” of portal servers in the Java world. Vendor sales teams love to sell them.

Update

Jakub Holý makes an excellent observation about validity of the concept of a portal server:

It’s a pity that portals and portlets aren’t easier to use and haven’t made it into the mainstream, the abilities of content aggregation, personalization, uniform security etc. are promising and as we can see in the rise of personal mashups like iGoogle, the fundamental ideas behind portals are still valid and extremely attractive. I hope that some mashup technology will soon provide a viable, light-weight alternative to portals.

That’s an important point: iGoogle is the most widely used example of a “portal” architecture. The modern trend towards the “mashup” (especially in social software) also shows the idea to aggregate different web applications under a common view, with security and other features is a valid one: it’s just the bloated, slow specification process, and predatory vendor sales departments that are stopping real innovation in this space in the Java area. Hopefully some light weight technology will soon emerge from among something like Spring, Tapestry, and GWT to produce a “portal” server that delivers actual value, and ease of development, deployment and usage, in a corporate context.