Instead of having a separate home for the rest of the app server components like Portal, and another home for Discoverer, you can now install both these components in a single Oracle Home (as in previous versions like 9.0.2 and 9.0.4).
Assuming that you have already installed your infrastructure, you can straightaway select the first option - Oracle Application Server 10g - as the product to be installed.
The Business Intelligence and Forms install type is back in phase 2!
Since I need to use Discoverer portlets I have checked Portal. I don't plan on using Wireless or Reports or Forms functionality on this instance, hence I have kept them unchecked. Note that I can always go back and install these components after installation. I don't need to do an uninstall and re-install.
Since this installation will require to be associated with an infrastructure, I have to specify the host name where the infrastructure is installed.
I can now specify the OID login (my infrastructure orcladmin password) to allow the middle tier to be associated with the infrastructure's IM.
Nothing new in this screen: you specify a unique instance name and a password.
Before the installation begins you are shown a list of all products and components that would be installed.
Notice the Discoverer version - it is not 10.1.2.0.2 as one may expect, but 10.1.2.1.0.
Ready for some version soup? Here goes: the Discoverer Plus / Viewer version itself is different! At the time I took these screenshots we were testing the 10.1.2.48.16B shiphome.
So the Oracle Application Server version is 10.1.2.0.2. The Discoverer version is 10.1.2.1.0. And the actual Plus / Viewer version is 10.1.2.48.16 (or 17 0r 18 etc...)!
Here is how it works: basically any component that was present in 10.1.2.0.0 but has been change because of bug fixes or UI changes, etc... is renamed to 10.1.2.1.0. Any components that are new to phase 2 are named 10.1.2.0.2. Unchanged components still carry the 10.1.2.0.0 version number. Trust me, I have to refer to my emails and notes to get this right! Who says the tough part of software is writing it?!
If your standard web port 80 is free, then the middle tier will use this port. Makes life much simpler as you do not have to type in the port number after the host name. Asking users to type in a port number like 7777 or 7779 is simply asking too much from end users.
Note: these screenshots are based on pre-production software, so all the usual caveats about this being subject to change, etc... apply.