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

Configuring the SWSE


This topic describes how to configure the SWSE for operation. You configure the SWSE in two distinct phases:

  • Create and configure the SWSE logical profile. This task is available in the Siebel Configuration Wizard, and is performed after you configure the Siebel Gateway Name Server and configure the Siebel Enterprise. This wizard is created when you install the Siebel Gateway Name Server, and launches automatically after installation. See Creating the SWSE Logical Profile.
  • Apply the SWSE logical profile to the installed SWSE. This task is available in the SWSE Configuration Wizard. This wizard is created when you install the SWSE, and launches automatically after SWSE installation. See Applying the SWSE Logical Profile.

You can use the same SWSE logical profile with multiple SWSE instances. You can also create multiple SWSE logical profiles for use with sets of SWSE instances with different configuration requirements. It is strongly suggested to retain all SWSE logical profiles and to document the SWSE instances to which you applied each profile.

To change a setting that was specified in the SWSE logical profile, perform the SWSE logical profile configuration task again, specifying the same or a different name. If you configure an SWSE logical profile and specify the location of an existing logical profile, the existing profile is replaced with the new one.

NOTE:  It is possible and sometimes desirable to manually edit settings in the eapps.cfg file. However, this file may then become out of sync with the SWSE logical profile. If the SWSE logical profile is re-created or reapplied, your manual changes to the eapps.cfg file may be lost.

If you create the SWSE logical profile in live mode directly after configuring the Siebel Enterprise, the profile derives the encryption type from temporary data defined during the previous task.

If you create the SWSE logical profile in offline mode, the encryption type is set to None in the ConnectString parameters in the eapps.cfg file. None is compatible with Enterprise configuration encryption type choices of None, SISNAPI Without Encryption (same as None), SISNAPI Using SSL 3.0, or SISNAPI Using Enhanced SSL.

NOTE:  If you configured the Enterprise with encryption type set to RSA, it is strongly recommended to create the SWSE logical profile in live mode, so encryption settings will be compatible between the Siebel Servers and the SWSE (as required).

For more information about encryption type and Secure Sockets Layer (SSL) settings, see Siebel Security Guide.

Before proceeding, review Requirements for SWSE Installation and Configuration. See also:

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