D53912GC11_ag

(1)

Siebel 8.1.x Installation

Activity Guide

D53912GC11

Oracle Internal & Or

(2)

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:

U.S. GOVERNMENT RIGHTS

The U.S. Government’s 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.

Trademark Notice

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

Oracle Internal & Or

(3)

Oracle Internal & Or

(4)

Oracle Internal & Or

(5)

Lesson 1: Installation Considerations

Practice 1-1 Reviewing an Existing Installation

(Optional)

Goals To read information about an existing Siebel Enterprise Time 10 – 15 minutes

Instructions:

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 Name E-mail Address Phone Number

Deployment Team Lead Renee Richards [email protected] (415) 555-3423 Siebel Administrator Stephen Storm [email protected] (212) 555-8900 System Administrator Jen Storm [email protected] (212) 555-4025 Database Administrator Brenda Grimm [email protected] (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

Oracle Internal & Or

(6)

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.

AOM EIM Siebel Gateway Name Server Web Server Siebel Servers Siebel File System Siebel Database Firewall

Siebel Enterprise Server

Oracle Internal & Or

(7)

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:

a. Database server information:

Machine Name EMEDBS01 IP Address 192.168.1.101

OS Windows Server 2003

Database Platform Oracle 10g SQLNet Connection String SIEBELTNS Connection Port 1521 Data Tablespace siebelts Index Tablespace siebelindexts Database Owner SIEBEL

Siebel Enterprise Server

Oracle Internal & Or

(8)

• 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 EMEDBS01 IP Address 192.168.1.101

Folder Name 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.

Oracle Internal & Or

(9)

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

Machine Name EMEGNS02

IP Address 192.168.1.102

Installation Directory D:\OUses Gateway Name Server Port 2320 Authentication Name SADMIN Authentication Password SADMIN Authentication Type DB Enterprise Name OUEnt

ODBC Name 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

Siebel Enterprise Server

Oracle Internal & Or

(10)

5. Examine the information for the Siebel Servers:

a. Server Parameters:

Machine Name EMESRV04 IP Address 192.168.1.104

Installation Directory D:\OUsrvr Server Name AOMServer Component Groups Call Center

Sales Connection Broker Port 2321 Sync Manager Port 40400

Machine Name EMESRV05 IP Address 192.168.1.105

Installation Directory D:\OUsrvr Server Name EIMServer Component Groups EIM

Workflow Connection Broker Port 2321 Sync Manager Port 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. AOM EIM Siebel Gateway Name Server Web Server Siebel Servers Siebel File System Siebel Database Firewall

Siebel Enterprise Server

Oracle Internal & Or

(11)

Lesson 1: Installation Considerations 6. Examine the information for the Siebel Web Server Extension:

Machine Name EMESWS03

IP Address 192.168.1.103

Web Server IIS 6.0

Installation Directory D:\OUWebServer

Compression No

HTTP 1.1-Compliant Firewall? Yes Login Session Timeout 300 Active Session Timeout 900

HTTP Port 80 HTTPS Port 443 FQDN AOM EIM Siebel Gateway Name Server Web Server Siebel Servers Siebel File System Siebel Database Firewall

Siebel Enterprise Server

Oracle Internal & Or

(12)

• 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.

Oracle Internal & Or

(13)

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

Time 40 – 50 minutes

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.

Oracle Internal & Or

(14)

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 machine’s 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.

Oracle Internal & Or

(15)

Lesson 2: Installing the Siebel Gateway Name Server 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.

Oracle Internal & Or

(16)

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.

Oracle Internal & Or

(17)

Lesson 2: Installing the Siebel Gateway Name Server 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.

Oracle Internal & Or

(18)

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.

Oracle Internal & Or

(19)

Lesson 2: Installing the Siebel Gateway Name Server 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 Value Purpose

Gateway Name Server

TCP/IP Port 2320 Port on which the Gateway Name Server will listen for connections. 2320 is the default, and should not be changed unless absolutely necessary.

Set the Gateway Name Server system service to start automatically

Selected Whether or not to start the Siebel Gateway Name Server service when the machine boots.

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. Click OK.

h. Leave the Siebel Configuration Wizard open.

i. Return to the system services window and select Action > Refresh.

j. Confirm that there is now a Siebel Gateway Name Server service and its status is Started. k. Return to Windows Explorer and confirm that D:\OUses\gtwysrvr\log now contains multiple

log files.

Oracle Internal & Or

(20)

d. Enter the parameters below, clicking Next each time to proceed through the configuration:

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.

Gateway Name Server Authentication User Account Name

SADMIN Used to access the Gateway Name Server. The username and password must be set up in the Gateway Name Server’s authentication system; for example, as a database user.

Gateway Name Server Authentication User Account Password - and confirm

SADMIN Used to access the Gateway Name Server. The username and password must be set up in the Gateway Name Server’s authentication system; for example, as a database user.

Gateway Name Server

Host Name <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.

Gateway Name Server

Port Number See below Used to connect to the Gateway Name Server.

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.

Oracle Internal & Or

(21)

Lesson 2: Installing the Siebel Gateway Name Server f. Complete the configuration:

Siebel Enterprise Name OUEnt Name of the new Siebel Enterprise. Enterprise Description OUEnt Enterprise Description of the enterprise. Siebel File System \\<machine

name>\siebfile

Where to store the Siebel File System. Use your machine name rather than D: to support the multi-server installation later in the course.

Database Platform Oracle Database Enterprise Edition

The database type used by the Siebel Enterprise. Database Table Owner SIEBEL The table owner of the database; set by the DBA. Oracle SQLNet Connect

String SIEBELDB Connection string to the Oracle database; provided by your DBA. Siebel Database User

Account Name SADMIN Database user used by the Siebel Enterprise components to connect to the database server. Set by the DBA.

Siebel Database User Account Password - and confirm

SADMIN Password for the Siebel Database User.

Enterprise Security

Authentication Profile Database Authentication

The default security mechanism used within the enterprise. Recommended practice is to leave this at database authentication.

Security Adapter Name DBSecAdpt Name of the security adapter; recommended practice is to leave this at its default.

Propogate

Authentication Settings to the Gateway Name Server

Selected 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.

Additional Tasks None Set up enhanced network security, charts, or data

quality connections

Oracle Internal & Or

(22)

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:

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

D:\OUses\gtwysrvr\admin\ Webserver

Location to store the logical profile. Can be any directory you choose, but it should be accessible by the Web server machine. Collect

Application-Specific Statistics Selected Whether to collect statistics on individual applications. Compression Type None 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.

HTTP 1.1-Compliant

Firewall Selected Enables network header compression to improve network performance. Login Session Timeout

Value 300 Time (in seconds) to keep a login session alive without any user activity. Active Session Timeout

Value 900 Time (in seconds) to keep an active (logged in) session alive without any user activity. HTTP Port Number 80 Port number on which the Web server listens

for HTTP connections. 80 is the default. HTTPS Port Number 443 Port number on which the Web server listens

for HTTPS connections. 443 is the default. Fully Qualified Domain

Name <blank> 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. High Interactivity or

Employee User Login Name

GUESTERM Used to bring up the initial login screen for employee applications; the user must be regsitered in the authentication system. High Interactivity or

Employee User Password

GUESTERM Used to bring up the initial login screen for employee applications; the user must be regsitered in the authentication system. Standard Interactivity

Password Encryption Unselected Whether to use RC2 encryption on the SI user password instead of the default Oracle

Oracle Internal & Or

(23)

proprietary encryption. Standard Interactivity or

Contact User Login Name

GUESTCST Used for anonymous browsing of customer applications; the SI user must be registered in the authentication system to allow anonymous browsing.

Standard Interactivity or

Contact User Password GUESTCST Used for anonymous browsing of customer applications; the SI user must be registered in the authentication system to allow anonymous browsing.

Siebel Enterprise

Security Token key Used to verify communications between Enterprise components. Can be any random string.

Default Statistics Page _stats.swe Where to store SWSE statistics.

Deploy SSL Unselected Whether to deploy SSL in the Enterprise. Used to support HTTPS connections.

d. Review the summary information and click Next.

e. Click Yes to execute the configuration. The execution should succeed in a few seconds. f. Click OK.

g. 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?

vii. Close eapps.cfg, not saving any changes.

viii. 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.

Oracle Internal & Or

(24)

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 Server’s 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.

Oracle Internal & Or

(25)

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)

5.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.

The only log file is base.txt. It contains the version and build number of the installation. There are no other log files.

8.g.vi. 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.

Oracle Internal & Or

(26)

Oracle Internal & Or

(27)

Lesson 3: Installing the Siebel Database

Practice 3-1 Configuring the Siebel Database

Goals To install the Siebel database Time 75 – 90 minutes

Instructions:

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.

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.

Oracle Internal & Or

(28)

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 system Password oracle Host String SIEBELDB

c. Click OK. You should receive a SQL> prompt. d. At the SQL> prompt, enter:

@D:\OUses\dbsrvr\Oracle\grantusr.sql

Oracle Internal & Or

(29)

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. e. Enter siebelts as the value for siebel_tablespace.

f. Enter temp as the value for temp_tablespace.

g. Enter siebelindexts as the value for siebel_indexspace. h. All grants should succeed.

i. Minimize SQLPlus.

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.

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.

Oracle Internal & Or

(30)

b. Enter the parameters below, being careful not to switch SIEBEL with SADMIN, and clicking Next each time to proceed through the configuration:

Siebel Server

Directory D:\OUses\siebsrvr Used to access Siebel Server executables and template files. Siebel Database

Server Directory D:\OUses\dbsrvr Used to access Siebel Database Server executables and template files. Database

Platform Oracle Database Enterprise Edition

Determines which SQL scripts to run to populate the schema and seed data.

Action Install Database Used to create the schema and seed data. Option Install Siebel Database Install a database or add a language. Option Yes, I wish to install a new

Siebel Database

Verify database installation. GRANTUSR.SQL GRANTUSR.SQL has been

run by the DBA to create Siebel users and roles

Specify that GRANTUSR.sql has been run. UNICODE UNICODE Database Determines available character sets. ODBC Data

Source Name OUEnt_DSN Used to connect to database. Enterprise name suffixed by _DSN. This connection was created when you configured the Siebel Enterprise. Database User

Name SADMIN Used to populate seed data.

Database Password - and confirm

SADMIN Used to populate seed data.

Database Table

Owner SIEBEL Used to generate schema.

Database Table Owner Password - and confirm

SIEBEL Used to generate schema.

Index Table

Space Name siebelindexts Contains Siebel indexes. This tablespace was created for you by your DBA. Table Space

Name siebelts Contains Siebel data tables. This tablespace was created for you by your DBA. Enter license

key? Yes, I would like to enter it now

Enter the license key to allow initial login; license keys may be added later, if desired. However, if you do not enter a license key, you will need to use the Siebel Developer Web client to enter one later. License Key <Copy and paste first line

from

D:\labs\8.1_Install\SIAkeys

License keys are available from Oracle at http://licensecodes.oracle.com.

Oracle Internal & Or

(31)

.txt >

Parallel Indexing Does not use the Oracle Parallel Indexing option

For database servers with multiple CPUs, using multiple indexing threads can improve

performance. It is not enabled in the classroom. Security Group

ID/Grantee SSE_ROLE Default database role for Siebel users; created by GRANTUSR.SQL. Log Output

Directory install Where to store installer log information.

c. Select “Yes apply configuration changes now” and click Next. d. Review the summary and click Next.

e. Click Yes to execute the configuration.

f. 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.

g. Once installation completes, click OK to close the Upgrade Wizard.

h. Switch to the Oracle Installer application and click OK in the Execution Successful dialog box.

i. Click Cancel to exit the configuration tool. j. Click Yes to confirm the cancellation. 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.

Oracle Internal & Or

(32)

Oracle Internal & Or

(33)

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

Time 15 – 20 minutes

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 co-locate 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.

Configuration Mode Configure Product in Live

Use offline configuration to generate an installer

response file; details are in a later lesson.

Oracle Internal & Or

(34)

Gateway Name Server

TCP/IP Port 2320 Port number on which the Siebel Gateway Name Server machine is listening for connections. Siebel Enterprise Name OUEnt The logical name of the Siebel Enterprise. Used to

connect to the Siebel Enterprise to get the enterprise-level parameters. The value is case-sensitive. Siebel Server Name OUSrvr A string of up to 12 characters including letters,

numbers, and underscores that uniquely identify the Siebel Server.

Siebel Server

Description Siebel Server OUSrvr

A description displayed in several of the administrative views.

Enable Component

Groups Call Center 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.

Siebel Connection

Broker Port 2321 Port on which the Siebel Server listens for connections; for example, from the Siebel Web Server Extension. Network TCP/IP Port for

Synchronization Manager

40400 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.

Additional Tasks None Configure SSL, LDAP, or Exchange synchronization Register External Oracle

DB ODBC Driver Selected Used by the Siebel Connector for Oracle Applications to connect to back office Oracle databases Clustering Configuration Not clustered Cluster Siebel Servers to provide redundancy in case

of Server failure Set the Siebel Server

system service to start automatically

Not Selected For most deployments, the Siebel Server should start up when the system boots. To preserve system resources, do not do this for this course

Start Siebel Server service at the end of profile execution

Not Selected Whether or not to start the Siebel Server service as soon as the profile execution completes.

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.

Oracle Internal & Or

(35)

Lesson 4: Installing a Siebel Server g. Click the Performance tab.

h. Wait for CPU Usage to stay below 50%. This should take 3-4 minutes. i. Minimize the Task Manager.

j. Bring up the Services window again and confirm that the Siebel Server [OUEnt_OUSrvr] service is listed as Started.

k. Minimize the Services window.

l. Using Windows Explorer, navigate to D:\OUses\siebsrvr\log.

m. If necessary, select View > Details to expose the file sizes. There should be several files, none of which are over 10 KB in size.

n. 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.

o. If restarting the service does not solve the problem, open the log and attempt to diagnose the problem. Ask your instructor for help.

p. Close any open log files, not saving any changes.

Oracle Internal & Or

(36)

Oracle Internal & Or

(37)

Lesson 5: Installing the Siebel Web Server Extension

Practice 5-1 Installing the Siebel Web Server Extension

Goals To install, configure, and test the Siebel Web Server Extension Time 20 – 25 minutes

Instructions:

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. 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.

Directory Name D:\OUWebServer\SWEApp Location to place installed files. Language(s) enu - English (American) Which language-specific files to install. Program Folder Siebel Enterprise Server

Configuration 8.1

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: Navigate away from the Configuration Tool, leaving it open.

Oracle Internal & Or

(38)

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 Microsoft’s 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.

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:

Action Apply an SWSE Logical Profile

Creates virtual directories on Web server and copies eapps.cfg and other support files to SWSE install directory. Load Balancer Single Siebel Server If load balancing is selected, balances sessions for

enterprises with multiple Application Object Managers of the same type.

Siebel Server Host

Name <machine name> If load balancing is not selected, the single Server’s name will be written into eapps.cfg. Siebel Server

Connection Broker Port Number

2321 If load balancing is not selected, the single Server’s connection broker port will be written into eapps.cfg. Siebel Web Server

Extension Logical Profile Location

D:\OUses\gtwysrvr\ ADMIN\Webserver

The location of the logical profile that will be applied to generate eapps.cfg and the virtual directories.

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.

Oracle Internal & Or

(39)

Lesson 5: Installing the Siebel Web Server Extension 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:

Oracle Internal & Or

(40)

g. Log in using:

User ID SADMIN Password SADMIN

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. ii. In the Siebel application, click the Site Map icon near the top of the screen. iii. Click the Administration - Application link.

iv. 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.

v. Click New.

vi. 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.

vii. Step off the record to save it.

viii. Repeat these steps for the other keys in SIAkeys.txt. ix. 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.

Oracle Internal & Or

(41)

Lesson 5: Installing the Siebel Web Server Extension 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 Manager’s 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

Oracle Internal & Or

(42)

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.

Oracle Internal & Or

(43)

Lesson 6: Installing the Siebel Developer or Mobile Web Client

Practice 6-1 Installing the Developer Web Client

Goals To install and configure the Siebel Developer Web Client Time 25 – 30 minutes

Instructions:

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.

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:

Name Siebel_Web_Client_81 Name of the Program Folder containing the shortcuts.

Path D:\OUClient Location in which to install the files. Product-Specific

Prerequisite Checks Next Click Next. Click Yes to proceed through the warning; it is generated because you do not have Microsoft Word installed on your classroom

machine.

Oracle Internal & Or

(44)

Database Alias SIEBELDB Connection information for contacting the database; in this case, the connection string already created for the Oracle database. Table Owner SIEBEL Used to read database schema.

File System Server D:\siebfile Used to read data from the enterprise’s Siebel File System. See the note below with regards to using an absolute file path.

Siebel Remote Server localhost Used for synchronization with a Siebel Server, if desired. See the note below with regards to using localhost.

Gateway Name

Server Address localhost Used to connect to the Siebel Gateway Name Server. See the note below with regards to using localhost.

Enterprise Server

Name OUEnt Used to collect enterprise information.

Request Server Name OUSrvr The name of a Siebel Server on which the Server Request Broker component is running.

Search Server

Hostname localhost 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. Search Server Port

Number 2048 Leave this at its default.

Summary Screen Install Click the Install button.

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. e. 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.

f. 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.

g. Once installation completes, click Exit and then click Yes.

h. 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.

Oracle Internal & Or

(45)

Lesson 6: Installing the Siebel Developer or Mobile Web Client 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.

Oracle Internal & Or

(46)

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.

b. 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.

c. 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.

d. 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.

e. Click the My Accounts link. Notice that there are no account records in the server database. f. Click the browser’s 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).

g. 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. h. Close the Technical Support dialog box.

i. In Microsoft Windows, return to the Services window. j. Stop the Siebel Gateway Name Server service.

k. Minimize the Services window. l. Return to the thick client.

m. 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.

n. Click the browser’s 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.

o. Log out of the thick client.

i. From the application-level (blue) menu, select File > Log Out.

Oracle Internal & Or

(47)

Lesson 6: Installing the Siebel Developer or Mobile Web Client

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.

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.

D53912GC11_ag

Siebel 8.1.x Installation

Oracle Internal & Or

Oracle Internal & Or

Table of Contents

Oracle Internal & Or

Oracle Internal & Or

Practice 1-1 Reviewing an Existing Installation

(Optional)

Instructions:

Oracle Internal & Or

Review Parameters for a (Hypothetical) Existing Installation

Siebel Enterprise Server

Oracle Internal & Or

Siebel Enterprise Server

Oracle Internal & Or

Oracle Internal & Or

Siebel Enterprise Server

Oracle Internal & Or

Siebel Enterprise Server

Oracle Internal & Or

Siebel Enterprise Server

Oracle Internal & Or

Oracle Internal & Or

Practice 2-1 Installing the Siebel Enterprise Server

Instructions:

Oracle Internal & Or

Oracle Internal & Or

Oracle Internal & Or

Oracle Internal & Or

Oracle Internal & Or

Oracle Internal & Or

Oracle Internal & Or

Oracle Internal & Or

Oracle Internal & Or

Oracle Internal & Or

Oracle Internal & Or

Oracle Internal & Or

Solutions 2-1 Installing the Siebel Enterprise Server

Answers

Oracle Internal & Or

Oracle Internal & Or

Practice 3-1 Configuring the Siebel Database

Instructions:

Oracle Internal & Or

Oracle Internal & Or

Oracle Internal & Or

Oracle Internal & Or

Oracle Internal & Or

Oracle Internal & Or

Practice 4-1 Configuring a Siebel Server

Instructions:

Oracle Internal & Or

Oracle Internal & Or

Oracle Internal & Or

Oracle Internal & Or

Practice 5-1 Installing the Siebel Web Server Extension

Instructions:

Oracle Internal & Or

Oracle Internal & Or

Oracle Internal & Or

Oracle Internal & Or

Oracle Internal & Or

Solutions 5-1 Installing the Siebel Web Server Extension

Answers

Oracle Internal & Or

Practice 6-1 Installing the Developer Web Client

Instructions:

Oracle Internal & Or

Oracle Internal & Or

Oracle Internal & Or

Oracle Internal & Or

Oracle Internal & Or