Download
Go to Oracle Delivery Cloud and sign in
Select ‘Siebel CRM’ as the Product Pack and an appropriate platform. You’ll still, for some infuriating reason, find 8.1.1.x under 32-bit Windows and 8.2.2.x under 64-bit Windows. Very odd
Download the 5 ZIP file components of the installation and unzip them all to a common folder
Open up a command prompt, as administrator, and CD to the unzip folder
Set the JAVA_HOME variable, if required. For example: set JAVA_HOME=”E:\Java\jre6″
Run snic.bat
Create a new p_w_picpath, patch set
Go through the usual process of selecting desitnation, platform and components and pick one or more languages
Though it looks like the JAVA process has frozen / crashed, it’s now unzipping the JAR files into appropriate installers
Install
Installation is the same as you would expect, if you have installed 8.1.1.8 or 8.2.2. Check out my earlier article for some gotchas on the new installation process
You’ll still get the stupid “you’re about to install into a non-empty directory” message. For a patch? Really?
The patch process also takes ages. This, I suspect, is because the installer recognises it’s own instability and does a ‘backup’ (i.e. OS level folder copy) of the entire SIA / SEA folder before it does anything. I still think Oracle have taken a huge step backwards with the clunky and unreliable installer
Once you’ve installed Enterprise, Web Server, Web Client and Tools (very important!) you’re ready for the next step
Enable Open UI
First up, you won’t find the instructions for enabling OpenUI in the patch documentation. Instead, refer to MOS article 1499842.1 for a Deployment Guide for Open UI
Unzip ‘OpenUI_Base_8119.zip’ from within the Siebel Tools REPPATCH folder. Here you’ll find instructions on what projects to lock and a .BAT file to import all the appropriate SIFs to enable OpenUI
Lock the projects, create the new Reports project then edit the preferences file appropriately – it’s all documented in the instructions
Run the import batch file and check the result in the Notifactions\Log folder. I chose ‘Import All Packages’ to save time. This seemed to work perfectly first time though it took forever as each SIF is imported individually, using a new Siebel Tools process
Perform a full compile of the SRF and deploy to your server environment
Now you have two choices – clone an existing OM (recommended) or update an existing one to use OpenUI in place of HI. I went for cloning as, though it’s more involved, it allows me to access and compare my existing HI OM
Personally, I used the server manager scripts that were generated from the mergecfg.exe tool to create the OM. I first created a new OM component then used the scripts to update the partameters to match those of the existing Sales (SSE) OM component
In the parameters for the new OM, set the new ‘EnableOpenUI’ paramter to ‘True’
In IIS, create a new Virtual Directory for your new OM and create appropriate entries in eapps.cfg to point to it. I called my OM ‘SSEOUIObjMgr_enu’ and the Virtual Directory and eapps entry ‘sales_openui_enu’. You can use the editmetabase.exe tool in the SWE bin folder to do this (metabaseedit.exe sales_openui_enu E:\sba81\SWEApp\BIN\ENU\eapps.mtb)
Restart everything, just to be sure
Now, navigate to your new OpenUI enhanced Siebel application and note that big red INTERAL Oracle warning sign! For internal use only? Perhaps QA should have removed that before making the software freely available for download!
