In this post I will go through the software installation process for an 11g PS2 SOA cluster. I will build on top of the environment described in my previous post.
I am installing my middleware into a shared middleware home so I only need to install it once. The final structure of my middleware software installation is shown below.
The SOA cluster will host a couple of web servers for resiliency and these will load balance across the WebLogic servers. I installed the 64-bit version of Oracle HTTP Server (OHS) as I was running on a 64-bit OS and would be using a 64-bit JVM. It is a good idea to match the OHS to the JVM, either both 32-bit or both 64-bit. The web server is part of the Oracle Web Utilities download.
First I ran the installer for Web Tier Utilities 18.104.22.168. I created an Oracle Inventory in /u01/app/oraInventory. I selected software install only, not install and config. Although the EDG says to do an install and config I find it easier to completely separate the configuration from the software installation because it allows me to do instance creation and WebLogic server registration as part of the same configuration step. It also makes it easy to keep the software on a shared storage device, in my case I am only using one share storage area for the software although in production I would want two so that I could do a rolling upgrade.
I installed the software on a single machine into the /u01/app/oracle/product/fmw middleware home that already contains my JRockit JVM and JRockit Mission Control. I set the Oracle Home to be Oracle_WEB as this is the web utilities I am installing.
After installing 22.214.171.124 I then ran the 126.96.36.199 upgrade, again choosing /u01/app/oracle/product/fmw as the middleware home and Oracle_WEB as the Oracle Home for web utilities. This brings the web utilities up to 11g PS2.
Now I have the Web Server software installed I need to update the Oracle Inventory on the machines in the SOA cluster that I did not run the installer on. I do this by executing the attachHome.sh script which is in the $ORACLE_HOME/oui/bin directory. I need to do this for two Oracle Homes; the oracle_common home and the Oracle_WEB home. Because the Oracle_WEB home depends on the oracle_common home we run the script for oracle_common home first. I found that I needed to provide the jreLoc parameter for the oracle_common home.
We then run it for Oracle_WEB home.
Next thing to install is Oracle WebLogic Server 10.3.3. Because I am using 64-bit JDK I chose to install generic WLS rather than platform specific.
java –jar wls1033_generic.jar
I created a “new” middleware home of my middleware home directory /u01/app/oracle/product/fmw and ignored the warning that there was already files in that directory. I then selected the JRockit JDK as the JVM to be associated with the Middleware home and selected a typical install. When the install was finished I unchecked the Run Quickstart option as I was not yet ready to create a WebLogic domain.
Because we installed the WebLogic software onto a shared server we need to copy the beahome details from the oracle user directory on the machine on which we did the install to the other nodes in the SOA cluster.
scp –r bea soa-cluster2:/home/oracle
We are not ready to install the SOA Suite software. Because SOA Suite 11g R1 PS2 is supplied as a patch set we must first install SOA Suite 11g R1 PS1. When prompted for the JDK location I provided /u01/app/oracle/product/fmw/jrrt-4.0.1-1.6.0 which is where I installed JRockit. After checking pre-requisites the installer should find the middleware home (/u01/app/oracle/product/fmw), if not provide the location where the WebLogic server and web tier are installed and choose a name for the Oracle SOA home, I chose Oracle_SOA.
After installing 188.8.131.52 I then ran the 184.108.40.206 upgrade (SOA Suite 11g R1 PS2), again choosing /u01/app/oracle/product/fmw as the middleware home and Oracle_SOA as the Oracle Home for SOA. This brings the SOA Suite up to 11g R1 PS2.
Note that in addition to upgrading the SOA Suite (BPEL PM, Mediator, Rules, B2B, Human Workflow, BAM and Enterprise Manager), the PS2 patch set also installs the BPM Suite.
Now I have the SOA software installed I again need to update the Oracle Inventory on the machines in the SOA cluster that I did not run the installer on. I do this by executing the attachHome.sh script which is in the $ORACLE_HOME/oui/bin directory. I need to do this for Oracle SOA Home Oracle_SOA.
Final piece of software to install is the service bus. You need to choose a custom installation because you do not want the Oracle Service Bus IDE, so uncheck this option. You can install the Oracle Service Bus IDE if you installed OEPE (Oracle Enterprise Pack for Eclipse) which can be installed standalone or with non-generic WebLogic Server installs. You can only install the examples if you have installed the samples database which is again an option with non-generic WebLogic Server Installs. So after choosing custom installation I made sure that the Service Bus IDE and Service Bus Samples options were not checked. After passing the pre-requisite checks I specified the same Middleware home (/u01/app/oracle/product/fmw) as before, this time selecting ORACLE_OSB as the Oracle Home and adding in the WebLogic server install location (u01/app/oracle/product/fmw/wlserver_10.3), note that all these values should be set by default.
Now I have the OSB software installed I again need to update the Oracle Inventory on the machines in the SOA cluster that I did not run the installer on. I do this by executing the attachHome.sh script which is in the $ORACLE_HOME/oui/bin directory. I need to do this for Oracle OSB Home Oracle_OSB.
We have now installed the software for
All this software is installed into a common Fusion Middleware home on a shared storage system. In production I would want to have two copies of this, although I could achieve this by cloning the volume on the NAS device.
In my next post I will look at the steps involved in configuring a SOA cluster.