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

About Configuring the Siebel Web Server Extension

As described in Process of Configuring the Siebel Web Server Extension, you configure the Siebel Web Server Extension (SWSE) in two phases: creating the SWSE logical profile on the Siebel Gateway Name Server computer and configuring the installed instance of SWSE on the Web server computer.

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 that you retain all of the SWSE logical profiles and note 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, then the existing profile is replaced with the new one. You must reapply the logical profile to each applicable SWSE.

About SWSE Configuration and the eapps.cfg File

It is possible to manually edit settings in the eapps.cfg file. However, doing so might cause this file to become out of sync with the SWSE logical profile. If the SWSE logical profile is re-created or reapplied, then your manual changes to the eapps.cfg file might be lost.

About SWSE Configuration and Encryption Type

If you create the SWSE logical profile directly after configuring the Siebel Enterprise, then the profile derives the encryption type from temporary data defined during the previous task, unless you skip validation in the Siebel Configuration Wizard.

If you create the SWSE logical profile without validating the user input in the Configuration Wizard, then the encryption type is set to None in the ConnectString parameters in the eapps.cfg and eapps_sia.cfg files. The connect string value None is compatible with Siebel Enterprise configuration encryption type choices of SISNAPI Without Encryption, SISNAPI Using TLS 1.2, SISNAPI Using SSL 3.0, or SISNAPI Using Enhanced SSL 3.0. For more information about validation in the Configuration Wizard, see Starting a Siebel Configuration Wizard.

NOTE:  If you configured the Siebel Enterprise with the encryption type set to SISNAPI Using RSA Encryption Algorithm, then it is strongly recommended not to create the SWSE logical profile with validation skipped, so that the encryption settings are compatible between the Siebel Servers and the SWSE (as is required).

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

Related Topics

Process of Configuring the Siebel Web Server Extension

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