Bookshelf Home | Contents | Index | PDF     

Siebel Installation Guide for UNIX > Installing and Configuring the Siebel Web Server Extension >

Requirements for SWSE Installation and Configuration

Before installing and configuring the SWSE, review the requirements listed in this topic.

CAUTION:  Do not install Siebel Business Applications without first reviewing Siebel System Requirements and Supported Platforms on Oracle Technology Network.

General Requirements

  • Review the issues described in Managing Temporary Disk Space Required by Siebel Installers and Wizards. For example, make sure you have adequate disk space, and make sure the login ID running the installer has write permissions to the temporary directory.
  • You must have installed a supported Web server as identified in Siebel System Requirements and Supported Platforms on Oracle Technology Network for the current release. See also Installing the Web Server.

    Make sure that the Web server machine on which you will install the SWSE meets all the hardware and software platform requirements documented in Siebel System Requirements and Supported Platforms on Oracle Technology Network.

    NOTE:  Note the port number for the Web server. For an Apache-based Web server, if you are using a nondefault port number, you must modify the httpd.conf file to reflect the correct port number. For details, see Editing the httpd.conf File for Apache-Based Web Servers.

  • You must have installed all key Siebel Enterprise Server components, including the Siebel Gateway Name Server, at least one Siebel Server, and the Database Configuration Utilities.

    You must have configured the Siebel Gateway Name Server, created and configured the Siebel Enterprise, created the SWSE logical profile, and configured the Siebel Server.

    Application Object Manager components must be enabled for the Siebel applications you purchased and intend to use. For information about enabling server components, see Siebel System Administration Guide.

    NOTE:  Wait to install additional Siebel Servers until after you have completed installation of the SWSE software and verified the connection from the Web server to the initial Siebel Server.

  • You can deploy multiple Language Packs on one Web server and one SWSE instance. The Siebel Server and the Web server do not need to be operated in the same language. However, the Siebel Server, the Web server, and all other server components must use the same character set. For more information, see Siebel Global Deployment Guide. See also About Installing and Deploying with Multiple Languages.
  • At least one SWSE is required for each Siebel Enterprise Server.
  • Note that uninstalling an SWSE instance you have configured removes the associated Siebel application virtual directories. See also Uninstalling Siebel Web Server Extension and Strong Encryption Pack.

Requirements for Heterogeneous Environments

Configuration for SWSE in some heterogeneous environments may involve particular steps not otherwise applicable.

If you installed the Siebel Gateway Name Server on a UNIX or Linux machine, and installed the Web server and SWSE on a Windows machine, then applying an SWSE logical profile previously created on UNIX or Linux may not succeed.

To configure the physical SWSE in an environment like this, create the SWSE logical profile on a Windows machine (same as the SWSE machine). You can install an instance of the Siebel Gateway Name Server on Windows just to be able to perform this task. When the Configuration Wizard launches, do not configure the Gateway Name Server or the Siebel Enterprise. Perform the configuration task to create the SWSE logical profile. As may suit your needs, you can move the logical profile folder to another machine before configuring the physical SWSE.

For more information, see 475502.1 (Article ID) on My Oracle Support. This document was previously published as Alert 1316.

Requirements for Siebel Load Balancing

If you will use Siebel native load balancing, you must generate the load-balancing configuration file (lbconfig.txt) and place the file in the SWSE logical profile folder after creating the profile. Do this before you apply the SWSE logical profile to each installed SWSE instance. The SWSE Configuration Wizard copies the lbconfig.txt file to the installed SWSE.

For more information, see Configuring Load Balancing for Siebel Applications.

Requirements for the Installation User

The SWSE must be installed as the same user who installed the Web server. Consequently, whether you install as root or as a nonroot user will also depend on requirements for Web server installation.

All future patch releases must be installed as the same user who installed the base installation being patched.

You must install SWSE using a user account that can modify the files appropriate for your Web server. See also Setting Permissions and Ownership.

  • Some supported Web servers (for example, Oracle HTTP Server) must be installed as a nonroot user. Consult your vendor documentation. Consequently, SWSE installation on such a Web server must also be performed as a nonroot user. See also 475370.1 (Article ID) on My Oracle Support. This document was previously published as Siebel Alert 1317.
  • For supported Web servers that can be installed as root or as a nonroot user, SWSE installation can be performed either as root or as a nonroot user, depending on how the Web server was installed. In general, it is recommended that installation be performed by a nonroot user for simpler administration and maintenance.
  • (IBM HTTP Server only) See also Configuring IBM HTTP Server for Linux Platforms.

Requirements for User Permissions

Some requirements are described below for permissions that affect installation or operation of the SWSE software and the Siebel virtual directories on the Web server.

The user that will run the SWSE plug-in must have read, write, and execute permissions on the SWSE_ROOT/public/language directories and their subdirectories (where SWSE_ROOT is the directory in which the SWSE is installed and language is a language directory such as ENU, FRA, CHT, and so on). These permissions allow static public files to be cached on the Web server. These folders are created during SWSE installation and configuration. In general, Siebel administrators require full access to SWSE_ROOT and all of its subdirectories.

The Web server administrator and all Siebel users and groups must have read and execute permission on all the virtual directories for the Siebel applications. The virtual directories are created on the Web server during SWSE configuration. If these permissions are not granted, login pages will not be rendered properly.

See also Setting SWSE and Virtual Directory Permissions and Granting User Permissions on the Web Server.

(AIX only) Before installing, verify that the login ID performing installation has permission to run slibclean by asking the administrator to change the permission as follows:

chmod 6555 /usr/sbin/slibclean

Requirements for Stopping and Starting the Web Server

Choosing the SWSE Configuration Wizard option to restart the Web server executes particular commands for supported Web servers.

  • For supported Apache-based Web servers, this wizard option executes the commands stopapa and startapa.
  • For Oracle iPlanet Web Server, this wizard option executes the commands stop and start.

NOTE:  From now on, if you restart the Web server instance for any reason, use these commands or equivalent methods, such as using the Web server's administration console. Do not use other commands for this purpose, such as apachectl.

Requirements for Configuring Anonymous Users

As noted in Creating the SWSE Logical Profile, when you configure the SWSE logical profile, you are prompted for user names and passwords of Siebel users that will serve as anonymous users for high interactivity and standard interactivity applications, respectively. You must meet the configuration requirement in a manner appropriate for your deployment. For details about configuring anonymous users, see Siebel Security Guide.

  • High interactivity user. The anonymous user for high interactivity applications starts the anonymous session that displays the login page to an end user for an employee application.

    The user GUEST already exists in the seed data as a Siebel user and may be specified as the high interactivity anonymous user, assuming it meets your requirements. Alternatively, you can create another user for this purpose.

  • Standard interactivity user. The anonymous user for standard interactivity applications starts the anonymous session that displays the login page to an end user for a customer application, and allows anonymous navigation within the application. This user must be defined as a user and must have access to any public view in the application.

    The user GUESTCST already exists in the seed data as a Siebel user and may be specified as the standard interactivity anonymous user, assuming it meets your requirements. Alternatively, you can create another user for this purpose.

  • If, after initial configuration, you change the password for the database account you are using, or decide to specify a different anonymous user, you can either edit the eapps.cfg file manually or re-create and reapply the SWSE logical profile to each physical SWSE.

    To manually edit the eapps.cfg file after configuration to update anonymous user settings, you update values for the parameters AnonUserName and AnonPassword. For more information, see Siebel Security Guide. Note the following:

    • Although access is limited for anonymous users, it is strongly recommended to change any default passwords prior to configuration or deployment.
    • If password encryption is in effect, you must use the encryptstring utility to encrypt any password before inserting it into eapps.cfg as a value for AnonPassword. See also 475381.1 (Article ID) on My Oracle Support. This document was previously published as Siebel Alert 1306.
    • The anonymous user for high interactivity applications that you configure in the wizard is defined in eapps.cfg as a default that applies to all applications of this type. The AnonUserName and AnonPassword parameters are defined once, in the [defaults] section.
    • The anonymous user for standard interactivity applications that you configure in the wizard is defined in eapps.cfg separately for each application of this type. The AnonUserName and AnonPassword parameters are defined in application-specific sections.
    • To use separate application-specific anonymous users, you must define AnonUserName and AnonPassword in separate application-specific sections of eapps.cfg. Example applications include Siebel Partner Relationship Management (PRM), which can use GUESTCP, and Siebel Employee Relationship Management (ERM), which can use GUESTERM.
  • Optionally, you can create new database users before initial configuration through editing the grantusr.sql script, which you execute before configuring the Siebel Database. (In general, It is recommended to review grantusr.sql before you execute it.) You still must add corresponding Siebel users. See also Creating Table Owner and Administrator Accounts.

Requirements for Binary Coexistence

If you will not require side-by-side installations of the same or different versions of SWSE on the same machine, uninstall the existing version of SWSE before installing the current version. See Uninstalling Siebel Web Server Extension and Strong Encryption Pack.

Side-by-side installations of the same or different versions of SWSE on the same machine (sometimes referred to as binary coexistence) may be helpful in some upgrade scenarios or for development or testing purposes. In general, however, it is recommended to install only instance of SWSE on each Web server machine.

For more information about creating and applying the SWSE logical profile, see Configuring the SWSE.

NOTE:  Scalability and performance implications must be taken into consideration when running multiple instances of SWSE on a single Web server machine.

Binary coexistence scenarios may be subject to limitations for your operating system and Web server platform. Note the following considerations and limitations applicable to binary coexistence:

  • Oracle Solaris platforms using Oracle iPlanet Web Server. You can install multiple instances (virtual server instances) of the Oracle iPlanet Web Server on the same machine. You can also install multiple instances of SWSE to run against these virtual server instances. Configure each SWSE instance to communicate with a separate virtual server instance using a different port.
  • UNIX platforms (including Linux) using Apache-based Web server. You can install multiple instances of an Apache-based Web server on the same machine. You can also install multiple instances of SWSE to run against these Web server instances. Configure each SWSE instance to communicate with a separate Web server instance using a different port.
  • Microsoft Windows platforms using IIS. You can install only a single instance of the Web server on the same machine. You can install multiple instances of SWSE on this machine, but you cannot run multiple instances of SWSE simultaneously, unless you configure them to run in separate memory spaces.

    Before you configure a new installed instance of SWSE where another instance is already installed and configured, you must edit the batch file that creates the virtual directories for the Siebel applications so the virtual directory names for the new instance will be unique. The virtual directories are created by the batch file eapps_virdirs.bat or eapps_virdirs_sia.bat (for Siebel Industry Applications). These files are in the SWSE logical profile directory.

    You can also edit the applicable batch file before configuring the SWSE to remove entries for virtual directories you do not need.

    
Siebel Installation Guide for UNIX Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.