- If you closed out of the SWSE Configuration Wizard after installation, relaunch it, using any method described in Launching the Siebel Software Configuration Wizard. Otherwise, proceed to Step 2.
The Load Balancing Configuration screen appears.
- Select the desired load-balancing method for your environment and click Next.
- Enter the hostname for the Siebel Server and the port number (default 2321) for the SCBroker (Siebel Connection Broker) component. Click Next and proceed to Step 6.
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 on the SCBroker component, see 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 PortNumber).
- 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 6.
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 6.
This file must already exist. For more information, see SWSE Installation Requirements.
- Enter the name of your Enterprise Server 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 13.
MSCRYPTO. Microsoft encrypted communications protocol for communication between Siebel components.
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 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:
None
ZLIB
The HTTP Port Number screen appears.
- Enter the port numbers for HTTP and HTTPS, and click Next:
HTTP Port Number. Type the HTTP port number used for Web browser communications, or accept the default setting used by the Web server (80).
HTTPS Port Number. Type the HTTPS port number used for secure Web browser connections, or accept the default setting used by the Web server (443).
NOTE: Confirm the HTTP and HTTPS port numbers for your Web server before you specify them here.
- On the Employee's Anonymous Login Name screen, indicate the following, and then click Next:
Employee's Anonymous Login Name. The anonymous employee login name is the Siebel user ID for a valid employee that is used to start the anonymous session from which the user is shown the login page; example: GUESTCST.
Employee's Anonymous Login Password. Type the password for the preceding user ID. This information should be recorded in your copy of the worksheet in Deployment Planning Worksheet.
Employee's Anonymous Login Password (confirm). Retype the password to confirm it.
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.
- On the Contact Login User Name screen, indicate the following, and then click Next:
Contact Login User Name. The contact login user name is the Siebel user ID for a valid contact user that is used to start the anonymous session from which the user is shown the login page for a Siebel customer application. If your organization uses a contact-based login, enter GUESTCST to use the Siebel seed data user provided for this purpose or enter another valid user ID.
NOTE: Make sure that any login ID you enter has the correct privilege to start the anonymous session. The ID used should also have authorization to access any public view.
Contact Login Password. If your organization uses a contact-based login, enter the password for this login ID. This information should be recorded in your copy of the worksheet in Deployment Planning Worksheet.
Contact Login Password (confirm). Retype the password to confirm it.
Make sure that it is a valid login for the application you are installing, regardless of the authentication method your company uses.
NOTE: If you do not enter values, the value specified in Step 10 will be used (derived from the [defaults] section of the eapps.cfg file).
NOTE: The password for the contact 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 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 Deploy Secure Sockets Layer screen appears (in a different wizard).
- Indicate whether you want to deploy Secure Sockets Layer (SSL) in your enterprise. Select or clear the Yes box on this screen, and then click Next.
- 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 Private Key information 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 Configuration Parameter Review screen appears.
- Review these values for accuracy against your copy of the worksheet in Deployment Planning Worksheet.
The configuration changes were applied successfully.
- Click OK.
