D53912GC11 Ag

Siebel 8.1.
x Installation
Activity Guide
D53912GC11 Edition 1.1 November 2009 D63773
Oracle Internal & Oracle Academy Use Only
Copyright 2009, Oracle. All rights reserved. Disclaimer This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way. Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display, perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization of Oracle. The information contained in this document is subject to change without notice. If you find any problems in the document, please report them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not warranted to be error-free. Restricted Rights Notice If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United States Government, the following notice is applicable:
Trademark Notice Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
U.S. GOVERNMENT RIGHTS The U.S. Governments rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restricted by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract.
Table of Contents
Practice 1-1 Optional: Reviewing an Existing Installation ..................................... 1 Practice 2-1 Installing the Siebel Enterprise Server .............................................. 9 Practice 3-1 Configuring the Siebel Database .................................................... 23 Practice 4-1 Configuring a Siebel Server ............................................................ 29 Practice 5-1 Installing the Siebel Web Server Extension .................................... 33 Practice 6-1 Installing the Developer Web Client ................................................ 39 Practice 6-2 Installing the Sample Database ...................................................... 44 Practice 7-1 Configuring an Application Object Manager to Use LDAP Authentication ..................................................................................................... 47 Practice 8-1 Installing the Siebel Management Agent......................................... 59 Practice 8-2 Installing the Siebel Management Server ....................................... 62 Practice 9-1 Performing a Silent Installation ....................................................... 69 Practice 10-1 Installing Siebel Tools ................................................................... 77 Practice 11-1 Configuring Multiple Servers......................................................... 81 Practice 11-2 Configuring Multiple Different Application Object Managers ......... 88 Practice 11-3 Using Native SWSE Load Balancing ............................................ 92 Practice 12-1 Adding a Language to an Enterprise............................................. 97 Practice 12-2 Optional: Enabling Multilingual Lists of Values ........................... 102
ii
Lesson 1: Installation Considerations
Practice 1-1 Reviewing an Existing Installation (Optional)

Goals Time To read information about an existing Siebel Enterprise 10 15 minutes
In this practice, you will examine the parameters for an existing Siebel Enterprise. This practice includes detailed descriptions of why each set of parameters is important, hence provides a useful foundation for the subsequent practices. 1. Note the deployment team members in the table below. In a real deployment environment, having this information in a convenient location provides a quick reference when you are having difficulty with a particular aspect of the installation.
Title Deployment Team Lead Siebel Administrator System Administrator Database Administrator Name Renee Richards Stephen Storm Jen Storm Brenda Grimm E-mail Address rrichards@siebel.com sstorm@siebel.com jstorm@siebel.com bgrimm@siebel.com Phone Number (415) 555-3423 (212) 555-8900 (212) 555-4025 (415) 555-4283
The Deployment Team Lead is in charge of managing the deployment project. He or she is in charge of initial deployment planning, deployment scheduling, and facilitating communication between deployment team members. The Siebel Administrator is an expert in Siebel CRM configuration, and should be able to create Siebel user accounts, modify Siebel applications using Siebel Tools, edit Siebel configuration files, and otherwise assist with any Siebel-specific issues. The System Administrator is an expert in the operating system used, whether it be Windows, Linux, or another flavor of UNIX. He or she should be able to create and manage OS accounts, manage firewalls and networking, share network drives, and otherwise provide all the infrastructure support necessary for a Siebel deployment. For more complex networking solutions, such as creating a demilitarized zone to separate the Web server from the Siebel Servers, consider adding an independent Network Administrator to this list of contacts. The Database Administrator is an expert in the RDBMS software. He or she should be able to create the database, facilitate connecting to the database, create database users and roles, modify and run scripts against the database, and otherwise provide complete database support.
Siebel 8.1.x Installation
Instructions:
Review Parameters for a (Hypothetical) Existing Installation

2. Examine the example Siebel Enterprise: A single Web server receives requests from Siebel Web Clients and passes them to a single Siebel Server running multiple Application Object Managers. A second Siebel Server provides processing support by running workflows and EIM jobs. Your installation will be similar; however, you will co-locate all of these components and you will not have a second Siebel Server.
Web Server
Siebel Database
Siebel Servers
AOM Siebel File System EIM
Siebel Gateway Name Server
Siebel Enterprise Server
Firewall
3. Examine the information for the database server. The Siebel File System is co-located on this server, so its parameters are included as well:
Web Server Firewall

Siebel Database
Siebel Servers
AOM Siebel File System EIM

EMEDBS01 192.168.1.101 Windows Server 2003 Oracle 10g
a. Database server information:

Machine Name IP Address OS Database Platform Connection Port Data Tablespace Index Tablespace Database Owner Owner Password Database User User Password Coding
SQLNet Connection String SIEBELTNS 1521 siebelts siebelindexts SIEBEL SIEBEL SADMIN SADMIN Unicode
The SQLNet Connection String is specific to the Oracle database; it is the connection name used by the Oracle listener to establish connections with the database. Similarly, tablespaces are specific to the database platform. In this case, the DBA created two tablespaces to support the Siebel Enterprise: siebelts contains all of the data tables, while siebelindexts contains all of the indexes.
The database owner owns the Siebel schema and is used to create tables and indexes. The database user can read and modify tables. Both of these values are established in a database script that must be run before populating the Siebel database. The DBA should provide you with these values. Unicode databases are larger, but provide more robust support for multiple languages. b. Siebel file system information:
Machine Name IP Address OS Folder Name EMEDBS01 192.168.1.101 Windows Server 2003 siebfile
The folder name should be as OS-independent as possible, to allow Siebel Servers installed on any operating system to access the file system. Avoid special characters, lengthy folder names, or deep file systems. The Siebel file system may be distributed across multiple directories and machines by using a comma-delimited list of file systems here. See the appropriate Siebel Installation Guide for more details on distributing the file system.
4. Examine the information for the Siebel Gateway Name Server:
Web Server Firewall

Siebel Database
AOM Siebel File System

Machine Name IP Address OS Installation Directory Gateway Name Server Port Authentication Name Authentication Password Authentication Type Enterprise Name ODBC Name
EIM

EMEGNS02 192.168.1.102 Windows Server 2003 D:\OUses 2320 SADMIN SADMIN DB OUEnt OUEnt_DSN
SWSE Logical Profile Location D:\OUWebServer\SWEApp
The base installation directory contains subdirectories including the support files for each Enterprise component; for example, D:\OUses\gtwysrvr contains the Gateway Name Server files, while D:\OUses\dbsrvr contains the Database Configuration Tool files. The authentication name and password are used to connect to the Gateway Name Server; the authentication type should be left at its default value of database authentication if possible. The authentication user must be added as a database user to support database authentication. The Enterprise name is a string used to identify the Enterprise. When you create the Enterprise, an ODBC connection of the form <Enterprise Name>_DSN is created. When you create the Enterprise, you must also create a Siebel Web Server Extension (SWSE) logical profile, which contains configuration information about the Enterprise. You later deploy this profile to the Web server during SWSE configuration.
Siebel Servers
5. Examine the information for the Siebel Servers:
Web Server Firewall

Siebel Database
AOM Siebel File System a. Server Parameters:

Machine Name IP Address OS Installation Directory Server Name Component Groups Connection Broker Port Sync Manager Port EMESRV04 192.168.1.104 Windows Server 2003 D:\OUsrvr AOMServer Call Center Sales 2321 40400
EIM
Machine Name IP Address OS Installation Directory Server Name Component Groups Connection Broker Port Sync Manager Port
EMESRV05 192.168.1.105 Windows Server 2003 D:\OUsrvr EIMServer EIM Workflow 2321 40400
The installation directory is the base directory; a siebsrvr subdirectory is created within this directory. The server name is a string of up to 12 characters that must be unique throughout the Enterprise. The default value for the server name is the machine name, but it can be changed to a more descriptive name. During installation, specify which component groups should be enabled on the server. This can be changed later using the Administration - Server Configuration screen within the application. The Connection Broker port is the TCP/IP port on which the Siebel Server listens for connections.
Siebel Servers
6. Examine the information for the Siebel Web Server Extension:
Web Server Firewall

Siebel Database
AOM Siebel File System
EIM

EMESWS03 192.168.1.103 Windows Server 2003 IIS 6.0 D:\OUWebServer No
Machine Name IP Address OS Web Server Installation Directory Compression Login Session Timeout Active Session Timeout HTTP Port HTTPS Port FQDN HI User Name HI Password SI Encryption SI User Name SI Password Enterprise Security Token
HTTP 1.1-Compliant Firewall? Yes 300 900 80 443 No GUESTERM GUESTERM No GUESTCST GUESTCST key
The installation directory is the base directory; a SWEApp subdirectory is created within this directory
Siebel Servers
ZLIB compression is useful when files are frequently uploaded to and downloaded from the server; for example, attachments. However, because compression is applied to all data indiscriminately, there is a performance impact in enabling it if the majority of the data is regular application data, rather than large file attachments. HTTP 1.1-Compliant Firewalls allow compressing the TCP/IP headers, improving network performance. The login session timeout is the amount of idle time before a login session expires. The active session timeout is the amount of idle time before an active (logged in) session expires. Fully Qualified Domain Names (FQDNs) append the domain name to every address; for example, EMEJHG20.us.oracle.com rather than simply EMEJHG20. This is useful in convincing pop-up blockers to allow Siebel application pop-ups. The HI User must be an employee in the application as well as a user in the authentication system. It is used to perform initial access of the database for employee applications. The default is GUESTERM. GUESTERM is part of the Siebel seed data, and is already an employee in the application. By default, passwords in the configuration files are encrypted using an Oracle proprietary algorithm. For integration with other systems, SI passwords may be encrypted using the RC2 algorithm instead. The SI User must be a user in the application as well as a user in the authentication system. It is used for anonymous access to a customer application; for example, to navigate a product catalog and populate a shopping cart before logging in or registering to complete the purchase. The Enterprise Security Token is used to authenticate communications between the various components in the enterprise; the token is passed along with any requests to verify that the request came from a valid enterprise component.
Lesson 2: Installing the Siebel Gateway Name Server
Practice 2-1 Installing the Siebel Enterprise Server

Goals To install the Siebel Enterprise Server, including the Siebel Gateway Name Server, Siebel Enterprise, and a Siebel Server 40 50 minutes
Time
Instructions:
In this practice, you will run the Siebel Enterprise Server installer to install the Siebel Gateway Name Server, a Siebel Enterprise, and a Siebel Server. You will complete the steps for configuring the Siebel Gateway Name Server and Siebel Enterprise, and exit the configuration tool just before configuring the Siebel Server. 1. Create and share the Siebel file system. This shared directory must be accessible by all the Siebel Servers in the Siebel Enterprise. a. Select Start > Programs > Accessories > Windows Explorer. b. In the left pane, expand <machine name> and select the D: drive. c. Verify that the siebfile directory exists. If it does not, create it: i. In the right pane, right-click and select New > Folder. ii. Change the folder name to siebfile. d. Right-click the siebfile folder and select Sharing and Security. e. If necessary, select the Share this folder radio button. f. Click the Permissions button. g. Click the Allow checkbox next to Full Control.
h. Click OK to close the Permissions dialog box. i. Click OK to close the Properties dialog box. Note: In an actual deployment you should set up the file server permissions so that only authorized users have access to the file system. j. Minimize Windows Explorer. 2. Determine your machines host name and IP address. The host name is a required installation parameter. In some environments, you may need to use the IP address instead: a. Select Start > Run. b. Enter cmd and click OK. This brings up a command prompt. c. Enter hostname. This returns your machine name. Note it here: While Windows is not case-sensitive, Java (and hence the Application Deployment Manager) is, so pay attention to case. d. Enter ipconfig to get the IP address for your machine. Note it here: Having both the machine name and IP address allows you to easily diagnose Domain Name Server issues. e. Close the command prompt. 3. Run the Siebel Enterprise Server installer. You would normally download the required JAR files from Oracle E-Delivery and run the appropriate Siebel image builder to create these installation folders. This step has been performed for you. a. Navigate to D:\labs\8.1_Install\Installers\Server\Siebel_Enterprise_Server. b. Double-click setup.exe. An After Installation dialog box immediately appears. Do not click Next; instead, wait for the Oracle installer to finish initializing and bring up the Welcome screen.
c. If the Welcome screen does not appear after a few seconds, check for the Installer in the task bar and click it.
10
d. In the Welcome screen, click Next.
e. Enter D:\OUses as the directory name (for Oracle University Siebel Enterprise Server). You may use any directory name supported by your operating system, but best practice is to ensure compatibility with all operating systems by avoiding spaces and special characters and keeping the directory name short (8 characters or less). f. Click Next.
11
g. Select Gateway Name Server, Siebel Server, and Database Configuration Utilities and click Next. Note: You are installing the Siebel Gateway Name Server and configuring a Siebel Enterprise. You must co-locate a Siebel Server installation on this machine in order to provide some of the executables required for configuring the Siebel Gateway Name Server. You must also run the database configuration utilities from the Siebel Gateway Name Server machine in order to properly configure the ODBC connection to the database on that machine.
h. Select Custom as the setup type. The Typical setup includes the Siebel Management Agent and you will install the Siebel Management Agent later in the course. i. Click Next.
12
j. Ensure that the options below are selected, and that the remaining options are not selected. In particular, make sure that the Siebel Management Agent option is not selected. Also deselect the DB2 options (not shown in the screen shot).
k. Click Next. l. Select enu - English (American) as the language and click Next. m. Accept Siebel Enterprise Server Configuration 8.1 as the program folder and click Next. Note that you can change this name to a more descriptive one in your actual deployment. n. Review the summary information and click Next.
13
The installer runs, copying all of the necessary files into D:\OUses. A progress bar should indicate the progress of the installation. The installation should take roughly 10 minutes. 4. Once installation completes, the Siebel Configuration Wizard starts automatically. Note: If you need to run the Configuration Wizard at a later time, select Start > Programs > Siebel Enterprise Server Configuration 8.1 > Siebel Enterprise Configuration to start it.
5. Before proceeding with the configuration, explore your file system and services to confirm that the installer did nothing more than copy the correct files to your system. This is the major benefit of separating the installer from the configuration tools: If you make an error in your configuration, you need only re-run the configuration tools, rather than the full installer. a. Leave the Siebel Configuration Wizard open and select Start > Programs > Accessories > Windows Explorer to start Windows Explorer. b. Navigate to D:\OUses. What subfolders do you see?
c. Navigate to D:\OUses\gtwysrvr\log. Are there any log files for the Gateway Name Server? Open the log file and describe its contents.
d. Confirm that D:\OUses\siebsrvr\log also contains only one file which contains nothing but build and version information. e. Select Start > Programs > Administrative Tools > Services.
14 Siebel 8.1.x Installation
f. Confirm that there are no system services starting with Siebel. g. Minimize the system services window. h. Close all open log files. 6. Return to the configuration wizard and proceed with the configuration: a. Ensure that Create New Configuration is selected and click Next. b. Ensure that Configure a New Gateway Name Server is selected and click Next. c. Enter the parameters below, clicking Next each time to proceed through the configuration: Note: Throughout this course, tables such as the one below are used to provide parameters for multiple installation screens. If you are trying to enter a parameter from the table and do not see it on the screen, please click Next to advance to the next screen. Similarly, in later practices the final confirmation steps (such as clicking Next in the Summary screen) may be omitted.
Parameter Gateway Name Server TCP/IP Port Set the Gateway Name Server system service to start automatically Value 2320 Purpose Port on which the Gateway Name Server will listen for connections. 2320 is the default, and should not be changed unless absolutely necessary. Whether or not to start the Siebel Gateway Name Server service when the machine boots.
Selected
d. Click Next in the Final Tasks dialog box. e. Click Next to have the Siebel Configuration Wizard execute the settings. f. Click Yes to execute the configuration. It should complete successfully within a few seconds. Troubleshooting: In the unlikely event you receive an error, consider: Is port 2320 already in use? Use netstat to check. Did you already configure a Siebel Gateway Name Server on this machine? Check the services to see whether one is already configured. g. h. i. j. k. Click OK. Leave the Siebel Configuration Wizard open. Return to the system services window and select Action > Refresh. Confirm that there is now a Siebel Gateway Name Server service and its status is Started. Return to Windows Explorer and confirm that D:\OUses\gtwysrvr\log now contains multiple log files. l. Examine the content of the log files. It is good to familiarize yourself with the typical harmless errors that occur so that you can more easily recognize significant errors in the future. 7. Configure a Siebel Enterprise. This configures a Siebel Enterprise to store enterprise-level parameters on the Gateway Name Server. a. Return to the Siebel Configuration Wizard. b. Select Create New Configuration and click Next. c. Select Configure a New Enterprise in a Gateway Name Server and click Next. A Siebel Enterprise provides a logical name for a collection of Siebel Servers, as well as storing enterprise parameters.
15
d. Enter the parameters below, clicking Next each time to proceed through the configuration: Note: Throughout this course, tables such as the one below are used to provide parameters for multiple installation screens. If you are trying to enter a parameter from the table and do not see it on the screen, please click Next to advance to the next screen. Similarly, in later practices the final confirmation steps (such as clicking Next in the Summary screen) may be omitted.
Parameter Gateway Name Server Authentication User Account Name Gateway Name Server Authentication User Account Password - and confirm Gateway Name Server Host Name Value SADMIN Purpose Used to access the Gateway Name Server. The username and password must be set up in the Gateway Name Servers authentication system; for example, as a database user.
SADMIN
<machine name> Used to connect to the Gateway Name Server. The Configuration Tool should default to your machine name, but you should confirm this. Refer to earlier in this practice to find your machine name. See below Used to connect to the Gateway Name Server.
Gateway Name Server Port Number
e. For the next step, intentionally generate an error: i. Change the port number to 2321. ii. Click Next. Note that the configuration tool attempts to connect to the Gateway Name Server and fails, generating an error. At the moment, the error message is not handled correctly, and displays Asian characters. This is a known issue. iii. Click OK. iv. Change the port number back to 2320. v. Click Next. This time the configuration tool successfully contacts the Gateway Name Server and allows you to proceed with your configuration.
16
Used to access the Gateway Name Server. The username and password must be set up in the Gateway Name Servers authentication system; for example, as a database user.
f. Complete the configuration: Note: Throughout this course, tables such as the one below are used to provide parameters for multiple installation screens. If you are trying to enter a parameter from the table and do not see it on the screen, please click Next to advance to the next screen. Similarly, in later practices the final confirmation steps (such as clicking Next in the Summary screen) may be omitted.
Parameter Enterprise Description Siebel File System Value Purpose Name of the new Siebel Enterprise. Description of the enterprise. Where to store the Siebel File System. Use your machine name rather than D: to support the multiserver installation later in the course. Siebel Enterprise Name OUEnt OUEnt Enterprise \\<machine name>\siebfile
Database Platform Database Table Owner
The database type used by the Siebel Enterprise. Oracle Database Enterprise Edition SIEBEL The table owner of the database; set by the DBA. Connection string to the Oracle database; provided by your DBA. Database user used by the Siebel Enterprise components to connect to the database server. Set by the DBA. Password for the Siebel Database User.
Oracle SQLNet Connect SIEBELDB String Siebel Database User Account Name Siebel Database User Account Password - and confirm Enterprise Security Authentication Profile Security Adapter Name Propogate Authentication Settings to the Gateway Name Server Additional Tasks SADMIN
SADMIN
Database Authentication DBSecAdpt Selected
The default security mechanism used within the enterprise. Recommended practice is to leave this at database authentication. Name of the security adapter; recommended practice is to leave this at its default. Propagates the changes, including the authentication information, to the gateway name server. This is required the first time you configure the enterprise to establish gateway name server security. It is optional thereafter. Set up enhanced network security, charts, or data quality connections
None
g. Click Next in the Review Summary. h. Click Yes to execute the configuration. The execution should complete successfully within a few seconds. i. Click OK. Leave the Siebel Configuration Wizard open. 8. Configure the Siebel Web Server Extension logical profile. This will generate the eapps.cfg file used by the Siebel Web Server Extension, as well as the eapps_virdirs.bat file used to generate the virtual directories on the Web server. Once you have created this profile, you need to copy it or make it available to the machine hosting the Web server. In this case, you will install the Web server on the same machine, so it will not be necessary to move this profile after creating it. a. In the Siebel Configuration Wizard, select Create New Configuration and click Next.
17
b. Select Configure a New Siebel Web Server Extension Logical Profile and click Next. A Siebel Web Server Extension Logical profile includes the eapps.cfg of configuration file the Siebel Web Server Extension reads on startup, plus a pair of batch files used to create the virtual directories in the Web server; for example /callcenter_enu. c. Enter the parameters below, clicking Next each time to proceed through the configuration: Note: Throughout this course, tables such as the one below are used to provide parameters for multiple installation screens. If you are trying to enter a parameter from the table and do not see it on the screen, please click Next to advance to the next screen. Similarly, in later practices the final confirmation steps (such as clicking Next in the Summary screen) may be omitted.
Parameter Value Purpose Siebel Enterprise Name OUEnt Used to collect information about the Enterprise. This must match the enterprise name you entered when configuring the enterprise.
Siebel Web Server Extension Logical Profile Name Collect ApplicationSpecific Statistics Compression Type
D:\OUses\gtwysrvr\admin\ Location to store the logical profile. Can be any directory you choose, but it should be Webserver accessible by the Web server machine. Selected None Whether to collect statistics on individual applications. Performs compression of transferred data. Use ZLIB if users will frequently be uploading large files to the server. Otherwise it is best not to perform data compression. Enables network header compression to improve network performance. Time (in seconds) to keep a login session alive without any user activity. Time (in seconds) to keep an active (logged in) session alive without any user activity. Port number on which the Web server listens for HTTP connections. 80 is the default. Port number on which the Web server listens for HTTPS connections. 443 is the default. Helps the application bypass popup blockers by providing a full domain name; for example, enter oracle.com if you want the application to use http://EMEJHG20.oracle.com/sales_enu rather than http://EMEJHG20/sales_enu. Used to bring up the initial login screen for employee applications; the user must be regsitered in the authentication system. Used to bring up the initial login screen for employee applications; the user must be regsitered in the authentication system. Whether to use RC2 encryption on the SI user password instead of the default Oracle
HTTP 1.1-Compliant Firewall Login Session Timeout Value
Selected 300
Active Session Timeout 900 Value HTTP Port Number HTTPS Port Number Fully Qualified Domain Name 80 443 <blank>
High Interactivity or Employee User Login Name High Interactivity or Employee User Password Standard Interactivity Password Encryption
18
GUESTERM
GUESTERM
Unselected
proprietary encryption. Standard Interactivity or GUESTCST Contact User Login Name Standard Interactivity or GUESTCST Contact User Password Used for anonymous browsing of customer applications; the SI user must be registered in the authentication system to allow anonymous browsing. Used for anonymous browsing of customer applications; the SI user must be registered in the authentication system to allow anonymous browsing. Used to verify communications between Enterprise components. Can be any random string. Where to store SWSE statistics. Whether to deploy SSL in the Enterprise. Used to support HTTPS connections.
Siebel Enterprise Security Token Default Statistics Page Deploy SSL
key
_stats.swe Unselected
d. e. f. g.
Review the summary information and click Next. Click Yes to execute the configuration. The execution should succeed in a few seconds. Click OK. Examine the files created for the Siebel Web Server Extension logical profile. i. Use Windows Explorer to navigate to D:\OUses\gtwysrvr\ADMIN\Webserver. ii. Right-click eapps.cfg and select Open. iii. Select Select program from a list and click OK. iv. Select Notepad. v. Ensure that Always use the selected program to open this kind of file is selected and click OK. This opens eapps.cfg using Notepad. vi. Scroll through the file and note the configuration settings you made. What is the value of GuestSessionTimeout?
Close eapps.cfg, not saving any changes. Right-click eapps_virdirs.bat and select Edit. These are the names of the virtual directories that will be created on the Web server. You may edit this file to change the names of or eliminate some of the virtual directories. Note that callcenter_%1 will be created as callcenter_enu, the virtual directory you use for most Siebel training courses. ix. Close eapps_virdirs.bat, not saving any changes. h. Return to the configuration wizard. i. Select Exit Configuration and click Next. j. Click Yes to exit the Siebel Enterprise Server configuration wizard. The Siebel Server Configuration Wizard starts. 9. Exit the Siebel Server Configuration Wizard. You must configure the Siebel database before configuring the Siebel Server. a. Select Exit Configuration and click Next. b. Click Yes.
vii. viii.
19
10. Switch to the Oracle installer window and click Finish. 11. In the After Installation dialog box, click Next then Finish. 12. Navigate to D:\OUses and confirm that there are now dbsrvr, gtwysrvr, and siebsrvr subfolders, all of which contain files. 13. Run the Environment Verification Tool to determine whether your machine is running on a supported Siebel platform: a. Select Start > Run and enter cmd to open a command prompt. b. Enter the command
cd D:\OUses\gtwysrvr\bin
to change directories to the Gateway Name Servers executables directory. Course Note: All of the text commands used in this course are contained in text files, allowing you to copy and paste the commands instead of having to type them manually. The commands for this practice are contained in D:\labs\8.1_Install\Solutions\GNS\evtStrings.txt. To copy a string to the command line, use Notepad to open evtStrings.txt, select the string to be copied, right-click and select Copy, and then right-click the top blue bar of the command window and select Edit > paste. c. Enter the command
evt.exe -g <machine name> -e OUEnt -r D:\OUses\gtwysrvr -d EXPLAIN -o HTML > evt1.html
This runs the Environment Verification Tool in verbose mode and writes the output to evt1.html. Note: The EVT generates a spurious error message that C:\Program is not recognized. This is harmless. d. Using Windows Explorer, navigate to D:\OUses\gtwysrvr\bin and double-click evt1.html. e. Examine the output of the test. Note that the classroom machines frequently have errors in their network settings, but your installation will still work correctly. This environment was designed and tested specifically for this course. f. Close evt1.html, not saving any changes. 14. Explore the other folders in the installation, not making any changes. Your next step is to install the Siebel schema and seed data in the pre-existing Oracle database.
20
Solutions 2-1 Installing the Siebel Enterprise Server

Answers
5.b. Navigate to D:\OUses. What subfolders do you see? _uninst (the uninstaller configuration files) dbsrvr (the database configuration tools) gtwysrvr (the Siebel Gateway Name Server support files) siebsrvr (the Siebel Server support files) Navigate to D:\OUses\gtwysrvr\log. Are there any log files for the Gateway Name Server? Open the log file and describe its contents. The only log file is base.txt. It contains the version and build number of the installation. There are no other log files. Scroll through the file and note the configuration settings you made. What is the value of GuestSessionTimeout? 300, which is exactly what you set it to during profile configuration.
5.c.
8.g.vi.
21
22
Lesson 3: Installing the Siebel Database
Practice 3-1 Configuring the Siebel Database

Goals Time To install the Siebel database 75 90 minutes
Instructions:
1. Edit grantusr.sql to set the correct parameters. This is typically performed by the DBA. a. Use Windows Explorer to create a backup copy of D:\OUses\dbsrvr\Oracle\grantusr.sql by copying it and pasting it in the same directory. b. Use Notepad to open D:\OUses\dbsrvr\Oracle\grantusr.sql. c. Scroll down to the section on creating db accounts for Siebel users. d. Copy, paste, and edit the four lines which create SADMIN and create two new users: GUESTERM with password GUESTERM and GUESTCST with password GUESTCST. These are the HI and SI anonymous users, respectively.
23
In this practice, you will run the Siebel Database Server Configuration Tool to configure the Siebel database. An empty Oracle database named siebeldb has already been created for you, containing two tablespaces: siebelts to contain the Siebel data tables, and siebelindexts to contain the Siebel indexes. Before running the Configuration Tool, you need to run a SQL script to create the necessary Siebel users and roles in this database. A sample script named grantusr.sql was installed as part of the Database Configuration Utilities installation. You first need to edit grantusr.sql to match your installation before running it.
Module 3: Installing the Siebel Database
e. Add two additional lines: alter user SADMIN quota unlimited on &&siebel_indexspace; alter user SIEBEL quota unlimited on &&siebel_indexspace; These lines ask for a siebel_indexspace, and then grant SADMIN and SIEBEL permission to access that tablespace. Verify that your grantusr.sql looks like the screen shot below:
Course Note: An edited version of grantusr.sql is available in D:\labs\8.1_Install\Solutions\DB. Consider comparing your edited version with this version before running it. f. Save and close grantusr.sql. 2. Run grantusr.sql against the database. A database named siebeldb has been created for you with two tablespaces: siebelts for Siebel data, and siebelindexts for Siebel indexes. a. Select Start > Programs > Oracle - OraDb10g_home1 > Application Development > SQL Plus. b. Enter the following parameters:
User Name Password Host String system oracle SIEBELDB
c. Click OK. You should receive a SQL> prompt. d. At the SQL> prompt, enter: @D:\OUses\dbsrvr\Oracle\grantusr.sql
e. f. g. h. i.
Course Note: All of the text commands used in this course are contained in text files, allowing you to copy and paste the commands instead of having to type them manually. The above command is contained in D:\labs\8.1_Install\Solutions\DB\SQLCommands.txt. Enter siebelts as the value for siebel_tablespace. Enter temp as the value for temp_tablespace. Enter siebelindexts as the value for siebel_indexspace. All grants should succeed. Minimize SQLPlus.
4. Double-click D:\labs\8.1_Install\SIAkeys.txt and carefully copy the first license key to the clipboard; that is, copy the first line of the text file. There are multiple keys listed in the file. Minimize Notepad once you have copied the key. 5. Generate the Siebel database: a. Select Start > Programs > Siebel Enterprise Server Configuration 8.1 > Database Server Configuration to launch the Database Configuration Wizard.
25
3. Examine some of the DDL and SQL files used to populate the database: a. Using Windows Explorer, navigate to D:\OUses\dbsrvr\ORACLE. b. Right-click applet.ddl and select Send To > Notepad. c. Examine the contents of applet.ddl. Notice that this data definition defines the database tables and indexes used to support applets. d. Close applet.ddl, not saving any changes. e. Right-click ddlview.sql and select Send To > Notepad. f. Examine the contents of ddlview.sql. This is the SQL code used to create database views (sets of columns from tables) used by the Siebel application when accessing the database. Database views are not the same as Siebel application views. g. Close ddlview.sql, not saving any changes. h. Right-click ddl.ctl and select Send To > Notepad. i. Examine the contents of ddl.ctl. This is a data definition file defining a large number of the tables and indexes of the Siebel database schema. j. Close ddl.ctl, not saving any changes.
b. Enter the parameters below, being careful not to switch SIEBEL with SADMIN, and clicking Next each time to proceed through the configuration: Note: Throughout this course, tables such as the one below are used to provide parameters for multiple installation screens. If you are trying to enter a parameter from the table and do not see it on the screen, please click Next to advance to the next screen. Similarly, in later practices the final confirmation steps (such as clicking Next in the Summary screen) may be omitted.
Parameter Siebel Server Directory Siebel Database Server Directory Database Platform Action Option Option Value D:\OUses\siebsrvr D:\OUses\dbsrvr Oracle Database Enterprise Edition Install Database Install Siebel Database Purpose Used to access Siebel Server executables and template files. Used to access Siebel Database Server executables and template files. Determines which SQL scripts to run to populate the schema and seed data. Used to create the schema and seed data. Install a database or add a language.
Yes, I wish to install a new Verify database installation. Siebel Database
GRANTUSR.SQL GRANTUSR.SQL has been Specify that GRANTUSR.sql has been run. run by the DBA to create Siebel users and roles UNICODE ODBC Data Source Name Database User Name Database Password - and confirm Database Table Owner UNICODE Database OUEnt_DSN Determines available character sets. Used to connect to database. Enterprise name suffixed by _DSN. This connection was created when you configured the Siebel Enterprise. Used to populate seed data. Used to populate seed data.
SADMIN SADMIN
SIEBEL
Used to generate schema. Used to generate schema.
Database Table SIEBEL Owner Password - and confirm Index Table Space Name Table Space Name Enter license key? siebelindexts siebelts
Contains Siebel indexes. This tablespace was created for you by your DBA. Contains Siebel data tables. This tablespace was created for you by your DBA.
Yes, I would like to enter it Enter the license key to allow initial login; license keys may be added later, if desired. However, if now you do not enter a license key, you will need to use the Siebel Developer Web client to enter one later. <Copy and paste first line License keys are available from Oracle at http://licensecodes.oracle.com. from D:\labs\8.1_Install\SIAkeys
License Key
26
.txt > Parallel Indexing Does not use the Oracle Parallel Indexing option SSE_ROLE install For database servers with multiple CPUs, using multiple indexing threads can improve performance. It is not enabled in the classroom. Default database role for Siebel users; created by GRANTUSR.SQL. Where to store installer log information.
Security Group ID/Grantee Log Output Directory
c. d. e. f.
g. h. i. j.
6. Verify the database installation: a. In SQLPlus, enter: connect SIEBEL/SIEBEL; This connects you as the Siebel database owner. Do not forget the semicolon. b. Enter select count (*)from S_ZIPCODE; This returns the number of records in the Zip Code table. It should be a number in the thousands. If it is 0, contact your instructor. c. Enter exit to exit SQLPlus.
27
Select Yes apply configuration changes now and click Next. Review the summary and click Next. Click Yes to execute the configuration. Click OK to begin the database installation. The database installation should take approximately 60-75 minutes. Note: Notify your instructor once you have started the database installation. Once all students have started the database installation, it is a good time for either a lunch break or the next lecture. Once installation completes, click OK to close the Upgrade Wizard. Switch to the Oracle Installer application and click OK in the Execution Successful dialog box. Click Cancel to exit the configuration tool. Click Yes to confirm the cancellation.
28
Lesson 4: Installing a Siebel Server
Practice 4-1 Configuring a Siebel Server

Goals To configure the Siebel Server you installed as part of the Siebel Enterprise Server installation 15 20 minutes
Time
Instructions:
In this practice, you will configure the Siebel Server that you installed in the previous practice on installing the Siebel Gateway Name Server. Recall that you installed the Siebel Server files to provide support for the Siebel Gateway Name Server service; it is not necessary to configure and run a Siebel Server on the Siebel Gateway Name Server machine. However, in this case you will colocate your Siebel Server with your Siebel Gateway Name Server, so you will configure this server. 1. Verify that a Siebel Server service has not yet been configured: a. Return to the Services window. b. Scroll down and confirm that no Siebel Server services exist; that is, the only service with the word Siebel in it is the Siebel Gateway Name Server service. c. Minimize the Services window. 2. Run the Siebel Server configuration tool to configure a Siebel Server service on your machine: a. Select Start > Programs > Siebel Enterprise Server Configuration 8.1 > Siebel Server Configuration. b. Enter the parameters below, clicking Next each time to proceed through the configuration: Note: After selecting the action, you will receive a warning that you need to have an existing Siebel database. You configured this database in a previous practice, so you may safely click Next.
Parameter Configuration Mode Value Configure Product in Live Mode Create New Configuration SADMIN Purpose Use offline configuration to generate an installer response file; details are in a later lesson. Can also add a language or remove a configuration; details are in a later lesson. Used to log in to the Siebel Gateway Name Server to collect information about the Siebel Enterprise. Used to log in to the Siebel Gateway Name Server to collect information about the Siebel Enterprise.
Action Gateway Name Server Authentication User Account Name Gateway Name Server Authentication User Account Password - and confirm Gateway Name Server Host Name
SADMIN
<machine name> Used to contact the Siebel Gateway Name Server.
29
Gateway Name Server TCP/IP Port
2320
Port number on which the Siebel Gateway Name Server machine is listening for connections. The logical name of the Siebel Enterprise. Used to connect to the Siebel Enterprise to get the enterpriselevel parameters. The value is case-sensitive. A string of up to 12 characters including letters, numbers, and underscores that uniquely identify the Siebel Server. A description displayed in several of the administrative views. Which component groups should be enabled on the Siebel Server when it first starts. These component groups can be changed in the Administration - Server Configuration screen once the Siebel Server has been configured. However, to be able to log in, at least one Application Object Manager on one Siebel Server must be enabled. Port on which the Siebel Server listens for connections; for example, from the Siebel Web Server Extension. Port used by Siebel Remote for synchronization. If you do not enable the Siebel Remote component group on this server, this port will not be used. Configure SSL, LDAP, or Exchange synchronization Used by the Siebel Connector for Oracle Applications to connect to back office Oracle databases Cluster Siebel Servers to provide redundancy in case of Server failure For most deployments, the Siebel Server should start up when the system boots. To preserve system resources, do not do this for this course Whether or not to start the Siebel Server service as soon as the profile execution completes.
Siebel Enterprise Name OUEnt
Siebel Server Name
OUSrvr
Siebel Server Description Enable Component Groups
Siebel Server OUSrvr Call Center
Siebel Connection Broker Port
2321
Network TCP/IP Port for 40400 Synchronization Manager Additional Tasks None Register External Oracle Selected DB ODBC Driver Clustering Configuration Not clustered Set the Siebel Server system service to start automatically Start Siebel Server service at the end of profile execution Not Selected
Not Selected
c. Click Next several times until you see the summary information. Click Next once again. d. Click Yes to confirm execution. It should take 1-2 minutes to complete, at which point a confirmation dialog box appears. e. Click OK in the Successful dialog box. f. Select Exit Configuration Wizard and click Next. 3. Verify that the Siebel Server service starts successfully: a. Return to the Services window. b. Select Action > Refresh to refresh the view. c. Verify that a service named Siebel Server [OUEnt_OUSrvr] exists and is not started. d. Right-click the Siebel Server [OUEnt_OUSrvr] service and select Start. e. Minimize the Services window. f. Right-click the task bar at the bottom of the screen and select Task Manager.
30
g. h. i. j. k. l. m. n.
o. p.
31
Click the Performance tab. Wait for CPU Usage to stay below 50%. This should take 3-4 minutes. Minimize the Task Manager. Bring up the Services window again and confirm that the Siebel Server [OUEnt_OUSrvr] service is listed as Started. Minimize the Services window. Using Windows Explorer, navigate to D:\OUses\siebsrvr\log. If necessary, select View > Details to expose the file sizes. There should be several files, none of which are over 10 KB in size. Use Notepad to examine OUEnt.OUSrvr.log. If you see error messages beyond simple notifications, try restarting the Siebel Server service. Note: When the Siebel Server service is restarted, one of its first actions is to copy all of the existing log files from D:\OUses\siebsrvr\log to D:\OUses\siebsrvr\logarchive. This ensures that you have an archive of all server log files without cluttering the log directory with obsolete logs. If restarting the service does not solve the problem, open the log and attempt to diagnose the problem. Ask your instructor for help. Close any open log files, not saving any changes.
32
Lesson 5: Installing the Siebel Web Server Extension
Practice 5-1 Installing the Siebel Web Server Extension

Goals Time To install, configure, and test the Siebel Web Server Extension 20 25 minutes
Instructions:
1. Install the Siebel Web Server Extension: a. Using Windows Explorer, navigate to D:\labs\8.1_Install\Installers\Server\Siebel_Web_Server_Extension. b. Double-click setup.exe. The setup program should be run on the machine hosting the Web server. c. Use the parameters below to perform the installation, clicking Next each time to proceed through the installation. This copies all of the SWSE files to the installation directory, but performs no configuration.
Parameter Directory Name Language(s) Program Folder Value D:\OUWebServer\SWEApp enu - English (American) Siebel Enterprise Server Configuration 8.1 Purpose Location to place installed files. Which language-specific files to install. Directory in Windows Start menu.
d. Once installation completes after a few minutes, the Siebel Web Server Extension Configuration Tool starts automatically. 2. Explore the installation prior to running the Configuration Tool: a. Navigate away from the Configuration Tool, leaving it open. b. Examine the default configuration file. This is a generic template file that will be replaced by the one you generated when you created the SWSE logical profile: i. Use Notepad to open D:\OUWebServer\SWEApp\ADMIN\t_swseapps.cfg. This is the template configuration file. ii. Verify that t_swseapps.cfg contains configuration settings for many applications (for example, callcenter_$(DeployedLanuage)). What is the default value for AnonUserName (near the top of the file)?
iii.
Close t_swsepps.cfg, not saving any changes.
33
In this practice, you will install, configure, and test the Siebel Web Server Extension (SWSE). The Siebel Web Server Extension consists of an executable (a .dll file in this case, as you are working in a Windows environment), a configuration file for that executable, and a set of virtual directories that invoke that executable whenever a <swe> tag is encountered in the underlying HTML document.
3. Return to the Siebel Web Server Extension Configuration Tool and complete the configuration using the parameters below, clicking Next each time to proceed through the configuration:
Parameter Action Load Balancer Value Apply an SWSE Logical Profile Purpose Creates virtual directories on Web server and copies eapps.cfg and other support files to SWSE install directory.
Single Siebel Server If load balancing is selected, balances sessions for enterprises with multiple Application Object Managers of the same type. <machine name> 2321 If load balancing is not selected, the single Servers name will be written into eapps.cfg. If load balancing is not selected, the single Servers connection broker port will be written into eapps.cfg. The location of the logical profile that will be applied to generate eapps.cfg and the virtual directories.
Siebel Server Host Name Siebel Server Connection Broker Port Number Siebel Web Server Extension Logical Profile Location
D:\OUses\gtwysrvr\ ADMIN\Webserver
4. Click Next twice and then Yes to execute the configuration. Note that a command window opens to run the eapps_virdir.bat batch file; do not proceed until the window closes and configuration is complete. This should take 1-2 minutes. 5. Click OK in the Execution Successful dialog box, and then Finish in the installer. 6. If necessary, click Next then Finish to exit the After Intallation dialog box.
c. Examine the configuration file generated when you created the SWSE logical profile during your Siebel Enterprise Server installation. The data in this file, as well as the configuration information you supply when applying the logical profile, will be used to replace the template eapps.cfg file: i. Use Notepad to open D:\OUses\gtwysrvr\ADMIN\Webserver\eapps.cfg. ii. Examine the file. Notice that the AnonUserName is GUESTERM; the value you entered when configuring the SWSE logical profile. iii. Close eapps.cfg, not saving any changes. iv. Right-click eapps_virdirs.bat and select Edit. This batch file is executed to generate the virtual directories that will be used by the various applications. Many customers edit this file to, for example, reduce the number of virtual directories created in the Web server, rename the application, or remove the language suffix from the application. v. Close eapps_virdirs.bat, not saving any changes. d. Select Start > Programs > Administrative Tools > Internet Information Services (IIS) Manager to open Microsofts Internet Information Services Manager. This is the third-party Web server used in this class. e. In the left pane, if necessary expand your <machine name>, and then expand Web Sites and then Default Web Site. f. Confirm that there are no virtual directories of the form <application>_<language code> (for example, callcenter_enu) for the default Web site. g. Minimize Internet Information Services (IIS) Manager.
35
7. Verify the installation: a. Open D:\OUWebServer\SWEApp\bin\eapps.cfg and verify that the connect strings for the applications now include the server name and connection broker port you entered; for example, //edpsr56p1:2321. b. Return to Internet Information Services (IIS) Manager, select Default Web Site in the left pane, and then select Action > Refresh. Confirm that there are now many virtual directories of the form <application>_<language code>. c. Close all open applications and files. d. If necessary, start the Siebel Server service: i. Select Start > Programs > Administrative Tools > Services. ii. Scroll down to locate Siebel Server [OUEnt_OUSrvr]. iii. If its status is not Started, right-click Siebel Server [OUEnt_OUSrvr] and select Start. iv. Right-click the task bar at the bottom of the window and select Task Manager. v. Click the Performance tab. vi. Wait until CPU usage drops below 50% for several seconds. The Siebel Server service may take several minutes to start. vii. Minimize the Task Manager and the Services dialog box. e. Select Start > Programs > Internet Explorer. f. Enter an address of http://localhost/callcenter_enu and click Go. If the installation is successful, a Siebel Call Center login screen should appear:
g. Log in using:
User ID Password SADMIN SADMIN
ii. iii. iv.
v. vi. vii. viii. ix.
near the top of the screen. In the Siebel application, click the Site Map icon Click the Administration - Application link. Under Administration - Application, click License Keys. Note: In future practices, this navigation may be abbreviated as, Navigate to Administration - Application > License Keys. Note the lack of a mention of the Site Map icon. Click New. Paste the key in the Key Value field and step off the record. If you receive an Invalid Key error, try re-copying and re-pasting the key. Step off the record to save it. Repeat these steps for the other keys in SIAkeys.txt. Close SIAkeys.txt.
8. Throughout the course, you will be using the Administration - Server Configuration and Administration - Server Management screens. Set your user preferences to make these tabs visible when you log in. i. From the application-level (blue) menu, select Tools > User Preferences. ii. Select Tab Layout from the drop-down list just to the right of Expense Reports.
36
Click the arrow to log in. Note: If you cannot log in or the login fails, please refer to the troubleshooting steps below. h. If necessary, dismiss the various information boxes: Note: Due to the configurations necessary to relax the security constraints of the classroom machines, you will probably not see these warnings in an Oracle classroom. i. When asked whether to install the ActiveX controls, click Install. ii. Click AutoFix in the Browser Health Check. iii. Click Run in the Browser Health Check. i. Add the additional license keys. i. Use Notepad to open D:\Labs\8.1_Install\SIAKeys.txt and copy the second key.
iii. Select the Hide checkbox next to item 8 (Administration - Product). iv. Scroll down and deselect the Hide checkbox next to items 55 and 56. b. In the Siebel application, select File > Log Out from the application-level (blue) menu. c. Close Internet Explorer. Troubleshooting (Optional Reading Practice) Most people performing installations first realize that there is a problem with their installation at this point; they have installed the Siebel Gateway Name Server, Siebel Server, and Siebel Web Server Extension, yet they cannot bring up their login screen or cannot log in. Here are some debugging tips to help resolve a failed installation: You start the browser, enter the address for your virtual directory (for example, http://<machine name>/callcenter_enu) and receive the message:
The server you are trying to access is either busy or experiencing problems.
This indicates that the Web server is correctly routing requests to the server, but the server is unable to process them. o Is the Siebel Server service running? If not, try restarting it. If it stops again, check the logs in D:\OUses\siebsrvr\log to try to determine which component is failing, and why. Larger, more recent logs are most likely to contain the pertinent information. o Did you remember to enable to Application Object Managers component group? Check to make sure the appropriate AOM log file exists and contains data; for example, SCCObjMgr_enu.log. If the logs are not there, it is likely you did not enable the AOM. You will either have to re-configure the Siebel Server (run the Configuration Tool to remove it, and then run it again to recreate it), or use the Siebel Developer Web client to enable the AOM on the server. o Did you correctly configure the database connection information? Try testing the ODBC connection manually in the ODBC Data Source Administrator to make sure it is correctly configured. o Has the database been correctly populated with Siebel tables and seed data? Perform the confirmation steps from the database configuration practice to ensure the database has been correctly configured. o Did you install a license key in the database? Use the Developer Web client to add license keys to the database. Note that this requires installing the Developer Web client, which is covered in a later practice. o Are the correct users added to both the database and the application? You used SADMIN and GUESTERM in this course because they are populated as employees in the Siebel application as part of the seed data. If you use different users, they may not exist in the application; you will need to add them using the Developer Web client. Other common issues o Is the Web server running? o Is the Siebel Gateway Name Server running? o Does the machine have access to the Siebel File System? Did you specify the path correctly? o Did you enable LDAP authentication without configuring the LDAP parameters in the application?
37
Solutions 5-1 Installing the Siebel Web Server Extension

Answers
2.b.ii. Verify that t_swseapps.cfg contains configuration settings for many applications (for example, callcenter_$(DeployedLanuage)). What is the default value for AnonUserName (near the top of the file)? $(EmplLoginUserName). This indicates that the generated eapps.cfg will use the employee login user name, which you entered as GUESTERM when you configured the SWSE logical profile.
38
Lesson 6: Installing the Siebel Developer or Mobile Web Client
Practice 6-1 Installing the Developer Web Client

Goals Time To install and configure the Siebel Developer Web Client 25 30 minutes
Instructions:
Note: You are installing the Developer Web client at this point to help you debug any later configurations. The Developer Web client is an extremely useful tool in dealing with misconfigured enterprises. However, if you do not complete this practice, it will not affect future practices. 1. Install the Siebel Developer Web Client: a. Using Windows Explorer, navigate to D:\labs\8.1_Install\Installers\Client\Siebel_Web_Client\Disk1\install b. Double-click oui.exe. Note that this is not the same as the setup.exe executable you have run for every other installer so far. c. Click Next on the Welcome screen. d. Enter the installation parameters below, clicking Next to proceed through the installation:
Parameter Name Path Product-Specific Prerequisite Checks Value Siebel_Web_Client_81 D:\OUClient Next Purpose Name of the Program Folder containing the shortcuts. Location in which to install the files. Click Next. Click Yes to proceed through the warning; it is generated because you do not have Microsoft Word installed on your classroom machine. Language(s) to install. Click Next.
Select Languages
English
Welcome to Siebel Next Business Applications Client Setup Client Type Developer Web Client
Select Mobile Web Client to end the installation here, right after specifying a Siebel Server with which to synchronize. The Developer Web Client needs significantly more information, including how to connect to the Gateway Name Server and Siebel database.
Siebel Database Server
Oracle Database Server Database platform of the enterprises database.
39
In this practice, you will install the Siebel Developer Web Client, and confirm that you can connect to the Siebel database whether or not the Siebel Server is running. You will then examine the configuration file to see how to set various connection options.
Database Alias
SIEBELDB
Connection information for contacting the database; in this case, the connection string already created for the Oracle database. Used to read database schema. Used to read data from the enterprises Siebel File System. See the note below with regards to using an absolute file path. Used for synchronization with a Siebel Server, if desired. See the note below with regards to using localhost. Used to connect to the Siebel Gateway Name Server. See the note below with regards to using localhost. Used to collect enterprise information. The name of a Siebel Server on which the Server Request Broker component is running. Location of the search server, if any. Since there is no search server, leave this value at its default. See the note below with regards to using localhost. Leave this at its default. Click the Install button.
Table Owner File System Server
SIEBEL D:\siebfile
Siebel Remote Server localhost
Gateway Name Server Address Enterprise Server Name
localhost
OUEnt
Request Server Name OUSrvr Search Server Hostname localhost
Search Server Port Number Summary Screen
2048 Install
e.
f. g. h.
Note: You would normally use machine names rather than localhost on these machines, as well as a network file path. In the classroom environment, your machine name has been added to the Trusted Sites list, which hides some of the client behavior you would see in a production environment. By using localhost rather than machine name, you see this behavior. During installation (after around 1-2 minutes), the installer invokes an instance of Internet Explorer in order to download the required ActiveX controls for the Developer Web client. Dismiss any warnings and allow the download to complete. Note: You may see a yellow bar at the top of the window warning you about blocked content. Right-click the bar and select Allow Blocked Content, then click Yes. After that, you may be asked whether to install Outlctrix.cab. Clck Install. Once the Internet Explorer window indicates that the download is complete, close Internet Explorer and return to the installer window. The installer should continue running. Once installation completes, click Exit and then click Yes. If necessary, in the Finish Admin Install dialog box click Next and then click Finish to dismiss it.
2. Create a new Developer Web Client shortcut to use uagent.cfg, the Siebel Call Center configuration file. This allows you to compare the Developer Web Client version of Siebel Call Center with the Web client version you have been using in the rest of this class. a. Select Start > Programs > Siebel_Web_Client_81 > Siebel Web Client 8.1, but do not select any application.
40
j. Enter:
User ID Password Connect To SADMIN SADMIN Server
k. Click OK to log in. The initial login may take 2-3 minutes as the executable loads all of its configuration information and connects to the database. Notice that the Developer Web Client version of Siebel Call Center looks identical to the Web (thin) client version.
41
b. Right-click a convenient application such as Siebel Oil, Gas & Chemicals - ENU and select Send To > Desktop. c. Select the desktop and locate the new shortcut. d. Right-click the shortcut and select Properties. e. Under the Shortcut tab, in the target field, scroll to the left to change the beginning to D:\OUClient\BIN\siebel.exe /c D:\OUClient\bin\ENU\uagent.cfg. This should only involve changing the name of the configuration file to uagent.cfg. f. Click the General tab. g. Change the name of the shortcut to Siebel Call Center - ENU. h. Click OK. Course Note: This shortcut is also provided in D:\labs\8.1_Install\Solutions\DeveloperWebClient. i. Double-click the Siebel Call Center - ENU shortcut. Notice that this login screen includes a Connect To field. This field allows you to select which database the Developer Web client connects to. By default, you can select a Local, Sample, or Server database. You can add additional data sources by editing the application configuration file.
l. If necessary, click Auto Fix in the Browser Health Check and then click Run. 3. Compare the functionality of the Developer Web (thick) client with the Siebel Server and Gateway Name Server running and stopped: a. Navigate to Administration - Server Management > Enterprises: i. Click the Site Map icon near the top of the screen. ii. Scroll down and click the Administration - Server Management link. iii. Click the Enterprises link. Note that you can monitor and administer servers from within the thick client, as the Siebel Server is available for administration. In particular, note that the Server is shown and its state is Running. In Microsoft Windows, return to the Services window and stop the Siebel Server [OUEnt_OUSrvr] service. i. Right-click the Siebel Server [OUEnt_OUSrvr] service and select Stop. Note: Because of the heavy load on your classroom machine, you may receive a message that the service could not be stopped in a timely manner. This is harmless; click OK to dismiss the warning and proceed with the practice. ii. Minimize the Services window. Return to the thick client and click the Accounts tab. Note that you can continue to navigate through the application even though the Siebel Server is not running. Click the My Accounts link. Notice that there are no account records in the server database. Click the browsers Back button until you return to the Administration - Server Management > Enterprises view. Notice that you can still access this view, but that the Siebel Server is listed as unavailable. (Most likely because the handshake failed). Select Help > Technical Support. Notice that the connect string to the enterprise database is SIEBELDB, the Oracle SQLNet connect string you provided when installing the Siebel Enterprise. The enterprise uses both ODBC and direct (native) connections to the database, depending on the situation. For example, for authentication it uses the ODBC connection. Close the Technical Support dialog box. In Microsoft Windows, return to the Services window. Stop the Siebel Gateway Name Server service. Minimize the Services window. Return to the thick client. Click the Contacts tab. Note that you can continue to navigate even without the gateway name server service. The thick client connects directly to the server database, bypassing the Siebel Server and Siebel Gateway Name Server. Click the browsers Back button to return to the Administration - Server Management screen. This time the screen returns an error. The gateway name server must be available in order to use this screen. Log out of the thick client. i. From the application-level (blue) menu, select File > Log Out.
b.
c.
d. e. f.
g.
h. i. j. k. l. m.
n.
o.
42
5. Using Windows Explorer, navigate to D:\OUClient\OBJECTS\ENU. This directory contains the Siebel repository file (.srf) used by the Developer Web Client. Recall that this is a compiled, compressed version of the Siebel Repository, and contains the object definitions defining the business logic and appearance of the application.
43
4. Examine the Siebel Call Center configuration file to learn about the customizations available for the Developer Web Client: a. Use Notepad to open D:\OUClient\BIN\ENU\uagent.cfg. This is the configuration file for Siebel Call Center. b. Examine the [Siebel] section. It includes overall parameters such as ODBC data source names (the ODBC connections are created by the installer), application title, and so forth. The only parameter that is frequently edited in this section is EnableFQDN; by default, the Developer Web Client uses an address of the form <machine name>.<full domain name>, where the <domain name> is specified by the FQDN parameter. Setting EnableFQDN to FALSE causes the Developer Web Client to use localhost instead. c. Examine the [InfraSecMgr] section. This determines the security adapter used by the Developer Web Client. The [DBSecAdpt] and [LDAPSecAdpt] sections farther down in the file provide connection information for the security adapter. Note that the [DBSecAdpt] section is populated by the installer; the [LDAPSecAdpt] section must be manually edited to enable LDAP authentication for the Developer Web Client. d. Examine the [Datasources], [Local], [Sample], and [ServerDataSrc] sections. These frequently-edited sections determine how the Developer Web Client connects to various data sources. You may add custom data sources here by creating a new datasource entry and another datasource section. e. Close uagent.cfg, not saving any changes.
Practice 6-2 Installing the Sample Database

Goals Time To install and explore the Siebel Sample database 10 15 minutes
Instructions:
Note: This practice is only used once more during the course, to test the Siebel Tools connection to the Sample database. If you do not complete it, it will not significantly affect your progress in the course. 1. Install the Sample database: a. Using Windows Explorer, navigate to D:\labs\8.1_Install\Installers\Client\Siebel_Sample_Database. b. Double-click install.exe. c. Enter the installation parameters, clicking Next to proceed through the installation:
Parameter Setup Language Setup Type Value English Typical Purpose Language in which to run the installation. A typical installation installs a default set of components. Selecting Custom allows you to select which components to install. Location in which to install the files. The Sample database installer requires an existing Siebel Developer or Mobile Web client installation. Languages to install for the Sample database. Note that the Sample data itself is in American English; only the application strings and menu items are translated. Folder in which the applications will appear in the Windows Start menu; the Siebel Sample database includes several demo applications which are placed in this Start menu.
Directory
D:\OUClient
Languages to Install Base + Language Files English (American)
Program Folder
Siebel Web Client 8.1
Installation should take around 10 minutes. Complete the dialog boxes (click Next, Yes, or Finish, as appropriate, to dismiss the confirmations) once installation completes. 2. Select Start > Programs and notice that there is a new Siebel Web Client 8.1 program folder that contains various demo applications; for example, Siebel Call Center Demo - ENU. These demos
In this practice, you will install the Siebel Sample database and log in. The Sample database is a populated local database, allowing a developer to explore application functionality and test configuration changes against a populated database.
are simply thick client connections to the Sample database, with the username and password specified in the shortcut. 3. Test the Sample database using the Developer Web Client. a. Double-click the desktop shortcut for Siebel Call Center - ENU. b. Enter:
User ID Password Connect To SADMIN SADMIN Sample
f.
g.
h. What is the full path to the Siebel Repository File?
i. Click OK to dismiss the Technical Support dialog box. j. Log out of Siebel Call Center. 4. Start the Siebel Gateway Name Server Windows service. You will need it running for the next practice. 5. Start the Siebel Server [OUEnt_OUSrvr] Windows service. You will need it running for the next practice. 6. Close the SQL Anywhere database connection. By default, the connection is left open to improve performance when restarting the thick client: a. In the Windows task bar notification area (at the bottom right of the screen), locate the SQL Anywhere icon . b. Right-click the icon and select Exit. You will not be using the Sample database again in this course.
45
c. d. e.
Note: Be careful not to accidentally log in to the Server database. Click OK to log in Click the Accounts tab. Click My Accounts and verify that many accounts are listed. The Sample database is a populated local database used for rapid deployment testing. Select Help > Technical Support. Notice the connect string to the Sample database, which provides a full path to the SQL Anywhere database, rather than the Oracle SQLNet connect string you saw for the Server database connection. What is the User ID of the current user?
Solutions 6-2 Installing the Sample Database

Answers
3.g. 3.h. What is the User ID of the current user? SADMIN. What is the full path to the Siebel Repository File? D:\OUClient\objects\enu\siebel_sia.srf.
46
Lesson 7: Configuring Other Authentication Mechanisms
Practice 7-1 Configuring an Application Object Manager to use LDAP Authentication

Goals To configure the Siebel Sales Application Object Manager (AOM) to use LDAP authentication 25 35 minutes
Time
In this practice, you will configure the Siebel Sales AOM to use LDAP authentication instead of database authentication. This requires configuring the LDAP server, installing the IBM Tivoli LDAP client on the Siebel Server, and configuring the appropriate parameters within the Siebel application. Make sure that you configure the Siebel Sales AOM; this ensures that if you make a mistake, you can still log in using Siebel Call Center to adjust the parameters. Note: While it is possible to enable LDAP authentication for an entire server or even the entire enterprise, this can significantly impact performance, as many batch and system components directly access the database. Recommended practice is to use LDAP only for AOMs to manage users logging in to the system. Note: It is not necessary to complete this practice in order to do the rest of the practices in this course; however, be sure to perform the final step to set Siebel Sales back to database authentication if you do not complete the practice. 1. Configure the LDAP server to support Siebel users. For this class, you will be using Oracle Internet Directory service as an LDAP server. In addition to an LDAP username and password, the required parameters are a Siebel user ID, database username, and database password: a. Start the OracleOIDProcessManager service. This service supports the Oracle Internet Directory. i. If necessary, select Start > Programs > Administrative Tools > Services. ii. Scroll down and locate the OracleOIDProcessManager service. iii. If necessary, right-click the service and select Start. iv. Minimize the Services window. b. Select Start > Programs > Oracle - OraDb10g_home1 > Integrated Management Tools > Oracle Directory Manager. This is the management tool used to manage OIDs LDAP server. Note: Be careful to use the path indicated above; because both the Oracle database and Oracle Internet Directory are installed on your machine, there are two instances of the Oracle Directory Manager executable. Choosing the wrong path will result in your configuration screens not exactly matching the screens shown below. c. Click OK in the Directory Server Connection dialog box. d. Click Add to add a connection.
47
Instructions:
e. Enter your <machine name> as the server. Leave the port number at its default of 389. f. Click OK. g. Verify that the server is listed as available. Note that your machine name will be different.
h. Click OK. i. Log in as:

User Password orcladmin oracle1
j. Click Login. k. Disable the default password policy. By default, OID requires strong passwords. The Siebel passwords you have been using do not meet this requirement, hence you need to disable security to be able to create the Siebel users and their passwords in the LDAP directory. i. In the left pane, expand Password Policy Management. ii. Select cn=default. iii. In the right pane, change Enable OID Password Policy to Disable.
Click Apply. Repeat these steps to disable the Password Policy for Realm dc=us,dc=oracle,dc=com. l. Add SADMIN as an LDAP user. This requires creating SADMIN as a user, and putting the Siebel database connection informations into one of the attributes (fields) for that user. You will use the description field to store the database connection information. In a production deployment, your LDAP administrator would create a new attribute to store this string.
iv. v.
i. ii. iii. iv.
Select Operation > Create Entry from the application-level menu. Click Browse next to the Distinguished Name field. Expand All Entries, then dc=com, then dc=oracle, and finally dc=us. Select cn=Users. This is the default directory for creating new users in this deployment of OID.
v. vi.
Click OK. Enter cn=SADMIN, before the other entries in the distinguished name field. The complete distinguished name of your entry should be cn=SADMIN,cn=Users,dc=us,dc=oracle,dc=com (With no spaces)
Note: The distinguised name is a set of parameters uniquely identifying an entry in the LDAP directory. It is typically an identifier (in this case SADMIN), a group (in this case Users), and then domain information (for example, us.oracle.com appears as dc=us,dc=oracle,dc=com). Course Note: All of the text strings used in this course are contained in text files, allowing you to copy and paste the strings instead of having to type them manually. The strings used in OID for this practice are contained in D:\labs\8.1_Install\Solutions\LDAP\OIDStrings.txt. vii. Click Add to add an object class. In Oracle OID, an objects class determines its attributes. You can select more than one class, and your object will have the union of all
49
the attributes. Note that before you select a class, you cannot add any further attributes; once you select a class, a set of attributes appropriate to that class is made available. viii. Scroll down to select Person and click Select. The Person class contains sufficient attributes for your work here.
ix.
x.
Under Mandatory Properties, enter SADMIN in the cn area. This is the attribute the Siebel application will use to search for the entry. It represents the top-level attribute of the Distinguished Name. Enter cn=Users,dc=us,dc=oracle,dc=com in the sn area. This represents the remainder of the Distinguished Name attribute. You will enter this string in the Siebel application as the Base Directory in which to search for LDAP entries.
xi.
Click the Optional Properties tab. These are the additional attributes provided by the Person class. xii. Under description, enter username=GUESTERM password=GUESTERM The format of the string is critical; this is the string that the Siebel application will use to connect to the database. Many LDAP issues can be traced to entering this string incorrectly; for example, by including a comma or forgetting the space.
50
2. Change the access permissions to allow users to modify LDAP entries. This allows users who are logged in to the Siebel application to modify the LDAP directory. For example, you may want to allow users to change their own password, or to create new employees, as you will do later in this practice. In a real deployment, the LDAP administrator would consider these privileges carefully, and grant certain permissions (such as user creation) to a limited number of users. a. Allow all users to access the Users directory in the LDAP directory structure, including creating or deleting entries:
51
Note: You use GUESTERM here because whatever username and password you use here will be propagated to any users created by SADMIN. For example, if SADMIN logs in to the Siebel application and creates NEWUSER, then NEWUSER is created in the LDAP directory with a connection string of username=GUESTERM password=GUESTERM. Thus, you want to choose a database user with limited application privileges for security reasons. xiii. Scroll to the bottom of the properties list and enter SADMIN as the userPassword. xiv. Click OK. SADMIN should be entered with no errors. m. Repeat these steps to add GUESTERM as a registered user. Recall that the anonymous connection uses GUESTERM to display the initial login screen, so GUESTERM must also be entered in the LDAP directory: i. Select Operation > Create Entry from the application-level menu. ii. Click Browse next to the Distinguished Name field. iii. Expand All Entries, then dc=com, then dc=oracle, and finally dc=us. iv. Select cn=Users. v. Click OK. vi. Enter cn=GUESTERM, before the other entries in the distinguished name field. The complete distinguished name of your entry should be cn=GUESTERM,cn=Users,dc=us,dc=oracle,dc=com. (With no spaces) vii. Click Add to add an object class. viii. Scroll down to select Person and click Select. ix. Under Mandatory Properties, enter GUESTERM in the cn area. x. Enter cn=Users,dc=us,dc=oracle,dc=com in the sn area.. xi. Click the Optional Properties tab. These are the additional attributes provided by the Person class. xii. Under description, enter username=GUESTERM password=GUESTERM. xiii. Scroll to the bottom of the properties list and enter GUESTERM as the userPassword. xiv. Click OK. GUESTERM should be entered with no errors.
i.
In the left pane, expand Entry Management, dc=com, dc=oracle, dc=us, and select cn=Users:
ii. iii.
Click the Subtree Access tab in the right pane. Click Create via Wizard under Structural Access Items. Important Note: There are two Create via Wizard buttons on the screen. You will use the top one in this step, and the bottom one in a subsequent step:
iv. v.
Click Next. You will not be filtering the object classes. Click Next. With no filter, you do not need any criteria.
52
3. Test your LDAP settings: a. Select Start > Programs > Oracle - OraDb10g_home1 > Integrated Management Tools > Oracle Directory Manager. b. Enter:
User Password cn=SADMIN,cn=Users,dc=us,dc=oracle,dc=com SADMIN
c. d. e. f. g.
Note that the user name is the Distinguished Name for SADMIN. Click Login. In the left pane, expand Entry Management, dc=com, dc=oracle, dc=us, and cn=Users. Confirm that you can see SADMIN and GUESTERM as users. This confirms that SADMIN has access to the LDAP directory. Select File > Exit to exit Oracle Directory Manager. Repeat these steps to test the GUESTERM entry: i. Select Start > Programs > Oracle - OraDb10g_home1 > Integrated Management Tools > Oracle Directory Manager. ii. Enter:
User Password cn=GUESTERM,cn=Users,dc=us,dc=oracle,dc=com GUESTERM
Click Login. In the left pane, expand Entry Management, dc=com, dc=oracle, dc=us, and cn=Users. Confirm that you can see SADMIN and GUESTERM as users. This confirms that GUESTERM has access to the LDAP directory. h. Minimize Oracle Directory Manager. 4. Install the IBM LDAP client on your Siebel Server machine. This client provides executables used by the Siebel Server to connect to the LDAP server: a. Unzip D:\Labs\8.1_Install\Installers\Server_Ancillary\IBM_LDAP_6.0_Client\enu\itds60client-win-ia32-ismp.zip to D:\Temp. b. Using Windows Explorer, navigate to D:\Temp\itdsV60Client\itds.
iii. iv. v.
53
Verify that Everyone is selected and click Next. All users will be able to perform the actions you select. In a production-level deployment, your LDAP administrator would restrict this access. vii. Accept the default access (Browse, Add, and Delete) and click Finish. This allows all users to view the Users directory, and Add or Delete users. b. Allow all users to modify existing LDAP entries in the Users directory: i. Click Create via Wizard under Content Access Items (the bottom panel). ii. Click Next. Once again, no filtering is required. iii. Verify that Everyone is selected and click Next. iv. Click Next. v. Select Grant for all options (Read, Search, Write, SelfWrite, and Compare) and click Finish. c. Select File > Exit to exit Oracle Directory Manager.
vi.
c. Double-click setup.exe. Since you are not using SSL you need just the basic Tivoli client. If you were using SSL you would need to install the GSKit as well. d. Accept English as the setup language and click OK. e. Click Next in the Welcome screen. f. Select I accept the terms in the license agreement and click Next. g. Accept the default installation directory and click Next. h. Uncheck GSKit so that only Client SDK 6.0 is selected and click Next. i. Click Next to perform the installation. j. Click Finish to exit the wizard. k. If necessary, click Next then Finish to exit the After Intallation dialog box.
User ID Password
SADMIN SADMIN
b. Click the arrow. c. Navigate to Administration - Server Configuration > Enterprises > Profile Configuration. d. In the middle applet, query the Profile column for LDAP* to locate the LDAP Security Adapter profile.
54
5. Configure the LDAP Security Adapter profile: a. Start the Siebel Call Center Web Client: i. Select Start > Programs > Internet Explorer ii. Enter Address: http://localhost/callcenter_enu. iii. Enter:
e. In the bottom applet, carefully change the parameters. Do not include the carriage returns, which were included here for space purposes: Course Note: All of the text strings used in this course are contained in text files, allowing you to copy and paste the strings instead of having to type them manually. The strings used in the Siebel application for this practice are contained in D:\labs\8.1_Install\Solutions\LDAP\SiebelServerStrings.txt.
Parameter Application User Application Password Base Dn Credentials Attribute Type Value cn=SADMIN,cn=Users, dc=us,dc=oracle,dc=com SADMIN cn=Users,dc=us, dc=oracle,dc=com description Purpose How the Siebel application logs in to the LDAP server. Same. Specifies the LDAP directory the Siebel application will search for users. Which LDAP entity attribute contains the database connection string (the username=GUESTERM password=GUESTERM string you entered earlier). Location of the LDAP server. Which LDAP entity attribute stores the Siebel User ID Which LDAP entity attribute stores the LDAP user ID. In most cases, the Siebel Username Attribute Type and Username Attribute Type are the same.
Server Name
<machine name>
Siebel Username Attribute Type cn Username Attribute Type cn
Note: For a detailed list of the LDAP Security Adapter profile parameters and their purpose, see the Siebel Security Guide on Oracle Technology Network. 6. Configure the Siebel Sales Object Manager to use LDAP authentication: a. In Siebel Call Center, navigate to Administration - Server Configuration > Enterprises > Component Definitions. Setting the parameters at the Enterprise level ensures that any Siebel Server that runs the Siebel Sales Object Manager will use LDAP: b. In the middle applet, query the Component column for Sales*. c. Select the Sales Object Manager (ENU) component definition. d. In the Component Parameters applet, query the Parameter column for Security. Two records should be returned. e. Change the value of Security Adapter Mode to LDAP.
55
f. Change the value of Security Adapter Name to LDAPSecAdpt.
7. Enable the Siebel Sales Object Manager component group: a. In Siebel Call Center, navigate to Administration - Server Configuration > Enterprises > Component Groups. Be very careful not to accidentally navigate to the Parameters view. This would set the LDAP security adapter enterprise-wide, which might have unexpected consequences. If you do this, use the Siebel Developer Web client to reset the parameter. b. In the Component Groups applet, query the Name column for Siebel Sales. c. In the Component Group Assignments applet in the lower right of the screen, click the Enable button. The Enabled on Server? check mark should appear.
d. Log out of Siebel Call Center. 8. Return to the Services window and restart the Siebel Server service. This will take several minutes. Use the Task Manager to monitor its progress. Restarting the Siebel Server service applies all of your configuration changes.
56
9. Log in to Siebel Sales and register a new user: a. In Internet Explorer, enter an address of http://localhost/sales_enu. Note that this is different than in previous practices; you are logging in to a different Siebel application. After a few moments, the Siebel Sales login screen should appear. If it does not, check the server logs in D:\OUses\siebsrvr\log to see whether you can determine the problem. In particular, SSEObgMgr_enu log files will provide information about the Sales object manager. If you cannot determine the problem, contact your instructor. b. Enter:
Last Name First Name User ID Responsibility Position Password Confirm Password
User Install INSUSER Siebel Administrator Siebel Administrator INSUSER INSUSER
f. Step off the record to save it. The Siebel Server automatically communicates this update to the LDAP server. g. Log out of Siebel Sales. h. In the login screen, enter:
User ID Password INSUSER INSUSER
i. Click the arrow to log in to Siebel Sales. The login should succeed. j. Log out of Siebel Sales, and minimize the login screen. 10. Return to Oracle Directory Manager and confirm that INSUSER now appears as an entry in the LDAP directory: a. Return to Oracle Directory Manager. b. If necessary, in the left pane, expand Entry Management, dc=com, dc=oracle, dc=us, and select cn=Users. c. Right-click Users and select Refresh subtree entry. d. Verify that INSUSER now appears as an entry. e. Select INSUSER and confirm that the description includes username=GUESTERM password=GUESTERM. All new entries use the database connection you specified during security adapter configuration. f. Close Oracle Directory Manager.
Siebel 8.1.x Installation 57
c. Click the arrow. d. Navigate to Administration - User > Employees. e. Create a new user with the following parameters. Note that you will need to scroll down in the form applet to enter the user password.
11. To preserve resources, shut down Oracle Directory Manager. Also disable LDAP for the Siebel Sales component group, as you will use the component group using database authentication in a later practice. Also disable the Siebel Sales component group itself. a. Return to the Siebel Sales login screen. You need to log in as SADMIN to perform some of the system administration tasks, such as enabling or disabling component groups. b. In the login screen, enter:
h. i. j. k. l. m. n. o. p.
58
c. d. e. f. g.
Click the arrow button to log in. Navigate to Administration - Server Configuration > Enterprises > Component Definitions. In the middle applet, query the Component column for Sales*. Select the Sales Object Manager (ENU) component definition. In the Component Parameters applet, query the Parameter column for Security. Two records should be returned. Change the value of Security Adapter Mode to DB. Change the value of Security Adapter Name to DBSecAdpt. Navigate to Administration - Server Configuration > Enterprises > Component Groups. In the Component Groups applet, query the Name column for Siebel Sales. In the Component Group Assignments applet in the lower right of the screen, click the Disable button. The Enabled on Server? check mark should disappear. Log out of Siebel Sales and close Internet Explorer. Return to the Services window and stop the OracleOIDProcessManager Windows service. This may take 1-2 minutes. Restart the Siebel Server [OUEnt_OUSrvr] Windows service. This applies your changes. Minimize the Services window.
Lesson 8: Installing the Siebel Management Agent and Server
Practice 8-1 Installing the Siebel Management Agent

Goals Time To install and configure the Siebel Management Agent 15 20 minutes
Instructions:
1. Install the Siebel Management Agent: a. Using Windows Explorer, navigate to D:\Labs\8.1_Install\Installers\Server\Siebel_Management_Agent. b. Double-click setup.exe. c. Click Next in the Welcome screen. d. Specify a directory of D:\OUAgent\mgmtagent and click Next. This copies all of the Siebel Management Agent files to this directory, but performs no configuration. e. Once installation completes, the Siebel Management Agent Configuration Tool starts automatically.
59
In this practice, you will install and configure a Siebel Management Agent to communicate with your Siebel Server. The Siebel Management Agent provides support for ADM, as well as the Siebel Diagnostic Tool. It is installed by default if you select a typical Siebel Server installation. Because you excluded it while performing a custom installation of your Siebel Server in a previous practice, you must install it separately now.
2. Configure the Siebel Management Agent: a. Enter these parameters to configure the Siebel Management Agent, clicking Next to proceed:
Parameter Home Directory of Siebel Server Siebel User Account Siebel User Account Password - and confirm JRE Home Value D:\OUses\siebsrvr SADMIN SADMIN Purpose Used by the Management Agent to locate Siebel Server executables. Used by the Management Agent to connect to the Siebel Server. Used by the Management Agent to connect to the Siebel Server. The Management Agent uses the Java Runtime Environment. The JRE must be installed separately as a prerequisite. This has been done for you on your machine. If you do not find the specified directory, browse for it in your machine; JRE versions may differ. Whether to use RC2 encryption rather than Oracle proprietary encryption to encrypt the Siebel user account password in the Management Agent properties file. Port on which the Management Agent listens for connections. The authentication system used by the Management Agent. It must match that of the Management Server, but does not have to match the Siebel Server it is monitoring. The Siebel User you entered above must be entered in the authentication system used by the Management Agent.
D:\jre_16010
RC2 Password Encryption?
Not selected
RMI Registry Port
1199
Authentication Type Database
Security Adapter Configuration File
D:\OUAgent\mgmtagent\ Which security adapter file to use to obtain connection information to the authentication bin\odbcsecadp.cfg system. The default file name is set according to the authentication type you selected. Recommended practice is to accept this default name. These files are located in the bin subdirectory of the installation directory during installation, and must be edited post-configuration. NoSSL Use SSL for all communication, local communication only (loopback; for example, for communicating with the Siebel Server), or none. The Siebel Management Agent runs as a nonsystem Windows service, hence needs a Windows user who has permission to log on as a service. For example, edpsr56p1\SEBLSRV Corresponding password for the Windows user account. The security adapter must be configured before starting the Management Agent.
SSL Type
Windows User Account
<machine name>\SEBLSRV
Windows User Account Password
SEBLSRV
Start the Not selected Management Agent Now

60
3. Execute the configuration and complete the installation. 4. If necessary, click Next then Finish to exit the After Intallation dialog box. 5. Configure the security adapter for the Siebel Management Agent: a. Use Notepad to open D:\OUAgent\mgmtagent\bin\odbcsecadp.cfg. b. In the [ServerDataSrc] section, change the DSConnectString value to OUEnt_DSN. This is the ODBC connection created by your server for communicating with your database.
c. Save and close odbcsecadp.cfg. 6. Start the Siebel Management Agent and confirm that it is operating successfully. a. Return to the Services window and select Action > Refresh to refresh the list. b. Right-click the Siebel Management Agent (port 1199) service and select Start. c. Use Notepad to open D:\OUAgent\mgmtagent\log\Agent.log. d. Examine the log for the following: i. The first line should read:
SecurityManager is not running. starting up SecurityManager
ii.
iii.
The second line should list SADMINs roles. If there is an error in getting SADMINs roles, ensure that the Siebel Server service is started, and that you correctly spelled the ODBC connection name in odbcsecadp.cfg. The Management Agent must be able to connect to its corresponding Siebel Server. There should be no other errors in the log, and the final few lines should read
refreshing system preferences
If you do not see these lines, try closing the log, not saving any changes, and reopening it to refresh it. e. Close the log, not saving any changes. Leave the Siebel Management Agent service running for the next practice.
61
Practice 8-2 Installing the Siebel Management Server

Goals Time To install and configure the Siebel Management Server 20 25 minutes
Instructions:
1. Install the Siebel Management Server: a. Using Windows Explorer, navigate to D:\Labs\8.1_Install\Installers\Server\Siebel_Management_Server. b. Double-click setup.exe. You would normally run this on the machine that was designated to run the Management Server. c. Click Next in the Welcome screen. d. Specify a directory of D:\OUAgent\mgmtsrvr and click Next. While it is not necessary to co-locate the Management Agent and Server, putting them in the same directory is convenient for this course. e. Once installation completes, the Siebel Management Server Configuration Tool runs automatically. 2. Configure the Siebel Management Server: a. Enter these parameters to configure the Siebel Management Server, clicking Next to proceed through the configuration:
Parameter Siebel Enterprise Siebel Gateway Name Server Host Name Siebel Gateway Name Server Port Siebel User Account Siebel User Account Password - and confirm Diagnostic Tool User Account Diagnostic Tool
62
Value OUEnt <Machine Name>
Purpose Used to monitor a particular Enterprise. Used to contact the Gateway Name Server.
2320 SADMIN SADMIN
Port number on which the Gateway Name Server is listening for connections. Used to obtain information about the Enterprise or particular servers. Used to obtain information about the Enterprise or particular servers. Used to log in to the Diagnostic Tool. This user must also be able to log in to the Siebel application. Used to log in to the Diagnostic Tool.
SADMIN SADMIN
In this practice, you will install and configure the Siebel Management Server. Only one Management Server is required to support all the Management Agents in an enterprise. The Siebel Management Server provides support for ADM and hosts the Siebel Diagnostic Tool.
Password - and confirm RC2 Password Encryption? Not selected Whether to use RC2 encryption rather than Oracle proprietary encryption to encrypt the Siebel user account password in the Management Server properties file. Port on which the Management Server listens for connections. Port used for the Diagnostic Tool; note that the default (8080) is used by both the Diagnostic Tool and the Update Server, so you will need to change this value for the Update Server.
RMI Registry Port Diagnostic Tool HTTP Port
1099 8080
JRE Home
D:\jre_16010
Authentication Type Database
The authentication system used by the Management Server. It must match that of the Management Agent. The Siebel User you entered above must be entered in the authentication system used by the Management Server.
Security Adapter Configuration File
D:\OUAgent\mgmtsrvr\ Which security adapter file to use to obtain connection information to the authentication system. bin\odbcsecadp.cfg The default file name is set according to the authentication type you selected. Recommended practice is to accept this default name. These files are located in the bin subdirectory of the installation directory during installation, and must be edited post-configuration. NoSSL Use SSL for all communication, local communication only (loopback; for example, when communicating with the Siebel Server), or none at all The Siebel Management Server runs as a nonsystem Windows service, hence needs a Windows user who has permission to log on as a service The password used to log in as the Windows user.
SSL Type
Windows User Account Windows User Account Password - and confirm ADM Default Package Directory
<machine name>\SEBLSRV SEBLSRV
D:\OUAgent\mgmtsrvr\ Default location to look for ADM packages; can be changed during deployment. Use the Browse button adm\packages to navigate to this folder and select it. Optionally, specify one or more existing Management Agents for the Management Server to track. The agents must have already been installed, configured, and started. Port on which Management Agent is listening for connections. Name of the Siebel Server the Management Agent
Management Agent <machine name> Host
Management Agent 1199 Port Server Name OUSrvr
63
The Management Server uses the Java Runtime Environment. The JRE must be installed separately as a prerequisite. This has been done for you on your machine. If you do not find the specified directory, browse for it in your machine; JRE versions may differ.
is monitoring. Server Type Siebel Server The Siebel Management Server can listen to Management Agents connected to other types of servers. You can register all of the Agents using the Configuration Tool, or register them later using the Perl scripts provided with the application. The security adapter must be configured before starting the Management Server
Configure Second Agent Start the Management Server Now
Not selected
Not selected
3. Execute the configuration and complete the installation.
5. Configure the security adapter for the Siebel Management Server: a. Use Notepad to open D:\OUAgent\mgmtsrvr\bin\odbcsecadp.cfg. b. In the [ServerDataSrc] section, change the DSConnectString value to OUEnt_DSN. This is the ODBC connection created by your server for communicating with your database. If you were on a machine that did not have this ODBC connection already configured, you would have to configure it manually.
c. Save and close odbcsecadp.cfg. 6. Perform additional configuration for the Siebel Management Server. Three Perl scripts need to be run to generate the XML files necessary to support the Siebel Management Server: getservers.pl connects to the Gateway Name Server and obtains a list of Siebel Servers in the Enterprise to generate configuration.globals.xml. Once that script has been run, makeagentconfig.pl reads the information and generates a list of agents connected to the Management Server and their connection information. Finally, admconfig.pl copies that information to the Management Servers registry to support ADM. Running the Perl scripts requires a Perl parser. ActiveState ActivePerl has been installed on your machine. a. Copy the two files configuration.globals.xml and configuration.agents.xml from D:\OUAgent\mgmtsrvr\pref\system to D:\OUAgent\mgmtsrvr\bin. b. Select Start > Run. c. Enter cmd and click OK to open a command prompt. Course Note: All of the text strings used in this course are contained in text files, allowing
4. If necessary, click Next then Finish to exit the After Intallation dialog box.
you to copy and paste the strings instead of having to type them manually. The strings used for this practice are contained in D:\labs\8.1_Install\Solutions\ManagementAgentAndServer\ managementServer.txt. d. Enter the command:
set PATH=%PATH%;D:\OUses\siebsrvr\bin
This adds the Siebel Server executable directory to the PATH environment variable of the command line. e. Enter the command:
cd D:\OUAgent\mgmtsrvr\bin
d:\perl\bin\perl.exe getservers.pl g <machine name> -u SADMIN p SADMIN l enu e OUEnt
g. h. i. j.
This should successfully generate configuration.globals.xml. Leave the command prompt open. In Windows Explorer, navigate to D:\OUAgent\mgmtsrvr\bin, right-click configuration.globals.xml, and select Open. Note that configuration.globals.xml includes the Enterprise name (OUEnt) and the Gateway Name Server host name (your machine name). Close configuration.globals.xml. Return to the command prompt and enter the command:
D:\perl\bin\perl.exe makeagentconfig.pl OUEnt
k.
l. m. n.
This should successfully generate configuration.agents.xml. Use Notepad++ to open configuration.agents.xml: i. In Windows Explorer, navigate to D:\OUAgent\mgmtsrvr\bin. ii. Right-click configuration.agents.xml and select Open With > Choose Program. iii. Click Browse. iv. Navigate to D:\Program Files\Notepad++ and select Notepad++. v. Click Open. vi. Select the Always use the selected program to open this kind of file checkbox. vii. Click OK. Note that configuration.agents.xml includes the Siebel Server name and connection information for the Siebel Server. Close configuration.agents.xml, not saving any changes. Return to the command prompt and enter the command:
D:\perl\bin\perl.exe admconfig.pl -e OUEnt -s 2321 -p D:\OUAgent\mgmtsrvr\adm\packages -r D:\OUAgent\mgmtsrvr
65
This puts you in the Management Server directory. f. Make sure the Siebel Server service is running, and then enter the command:
7. Return to the Services window and restart the Siebel Management Server service. This loads the configuration information you just copied. 8. Confirm that the Siebel Management Server is operating successfully. a. Use Notepad to open D:\OUAgent\mgmtsrvr\log\ManagementServer.log. b. Examine the log for the following: i. At the top of the log, the security manager should start, and then a section listing SADMINs roles should be shown. If there is an error in getting SADMINs roles, ensure that the Siebel Server service is started, and that you correctly spelled the ODBC connection name in odbcsecadp.cfg. ii. Near the bottom should be a series of messages updated every 30 seconds that state that the Management Server is refreshing system preferences. c. Close the log. 9. Confirm that you can log in to the Siebel Diagnostic Tool using the user you entered during installation: a. Start Internet Explorer. b. Enter an address of http://<machine name>:8080/DiagTool. Because this is a Java application, case is important. c. Enter:
d. If you are asked whether you want Windows to remember your password, click No. e. Click the arrow. f. If your configuration is successful, you should see the screen below. Note that the Server and Component fields are populated. If they are not, review your configuration, as this indicates a problem with communications between the management server, management agent, and
66
This generates deploy_OUEnt.bat, which is used to deploy ADM packages. o. Copy the configuration files to their correct locations: i. Copy configuration.globals.xml from D:\OUAgent\mgmtsrvr\bin back to D:\OUAgent\mgmtsrvr\pref\system, replacing the orginal file. ii. Copy configuration.agents.xml from D:\OUAgent\mgmtsrvr \bin back to D:\OUsea\mgmtsrvr\pref\system, replacing the original file. p. Return to the Services window and start the Siebel Management Server service. This creates the WEB-INF directory that will contain the agent configuration file. Note: If you do not see the Siebel Management Server service listed, select Action > Refresh to refresh the window. q. Copy configuration.agents.xml from D:\OUAgent\mgmtsrvr\bin to D:\OUAgent\mgmtsrvr\tomcat\webapps\DiagTool\WEB-INF
Siebel Server:
g. h. i. j. k.
Click the Event Log Analysis tab. Enter OUSrvr as the server. If you are asked whether or not to turn AutoComplete on, click No. Click Submit. Note that you can review server event logs from the Diagnostic Tool. Log out of the Diagnostic Tool. Because you have not configured SARM on your Siebel Server, you cannot perform Server or User analysis.
10. Stop the Siebel Management Server service. 11. Stop the Siebel Management Agent service.
67
68
Lesson 9: Silent Installation
Practice 9-1 Performing a Silent Installation

Goals Time To Configure and Perform a Silent Installation 25 30 minutes
Instructions:
1. Run the Siebel Enterprise Server installer to generate an installation response. To do this, you must run the installer from the command line with the RECORD flag set: a. If necessary, open a command prompt. i. Select Start > Run. ii. Enter cmd and click OK. b. Change directories to the Siebel Enterprise Server installer directory. i. Enter the command
cd D:\labs\8.1_Install\Installers\Server\Siebel_Enterprise_Server
This changes your current directory to the Siebel Enterprise Server installer directory. Course Note: All of the text strings used in this course are contained in text files, allowing you to copy and paste the strings instead of having to type them manually. The strings used for this practice are contained in D:\labs\8.1_Install\Solutions\SilentInstall\ silentStrings.txt. c. Launch the Siebel Enterprise Server installer in record mode: i. Enter the command
setup.exe -args RECORD=D:\Temp\silentSiebel.ini
Spacing is important. Do not forget the equals sign. This launches the setup program in record mode, and records the results in a file named silentSiebel.ini. Recall that siebel.ini is the default name. Giving it a different name makes it easier to recognize. Once the setup program launches, note that it looks identical to the setup program you ran in a previous practice.
69
In this practice, you will configure and perform a silent installation of a Siebel Server.
ii.
Enter the parameters below, clicking Next to proceed:

Parameter Directory Name Value D:\OUSilent Purpose Where the silent installer will install the files when it runs. Note that this is only a configuration setting at the moment; no files will be placed in the directory until after you run the silent installer in the next practice. Which products to install. Whether to accept the default installation values or to customize them.
Products to Install Setup Type Features
Siebel Server Custom
Languages to install enu - English (American) Program Folder
Which languages to install on the server.
Siebel Enterprise Where to put the programs in the Windows Start menu. Server Configuration 8.1
d. e.
f. g. h.
Note: Although running the installer in record mode prevents it from performing an installation, it still performs the same consistency checks as the normal installer; in particular, you cannot install into a directory containing an existing installation. iii. Verify that once configuration is complete, you are notified that the silent response file has successfully been created. iv. If necessary, click Next then Finish to exit the After Intallation dialog box. Use Notepad to open D:\Temp\silentSiebel.ini. Scroll down so that both the [Defaults.Windows] and [Defaults.ProductSelection] sections are visible and confirm that your installation directory and product selection options are recorded in the file. In particular, note that the [Defaults.ProductSelection] section contains only the Siebel Server, not the Gateway Name Server or Database Configuration Utility. Minimize silentSiebel.ini. Verify that the folder D:\OUSilent is empty. This confirms that the installer did not perform the installation. Minimize the command window.
2. Run the Siebel Server Configuration Tool in offline mode to generate the configuration response file (siebel_server_sia.xml by default). a. Select Start > Programs > Siebel Enterprise Server Configuration 8.1 > Siebel Server Configuration.
70
Which features of the Siebel Server to install. - Siebel Server - Object Manager Component
b. Enter the parameters:

Parameter Mode Action Database Configuration Information Value Purpose Configure Product for Generate an XML response file instead of performing configuration. Offline Deployment Create New Configuration Next Create a new Siebel Server configuration. A warning to ensure your database is properly configured before configuring the server. Used to connect to the Gateway Name Server to obtain Enterprise configuration parameters. Used to connect to the Gateway Name Server to obtain Enterprise configuration parameters.
Gateway Name SADMIN Server Authentication User Account Name Gateway Name SADMIN Server Authentication User Account Password - and confirm Gateway Name Server Host Name Gateway Name Server TCP/IP Port Siebel Enterprise Name Siebel Server Name <machine name> 2320 OUEnt <machine name>
Used to contact the Gateway Name Server. Port on which the Gateway Name Server is listening for connections. Which Enterprise the Siebel Server will be a part of. String used to identify the Siebel Server; must be unique within the Enterprise. Recall that you named your first server OUSrvr, so accepting the default value of <machine name> provides a unique name. String describing the Siebel Server. Which component groups to initially enable on the Siebel Server. Port on which the Siebel Server listens for connections; the default of 2321 would work here for most machines, but because you will be performing the installation on a machine with an existing installation, it cannot match the port number of the existing Siebel Server. Port on which the Siebel Server listens for synchronization requests. Once again, the default of 40400 would work on any machine except one with an existing Siebel Server. Used to configure additional security or Exchange server integration on the Siebel Server. Create an ODBC connection to the Oracle database. This already exists because of the existing Siebel Server. Cluster Siebel Servers to provide high availability for the Enterprise.
71
Siebel Server Description Enable Component Groups Siebel Connection Broker Port
Siebel Server Profile <machine name> Sales 2322
Network TCP/IP Port for Synchronization Manager Additional Tasks Register Oracle ODBC Driver Clustering Configuration
40401
None Not selected
Not clustered
Set the Siebel Server Not selected system service to start automatically Start the Siebel Not selected Server system service at the end of profile execution Final Tasks Summary View Next Next
Whether to start the Siebel Server when the system boots. Whether to start the Siebel Server once configuration is complete.
Do not perform any custom tasks Review and accept the summary information.
3. Edit your silentSiebel.ini file to invoke the configuration response file you just created: a. Return to silentSiebel.ini. If you closed it, it is in D:\Temp. b. Scroll down to the [RunAfter.Windows] section. c. Change the ConfigServer.Windows parameter to yes:
d. Scroll down to the [ConfigServer.Windows] section. Be sure to edit the correct section. e. Change the Execute parameter to
$(SiebelRoot)\siebsrvr\bin\ssincfgw.exe
f. Change the Arg parameter to

-args MODE=EXECUTE REPEAT=FALSE IN_RESPONSE_FILE=D:\Temp\silent_server.xml
This is the configuration response file you just generated.
g. Save and close silentSiebel.ini.
72
c. d. e. f.
Browse to D:\Temp and save the response file as D:\Temp\silent_server.xml. Using Windows Explorer, navigate to D:\Temp. Double-click silent_server.xml. Verify that it contains your responses to the Configuration Tool; in particular, check for a connection broker port (SBCPort) of 2322 and a synchronization port (LocalSynchMgrPort) of 40401. These are non-default values, so finding them proves that your responses were recorded in this file. g. Close silent_server.xml, not saving any changes.
4. Invoke the silent installer to confirm that your settings successfully install and configure a Siebel Server. You would normally do this on a clean machine; that is, one not already containing a Siebel Server. You would copy over the installer directory and the configuration files, then invoke the installer from the command line. Since the installer directory and configuration files are already on this machine, no copying is necessary. a. Return to the command prompt. b. Enter the following command (with no line feed):
setup.exe -is:javaconsole -console args SS_SETUP_INI=D:\Temp\silentSiebel.ini
5. Verify the installation: a. In the Services window, select Action > Refresh to refresh the list. b. Verify that the Siebel_Server[OUEnt_<machine name>] service exists. c. Right-click the service and select Start. d. Once the service has completely started, start the Siebel Call Center Web client: i. Select Start > Programs > Internet Explorer ii. Enter Address: http://localhost/callcenter_enu. iii. Enter:
iv.
Click the arrow.
73
c. Verify that the console installer runs. It should show several windows, and run for several minutes, showing progress the entire time.
e. Navigate to Administration - Server Management > Servers and confirm that both servers appear as running.
6. Remove the Siebel Server you just created. This will help avoid confusion in later practice where you add multiple Siebel Servers to a single Enterprise. a. Select Start > Programs > Siebel Enterprise Server Configuration 8.1 > Siebel Server Configuration to invoke the Siebel Server Configuration Tool. b. Select Configure Product in Live Mode and click Next. c. Select Remove Existing Configuration and click Next. d. Enter the parameters to remove the extra Siebel Server, clicking Next to proceed:
Parameter Gateway Name Server Authentication User Account Name Gateway Name Server Authentication User Account Password - and confirm Gateway Name Server Host Name Gateway Name Server TCP/IP Port Value SADMIN Purpose Used to log in to the Gateway Name Server to collect Siebel Server information, and later to remove the Server information from the Gateway Name Server. Used to log in to the Gateway Name Server.
SADMIN
<Machine Name> 2320
Used to connect to the Gateway Name Server. Port on which the Gateway Name Server is listening for connections. Enterprise containing the Server to be removed. The Siebel Server to remove. Be careful to remove the Siebel Server with this name, rather than OUSrvr. Remove the configuration from the Gateway Name Server. Remove the Windows service that implements
Siebel Enterprise Name OUEnt Siebel Server Name <Machine Name>
Remove Siebel Server Configuration Remove Siebel Server
Selected Selected
74
f. Select <machine name> and click Shut Down. This confirms that you can manage the second Siebel Server, and also preserves system resources. Note: With additional time, you could test the server by editing the [/sales_enu] section of eapps.cfg to point to the second server, then log in. This duplicates work you will be performing in a later practice, hence it is not done here. g. Log out of Siebel Call Center and close Internet Explorer. h. Stop the Siebel Server [OUEnt_<machine name>] Windows service. You must stop it before removing it.
Windows Service Remove Siebel Server ODBC Data Source Not selected
the Siebel Server. Do not remove the ODBC Data Source until you have removed all Siebel Servers from this machine, or you will not be able to re-run the Server Configuration Tool because the connection to the Gateway Name Server will be lost. Confirm that you wish to remove the Siebel Server.
Remove Selected Siebel Server
Selected
75
e. f. g. h.
Complete the configuration. If necessary, click Next then Finish to exit the After Intallation dialog box. Return to the Services window and select Action > Refresh. Confirm that the Siebel Server [OUEnt_<machine name>] Windows service has been removed. Note: If it has not been removed, the likely cause is that the configuration tool was run before the service stopped completely. Re-run the configuration tool with the same parameters, and the service should be removed successfully.
76
Lesson 10: Installing Siebel Tools
Practice 10-1 Installing Siebel Tools

Goals Time To install and configure Siebel Tools 15 20 minutes
Instructions:
1. Install Siebel Tools: a. Using Windows Explorer, navigate to D:\Labs\8.1_Install\Installers\Client\Siebel_Tools\Disk1\install. b. Double-click oui.exe. c. Enter the installation parameters, clicking Next to proceed:
Parameter Product to Install Name Path Language Siebel Database Server Database Alias Value Purpose Siebel Business Application Install Siebel Tools. Tools 8.1.1.0.0 Development Siebel_Tools D:\OUTools English Oracle Database Server SIEBELDB Program Folder name. Installation path. Language(s) to install. Database platform of the enterprise database. Connection information for contacting the database; must be configured by DBA on each machine that will run Siebel Tools. Used to read database schema. Used to read data from the enterprises Siebel File System. See the note below with regards to using an absolute file path. Used for synchronization with a Siebel Server, if desired. See the note below with regards to using localhost. Used to connect to the Gateway Name Server. See the note below with regards to using localhost. Used to collect Enterprise configuration information.
Table Owner File System Server
SIEBEL D:\siebfile
Siebel Remote Server Hostname Gateway Name Server Address Enterprise Server Name
localhost
localhost
OUEnt
77
In this practice, you will install Siebel Tools, and confirm that you can connect to the Enterprise database. You will then modify the configuration file to allow you to connect to the local Sample database.
Note: You would normally use machine names rather than localhost on these machines, as well as a network file path. In the classroom environment, your machine name has been added to the Trusted Sites list, which hides some of the client behavior you would see in a production environment. By using localhost rather than machine name, you see this behavior. d. Once installation completes, click Exit and then click Yes. e. If necessary, in the Finish Admin Install dialog box click Next and then click Finish to dismiss it. 2. Test Siebel Tools connection to the Siebel Enterprise Server database: a. Select Start > Programs > Siebel_Tools 8.1 > Siebel Tools. b. Click Agree to Terms. c. Enter:
User ID Password Connect To SADMIN SADMIN Server
d. Click OK. The application should load in 20-30 seconds. e. Select Applet in the left pane. Observe the list of Applet object definitions in the right pane. A developer could lock one of these applets, customize it, and compile it to the server. However, working against the server database is not recommended. Developers should work against a local database and test their changes first. f. Select File > Exit to exit Siebel Tools. 3. Test Siebel Tools connection to the local Sample database: a. Select Start > Programs > Siebel_Tools 8.1 > Siebel Tools. b. Enter:
c. Click OK. A dialog box appears telling you that the local database was not found. This is because the Siebel Tools configuration file has not been configured to connect to the Sample database. The Sample database was installed in the Developer Web Client directory rather than the Siebel Tools directory, hence you must edit tools.cfg. d. Click No to dismiss the dialog box. e. Create a backup copy of D:\OUTools\bin\enu\tools.cfg and name it originaltools.cfg. f. Use Notepad to open tools.cfg. g. Locate the [Sample] section. h. Change the ConnectString parameter to:
D:\OUClient\sample\UTF8\sse_samp.dbf -q -m -x NONE -gp 4096 -c40m -ch60m
This should only involve replacing the word Tools with the word Client. Course Note: All of the text strings used in this course are contained in text files, allowing
78
you to copy and paste the strings instead of having to type them manually. The strings used for this practice are contained in D:\labs\8.1_Install\Solutions\Tools\toolsStrings.txt. i. Save and close tools.cfg. j. Re-test the connection: i. Select Start > Programs > Siebel_Tools 8.1 > Siebel Tools. ii. Enter:
79
iii. Click OK. You should successfully connect to the Sample database. k. Select Applet in the left pane and confirm that you see a list of applet object definitions in the right pane. l. Select File > Exit to close Siebel Tools.
80
Lesson 11: Configuring Multiple Servers within an Enterprise
Practice 11-1 Configuring Multiple Servers

Goals Time To combine servers from at least two different machines into an enterprise 30 40 minutes
Instructions:
Note: It is possible to perform these practices on a single, powerful machine, with at least 3 GB of RAM. However, when configuring OUSrvr2 you will need to change the Siebel Connection Broker Port to 2322, and use that throughout the configuration. The practice is written for groups with multiple machines. In this first practice, you will configure at least one additional Siebel Server in your enterprise, and enable the Workflow component group on all of the servers. By invoking multiple batch jobs in the enterprise, you can see how default load balancing and distribution occurs within the enterprise when Application Object Managers (AOMs) are not involved. Note that because you are working in a team on multiple machines, some of these steps may be performed in parallel. To indicate which machine you should be working on, the steps in this practice are labeled: Siebel Gateway Name Server (GNS) steps are steps to be performed on the Siebel Gateway Name Server machine. Siebel Server (SS) steps are steps to be performed on each Siebel Server machine. Steps on different machines may be performed in parallel unless otherwise indicated. Practice Note: Although you correctly configured your Siebel Enterprise to use a network file path for the Siebel file system, Windows security policies will prevent the second Siebel Server (running as a local system service) from mounting the networked directory. This does not affect the practice as written; you might notice that your SADMIN preferences file is not being read by the second server. If you wish to try to resolve this, consider running the second server as a user rather than as a local system service. For example, after configuring the second Siebel Server but before starting it for the first time, right-click the Siebel Server [OUEnt_<machine name>] service and select Properties, click the Log On tab, select the This account radio button, and enter SEBLSRV as both the account and the password, then click OK. Then start the service and see whether the preferences files are read. (This is easily recognized by whether the Administration - Server Configuration tab is
81
Practice Note: The following practices are intended to be performed on at least two machines. Team up with at least one partner to combine your machines into a single enterprise. Over the next few practices, you will first add a second Siebel Server to your enterprise, but it will not be running an Application Object Manager (AOM), hence it requires no additional configuration. You will then enable Siebel Sales on that server, which is a different AOM from the one (Siebel Call Center) on your original server. This requires editing eapps.cfg. You will finally enable Siebel Call Center on both servers. This requires enabling load balancing.
visible after logging in to Siebel Call Center multiple times in practice 11-3). If you encounter issues, restore the service to run as a local system service. 1. Select one machine to support the Siebel Gateway Name Server for the enterprise. Since you have already installed a complete enterprise on this machine, any additional machines will only require Siebel Servers.
Component Siebel Gateway Name Server Siebel Server 1 Siebel Server 2 Siebel Server 3 Machine Name IP Address
2.
SIEBEL GATEWAY NAME SERVER (GNS): Verify that OUSrvr is the only server left in your enterprise. Otherwise, load balancing may not work correctly when you add the additional server. a. If necessary, start the Siebel Server [OUEnt_OUSrvr] Windows service. b. Once the service has started completely, start the Siebel Call Center Web client: i. Select Start > Programs > Internet Explorer ii. Enter Address: http://localhost/callcenter_enu. iii. Enter:
iv. Click the arrow. c. Navigate to Administration - Server Configuration > Servers and confirm that OUSrvr is the only server left in the Enterprise. If it is not, refer to the next major step (for the Siebel Server machine) for instructions on how to remove a Siebel Server. d. Log out of Siebel Call Center. 3. SIEBEL SERVER MACHINE(S) (SS): Remove the existing Siebel Servers. Recommended practice is to have only one server using a given server directory (for example, D:\OUses\siebsrvr), hence you should remove OUSrvr before creating your new server. You must also avoid port conflicts (for example, port 2321, the Siebel Connection Broker port). Finally, you cannot have two identically-named Siebel Servers in the same enterprise. The easiest way to avoid these conflicts is to remove all of the servers from this machine before proceeding. a. If necessary, start the Siebel Gateway Name Server service. b. Stop the Siebel Server [OUEnt_OUSrvr] service. c. Select Start > Programs > Siebel Enterprise Server Configuration 8.1 > Siebel Server Configuration to invoke the Siebel Server Configuration Tool. d. Select Configure Product in Live Mode and click Next. e. Select Remove Existing Configuration and click Next.
82
Siebel Server 4
f. Enter these parameters to remove the extra Siebel Server, clicking Next to proceed:
Parameter Gateway Name Server Authentication User Account Name Gateway Name Server Authentication User Account Password - and confirm Gateway Name Server Host Name Value SADMIN Purpose Used to log in to the gateway name server to collect Siebel Server information, and later to remove the server information from the gateway name server. Used to log in to the gateway name server.
SADMIN
<machine name>
Gateway Name Server TCP/IP Port Siebel Server Name Remove Siebel Server Configuration Remove Siebel Server Windows Service Remove Siebel Server ODBC Data Source
2320
Port on which the gateway name server is listening for connections. Enterprise containing the server to be removed. The Siebel Server to remove. Remove the configuration from the gateway name server. Remove the Windows service that implements the Siebel Server. Do not remove the ODBC Data Source until you have removed all Siebel Servers from this machine, or you will not be able to re-run the Server Configuration Tool because the connection to the Siebel Gateway Name Server will be lost. Confirm that you wish to remove the Siebel Server.
Siebel Enterprise Name OUEnt OUSrvr Selected Selected Not selected
Selected
g. If necessary, repeat these steps to remove the Siebel Server named <machine name> as well. h. As a verification step, bring up the Services window and select Action > Refresh. There should be no Siebel Server services on your Siebel Server machine. 4. SIEBEL SERVER MACHINE(S) (SS): Edit tnsnames.ora to point to the correct database. Note that your current ODBC connection points to your local database; you need to modify that connection so that it points to the database on the Siebel Gateway Name Server machine. a. Using Windows Explorer, navigate to D:\OID\NETWORK\ADMIN. b. Right-click tnsnames.ora and select Send To > Notepad. c. In the SIEBELDB section, change the HOST to <GNS machine name>. d. Save and close tnsnames.ora. e. Test the connection. i. Select Start > Run. ii. Enter cmd and click OK. iii. Enter the command
83
Used to connect to the gateway name server. Use the Siebel Server machine name, as you are removing the existing server connected to the local gateway name server.
tnsping siebeldb
and confirm that it returns OK. Course Note: All of the text strings used in this course are contained in text files, allowing you to copy and paste the strings instead of having to type them manually. The strings used for this practice are contained in D:\labs\8.1_Install\Solutions\MultiServer\multiserverStrings.txt. Close the command prompt.
iv.
Parameter Gateway Name Server Authentication User Account Name Gateway Name Server Authentication User Account Password - and confirm Gateway Name Server Host Name Gateway Name Server TCP/IP Port Siebel Server Name
Value SADMIN
Purpose Used to log in to the gateway name server to obtain configuration parameters. Used to log in to the gateway name server.
SADMIN
<GNS machine name> 2320
Used to connect to the gateway name server. Recall that this is the other persons machine. Port on which the gateway name server listens for connections. Used to connect to the Siebel Enterprise. A string of up to 12 characters including letters, numbers, and underscores that uniquely identify the Siebel Server. A description displayed in several of the administrative views. Which component groups should be enabled on the Siebel Server when it first starts. Port on which the Siebel Server listens for connections. Port used by Siebel Remote for synchronization.
Siebel Enterprise Name OUEnt OUSrvr2
Siebel Server OUSrvr2 Sales 2321
Network TCP/IP Port for 40400 Synchronization Manager
84
5. SIEBEL SERVER MACHINE(S) (SS):: Configure a Siebel Server to communicate with the GNS machine: a. Select Start > Programs > Siebel Enterprise Server Configuration 8.1 > Siebel Server Configuration to invoke the Siebel Server Configuration Tool. b. Select Configure Product in Live Mode and click Next. c. Select Create New Configuration and click Next. d. Click Next. e. Enter the parameters below to create a new Siebel Server. Note that you are naming this server OUSrvr2, as the name must be distinct from the existing Siebel Servers in the enterprise. Be careful to use the OTHER machines name, rather than your machines, for the GNS host name.
Additional Tasks
None
Configure SSL, LDAP, or Exchange synchronization. Used by the Siebel Connector for Oracle Applications to connect to back office Oracle databases. Cluster Siebel Servers to provide redundancy in case of server failure. For most deployments, the Siebel Server should start up when the system boots. To preserve system resources, do not do this on the classroom machine. Whether or not to start the Siebel Server service as soon as the profile execution completes.
Register External Oracle Checked DB ODBC Driver Clustering Configuration Not clustered Start Siebel Server service automatically? Unchecked
f. Return to the Services window and select Action > Refresh. g. Start the Siebel Server [OUEnt_OUSrvr2] Windows service. h. Minimize the Services window. 6. ANY MACHINE; can be performed in parallel on multiple machines: Confirm that both Siebel Servers are visible in the enterprise, and that load balancing is automatically performed between the two servers. a. In Internet Explorer, enter an address of http://<GNS Machine Name>/callcenter_enu. b. Enter:
c. Click the arrow. d. Perform a synchronization to ensure that both servers components are available. i. Navigate to Administration - Server Configuration > Enterprises > Synchronize. ii. Click the Synchronize button in the middle of the view. The process should take 1-2 minutes. e. Navigate to Administration - Server Management > Servers and confirm that both OUSrvr and OUSrvr2 are listed. f. Click the Component Groups view tab.
85
Start Siebel Server service at the end of profile execution?
Unchecked
g. For each Siebel Server, confirm that the Server State is Running and that the System Management component group is online for that server.
h. Click the Jobs view link. You will be running several Siebel Administrator Notification Component jobs to confirm that the jobs are distributed between the two Servers, both of which are running. i. Create a new Siebel Administrator Notification Component job: i. Click New. ii. Click the Select button in the Component/Job field. iii. Query for a short name starting with AdminNotify, select it, and click OK. iv. Scroll down to the Job Parameters applet and click New. v. Click the Select button in the Name field. vi. Select the Notification Handler job parameter and click OK. vii. Enter AdminEmailAlert as the value for this parameter. viii. Step off the record to save it. ix. Note that the record status is Creating. j. Create four additional Siebel Administrator Notification Component jobs to create five total jobs. By default, the first four jobs will be sent to the first server, then the next four will be sent to the second server, and so forth. This configurable parameter assumes that it is more efficient for a single server to run multiple instances of the same job than it is to perform total round-robin distribution, where one job at a time is sent to each server: i. Select the Siebel Administrator Notification Component job you just created. ii. Select Menu > Copy Record from the applet-level menu. iii. Repeat this step to create three more jobs, for five jobs in total. k. Perform the following steps as quickly as possible: i. Scroll up and click Submit Job. ii. Select the next job with a status of Creating and click Submit job. iii. Repeat until all 5 jobs have been submitted. l. Click Query and then click Go to refresh the jobs list. m. Examine the Execution Server column of the jobs. You should notice that the jobs got distributed betweeen the two servers without any additional configuration on your part.
7. Remain logged in to Siebel Call Center. In the next practice you will configure the Siebel Servers to support two different Application Object Managers.
87
Practice 11-2 Configuring Multiple Different Application Object Managers (AOMs)

Goals To configure the Siebel Enterprise to support both Siebel Sales and Siebel Call Center when those applications are enabled on different servers 15 20 minutes
Time
In this practice you will examine how the Siebel Web Server Extension (SWSE) determines where to send client requests. You will then configure the SWSE to send Call Center requests to one server, and Sales requests to a second server. 1. On any machine, in Siebel Call Center, confirm that OUSrvr2 supports the Siebel Sales AOM. a. If necessary, log in to Siebel Call Center as SADMIN/SADMIN. b. If necessary, navigate to Administration - Server Management > Jobs. This is where you ended the last practice. c. Click the Servers view link. d. Select the Component Groups view tab. e. Select OUSrvr2 in the Servers applet and confirm that the Siebel Sales component group is online on that Server. f. Log out of Siebel Call Center. When you restart the Web server later in this practice, it will automatically terminate any active sessions. 2. Try to log in to Siebel Sales. a. In Internet Explorer, enter an address of http://<GNS Machine Name>/sales_enu. Recall that the Web server is co-located with your Gateway Name Server, so you may not use the Siebel Server machine name. b. What error message do you receive? Why do you think this is happening?
3. Edit eapps.cfg on the gateway name server machine to route Siebel Sales requests to OUSrvr2: a. Create a backup copy of D:\OUWebServer\SWEApp\bin\eapps.cfg, naming it originaleapps.cfg. b. Use Notepad to open eapps.cfg. c. Locate the section labeled [/sales_enu].
Instructions:
d. Change the connect string in this section by replacing the GNS machine name with the SS machine name; for example, assume that edpsr14p1 is the GNS machine name and edpsr15p1 is the name of the Siebel Server machine that is hosting the Siebel Sales AOM. Replace:
ConnectString = siebel.TCPIP.None.None://edpsr14p1:2321/OUEnt/SSEObjMgr_enu
with
ConnectString = siebel.TCPIP.None.None://edpsr15p1:2321/OUEnt/SSEObjMgr_enu
4. On either machine, confirm that sessions of Siebel Call Center and Siebel Sales now run on different Servers. a. In an instance of Internet Explorer, enter an address of http://<GNS machine name>/callcenter_enu. b. Enter:
c. Click the arrow. You should successfully log in to Siebel Call Center. d. In a second instance of Internet Explorer, enter an address of http://<GNS machine name>/sales_enu. e. Enter:
f. Click the arrow. You should successfully log in to Siebel Sales. g. In either application, navigate to Administration - Server Management > Sessions. h. Select Menu > Columns Displayed in the applet-level menu.
89
e. f. g. h.
Save and close eapps.cfg. Return to the Services window. Right-click the IIS Admin Service and select Restart. Click Confirm to also restart its dependent services. This restarts the Web server and re-reads the eapps.cfg file.
i. Add the Siebel Server column and move it so that it appears immediately after the Component column:
j. Click Save to dismiss the Columns Displayed dialog box. k. Query for a component of SCCObjMgr_enu and confirm that a session is running for it on the gateway name server machine. l. Query for a component of SSEObjMgr_enu and confirm that a session is running for it on the Siebel Server machine. This shows that editing eapps.cfg is all that is necessary to distribute requests among different AOMs. m. Log out of Siebel Sales and close that instance of Internet Explorer. n. Remain logged in to Siebel Call Center.
90
Solutions 11-2 Configuring Multiple Different Application Object Managers (AOMs)

Answers
2.b. What error message do you receive? Why do you think this is happening? The server you are trying to access is either busy or experiencing difficulties. Please close the Web browser, open a new browser window, and try logging in again.[<timestamp>]. Although the Siebel Sales component group is enabled on one of the Siebel Servers, the Siebel Web Server Extension (SWSE) was configured for a single Siebel Server. It is still forwarding all of its requests to OUSrvr, even though that Server does not have Siebel Sales enabled.
91
Practice 11-3 Using Native SWSE Load Balancing

Goals Time To enable SWSE load balancing for your enterprise 25 30 minutes
Instructions:
1. Enable the Siebel Call Center component group on the Siebel Server machine: a. On any machine, in Siebel Call Center, navigate to Administration - Server Configuration > Enterprises > Component Groups. b. Query for the Siebel Call Center component group. c. Enable the Siebel Call Center component group on OUSrvr2. d. Restart the Siebel Server [OUEnt_OUSrvr2] service on the Siebel Server machine. Wait for the service to fully start before proceeding. 2. Generate the load balancing configuration file, lbconfig.txt. This file will contain load balancing information that will be used by the SWSE to distribute session requests among the Siebel Servers. a. On the GNS machine, open a command prompt and navigate to the D:\OUses\siebsrvr\bin directory. Note that you can perform this step on any machine, but performing it on the machine hosting the Gateway Name Server allows you avoid having to copy the file between two machines. i. Select Start > Run. ii. Enter cmd and press OK. iii. Enter the command
cd D:\OUses\siebsrvr\bin
b. Start the command-line server manger by entering the command:

srvrmgr.exe -g <GNS machine name> -e OUEnt -u SADMIN -p SADMIN
This connects to the Gateway Name Server and Enterprise as SADMIN/SADMIN, but does not connect to any server in particular.
92
In this practice, you will enable the Siebel Call Center AOM on both server machines, and then modify the SWSE configuration to support distributing the load between the two servers. The builtin load balancing is quite simple: The first session request goes to the first server, the second goes to the second, and so forth.
c. At the srvrmgr> prompt, enter the command

generate lbconfig
This reads the configuration information from each Siebel Server and creates a file named lbconfig.txt in the ADMIN subdirectory of the Siebel Server directory. d. Enter exit to exit the server manager. e. Use Notepad to open D:\OUses\siebsrvr\admin\lbconfig.txt and examine the contents. Confirm that both the Gateway Name Server and Siebel Server machine names are listed under VirtualServer. Recall that the first Siebel Server is co-located with the Gateway Name Server. f. Close lbconfig.txt, not saving any changes. 3. Copy lbconfig.txt to the existing SWSE logical profile. None of the logical profile settings depend on load balancing: a. On the Gateway Name Server machine, copy lbconfig.txt from D:\OUses\siebsrvr\admin to D:\OUses\gtwysrvr\admin\Webserver. 4. Reapply the SWSE logical profile: a. On the Gateway Name Server machine, select Start > Programs > Siebel Enterprise Server Configuration 8.1 > Siebel Web Server Extension Configuration. b. Select Configure Product in Live Mode and click Next. c. Select Apply an SWSE Logical Profile and click Next. d. Select Siebel Native Load Balancing and click Next. e. Browse for the logical profile at D:\OUses\gtwysrvr\admin\Webserver and click Open. f. Click Next. Confirm the next few dialog boxes. g. The profile should apply successfully. h. Cancel out of the configuration tool. 5. Edit eapps.cfg to ensure it is using lbconfig.txt: a. Use Notepad to open D:\OUWebServer\SWEApp\bin\eapps.cfg. b. Under the [ConnMgmt] section, edit the VirtualHostsFile parameter to set it to D:\OUWebServer\SWEApp\admin\lbconfig.txt. This should involve changing the .cfg suffix to .txt. c. Save and close eapps.cfg. 6. Restart the IIS Admin Service Windows service, as well as its dependent services. This restarts the Web server and re-reads the configuration files. 7. Verify that load balancing is occurring in the Enterprise: a. In an instance of Internet Explorer, enter an address of http://<GNS machine name>/callcenter_enu and log in as SADMIN/SADMIN. b. Create at least three more sessions by logging in from other machines, or in additional instances of Internet Explorer on the same machine. c. In one of the instances, navigate to Administration - Server Management > Sessions.
Siebel 8.1.x Installation 93
d. Query for a component of SCCObjMgr_enu. Confirm that multiple sessions of Call Center are running on different machines, evenly distributed between the two machines. This shows that Siebel native load balancing is working. Note: It may be necessary to re-expose the Siebel Server column to see how the sessions are distributed. 8. Verify that you can still log on to an AOM that is enabled on only one server: a. In an instance of Internet Explorer, enter an address of http://<GNS machine name>/sales_enu and log in as SADMIN/SADMIN. b. The fact that you were able to log in even though the Siebel Sales component group is enabled on only one of the Siebel Servers shows that load balancing properly handles different AOMs enabled on different Siebel Servers. 9. Log out of all applications and close all instances of Internet Explorer. Restore your configurations for the next practice: 10. SIEBEL GATEWAY NAME SERVER (GNS): Re-apply the SWSE logical profile to eliminate load balancing: a. On the Gateway Name Server machine, select Start > Programs > Siebel Enterprise Server Configuration 8.1 > Siebel Web Server Extension Configuration. b. Select Configure Product in Live Mode and click Next. c. Select Apply an SWSE Logical Profile and click Next. d. Select Single Siebel Server and click Next. e. Enter your machine name and click Next. f. Accept the default port number and click Next. g. Browse for the logical profile at D:\OUses\gtwysrvr\admin\Webserver and click Open. h. Complete the configuration. i. The profile should apply successfully. j. Cancel out of the configuration tool. k. Confirm that you can log in to Siebel Call Center as SADMIN/SADMIN. Recall that the URL is http://localhost/callcenter_enu. 11. SIEBEL SERVER: Remove OUSrvr2: a. Stop the Siebel Server [OUEnt_OUSrvr2] service. Wait until it is fully stopped before proceeding. b. Select Start > Programs > Siebel Enterprise Server Configuration 8.1 > Siebel Server Configuration to invoke the Siebel Server Configuration Tool. c. Select Configure Product in Live Mode and click Next. d. Select Remove Existing Configuration and click Next. e. Enter these parameters to remove the extra Siebel Server:
Parameter Gateway Name Server Authentication User Account Name Value SADMIN Purpose Used to log in to the gateway name server to collect Siebel Server information, and later to remove the server information from the gateway name server.
94
Gateway Name Server Authentication User Account Password - and confirm Gateway Name Server Host Name Gateway Name Server TCP/IP Port Siebel Server Name Remove Siebel Server Configuration Remove Siebel Server Windows Service Remove Siebel Server ODBC Data Source
SADMIN
Used to log in to the gateway name server.
<GNS machine name> 2320
Used to connect to the gateway name server. Port on which the gateway name server is listening for connections. Enterprise containing the server to be removed. The Siebel Server to remove. Remove the configuration from the gateway name server. Remove the Windows service that implements the Siebel Server. Do not remove the ODBC Data Source until you have removed all Siebel Servers from this machine, or you will not be able to re-run the Server Configuration Tool because the connection to the Siebel Gateway Name Server will be lost. Confirm that you wish to remove the Siebel Server.
Siebel Enterprise Name OUEnt OUSrvr2 Selected Selected Not selected
Selected
12. SIEBEL SERVER: Edit tnsnames.ora to point to your local database: a. Using Windows Explorer, navigate to D:\oracle\product\10.2.0\db_1\NETWORK\ADMIN. b. Right-click tnsnames.ora and select Send To > Notepad. c. In the SIEBELDB section, change the HOST to <your machine name>. d. Save and close tnsnames.ora. e. Test the connection. i. Select Start > Run. ii. Enter cmd and click OK. iii. Enter the command
tnsping siebeldb
and confirm that it returns OK. f. Close the command prompt. 13. SIEBEL SERVER: Re-install OUSrvr: a. Verify that the Siebel Gateway Name Server service is running. b. Select Start > Programs > Siebel Enterprise Server Configuration 8.1 > Siebel Server Configuration to invoke the Siebel Server Configuration Tool. c. Select Configure Product in Live Mode and click Next. d. Select Create New Configuration and click Next.
95
e. Enter the parameters below to create a new Siebel Server.

Parameter Gateway Name Server Authentication User Account Name Gateway Name Server Authentication User Account Password - and confirm Gateway Name Server Host Name Gateway Name Server TCP/IP Port Siebel Server Name Value SADMIN Purpose Used to log in to the gateway name server to obtain configuration parameters. Used to log in to the gateway name server.
SADMIN
<machine name> 2320
Used to connect to the gateway name server. Recall that this is the other persons machine.
Siebel Enterprise Name OUEnt OUSrvr
Used to connect to the Siebel Enterprise. A string of up to 12 characters including letters, numbers, and underscores that uniquely identify the Siebel Server. A description displayed in several of the administrative views. Which component groups should be enabled on the Siebel Server when it first starts. Port on which the Siebel Server listens for connections. Port used by Siebel Remote for synchronization.
Siebel Server OUSrvr Call Center 2321
Network TCP/IP Port for 40400 Synchronization Manager Additional Tasks None
Configure SSL, LDAP, or Exchange synchronization. Used by the Siebel Connector for Oracle Applications to connect to back office Oracle databases. Cluster Siebel Servers to provide redundancy in case of server failure. For most deployments, the Siebel Server should start up when the system boots. To preserve system resources, do not do this on the classroom machine. Whether or not to start the Siebel Server service as soon as the profile execution completes.
Register External Oracle Checked DB ODBC Driver Clustering Configuration Not clustered Start Siebel Server service automatically? Unchecked
Start Siebel Server service at the end of profile execution?
Unchecked
f. Return to the Services window and select Action > Refresh. g. Start the Siebel Server [OUEnt_OUSrvr] Windows service. h. Once the service has completely started, log in to Siebel Call Center as SADMIN/SADMIN to confirm your configuration. Recall that the URL is http://localhost/callcenter_enu.
96
Port on which the gateway name server listens for connections.
Lesson 12: Multilingual Installations
Practice 12-1 Adding a Language to an Enterprise

Goals Time To add an additional language to an existing Siebel Enterprise 20 30 minutes
Instructions:
1. Add French to the Siebel Enterprise. This adds French Application Object Managers (AOMs), as well as French support files to your installation. a. Using Windows Explorer, navigate to D:\Labs\8.1_Install\Installers\Server\Siebel_Enterprise_Server. b. Double-click setup.exe. c. Click Next on the Welcome screen. d. The setup program recognizes the existing installation and presents a new option window:
97
In this practice, you will add French to your existing Siebel Enterprise. Recommended practice is to install all expected languages on initial deployment, but it is also possible to add new languages after the Enterprise has been deployed. To deploy a new language, run all of the installers and configuration tools in the same order as you would for an initial deployment.
Module 12: Multilingual Installations
e. Select Add languages to Siebel Enterprise Servers in D:\OUses and click Next. f. Select fra - French (Standard) and click Next. The language packs available to you depend on what you selected when you downloaded from E-Delivery. g. Once installation completes after 1-2 minutes, the Siebel Server Configuration Tool runs automatically. h. Select Add Language Support for the Siebel Server and click Next. i. Enter the parameters:
Parameter Gateway Name Server Authentication User Account Name Gateway Name Server Authentication User Account Password - and confirm Gateway Name Server Host Name Gateway Name Server TCP/IP Port Deployed Languages Value SADMIN Purpose Used to log in to the Siebel Gateway Name Server to obtain configuration information.
<Machine Name> 2320
Used to connect to the Siebel Gateway Name Server. Port on which the Siebel Gateway Name Server is listening for connections. Enterprise containing the Siebel Server. The languages to deploy on the Siebel Server.
Siebel Enterprise Name OUEnt English (American) French (Standard)
j. If necessary, click Next then Finish to exit the After Intallation dialog box. 2. Add French to the Siebel database seed data. This provides string translations for menu items and other strings displayed in the application. a. Select Start > Programs > Siebel Enterprise Server Configuration 8.1 > Database Server Configuration. b. Enter the parameters:
Parameter Siebel Server Directory Value D:\OUses\siebsrvr Purpose Location of Siebel Server executables. Location of Siebel Database Configuration Tool executables. Type of database used by the Siebel Enterprise. Used to either install the initial database, or add a language to an existing database.
Siebel Database Server D:\OUses\dbsrvr Directory Database Platform Action Action Type Has GRANTUSR.SQL been run? Oracle Database Enterprise Edition Install Database
Used to add a new language to an existing Add a language to an existing Siebel Database database. GRANTUSR.SQL has been run by the DBA to create Siebel users and roles English (American) Unless GRANTUSR.SQL has been run, the configuration scripts will fail, hence this step is a safety check. The language in which installer log files and other enterprise-wide messages are
Base Language
98
SADMIN
Used to log in to the Siebel Gateway Name Server.
displayed. Lanuage to add ODBC Data Source Name Database User Name Database User Password - and confirm Database Table Owner Database Table Owner Password - and confirm Parallel Indexing? Security Group ID/Grantee Log output directory Apply changes now? French (Standard) OUEnt_DSN SADMIN SADMIN Language to add to the database. Used to connect to the Siebel database. Used to log in to the Siebel database to access or update tables. Used to log in to the Siebel database.
SIEBEL SIEBEL
Used to access the Siebel database schema. Used to access the Siebel database schema.
Siebel Repository Name Siebel Repository Does not use the Oracle Parallel Indexing option SSE_ROLE install_lang Yes
Used to add data to the Siebel Repository. Used to improve performance when using multiple machines for the database server. Role of Siebel Users in the database. Location to store installer log files. Whether or not to apply the changes immediately.
c. Click OK in the Siebel Upgrade Wizard to start the database upgrade. d. Once the database upgrade completes, click OK and cancel out of the Database Configuration Tool. 3. Add French to the Siebel Web Server Extension. This adds virtual directories that point to the French object managers. a. Using Windows Explorer, navigate to D:\Labs\8.1_Install\Installers\Server\Siebel_Web_Server_Extension. b. Double-click setup.exe. c. Select Add languages to Siebel Web Server Extension in D:\OUWebServer\SWEApp and click Next. d. Select fra - French (Standard) as the language to add and click Next. e. Once installation completes, the Siebel Web Server Extension Configuration Tool runs. f. Select Add Language Support for the SWSE Configuration and click Next. g. Select both English (American) and French (Standard) as the deployed languages. h. Click Next and complete the configuration. The configuration should take a minute or two, during which some command prompts may open and close. 4. Restart the Siebel Server [OUEnt_OUSrvr] service. This is required to load the French version of the Siebel Call Center Application Object Manager. Wait for the Siebel Server service to fully start before proceeding. It should take several minutes.
99
5. Confirm the French language installation. a. Start a new instance of Internet Explorer and enter an address of http://<machine name>/callcenter_fra. b. Confirm that the field labels and copyright notice are shown in French:
6. Confirm that LOVs have not yet been translated. a. Enter:

b. Click the arrow. c. If a dialog box appears stating that, Votre navigateur nest pas configur correctement, click Rpar, Auto. Then click Excuter. This is the same Auto-Fix dialog box that appears in the English version of the application. d. Click the Socits tab. This translates to Accounts. e. Click My Accounts. Note that this string is not translated by default. This is the sort of testing you need to do when deploying a new language: When you are looking at a new language, you should navigate through the application and determine which strings, logos, or other images still require translation. f. Click Nouveau to create a new account. g. Enter INS Account in the Nom field. This is the account name. h. Select the drop-down list in the Statut field. Note that all of these account statuses are still in English. This is an example of an untranslated List of Values (LOV). i. Step off the record to save it.
100
j. Select Fichier > Dconnexion from the application-level menu to log out of the application.
101
Practice 12-2 Enabling Multilingual Lists of Values (MLOVs) (Optional)

Goals Time To enable an MLOV on the Account Status field 25 35 minutes
Instructions:
In this practice, you will enable a Multilingual List of Values (MLOV) on the Account Status field you examined in a previous practice. Multilingual Lists of Values store references to translated strings in the S_LST_OF_VAL table rather than the strings themselves therefore enabling large numbers of MLOVs can impact performance and affect integration strategies. See Creating and Administering Lists of Values in Configiuring Siebel Business Applications on Oracle Technology Network for more details. Note: This practice provides detailed steps on enabling a single MLOV in the application. Oracle provides automated tools for enabling large numbers of MLOVs at once. Contact your Oracle representative for assistance in obtaining and utilizing these tools. 1. Use Siebel Call Center to determine the LOV type for the Account Status field. a. Select Start > Programs > Internet Explorer b. Enter Address: http://localhost/callcenter_enu. c. Enter:
d. Click the arrow. e. Click the Accounts tab. f. Click INS Account under Recent Records. Note that accounts you create in one language are visible in other languages, because they are all stored in the same database. g. Click the Account List link. h. Select the Status drop-down list for the INS Account and select a value from it that is probably unique to Account Status. (Check the solutions if you have trouble):
i. Navigate to Administration - Data > List of Values. j. Query for a Display Value equal to the value you entered above, for example, Red Customer. More than one Type may be returned. What is the most likely LOV Type for Account Status in the list of returned types?
102
k. Select the record whose Type is ACCOUNT_STATUS and whose and Display Value matches the value you entered above. l. If necessary, scroll to the right to expose the Translate column.This determines whether the ACCOUNT_STATUS LOV Type is translatable. m. Verify that the Translatable checkbox is selected for ACCOUNT_STATUS. n. Log out of Siebel Call Center. o. Stop the Siebel Server [OUEnt_OUSrvr] service. You will be compiling to the server srf file, hence any Siebel Servers connected to the repository must be stopped. 2. Use Siebel Tools to determine whether or not the ACCOUNT_STATUS LOV can be transformed into an MLOV. Then modify the necessary columns to perform the transformation. Note that this process can be automated with tools available from your Oracle representative. Note: Siebel Tools is a tool used by developers to perform application customizations. It reads a set of tables in the database known as the Siebel Repository, and compiles these tables to a proprietary compressed binary file known as the Siebel Repository File. Typically an installation specialist would not be using Siebel Tools. a. Select Start > Programs > Siebel_Tools_81 > Siebel Tools. b. Log in as SADMIN/SADMIN, connecting to the Server database. c. Click the Flat tab in the Object Explorer. While the Types tab lists object types in their hierarchies, the Flat tab lists all object types in alphabetical order, and is useful for quickly finding child object types.
d. Select Column. e. Right-click anywhere in the column list on the right of the screen and select Columns Displayed.
103
f. Move LOV Type and LOV Bounded to the top of the list:
g. Click OK. h. Query for columns with an LOV Type of ACCOUNT_STATUS: i. Click the Query button . ii. Enter ACCOUNT_STATUS in the LOV Type column. iii. Click the Execute Query button . i. Modify the columns to support the ACCOUNT_STATUS MLOV: i. Verify that each column has the LOV Bounded checkbox checked. Only bounded picklists can be converted to MLOVs. Hence all of the columns returned by the query must have this checkbox checked in order for you to be able to enable translation on the LOV. ii. List the parent tables of the columns. You must lock each parent table for editing in order to modify the table:
iii. iv. v.
vi. vii. viii.

104
Click Table in the Object Explorer on the left of the screen. Query for a Name of S_ORG_EXT. Note that you need to scroll to the right to expose the table name. Right-click S_ORG_EXT and select Lock Object. Note: Normally a developer would not lock objects in the Server repository, but would instead work in a local repository and then check in the changes. Performing these changes in the server database is strictly for educational purposes. Repeat these steps to lock the other tables you found: S_ORG_BU, S_UCM_ORG_EXT, S_FINAN_PROF, and S_INV_PROF. Click Column in the Object Explorer and re-query for columns with LOV Type ACCOUNT_STATUS. For each column, change the Translation Table Name to S_LST_OF_VAL.
3. Run the Database Configuration Utility to translate all existing LOV values in the application. a. Select Start > Programs > Siebel Enterprise Server Configuration 8.1 > Database Server Configuration.
105
j. Compile each table into the Server srf file: i. Click the S_ORG_EXT Parent Table link in the appropriate record. ii. Right-click S_ORG_EXT and select Compile Selected Objects. iii. Browse for D:\OUses\siebsrvr\objects\enu\siebel_sia.srf. This is the repository file being used by your English applications. Note: Best practice is NOT to compile into the server repository; it is done here only to expedite this lab. iv. Click Compile. If you receive an error message that the file is in use, check to make sure all the Siebel Server services in the Enterprise are stopped. v. Repeat these steps to compile to the French srf file in D:\OUses\siebsrvr\objects\fra\siebel_sia.srf. vi. Click the back button to return to the column list. vii. For each of the other four columns, compile the parent table to both the English and French srf files. k. Select File > Exit from the application-level menu to close Siebel Tools.
b. Enter the parameters:

Parameter Siebel Server Directory Value D:\OUses\siebsrvr Purpose Location of Siebel Server executables. Location of Siebel Database Configuration Tool executables. Type of database used by the Siebel Enterprise. Note that you need to scroll down to locate this option. Used to synchronize database schemas, convert to Universal Time Code (UTC), or convert LOVs to MLOVs.
Siebel Database Server D:\OUses\dbsrvr Directory Database Platform Oracle Database Enterprise Edition Run Database Utilities (Scroll down to find this)
Action
Validate or Translate? Base Language ODBC Data Source Name Database User Name Database User Password - and confirm Database Table Owner Database Table Owner Password - and confirm Parallel Indexing? Security Group ID/Grantee Log output directory Apply changes now?
Translate English (American) OUEnt_DSN SADMIN SADMIN
Validation tests your settings before performing the actual translations. Language for error logs. Used to connect to the Siebel database. Used to connect to the Siebel database. Used to connect to the Siebel database.
SIEBEL SIEBEL
Used to access the Siebel database schema. Used to access the Siebel database schema.
Siebel Repository Name Siebel Repository Does not use the Oracle Parallel Indexing option SSE_ROLE mlov_translate Yes
Used to add data to the Siebel Repository. Used to improve performance when using multiple machines for the database server. Role of Siebel Users in the database. Location to store installer log files. Whether or not to apply the changes immediately.
c. Click OK to proceed with the Upgrade Wizard. d. Once it is complete, cancel out of the Database Configuration Tool. 4. Start the Siebel Server [OUEnt_OUSrvr] service. Allow it to fully start before proceeding. 5. Test your changes: a. Start Internet Explorer and enter an address of http://<machine name>/callcenter_enu. b. Log in as SADMIN/SADMIN. c. Click the Accounts tab. d. Click My Accounts.
106
Action Type
Multilingual List of Value Used to translate existing LOV values in the database to MLOV values. Conversion
e. Select the Status drop-down field for the INS Account and verify the options are all in English. f. Set the status to Qualified. g. Log out of Siebel Call Center. h. In Internet Explorer, enter an address of http://<machine name>/callcenter_fra. i. Log in as SADMIN/SADMIN. j. Click the Socits tab. k. Click My Accounts. l. Verify that the statut for the INS Account is Qualifie, French for Qualified. m. Select the Statut drop-down field and verify the options are all in French. n. Select Fichier > Dconnexion from the application-level menu to log out of the application.
107
Solutions 12-2 Enabling Multilingual Lists of Values (MLOVs)

Answers
1.h. Select the Status drop-down list and select a value from it that is probably unique to Account Status:. Any of the Statuses containing the word Customer are likely candidates; for example, Red Customer, Former Customer, New Customer, or Present Customer. Query for a Display Value equal to the value you entered above, for example, Red Customer. More than one Type may be returned. What is the most likely LOV Type for Account Status in the list of returned types? ACCOUNT_STATUS. If the answer were not this obvious, you would need to query for several other of the available values for Account Status until you got a unique LOV Type. List the parent tables of the columns. You must lock each parent table for editing in order to modify the table: S_ORG_EXT, S_UCM_ORG_EXT, S_ORG_BU, S_INV_PROF, S_FINAN_PROF
1.j.
2.i.ii.
108

D53912GC11 Ag

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

D53912GC11 Ag

Uploaded by

Copyright:

Available Formats

Siebel 8.1.

D53912GC11 Edition 1.1 November 2009 D63773

Oracle Internal & Oracle Academy Use Only

Oracle Internal & Oracle Academy Use Only

Oracle Internal & Oracle Academy Use Only

Oracle Internal & Oracle Academy Use Only

Lesson 1: Installation Considerations

Practice 1-1 Reviewing an Existing Installation (Optional)

Siebel 8.1.x Installation

Oracle Internal & Oracle Academy Use Only

Lesson 1: Installation Considerations

Review Parameters for a (Hypothetical) Existing Installation

Siebel Gateway Name Server

Siebel Enterprise Server

Siebel 8.1.x Installation

Oracle Internal & Oracle Academy Use Only

Lesson 1: Installation Considerations

Web Server Firewall

Siebel Gateway Name Server

Siebel Enterprise Server

a. Database server information:

Siebel 8.1.x Installation

Oracle Internal & Oracle Academy Use Only

Lesson 1: Installation Considerations

Siebel 8.1.x Installation

Oracle Internal & Oracle Academy Use Only

Lesson 1: Installation Considerations

4. Examine the information for the Siebel Gateway Name Server:

Web Server Firewall

AOM Siebel File System

Siebel Enterprise Server

SWSE Logical Profile Location D:\OUWebServer\SWEApp

Siebel 8.1.x Installation

Oracle Internal & Oracle Academy Use Only

Siebel Gateway Name Server

Lesson 1: Installation Considerations

5. Examine the information for the Siebel Servers:

Web Server Firewall

AOM Siebel File System a. Server Parameters:

Siebel Enterprise Server

Siebel 8.1.x Installation

Oracle Internal & Oracle Academy Use Only

Siebel Gateway Name Server

Lesson 1: Installation Considerations

6. Examine the information for the Siebel Web Server Extension:

Web Server Firewall

AOM Siebel File System

Siebel Enterprise Server

Siebel 8.1.x Installation

Oracle Internal & Oracle Academy Use Only

Siebel Gateway Name Server

Lesson 1: Installation Considerations

Siebel 8.1.x Installation

Oracle Internal & Oracle Academy Use Only

Lesson 2: Installing the Siebel Gateway Name Server

Practice 2-1 Installing the Siebel Enterprise Server

Siebel 8.1.x Installation

Oracle Internal & Oracle Academy Use Only

Lesson 2: Installing the Siebel Gateway Name Server

Siebel 8.1.x Installation

Oracle Internal & Oracle Academy Use Only

Lesson 2: Installing the Siebel Gateway Name Server