Siebel Installation Guide for UNIX > Configuring Siebel Enterprise Server Components and the Siebel Web Server Extension > Process of Configuring the Siebel Web Server Extension >
Applying the SWSE Logical Profile
This procedure describes the steps for applying a logical profile to a specific installed instance of SWSE. You perform the same procedure for each SWSE. This task is a step in Process of Configuring the Siebel Web Server Extension. NOTE: When the SWSE and the Web server are on a different computer from the Siebel Gateway Name Server (as is typical), then, after creating the profile as described in Configuring the SWSE Logical Profile, you must either copy the profile directory to the Web server computer or provide remote access to the directory for the task described in this topic. For example, on Windows you might map the profile directory to the applicable drive on the remote computer.
To apply the SWSE logical profile
- Determine which SWSE logical profile to use for this installed instance of SWSE.
- Verify access to the logical profile directory, if it is located on a remote computer.
- If you will be using load balancing, then make sure that you created the lbconfig.txt file and placed it in the SWSE logical profile directory.
For more information, see Process of Configuring Load Balancing for Siebel Business Applications.
- Open a shell window on the computer on which you installed the SWSE.
- Source the cfgenv.csh or cfgenv.sh environment setup file.
Navigate to the $ SWSE_ROOT directory and source the environment file by using one of the following commands, depending on the type of shell that you use. Perform this step before each time that you run the SWSE Configuration Wizard.
C shell
source cfgenv.csh
Bourne or Korn shell
. ./cfgenv.sh
TIP: Make sure that there is a space between the initial period and ./cfgenv.sh .
In this path, $ SWSE_ROOT is the location of the Siebel Web Server Extension root directory. For example, for Siebel CRM version 8.1.1.14, this directory might be /export/home/siebel/8.1.1.14.0/sweapp .
- Start the Siebel Web Server Extension Configuration Wizard.
For more information, see Starting a Siebel Configuration Wizard.
Enter a command similar to the following:
install_path /config/config -mode swse
In this path, install_path is the installation path for the installed Siebel Web Server Extension software.
- Choose Apply an SWSE Logical Profile.
- Provide input as described in Table 8. Click Next to go to the next screen.
Where it is available, click Help to display help text with more information about the settings.
NOTE: You can click Cancel to exit the Configuration Wizard before you complete the configuration.
After you specify or confirm all of your selections, the summary screen appears.
- In the summary screen, do one of the following:
- Click Next again to complete the configuration. Go to the next step.
- Optionally save a response file in this screen, to use in an unattended configuration, then click Cancel to exit the Configuration Wizard without completing configuration.
- After configuration is complete, click Exit to exit the Configuration Wizard.
To help you to verify that the configuration completed successfully, the log file is referenced at the end of the configuration task.
Configuration Settings for the SWSE
Table 8 lists the settings requested in the SWSE Configuration Wizard for configuring the SWSE: applying the SWSE logical profile. Where it is available, you can click Help to display help text with more information about the settings.
Table 8. Settings for Configuring the SWSE
Setting in SWSE Configuration Wizard |
|
Deployed Languages |
Specifies the installed languages that you want to deploy on the Web server and the SWSE. Each language that you select must be an installed language. For each deployed language and each application, a separate section is created in the eapps.cfg or eapps_sia.cfg file. For example, Siebel Call Center uses the sections named [/callcenter_lang]. Part of the ConnectString value represents the three-letter code for the deployed language. NOTE: This option does not appear for a single-language installation. In this case, the installed language is automatically deployed when you configure the SWSE.
After initially configuring the SWSE, you can deploy languages that you installed but did not deploy by running the SWSE Configuration Wizard again and choosing the task Add Language Support for the SWSE Configuration. For more information, see Installing and Deploying Siebel Business Applications with Multiple Languages. |
Select a Load Balancer |
Specify whether you are using Siebel native load balancing, third-party load balancing, or no load balancing. Specify no load balancing for a deployment with a single Siebel Server. For more information, see Process of Configuring Load Balancing for Siebel Business Applications. |
Siebel Server Host Name (Siebel Server) |
The host name of the Siebel Server computer. Specify this for a deployment with a single Siebel Server. |
Siebel Connection Broker Port |
The Siebel Connection Broker (SCBroker) port number on the Siebel Server computer, as you specified in Configuring the Siebel Server. Specify this port number for a deployment with a single Siebel Server. The default port number for SCBroker is 2321. |
Host Name or Virtual IP Address for Third-Party Load Balancer |
A host name or virtual IP address for use with a third-party load balancer. |
Network Port Number for Third-Party Load Balancer |
A network port number for use with a third-party load balancer. |
Siebel Web Server Extension Logical Profile Location |
The location of the SWSE logical profile that you created in Configuring the SWSE Logical Profile. |
Web Server Instance Location |
The location of the Web server instance for which this SWSE is installed. |
Restart Web Server |
Indicate whether to restart the Web server now to complete the changes. If you do not choose to restart your Web server processes at this time, then you must do so before making Siebel Business Applications available to your users through their browsers. For more information about stopping and restarting the Web server, see Requirements for Stopping and Starting the Web Server. |
|