Siebel Server Installation Guide for UNIX > Installing Siebel Web Server Extension >

Installing and Configuring the Siebel Web Server Extension

The Siebel Web Server Extension (SWSE) files will be installed on the same machine as the Web server. The installation program sets up the Siebel directory structures, copies required files and components to the target disk, and configures the host environment.

NOTE:  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.

To install the Siebel Web Server Extension plug-in

NOTE:  This procedure is for installing the base product. For patch installation instructions, refer to Maintenance Release Guide provided with the patch.

  1. Insert the UNIX_OS Server Programs, Web Server Extensions CD-ROM into the CD-ROM drive of the server

    2. where:

    UNIX_OS = your UNIX operating system, such as Solaris, HP-UX, or AIX.

    NOTE:  The volume label for the CD is seaUNIX_OSeapplep1 or siaUNIX_OSeapplep1, as appropriate to the Siebel applications you are installing; it may not be required, depending on how you access the CD-ROM.

  2. Open a new shell and unset any Siebel environment variables.
  3. Verify the directories and permissions to those directories into which you will install the product. You must have write and execute permission.
  4. Navigate to the /eappweb directory on the CD-ROM and open a new shell.

    5. NOTE:  To install the Siebel Web Server Extension, you must install using a user account that can modify the Web server files appropriate for your installation: Sun One, IBM HTTP, or HP-Apache 2 Web server files.

  5. To start the Siebel Web Server Extension installation process, enter the following command, appending any desired flag described in Additional Flags for Installation Commands.

    6. ./setupUNIX_OS

    The Installer Welcome screen appears.

  6. Click Next.

    7. If you have installed other Siebel components on the same machine, the installer displays the message that an existing installation has been found.

  7. 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:
  8. Enter the fully qualified path to the installation directory and click Next.

    9. The Installer Language Selection screen appears.

  9. Choose the language or languages to be installed and click Next.

    10. All servers are installed with at least one (base) language. Additional languages can be installed at a later date, if desired. For more information, see Global Deployment Guide.

    When installing languages at a later date, you must also reinstall any patches that have been run on the directory.

    NOTE:  In a Unicode-enabled database environment, you can install any of the available Siebel language packs. In a non-Unicode database environment, you must consider the correlation of the language packs you want to install and the characters supported by your database code page. For example, in a Western European code page database, you can only install Western European language packs such as English, French, Spanish, or German language packs. And in a Japanese code page database, you can only install Japanese or English language packs.

    For a list of supported code pages and encoding strategies, see System Requirements and Supported Platforms.

    The Installation Verification screen appears.

  10. Click Next.

    11. The Installation Progress screen appears, and the installer creates uninstallation information.

  11. Select the primary language for this installation and click Next.

    12. The Web Server Root Directory screen appears.

  12. Select the root directory for the SWSE on your Web server and click Next.

    13. The Resonate screen appears.

  13. Click to indicate whether or not Resonate load-balancing is installed anywhere in this Enterprise and click Next.
  14. Enter the Siebel Gateway virtual IP Address and click Next.

    15. The Siebel Gateway Address screen appears.

  15. Enter the actual Gateway IP address and click Next.

    16. The Siebel Gateway Port screen appears.

  16. Accept the default Siebel Gateway port number (2320), or change it, and click Next.

    17. The Enterprise Name screen appears.

  17. Enter the Siebel Enterprise Server name and click Next.

    18. The Siebel Server Name screen appears.

  18. Enter the name of the Siebel Server and click Next.

    19. NOTE:  This should be the descriptive name for this Siebel Server, not the machine name.

    The Compression Type screen appears.

  19. Click on the compression type and click Next.

    20. The Encryption screen appears.

  20. Click on the encryption type and click Next.

    21. The Logging Level screen appears.

  21. Choose the logging level, as indicated below:

    22. fatal. Only fatal operational errors are logged.

    errors. Only non-fatal and fatal operational errors are logged.

    warnings. Only warning messages are logged.

    info. Only non-fatal operational errors are logged.

    details. All operational statistics, information messages, warnings, and errors are logged.

    NOTE:  For the best performance, choose errors. Choose details only for debugging, as it negatively impacts performance.

    Click Next.

    The Web Server HTTP Port screen appears.

  22. Accept the default HTTP port, or enter a new port number, and click Next.
  23. Accept the default Web Server HTTPS port (443), or enter a new port number, and click Next.

    24. The Web Update Protection Key screen appears.

  24. Enter the Web Update Protection Key that your administrator will use for Web maintenance.

    25. This key, or password, allows only your Siebel Administrator to refresh the application image files on your Web server by accessing any updated images your developers have placed on the Siebel Server, following customizations with Siebel Tools.

    The Web server contacts the Siebel Server and refreshes these images each time the administrator restarts it. However, administrators will find entering this password in a command line a much more efficient way to perform the image file refresh, particularly when multiple Web servers are deployed.

    NOTE:  Although this password is set during SWSE configuration, you may change the password later on, if desired, by editing it in the eapps.cfg file, located in the /bin subdirectory of your $SWEAPP_ROOT directory.

    The Anonymous Login Employee Name screen appears.

  25. Enter the anonymous employee login ID and click Next.

    26. NOTE:  This 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.

    The Anonymous Login Employee Password screen appears.

    This parameter is for employees who may browse applications without logging in.

    NOTE:  If you do not want to enable this feature for some employees, you can bypass this screen without entering anything by just clicking Next.

  26. If you use this parameter, enter the anonymous login password, confirm it, and click Next.

    27. The Anonymous Login Contact Name screen appears.

  27. Enter the anonymous login contact name and click Next.

    28. The Anonymous Contact Password screen appears.

  28. Enter the anonymous login password, reconfirm it, and click Next.

    29. The Restart screen appears.

  29. Indicate whether or not you want to restart the Web server now to complete the changes and click Next.

    30. The Installer Verification screen appears.

  30. Verify the settings:
  31. Click Finish.

    32. NOTE:  If you did not choose to restart your Web server earlier during configuration, your changes will not take effect until you do so.

Installing Multiple Instances of SWSE

It is not supported to install multiple instances of SWSE on a single Web server to support different versions of Siebel eBusiness Applications in a production environment. As an alternative, for development and test environments, you can install separate Web server instances on a single box, with each listening to a different port. Each of these Web server instances can have its own SWSE. For more details on installing multiple instances of SWSE in your development and test environment, refer to Technical Note 456 on Siebel SupportWeb. You also need to modify the following two lines in the httpd.conf file:

Listen (IP Address of Web Server m/c):port#; for example, 172.20.167.154:16131

SeverName (m/c name):port; for example, sdch70a012.siebel.com:16131


 Siebel Server Installation Guide for UNIX 
 Published: 24 June 2003