|
Siebel Installation Guide for Microsoft Windows: Servers, Mobile Web Clients, Tools > Installing the Siebel Web Server Extension >
Configuring the Siebel Web Server Extension
Complete the steps that follow to configure the Siebel Web Server Extension for operation. To configure the Siebel Web Server Extension
- If you closed out of the Siebel Software 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.
- If you select Single Siebel Server in the Enterprise, proceed to Step 3.
- If you select Use a Third Party Load Balancer, proceed to Step 4.
- If you select Use Siebel Load Balancing, proceed to Step 5.
- Enter the hostname for the Siebel Server and the port number (default 2321) for the SCBroker 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.
- Enter virtual IP address or hostname and virtual port number for the third-party load balancer. Click Next and proceed to Step 6.
- 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 Siebel Web Server Extension Installation Requirements.
- Enter the name of your Enterprise Server and click Next.
- On the Encryption Type screen, 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 for SISNAPI between Siebel Server and Web server.
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 Application Object Managers to which the Siebel eBusiness Applications connect must be configured to use the same protocol. For more information, see Installing the Siebel Gateway Name Server.
The Compression Type screen appears.
- Select the type of compression you want to use for communications between the Web Server 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).
- 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 Deployment Planning Worksheet.
Employee's Anonymous Login Password (confirm). Retype the password to confirm it.
- 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 makes use of 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 makes use of a contact-based login, enter the password for this login ID; for example, GUESTCST. This password is written to the eapps.cfg file in encrypted form.
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 11 will be used (derived from [defaults] section).
The Web Update Protection Key screen appears.
- Type the Web Update Protection key your administrator will use for Web maintenance and click Next. For information on what this key is used for, see About the Web Update Protection Key.
The Deploy Secure Sockets Layer screen appears.
- Indicate whether or not 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 Deployment Planning Worksheet.
The configuration changes were applied successfully.
- Click OK.
If you would like to view events that occurred during the installation, you can access the log generated by the installer at SWEAPPS_ROOT\log.txt or the log generated by the Siebel application at SWEAPPS_ROOT\eapps\LOG.
About the Web Update Protection Key
The Web Update Protection Key is the password your Siebel administrator uses to refresh the application image files on your Web server your developers have updated and placed on the Siebel Server after customizing the Siebel application with Siebel Tools. The Web server contacts the Siebel Server, refreshing these images each time the administrator restarts the Web server. However, administrators can achieve the same result, refreshing the images by just entering this password in a command line, particularly when deploying multiple Web servers. For more information on this topic, see Security Guide for Siebel eBusiness Applications. NOTE: Although the Web Update Protection Key is set during SWSE configuration, you may change it later on, if desired, by editing it in the eapps.cfg file, located in the bin subdirectory of your SWSE installation.
To avoid the Web server cycling every time the SWSE directory images are refreshed, complete the following procedure. To refresh the SWSE directory structure without cycling the Web server
- Log in to the application.
- Type the following URL into the Address field of the browser:
http://host:port/application/start.swe?SWECmd=UpdateWebImages&SWEPassword=passwd
where:
host = The name of the Web server machine
port = Web Server listen port (Not required if using the default port, 80)
application = Any Siebel application, such as callcenter_enu, sales_enu, and so on
passwd = Password defined in eapps.cfg by WebUpdatePassword
For example:
http://siebe1:81/callcenter/start.swe?SWECmd=UpdateWebImages&SWEPassword=siebel
|
