Siebel Installation Guide for UNIX: Servers, Mobile Web Clients, Tools > Installing the Siebel Web Server Extension >
Installing and Configuring the SWSE
This topic describes provides instructions for installing and configuring the SWSE on your Web server machine.
The installation program sets up the Siebel directory structures, copies required files and components to the target disk, and configures the host environment.
To prevent installation problems related to permissions, the user who installs the SWSE should be the same user or have the same permissions as the user who installed the Web server instance.
NOTE: The following procedure is for installing the base product. For patch installation instructions, refer to the Maintenance Release Guide provided with the patch. See also About Installing Siebel Releases.
To install and configure the SWSE under UNIX
- Install or create an instance of the Web server (for Sun Java System Web Server, you can instantiate a virtual Web server on existing installed software), and record the port number at which it is listening.
- (Optional) Uninstall your existing SWSE. For more information, see SWSE Installation Requirements.
- Open a new shell and navigate to the Siebel image location for the current software version. Then navigate to the directory where the installer is located.
For example, for Solaris, navigate to Siebel_Image/Solaris/Server/Siebel_Web_Server_Extension.
- Siebel_Image = The directory for your version-specific Siebel network image, such as
- Open a new shell and unset any Siebel environment variables.
- Verify the directories and permissions to those directories into which you will install the product. You must have read, write, and execute permission.
NOTE: To install the SWSE, you must install using a user account that can modify the files appropriate for your Web server: Sun Java System Web Server, IBM HTTP Server, or HP Apache Web Server.
- To start the SWSE installation process, enter the following command. Optionally, append any flags described in Additional Flags for Installation Commands.
UNIX_OS = Your operating system (sol, aix, or hpux)
The screen Welcome to the InstallShield Wizard for Siebel Web Server appears. (Siebel Web Server is another term for Siebel Web Server Extension.)
- Click Next.
If a previously installed instance of SWSE of the same version was found on the same machine, the installer displays the message that an existing installation has been found. Otherwise, go to Step 9.
- Depending on whether you are installing your SWSE files for the first time or adding a new language to an existing instance, take the appropriate action, and then click Next:
- Confirm the default installation directory or enter a different fully qualified path to the desired installation directory, and click Next.
The default SWSE installation directory is /siebel.
CAUTION: Do not specify the Web server installation directory as the directory in which to install SWSE.
The Installer Language Selection screen appears.
- Choose the language or languages to be installed and click Next.
All servers are installed with at least one primary (base) language. Additional languages can be installed at a later date, if desired. For more information, see the Global Deployment Guide.
When installing languages at a later date, you must also reinstall any patch releases that were previously installed.
NOTE: Before you install Language Packs, see the information about code pages in Planning RDBMS Installation and Configuration.
The installer displays the location into which it will install the SWSE, and also the disk space required for the software you are installing.
- Click Next to copy the files for the current product into the installation location. Alternatively, to change any settings, click Back, adjust your selections, and click Next to return to this screen.
The Installation Progress screen appears, and the installer creates the uninstaller folder.
- If you are installing more than one language, the Primary Language screen appears. Proceed to Step 12.
- If you are installing only one language, the Web Server Root Directory screen appears. Proceed to Step 13.
- Select the primary language for this installation and click Next.
The installer proceeds to install the specified files.
A message appears, stating that language files are being installed.
When installation of all the language files is completed, the Web Server Root Directory screen appears.
- Select the root directory for the Web server and click Next.
NOTE: After you click Browse, click once to select a directory. (Double-clicking adds the directory name twice.)
The Load Balancing Configuration screen appears (in the SWSE Configuration Wizard).
- Select the desired load-balancing method for your environment and click Next.
- Enter Hostname for the Siebel Server and the port number (default 2321) for the SCBroker (Siebel Connection Broker) component. Click Next and proceed to Step 18.
NOTE: This port is used for all communications between the Web server and the Siebel Server. Make sure the port you specify for SCBroker is not occupied by any other applications, other Siebel components (such as Siebel Gateway Name Server), or other Siebel Server instances. If you have installed multiple Siebel Servers on this machine, make sure you enter a unique SCBroker port for each Siebel Server instance. For more information about SCBroker, see the Siebel System Administration Guide and the Deployment Planning Guide.
If you need to change an SCBroker port number later, use Siebel Server Manager to specify a value for the
Static Port Number parameter (alias
- Enter virtual IP address or hostname and virtual port number for a third-party load balancer, if you use one. Click Next and proceed to Step 18.
For information on writing routing rules for third-party HTTP load balancers, see Managing Load Balancing for Siebel Applications.
- Enter the full path to the load-balancing configuration file (lbconfig.txt). Click Next and proceed to Step 18.
This file must already exist. For more information, see SWSE Installation Requirements.
- Enter the name of your Enterprise Server and click Next.
The Compression Type screen appears.
- Select the type of compression you want to use for communications between the SWSE and the Siebel Servers, and click Next:
The Encryption Type screen appears.
- Select the encryption type the Siebel Web Clients should use to communicate with the Application Object Managers and click Next:
NONE. No networking encryption. Select this option if you will be configuring SSL between the Siebel Server and the Web server. Later in the configuration process, you will do additional configuration for SSL, starting in Step 28.
RSA. Required protocol if you will be using the RSA Security Systems 128-bit strong encryption feature for data transport.
NOTE: The Siebel Servers that connect to this SWSE must be configured to use the same protocol. For more information, see Installing the Siebel Server.
For more information on the options on this screen, see the Security Guide for Siebel Business Applications.
The Web Server HTTP Port screen appears.
- Accept the default Web server HTTP port (
80) used for Web browser communications, or enter a new port number, and click Next.
The Web Server HTTPS (Secure HTTP) Port screen appears.
- Accept the default Web Server HTTPS port (
443) used for secure Web browser communications, or enter a new port number, and click Next.
The Web Update Protection Key screen appears.
- Enter the Web Update Protection Key that your administrator will use for updating files on the SWSE and click Next.
For more information, see Updating Web Server Static Files on the SWSE Using the Web Update Protection Key.
The Anonymous Login Employee Name screen appears.
- Enter the employee's anonymous login ID and click Next.
NOTE: This value should be a login ID that any employee may use to access the Login view. The login ID should be a valid client login with privileges to navigate to Login views. This parameter is for employees who may browse applications without logging in.
- Enter the employee's anonymous login password, confirm it, and click Next.
NOTE: The password for the anonymous employee login is stored in the eapps.cfg file, and is encrypted by default. For more information about managing encrypted passwords in the eapps.cfg file, see the Security Guide for Siebel Business Applications.
The Anonymous Login Contact Name screen appears.
- Enter the contact user login ID and click Next.
- Enter the contact user login password, confirm it, and click Next.
NOTE: The password for the contact user login is stored in the eapps.cfg file, and is encrypted by default. For more information about managing encrypted passwords in the eapps.cfg file, see the Security Guide for Siebel Business Applications.
- If you are installing in console mode, the Deploy Secure Sockets Layer in the Enterprise screen appears (in a different wizard). Go to Step 28.
- If you are installing in GUI mode, go to Step 32. If you want to configure SSL, you must start the wizard manually. For details, see the Security Guide for Siebel Business Applications.
- Indicate whether you want to deploy Secure Sockets Layer (SSL) in your enterprise. Select or clear the Yes box on this screen.
- On the Certificate File Name screen, enter the following and click Next:
Certificate File Name. The certificate file name.
CA Certificate File Name. The certificate authority file identifying the trusted authority who issued the certificate.
The Private Key File Name screen appears.
- Enter the following and click Next:
Private Key File Name. Name of the private key file.
Private Key File Password. Password for the private key file name.
Private Key File Password (confirm). Password you entered in the preceding example.
The Peer Authentication screen appears.
- Select whether or not you want Peer Authentication.
The Restart screen appears.
- Indicate whether or not you want to restart the Web server now to complete the changes and click Next.
NOTE: If you do not choose to restart your Web server processes at this time, you must do so before making Siebel Business Applications available to your users through their browsers.
CAUTION: For supported Apache-based Web servers (including IBM HTTP Server and HP Apache Web Server), choosing the option to restart the Web server executes the commands
startapa. From now on, any time you restart the Web server, you must do so using these commands. Do not use the
apachectl command for this purpose.
The Finish screen appears.
- To complete the installation, click Finish.