Installing Siebel Web Extension (SWE) on top of Sun Java System Web Server 7.0
By Giri Mandalika on May 17, 2009
As of today, Sun Java System Web Server 7.0 is not a certified platform to deploy Siebel 8.x enterprise on. We are working with Oracle Corporation to make this certification happen so our customers can take advantage of the performance optimizations that went into the web server release 7.0.
Meanwhile those who want to give it a try can do so with little effort. In release SJSWS 7.0, the
start/stop/restart/.. scripts were appropriately relocated to
bin directory under the virtual web server instance. The installer for Siebel 8.x Web Server Extension looks for the
start script [of the web server] under the home directory of the virtual web server instance. (because it was the default location until the release of SJSWS 7.0). The installation fails if the installer cannot find the
start script in the location it is expecting it to be.
Due to the relocation mentioned above, installation of the Siebel Web Server Extension fails at the very last step where it tries to modify the
start script with a bunch of
LD_PRELOADs so the Siebel Web Extension loads up and runs on the Sun Java System Web Server. To get around this failure, all you have to do is to create a symbolic link in the home directory of the virtual web server instance pointing to the
startserv script residing in the
The following example shows the necessary steps.
% pwd /export/pspp/SJWS7U5/https-siebel-pspp % ln -s bin/startserv start % ls -l start lrwxrwxrwx 1 pspp dba 13 May 17 17:01 start -> bin/startserv
Install Siebel Web Extension in the normal way. No other changes are required.
AFTER SWE INSTALLATION:
% ls -l start\* -rwxr-xr-x 1 pspp dba 4157 May 17 17:38 start -rwxr-xr-x 1 pspp dba 3456 May 17 17:38 start_.bak % mv bin/startserv bin/startserv.orig % mv start bin/startserv
Notice that the Siebel installer actually made two copies of the startup script from the symbolic link. The original
bin/startserv remained intact after the SWE installation.
Finally start the Web Server instance by running the
startserv script. It should start with no issues.
% pwd /export/pspp/SJWS7U5/https-siebel-pspp/bin % ./startserv Sun Java System Web Server 7.0U5 B03/10/2009 16:38 info: swe_init reports: SWE plug-in log file info: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.5.0_15] from [Sun Microsystems Inc.] info: HTTP3072: http-listener-1: http://siebel-pspp:8000 ready to accept requests info: CORE3274: successful server startup
Before we conclude, do not forget the fact that Sun Java System Web Server 7.0 is not yet certified with Siebel 8.x release. Use the instructions mentioned in this blog post at your own risk. However if you do like to take that risk, consider installing the latest release of Sun Java System Web Server, which is SJSWS 7.0 Update 5 as of this writing.
Stay tuned for the certification news though.