Siebel crm webServer upgrade to ohs11G

Description

Occurrence

Symptoms

Workaround

 Installation Steps

 OHS 11g

 SWSE Configuration

 OHS 11g with SSL

 Recommended settings for ulimit parameters

 SBL-NET-01020: Internal: unknown hostname

 My Oracle Support Community

History

References

--------------------------------------------------------------------------------

Applies to:

Siebel CRM - Version 8.0.0.13 [20448] to 8.2.2 SIA[22320] [Release V8]

Siebel System Software - Version 8.0.0.13 [20448] to 8.2.2 SIA[22320] [Release V8]

Generic Linux

Description

OHS 10g which is a supported web server for earlier Siebel version 8.1.1.x fix packs is not supported for Siebel version 8.0.0.13 or 8.1.1.6 onwards (including Siebel CRM version 8.2.x).

So for all customers planning to deploy 8.0.0.13, 8.1.1.6 or above and 8.2.2 on Linux, it is mandatory to upgrade OHS web server to OHS 11g (32-bit).

NOTE: The same issue as reported on this document has been noticed with the Siebel version 8.0.0.13 fix pack. For this Siebel version also, a OHS 11g (32-bit) upgrade will be necessary.

Siebel version 8.0.0.12 still works fine with OHS 10g.

Occurrence

If you install Siebel CRM version 8.0.0.13 or 8.1.1.6 fix pack (or Siebel CRM version 8.2.x or also Siebel version 8.0.0.13) on Linux without upgrading your web server to OHS 11g, the web server will fail to start.

Only the 32-bit version of OHS 11g is supported. If you have installed 64-bit version, you will see a similar error to the following when starting the web server:

libmod_swe.so: wrong ELF class: ELFCLASS32

Symptoms

The OHS 10g web server will fail to start with an error similar to the following:

apachectl startssl: execing httpd

Syntax error on line 1206 of /siebel/product/10.1.3.5/companionCDHome_1/ohs/conf/httpd.conf:

Cannot load /siebel/product/10.1.3.5/companionCDHome_1/ohs/modules/libmod_swe.so into server: /siebel/product/10.1.3.5/companionCDHome_1/ohs/modules/libmod_swe.so: undefined symbol: ap_run_http_scheme"

Workaround

Installation Steps

1. Download OHS 11.1.1.6 base installer from:

http://www.oracle.com/technetwork/java/webtier/downloads/index2-303202.html

You need to select Linux 32-bit, accept the license agreement and then download the zip file.

Then install the OHS 11.1.1.6 software.

2. Install Siebel 8.1.1.6 (Patch ID 13078549) or higher or 8.0.0.13 or 8.2.2

3. Run the Siebel Web Server Configuration wizard.

OHS 11g

Please note that the structure of the OHS 11g is entirely different to OHS 10g.

We have the concept of instances and instance names in OHS 11g.

In the example below, the root folder was defined as ohs11g, the Oracle Home Directory as Oracle_OHS11, and the instancename was instance1

The start script opmnctl is in subfolder ohs11g/Oracle_OHS11/instances/instance1/bin.

You start OHS from this folder:

./opmnctl startall

The related opmn.xml and httpd.conf files can now be found in folders:

instances/instance1/config/OPMN/opmn/opmn.xml

instances/instance1/config/OHS/ohs1/httpd.conf

SWSE Configuration

You will see an error similar to the following in ~sweapp/log/sw_cfg_util.log if you do not correctly specify the Web Server Instance Location.

SBL-GEN-00255: Internal: Error during exec()

Step ShutdownOHSServer: failed to run program %%WebServerInstance%%%%OSDirSeparator%%..%%OSDirSeparator%%..%%OSDirSeparator%%bin%%OSDirSeparator%%opmnctl with cmdline stopproc

In order to avoid this error, you need to specify the full path for the web server instance. For example, Oracle_home_dir/instances/instance1/OHS/ohs1

SWSE configuration on Red Hat 4 or OEL 4

When you run the ssincfgw utility of Siebel version 8.0.0.13 or 8.1.1.6 in order to apply the  SWSE logical profile on Red Hat Linux version 4 or OEL version 4 you might encounter the following error:

12-04-03 02:52:22 Step SetMimeTypes: failed to run program %%SiebelRoot%%%%OSDirSeparator%%install_script%%OSDirSeparator%%install%%OSDirSeparator%%UpdateMimeTypes with cmdline %%SiebelRoot%% %%WebServerInstance%%

This error is caused by a different behavior of the "head -1" command syntax on these two operating systems. To fix that error go to the folder sweapp/install_script/install. In this folder reside several shell scripts that are called by ssincfgw.  Replace in all shell scripts in this folder the occurrence of  "head -1"  with "head -n 1"

OHS 11g with SSL

If your application is configured to use SSL (that is, the SecureBrowse parameter is set to true for the Application Object Manager), then the default behavior will be that you see a blank screen and the browser will hang upon login - the login prompt will not appear.

To resolve this, you will need to make the following change to the OHS 11g ssl.conf file.

Backup and modify the ~instances/instance1/config/OHS/ohs1/ssl.conf, disabling these three lines.

#BrowserMatch ".*MSIE.*" \

#nokeepalive ssl-unclean-shutdown \

#downgrade-1.0 force-response-1.0

Then restart the web server and the web client will work as expected.

OHS 11g 32-bit installation on a 64-bit Linux operating system

As mentioned above, only the 32-bit version of OHS 11g is supported. However 64-bit Linux OS is supported as stated in the Supported Platforms Guide. That means that even on 64-bit systems you will always have to install the 32-bit version of OHS 11g.

Before starting the 32-bit installer, enter the Linux command: linux32 bash

If the installer will not launch in your X-Windows console, then the rpm package libXp is missing in the 32-bit version on your 64-bit Linux system. This rpm needs to be installed.

In case you get some linking errors when the installer is relinking the 32-bit shared libraries shipped with the OHS 11g product, then additional 32-bit rpm packages are required.

Please follow the instruction as given in note: "Install Of Oracle 32bit Client On Linux X86-64 Fails : Skipping Incompatible Libgcc.a When Searching For -lgcc" (Doc ID 1358983.1).

Additionally, for Red Hat Enterprise Linux 6.1 and Oracle Enterprise Linux 6.1, the installer must be run from ~/Disk1/install/linux rather than from the default location of ~/Disk1 to prevent installation failure due to an invalid Operating System.

For other prerequisites on OEL 6.1 and Red Hat 6.1 see note: "How to install OHS 11g for Siebel 8.1 and 8.2 deployments on OEL 6.1 64-bit version" (Doc ID 1507897.1).

Startup error due to privileged port usage

During the configuration step when running the Swse configuration wizard, the http listening port as defined in your current eapps.cfg template will replace the current listening port as defined in the httpd.conf file.

If you have defined the listening port to a port less than 1024 in your eapps.cfg file then you need to run the web server with root privileges.

Otherwise you will see this error during startup:

ohs/bin/apachectl startssl: execing httpd

httpd.worker: Syntax error on line 1038 of instances/instance1/config/OHS/ohs1/httpd.conf:

Cannot load instances/instance1/config/OHS/ohs1/modules/libmod_swe.so into server: libstcaswpi.so:

cannot open shared object file: No such file or directory

additionally in ohs.log file you see this error if for example port 80 has been specified:

[OHS] [INCIDENT_ERROR:32] [OHS-9999] [worker.c]

[host_id: hostname [host_addr: ip-address] [pid: process-id] [tid: thread-id] [user: <username>]

[VirtualHost: main] (13)Permission denied: make_sock: could not bind to address [::]:80

This happens when the user as specified in <username> alias has no root privileges.

See also http://docs.oracle.com/cd/E21764_01/web.1111/e10144/getstart.htm#CHDFHCHG

To enable the web server to listen on a privileged port and run as non-privileged user the following three steps need to be done:

a) make sure the non-privileged user account is defined in the "User" directive in httpd.conf and also the "CoreDumpDirectory" directive is set to a valid directory  writeable by this user

b) as the root user, change the .apachectl binary file in folder Oracle_home_dir/ohs/bin/ as follows:

         chown root .apachectl

         chmod 6750 .apachectl

c) edit the apachectl script file in folder Oracle_home_dir/ohs/bin/ as follows:

   add a line:

   LD_LIBRARY_PATH=Siebel_home_dir/sweapp/bin:Siebel_home_dir/sweapp/bin/enu

   above the lines:

   #set ulimit for OHS to dump core when it crashes

   ulimit -c unlimited

Recommended settings for ulimit parameters

We recommend that you define the stack size (to minimize memory consumption of the web server) and set the core dump file size to unlimited (for better troubleshooting).

For larger deployments you also should increase the number of open files.

Make sure that in the file /etc/security/limits.conf a line like this is added:

* hard nofile 65536

This allows a maximum of 65536 file handles per process.

Backup and modify the Oracle_home_dir/ohs/bin/apachectl script as follows:

# set reasonable stack size:

ulimit -s 128

# set ulimit for OHS to dump core when it crashes:

ulimit -c unlimited

# increase file descriptor limit

ulimit -n 16384

SBL-NET-01020: Internal: unknown hostname

When you can resolve the hostname as specified in eapps.cfg connect string outside of OHS 11, but you get an error message like this in the swse log:

GenericLog    GenericError    1    000000045048277b:0    2012-09-06 10:01:14    (smconn.cpp (284) err=1180668 sys=852198) SBL-NET-01020: Internal: unknown hostname

SessMgr    ConnOpen    3    000000045048277b:0    2012-09-06 10:01:14    -260084880: [SESSMGR] Open(siebel.TCPIP.None.None://localhost:2321/SBA_81/SCCObjMgr_enu, 60, 1800)

SisnTcpIp    SisnSockInfo    3    000000045048277b:0    2012-09-06 10:01:14    -260084880: [TCPIP-client] failed to resolve hostname: localhost (err=852198 | Internal: gethostbyname_r ()failed with error. (%sysError))

then the following line needs to be added to the ohs/bin/apachectl script:

RESOLV_MULTI=off ; export RESOLV_MULTI

Incorrect information regarding supported web servers in the current System Requirements and Supported Platforms, Version 8.1 document:

Bug 13387000 has been created to update the System Requirements and Supported Platforms, Version 8.1, Rev. O > Server Environment Requirements > Supported Web Servers table needs to be updated to reflect the following information:

Oracle HTTP Server 10.1.3.3 (Apache Web Server v2.x or above)

NOTE: This is supported for Siebel version 8.1.1 to Siebel version 8.1.1.5 and 8.0 through 8.0.0.12.

Oracle HTTP Server 11g

NOTE: This is supported for Siebel version 8.1.1.6 or above (including Siebel version 8.2.x), as well as for Siebel version 8.0.0.13 maintenance release.

The Version 8.1 Supported Web Servers table was updated with the release of Rev. P.

My Oracle Support Community

This Siebel Installation Community document contains additional information regarding Siebel CRM version 8.1.1.6 fix pack: Siebel 8.1.1.6 fix pack: Important Notes