siebel 6 - clientad

SIEBEL® eBUSINESS APPLICATIONS

SIEBEL CLIENT INSTALLATIONAND ADMINISTRATION GUIDE

SIEBEL 2000VERSION 6.2, REV. A

JUNE 2001

10PA1-CI01-06200

Siebel Systems, Inc., 2207 Bridgepointe Parkway, San Mateo, CA 94404 Copyright © 2001 Siebel Systems, Inc.All rights reserved. Published 2001Printed in the United States of America

No part of this publication may be stored in a retrieval system, transmitted, or reproduced in any way, including but not limited to photocopy, photographic, magnetic or other record, without the prior agreement and written permission of Siebel Systems, Inc.

The full text search capabilities of Siebel eBusiness Applications include technology used under license from Fulcrum Technologies, Inc. and are the copyright of Fulcrum Technologies, Inc. and/or its licensors.

Siebel, the Siebel logo, TrickleSync, TSQ, Universal Agent, and other Siebel product names referenced herein are trademarks of Siebel Systems, Inc., and may be registered in certain jurisdictions.

Windows® is a registered trademark of Microsoft Corporation.

All other product names, marks, logos, and symbols may be trademarks or registered trademarks of their respective owners.

U.S. GOVERNMENT RESTRICTED RIGHTS. Programs, Ancillary Programs and Documentation, delivered subject to the Department of Defense Federal Acquisition Regulation Supplement, are “commercial computer software” as set forth in DFARS 227.7202, Commercial Computer Software and Commercial Computer Software Documentation, and as such, any use, duplication and disclosure of the Programs, Ancillary Programs and Documentation shall be subject to the restrictions contained in the applicable Siebel license agreement. All other use, duplication and disclosure of the Programs, Ancillary Programs and Documentation by the U.S. Government shall be subject to the applicable Siebel license agreement and the restrictions contained in subsection (c) of FAR 52.227-19, Commercial Computer Software - Restricted Rights (June 1987), or FAR 52.227-14, Rights in Data—General, including Alternate III (June 1987), as applicable. Contractor/licensor is Siebel Systems, Inc., 2207 Bridgepointe Parkway, San Mateo, CA 94404.

Proprietary InformationSiebel Systems, Inc. considers information included in this documentation andin Siebel Online Help to be Confidential Information. Your access to and use ofthis Confidential Information are subject to the terms and conditions of: (1) theapplicable Siebel Systems software license agreement, which has been executedand with which you agree to comply; and (2) the proprietary and restrictedrights notices included in this documentation.

Contents

IntroductionWho Should Use This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intro-2

How This Guide Is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intro-3

What’s New in This Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intro-4

Additional Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intro-4

Contacting Siebel Technical Support . . . . . . . . . . . . . . . . . . . . . . . . Intro-6

Siebel Systems Welcomes Your Comments . . . . . . . . . . . . . . . . . . . Intro-8

PART 1. Siebel Client Basics

Chapter 1. Overview of Siebel ClientsIntroduction to Siebel Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Siebel Client Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Benefits of Thin Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Application Object Manager and Thin Clients . . . . . . . . . . . . . . . . . . . . 1-6

Choosing a Thin Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

The Main Differences Between the Thin Clients . . . . . . . . . . . . . . . . . . . . 1-7

Chapter 2. Introduction to Configuration FilesAbout This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Sample Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Example Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Editing Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

How to Edit Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Version 6.2, Rev. A Siebel Client Installation and Administration Guide i i i

Contents

PART 2. Dedicated and Mobile Clients Installation and Configuration

Chapter 3. Dedicated and Mobile Clients OverviewWhat Are the Siebel Dedicated and Mobile Clients? . . . . . . . . . . . . . . . . 3-2

More Information About the Mobile Client and Siebel Remote . . . . . . . . . 3-2

Comparing the Siebel Dedicated and Mobile Clients . . . . . . . . . . . . . . . 3-5

Chapter 4. Installing the Dedicated and Mobile ClientsAbout This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Preinstallation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Choosing a Directory Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Verifying Siebel Client Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Installing Database Connectivity Software . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Installing Included Third-Party Software . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Installing Fulcrum SearchServer Desktop . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Installing the Siebel Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Post-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

Verifying Successful Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-11

Verifying the Siebel Client Directory Structure . . . . . . . . . . . . . . . . . . . . 4-14Verifying the Siebel Client Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16Verifying Siebel Client ODBC Data Sources . . . . . . . . . . . . . . . . . . . . . . . 4-17

Removing the Dedicated Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18

Chapter 5. Configuring the Dedicated and Mobile ClientsLogging Onto Your Siebel Application . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Establishing Network Connectivity to the Siebel Remote Server . . . . . . . 5-3

Setting User Synchronization Options . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Synchronization Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

i v Siebel Client Installation and Administration Guide Version 6.2, Rev. A

Contents

Editing Mobile Client Configuration Parameters . . . . . . . . . . . . . . . . . . . 5-9

Setting Siebel Remote Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

Sample Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11

Editing the Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11Recovering from Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-12

Setting Up the Siebel Remote Server . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13

Setting Up a New Siebel Remote User . . . . . . . . . . . . . . . . . . . . . . . . . 5-13

Creating a Mobile Client User Account . . . . . . . . . . . . . . . . . . . . . . . . . .5-13

Setting Up Mobile Client Hardware and Software . . . . . . . . . . . . . . . . . . .5-14

Establishing Autodial Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-14

Registering a Mobile Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-14

Running Database Extract for a Mobile Client . . . . . . . . . . . . . . . . . . . . .5-15

Starting Siebel Remote Server Processes . . . . . . . . . . . . . . . . . . . . . . . . . .5-17

Starting the Transaction Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-18

Initializing a Mobile Client Local Database . . . . . . . . . . . . . . . . . . . . . . .5-21

Synchronizing a Mobile Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22

How Changes Are Propagated to and from a Mobile Client Machine . . . . .5-22

Workflow for Changes Made by Mobile Users . . . . . . . . . . . . . . . . . . . . .5-24Synchronizing a Mobile Client Machine . . . . . . . . . . . . . . . . . . . . . . . . . .5-26

Editing Dedicated Client Configuration Files . . . . . . . . . . . . . . . . . . . . 5-26

Chapter 6. Optimizing Dedicated and Mobile Client Performance

Configuring Cursor Close . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Calculating Cursor Configuration Parameter Values . . . . . . . . . . . . . . . . . 6-3

Setting Cursor Configuration Parameter Values . . . . . . . . . . . . . . . . . . . . . 6-4

Configuring Active Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7

Siebel Docking Transaction Logging at Runtime . . . . . . . . . . . . . . . . . . . 6-7

Configuring Antivirus Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8

Server-Side Performance Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8

Version 6.2, Rev. A Siebel Client Installation and Administration Guide v

Contents

Chapter 7. Troubleshooting the Dedicated ClientReturning More Rows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

PART 3. Thin Client for Windows and Java Thin Client Installation and Configuration

Chapter 8. Thin Client for Windows and Java Thin Client Overview

What Are Thin Client for Windows and Java Thin Client? . . . . . . . . . . . 8-2

What’s New in Java Thin Client and Thin Client for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5

Deploying Windows and Java Thin Client Applications . . . . . . . . . . . . . 8-6

User Interface Functionality Supported in Windows and Java Thin Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7

Applet Classes Supported by Thin Clients . . . . . . . . . . . . . . . . . . . . . . . . 8-8

Supported Control Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9

Unsupported Siebel Script Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-10

Chapter 9. Installing and Configuring Siebel Thin Client for Windows

About This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Connect String Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Where to Find Information for New Connect String . . . . . . . . . . . . . . . . . 9-2

Support for Connect String Style Prior to Siebel 2000 . . . . . . . . . . . . . . . . 9-3

Pre-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

Verifying Thin Client Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

Verifying the Siebel Enterprise Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4

Understanding the Administrator Installation Tasks . . . . . . . . . . . . . . . . . 9-5

Installing Siebel Thin Client for Windows . . . . . . . . . . . . . . . . . . . . . . 9-5

v i Siebel Client Installation and Administration Guide Version 6.2, Rev. A

Contents

Launching Siebel Thin Client for Windows . . . . . . . . . . . . . . . . . . . . . 9-10

Creating a Custom Installer and Sharing Thin Client Files . . . . . . . . . . 9-10

Creating a Custom Thin Client for Windows Installer . . . . . . . . . . . . . . . . 9-11

Packaging the Thin Client for Windows Installer . . . . . . . . . . . . . . . . . . .9-15

Distributing the Thin Client Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-16

Modifying the Shortcut for the Stand-Alone Executable . . . . . . . . . . . . 9-17

Sample Connect Strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-18

Server-Side Performance Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20

Removing Thin Client for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20

Chapter 10. Installing and Configuring Siebel Java Thin ClientAbout This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Where to Find Information for New Connect String . . . . . . . . . . . . . . . 10-2


Verifying Thin Client Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-2Verifying the Siebel Enterprise Server . . . . . . . . . . . . . . . . . . . . . . . . . . .10-3

Installing Siebel Java Thin Client Under UNIX . . . . . . . . . . . . . . . . . . . 10-4

Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6

Editing the Java Thin Client Configuration File . . . . . . . . . . . . . . . . . . . . .10-6

Year 2000 Compliance in Siebel Java Thin Client . . . . . . . . . . . . . . . . . . 10-11

Customizing the Java Thin Client Help . . . . . . . . . . . . . . . . . . . . . . . . . 10-11

Sharing Thin Client Start-Up Files . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17

Starting Java Thin Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17

Removing Java Thin Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-18

Chapter 11. Deploying Siebel Thin Client for WindowsAbout This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2

Thin Client for Windows Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2

Deployment Sample Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3

Version 6.2, Rev. A Siebel Client Installation and Administration Guide v i i

Contents

Chapter 12. Java Thin Client and Thin Client for Windows Network Requirements

About This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2

Accessing the Thin Clients from Outside a Firewall . . . . . . . . . . . . . . . 12-2

Firewall Requirements in a Load-Balanced Environment . . . . . . . . . . . . . 12-2Firewall Requirements in a Non-Load-Balanced Environment . . . . . . . . . 12-4

Chapter 13. Troubleshooting Thin Client for Windows and Java Thin Client

Troubleshooting Your Thin Client . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

PART 4. HTML Thin Client Installation and Configuration

Chapter 14. Siebel HTML Thin Client OverviewAbout This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2

What’s New in This Release of HTML Thin Client . . . . . . . . . . . . . . . . 14-2

How Siebel HTML Thin Client Works . . . . . . . . . . . . . . . . . . . . . . . . . 14-3

What Is Siebel HTML Thin Client? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4

Key Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4

What Happens When a User Enters a URL . . . . . . . . . . . . . . . . . . . . . 14-5

Where to Find Additional Information . . . . . . . . . . . . . . . . . . . . . . . . 14-8

v i i i Siebel Client Installation and Administration Guide Version 6.2, Rev. A

Contents

Chapter 15. Preparing to Install Siebel .COM Applications on Windows NT Server and UNIX Systems



Verifying Thin Client Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-2

Planning the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-3

Verifying the Siebel Enterprise Server . . . . . . . . . . . . . . . . . . . . . . . . . . .15-5

Verifying Web Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-5

Installing Siebel .COM Applications . . . . . . . . . . . . . . . . . . . . . . . . . 15-6

Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15-6

Chapter 16. HTML Thin Client Network RequirementsAbout This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2

Firewall Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3

Browser to Web Server Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16-4

Web Server Extension to Application Object Manager Connection . . . . . . .16-4

Firewall Requirements in a Load-Balanced Environment . . . . . . . . . . . . 16-5

Firewall Requirements in a Non-Load-Balanced Environment . . . . . . . . 16-6

Chapter 17. TroubleshootingGeneral Troubleshooting Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2

Windows NT Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-2

Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-2

Object Manager Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-2

Using a Single .srf and .cfg File for Troubleshooting . . . . . . . . . . . . . . . . .17-3

Visual Basic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-3

Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17-3

Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-4

Version 6.2, Rev. A Siebel Client Installation and Administration Guide ix

Contents

PART 5. Appendices

Appendix A. Index of Configuration ParametersAppendix Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

Configuration Parameters Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

Appendix B. Siebel.cfg Configuration ParametersGeneric Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2

Client and Server Application Parameters . . . . . . . . . . . . . . . . . . . . . . . . . B-3

Datasources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7

Properties of DataSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8

Actuate Reports Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-15

Preload Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-15

Product Configurator Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-16DataCleansing Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-17

DeDuplication Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-18

SAP Subsystem Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-19Security Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-20

LDAP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-21Internet Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-24

Appendix C. Limiting Views to the Thin or Dedicated ClientLimiting Views to Thin Client or Dedicated Client . . . . . . . . . . . . . . . . . C-2

Administration of Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2

Configuration of Screen Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2

Appendix D. Optimizing Thin Client PerformanceApplication Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2

Server-Side Performance Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2

x Siebel Client Installation and Administration Guide Version 6.2, Rev. A

Contents

Appendix E. UNIX-Supported Business Component ClassesBusiness Component Classes Supported Under UNIX . . . . . . . . . . . . . . . E-1

Index

Version 6.2, Rev. A Siebel Client Installation and Administration Guide x i

Contents

xi i Siebel Client Installation and Administration Guide Version 6.2, Rev. A

Introduction

Who Should Use This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intro-2

How This Guide Is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intro-2

What’s New in This Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intro-3

Additional Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intro-3

Contacting Siebel Technical Support . . . . . . . . . . . . . . . . . . . . . . . . Intro-5

Siebel Systems Welcomes Your Comments . . . . . . . . . . . . . . . . . . . Intro-6

Version 6.2, Rev. A Siebel Client Installation and Administration Guide Intro -1

Introduction

Who Should Use This Guide

Who Should Use This Guide Intro

The audience for this guide consists of:

How This Guide Is Organized Intro

This book is organized around related audiences.

� The chapters in Part 1, “Siebel Client Basics” apply to all audiences.

� The appendixes contain information that is applicable in special cases or to a subset of the clients.

� The rest of the parts of this guide are organized by client type. Table 1 provides a list of the parts of the book by client type.

� See Appendix A, “Index of Configuration Parameters,” for an alphabetical list of the client configuration parameters documented in this guide.

Siebel Application Administrators

Persons responsible for planning, setting up, and maintaining Siebel applications.

Siebel System Administrators

Persons responsible for the whole system, including installing, maintaining, and upgrading Siebel products.

Siebel Application Developers

Persons who plan, implement, and configure Siebel applications, possibly adding new functionality.

Installers Persons responsible for setting up Siebel systems for initial use.

Table 1. This Guide Is Organized by Client Type

If you are interested in installing and configuring: See the following part of this guide:

Dedicated or mobile client applications Dedicated and Mobile Clients Installation and Configuration

Thin Client for Windows and Java Thin Client applications

Thin Client for Windows and Java Thin Client Installation and Configuration

HTML Thin Client applications HTML Thin Client Installation and Configuration and the Siebel Server Installation Guide and Configuring Siebel .COM Applications

Int ro -2 Siebel Client Installation and Administration Guide Version 6.2, Rev. A

Introduction

What’s New in This Release

This guide provides information necessary to implement, configure, and monitor Siebel applications, with particular detail provided for application, client/server, and thin client administration.

What’s New in This Release Intro

See the overview chapters for each client type for a list of the new features in this release. The overview chapters are:

� Chapter 3, “Dedicated and Mobile Clients Overview”

� Chapter 8, “Thin Client for Windows and Java Thin Client Overview”

� Chapter 14, “Siebel HTML Thin Client Overview”

NOTE: Your Siebel implementation may not have all the features described in this guide, depending on which software modules you have purchased.

Additional Documentation Intro

The following documentation also provides information on the topics addressed in this guide.

NOTE: Users must understand how to use Siebel Tools to be successful in configuring Siebel HTML Thin Client applications. Users should read the Siebel Tools Guide and Configuring Siebel .COM Applications before configuring their Siebel HTML Thin Client applications.

Configuring Siebel .COM Applications

Siebel Applications Administration Guide

Siebel eBriefings Guide

Siebel Object Interfaces Reference

Siebel Object Types Reference

Siebel Release Notes

Siebel Server Administration Guide

Siebel Tools Guide


Introduction

Additional Documentation

This guide does not provide information about general software concepts, such as records and queries, or about using Windows and UNIX. Neither does it provide instructions for basic navigation of Siebel applications. For this kind of information about Siebel applications, refer to Siebel Basics.

Administrators and developers, such as marketing administrators, call center administrators, and application developers, should also read the Siebel Applications Administration Guide for information on how to set up and maintain Siebel applications features.

You can find information about Siebel Technical and Professional Services in Guide to Siebel Global Services.

For copies of these documents, please use the Siebel Books Online Web site (http://ebusiness.siebel.com/booksonline). Through Siebel Books Online, you can order additional Siebel documentation and copies of the Siebel Bookshelf for Enterprise Applications CD-ROM.

For the most current and accurate documentation, see the Documentation Updates section of the Siebel SupportWeb site (http://ebusiness.siebel.com/supportweb/). The Documentation Updates show changes that have been made to the documentation since it was released. For up-to-the-minute information on Siebel products, see Siebel Release Notes. Siebel Release Notes appear on the Siebel SupportWeb site.

Siebel Systems reserves the right to modify the documentation at any time by posting revised documentation on the Siebel SupportWeb site.

Another source of information is Siebel Online Help.


http://ebusiness.siebel.com/booksonline

http://ebusiness.siebel.com/supportweb/


Introduction

Contacting Siebel Technical Support

Contacting Siebel Technical Support Intro

Do you know how to access Siebel Technical Support? It is crucial that you understand the requirements for getting support before you encounter technical issues that require Siebel Technical Support’s assistance. This will facilitate smooth resolution of your issues. If you have questions, please don’t hesitate to contact us.

To maximize your knowledge of Siebel products and your return on investment:

� You must attend Siebel training to become a designated contact.

� Your Siebel-trained designated contacts provide technical support to your users. Siebel Technical Support provides support directly to your designated contacts only.

To provide efficient, timely support and access to the Technical Support knowledge base:

� Siebel Technical Support is primarily Web-based; it can be accessed through Siebel SupportWeb (http://ebusiness.siebel.com/supportweb/). Please submit new service requests to us through SupportWeb, where you can also search the knowledge base for solutions.

� Designated contacts receive read/write access to Siebel SupportWeb. All other project team members at your company receive read-only accounts so that they can access the knowledge base.

To register for Siebel training, access http://siebeluniversity.siebel.com/edPortal and choose Implementation Team Training.

Please submit your technical issues and updates to Siebel SupportWeb (http://ebusiness.siebel.com/supportweb/). If you do not have a SupportWeb account, or if you have a question, please contact us at [email protected] or call your local Siebel Support Center:

� North America: +1 800 214 0400 or +1 650 295 5724

� Brazil (São Paulo): +55 11 5110 0800

� UK (London): +44 800 072 6787 or +44 1784 494949

� Germany (Munich): +49 89 95718 400

� France (Paris): +44 800 072 6787 or +44 1784 494949




http://siebeluniversity.siebel.com/edPortal


Introduction

Siebel Systems Welcomes Your Comments

� Ireland (Galway): +44 800 072 6787 or +44 1784 494949

� Japan (Tokyo): 0120 606 750 (Japan domestic only), +81 3 5464 7948 (outside of Japan)

� Singapore: +65 212 9266

Outside of local support center hours, Gold and Rollout Support Option customers can call +1 800 214 0400 or +1 650 295 5724.

We appreciate your business and look forward to working with you.

Siebel Systems Welcomes Your Comments Intro

To help us improve our products, we want to know about any corrections or clarifications to this guide that you would find useful. Please include in your message:

� The title and version of the guide (very important)

� The name and version number of the Siebel eBusiness Application you are using

� Your name, job title or functional area, company name, phone number, and email address

Contact us through regular mail or email at:

Siebel Systems, Inc.Technical Publications Department2207 Bridgepointe ParkwaySan Mateo, CA 94404-5009

[email protected]

We appreciate your feedback.


S i e b e l C l i e n t B a s i c s Part 1

Chapter 1. Overview of Siebel Clients

Chapter 2. Introduction to Configuration Files

Version 6.2, Rev. A Siebel Client Installation and Administration Guide

Siebel Client Installation and Administration Guide Version 6.2, Rev. A

Overview of Siebel Clients 1

Introduction to Siebel Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Siebel Client Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Benefits of Thin Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Application Object Manager and Thin Clients . . . . . . . . . . . . . . . . . . . . 1-6

Choosing a Thin Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

The Main Differences Between the Thin Clients . . . . . . . . . . . . . . . . 1-7

Version 6.2, Rev. A Siebel Client Installation and Administration Guide 1-1

Overview of Siebel Clients

Introduction to Siebel Clients

Introduction to Siebel Clients 1

This chapter contains an overview of your Siebel client and how it works. Figure 1-1 illustrates the architecture of a Siebel deployment. Following the figure is a summary of the entities that make up the Siebel client and descriptions of each type of client.

Figure 1-1 is a logical diagram of the entities that make up the Siebel eBusiness Applications environment and demonstrates at a high level how the clients interact with the Siebel database.

Figure 1-1. Logical Diagram of the Siebel eBusiness Applications Environment

Siebel Gateway Server and Name Server

Resonate

Siebel FileSystem

SiebelServer

SiebelServer

SiebelServer

Siebel Enterprise Server

Server Manager

Application

Application

MobileClient

Web Browser/Application

Thin Client

Application

DedicatedClient

SiebelDatabase

1-2 Siebel Client Installation and Administration Guide Version 6.2, Rev. A



All Siebel eBusiness Applications installations include one or more of the various Siebel clients that connect to various servers (depending on the type of client) to request and analyze data. You may deploy a mixture of dedicated and thin clients.

NOTE: In addition to these Siebel clients for individual users, the dedicated client is required in any deployment for administration.

Siebel Client Types 1

A Siebel client is a computer that operates Siebel Sales, Siebel Call Center, Siebel Field Service, Siebel Marketing, and/or Siebel .COM Applications, accessing data and services from one or more servers.

Siebel eBusiness Applications supports these types of clients:

� Thin client. With two exceptions, thin clients run inside a standard Web browser from the client PC and do not store data locally. Thin client connects directly to the Gateway Server only, not to any other server. The Siebel Server executes all business logic for thin clients. There are three types of thin clients: Siebel Java Thin Client, Siebel Thin Client for Windows, and Siebel HTML Thin Client.

The two thin clients that do not run inside a Web browser are Siebel Java Thin Client, which enables enterprises to deploy the user interface layer of Siebel eBusiness Applications as a stand-alone Java application, and the new stand-alone Thin Client for Windows. Java Thin Client and the stand-alone Thin Client for Windows do not run inside a browser; like the other thin clients, they do not store any data locally.

See Chapter 8, “Thin Client for Windows and Java Thin Client Overview,” and Chapter 14, “Siebel HTML Thin Client Overview,” for more information about each thin client.

� Dedicated and mobile clients. The dedicated client is connected directly to a database server for all data access, and it does not store any Siebel data locally. The mobile client is designed for local data access, without the need to be connected to a server. See Chapter 3, “Dedicated and Mobile Clients Overview,” for more information about dedicated and mobile clients.

Siebel thin client is different from Siebel dedicated client, which is the default Siebel client for Siebel eBusiness Applications. In Siebel dedicated and mobile clients, unlike Siebel thin clients, all layers of the Siebel eBusiness Applications architecture, except for the database, reside on the user’s personal computer. For mobile client users, a local database is stored on each mobile machine.




Figure 1-2 shows the deployment differences between Siebel dedicated client and Siebel thin clients.

Figure 1-2. Deployment Difference Between the Siebel Dedicated Client and the Thin Clients

Siebel Gateway Server

Business ObjectsLayer

Data ObjectsLayer

Siebel ObjectManagers

Siebel Servers

Siebel Active XInterfaces

External App

Siebel WebEngine

Web Server

HTML ThinClient

ExternalApplications

Dedicated Client

HTML Page

Web Browser

Thin Client forWindows

User InterfaceObjects Layer

Web Browser

JavaInterfaces

Application

Java ThinClient

SiebelDatabase

BusinessObjects Layer

Data ObjectsLayer

User InterfaceObjects Layer

Siebel

Applications

Client



Benefits of Thin Clients

Benefits of Thin Clients 1

Siebel thin clients are true thin clients—no application logic is stored on the client machines. Siebel thin clients provide numerous benefits to the deployment of your Siebel applications:

� Central management and universal support mean reduced IT and deployment costs while implementing Siebel on a heterogeneous assortment of desktop computers—no complex installation, changes, or upgrades are required on client machines

� A look-and-feel shared with the traditional Siebel dedicated and mobile clients

� Reduced hard disk, CPU, and memory requirements on client machines, as only the user interface is stored on the client machine

� Support for user hoteling—the ability of users to store preferences on the server and access them from any client machine—in Siebel Thin Client for Windows

� Single configuration environment using Siebel Tools



Application Object Manager and Thin Clients

Application Object Manager and Thin Clients 1

The Application Object Manager hosts the Business Objects layer and Data Objects layer of the Siebel architecture. The thin clients host the Siebel applications user interface layer.

By hosting Siebel Business Objects and the business logic processing on the server, Application Object Manager supports:

� Deployment of Siebel Thin Client for Windows

� Siebel HTML Thin Client

� Siebel Java Thin Client

� Real-time integration with external applications through the Siebel Object Interface, at the Application Object Manager level

The Application Object Manager communicates with thin clients using the TCP/IP protocol. Communication between the clients and the Application Object Manager can be compressed and encrypted. An independent session is established to serve incoming connect requests from each client. Subsequent requests from clients are directed to the same Application Object Manager tasks until the sessions are terminated.

The Siebel repository file (.srf) is installed as part of each Siebel Server installation. Any changes to the application’s repository file must be applied to the appropriate Siebel Server installations that serve the modified application to the thin clients. When they reconnect to the Application Object Manager, thin client users automatically retrieve the new Siebel application configuration. User preferences set and saved by thin clients will be saved on the server.

For more information about Siebel thin clients, see Chapter 8, “Thin Client for Windows and Java Thin Client Overview,” and Chapter 14, “Siebel HTML Thin Client Overview.”



Choosing a Thin Client

Choosing a Thin Client 1

Table 1-1 compares the features for each of Siebel thin clients.

The Main Differences Between the Thin Clients 1

Siebel Thin Client for Windows and Siebel Java Thin Client are deployment platforms that customers should choose if they want to deploy a thin client while leveraging the look-and-feel of their existing Siebel eBusiness Applications.

The Siebel HTML Thin Client is the correct choice for those who want to customize their Siebel .COM Applications and their other Siebel eBusiness Applications.

Table 1-1. Deciding Which Siebel Thin Client Meets Your Needs

Thin Client Feature Windows Java HTML

High responsiveness � �

Complete Siebel look-and-feel � �

Windows on user’s desktop � �

Non-Windows platforms � �

Tight integration with the look-and-feel of Web site �

Low bandwidth connection �

User behind restrictive firewall � �



Choosing a Thin Client


Introduction to Configuration Files 2


Sample Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Example Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Editing Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

How to Edit Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6


Introduction to Configuration Files

About This Chapter

About This Chapter 2

This chapter provides general information about configuration files (and an example of a configuration file) and how to edit them. Many configuration files are required by the different Siebel clients.

Other sources of information for configuration files and configuration parameters include:

� Appendix A, “Index of Configuration Parameters,” which provides an alphabetical list of the configuration parameters, along with cross-references to the description for each, documented in this guide.

� “Editing Mobile Client Configuration Parameters,” in Chapter 5, which addresses configuration parameters for the mobile client.

� Appendix B, “Siebel.cfg Configuration Parameters,” which addresses siebel.cfg configuration parameters.

� The Siebel Server Installation Guide, which addresses configuration parameters for the .COM applications.



Sample Configuration File

Sample Configuration File 2

Siebel clients use configuration files to hold the information that tells the clients how to function at startup.

Because all the configuration files are plain-text files, you can edit them manually using any text editor instead of running the Installer again. You must also copy and edit these files for each new application you create.

Example Configuration File 2

Below is an example of the uagent.cfg configuration file from the Siebel Server for Call Center. On the left are the parameters, and on the right are sample values. Edit the values according to how you want your system to function. See “How to Edit Configuration Files” on page 2-6 before you attempt to edit any configuration files.

[Siebel]RepositoryFile = siebel.srfApplicationName = Siebel Universal AgentApplicationTitle = Siebel Call CenterApplicationSplashText = Call CenterComponentName = Siebel Call Center ClientShowMessageBar = TRUEDataSource = LocalClientRootDir = c:\2456\SeaTempDir = c:\2456\Sea\tempJTCHelpURL = %JTC_HELP_URL%Version = 100ClientFileServSupport = TRUEMultiCurrency = TRUEEnableScripting = TRUEScriptingDLL = sscfbas.dllEnableOLEAutomation = TRUEOLEAutomationDLL = sscfole.dllEnableCORBA = FALSECORBADLL = sscfcorb.dllCorrespODBCDataSource = SEA MMerge c:/2456/SeaReportsODBCDataSource = CHANGE_MEServerDbODBCDataSource = SEA Oracle80 c:/2456/SeaDockRepositoryName = Siebel RepositoryHoldExportOdbcConnection = FALSELargeFont = MS Sans Serif-10-normalSmallFont = MS Sans Serif-8-normalDefaultChartFont = Arial-10-normalNavBarItemFont = MS Sans Serif-8-boldNavBarSelectFont = MS Sans Serif-8-bold




NavBarTitleFont = Arial Black-10-normalAppletTitleFont = Arial-10-boldSrvrUpdateInterval = 60SrvrTimeOutInterval = 600AccessDir = CHANGE_MELocalDbODBCDataSource = SEA Local Db c:/2456/Sea

[DataSources]Local = LocalSample = SampleServer = ServerGateway = GatewayDataMart = DataMart

[Local]Docked = FALSEConnectString = c:\2456\Sea\local\sse_data.dbf -Q -mTableOwner = SIEBELDockedDBFilename = CHANGE_MEDLL = SSCDW55.DLLSqlStyle = WatcomMaxCachedCursors = 16MaxCachedDataSets = 16ReverseFillThreshold = 100CaseInsensitive = FALSEInsensitivityFactor = 2DockTxnsPerCommit = 500DockConnString = laptop1SearchStyle = FulcrumSearchConnectString = SEA Search c:/2456/SeaSearchDefName = Fulcrum SampleOLAPServer=ichan2456

[Sample]Docked = FALSEConnectString = c:\2456\Sea\sample\sse_samp.dbf -Q -mTableOwner = SIEBELDockedDBFilename = CHANGE_MEDLL = SSCDW55.DLLSqlStyle = WatcomMaxCachedCursors = 16MaxCachedDataSets = 16ReverseFillThreshold = 100CaseInsensitive = TRUEInsensitivityFactor = 2SearchStyle = FulcrumSearchConnectString = SEA Search c:/2456/SeaSearchDefName = Fulcrum SampleOLAPServer = olap




[Server]Docked = TRUEConnectString = siebel_dbTableOwner = siebelDLL = sscdo80.dllSqlStyle = OracleMaxCachedCursors = 16MaxCachedDataSets = 16ReverseFillThreshold = 100CaseInsensitive = FALSEInsensitivityFactor = 2FileSystem = c:\filesSearchStyle = FulcrumSearchConnectString = SEA Search c:/2456/SeaSearchDefName = Fulcrum SampleGatewayAddress = gtwayEnterpriseServer = siebelRequestComponent = SRMSynchRequestServer = rqstsrvrOLAPServer = olap

[DataMart]Docked = TRUEConnectString = CHANGE_METableOwner = CHANGE_MEDLL = sscdo80.dllSqlStyle = OracleMaxCachedCursors = 16MaxCachedDataSets = 16ReverseFillThreshold = 100CaseInsensitive = FALSEInsensitivityFactor = 2FileSystem = c:\filesSearchStyle = FulcrumSearchConnectString = SEA Search c:/2456/SeaSearchDefName = Fulcrum SampleOLAPServer = olap

[Gateway]ConnectString = gtwayPrimaryEnterprise = siebelDLL = sscda10.dllHidden = TRUECaseInsensitive = FALSEInsensitivityFactor = 0

[Preload]View1 = Opportunity List ViewView2 = All Service Request List View



Editing Configuration Files

[CTI]Enable = FALSEDeviceDriver = CSTGenesysDriver

[ProductConfigurator]ConfiguratorDLLName = SSCSBC.DLL

[DataCleansing]Enable = FALSEType = IdCentricDir = CHANGE_ME

[DeDuplication]Enable = FALSEType = IdCentricDir = CHANGE_ME[Internet]TableOwner = siebelSqlStyle = Oracle

Editing Configuration Files 2

There are many reasons why you might edit configuration files and you will likely want to do so at some point after the installation; for example, you may want to edit configuration files to enable or disable certain functionality, fonts, and features.

How to Edit Configuration Files 2

1 Create a backup copy of the default .cfg file for which you want to edit parameter values, and save that file as a backup file.

2 Using any text editor, such as Notepad, open the default version of the .cfg file.

3 Edit the parameter values to obtain the desired application behavior.

4 Run a test using the .cfg file that you edited.

5 If there is an error in your test, resave the backup file as the default .cfg file.

6 If no error occurs, then use the modified .cfg file.


D e d i c a t e d a n d M o b i l e C l i e n t sI n s t a l l a t i o n a n d C o n f i g u r a t i o n Part 2

Chapter 3. Dedicated and Mobile Clients Overview

Chapter 4. Installing the Dedicated and Mobile Clients

Chapter 5. Configuring the Dedicated and Mobile Clients

Chapter 6. Optimizing Dedicated and Mobile Client Performance

Chapter 7. Troubleshooting the Dedicated Client


Dedicated and Mobile Clients Overview 3

What Are the Siebel Dedicated and Mobile Clients? . . . . . . . . . . . . . . . . 3-2

More Information About the Mobile Client and Siebel Remote . . . . . . 3-2

Comparing the Siebel Dedicated and Mobile Clients . . . . . . . . . . . . . . . . 3-5


Dedicated and Mobile Clients Overview

What Are the Siebel Dedicated and Mobile Clients?

What Are the Siebel Dedicated and Mobile Clients? 3

The Siebel dedicated client and mobile client allow a user to access information managed by Siebel eBusiness Applications. They run on a Windows-based PC and contain both user interface and business logic.

There are two types of traditional client/server Siebel clients:

� Dedicated Client. The dedicated client connects directly to the Siebel Database Server and the Siebel File System to perform its functions. The dedicated client may also interact with Enterprise Server components for additional functionality. A dedicated client does not store any Siebel data locally.

� Mobile Client. The mobile client, typically a laptop computer used by a field sales or service representative, is designed to operate without a real-time connection to any of the servers. See “More Information About the Mobile Client and Siebel Remote” to learn more about the mobile client.

More Information About the Mobile Client and Siebel Remote 3

The mobile client is designed to operate without a real-time connection to any server. This is achieved by downloading a portion of the Siebel database and the Siebel File System to the laptop so that users can access the data locally without being connected directly to the Database Server, Siebel Server, or File System. The mobile client then periodically accesses the Siebel Server through a dial-up, WAN, or LAN connection to synchronize data changes with the Database Server and File System.

See the Siebel Remote Administration chapter in the Siebel Remote and Replication Manager Administration Guide for complete setup instructions for Siebel Remote.




Local Database and File SystemMobile clients use a local database to store data for user access. The local database contains Siebel applications tables that store user data.

The local database also contains a local transaction log to store transactions created by the mobile user. Siebel Remote forwards these transactions to the Siebel Remote server when the client synchronizes. Do not directly modify the local transaction log under any circumstances. The Siebel Remote synchronization client automatically purges the local transaction log table once the changes have been merged onto the server database.

Mobile clients also use a local Siebel File System to store files from the Siebel File System, which are available when the mobile user disconnects from the Siebel Server. Users can request specific files to download to their local File System during synchronization. The Siebel administrator can also specify files that should be published or broadcast to all mobile users. Files added to the local File System by the mobile user will be uploaded to the Siebel File System at the next synchronization session.

Siebel Remote Client SoftwareThe Siebel Remote client software runs on the Siebel mobile client and manages the synchronization process between the mobile client and the Siebel Remote server.

Mobile users can start the Siebel Remote client in two ways:

� Background synchronization

While the Siebel client is running, mobile users can choose File � Synchronize from the Siebel menu bar. This launches the Siebel Remote client as a background process; thus, work can continue within Siebel applications or in other Windows applications during the synchronization process.

� Stand-alone synchronization

Mobile users can launch Siebel Remote in stand-alone synchronization mode using the Siebel Remote icon or a third-party scheduling program. During stand-alone synchronization, Siebel Remote runs separately from the Siebel client, and does not require it to be running in order to synchronize the mobile database. Mobile users can thus work locally while performing a stand-alone synchronization.




The Siebel Remote client uses the TCP/IP protocol to communicate with the Siebel Remote server over a modem using dial-up networking, a local area network, a wide area network, or a public network such as the Internet.

The Siebel Remote client does the following to manage the synchronization process:

1 Connects to the Siebel Remote server, which starts a synchronization manager for the mobile client.

NOTE: The synchronization manager notifies the mobile user and initializes the local database if the Siebel administrator performed a database extract for the mobile client or if the local database does not exist.

2 Extracts transactions from the local database.

3 Sends and receives transaction files to and from Synchronization Manager.

4 Sends and retrieves file attachments.

5 Applies transaction files from the Siebel Remote server to the local database.



Comparing the Siebel Dedicated and Mobile Clients

Comparing the Siebel Dedicated and Mobile Clients 3

Figure 3-1 shows the two types of traditional Siebel clients working in the Siebel Server architecture.

Figure 3-1. Siebel Dedicated and Mobile Clients

Siebel DatabaseServer

Note that eachmobile client has alocal database.

Siebel FileSystem

GatewayServer

ServerManager

SiebelServer

SiebelServer

SiebelServer

Siebel Enterprise Server

MobileClient

MobileClient

MobileClient

DedicatedClient

DedicatedClient

DedicatedClient

Administrator clients are the only ones thatconnect directly through the GatewayServer. Non-administrator clients connectdirectly through the database server.

Each mobile clientconnects directlyto the SiebelServer from whichit was lastextracted.



Comparing the Siebel Dedicated and Mobile Clients


Installing the Dedicated and Mobile Clients 4


Preinstallation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Choosing a Directory Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Verifying Siebel Client Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Installing Database Connectivity Software . . . . . . . . . . . . . . . . . . . . 4-3

Installing Included Third-Party Software . . . . . . . . . . . . . . . . . . . . . 4-4

Installing Fulcrum SearchServer Desktop . . . . . . . . . . . . . . . . . . . . . 4-5

Installing the Siebel Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Post-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

Verifying Successful Installation . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

Verifying the Siebel Client Directory Structure . . . . . . . . . . . . . . . . 4-14

Verifying the Siebel Client Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-16

Verifying Siebel Client ODBC Data Sources . . . . . . . . . . . . . . . . . . . . . . .4-17

Removing the Dedicated Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18


Installing the Dedicated and Mobile Clients

About This Chapter


Siebel supports dedicated and mobile client installations on the PC hardware and operating systems detailed in the Siebel Release Notes.

Use the installation process described in this chapter—a standard client installation—to install the Siebel client for use in a client/server environment, for administrative access to the application, and for demonstration and configuration purposes. This installation is based on default installation parameters set by Siebel Systems.

When application configuration and testing are complete, use the Custom Client Installation Program to create a configured client installation to distribute to end users. The Custom Client Installation is explained in Step 4 on page 4-7.

Preinstallation Tasks 4

Perform the following tasks before running the standard client installation program:

� “Choosing a Directory Name” on page 4-3

� “Verifying Siebel Client Prerequisites” on page 4-3

� “Installing Database Connectivity Software” on page 4-3

� “Installing Included Third-Party Software” on page 4-4

� “Installing Fulcrum SearchServer Desktop” on page 4-5



Preinstallation Tasks

Choosing a Directory Name 4

By default, several Siebel installers assume an installation directory of c:\sea\client. You cannot install different Siebel components in the same directory. If you will install more than one component on the same machine, determine your directory-naming convention before beginning the installation process.

NOTE: It is recommended that you choose names that describe both the version number and the component being installed.

Verifying Siebel Client Prerequisites 4

Before beginning the client installation, be sure that you have completed preparation of the client PC, verified that your hardware meets the minimum configuration, and installed all required third-party software listed in the Siebel Release Notes.

Installing Database Connectivity Software 4

Dedicated client PCs must have vendor-specific database connectivity software installed. Refer to the Siebel Release Notes for the software and versions.

When you have installed your connectivity software, configure it as follows:

� For Oracle, enter the appropriate connect string using the Net 8 Easy Configuration utility. This connect string points to the server and database instance this client will use. This connect string should be recorded on the Deployment Planning Worksheet in the Siebel Server Installation Guide.

� For Microsoft SQL Server, install the ODBC driver version specified in the Siebel Release Notes. The client uses this driver, but will create its own ODBC data source during installation. This data source should be recorded on the Deployment Planning Worksheet in the Siebel Server Installation Guide.

� For IBM DB2, install the DB2 client software and configure it to connect to the database server that you have chosen to run the DB2 database. The connect string and tableowner information should be recorded on the Deployment Planning Worksheet.




Installing Included Third-Party Software 4

Your Siebel application requires some third-party software products (detailed in the Siebel Release Notes) for full functionality. These products are provided by Siebel through licensing arrangements with their respective vendors.

Complete the steps in “Installing Adobe Acrobat Reader” and “Installing Fulcrum SearchServer Desktop” on page 4-5 to install the provided third-party software that is required for full Siebel functionality:

� Adobe Acrobat Reader (required)

� Fulcrum SearchServer (this optional component is required only if you want full content search capabilities)

Installing Adobe Acrobat ReaderThe Siebel dedicated and mobile clients require Adobe Acrobat Reader for viewing documents in Portable Document Format (PDF) through the Siebel client; for example, Siebel Encyclopedia items, file attachments, and Siebel documentation provided on the Bookshelf for Siebel eBusiness Applications CD-ROM.

Complete the following steps to install Adobe Acrobat Reader on all end-user and administrator client PCs. You must install Adobe Acrobat Reader on each end-user and administrator client PC before running the Siebel client installation program.

To install Adobe Acrobat Reader on each Siebel client PC

1 Close any open Windows programs.

2 Insert the Siebel eBusiness Applications Client Programs CD-ROM into the CD-ROM drive on the Siebel administrator’s PC.

3 Using Windows Explorer, navigate to the \Thirdpty\enu\acrobat directory on the Siebel eBusiness Applications Client CD-ROM.

Caution: You must run this and other installation programs from the CD-ROM or a network drive mapped to a drive letter. If you attempt to install from an unmapped network drive, the installation program will be unable to locate files it needs to proceed and will fail.




4 Double-click the rs405eng.exe file to start the Acrobat installer.

5 Read and accept the terms and conditions.

By default, Adobe Acrobat Reader will be installed into C:\ProgramFiles\Adobe\Acrobat 4.0.

To install Adobe Acrobat Reader into a different directory, change the target directory location and click Install to continue.

6 The setup program will copy files to the PC’s hard disk and create an icon labeled Acrobat Reader 4.0 in the Adobe Acrobat 4 program group.

7 Click OK to complete the installation.

Installing Fulcrum SearchServer Desktop 4

If you will use Fulcrum SearchServer, Siebel recommends that you install it on the client PC prior to completing the Siebel client installation. See the installation chapter in the Siebel Search Guide for instructions on installing Fulcrum SearchServer.



Installing the Siebel Client

Installing the Siebel Client 4

The standard Siebel client installation program performs the following tasks:

� Checks the PC to verify whether required components have already been installed.

� Calls the Microsoft Data Access Components (MDAC) to install the Microsoft Access, Text, SQL Server ODBC drivers, and ADO providers for Siebel Marketing, as required.

� Creates all required ODBC data sources.

� Installs Siebel client software and enables the user to view the installation log file.

To complete the installation, refer to the Siebel Release Notes that accompanied your software. The “System Requirements and Supported Platforms” chapter in the Siebel Release Notes contains version numbers and other updated information.

NOTE: Do not attempt to perform a single client installation for use across multiple Siebel Enterprises. Although running the client with different .cfg files will allow it to work with multiple Enterprises for testing purposes, this can cause Siebel Anywhere failures. Files from different Enterprises in the client root directory will collide and Siebel Anywhere may behave erratically. The only solution to this issue is to perform a clean reinstallation.

To install the client software on dedicated and mobile client PCs

1 Using Windows Explorer, navigate to the \sea directory of the Siebel eBusiness Applications Client Programs CD-ROM.

2 Double-click setup.exe to start the installation program.

Caution: You must run this and other installation programs from the CD-ROM or a network drive mapped to a drive letter. If you attempt to install from an unmapped network drive, the installation program will be unable to locate files it needs to proceed and will fail.




3 In the Welcome dialog box, click Next.

4 In the Setup Type dialog box, select the type of Siebel installation to perform:

� Typical Setup. This setup option will install all Siebel components except the Packager Utility, Server Manager, Sagent Runtime, DataMart Administration, and SME Cache Generator. This option is recommended for most users.

� Compact Setup. This setup option will install all components except the Help Files, Packager Utility, and demonstration database. Select this option for end-user client PCs that will receive customized help text, that will not be used for packaging Siebel software for distribution to other PCs, and that will not be using Siebel Marketing.

� Custom Setup. This setup option lets you customize your installation by choosing components you wish to install. Each component is listed with the amount of disk space it requires. Click the Disk Space button to see the disk space available on the designated installation drive.

NOTE: You must use the Custom Setup option to install the Server Manager and the Packager Utility. This setup should be performed by the Siebel administrator so that the Siebel client can be installed on the rest of the non-administrator machines.

You must also use this option to install the Data Mart Administration, Sagent Runtime, and SME Cache Generator options for Siebel Marketing. See the Siebel Marketing Guide for more information on these options.

5 While still in the Setup Type dialog box, verify that the installation directory listed is correct.

The default directory for Siebel is c:\sea\client.

� Click Next to accept the default directory.

� Click Browse to select a different destination directory.

The directory pathname can be up to 18 characters long and must not include spaces or special characters. If you specify a directory other than c:\sea\client, make the appropriate substitutions throughout the remainder of this chapter.




6 In the Database Identification dialog box, enter the type of server database on which you are implementing your Siebel application and click Next.

7 In the Document Integrator dialog box, select the product suite that you want to use for document integration and click Next. The possible sections include:

� Microsoft Office

� Lotus SmartSuite

8 Complete the instructions in the Required Software Component dialog box.

� If your PC has the required versions of the ODBC Text and Access drivers (and the Microsoft SQL Server, if you are deploying on that database), this dialog box does not appear.

� If you have newer versions of the ODBC drivers installed, this dialog box will let you choose whether to install the older version of the ODBC drivers included with the Siebel eBusiness Applications software.

� If you have older versions of the ODBC drivers installed, you must install the versions provided with the Siebel eBusiness Applications to continue with the installation.

9 In the Server Locations dialog box, enter your Siebel Remote Server and File System connectivity information.

You must use the network name (machine name) of the server where the Siebel Remote Server is installed. For instance, a network name might be NTSRV1.

Siebel File System connectivity information can be either the UNC share name of the Siebel File System directory (for example, \\NTSRV1\siebfile), or a drive letter mapped to the Siebel File System directory (for example, K:\).

Caution: Do not install an older version of ODBC if you are using Windows 2000.





10 In the Database Identification dialog box, enter the following information:

� If you selected Oracle in the Server Database dialog box, specify your Database Alias and your Table Owner. Then click Next.

� If you selected Microsoft SQL Server in the Server Database dialog box, specify your Server Name and Database Name. Then click Next.

� If you selected IBM DB2 in the Server Database dialog box, specify your Database Alias, Table Owner, and SQL ID. Then click Next.

11 In the Enterprise Server Information dialog box, specify the Gateway Server Address and Enterprise Server to which this client will connect for administration.

The address specified for the Gateway Server will vary depending on whether your Siebel Servers are using Resonate Central Dispatch to support connection brokering:

� If you are using Resonate Central Dispatch, the Gateway Server address is the Gateway VIP (virtual IP address) of the machine on which the Gateway Server is installed.

� If you are not using Resonate Central Dispatch, enter either the network name or the IP address of the application server on which the Gateway Server is installed.

The Enterprise Server name is the name of the Enterprise Server under which the Siebel Servers that support this client’s server database were installed.

12 In the Server Request Information dialog box, enter the information that dedicated clients will use to invoke the Server Request Manager component for dynamic assignment and other interactive operations, and then click Next.

These settings are not applicable if you are not using the Request Manager component:

� The Request Component is the name of the Request Manager component. The default value of SRMSynch is correct for the server component definitions included in the default Siebel Server installation. Do not change this value unless you have created your own Request Manager configured component.

� If you are not using Resonate Central Dispatch, you must also specify the Request Server Name. This is the logical name of the Siebel Server operating the Request Manager component.



13 In the Analysis Proxy Server Setup dialog box, enter the machine name or IP address of the Siebel Server on which the Marketing Analysis Proxy Manager server component is operating, and then click Next.

This setting is used only for Siebel Marketing. See the Siebel Marketing Guide for more information. If you are not using Siebel Marketing, you do not need to enter anything in this dialog box.

14 In the Fulcrum Setup dialog box:

� If you are using Fulcrum, enter the following:

� Search Hostname

� Search Port Number

� Search Definition Name

for the server on which Fulcrum SearchServer is operating.

� If you are not using Fulcrum, accept the default parameters, and click Next.

15 In the Select Program Folder dialog box, enter the name of the program folder that will contain your Siebel icons in the Select Program Folder dialog box.

The default name is Siebel Client 6.0. You can use spaces and the backslash (\) in folder names to create a folder hierarchy.

16 When you click Next, the setup program will copy files to the local host machine’s hard disk.

A status bar in the Setup Status dialog box indicates the progress of the installation.

Caution: If you are deploying Windows NT 4.0 clients operating against an Oracle database, do not include parentheses in the labels of the Siebel icons if you modify them. Including parentheses will prevent the application from connecting to the Oracle database.



Post-Installation Tasks

17 Review the Event Log dialog box, and when you are finished, click Next.

This log provides details of the steps the installer completes during your Siebel client installation.

18 Review the Registry Log dialog box, and when you are finished, click Next.

This log provides details of the registry information the installer completes during your Siebel client installation.

19 Click Finish in the Setup Complete dialog box.

The Siebel client installation is now complete.

Post-Installation Tasks 4

Perform the following tasks after running the Siebel client installation program:

� “Verifying Successful Installation”

� “Verifying the Siebel Client Directory Structure” on page 4-14

� “Verifying the Siebel Client Icons” on page 4-16

� “Verifying Siebel Client ODBC Data Sources” on page 4-17

Verifying Successful Installation 4

Complete the following instructions to verify a successful Siebel client installation.

Starting Siebel Client Without Siebel VB or Siebel eScript LicensedThe default configuration (.cfg) files for the Siebel client have Siebel VB or Siebel eScript enabled by the parameter EnableScripting = TRUE. However, if you do not have Siebel VB or Siebel eScript licensed, the client will not start, returning an error message indicating that you must turn Siebel VB or Siebel eScript off before running the client.




To start Siebel Client without a licensed Siebel VB or eScript installation

� Set EnableScripting = FALSE in the .cfg file used by your Siebel client configuration. By default, this .cfg file resides in the C:\sea\client\bindirectory.

Logging On to the Demonstration DatabaseYou can verify whether the SQL Anywhere database is installed properly if you have installed the sample database using the Typical or Custom install option. This option is not available if you chose the Compact option during installation. Verify that you can log on to the sample database by clicking one of the Siebel Demo icons in the Siebel program group.

If you are unable to log on to the demonstration database, and see an error message such as Internal error with the connector DLL, it means that Siebel is unable to locate the SQL Anywhere database. Confirm that sse_samp.dbf is installed in the sample directory of your Siebel installation.

Several different Demo icons are provided—such as Sales Demo, Service Demo, and Call Center Demo—that will log you on to the database as several different users with different privileges.

To see all Siebel views

1 Choose File � Connect.

2 Specify SADMIN for the User Name and Password, and choose Sample from the Connect To picklist.

Logging on as SADMIN allows you to see all screens and views. Details on other logons included in the sample database can be found in the Siebel Release Notes.




Testing Siebel Correspondence FunctionalitySeveral components must be installed correctly for Siebel correspondence to function properly.

To test Siebel correspondence functionality

1 While connected to the sample database, click the New Correspondence toolbar button.

2 Pick a correspondence template and attach recipients.

3 View the correspondence.

If you are unable to view the correspondence, make sure that the ODBC data source called SEA MMerge C:/sea/client is correctly installed. See “Verifying Siebel Client ODBC Data Sources” on page 4-17 for more information.

NOTE: If you are running Microsoft Word 97 under Windows 95 or 98, you must complete the next set-up steps, “To enable Siebel Correspondence on Windows 95/98,” to configure your Siebel client system to display MS-DOS file extensions.

To enable Siebel Correspondence on Windows 95/98

1 Choose View � Options either from the Explorer menu or from My Computer.

2 Click the View tab.

3 Disable (uncheck) the check box labeled Hide MS–DOS file extensions for file types that are registered.




Verifying the Siebel Client Directory Structure 4

The Siebel installation program creates directories on each Siebel client. Use Windows Explorer to make sure that the following directory structure exists on the client’s hard disk:

seaclient

actuateafcbincache

binhelpidcentriclocal

filesinboxoutbox

localelogmsgtemplobjectspackager (if the Packager option was selected)

archivesinstall

reportsenu

samplefilesinboxlogoutboxsiimages

searchdataindexscripts

tempupgrade




sea. The top-level directory for Siebel installation. You can change the name during the installation process.

actuate. Contains all the Actuate-related files, for reports.

afc. Contains all the Actuate Foundation Class files.

bin. Contains all the Actuate binary files.

cache. Stores decompressed copies of file attachments for rapid access.

bin. Contains all binary files (*.exe, *.dll, *.cfg, *.ssf, *.pre), configuration files, and user preference files.

help. Stores online help files.

local. Where the local database is stored.

files. Where local file attachments are stored.

inbox. For Siebel Remote.

outbox. For Siebel Remote.

locale. Stores language-specific files.

log. Stores the log files from client operations, such as synchronization.

msgtempl. Stores message files used by the client.

objects. Contains compiled Siebel Repository (.SRF) files.

reports. Contains all report files.

enu. American English version of reports.

packager. Stores files used by the Siebel Packager Utility.

archives. Stores files used by the Siebel Packager Utility.

install. Stores files used by the Siebel Packager Utility.




sample. Where the sample database is installed.

files. Where the sample literature and correspondence files are installed.

inbox. Siebel Remote directories for the sample database.

log. Stores the log files from client operations.

outbox. Siebel Remote directories for the sample database.

si. Siebel eBriefings.

images. Contains image files used by Siebel eBriefings.

search. Contains sample search data and index for the Siebel Search module.

data. Contains the physical documents that the Siebel Search index references.

index. Contains the Siebel Search index used by Siebel to perform text retrieval on a local client.

scripts. Files used by the Siebel Search engine.

temp. Contains working report files.

upgrade. Will contain Siebel Anywhere upgrade files retrieved by the user.

Verifying the Siebel Client Icons 4

The Siebel installation creates icons in the Siebel program folder for the modules you have chosen to install. These icons include the following:

Siebel Packager. Use this icon if you chose the Packager option during a Custom install.

Siebel Call Center. Use this icon to open Siebel Universal Agent, a configuration combining Siebel Sales and Siebel Service applications into a single desktop. Use this icon to connect to the database server (for LAN-connected users), to an initialized local database, or to the Siebel demonstration database shipped with the product.




Siebel Call Center Demo. Use this icon to start the Siebel demonstration database, a configuration combining Siebel Sales and Siebel Service applications into a single desktop.

Siebel eBusiness Applications Help. Use this icon to access the Online Help.

Siebel Marketing. Use this icon to start Siebel Marketing.

Siebel Remote. Use this icon to start the stand-alone synchronization program.

Siebel Sales. Use this icon to start Siebel Sales. You can start in three modes:

� Connected to the database server (for LAN-connected users)

� Connected to an initialized local database (for mobile users)

� Connected to the Siebel demonstration database found in the standard Siebel application

Siebel Sales Demo. Use this icon to start the Siebel demonstration database for Siebel Sales.

Siebel Service. Use this icon to start Siebel Service when you are connected to the database server (for LAN-connected users), to an initialized local database (for mobile users), or to the Siebel demonstration database included with the standard Siebel product.

Siebel Service Demo. Use this icon to start the Siebel demonstration database for Siebel Service.

Verifying Siebel Client ODBC Data Sources 4

The Siebel client installer creates the ODBC data sources shown in Table 4-1 on page 4-18. By default, these are created as user data sources, which are only visible to the user account under which Siebel is installed.



Removing the Dedicated Client

The drive letter and directory at the end of each data source name will vary, depending on where you have chosen to install the Siebel client.

NOTE: If the database server is SQL Server, the client must be configured to use SQL Server authentication. All ODBC data sources and the SQL Server database should be configured using SQL Server authentication.

NOTE: It is necessary to use the ODBC drivers included on the Siebel Software CD. Do not use other drivers.

Removing the Dedicated Client 4

To remove the dedicated client, double-click Add/Remove Programs in the Control Panel, and follow the instructions for removing programs.

Table 4-1. Siebel Client ODBC Data Sources

Data Source Use

SEA Local Db C:/sea/client Connects to the local SQL Anywhere database.

SEA MMerge C:/sea/client Executes mail merge when generating correspondence.

SEA MSQL C:/sea/client For Microsoft installations only, connects to the Microsoft SQL Server database.

SEA Oracle C:/sea/client For Oracle installations only, connects to the Oracle database. This data source is used only by the Siebel Administrator when creating Siebel Anywhere upgrade kits.

SEA Search C:/sea/client ODBC data source used by Fulcrum SearchServer; created only if Fulcrum is installed. This data source is always created as a System DSN.

SEA Text C:/sea/client Used for reporting and data merge into the local SQL Anywhere database.

SEA DB2UDB C:/sea/client For IBM DB2 installations only, connects to the DB2 database.


Configuring the Dedicated and Mobile Clients 5

Logging Onto Your Siebel Application . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Establishing Network Connectivity to the Siebel Remote Server . . . . . . . 5-3

Setting User Synchronization Options . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Synchronization Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

Editing Mobile Client Configuration Parameters . . . . . . . . . . . . . . . . . . . 5-9

Setting Siebel Remote Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

Sample Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11

Editing the Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11

Recovering from Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-12

Setting Up the Siebel Remote Server . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13

Setting Up a New Siebel Remote User . . . . . . . . . . . . . . . . . . . . . . . . . 5-13

Creating a Mobile Client User Account . . . . . . . . . . . . . . . . . . . . . 5-13

Setting Up Mobile Client Hardware and Software . . . . . . . . . . . . . . 5-14

Establishing Autodial Preferences . . . . . . . . . . . . . . . . . . . . . . . . . 5-14

Registering a Mobile Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14

Running Database Extract for a Mobile Client . . . . . . . . . . . . . . . . . 5-15

Starting Siebel Remote Server Processes . . . . . . . . . . . . . . . . . . . . . 5-17

Starting the Transaction Processor . . . . . . . . . . . . . . . . . . . . . . . . . 5-18

Initializing a Mobile Client Local Database . . . . . . . . . . . . . . . . . . . 5-21

Synchronizing a Mobile Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22

How Changes Are Propagated to and from a Mobile Client Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22

Workflow for Changes Made by Mobile Users . . . . . . . . . . . . . . . . . 5-24

Synchronizing a Mobile Client Machine . . . . . . . . . . . . . . . . . . . . . . . . . .5-26

Editing Dedicated Client Configuration Files . . . . . . . . . . . . . . . . . . . . 5-26


Configuring the Dedicated and Mobile Clients

Logging Onto Your Siebel Application

Logging Onto Your Siebel Application 5

This section provides instructions for logging on to your Siebel application through the mobile or dedicated client.

To log on to your Siebel application and connect to the server database

1 Click one of the Siebel icons in the program group.

The user name and password must be those of an employee with a valid position and division defined in the Siebel database. Therefore, the first time you log on to the server database, you should use SADMIN as the user name and password. Then you can set up other users as employees with defined positions and responsibilities.

See the Siebel Applications Administration Guide for more information on setting up employees.

2 Specify the Server database and click OK.

The first time you log on to the Server database, the system prompts you to enter a license key number.

3 Enter your license key number in the dialog box that appears and click OK.

You can find the license key number that has been assigned to your site on the CD-ROM case.

NOTE: If you need to find the License Keys dialog box at a later time, choose Help � Technical Support and click the License Key button.

If you see a warning message dialog box, click OK, and then enter your license key number in the dialog box that appears.

NOTE: The first time that you launch Siebel as a remote user (specify a local database), it will automatically prompt you to connect to the Siebel server and retrieve a new local database. You must first extract this database. See the Siebel Remote and Replication Manager Administration Guide for more information on Siebel Remote and extracting local databases.



Establishing Network Connectivity to the Siebel Remote Server

Establishing Network Connectivity to the Siebel Remote Server 5

Siebel Remote clients must be able to connect to the Siebel Remote Server using TCP/IP. Verify that you have the correct hardware and software installed and are able to establish TCP/IP connectivity to the Siebel Remote Server.

If you wish to specify a Remote Server name in the setup.ini file, you must add the statement:

DockConnString = <Remote Sever Name>

to the Server Database Section of the setup.ini file. This statement is not added when the mobile client is created; you must edit the setup.ini file and add it manually if you wish to set up the client as a mobile client.

See the Siebel Remote and Replication Manager Administration Guide for more information.

Setting User Synchronization Options 5

This section describes the user synchronization options supported by Siebel Remote. The user accesses these options by selecting File � Synchronize from the Siebel client menu bar or by starting Siebel Remote in stand-alone mode. You can also click the Synchronization icon on the toolbar or double-click the Synchronization icon in the status bar. Synchronization occurs in the background, so you can continue to use Siebel applications during synchronization.

The stand-alone synchronization feature enables mobile users to synchronize their local databases with the server database without starting the Siebel application.



Setting User Synchronization Options

Synchronization Dialog Box 5

The Siebel Remote synchronization dialog box shown in Figure 5-1 contains a list of synchronization actions. Depending on your database options, the list may appear different from that in the example. For instance, if you do not have a local database, only the Connect to Server action will appear in the dialog box. Also, if you are running the stand-alone synchronizer in a looping mode, you will see a Sleep check box.

Synchronization ActionsThis section describes the available actions in the Siebel Remote synchronization dialog box as shown in Figure 5-1.

Extract Local Database Changes This action connects to the local database and extracts all the local transactions. This action happens automatically and cannot be disabled. In general, you should be able to ignore this action. This action displays the number of transactions that still need to be extracted.

Figure 5-1. Siebel Remote Synchronization Dialog Box




Connect to ServerThis action connects to the server, dials the phone number if necessary, and performs version, schema, and database initialization checking. If a dbinit or upgrade is pending, this action downloads and applies the pending dbinit or upgrade. This action must run successfully for the following three actions to be enabled.

Send Database Changes This action sends the local transactions to the server by sending one or more .dx files and associated attachment files to the server. This action displays the number of transactions that still need to be sent.

Retrieve Database Changes This action retrieves transactions from the server by retrieving one or more transaction files and associated attachment files from the server. These files are generated by the Transaction Router on the Siebel Remote server. This action displays the number of transactions that still need to be retrieved.

Retrieve Requested Files This action retrieves user-requested attachment files from the server. This action displays the number of files that still need to be retrieved.

Apply Database Changes This action applies database changes retrieved from the server to the local database. This action displays the number of transactions that still need to be applied.

Sleep This action sets the Siebel Remote client to sleep mode for a given number of seconds. This action displays the number of seconds of remaining sleep time.




Action ListYou can enable or disable each action by clicking the check box to the left of the action. Here are the possible check box states:

While an action is running, you can reset the action check box before the action has finished. If an action is running when you disable it, it will stop as soon as possible, and synchronization will continue with the next action.

The action status check boxes persist throughout the session. If you start synchronization with the Apply Database Changes option disabled, it will remain disabled throughout synchronization. If you restart Siebel applications, the action status check boxes return to their default state (enabled).

Item Status FieldThe word pausing appears in the Item Status field. Actions are made up of one or more items and may be hidden. The items (and sub-items) that appear in this field update the synchronization status to the user. Below the Item Status field is the item progress indicator, which indicates the remaining processing time for the item.

NOTE: The progress indicator provides reasonably accurate time estimates for long-running items (such as transferring files or merging transactions), but less accurate estimates for short-running items (such as connecting to the server or database).

Enabled. This action will run when its turn comes.

Disabled. This action will not run when its turn comes.

Not runnable. This action cannot run because an action it depends upon did not (or will not) run.

Finished. This action is finished.

Skipped. This action was skipped.




Skip File ButtonThe Skip File button is enabled whenever synchronization is performing an item (or sub-item) that is not critical to the current action. Retrieving an optional attachment file is the only action that can be skipped. Clicking this button skips the current item (or sub-item), and the current action continues. Double-clicking this button generates a prompt and skips all remaining optional items for this action.

Overall Transfer Progress PanelThis panel appears when communications with the server are active. The progress indicator displays the progress toward completing the actions that require the communications line.

Transfer Time Remaining FieldThis field contains the estimated time for completing the actions.

NOTE: The estimated time may be inaccurate when transferring large attachment files.

Start/Stop Command ButtonThe Start button starts synchronization. You can click this button even while synchronization is still performing hidden actions, such as connecting to the local database and extracting local database changes. When you click this button, the Synchronization dialog box is hidden (unless the SHIFT key is held down), and the label on the button changes to Stop.

Clicking the button again will stop synchronization if it is still running. When synchronization finishes, the button changes to OK. Clicking the button again hides the synchronization dialog box. If the Synchronization dialog box is hidden while synchronization is running, invoking synchronization will re-display the Synchronization dialog box. If synchronization is finished, invoking synchronization will reset the Synchronization dialog box and then display the dialog box.




Cancel/Hide ButtonIf synchronization has not started, clicking Cancel will close the Synchronization dialog box and abort synchronization. If synchronization has started, the label on this button will change to Hide, and clicking the button will hide the Synchronization dialog box.

Setup ButtonClicking the Setup button displays the Docking Preferences dialog box. The two File options control which files to synchronize. File options can be changed while synchronization is running.

Retrieve Published Files BoxWhen this check box is selected, synchronization will retrieve all newly published files.

Retrieve Auto Update Files BoxIf this check box is selected, synchronization will retrieve updates to local files marked for auto update. Auto update files, which are not local or have not been requested, will not be retrieved. The auto update flag is local to each node, so users can choose to update files automatically, without affecting other users. If you do not choose the Retrieve Auto Update Files option during this synchronization session, then synchronization will mark the files that need to be updated. Synchronization will then make all auto update files current during the next session when Retrieve Auto Update Files is enabled.

Changes to the dial-up networking options will take effect the next time synchronization makes a connection to the server. The Connection box allows users to select a dial-up networking connection. Leaving the box blank will cause synchronization to use an existing network connection.

Siebel has approximately 20 tables registered as file tables. These tables have 11 special FILE_ columns. Screens based on these tables use the special CSSFRFile and CSSBCFile business components. These business components handle drag-and-drop, and other mechanisms for adding and updating files. Changes to files cause transactions to flow through the system, and then synchronization monitors transactions on these tables.



Editing Mobile Client Configuration Parameters

When the mobile client receives a transaction on a file table, synchronization decides whether to retrieve the file locally. The default is not to bring down files to the mobile client unless the file is requested. File screens generally have a request field that users can select to bring down the file during the next docking session (if the Retrieve Requested Files action is enabled). Files are also sent upward by docking. If you change a file, you must send the new file up with the transaction to make the corporate database consistent. These files are stored near the corporate database on a file server. Files are named carefully to avoid conflicts should two users attempt to modify a file at the same time.

Auto-Start Siebel Remote BoxIf this check box is selected, Siebel Remote will begin synchronization as soon as you invoke file synchronization. The Siebel Remote dialog box will not be displayed. If you want to display the dialog box throughout your session, press the SHIFT key when you click Start.

Editing Mobile Client Configuration Parameters 5

The Siebel Remote client reads configuration parameters in the Siebel configuration file, siebel.cfg, to specify the location of the Siebel Server directories, Siebel File Server directories, and the Siebel database installation. Before using Siebel Remote, you must set the values for the configuration parameters.

Setting Siebel Remote Preferences 5

The Siebel installation program creates a siebel.cfg file in the client bin directory with default values for each of these configuration parameters.

The configuration parameters that Siebel Remote uses are:

� ClientRootDir. Name of the Siebel client installation directory.

� DockConnString. The name of the Siebel Server to which you connect for synchronization. This parameter has the following format:

siebel server name:network protocol:sync port#:service:encryption

where




� siebel server name = the name of the computer where the Siebel Server is currently running.

� network protocol = the name of the networking protocol to use. TCP/IP is the only valid value and is the default value.

� sync port # = the TCP/IP port number dedicated to the Synchronization Manager. The default value is 40400.

NOTE: You can use the Siebel Server Administration screens to override the default value by specifying a value for the SeblMgr component’s SyncPort parameter and restarting the Siebel Server. You can also specify this port number as a command line option when starting the Siebel Server.

� service = the TCP/IP service you are requesting. For docking, it should always be set to the default DOCK.

� encryption = the encryption package you are using. The encryption facility must match the type used by the server. Currently, the only supported encryption facility is Mscrypto. The default is NONE.

Examples of valid values are:

SIEBAPP1:TCP-IP:40400

SIEBAPP1::9000

SIEBAPP1

� DockRepositoryName. Name of the Siebel repository that you are currently using. This parameter must have the same value as the Siebel Server repository.

NOTE: Make sure that you set the value of Siebel_Repository to the name of the repository that you are currently using.

� TableOwner. Name of the database account on the local database where the Siebel schema is installed. Default is SIEBEL. To initialize a mobile client database, this parameter must be set to SIEBEL.




� FileSystem. Name of the directory on the mobile client where attachment files reside. To use alternative file systems, use a comma-separated list of file system directories. An example is:

D:\files,\\bstevens\files

In this example, D:\files is a directory on a CD-ROM, and \\bstevens\files is a directory on the mobile client. In this example, the client will search both directories when files are requested.

� DockTxnsPerCommit. Number of transactions that Siebel Remote applies to the local database before performing a commit. You should set this configuration parameter to a value that satisfies the needs at your site. The default is 500.

� Single user mobile clients. If a user uses the Siebel client application to dock, set the DockTxnsPerCommit to a high value. Presumably, the database is not used by another user; while not committing, merged transactions will not lock out other users. This will enhance the performance of Siebel Remote.

� Stand-alone synchronizer. If a user uses the stand-alone synchronizer, set the DockTxnsPerCommit to a high value only if the program will be the only active user on the database. If the program will be applying transactions while other users are using the database, then set a low value to prevent locking out other users while merging transactions.

Committing often will affect the performance of other users. Set the DockTxnsPerCommit parameter to any desired value starting with 10 transactions per commit.

Sample Configuration File 5

To view a sample configuration file, see Chapter 2, “Introduction to Configuration Files.”

Editing the Configuration File 5

For an introduction to editing configuration files, see Chapter 2, “Introduction to Configuration Files.” Appendix B, “Siebel.cfg Configuration Parameters,” provides a description of the parameters included in the siebel.cfg file.




Recovering from Failures 5

Siebel Remote is designed to minimize the impact of a software, communications, or hardware failure. This section describes the most likely failures and how to recover from them.

Siebel Remote Transmission FailureMobile clients may experience occasional transmission failures. These failures may be caused by noise on the telephone line. If an error is detected, Siebel Remote automatically retransmits the files until the synchronization is successful.

Siebel Client Database FailureIf the client machine loses power during a merger process, then the SQL Anywhere database may be corrupted. To avoid this, make sure that the client machine has sufficient power before synchronization.

If a client database becomes unusable because of a media failure or other event, you must refresh the client database. This requires that you run Database Extract for the client.

For more information about the Database Extract process, see the Siebel Remote and Replication Manager Administration Guide.

NOTE: Depending on the kind of failure, database changes and file attachments that were awaiting upload during the next synchronization session may also be lost. In this case, the user must re-enter them.



Setting Up the Siebel Remote Server

Setting Up the Siebel Remote Server 5

The Siebel Remote server runs the Siebel Remote components and manages synchronization sessions with mobile clients. The Siebel Remote server provides an interim storage area for data required to synchronize mobile databases with the Siebel database server. See the Siebel Remote and Replication Manager Administration Guide for information about setting up the Siebel Remote server.

Setting Up a New Siebel Remote User 5

Setting up a mobile client involves certain tasks for both the Siebel Remote server and the mobile client. The system administrator must repeat each of these steps for each mobile client:

� Create a mobile client user account

� Set up mobile client hardware and software

� Establish autodial preferences

� Set synchronization preferences

� Register a mobile client

� Run Database Extract for a mobile client

� Start the Siebel Remote server processes

� Initialize a mobile client local database

NOTE: See the Siebel Server Administration Guide for advanced topics; for example, security and authentication, and conflict detection and resolution.

Creating a Mobile Client User Account 5

Use the Mobile Clients view in the Siebel Remote Administration screen to set the synchronization password for each mobile user. See the Siebel Remote and Replication Manager Administration Guide for more information.



Setting Up a New Siebel Remote User

Setting Up Mobile Client Hardware and Software 5

Installing the necessary hardware and software on the mobile client may include configuring users, setting preferences, and installing disk drives, memory cards, and operating system software. For information about supported software and versions, see the Siebel Release Notes.

Establishing Autodial Preferences 5

A mobile client user using Microsoft Dial-up Networking can configure Siebel Remote to automatically establish a connection with the Siebel Remote server when the user initiates a synchronization session.

To establish autodial preferences

1 Choose File � Synchronize.

2 Click Setup in the Synchronize dialog box to toggle the autodial feature and define its parameters.

Registering a Mobile Client 5

This section describes how to register a mobile client.

To register a new mobile client

1 Log on to your Siebel application using an account with access to the System Administration screen.

2 Choose Screens � Siebel Remote Administration � Mobile Clients.

3 Enter the user name in the Mobile Client field (required).

The mobile client name must be entered in uppercase letters and have a maximum of eight characters. It cannot include spaces, periods, or other invalid characters for a DOS filename. The mobile client name can contain only single-byte, alphanumeric characters, and the _ and - characters.

Siebel Remote uses the mobile client name to create inbox and outbox directories on the Siebel Server. You should use the mobile client user login name (see next step) as the mobile client name.




4 Enter the user name in the User Login Name field (required).

This is the login name of the mobile client. It will be used to access the local database during initialization and synchronization.

5 Select a value from the Routing Group field (required).

This is the routing group to which the mobile client belongs. For information on configuring routing groups, see the Siebel Remote and Replication Manager Administration Guide.

NOTE: The remaining fields are optional.

Running Database Extract for a Mobile Client 5

The Database Extract component creates a database snapshot file and retrieves data visible to a specific mobile client from the server database. The file contains the data necessary to initialize the user’s local database.

Prior to running Database Extract for a client, you must ensure that your organization’s reporting hierarchies are updated.

To verify that your clients are listed in the Position View

1 Choose Application Administration � Positions from the Screens menu.

2 Click the Positions applet, and choose Query � New Query from the menu.

3 Enter the last name for a client user in the Last Name field, and then choose Query � Execute Query from the menu.

If the user has a position assigned in the organization hierarchy, the record appears. The position information is used by the system’s routing rules, and may affect the outcome of Database Extract.




To Run Database Extract

1 Start Siebel Server Manager.

To view the task indicating that Server Manager is running, complete these steps:

a Choose Server Administration � Servers � Server Tasks from the Screens menu.

b Click the Server Tasks applet. If there is a record with Server Manager in the Component field and Running in the Task State field, then Server Manager is already running.

2 Click New on the Server Tasks applet again.

A blank server task record appears.

3 Click the drop-down arrow in the Component field, and select Database Extract from the Pick Assigned Component dialog box.

4 Click Parameters, find the Client Name parameter, and change the Value field to the name of your client user.

The Client Name parameter is required to run Database Extract. The correct value corresponds to the name that appears in the Mobile Client field on the Mobile Clients view of the Siebel Remote Administration screen.

5 Close the Parameter Overrides dialog box.

6 Click Start.

The Task State changes to Starting up. When the Database Extract task is finished running, the Task State changes to Completed.

Sample Directory Tree After Running Database ExtractThe installation program places a directory called sample in the c:\siebel\docking directory. The Database Extract program replicates the sample directory and its subdirectories for each mobile client.




The following example shows a portion of the server directory tree after you run Database Extract for the mobile client called MThrelfall:

siebel

docking

sample

inbox

outbox

MThrelfall

inbox

outbox

Starting Siebel Remote Server Processes 5

This section describes each server component required to use Siebel Remote and provides instructions for starting each one. You must start these components before initializing the local database.

Starting the Synchronization ManagerThe Siebel Remote server starts a Synchronization Manager task for each incoming synchronization request from a mobile client. Each Synchronization Manager task services only one mobile client at any one time.

Before mobile users can connect to the Siebel Remote server for synchronization, the Synchronization Manager component must be enabled. Synchronization Manager tasks start automatically; you do not need to start tasks for this component manually.

For each request, the Synchronization Manager:

� Verifies the mobile client status

� Exchanges transaction files

� Transfers file attachments to and from the Siebel File Server




To enable the Synchronization Manager component

1 Choose Server Administration � Servers � Server Components from the Screens menu.

2 In the Assigned Components list applet, select the Synchronization Manager record.

3 If the Server Manager Task Status is not Running or Enabled, click Enable.

When the component starts, the value of the Component State field changes to Starting up. Once the component is started, the value of the Component State field changes to Enabled or Running.

Starting the Transaction Processor 5

You must run one transaction processor on the Siebel Remote server. Upon start-up, the transaction processor verifies that another transaction processor is not already running.

To enable and start up the Transaction Processor


2 In the Assigned Components list applet, select Transaction Processor.

3 Click Enable if the value of the Component field is not already Enabled.

4 The value of the Component State field changes to Enabled.

5 Click Startup.

When the Transaction Processor starts, the value of the Component State field changes to Starting up. Once the Transaction Processor is started and the task is completed, the value of the Component State field changes to Enabled or Running.

NOTE: The Transaction Processor must be enabled before you can start it.




Starting the Transaction RouterYou must run at least one transaction router on the Siebel Remote server.

To enable and start up a transaction router


2 In the Assigned Components list applet, select Transaction Router.


The value of the Component State field changes to Enabled.

4 Click Startup.

When Transaction Router starts, the value of the Component State field changes to Starting up. Once Transaction Router is started and the task is completed, the value of the Component State field changes to Enabled or Running.

NOTE: The transaction router must be enabled before you can start it.




Starting the Transaction MergerThe Transaction Merger component applies transactions that have been uploaded by Siebel Remote mobile users to the Siebel database server. At least one transaction merger must be running on the Siebel Remote server.

To start up a transaction merger


2 In the Assigned Components list applet, select Transaction Merger.


The value of the Component State field changes to Enabled.

4 Click Startup.

When Transaction Merger starts, the value of the Component State field changes to Starting Up. Once Transaction Merger is started and the task is complete, the value of the Component State field changes to Enabled or Running.

NOTE: The transaction merger must be enabled before you can start it.




Initializing a Mobile Client Local Database 5

The volume of information that must be downloaded from the Siebel Remote server to initialize a mobile client’s database is usually substantial. You should establish a LAN (rather than a modem or WAN) connection between the server and the mobile client for this initial process.

To initialize a mobile client’s local database using the GUI

1 From the mobile client, establish a connection between the Siebel Remote server and the client machine.

2 Choose Start � Programs � Siebel eBusiness Applications � Siebel Remote.

A warning dialog box appears stating that the local Siebel database could not be found. This is expected, as the local database has not yet been initialized.

3 Click Yes in the warning dialog box.

The Siebel Remote Parameters dialog box appears.

4 Enter the first and last name of the mobile client user in the Client Name field, and enter the user name in the User Name field.

5 Click Continue.

After the synchronization completes, the client machine is ready for use in the field. From time to time, the mobile user will need to resynchronize with the Siebel Remote Server. Instructions for this process are included in the next section, “Synchronizing a Mobile Client.”



Synchronizing a Mobile Client

Synchronizing a Mobile Client 5

This section explains the workflow for a synchronization session from both the server side and the client side and provides instructions for synchronizing a mobile client.

How Changes Are Propagated to and From a Mobile Client Machine 5

Between synchronization sessions, the Siebel Remote server prepares transactions applied to the database server by other users—mobile and stationary—and Siebel Server components then write the transactions to separate directories for each mobile user. These transactions, combined with updated, published, or requested marketing literature, correspondence templates, and other types of file attachments, are downloaded to the mobile client and uploaded to the server during the next synchronization session.

Workflow for Changes Made by Users Connected to a ServerThis section provides a description of each phase of the workflow, from the stage when a user who is connected directly to a server creates a new opportunity, until the time when the new opportunity appears on a mobile user’s machine.

This workflow description is built around the example of a telesales representative in the Call Center who is talking to potential customers who are responding to a new advertising campaign. The telesales person creates a new opportunity record for one of the more promising responses. Here are the workflow steps:

1 The new opportunity record is saved to the opportunities table in the Microsoft SQL Server database, and a record is saved to the master transaction log.

2 A Transaction Router task writes each transaction from the database server to transaction files in separate outbox directories for each mobile client.

The mobile client outbox directories are stored on the Siebel Remote server.

3 A mobile client user synchronizes the client machine.

See the next section, “Synchronizing a Mobile Client Machine” on page 5-26, for step-by-step synchronization instructions.

During the synchronization session, the following steps occur to record the new opportunity record:




a The Siebel Remote client on the laptop dials the modem to connect to the Siebel Remote server.

This can be handled by an existing modem or LAN connection.

b The Siebel Remote client connects to the Siebel Remote server.

c The Siebel Remote server starts the Synchronization Manager for the mobile client.

d The Synchronization Manager validates the mobile client’s node name against the list of valid mobile clients in the server database.

e The Transaction Processor scans the master transaction log on the database server and prepares the transaction log for the Transaction Router.

The transaction log contains a record for the new opportunity.

f The Siebel Remote client receives transaction files going to and from the Synchronization server, and retrieves file attachments.

g The client retrieves transaction files created by the Transaction Router from the client user’s outbox directory on the Siebel Remote server and stores the transaction files in the mobile user’s local inbox directory. The client also retrieves the user’s requested, published, or broadcasted file attachments from the Siebel File Server.

h The Transaction Router routes the transactions since the user’s last synchronization from the master transaction log to the user’s mobile client outbox directory on the Siebel Remote server.

i The new opportunity record is saved to the opportunities table in the user’s local copy of the database.

j The Siebel Remote client closes the connection with the Siebel Remote server.

k On the Siebel Remote server, the Synchronization Manager deletes all transaction files in the user’s outbox directory (on the server) that the mobile client successfully applied to the user’s local database.




l After disconnecting from the Siebel Remote server, the Siebel Remote client applies the incoming transaction files to the local database and applies retrieved file attachments to the local file system.

The mobile user can use the Siebel client while the Siebel Remote client applies the changes to the local database.

Workflow for Changes Made by Mobile Users 5

Mobile clients use a local database to store data for user access. The local database contains Siebel eBusiness Applications tables that store user data. The local database also contains a local transaction log to store transactions created by the mobile user. Siebel Remote forwards these transactions to the Siebel Remote server when the client synchronizes.

This section provides a description of each phase of the workflow, from the time when the mobile client user modifies the new opportunity until the time when the modifications appear to stationary users connected directly to the server. For this example, assume that a mobile client user is meeting with the potential new client, represented by the opportunity record entered by the telesales representative mentioned in the previous section.

1 As a result of the meeting, the mobile client user makes changes to the opportunity record.

2 The modified opportunity record is saved to the opportunities table in the local database server, and a transaction record is saved to the local transaction log.

3 The mobile client user synchronizes the laptop.

See the next section, “Synchronizing a Mobile Client Machine” on page 5-26, for step-by-step synchronization instructions.

Caution: Users should never directly modify the local transaction log. The Siebel Remote synchronization client automatically purges the local transaction log table.




During the synchronization session, the following steps occur to record the changes to the opportunity record:

a Siebel Remote dials the modem to connect to the Siebel Remote server.

This can be handled by an existing modem or LAN connection.

b The Siebel Remote client connects to the Siebel Remote server.

c The Siebel Remote server starts the Synchronization Manager for the mobile client user.

d The Synchronization Manager validates the mobile client user’s node name against the list of valid mobile clients in the server database.

e The Siebel Remote client extracts all pending transactions from the local transaction log into transaction files and then sends the transaction files to the mobile client user’s inbox directory on the Siebel Remote server.

f The Transaction Merger task merges the incoming transaction files, including the mobile client user’s change to the opportunity record, to the database server and Siebel File Server.

g Siebel Remote closes the connection with the Siebel Remote server.



Editing Dedicated Client Configuration Files

Synchronizing a Mobile Client Machine 5

Mobile client users must synchronize periodically to see possible updates to the store of documentation, marketing literature, and sales brochures in the company’s online warehouse.

To synchronize

1 Start Siebel Sales in the Siebel program group on the mobile client machine.

2 Choose File Synchronize from the menu.

The Synchronization dialog box appears. Choose the synchronization options, as discussed in, “Setting User Synchronization Options” on page 5-3.

3 Click Synchronize.

Editing Dedicated Client Configuration Files 5

For more information about editing client configuration files, see Chapter 2, “Introduction to Configuration Files,” which contains a sample configuration file and general instructions for editing configuration files.

For an alphabetical list of client configuration parameters documented in this guide, see Appendix A, “Index of Configuration Parameters.” For a list of generic configuration file parameters, see Appendix B, “Siebel.cfg Configuration Parameters.”


Optimizing Dedicated and Mobile ClientPerformance 6

Configuring Cursor Close . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Calculating Cursor Configuration Parameter Values . . . . . . . . . . . . . . 6-3

Setting Cursor Configuration Parameter Values . . . . . . . . . . . . . . . . . 6-4

Configuring Active Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7

Siebel Docking Transaction Logging at Runtime . . . . . . . . . . . . . . . . . . . 6-7

Configuring Antivirus Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8

Server-Side Performance Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8


Optimizing Dedicated and Mobile Client Performance

Configuring Cursor Close

Configuring Cursor Close 6

Cursor close enables you to tune system resource utilization by Siebel clients in an OS/390 environment by setting cursor configuration parameters. In order to use cursor close, you must be running your Siebel application on an IBM DB2/390 database server.

Due to virtual memory constraints in the OS/390 environment, DB2/390 limits the number of concurrent active threads. Siebel clients must obtain a DB2 active thread to perform database operations. Siebel applications use a database facility, called a cursor, to hold information returned from the database. While a cursor remains in use, the DB2 active thread is marked busy, even if the user is not performing work within DB2/390 or on the user’s workstation.

To use cursor close, set cursor configuration parameters to specify the number of database rows a Siebel client cursor may return from a user-entered QBE query (or a Siebel operation which generates a SQL query). The number of rows is directly related to the length of time a Siebel client occupies a DB2 active thread. The cursor configuration parameters, MaxCursorSize and PreFetchSize, are specified in the Siebel configuration files (.cfg). For descriptions of these parameters, see Table B-3 on page B-8.

The cursor configuration parameters are set at startup for Siebel dedicated and mobile clients, and at the Siebel Object Manager for Siebel thin client users. You should work with your database administrator to specify different values for these parameters as required by different user classes to provide effective application usability and maximize scalability for all client users.

Use the guidelines in this section to achieve the best balance between system resource utilization, user responsiveness, and productivity.




Calculating Cursor Configuration Parameter Values 6

You should calculate cursor configuration parameter values to limit database rows that will be returned in order for the users to be productive and avoid retrieving unnecessary rows. Setting a high value will seriously impact the user response time while reducing system scalability and consuming excess system and network resources.

The cursor configuration parameters must be set to identical values. Values should be rounded up to a multiple of 16 and must always be equal to or greater than 32, except when turned off by setting the value to -1. A value of 32 generally enables users to scroll through two complete applet views without a re-query.

Set the values of cursor configuration parameters based on user classes. Table 6-1 lists the user classes and recommended cursor configuration parameter values for each class.

Table 6-1. User Classes

User Class Description

Recommended Cursor Configuration Parameter Values

Siebel administrator

Accesses the system to perform system updates and may need to access large amounts of data.

-1

Siebel application developers

Performs development and customization of the Siebel application by running Siebel Tools against the Siebel repository on DB2.

-1

Special Sporadically submits queries or execute operations returning a large number of rows. Examples include:

� No re-query formulation is available to access the next set of data.

� Operation requires the complete result set, such as a client Export to Excel.

� Data returned must be internally consistent. When a re-query is issued, the returned data set may be changed because of other database activity.

-1

Typical Majority of users. Examples include call center agents and sales representatives.

48




Setting Cursor Configuration Parameter Values 6

The cursor configuration parameters, MaxCursorSize and PreFetchSize, are specified in the .cfg file for each:

� Siebel dedicated client

� Mobile client when connected to the server database

� Instance of the Siebel Object Manager processing Siebel thin clients

NOTE: Some Siebel Server programs, such as Incentive Compensation and Report Server, use a Siebel Object Manager (SOM) instance for a subset of their operations. Anomalous behavior will occur if cursor configuration parameters are set for a SOM used by these Siebel Server programs.

Setting Cursor Configuration Parameter Values for Dedicated ClientsDetermine the standard cursor configuration value for typical users. Identify any subsets of typical users who would benefit from a different cursor configuration parameter setting. Update the .cfg files for all typical users and each typical user subset with the appropriate cursor configuration parameter values. For information on updating configuration files, see “Editing Configuration Files” on page 2-6.

NOTE: If usage pattern averages are not available, you should set the Typical standard cursor configuration value to 48 for dedicated clients on a high speed LAN/WAN.

Identify special users and the standard cursor configuration parameter value for their normal, limited query operations. Create the two logon procedures, Typical and Special.

For Siebel administrators and Siebel application developers, turn off the cursor configuration parameters by setting them to -1 in their .cfg files.




Setting Cursor Configuration Parameter Values for Mobile ClientsDetermine the cursor configuration parameter values based on the usage and network access of the mobile client. For mobile users that:

� Exclusively use the local Siebel database and update using synchronization, do not use cursor configuration parameters in the [Local] section of their .cfg file.

� Access both their local Siebel database and connect to the server database, use different cursor configuration values in the [Server] section of their .cfg file.

� Connect primarily over a low-speed WAN to the database server (any network operating at less than 256Kb/sec), use a cursor configuration value of 32.

NOTE: Special users that are also mobile users would be the exception to this guideline, but this combination should be rare.

� Connect over a high-speed LAN/WAN to the server database, use the same cursor configuration parameter values as those for the dedicated client users.

Setting Cursor Configuration Parameter Values for Thin ClientsA Siebel Object Manager (SOM) instance is a proxy for all thin client users connecting to the Siebel application and server database through that instance. The cursor configuration parameters, MaxCursorSize and PreFetchSize, are specified in the SOM [Server] .cfg file for each SOM instance. The value set for these parameters will apply to every thin client user accessing the application through the same SOM instance. Therefore, you should set up different SOM instances based on the different classes of thin client users.

For example, an installation might have three SOMs:

� Typical thin client users

� Thin client users that need a higher cursor configuration parameter value

� Special users




To set the cursor configuration parameter values for thin clients

1 Copy a Siebel .cfg client configuration file (siebel.cfg or uagent.cfg) and rename it.

2 Set the parameters MaxCursorSize and PreFetchSize in this client configuration file to the desired values.

3 Choose Server Administration � Enterprise Configuration � Component Definitions.

4 Create a new component using the AppObjMgr component type and set the Configuration File parameter of this component to the parameter value used in Step 2.

For information on creating server components, see the Siebel Server Administration Guide.

5 Assign the component to the Siebel Thin Client component group.

For information on assigning server components, see the Siebel Server Administration Guide.

6 Stop and restart the Siebel Server on which this new component was created.



Configuring Active Fields

Configuring Active Fields 6

All fields on an applet are automatically activated. Siebel performs queries for active fields only. This means that if the underlying business component has fields that are active, but not displayed, Siebel will generate the necessary SQL for them. If you prevent Siebel from generating the SQL for fields that are not displayed, this could yield fewer joins on queries.

To prevent Siebel from generating SQL for fields that are not displayed

Do one of the following at the business component level:

� Select which fields are automatically activated.

� Remove fields from the applet, so long as they are not marked as active.

Siebel Docking Transaction Logging at Runtime 6

One way to improve response time is to turn off Siebel Docking Transaction logging if it is not being used.

To turn off Siebel Docking Transaction logging

1 From the Siebel client, choose Application Administration � System Preferences from the Screens menu.

2 Find Docking:Transaction Logging in the System Preference Name field, and change the System Preference Value to FALSE.



Configuring Antivirus Software

Configuring Antivirus Software 6

Configuration information for the Siebel dedicated clients (Sales, Service, and Tools) is stored in a Siebel Repository file (.srf) on each client workstation. As this file is read extensively during start-up and throughout client operation, monitoring of this file by virus scanning software may significantly degrade Siebel client performance.

If you have virus scanning software installed on your client workstations, you should configure it to skip .srf files. These are binary data files that, to Siebel’s knowledge, cannot be infected, so the risk of this exclusion is very low.

Server-Side Performance Tips 6

See the Siebel Server Administration Guide for information about disabling Find Fast, load balancing, and other server-side performance enhancements.


Troubleshooting the Dedicated Client 7

Returning More Rows 7

This section applies only to users connected to a DB2/390 database.

If the following message appears while you are paging through the result set of a query, you must refine your query (use the Ctrl-R keyboard shortcut):

"There were more rows than could be returned. Please refine yourquery to bring back fewer rows."

A refined query selects a smaller set of rows containing the desired row or, if you are paging through a list, the next set of rows from the database.

For example, if you are looking for the contact "ABLE" and enter a query for all names that start with "A," it is likely the result set will be long and the message above will appear when you begin paging through the rows. Instead, refine the query to look for all names that start with "ABL." The result set will be much smaller and more likely to contain the desired row.


Troubleshooting the Dedicated Client

Returning More Rows


T h i n C l i e n t f o r W i n d o w s a n dJ a v a T h i n C l i e n t I n s t a l l a t i o n

a n d C o n f i g u r a t i o n Part 3

Chapter 8. Thin Client for Windows and Java Thin Client Overview

Chapter 9. Installing and Configuring Siebel Thin Client for Windows

Chapter 10. Installing and Configuring Siebel Java Thin Client

Chapter 11. Deploying Siebel Thin Client for Windows

Chapter 12. Java Thin Client and Thin Client for Windows Network Requirements

Chapter 13. Troubleshooting Thin Client for Windows and Java Thin Client


Thin Client for Windows and Java ThinClient Overview 8

What Are Thin Client for Windows and Java Thin Client? . . . . . . . . . . . 8-2

What’s New in Java Thin Client and Thin Client for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5

Deploying Windows and Java Thin Client Applications . . . . . . . . . . . . . 8-6

User Interface Functionality Supported in Windows and Java Thin Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7

Applet Classes Supported by Thin Clients . . . . . . . . . . . . . . . . . . . . . 8-8

Supported Control Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9

Unsupported Siebel Script Types . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10


Thin Client for Windows and Java Thin Client Overview

What Are Thin Client for Windows and Java Thin Client?

What Are Thin Client for Windows and Java Thin Client? 8

Siebel Thin Client for Windows and Siebel Java Thin Client enable enterprises to deploy the user interface layer of Siebel eBusiness Applications in a form in which it can be accessed using a Web browser, as a stand-alone Windows application, or as a Java application. The thin client can dramatically reduce the costs of deploying Siebel eBusiness Applications in the enterprise—users access the Siebel application from their desktop clients, which connect to a Siebel Server.

There are three types of Siebel thin clients:

� Siebel Thin Client for Windows. Siebel Thin Client for Windows enables enterprises to deploy the user interface layer of Siebel eBusiness Applications in a standard Web browser or as a stand-alone Windows executable.

� Siebel Java Thin Client. Siebel Java Thin Client enables enterprises to deploy the user interface layer of Siebel eBusiness Applications as a stand-alone Java application.

� Siebel HTML Thin Client. Siebel HTML Thin Client uses HTML for the user interface. Because HTML Thin Client differs substantially in its installation and usage, it is covered separately beginning with Chapter 14, “Siebel HTML Thin Client Overview,” in this guide.

With the Siebel thin client architecture, all business logic embodied in the Siebel business objects layer and data objects layer executes in scalable, multi-threaded Application Object Manager server components. The Application Object Manager is a component of the Siebel Server environment and is described in more detail in the Siebel Server Administration Guide.




Figure 8-1 shows an example of a view in Siebel eBusiness Applications as it appears in the stand-alone implementation of Siebel Thin Client for Windows.

Figure 8-1. Opportunity List View Displayed in Siebel Thin Client for Windows




Figure 8-2 shows the same view as it appears in the Siebel Java Thin Client.

Figure 8-2. Opportunity List View Displayed in Siebel Java Thin Client



What’s New in Java Thin Client and Thin Client for Windows

What’s New in Java Thin Client and Thin Client for Windows 8

Table 8-1 list the new features for the Java Thin Client and Siebel Thin Client for Windows in release 6.x.

Table 8-1. New 6.x Features for Java Thin Client and Siebel Thin Client for Windows (Sheet 1 of 2)

Feature Description New in Thin Client for Windows

New in Java Thin Client

New in Both Java Thin Client and Thin Client for Windows

Attachment Upload and view an attachment file, such as an HTML or PDF file.

�

(already part of Thin Client for Windows)

Column Reordering

Re-order the columns displayed in the list applet.

�


Network Data Performance

Enhances performance by reducing amount of data transferred.

�

Embedded Web Browser

View an HTML page inside Thin Client for Windows without the need to launch an external browser.

�

HTTP Tunneling Use HTTP as the communication protocol between the thin client and Application Object Manager. This is useful for data transfers across firewalls.

�

Send Email/FAX/Page

Send a Siebel record through email, fax, or page.

�



Deploying Windows and Java Thin Client Applications

Deploying Windows and Java Thin Client Applications 8

Applications delivered through Siebel Thin Client for Windows or Siebel Java Thin Client are configured using Siebel Tools in the same manner as all other Siebel applications. This enables you to use the methods described in this book to configure thin client applications in the same manner that you configure all other Siebel applications.

Unlike the dedicated client, Siebel thin client requires no client-side repository information. Instead, the repository information resides on the Siebel Server.

Methods for deploying and managing configuration and repository information on the Siebel Server are described in more detail in the Siebel Server Administration Guide and the Siebel Server Installation Guide.

Reports and Printing

Generate reports and print, similar to the dedicated client.

�

SmartScript Provides an interactive workflow questions-and-answers guide for call center agents. This feature functions the same as its counterpart in the dedicated client.

�


Table 8-1. New 6.x Features for Java Thin Client and Siebel Thin Client for Windows (Sheet 2 of 2)

Feature Description New in Thin Client for Windows

New in Java Thin Client

New in Both Java Thin Client and Thin Client for Windows



User Interface Functionality Supported in Windows and Java Thin Clients

User Interface Functionality Supported in Windows and Java Thin Clients 8

Siebel Thin Client for Windows and Siebel Java Thin Client support most of the user interface functionality present in the dedicated client. To help developers make sure that their configurations comply with the functional subset supported by thin client, this chapter lists the elements supported in the current release.

To successfully deploy thin client, developers should work with application administrators who, in turn, should identify users in the enterprise who can be fully served through the reduced functionality supported in one or the other thin client (compared with the traditional Siebel dedicated client).

Functionality available to thin client users can be grouped as follows:

� Supported applet classes

� Supported control types

� Supported Siebel script types

Information about the applet classes, control types, and script types is provided in the following three sections.




Applet Classes Supported by Thin Clients 8

Thin client for Windows and Java Thin Client do not display views containing applets that are based on unsupported applet classes. Such views are not available for selection by the user when accessing an application through the thin client. They are not displayed on the Screens menu or in the View bar, nor are they accessible by drill down from a supported view.

Developers configuring applications for thin client must work only with views that are constructed from applets that are fully supported by thin client. The list of applets supported in Thin Client for Windows is different from that supported by Java Thin Client, so verify that your applets will work in your environment or environments.

To view the list of supported classes for Siebel Thin Client for Windows

� Using Siebel Tools, query the thin client property within the repository and view the class object.

See the Siebel Tools Guide for more information about viewing supported thin client applet classes in Siebel Tools.

To view the list of supported classes for Siebel Java Thin Client

� Using Siebel Tools, query the Java Thin Client property within the repository and view the class object.

See the Siebel Tools Guide for more information about viewing supported thin client applet classes in Siebel Tools.




Supported Control Types 8

The following control types can be included on an applet that is part of a Thin Client for Windows or Java Thin Client-deployed view:

� Chart

Charts are supported in Thin Client for Windows but not in Java Thin Client.

� Checkbox

� ComboBox

� Label

� ListControl

� Pushbutton

� TextBox

� Group

� Third-party ActiveX controls, provided they do not call user interface methods.

Third-party ActiveX controls are supported in Thin Client for Windows only.

NOTE: Tree controls are not supported in either Siebel Thin Client for Windows or Siebel Java Thin Client, and any view whose applets contain tree controls will not be displayed.




Unsupported Siebel Script Types 8

Siebel VB and Siebel eScript scripts associated with an applet are not supported in Thin Client for Windows and Java Thin Client. Scripts associated with a business component are supported, with the following exceptions:

� Methods that refer to Siebel user interface objects (such as GotoApplet and GotoView) are not supported in business component-level scripts.

� User interface methods, such as MsgBox and InputBox, are not supported.

Any views containing unsupported business component scripts can be displayed to a thin client user, but the functionality provided by the script will be unavailable.


Installing and Configuring Siebel Thin Clientfor Windows 9


Connect String Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Where to Find Information for New Connect String . . . . . . . . . . . . . . 9-2

Support for Connect String Style Prior to Siebel 2000 . . . . . . . . . . . . . 9-3

Pre-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

Verifying Thin Client Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

Verifying the Siebel Enterprise Server . . . . . . . . . . . . . . . . . . . . . . . 9-4

Understanding the Administrator Installation Tasks . . . . . . . . . . . . . . 9-5

Installing Siebel Thin Client for Windows . . . . . . . . . . . . . . . . . . . . . . . 9-5

Launching Siebel Thin Client for Windows . . . . . . . . . . . . . . . . . . . . . 9-10

Creating a Custom Installer and Sharing Thin Client Files . . . . . . . . . . 9-10

Creating a Custom Thin Client for Windows Installer . . . . . . . . . . . 9-11

Packaging the Thin Client for Windows Installer . . . . . . . . . . . . . . . 9-15

Distributing the Thin Client Installer . . . . . . . . . . . . . . . . . . . . . . . 9-16

Modifying the Shortcut for the Stand-Alone Executable . . . . . . . . . . . . 9-17

Sample Connect Strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18

Server-Side Performance Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20

Removing Thin Client for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20


Installing and Configuring Siebel Thin Client for Windows

About This Chapter


This chapter describes the steps involved in installing and configuring Siebel Thin Client for Windows. The Thin Client for Windows connects to the Application Object Manager, which is a component of the Siebel Server. See the Siebel Server Administration Guide for detailed information on the Application Object Manger.

There are three implementations for Thin Client for Windows:

� ActiveX control within the Microsoft Internet Explorer browser.

� Netscape plug-in within the Netscape browser.

� Stand-alone Windows executable program. This is new in Siebel 2000.

Pre-installation, installation, and configuration tasks are described in this chapter.

Connect String Changes 9

The connect string for Siebel 2000 has been changed to better support firewalls. The actual connection mechanism exposes only one IP address, the Gateway Server virtual IP address, and one port per transport type (HTTP and TCP/IP) to the outside world.

The change means that the firewall administrator will only need to open the gateway VIP and one port (either port 80 for HTTP communication protocol or port 2320 for TCP/IP protocol). In the earlier implementation, administrators needed to expose one port for each Siebel Server component.

Where to Find Information for New Connect String 9

If you are using the stand-alone Thin Client for Windows, see “Modifying the Shortcut for the Stand-Alone Executable” on page 9-17.

If you are running Thin Client for Windows in a Web browser, see the Siebel Server Installation Guide for instructions on modifying the tclient.stc and tclient.htm configuration files.



Pre-Installation Tasks

Support for Connect String Style Prior to Siebel 2000 9

Siebel Systems continues to support the connect string style that was used in version 5.6 and earlier releases. Prior to Siebel 2000, the Communication Protocol and the encryption and compression settings were only specified on the Siebel Server using the Siebel dedicated client. In Siebel 2000, the encryption and compression settings:

� Must be specified at the client when you are using load balancing.

� Can optionally be specified when directly connecting to a server, if you are not using load balancing.

Pre-Installation Tasks 9

You must complete the following pre-installation tasks before you begin the installation and configuration tasks for Siebel Thin Client for Windows:

� “Verifying Thin Client Platforms”

� “Verifying the Siebel Enterprise Server” on page 9-4

� “Understanding the Administrator Installation Tasks” on page 9-5

Verifying Thin Client Platforms 9

You must verify that the client machines on which you will install and operate Thin Client for Windows have the following:

� Required hardware and software components installed and configured, as specified in the Siebel Release Notes.

� Network connectivity to the Siebel Enterprise Server using one of the supported network protocols and configurations specified in the Siebel Release Notes.

NOTE: CORBA and Resonate Central Dispatch are not required to run Siebel Thin Client for Windows.




Verifying the Siebel Enterprise Server 9

Before installing the thin client software, you must have completed the installation of the Siebel Database Server and Siebel File System, and have installed and configured an Enterprise Server containing the Gateway Server and at least one Siebel Server, following the instructions provided in the Siebel Server Installation Guide.

NOTE: It is strongly recommended that you implement the connection-brokering capabilities of the Siebel Gateway Server if you will support the thin client software from multiple Siebel Servers. These capabilities help to provide high scalability and availability for your thin client users. Refer to your Siebel Server Installation Guide for more information about connection brokering.

If you or someone else filled out the Deployment Planning Worksheet before installing your Siebel servers, make a copy and keep it with you while installing the thin client; otherwise, make a note of the Siebel Enterprise Server name and the IP address (or Gateway VIP if you are using Resonate Central Dispatch) of the Gateway Server, as well as the name of the Object Manager-defined components operating on the Enterprise Server.

You will need this information when configuring the thin client start-up files for Windows.



Installing Siebel Thin Client for Windows

Understanding the Administrator Installation Tasks 9

In preparing for your thin client users to install Siebel Thin Client for Windows you should:

1 Test the standard installer for Thin Client for Windows to decide how you want to customize the installation for your users. See “Installing Siebel Thin Client for Windows” on page 9-5, which provides instructions for installing Thin Client for Windows using the standard installation process provided on your CD-ROM.

2 Customize the installation process by editing the siebel.ini file. You may want to suppress dialog boxes that you don’t want your users to see, select and enforce a default installation directory, and so on. See “Creating a Custom Thin Client for Windows Installer” on page 9-11 for instructions.

3 Provide your users with the location of the customized installation program and instructions for installing in their environment.

NOTE: Typically, you would place your customized self-extracting installer, such as the setupex.exe file, on the public Web server, to be downloaded by the thin client end-users, to install before they launch the thin client program.

Installing Siebel Thin Client for Windows 9

This section provides instructions for using the standard installation program for Siebel Thin Client for Windows. In the standard installation provided on the Siebel eBusiness Applications Client CD-ROM, the files for Siebel Thin Client for Windows are automatically installed into c:\Program Files\Siebel\tclient during the thin client installation process. The client installation process for the stand-alone executable Thin Client for Windows is the same as the installation for the ActiveX control and the Netscape plug-in. See “To install Thin Client for Windows using the standard installation process” on page 9-6 for standard installation instructions.





The thin client start-up files for the ActiveX control and the Netscape plug-in are automatically installed into the \tclient subdirectory of the Siebel Server during Siebel Server installations on Windows NT. See “To verify that the Thin Client for Windows start-up files were installed” on page 9-9. The stand-alone Thin Client for Windows does not require a start-up file.

NOTE: You should test the standard installation process, compare it to the way you want your thin client users to install the program, and modify the installation process to conform to the needs of your thin client users. You should not distribute the thin client installation program to your users as it stands. You should customize the installation process, possibly suppressing all dialog boxes and choosing defaults for your users, to produce the easiest possible installation process.

To customize the installation for your thin client users, see “Creating a Custom Thin Client for Windows Installer” on page 9-11.

To install Thin Client for Windows using the standard installation process

NOTE: This standard installation process applies to all Thin Client for Windows installations, including the ActiveX control, Netscape plug-in, and stand-alone Thin Client for Windows implementations.

1 On the CD-ROM drive, navigate to the Windows Client\thinclientdirectory and double-click setup.exe.

2 In the Choose Setup Language dialog box, select your language from the picklist, and then click OK.

The Welcome dialog box appears.

3 Click Next in the Welcome dialog box.

The Setup Type dialog box appears.



4 Select the Custom install type.

� Typical option installs only ActiveX and CTI components.

� Compact option installs ActiveX only.

� Custom option allows you to select which components to install, out of four possible components.

5 Click Next in the Setup Type dialog box.

The Select Components dialog box appears. You must select one of the following three options for running Thin Client for Windows and select desired optional components:

� Stand-alone Windows Executable: Select this option if your users will not run Thin Client for Windows within a browser. This is the win32 stand-alone executable version of the Thin Client for Windows.

� ActiveX Control: Select this option if your users will run Thin Client for Windows within the Internet Explorer browser.

� Netscape Plug-in: Select this option if your users will run Thin Client for Windows within a Netscape browser.

� In addition, there are optional components that can be installed during the Siebel Thin Client for Windows installation; for example, CTI (Computer Telephony Integration support).

6 In the Select Components dialog box, click the Browse button to select an alternate destination directory if needed and then click Next.

If an alternate destination directory is not selected, Thin Client for Windows files will be automatically installed in the default Program Files\siebel\tclient directory.

NOTE: To install the Thin Client for Windows files in a different directory, change the RootDirectory parameter from Program Files\siebel\tclient to the directory where you want your users to install the files. If you are making changes such as this one to the client installation program, you will later create a custom installation program so that your users can install the thin client for Windows on their client machines. The RootDirectory parameter resides in the siebel.ini file. Instructions are provided in “Creating a Custom Thin Client for Windows Installer” on page 9-11.




7 In the Load Balancing dialog box, select the applicable option and click Next:

� Click Yes if your Siebel Server will use Resonate.

� Click No if your Siebel Server will not use Resonate.

NOTE: Step 7 through Step 13 will only appear if the Stand-alone version is selected during the Custom installation option. If you did not select the Stand-alone version, go to Step 14 now.

8 In the Gateway and Enterprise Server Information, enter information for each of the fields, and click Next.

� Gateway Server Host: the default is localhost.

� Gateway Port: the default is 2320.

� Enterprise Server Name: the default is siebel.

9 In the Siebel Server Information dialog box, enter the name of your Siebel Server, and then click Next.

10 In the Object Manager Component dialog box, enter the component name for your Object Manager and click Next.

You can use one of the following components:

� SSEObjMgr for Siebel Sales

� SSVObjMgr for Siebel Service

� SCCObjMgr for Siebel Call Center

� SFSObjMgr for Siebel Field Service

11 In the Connection Protocol dialog box, select either TCP/IP or HTTP, and then click Next.

12 In the Encryption Type dialog box, select the type of encryption to use for the connection, and then click Next.

13 In the Compression Method dialog box, select the compression type to use for the connection, and then click Next.

A status bar appears to show the progress of the installation.




14 Click Finish in the Completion dialog box.

Your Siebel Thin Client for Windows installation is now complete.

During this installation process, a shortcut was created in the program folder to point to siebtc.exe for the stand-alone Thin Client for Windows. The shortcut includes the parameter values you selected during the standard Siebel Thin Client for Windows installation process. Users who are using the stand-alone Thin Client for Windows will just double-click the shortcut to access the application.

See “Modifying the Shortcut for the Stand-Alone Executable” on page 9-17 for more information about changing parameter values in the connect string for the stand-alone Thin Client for Windows without re-running the installation program.

NOTE: If instead you are using either the ActiveX control or the Netscape plug-in version of Thin Client for Windows, shortcuts are created during the thin client installation to point to tclient.htm for the ActiveX control and tclient.stc for the Netscape plug-in. When you customize siebel.ini, you will customize the URL address for these shortcuts.

To verify that the Thin Client for Windows start-up files were installed

� Ensure that the \tclient directory exists on one Siebel Server and has been populated with these files: enu.txt, tclient.htm, tclient.stc.

The files are installed from the Siebel Server, so they need only be available on one Siebel Server.

There are no further steps for installing Thin Client for Windows. Now you must modify the start-up files for the clients if you are running the thin client from a Web browser. See the Siebel Server Installation Guide for instructions on configuring tclient.stc and tclient.htm.

The stand-alone Thin Client for Windows does not require further configuration.



Launching Siebel Thin Client for Windows

Launching Siebel Thin Client for Windows 9

Starting Siebel Thin Client for Windows is the same as starting any other Windows program.

To start Siebel Thin Client for Windows

� Choose Start � Programs � Siebel Thin Client 6.0 � Siebel Thin Client for Windows, or

� Double-click the shortcut Siebel Thin Client for Windows, created on the desktop during installation.

The shortcut launches either Microsoft Internet Explorer or the Netscape Web browser with the URL address specified in the siebel.ini file.

Creating a Custom Installer and Sharing Thin Client Files9

Once you have edited one or both of the Siebel Thin Client for Windows start-up files, tclient.stc and tclient.htm, they and the client installation program must be made available to the thin client users.

For ease of maintenance it is strongly recommended that you share the start-up files and the custom installer from a network shared drive or a Web server. This allows you to distribute changes easily in the event that your Siebel Enterprise Server configuration is altered.

See the Siebel Server Installation Guide for information about editing tclient.htm and tclient.stc.

NOTE: You may also use the Siebel Packager Utility to prepare custom software installation packages for distribution to end users. Please refer to the Siebel Upgrade Guide for details.

NOTE: If client users will use the stand-alone version of Thin Client for Windows, you do not need to distribute the start-up files. In this case, you must distribute only the Thin Client for Windows client installation program after you have finished customizing it.



Creating a Custom Installer and Sharing Thin Client Files

Creating a Custom Thin Client for Windows Installer 9

The Siebel eBusiness Applications CD-ROM contains a standard installer for Siebel Thin Client for Windows. While you can certainly distribute this installer as it is provided, it is more likely that you will create a customized installer that automatically installs Siebel Thin Client for Windows software onto the user desktop without ever prompting users to enter installation parameters. The customized installer will be a self-extracting setupex.exe file that users can download and install over the Internet or corporate intranet.

If you elect to create a custom installer for Siebel Thin Client for Windows, you must complete the following tasks:

� “Preparing the Siebel Administrator’s Workstation” on page 9-11

� “Configuring the Thin Client for Windows Installer” on page 9-12

Preparing the Siebel Administrator’s WorkstationTo prepare the Siebel Administrator’s workstation to create a customized installer, you must perform two steps.

To prepare the administrator’s workstation

1 Install the standard Siebel client.

Refer to Chapter 4, “Installing the Dedicated and Mobile Clients,” for instructions on installing the standard Siebel client.

During the installation process, you must specify a Custom install type and select the Siebel Packager module to install the files required to modify the Siebel Thin Client for Windows installer.

2 Copy the Thin Client for Windows files to the administrator’s workstation. Copy the entire Windows Client\thinclient directory from the Siebel eBusiness Applications Client Programs CD-ROM to a directory on the administrator’s workstation.

This next section assumes that the directory on the administrator’s workstation is c:\ThinClient; be sure to substitute the actual directory name where you see this reference.




Configuring the Thin Client for Windows InstallerThe behavior of the Thin Client for Windows installer is determined by the siebel.ini file, which is located in the c:\ThinClient directory on the Siebel administrator’s workstation. You must edit this file to set the parameters for your desired installer behavior.

To edit the siebel.ini file

1 Open the siebel.ini file with a standard text editor.

You will see that the file consists of a number of sections with labels enclosed in square brackets (for example, [Startup]). Each section contains a number of parameters whose values determine the behavior of the installer.

A description of the parameters that you can modify is presented next. To modify a parameter, simply replace its value with the desired value. For example, you might change HideBackground=no to HideBackground=yes.

2 Startup. In the [Startup] section, you can modify the following parameters:

� HideBackground. When the HideBackground parameter is set to No, the installation background window is displayed during the client installation. When it is set to Yes, the user will not see the background. The default setting is No.

� Language. This parameter specifies the language for the installation. The default setting is ENU for American English.

3 [Icons]. In the [Icons] section:

� siebtc. Set this parameter to Yes if your thin client users will be using the stand-alone Thin Client for Windows. Set this parameter to No if your users will not be using the stand-alone Thin Client for Windows.

� DesktopIcon. This parameter is set to Yes by default to create a shortcut on the client machine’s desktop to the Thin Client for Windows executable.

� FolderIcon. This parameter is set to Yes by default to create a shortcut in the client machine’s Program Folder to the Thin Client for Windows executable.




4 DesktopIcon. In the [DesktopIcon] section:

� Command. This parameter is the shortcut to the tclient.htm or tclient.stc file.

Here is an example if your users are accessing Thin Client for Windows from Internet Explorer. Notice the .htm extension at the end of the path:

http://myserver/tc/elise/CallCenter.htm

Here is an example for your users who are accessing Thin Client for Windows from within a Netscape Web browser. Notice the .stc extension at the end of the path:

http://myserver/tc/elise/CallCenter.stc

� Caption. The default is Siebel Thin Client for Windows.URL. Change this setting if you would like to change the text on the icon.

� Folder. This is set to Desktop by default and specifies where the shortcut to Thin Client for Windows is located for your users. The shortcut differs depending on whether your users are running Siebel Thin Client for Windows from within the Netscape or the Internet Explorer Web browser.

5 Dialog. You can modify the following parameters in the [Dialog] section. If you would like to supply a silent installation that enforces particular parameter values, set each dialog box to No.

� Welcome. Setting the Welcome parameter to Yes shows a Welcome dialog box when users begin the installation of Thin Client for Windows. The default setting for this parameter is Yes. Set this parameter to No if you don’t want your users to see this dialog box.

� FolderName. If set to Yes, this dialog box appears and enables the user to set the name of the folder in which Thin Client for Windows will appear in the Programs group. Set this parameter to No if you do not want your users to see this dialog box.




� Setup Type. If set to Yes, the Setup Type dialog box appears during the installation. The user can select from Typical, Compact, or Custom options in this dialog box. Set this parameter to No if you do not want your users to see this dialog box during the installation process.

� Finish. If set to Yes, the Finish parameter will display a dialog box indicating that the installation was successful. The default setting for the Finish parameter is No. This ensures that the installation will not be noticeable to the end user.

6 Defaults. You can modify the following parameters in the [Defaults] section:

� RootDirectory. The directory into which Thin Client for Windows will be installed. The default is \Program Files\siebel\tclient. Leaving this parameter set to No will not give users the ability to edit the default installation directory. The default installation directory is specified in the Defaults section in the siebel.ini file. The default setting for this parameter is Yes. Set this parameter to No if you don’t want your users to see this dialog box.

� GatewayHost. Replace with the name of your Gateway Server.

� GatewayPort. Replace with the transport protocol with 80 for TCP/IP or 2320 for HTTP. The default is 2320.

� Enterprise. Replace with your Enterprise Server name. The default is siebel.

� SiebelServer. Replace with your Siebel Server name.

� ObjMgrComponent. Replace with the name of your Application Object Manager component.

� ConnectionProtocol. Replace with the transport protocol for your configuration. The default is tcpip.

� ConnectionEncryption. Replace with the encryption used during data transfers. The default is none.





� ConnectionCompression. Replace with the compression used during data transfers. The default is none.

� ResonateInstalled. Replace with TRUE if your configuration includes Resonate Central Dispatch. The default is FALSE.

� FolderName. Specifies the default Program group name, Siebel Thin Client 6.0.

7 Module. If you are creating a silent installation, identify the components you want to install by setting the parameters in the [Modules] section.

For example:

[Module.Configuration]

Typical = ACTIVEX,CTI

� Save and close the siebel.ini file once you have made the desired edits. To test the settings, double-click the C:\ThinClient\setup.exe file in Windows Explorer to launch the Thin Client for Windows installer. It will execute using the settings that you just entered in the siebel.ini file.

Packaging the Thin Client for Windows Installer 9

Once you have edited the siebel.ini file, you must complete the following steps to package a new Thin Client for Windows installer containing these changes.

1 In Windows Explorer, double-click the file exebuild.exe in the \packager\bin subdirectory of your Siebel dedicated client installation to start the EXE Builder.

2 Perform the following steps to run exebuild.exe, the program that builds the new installer:

a Click Next in the Welcome dialog box.

b In the first of four dialog boxes, specify the directory into which you copied the thin client files in Step 2 on page 9-11. Select both Create a 32bit self-extracting EXE and Compress the included files. Click Next.

c In the second dialog box, select setup.exe as the executable to be launched upon extract. Click Next.



d In the third dialog box, enter the target directory in which the self-extracting executable will be created. Enter an application name, if desired. You may also enter a password that users will need to specify to install the software. Click Next.

e In the fourth dialog box, review Source File Location, Command line to run, and Self-extracting EXE to create information. If any of these settings is incorrect, click Back to return to the appropriate dialog box and correct the information. Click Finish when you are ready to create the Installer.

NOTE: The EXE Builder will package your customized Siebel Thin Client for Windows installer into a single, self-extracting executable file, setupex.exe. This is the file that must be distributed to your thin client users for installation.

Distributing the Thin Client Installer 9

The Siebel Thin Client for Windows installer file you created must be made accessible to the thin client machines so that users can install Siebel Thin Client for Windows. The following are sample methods that you might use to distribute the Thin Client for Windows installer in your environment:

� Place it on a Web page for users to download.

� Place it on a network shared drive that provides read access to the thin client machines. This option is typically used for thin clients operating from your intranet. The application server operating system must support long filenames.

� Distribute the actual file through email, CD-ROM, or other distribution medium.

� Use commercial software distribution products to distribute and potentially execute the thin client installer.

You may elect to use a combination of these methods to serve different user communities. Whichever sharing mechanisms you elect to deploy, distribute the customized installer now and make sure that the thin client machines have read access to them.

Once the Thin Client for Windows customized installer is accessible to the thin client machines, your clients are ready to proceed with installing Siebel Thin Client for Windows.



Modifying the Shortcut for the Stand-Alone Executable

Modifying the Shortcut for the Stand-Alone Executable 9

This section provides instructions for modifying the shortcut for the stand-alone executable version of Thin Client for Windows. Once the stand-alone Thin Client for Windows is installed on the client machines, the shortcut must be changed on each machine if there are changes to the Siebel Server connect string information.

To modify the shortcut for the stand-alone thin client on a single machine

1 Find and right-click the shortcut icon, and choose Properties from the Shortcut menu. By default, a shortcut is created in the Programs folder and on the Desktop.

The Siebel Thin Client Shortcut Properties dialog box appears.

2 The shortcut URL appears in the Target field on the Shortcut tab, and looks similar to this example:

"C:\Program Files\siebel\tclient\BIN\siebtc.exe" /host"siebel[.transport][.encryption][.compression]://<gatewayserver>[:port]/<enterpriseserver>/<objectmanager>/<siebelserver>"

where < > (angle brackets) indicate a required parameter, and [ ] (square brackets) indicate an optional parameter.

a Specify the protocol settings:

[transport][.encryption][.compression]

� Transport values are tcpip or http. The default is tcpip.

� Encryption values are none or mscrypto. The default is none.

� Compression values include none, zlib, and pkware. The default is none.

NOTE: If you want to accept the default protocol settings, all protocol values can be omitted from the connect string.

Caution: Manually editing the connect string information is not recommended, and it should be avoided if possible.




b Substitute your Gateway Server address and port for <gatewayserver>, your Enterprise Server name for <enterpriseserver>, your Application Object Manager component name for <objectmanager>, and your Siebel Server name for <siebelserver>.

NOTE: You must specify <siebelserver> if you are not using Resonate Central Dispatch. If you are using Resonate Central Dispatch, <siebelserver> is optional.

3 Click Apply to save your changes, and then click OK to dismiss the Siebel Thin Client Properties dialog box.

Sample Connect Strings 9

This section contains examples of the different variations on the connect string.

Configuration That Does Not Include Resonate Central DispatchHere is an example of specifying the server name for a setup that does not include Resonate Central Dispatch:

"siebel.tcpip.mscrypto.pkware://<gatewayaddress>[:port]/<siebelenterprise>/<objectmanager>/<siebelserver>"

Configuration That Uses Defaults for Protocol and LanguageHere is an example using the default values for the protocol and language. Notice that the protocol values and the language value are left out entirely, which means that the default values are automatically substituted. In addition, the following example assumes that Resonate Central Dispatch is installed:

"siebel://<gatewayaddress>[:port]/<siebelenterprise>/<objectmanager>"




Configurations That Use Different Transport MechanismsHere are two examples that use mscrypto for encryption and tcpip for transport. The difference between the two is http is specified in the second example. It’s not necessary to specify the transport if using the default, tcpip. In addition, the following examples assume that Resonate Central Dispatch is installed.

Example 1"siebel.none.mscrypto://<gatewayaddress>[:port]/<siebelenterprise>/objectmanager>"

Example 2"siebel.http.mscrypto://<gatewayaddress>[:port]/<siebelenterprise>/<objectmanager>"

Here is an example that uses http for the transport, no compression, and no encryption:

"siebel.http.none.none://<gatewayaddress>[:port]/<siebelenterprise>/<objectmanager>"



Server-Side Performance Tips

Server-Side Performance Tips 9

See the Siebel Server Administration Guide for information about disabling Find Fast and other server performance enhancements that will improve client performance.

Removing Thin Client for Windows 9

To remove Siebel Thin Client for Windows, perform one of the following steps:

� Double-click Add/Remove Programs in the Control Panel, and follow the instructions for removing programs.

� Double-click the installation program, setup.exe, for Siebel Thin Client for Windows, and then click Yes to remove the program.


Installing and Configuring Siebel Java ThinClient 10


Where to Find Information for New Connect String . . . . . . . . . . . . . . . 10-2


Verifying Thin Client Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Verifying the Siebel Enterprise Server . . . . . . . . . . . . . . . . . . . . . . . . . . .10-3

Installing Siebel Java Thin Client Under UNIX . . . . . . . . . . . . . . . . . . . 10-4

Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6

Editing the Java Thin Client Configuration File . . . . . . . . . . . . . . . . 10-6

Year 2000 Compliance in Siebel Java Thin Client . . . . . . . . . . . . . . 10-11

Customizing the Java Thin Client Help . . . . . . . . . . . . . . . . . . . . 10-11

Sharing Thin Client Start-Up Files . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17

Starting Java Thin Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17

Removing Java Thin Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-18


Installing and Configuring Siebel Java Thin Client

About This Chapter


This chapter covers the installation of Siebel Java Thin Client. Siebel Java Thin Client should be installed once in a directory accessible to all the thin client users.

Siebel Java Thin Client is currently supported under Solaris 2.6 UNIX.

Where to Find Information for New Connect String 10

See “Sample Java Thin Client Start-Up File” on page 10-6 and “Editing the Java Thin Client Configuration File” on page 10-7.

Siebel Systems continues to support the connect string style that was used in version 5.6 and earlier releases.


You must complete the following pre-installation tasks before you begin installation of Siebel Java Thin Client:

� “Verifying Thin Client Platforms”

� “Verifying the Siebel Enterprise Server” on page 10-3


You must verify that the machine on which you will install and operate Java Thin Client has the following:

� Required hardware and software components, including a supported Web browser, installed and configured, as specified in the Siebel Release Notes.






Before installing Siebel Java Thin Client, you must have completed the installation of the Siebel Database Server and Siebel File System, and have installed and configured an Enterprise Server containing the Gateway Server and at least one Siebel Server, following the instructions provided in the Siebel Server Installation Guide.

Java Thin Client supports the Enterprise Server running on both Windows NT and UNIX platforms.

NOTE: It is strongly recommended that you implement the connection-brokering capabilities of the Siebel Gateway Server if you will support the Java Thin Client from multiple Siebel Servers. These capabilities help to provide high scalability and availability for your thin client users. Refer to your Siebel Server Installation Guide for more information on connection brokering.

If you or someone else filled out the Deployment Planning Worksheet before installing your Siebel Servers, make a copy and keep it with you while installing Java Thin Client; otherwise, make a note of the Siebel Enterprise Server name and the IP address (or VIP if you are using Central Dispatch) of the Gateway Server, as well as the name of the Application Object Manager-defined components operating on the Enterprise Server.

You will need this information when configuring siebel.cfg for Java Thin Client.



Installing Siebel Java Thin Client Under UNIX

Installing Siebel Java Thin Client Under UNIX 10

Java Thin Client consists of client-side software written in the Java language. The Java Thin Client connects to the Application Object Manager, which is a component of the Siebel Server. See the Siebel Server Administration Guide for detailed information about the Application Object Manager.

To install Siebel Java Thin Client on a supported UNIX platform, you must first install a supported Web browser.

Once you have installed the Web browser, you are ready to install Siebel Java Thin Client on a network-accessible machine to which all the thin client users have access.

To install Siebel Java Thin Client

1 Open a command shell window.

2 Create a directory in which you want to install Siebel Java Thin Client.

3 Navigate to the /Java Client/jtc/jtc_Installer directory on your UNIX server CD-ROM and open the install.htm file using your Web browser.

4 The Siebel Java Thin Client Installer Web page opens.

5 Select the “For Solaris” link for your UNIX install.

The Java Thin Client Installer instructions screen appears.

6 Select the “Install the Siebel Java Thin Client for Solaris” link for your UNIX install.

The Save Downloaded File dialog box appears.

7 Choose the directory you created in Step 2, and click OK.

The file will download into the appropriate location.

8 Open a UNIX shell command window and change directory into the directory into which you downloaded the installation file, setup.bin.



Installing Siebel Java Thin Client Under UNIX

9 Execute the Siebel Java Thin Client installation program by typing the following command and pressing ENTER:

sh setup.bin

A Siebel dialog box appears.

10 Enter the directory created in Step 2, and then click Next to install Siebel Java Thin Client.

The default selection is Siebel.

11 Follow the Java Thin Client installer's instructions.

The installer will install Siebel Java Thin Client, and prompt you when it is finished.

To retrieve the configuration information for Java Thin Client

1 Click the Back button in the browser to return to the initial Siebel Java Thin Client Installer Web page.

2 Select the Update the Default Configuration File hyperlink.

The Save Downloaded File dialog box appears.

NOTE: If the Save Downloaded File dialog box does not appear, right-click the link and choose Save Link As. The dialog box will now appear.

3 Choose the same directory into which you installed the Java Thin Client, and click Save.

4 Close the browser.

This completes the installation of Siebel Java Thin Client.

Caution: Be sure that your siebel.cfg file is not saved with the wrong extension. Note that your browser will save the .cfg file with the extension of the last file that it saved. Therefore, if the last file your browser saved had a .exe extension, your configuration file (siebel.cfg) would become saved as siebel. If this happens you will not see anything in the login pop-up box.



Configuration Tasks

Configuration Tasks 10

After installing Java Thin Client on a machine to which all thin client users have access and copying the configuration file to the same directory, you must:

� Edit the configuration file, siebel.cfg, to set the default Siebel connectivity information.

� Ensure Year 2000 compliance in your Java Thin Client applications.

Editing the Java Thin Client Configuration File 10

Siebel Java Thin Client is configured with the siebel.cfg file, a text file that sets a number of run-time parameters, including its default appearance, authorization information, and connectivity information. If you have not already retrieved the file from the CD-ROM, it’s located on the UNIX Server CD-ROM under /Java Client/jtc/jtc_installer.

Sample Java Thin Client Start-Up FileThis section contains a sample siebel.cfg file to assist you in editing your own siebel.cfg file. Briefly review this sample, and then follow the instructions in the next section, “Editing the Java Thin Client Configuration File,” to edit your siebel.cfg file.

Here is an example of a configured siebel.cfg file that lets users connect to Call Center, Field Service, Siebel Sales, or Siebel Service on the ESPRIT server. In this example, the Gateway Server name is ELAN, and the Enterprise Server name is ESPRIT.

[Siebel]DataSource = "SSE"DateYearFormat = "YYYY"DecimalNumberScale = "2"

[Datasources]Sample = “Sample Database”SSE = “Siebel Sales”SSV = “Siebel Service”SCC = “Siebel Call Center”SFS = “Siebel Field Service”



Configuration Tasks

[SSE]SOMConnectString = "siebel://elan/esprit/sseobjmgr/esprit"

[SSV]SOMConnectString = "siebel://elan/esprit/ssvobjmgr/esprit"

[SCC]SOMConnectString = "siebel://elan/esprit/sccobjmgr/esprit"

[SFS]SOMConnectString = "siebel://elan/esprit/sfsobjmgr/esprit"

[FileExtensionMap]Browser = "/opt/netscape/netscape"html = "/opt/netscape/netscape"jpg = "/opt/netscape/netscape"gif = "/opt/netscape/netscape"bmp = "/opt/microsoft/bin/iexplorer"txt = "/usr/dt/bin/dtpad"cfg = "/usr/dt/bin/dtpad"

Editing the Java Thin Client Configuration FileThe siebel.cfg configuration file shipped with Siebel Java Thin Client contains several sections. You must edit your siebel.cfg file so that Java Thin Client will start up and function as expected. The sections of the siebel.cfg file are described in the following procedure, “To edit siebel.cfg.”

NOTE: If different users will connect to different Siebel Enterprise servers, you may want to produce separate siebel.cfg files for each group. Each siebel.cfg file would specify a different Siebel Enterprise Server. The Siebel Server to which the client would connect would then depend on which siebel.cfg file was used.



Configuration Tasks

To edit siebel.cfg

1 Edit the DataSource, DateYearFormat, and DecimalNumberScale parameters in the Siebel section as described here:

� [Siebel]: This section sets the default connection, date format, and number format for your Siebel client. The default for this section reads as follows:

DataSource = "SCC"DateYearFormat = "YYYY"DecimalNumberScale = "2"

� Edit DataSource to show your user’s default data source, selecting from the available data sources listed in Step 2.

� Leave DateYearFormat as it stands; it is already properly set to use four-digit dates. Using four-digit dates prevents Year 2000 problems with your data.

� Leave DecimalNumberScale as it stands unless you want your Siebel application to display numbers in some format other than with two decimal places showing.

2 Edit the parameters in the [DataSources] section to add or modify the servers in your local Siebel deployment.

� [DataSources]: This section lists the available Siebel Servers in your deployment in the following format:

Sample = "Sample Database"SSE = "Siebel Sales"SSV = "Siebel Service"SCC = "Siebel Call Center"SFS = "Siebel Field Service"

3 Add a data source section for each data source you added in Step 2, and replace <gatewayserver> with the name of your Gateway Server, <enterpriseserver> with the name of your Enterprise Server, and <siebelserver> with the name of your Siebel Server in each connect string to show the servers from which that particular data source is available.



Configuration Tasks

� [Individual Data Source Connections]: Each data source listed in [DataSources] will have a section of its own. The connect string for each data source takes this general form:

"siebel[.transport][.compression]://<gatewayserver>[:port]/<enterprisename>/<objectmanagername>[/<siebelservername>]"

[SSE]SOMConnectString = "siebel://<gatewayserver>/<enterpriseserver>/sseobjmgr/<siebelserver>"

[SSV]SOMConnectString = "siebel://<gatewayserver>/<enterpriseserver>/ssvobjmgr/<siebelserver>"

[SCC]SOMConnectString = "siebel://<gatewayserver>/<enterpriseserver>/sccobjmgr/<siebelserver>"

[SFS]SOMConnectString = "siebel://<gatewayserver>/<enterpriseserver>/sfsobjmgr/<siebelserver>"

4 Modify the parameters in the FileExtensionMap section to point to your default browser, and add other extensions as needed for the file types used in your deployment.

� [FileExtensionMap]: This section lists file extensions and associates them with the correct application programs. The default reads as follows:

Browser = "/usr/bin/netscape"html = "/usr/bin/netscape"

In addition to these default entries, you can add any other extensions you want and associate them with any application program installed on your workstation. Examples of extensions you may want to add include:

NoExtension = "<application>"asc = "<application>"txt = "<application>"text = "<application>"htm = "<application>"shtml = "<application>"htp = "<application>"asp = "<application>"



Configuration Tasks

NoExtension tells Siebel how to treat files with no extension, such as a Readme file. The extensions asc, txt, and text are common extensions for ASCII text files, and should be associated with a text editor, such as vi or Emacs. The remaining extensions in the sample list refer to several different types of HTML files, which should be associated with your Web browser.

You can also add extensions for attached files in formats such as graphics programs, audio clips, video clips, and any other type of data you may include on your server.

5 Set the parameters in the Preferences section to reflect the color scheme and fonts for your user interface.

� [Preferences]: This section allows you to set the default color scheme and fonts that Siebel Java Thin Client will use. The default entries are:

;Colors = Web;DefaultFont = SansSerif-12-normal;ScreenBitmap = FALSE;ListAlternateColor = FALSE

� To set Colors to a value other than the default, remove the semicolon from the beginning of the line. The options for this entry are Web, High, and VGA.

� To set DefaultFont to a different font, remove the semicolon from the beginning of the line. You can also change this entry to modify the point size and style. Available fonts are Serif, SansSerif, and Monospaced. Available point sizes are whole numbers between 8 and 24, although most users on most systems will find any point size below 10 too small and any size above 14 too large. Available styles are normal, bold, and italic.

� To set ScreenBitmap to TRUE, remove the semicolon from the beginning of the line. If this parameter is set to FALSE, the bitmap of the currently selected view will not appear in the View bar. If set to TRUE, the bitmap will appear in the View bar.

� To set ListAlternateColor to TRUE, remove the semicolon from the beginning of the line. If set to FALSE, the rows in list applet tables will not use alternating list color, which means all rows in each list applet table will use the same background color. In this case the tables will display horizontal grid lines. If set to TRUE, list applet tables will display alternate rows in different colors.



Configuration Tasks

Year 2000 Compliance in Siebel Java Thin Client 10

The Java VM (Virtual Machine) returns a 2-digit date by default. For example, 99 is the 2-digit format representing the 4-digit format for 1999. This default 2-digit format could have an impact on users running Siebel applications in the Java Thin Client environment. Users may inadvertently enter a date with an incorrect century.

The siebel.cfg file shipped with Java Thin Client is configured correctly to enforce use of a 4-digit date format for Java Thin Client itself, as the DateYearFormat parameter is set to YYYY.

Ensure that this setting is present in every .cfg file for each application installed on each client computer in your organization that will use the Java Thin Client environment.

Customizing the Java Thin Client Help 10

This section provides information you may need to customize the online help provided with Siebel Java Thin Client. It explains how the help is organized and contains a table listing each file and its general purpose or contents.

Overview of the Siebel Java Thin Client HelpThe Siebel Java Thin Client help system is a group of HTML files. The HTML files contain either information that applies to a specific screen or general information about using Java Thin Client.

The help system is displayed in a set of three frames. The frame on the left contains the tables of contents. Text appears in the frame on the right. The top frame contains the Siebel header. The frameset is specified in the start.html file. The Java Thin Client help system is formatted using HTML version 4.0. A cascading style sheet,javatc.css, is used to customize the formatting of the system. In general, the formatting of the HTML files has been kept simple. The system contains no additional applets, scripting, or dynamic HTML elements.

The help source is included on the installation CD for Java Thin Client. It is located in the /jtc/help directory.



Configuration Tasks

Understanding the Structure of Java Thin Client Online HelpThe Java Thin Client online help is designed in a highly structured manner, which is described in this section. The intent of the structure is to make the help system easy to use and modify.

Almost every HTML file in the system contains a short table of contents at the beginning of the file. This list contains intra-topic jumps to the subsections of the file. These intra-topic jumps are not included in the tables of contents displayed in the left pane, to minimize the number of contents files in the system and to avoid using applets to display contents.

Understanding the TopicsThe Siebel Basics topics describe basic procedures used throughout Java Thin Client. These topics provide information on working with menus, navigating between views, finding and sorting information, creating and using queries, and other common tasks. In the help system’s table of contents, these topics appear under the Siebel Basics heading. The HTML files for Siebel Basics are located in the jtc_basics directory.

Help is provided for each screen in the application. In the table of contents, these topics appear under the Siebel Screen Topics heading. The HTML files for Siebel Screen Topics are located in both the screentopics and other directories.

Each screen topic contains an “About” topic that provides introductory information for the screen. In addition, each screen generally has between two and ten procedural topics. The procedures document tasks that users can perform within the screen views.

Determining Which Source Files You Will UseAfter you understand the structure of the help system, you should be able to identify the source files that contain the topics you want to retain or remove. In general, your customized help should include only those topics that apply to the screens and views included in your company’s implementation of Java Thin Client.

For example, if your company has implemented only the Call Center, you can remove the help source files for Field Service from both the directory and the appropriate contents files. In addition, you can edit the HTML text to remove references to views you are not implementing or to use your organization's terminology or business processes.



Configuration Tasks

Siebel Java Thin Client Help System ContentsTable 10-1 provides a general explanation of the contents of each HTML file included in the Java Thin Client help system and its location in the Help directory.

Table 10-1. The Java Thin Client Help Files (Sheet 1 of 4)

Directory Filename Purpose/Contents

root contents_get_start.html Getting Started table of contents

javatc.css Cascading style sheet for the project

jtc_contents1.html Table of contents

siebel_header.html Page containing Siebel banner

start.html Page containing frames; page to click to start viewing help system

welcome.html Welcome topic

jtc_basics contents_basics.html Basics table of contents

entering_info.html Entering information topics

finding_sorting.html Finding and sorting topics, including querying

keyboard_scuts.html Keyboard shortcut topics

logging_on.html Logon instructions topic

menu_reference.html Menu topics

menus_screens_views.html Working with menus, screens, and views topics

navigating_between_views.html Navigating between views topics

setting_options.html Setting options topics

other admin.html Administration screen topics

cti_bar.html CTI Toolbar topics

glossary.html Glossary



Configuration Tasks

screentopics contents_screen_topics.html Screen topics table of contents

sa_accounts.html Accounts screen topics

sa_activ.html Activity Management screen topics

sa_agree.html Agreements screen topic

sa_cal.html Calendar screen topics

sa_cont.html Contact Management screen topics

sa_empl.html Employees screen topics

sa_ent.html Entitlements screen topics

sa_prodi.html Product Information screen topics

se_camp.html Campaigns screen topics

se_cat.html Categories screen topics

se_incent.html Incentive Compensation screen topics

se_list.html List Management screen topics

se_opp.html Opportunity Management screen topics

se_price.html Price Lists screen topics

se_quote.html Quotes screen topics

se_resp.html Responses screen topics





Configuration Tasks

screentopics(continued)

se_slqta.html Sales Quotas screen topics

sf_cycle.html Cycle Counts screen topics

sf_invt.html Inventory Transactions screen topics

sf_order.html Orders screen topics

sf_parb.html Part Browser screen topics

sf_rec.html Receiving screen topics

sf_repair.html Repair screen topics

sf_reqst.html Service Requests screen topics

sf_servi.html Service Inventory screen topics

sf_ship.html Shipping screen topics

sv_assets.html Assets screen topics

sv_qual.html Quality and Defect Tracking screen topics

sv_solu.html Solutions screen topics





Configuration Tasks

gif graphics 11.gif New Query icon

13.gif Run Query icon

17.gif Add New Record icon

2.gif Switch icon

arrowup.gif Bitmap for returning to the top of the page

b_b_o_lt.gif Copy button

b_cncel.gif Cancel button

b_dlete.gif Delete button

b_new.gif New button

b_swtch.gif Switch icon

blubull.gif Blue bullet used in the tables of contents

c_right.gif Copyright symbol

call.gif Call button

newcor.gif New Correspondence button

qry_qry.gif New Query icon

qry_ylw.gif Run Query icon

resize1.gif Resizing a column, image 1

resize2.gif Resizing a column, image 2

siebel_header.gif Siebel header





Sharing Thin Client Start-Up Files

Sharing Thin Client Start-Up Files 10

Once you have installed Siebel Java Thin Client and edited the configuration file, notify your thin client users. For ease of maintenance, Siebel strongly recommends that you share the configuration file from a network-accessible machine, in the same directory in which you installed Java Thin Client. This allows you to easily distribute changes in the event that your Siebel Enterprise Server configuration is altered.

Starting Java Thin Client 10

Java Thin Client is a stand-alone client; it does not require a Web browser except for installation.

To start Java Thin Client

1 Execute Siebel Java Thin Client using the siebel program directly from a command shell window with the ./Siebel command.

The logon dialog box appears.

2 Enter your Siebel user ID, password, and connect string or data source name.

If the siebel.cfg file has been properly configured, then you can choose the data source to which you want to connect. Enter the name of the data source you will use from those listed in your siebel.cfg file.

� If you are a system administrator setting up a client workstation, look in the siebel.cfg file for a list of available data sources.

� If you are an end user, your system administrator should provide you with an appropriate connect string and data source.

� If you prefer, you can enter the appropriate data source name instead of a connect string.

You will then be connected directly to the specified data source.



Removing Java Thin Client

Removing Java Thin Client 10

Should you wish to remove Java Thin Client, you can run the uninstall script that was installed automatically in the Siebel Java Thin Client directory during installation, or remove the client manually.

To remove Java Thin Client from a UNIX client machine

1 Open a command shell window.

2 Change directory to the parent directory of the Java Thin Client installation directory.

3 Type the following commands exactly as shown:

rm -rf [directory]

The directory and all its contents will be removed.


Deploying Siebel Thin Client for Windows 11


Thin Client for Windows Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2

Deployment Sample Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3


Deploying Siebel Thin Client for Windows

About This Chapter


This chapter presents an example of a deployment of Siebel Thin Client for Windows.

Thin Client for Windows Scenario 11

Siebel Thin Client for Windows is a deployment option for customers who want to deploy their existing Siebel eBusiness Applications over the Internet or on their corporate intranet. Thin Client for Windows is a deployment option because customers do not have to perform additional configuration using Siebel Tools. The application configurations that were completed for dedicated clients can also be deployed through Thin Client for Windows.

For example, A. K. Parker’s PC sales division has an existing Siebel Call Center application that supports the call center agents when potential customers call or when agents are following up with customer leads. A. K. Parker wants to make the application available to satellite sales offices. Because A. K. Parker already has a fully functional Siebel Call Center application in use, the work required to implement Thin Client for Windows is minimal.

The next section, “Deployment Sample Steps,” provides a model for implementing Siebel Thin Client for Windows.

NOTE: There are a few exceptions in which dedicated client functions have yet to be supported on Thin Client for Windows. Please see Chapter 8, “Thin Client for Windows and Java Thin Client Overview,” for more information.



Thin Client for Windows Scenario

Deployment Sample Steps 11

Deploying Siebel Thin Client for Windows is a straightforward process. You must install the dedicated client for server administration and for debugging purposes, customize your Siebel application, install and configure Siebel Thin Client for Windows, and then test your Siebel application.

To deploy Thin Client for Windows

1 Install and customize a Siebel eBusiness Application, such as Siebel Call Center.

a Use Siebel Tools to customize the applets and views within the selected Siebel eBusiness Application.

b Install the dedicated client.

Every Siebel Thin Client for Windows deployment should contain at least one dedicated client installation. This is so that administrators can configure and administer the non-administrator client machines. Administrators use the dedicated client to set server component parameters, define workflow rules, and so on. In addition, the dedicated client can be a useful way to debug a thin client application.

2 Install Siebel Thin Client for Windows.

Please see Chapter 9, “Installing and Configuring Siebel Thin Client for Windows,” for instructions.



Thin Client for Windows Scenario

3 Configure Siebel Thin Client for Windows.

NOTE: The tclient.htm and tclient.stc start-up files are automatically configured during the Siebel Server installation. Neither administrator nor users should need to configure the tclient.htm or tclient.stc files.

� If thin client users will run the Siebel application using a Netscape browser, and you need to edit start-up parameters, edit tclient.stc.

� If thin client users will run the Siebel application using the Internet Explorer browser, and you need to edit start-up parameters, edit tclient.htm.

� If both Netscape and Internet Explorer browsers are in use among the thin client users, and you need to edit start-up parameters, you must edit both tclient.stc and tclient.htm.

� If the thin client users will run the stand-alone Thin Client for Windows, you do not need to edit start-up files.

4 Test your Siebel application by viewing it with Siebel Thin Client for Windows.

5 If necessary, you can run the application using the dedicated client if you need to debug the customizations in your Siebel application.


Java Thin Client and Thin Client for WindowsNetwork Requirements 12


Accessing the Thin Clients from Outside a Firewall . . . . . . . . . . . . . . . 12-2

Firewall Requirements in a Load-Balanced Environment . . . . . . . . . 12-2

Firewall Requirements in a Non-Load-Balanced Environment . . . . . . . . . .12-4


Java Thin Client and Thin Client for Windows Network Requirements

About This Chapter


This chapter outlines the network configuration requirements for deploying Siebel Java Thin Client and Siebel Thin Client for Windows. This information is particularly useful when deploying these applications across firewalls.

Accessing the Thin Clients from Outside a Firewall 12

One of the key advantages of Siebel Thin Client for Windows and Siebel Java Thin Client is the capability of allowing users to connect to Siebel eBusiness Applications through a remote connection. Enabling thin clients to connect to Siebel Servers over the Internet and through a firewall requires specific client/server, firewall, and network configurations.

Firewall Requirements in a Load-Balanced Environment 12

NOTE: Siebel Systems supports network address translation (NAT) with Resonate Central Dispatch installed. If Resonate Central Dispatch is not installed, network address translation (NAT) is not supported.

If you are using Resonate Central Dispatch to dynamically load-balance connections across the Enterprise Server, you need to expose only a single port through the firewall. The Siebel thin clients use this port to connect to the Siebel Gateway Server, which in turn forwards the connection to the Application Object Manager. In the load-balanced environment, the Application Object Manager supports connections using both TCP/IP and tunneled HTTP. If you are using TCP/IP, you must expose the TCP port of the Gateway Server (the default is 2320) through the firewall. If you are using HTTP, you need to expose only a generic HTTP port; the default HTTP port is 80.

If you are using load balancing, both HTTP and TCP/IP connections to Application Object Manager support firewalls that perform network address translation. However, neither can be used with a firewall that has a multiplexing application proxy. While the use of HTTP does create some overhead and can degrade response times, you may prefer it for firewall configurations requiring packet filtering or other stringent security measures.



Accessing the Thin Clients from Outside a Firewall

The Application Object Manager communications protocol is set as part of the definition of each Object Manager-defined component. As multiple defined components can operate in the Enterprise Server, it is possible to use a mix of HTTP and TCP/IP communications in your deployment; however, each Object Manager can use only a single protocol, and the start-up file for a thin client can only specify one Application Object Manager-defined component. See the Siebel Server Administration Guide for instructions on configuring the communication protocol for Application Object Manager.

NOTE: See “Editing the Java Thin Client Configuration File” on page 10-6 for information about configuring Java Thin Client. See the Siebel Server Installation Guide for instructions on configuring the thin client startup files for the ActiveX control and the Netscape plug-in. The stand-alone Thin Client for Windows does not require configuration.



Accessing the Thin Clients from Outside a Firewall

Firewall Requirements in a Non-Load-Balanced Environment 12

The firewall requirements are slightly different if you do not use load balancing in your Enterprise Server. The Application Object Manager only supports connections over TCP/IP in this environment. In addition to the Gateway Server TCP port (the default is 2320), the TCP port on which each Object Manager listens must also be exposed through the firewall. The Object Manager port is determined by the Object Manager configuration and can be allocated dynamically or statically.

To minimize the number of ports that must be opened through the firewall, it is recommended that you use static port allocation and create as small a number of Object Manager-defined components as possible.

NOTE: In the non-load-balanced environment, the Object Manager connection does not support network address translation, and does not support firewalls with multiplexing proxy servers.


Troubleshooting Thin Client for Windows andJava Thin Client 13

Troubleshooting Your Thin Client 13

As Java Thin Client and Thin Client for Windows are deployment platforms, there are several items you can check if your client is not functioning as expected:

� Check that you are connected to the Siebel Server.

� Make sure that the Siebel Server Object Manager component configuration file has the correct parameters; for example, make sure that the configuration file for Siebel Call Center, uagent.cfg, has the correct parameters, such as Database ConnectString and TableOwner.

� Verify that Siebel Servers and the Object Manager components to which Siebel Thin Client for Windows will be connecting are operating.

� Verify that the user login and password are correct.

� Make sure that each item in your connect string—including the Gateway Server, Enterprise Server, Object Manager, and Siebel Server setting—is correct.

� Verify that the configuration files used by Siebel Server have the correct data source setting; for example, make sure that the data source setting in uagent.cfg, located in \server\bin, is set correctly for Siebel Call Center.


Troubleshooting Thin Client for Windows and Java Thin Client

Troubleshooting Your Thin Client


H T M L T h i n C l i e n t I n s t a l l a t i o na n d C o n f i g u r a t i o n Part 4

Chapter 14. Siebel HTML Thin Client Overview

Chapter 15. Preparing to Install Siebel .COM Applications on Windows NT Server and UNIX Systems

Chapter 16. HTML Thin Client Network Requirements

Chapter 17. Troubleshooting


Siebel HTML Thin Client Overview 14


What’s New in This Release of HTML Thin Client . . . . . . . . . . . . . . . . 14-2

How Siebel HTML Thin Client Works . . . . . . . . . . . . . . . . . . . . . . . . . 14-3

What Is Siebel HTML Thin Client? . . . . . . . . . . . . . . . . . . . . . . . . . 14-4

Key Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4

What Happens When a User Enters a URL . . . . . . . . . . . . . . . . . . . . . 14-5

Where to Find Additional Information . . . . . . . . . . . . . . . . . . . . . . . . 14-8


Siebel HTML Thin Client Overview

About This Chapter


This chapter defines the concepts behind Siebel HTML Thin Client, the technology behind Siebel .COM Applications, and describes the architecture of an n-tiered system developed using Siebel HTML Thin Client.

NOTE: Siebel HTML Thin Client differs substantially from the other Siebel thin clients.

What’s New in This Release of HTML Thin Client 14

Version 6.0 of Siebel HTML Thin Client has several new features:

Feature Description

Applet and View Web Layout Editor Enables developers to graphically edit the Web layout of a .COM application in Siebel Tools.

Launch an external HTML editor from Siebel Tools

Enables developers to edit their HTML layout in an external editor, right after viewing the application layout in the Applet Web Layout Editor or the View Web Layout Editor.

Style and structure are reusable across multiple HTML display objects

Modifications to the style and structure can be easily propagated to all HTML display objects.

The new approach separates style and structure (style sheets and templates) from the binding (HTML display objects) to data. Applets and views (HTML display objects) are now based in the repository.

SmartScripts A Siebel option that enables business analysts, call center managers, and Siebel developers to define the application workflow for an interactive situation in a script. These situations include both inbound communications and outbound contacts.

Dynamic drilldown Dynamic drilldown enables hyperlink navigation to multiple views from the same hyperlink field, depending on the value of a field in the applet’s current record.

Personalization Records in an applet are targeted to each visitor using Siebel Personalization Manager based on visitor’s profile.



How Siebel HTML Thin Client Works

How Siebel HTML Thin Client Works 14

Siebel HTML Thin Client is a set of components for customizing and implementing the .COM Web applications based on Siebel object definitions, as shown in Figure 14-1. While the figure denotes Siebel HTML Thin Client components with a shaded box, the areas that are not shaded, such as the Web server and the database server, are integral to the HTML Thin Client technology.

Figure 14-1. HTML Thin Client Architecture

Siebel WebServer Extension

Web server

Web browser

Web application(generated HTML pages)

A shaded boxdenotes an

HTML Thin Clientcomponent

Database

Siebel Server

Application ObjectManager

Siebel WebEngine

Siebelapplicationdefinition

(.srf) Templates



How Siebel HTML Thin Client Works

What Is Siebel HTML Thin Client? 14

Siebel HTML Thin Client is a technology used for deploying the Siebel .COM Applications. The .srf definition of applications can be displayed using .swt files for HTML formatting and layout. Users of the Siebel .COM Applications can:

� View dynamically generated Web pages that include data from a Siebel database.

� Add to, delete, or modify data in a Siebel database.

� Perform queries, sorts, and other operations using any of the other thin clients or a dedicated client.

Siebel HTML Thin Client is part of a larger system that also includes Application Object Manager, Siebel Server, a database server, and a Web server, which together enable you to deploy and customize Siebel .COM Applications.

Key Components 14

Figure 14-1 on page 14-3 lists the key components of the HTML Thin Client system:

� Siebel Web templates. HTML pages that contain both standard HTML tags and Siebel tags. The Web application developer creates an application definition in Siebel Tools, associates templates for layout, and deploys the resulting application on a Web server, enabling users to access it through a Web browser.

� Siebel Web Engine. Joins template layout definition with repository-based application definition; this service inside Application Object Manager dynamically generates the HTML pages that make up the application’s user interface.

� Application Object Manager. The component of the Siebel Server that passes Siebel object definitions and data between the database and the Siebel Web Engine. These object definitions provide the application logic and enable the user to interact with the database.



What Happens When a User Enters a URL

What Happens When a User Enters a URL 14

Figure 14-2 illustrates what happens when a user enters your application’s URL, either by typing the URL and pressing ENTER or, more usually, by clicking a link.

The following steps describe the process illustrated in Figure 14-2.

1 A user with a browser sends the URL of your application to your Web server.

The user can do this by typing in the URL or clicking a link on your main site.

An example of this URL is:

http://www.mycompany.com/siebel/eService/start.swe?SWEView=ISS+Service+Request+View

2 The suffix of this URL (.swe) tells your Web server to direct the request to the Siebel Web Server Extension. For instance:

http://www.mycompany.com/siebel/eService/start.swe?SWEView=ISS+Service+Request+View

Figure 14-2. What Happens When a User Enters a URL

User’s WebBrowser

UserClicks

Web Server

� Pass all requestswith .swe extensionto Siebel WebEngine

Siebel Web Engine� Get or create state

information� Get or create object

manager session� Parse request to

pass to objectmanager

Siebel Web Engine

� Matches repositorydefinition of appletwith Siebel webtemplate file (.SWT)for layout

� Returns HTML

Siebel Object Manager

� Reads and/or writesdata

� Instantiates BO,Views, and applets




3 The Siebel Web Engine matches the virtual directory specified in the URL. It does this in one of two ways:

� In the above example, eapps.cfg, the configuration file, is located in the virtual directory sweapp/bin.

� On UNIX, it uses the file swe.conf.

The file swe.conf is referenced from Netscape Server configuration file obj.conf. The Siebel installer will add the reference to obj.conf. For example, here’s a typical line added to obj.conf:

Init fn="swe-init" config-file="/usr/netscape/suitespot/https-test/config/swe.conf"

4 The Siebel Web Engine reads the eapps.cfg file to find out:

� Which Gateway Server to direct the request to, and at which port

� The name of the Application Object Manager server (in case Resonate Central Dispatch is not being used)

5 The Web server directs the request through the Gateway Server to an available Siebel Web Engine and Application Object Manager server.

6 Application Object Manager determines the configuration file corresponding to the particular service (as set in the Configuration File component parameter for this Object Manager service).

For example, the Configuration File parameter might be set to esales.cfg.

7 Application Object Manager reads the configuration file (located in the Siebel Server’s \bin directory) to find out the application name and the name of the .srf file.

For example, one of the parameters in the configuration file may identify the application name as Siebel eSales—Thin and the .srf file as siebel.srf.




8 The ApplicationName parameter tells Application Object Manager which application definition (from the .srf file in the \objects directory) to use for retrieving data.

9 The Siebel Web Engine retrieves data from the database and the repository definition of the views and applets through the Application Object Manager.

10 From the request, the Siebel Web Engine determines which .swt file to use. It will then parse the .swt file for the Siebel tags.

11 The Siebel Web Engine generates the HTML file based on the .swt file, the Siebel data, and the repository definition of the views and applets, and sends it back to the Web server.

12 The Web server receives the generated HTML file from the Siebel Web Engine and passes it back to the browser.

For instructions on configuring your servers and application to enable this flow of events, see Chapter 15, “Preparing to Install Siebel .COM Applications on Windows NT Server and UNIX Systems,” Configuring Siebel .COM Applications, and the Siebel Server Installation Guide.



Where to Find Additional Information

Where to Find Additional Information 14

For questions not answered in this guide, refer to the other available sources of information listed in Table 14-1.

For copies of these documents, contact Siebel Books Online, on the Siebel Systems Web site (www.siebel.com).

Table 14-1. Additional Information About Siebel HTML Thin Client

For Information About See

Installing the .COM applications, which are supported by Siebel HTML Thin Client technology

Siebel Server Installation Guide

How Siebel HTML Thin Client components interact with Siebel Servers

Siebel Server Administration Guide

Using Siebel Tools to configure applications Siebel Tools Guide

Siebel eService, eSales, and eChannel, which are part of the Siebel .COM Applications and based on Siebel HTML Thin Client technology

Siebel .COM Applications Guide

Customizing your Siebel .COM Applications using Siebel HTML Thin Client technology

Configuring Siebel .COM Applications


Preparing to Install Siebel .COM Applicationson Windows NT Server and UNIX Systems 15



Verifying Thin Client Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2

Planning the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3

Verifying the Siebel Enterprise Server . . . . . . . . . . . . . . . . . . . . . . 15-5

Verifying Web Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . 15-5

Installing Siebel .COM Applications . . . . . . . . . . . . . . . . . . . . . . . . . 15-6

Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-6


Preparing to Install Siebel .COM Applications on Windows NT Server and UNIX Systems

About This Chapter


This chapter describes the pre-installation tasks for Siebel .COM Applications under Windows NT and UNIX. The installation steps are documented in the Siebel Server Installation Guide.

The Web Engine is installed as part of the Siebel Server installation, and the Siebel .COM Applications are installed on the same machine as the Web Server host to support Siebel HTML Thin Client technology. As with Siebel Thin Client for Windows and Siebel Java Thin Client, the .COM applications connect to the Application Object Manager, in this case executing the Siebel Web Engine.


You must complete the following pre-installation tasks before you begin installing Siebel .COM Applications:

� Verifying Thin Client Platforms

� Planning the Installation on page 15-3

� Verifying the Siebel Enterprise Server on page 15-5

� Verifying Web Server Requirements on page 15-5


You must verify that the client machines on which you will operate Siebel .COM Applications have the following:

� Required hardware and software components, including a Web browser, installed and configured, as specified in the Siebel Release Notes.





Planning the Installation 15

Siebel Web Engine is one of several software components that are installed to support Siebel HTML Thin Client technology and the .COM applications. The Siebel Web Engine is automatically installed along with the Siebel Server. Siebel HTML Thin Client technology also requires a Web server (Netscape for Solaris installations and Microsoft IIS for Windows NT installations).

Before beginning the installation process, consider how you will distribute these software components. There are two possible deployment topologies:

� Single-node, in which all components are operated on a single server

� Distributed, in which the components are distributed across multiple application servers

Single-Node InstallationIn a single-node installation, recommended only for development and testing purposes, all the server-side components are installed on one machine (or node). These are:

� The Web server (Microsoft IIS for Windows NT installations and Netscape for Solaris installations)

� Application Object Manager and Siebel Web Engine

Each client’s browser (in which the Web application appears at run time) would be installed on a separate node, such as on each user’s laptop or other personal computer.

Distributed InstallationThe recommended production deployment topology is to distribute the HTML Thin Client components among two or more machines. The recommended distributed configuration has each component (Web server and Application Object Manager) on a separate machine.

NOTE: In both the single-node and distributed configurations, the database server resides on a separate node.




Advantages of Each ConfigurationThe single-node installation is recommended for a development and testing environment because it is easier to manage than a distributed installation.

For a production environment, a distributed installation offers the following advantages over a single-node installation:

� Less resource contention. If the Web server is on a single-processor machine, having the Application Object Manager and Siebel Web Engine on another machine reduces contention for CPU and other resources. However, to take advantage of the performance improvement, you must have a high-speed network connection between the two machines.

� Load balancing. A single Web server can distribute the load of multiple user requests among multiple installations of Application Object Manager, using the connection-brokering capabilities of Siebel Gateway Server.

� Higher fault tolerance. Balancing the load across multiple machines reduces the chance of system failure and downtime, particularly if you have multiple installations of Application Object Manager.

� Greater flexibility with firewalls. Installing the Web server on a different machine from the Application Object Manager enables you to deploy your Web server outside the firewall while keeping Application Object Manager behind the firewall.

Because of these advantages, a multi-node configuration is strongly recommended for deployments that support large numbers of concurrent users or where high availability is an operating requirement.





Before installing the Siebel .COM Applications, you must have completed the installation of the Siebel Database Server and Siebel File System, and have installed and configured an Enterprise Server containing the Gateway Server and at least one Siebel Server. Complete the steps in your Siebel Server Installation Guide to install and configure the Enterprise Server entities, following the configuration chosen in the previous pre-installation task, “Planning the Installation” on page 15-3.

NOTE: It is strongly recommended that you implement the connection-brokering capabilities of the Siebel Gateway Server if you will support the thin client software from multiple Siebel Servers. These capabilities help to provide high scalability and availability for your thin client users. Refer to your Siebel Server Installation Guide for more information on connection brokering.

If you or someone else filled out the Deployment Planning Worksheet (in the Siebel Server Installation Guide) before installing your Siebel servers, make a copy and keep it with you while installing the thin client components. Otherwise, make a note of the Siebel Enterprise Server name and the IP address (or VIP if you are using Central Dispatch) of the Gateway Server, as well as the name of the Object Manager-defined components operating on the Enterprise Server.

You will need this information when configuring the client start-up files.

Verifying Web Server Requirements 15

Ensure that the application server that will support the Siebel Web Engine meets all the Siebel Server hardware and software platform requirements documented in the Siebel Release Notes. You must also install and configure a Web server for your platform:

� For Windows NT servers, install Microsoft IIS on the application server. Follow the documentation provided by Microsoft to complete this task.

� For UNIX servers, install and configure Netscape Enterprise Server on the application server. Follow the documentation provided by Netscape to complete this step.



Installing Siebel .COM Applications

Installing Siebel .COM Applications 15

In the version 6.0 release of Siebel Server, Siebel Web Engine supports Windows NT Web servers running Microsoft Internet Information Server (IIS) and Sun Solaris (UNIX) Web servers running Netscape Enterprise Server.

NOTE: There is no client component installation for Siebel .COM Applications. The only software that must be installed on each client machine are a Web browser and network connectivity software. All the Siebel components for the HTML Thin Client technology and Siebel .COM Applications are stored on the server.

Because the HTML Thin Client components are part of the Siebel Server installation and the Siebel .COM Applications installation (both server installations), the installation steps are documented in the Siebel Server Installation Guide.

Configuration Files 15

The information supplied during the .COM application installation is written to a configuration file, eapps.cfg, that supports the Siebel .COM Applications.

If you move one of the server-side components to another machine, you must edit the eapps.cfg file with the new information. In addition, you can edit the configuration file to change .COM application-specific preferences, such as timeout interval, logging level, and so on.

See the Siebel Server Installation Guide for information about editing the parameters contained in the eapps.cfg installed with the .COM Applications.


HTML Thin Client Network Requirements 16


Firewall Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3

Browser to Web Server Connection . . . . . . . . . . . . . . . . . . . . . . . . 16-4

Web Server Extension to Application Object Manager Connection . . . 16-4

Firewall Requirements in a Load-Balanced Environment . . . . . . . . . . . . 16-5

Firewall Requirements in a Non-Load-Balanced Environment . . . . . . . . 16-6


HTML Thin Client Network Requirements

About This Chapter


This chapter provides information on the network configuration requirements for HTML Thin Client and the .COM applications. This information is particularly useful when deploying these applications across firewalls.



Firewall Configuration

Firewall Configuration 16

Figure 16-1 shows one possible network configuration for deploying Siebel HTML Thin Client. Your actual configuration will vary depending on the firewall hardware or software and security standards of your organization; however, the requirements outlined here apply across all configurations and should be used as the guidelines for your environment.

Figure 16-1. Two Firewalls to Protect Data on the Servers

Siebel WebServer Extension

Web server

Web browser

Web application(generated HTML pages)

External firewall

HTTP port

Siebel ObjectManager

Internal firewall

TCP/IP port

Siebel Web EngineSiebelapplicationdefinition

(.srf)

A shaded boxdenotes an

HTML Thin Clientcomponent

Database

Templates



Firewall Configuration

In an HTML Thin Client deployment, there are two distinct network connections: the Web browser connection to the Web server and the Siebel Web Server Extension connection to the Siebel Application Object Manager component running on the Siebel Enterprise Server. These connections have unique requirements, particularly for firewall configuration. Each is discussed in turn.

Browser to Web Server Connection 16

The Web browser uses a standard HTTP or SSL connection to the Web server. Typically this connection requires only that the firewall be able to pass HTTP or SSL traffic to a single port on the Web server. These requirements are determined entirely by the configuration of your browsers and Web server; refer to the documentation provided by the product vendors for more information on supported firewall configurations in these environments. Usually these connections can be supported over VPNs, through firewalls that perform network address translation, through multiplexing proxies, and so on.

NOTE: The use of SSL does impose some overhead that can degrade performance. For that reason, Siebel Systems recommends its use only in those portions of your application configuration where network security is critical, such as transfers involving login information.

Web Server Extension to Application Object Manager Connection 16

The Siebel Web Server Extension, operating on the Web server, connects to the Application Object Manager component operating within the Siebel Enterprise Server. This connection uses Siebel's application protocol, which is compressed by default and can also be encrypted when both components are deployed on Windows NT.

The supported configurations for a firewall between the Web server and Siebel Enterprise Server vary depending on whether you are using dynamic load balancing in the Enterprise Server.



Firewall Requirements in a Load-Balanced Environment

Firewall Requirements in a Load-Balanced Environment 16

NOTE: Siebel Systems supports network address translation (NAT) with Resonate Central Dispatch installed. If Resonate Central Dispatch is not installed, network address translation (NAT) is not supported.

If you are using Resonate Central Dispatch to dynamically load-balance connections across the Enterprise Server, you need to expose only a single port through the firewall. The Web Server Extension uses this port to connect to the Siebel Gateway Server, which in turn passes the connection to the Application Object Manager. In the load-balanced environment, the Application Object Manager can be configured to support connections over TCP/IP and tunneled HTTP. If you are using TCP/IP, you must expose the TCP port of the Gateway Server (the default is 2320) through the firewall. If you are using HTTP, you need to expose only a generic HTTP port (the default is 80).

If you are using load balancing, both HTTP and TCP/IP connections to the Application Object Manager support firewalls that perform network address translation. However, neither can be used with a firewall that has a multiplexing application proxy. While the use of HTTP does create some overhead and can degrade response times, you may prefer it for firewall configurations requiring packet filtering or other stringent security measures.

The Application Object Manager communications protocol is set as part of the definition of each Application Object Manager-defined component. As multiple defined components can operate in the Enterprise Server, it is possible to use a mix of HTTP and TCP/IP communications in your deployment; however, each Application Object Manager can use only a single protocol, and each Web Server Extension can only connect to one defined component. See the Siebel Server Administration Guide for instructions on configuring the communication protocol for the Application Object Manager.

NOTE: See the Siebel Server Installation Guide for information about modifying the configuration files for Siebel .COM Applications.



Firewall Requirements in a Non-Load-Balanced Environment

Firewall Requirements in a Non-Load-Balanced Environment 16

The firewall requirements are slightly different if you do not use load balancing in your Enterprise Server. The Object Manager connection can only use TCP/IP in this environment. In addition to the Gateway Server TCP port (the default is 2320), the TCP port on which each Object Manager listens must also be exposed through the firewall. The Object Manager port is determined by the Object Manager configuration and can be allocated dynamically or statically. To minimize the number of ports that must be opened through the firewall, it is recommended that you use static port allocation and create as small a number of Object Manager-defined components as possible.

NOTE: In the non-load-balanced environment, the Object Manager connection does not support network address translation, and does not support firewalls with multiplexing proxy servers.


Troubleshooting 17

General Troubleshooting Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2

Windows NT Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2

Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2

Object Manager Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2

Using a Single .srf and .cfg File for Troubleshooting . . . . . . . . . . . . 17-3

Visual Basic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3

Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3

Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-4


Troubleshooting

General Troubleshooting Tips

General Troubleshooting Tips 17

This section provides suggestions for troubleshooting problems you may encounter.

Windows NT Services 17

Stopping and restarting the following Windows NT services solves some problems:

� IIS Admin Service

� World Wide Web Publishing Service

Configuration Files 17

If you’ve moved any components of your installation, including the Application Object Manager or the Gateway Server, you must make the appropriate changes in the configuration files. For details about the Siebel .COM Applications .cfg files, see the Siebel Server Installation Guide.

Object Manager Configuration 17

You may need to reset some Application Object Manager parameters. These include:

� Maximum MT Servers

� Maximum Tasks

� Configuration File

� Static Port Number

For information, see the Application Object Manager chapter of the Siebel Server Administration Guide.


Troubleshooting

General Troubleshooting Tips

Using a Single .srf and .cfg File for Troubleshooting 17

If you’re having problems with your HTML-based application, try running this application through the Siebel dedicated client. That is, set up your Siebel dedicated client to use the same .srf file and the same Application Object Manager configuration file (such as Siebel.cfg) as used by the HTML Thin Client application.

For instance, you could create a shortcut that calls an instance of the dedicated client, but with the flag /c c:\SiebelServer\bin\ThinClient.cfg, where the string after the flag is the name and location of the .cfg file that the thin client is using. The shortcut will start a dedicated client using the same parameters and repository as the thin client.

You should be able to see the same set of records through the dedicated client and through HTML Thin Client. If you are unsure about a certain behavior you are seeing in HTML Thin Client, try using the dedicated client to perform a similar operation, using the same .srf and .cfg file, and the same user name and password. For example, if a query or picklist does not have the expected result, try the same operation with the dedicated client.

Visual Basic 17

If your application uses VB scripts and an error occurs, you can tell whether the error is caused by VB by turning off VB. Specifically, on the SOM, edit the configuration file (such as Siebel.cfg) to set EnableBASIC to FALSE.

Log Files 17

When a problem occurs, check the various available log files to discover the cause. For more information, see the following section, “Log Files” on page 17-4.


Troubleshooting

Log Files

Log Files 17

For each Internet application, Siebel Web Engine generates one or more log files. Depending on the logging level you choose, these files log errors, warnings, and general information. Analyzing the log files can provide clues as to how you can improve the performance of your application.

In addition, Siebel Web Engine itself creates log files. See the Siebel Server Installation Guide for more information about the log files that are created during the Siebel Web Engine and .COM applications installations.


A p p e n d i c e s Part 5

Appendix A. Index of Configuration Parameters

Appendix B. Siebel.cfg Configuration Parameters

Appendix C. Limiting Views to the Thin or Dedicated Client

Appendix D. Optimizing Thin Client Performance

Appendix E. UNIX-Supported Business Component Classes


Index of Configuration Parameters A

Appendix Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-2

Configuration Parameters Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-2

Version 6.2, Rev. A Siebel Client Installation and Administration Guide A-1

Index of Configuration Parameters

Appendix Overview

Appendix Overview A

This appendix lists configuration parameters in alphabetical order, with cross-references to the page that documents each one and the configuration file in which it can be found. The list contains dedicated client, mobile client, and thin client configuration parameters.

NOTE: This appendix does not document the parameters. It provides a cross-reference to the location in this guide where you can find the documentation for each parameter.

Configuration Parameters Index A

Table A-1 contains an alphabetical listing of Siebel client configuration parameters, showing the configuration files in which each one can be found and the page that documents each one.

NOTE: Because there is no client component to the installation of Siebel HTML Thin Client, the parameters for HTML Thin Client are not described in this guide. See the Siebel Server Installation Guide for information about the Siebel .COM Applications configuration files.

Table A-1. Siebel Configuration Parameters in Alphabetical Order (Sheet 1 of 7)

Configuration Parameter Name Configuration File Name Documented on Page

AccessDir siebel.cfg B-3

AnonPassword eapps.cfg Siebel Server Installation Guide

AnonUserName eapps.cfg Siebel Server Installation Guide

AnonUserPool eapps.cfg Siebel Server Installation Guide

AppletTitleFont siebel.cfg B-3

ApplicationName siebel.cfg B-3

A-2 Siebel Client Installation and Administration Guide Version 6.2, Rev. A


Configuration Parameters Index

ApplicationSplashText siebel.cfg B-3

BaseDN siebel.cfg B-21

Browser siebel.cfg 10-9

CaptionPrefix siebel.cfg B-3

CaseInsensitive siebel.cfg B-8

ClientFileServSupport siebel.cfg B-3

ClientRootDir siebel.cfg 5-9, B-3

Colors siebel.cfg 10-10

ComponentName siebel.cfg B-3

ConfiguratorDLLName siebel.cfg B-16

ConfiguratorExeDir siebel.cfg B-16

ConfiguratorExeFileName siebel.cfg B-16

ConfiguratorModelDir siebel.cfg B-16

ConfiguratorModelExportFileName siebel.cfg B-16

ConnectString siebel.cfg B-8

ContactLogin siebel.cfg B-8

CorbaDLL siebel.cfg B-3

CorrespODBCDataSource siebel.cfg B-3

CredentialsAttributeType siebel.cfg B-21

DataMart siebel.cfg B-7

DataSource siebel.cfg 10-8, B-3

DateYearFormat siebel.cfg 10-8, 10-11

DecimalNumberScale siebel.cfg 10-8

DefaultChartFont siebel.cfg B-3






DefaultFont siebel.cfg 10-10

Dir siebel.cfg B-17 (DataCleansing), B-18 (Data DeDuplication)

DLL siebel.cfg B-8

DllName siebel.cfg B-21

DockConnString siebel.cfg 5-9, B-8

Docked siebel.cfg B-8

DockRecvTxnsPerCommit siebel.cfg B-8

DockRepositoryName siebel.cfg 5-10, B-3

DockTxnsPerCommit siebel.cfg 5-11, B-8

Enable siebel.cfg B-17 (DataCleansing), B-18 (Data DeDuplication)

EnableCORBA siebel.cfg B-4

EnablePersonalization siebel.cfg B-4

EnableOLEAutomation siebel.cfg B-4

EnableScripting siebel.cfg B-4

EncryptCredentialsPassword siebel.cfg B-21

EncryptPassword siebel.cfg B-4

EnterpriseServer siebel.cfg B-9

ExtensionType siebel.cfg B-9

FileSystem siebel.cfg 5-11, B-4

Finish setup.ini 9-14

Gateway siebel.cfg B-7

GatewayAddress siebel.cfg B-9

GatewayServer tclient.htm and tclient.stc Siebel Server Installation Guide






Height tclient.htm and tclient.stc Siebel Server Installation Guide

HelpFile siebel.cfg B-4

Hidden siebel.cfg B-9

HideBackground setup.ini 9-12

HoldExportODBCConnection siebel.cfg B-4

html siebel.cfg 10-9

InsensitivityFactor siebel.cfg B-9

InsUpdAllCols siebel.cfg B-9

IntegratedSecurity siebel.cfg B-10

InternalConnectString siebel.cfg B-10

JSECorbaConnector siebel.cfg B-5

JTCHelpURL siebel.cfg B-5

Lang tclient.htm and tclient.stc Siebel Server Installation Guide

LargeDataFont siebel.cfg B-5

LargeFont siebel.cfg B-5

LDAP siebel.cfg B-20

Local siebel.cfg B-7

LocalDbODBCDataSource siebel.cfg B-5

Login tclient.htm and tclient.stc Siebel Server Installation Guide

MainRepositoryName siebel.cfg B-5

MaxCachedCursors siebel.cfg B-10

MaxCachedDataSets siebel.cfg B-10

MaxConnections siebel.cfg B-10

MaxCursorSize siebel.cfg B-10






MultiCurrency siebel.cfg B-5

NavBarItemFont siebel.cfg B-5

NavBarSelectFont siebel.cfg B-6

NavBarTitleFont siebel.cfg B-6

NetworkPacketSize siebel.cfg B-10

NoExtension siebel.cfg 10-10

NonSQL siebel.cfg B-10

ObjectManager tclient.htm and tclient.stc Siebel Server Installation Guide

OLEAutomationDLL siebel.cfg B-6

OLEMessagePendingDelay siebel.cfg B-6

PasswordAttributeType siebel.cfg B-21

PersonalizationLog siebel.cfg B-6

Placeholder siebel.cfg B-10

Port siebel.cfg B-21

PrefetchSize siebel.cfg B-10

PrimaryEnterprise siebel.cfg B-10

ReportsDir siebel.cfg B-6

ReportsODBCDataSource siebel.cfg B-6

RepositoryFile siebel.cfg B-6

RequestComponent siebel.cfg B-11

RequestServer siebel.cfg B-11

ReverseFillThreshold siebel.cfg B-11

RolesAttributeType siebel.cfg B-22

RootDirectory setup.ini 9-14






Sample siebel.cfg B-7

SAPIdocAllowedObjects siebel.cfg B-19

SAPRfcConnectString siebel.cfg B-19

SAPRfcDestEntry siebel.cfg B-19

SAPRfcPassword siebel.cfg B-19

SAPRfcUserName siebel.cfg B-19

ScriptingDLL siebel.cfg B-6

SearchCheckStatus siebel.cfg B-11

SearchCharacterSet siebel.cfg B-11

SearchConnectString siebel.cfg B-11

SearchDefName siebel.cfg B-11

SearchDisableViewer siebel.cfg B-11

SearchStyle siebel.cfg B-11

SearchTermGenerator siebel.cfg B-11

SearchThesaurus siebel.cfg B-11

SecurityAdapter siebel.cfg B-11

Server siebel.cfg B-7, B-11

ServerName siebel.cfg B-22

SharedModeUsersDir siebel.cfg B-6

ShowMessageBar siebel.cfg B-6

SiebelEnterprise tclient.htm and tclient.stc Siebel Server Installation Guide

SiebelServer tclient.htm and tclient.stc Siebel Server Installation Guide

SmallDataFont siebel.cfg B-6

SmallFont siebel.cfg B-7






SqlStyle sieble.cfg B-12

SslDatabase siebel.cfg B-22

StatsPage eapps.cfg Siebel Server Installation Guide

SupportsIntegratedAuthentication siebel.cfg B-22

TableOwner siebel.cfg 5-10, B-12

TempDir siebel.cfg B-7

Type siebel.cfg B-17 (DataCleansing), B-18 (Data DeDuplication)

UpperCaseLogin siebel.cfg B-12

UsernameAttributeType siebel.cfg B-22

Version siebel.cfg B-7

View1 siebel.cfg B-15

View2 siebel.cfg B-15

Welcome setup.ini 9-13

Width tclient.htm and tclient.stc Siebel Server Installation Guide




Siebel.cfg Configuration Parameters B

Generic Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-2

Client and Server Application Parameters . . . . . . . . . . . . . . . . . . . . . . . . . B-3

Datasources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-7

Properties of DataSources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-8

Actuate Reports Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-15

Preload Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-15

Product Configurator Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . B-16

DataCleansing Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-17

DeDuplication Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-18

SAP Subsystem Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-19

Security Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-20

LDAP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-21

Internet Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-24

Version 6.2, Rev. A Siebel Client Installation and Administration Guide B-1

Siebel.cfg Configuration Parameters

Generic Configuration Parameters

Generic Configuration Parameters B

This chapter lists and defines parameters in the siebel .cfg configuration files. The name of the .cfg file will vary, depending on the application you are using. Use this information to determine which parameters you must set to achieve optimal performance and enable the features you require.

The information contained within this section is as follows:

� “Siebel Application Parameters” on page B-3

� “DataSources” on page B-7

� “Properties of DataSources” on page B-8

� “Actuate Reports Parameters” on page B-15

� “Preload Parameters” on page B-15

� “Product Configurator Parameters” on page B-16

� “DataCleansing Parameters” on page B-17

� “DeDuplication Parameters” on page B-18

� “SAP Subsystem Parameters” on page B-19

� “Security Adapters” on page B-20

� “LDAP Parameters” on page B-21

� “Internet Parameters” on page B-24

B-2 Siebel Client Installation and Administration Guide Version 6.2, Rev. A



Client and Server Application Parameters B

Table B-1 defines Siebel application parameters.

Table B-1. Siebel Application Parameters (Sheet 1 of 5)

Name Description

AccessDir Directory where Microsoft Access is installed.

AppletTitleFont Font to use in the applet title. The font settings are for the user interface. AppletTitleFont controls the font for the title control for applets.

ApplicationName Name of application object in repository to use (Siebel Sales, Siebel Service, and so on). The ApplicationName setting determines which splash screen appears and which set of menus is enabled.

ApplicationSplashText Text that appears on the application splash screen when starting up a Siebel application.

The default varies by the application. If you are starting Siebel Sales, for example, the ApplicationSplashText is set to Siebel Sales by default.

CaptionPrefix Allows customizing of the title in the upper left hand corner of the Siebel client application. Reads Siebel by default.

ClientFileServSupport TRUE or FALSE.

ClientRootDir Directory where client software is installed.

ComponentName This parameter specifies the Siebel Anywhere configuration that should be used during version check. Navigate to the Siebel Anywhere Administration� Configurations view to see the configurations.

Change the setting for this parameter if you want this .cfg file to be version checked by a specific Siebel Anywhere configuration.

For example, if you want to version check the office in one city separately from the office in another city, create two Siebel Anywhere configurations appropriately named, then in the .cfg file for each set of users, enter a different value for the ComponentName entry.

CorbaDLL The Siebel extension language for CORBA.

CorrespODBCDataSource Name of ODBC data source used by mail merges and correspondence.

DataSource Name of default data source as defined in the .cfg file.

DefaultChartFont Font name specification for chart applets. Defaults to Arial-10 normal.

DockRepositoryName Obsolete.




EnableCORBA EnableCORBA is used to load CORBADLL. For all installations except CORBA Object Manager, this flag is FALSE by default.

When using a configuration file with one of the CORBA Object Manager executables, ssomorbx.exe or ssomvisi.exe, the CORBA Object Manager installer sets the EnableCORBA parameter to TRUE.

EnableOLEAutomation TRUE or FALSE. Enables OLE interfaces.

EnablePersonalization Must be set to TRUE to activate the personalization (content targeting) functionality.

EnableScripting TRUE or FALSE. Enables use of Siebel Visual Basic or Siebel eScript.

EncryptPassword Determines whether to encrypt user’s password before passing it the RDBMS. Used by customers who do not want their users to directly log into the server database using SQL*Plus or some other RDBMS tool other than Siebel. When enabled, Siebel applies a simple encryption algorithm to the password before it is sent to the database. This occurs when users attempt to login to Siebel with their password. The users’ Oracle login would also have to have been setup with the encrypted version of the password. Siebel has a special utility to help the administrator set these up.

FileSystem Where the Siebel File Server resides.

HelpFile Help file for the current configuration.

HoldExportOdbcConnection This option applies to Access reports and Correspondence only. It does not apply to Actuate reports which use OLE to retrieve data.

TRUE or FALSE. This parameter tells Siebel to disconnect from, or to keep the connection with, the Microsoft ODBC data source after Siebel has exported data into a staging database during a report generation or correspondence mail merge. Siebel engineers have found that keeping the connection is more stable than not. If the option is turned off, then the ODBC jet engine driver (ODBCJT32.DLL) from Microsoft will consistently crash on the second disconnect attempt.


Name Description




JSECorbaConnector Required for eScript CORBA support (if you are using Siebel eScript and calling CORBA from eScript). Defines the name of the eScript CORBA extension DLL.

Change this setting, depending on the CORBA ORBs (Object Request Broker) that you are using:

� Use corbavgn.dll for Inprise Visibroker

� Use corborbx.dll for Iona ORBIX

The default setting for this parameter is corbavgn.dll.

Note that the ScriptingDLL parameter must be set to sscfjs.dll to select Siebel eScript as the scripting language. By default, the ScriptingDLL parameter is set to Visual Basic.

JTCHelpURL A server parameter that defines the location of the online help for Java Thin Client provided by Siebel Systems. Set this parameter to the location where the help file was copied from the CD-ROM. When Java Thin Client users press the F1 key, Siebel launches the help file.

The [File Extension] section of the client siebel.cfg file determines the browser with which the help file is launched.

LargeFont Font to use when Siebel calls for large font.

LargeDataFont Use in the list applets when Siebel calls for a large font.

LocalDbODBCDataSource Name of the ODBC datasource that is set up to access the local database. It is used by a variety of features in the Siebel eBusiness Applications and in Siebel Tools. It should not need to be modified as it is correctly configured by the installation program.

MainRepositoryName Repository this configuration should run against.

MainRepositoryName is different from the RepositoryFile parameter. RepositoryFile is the physical file that is read that contains all runtime object definitions, while MainRepositoryName is used in cases where some part of the code must connect to the database to obtain information from the repository.

MultiCurrency TRUE or FALSE. Enables multi-currency support.

NavBarltemFont The NavBar settings affect the Page Tabs and the Viewbar areas. Font to use for the Navigation Bar text.


Name Description




NavBarSelectFont Font to use when a Navigation Bar item is selected.

NavBarTitleFont Font to use for titles in the Navigation Bar (View bar’s title area).

OLEAutomationDLL Name of .DLL that implements OLE interfaces.

OLEMessagePendingDelay Controls the amount of time that Siebel will wait for an OLE server to respond to a request before a "Server not responding ..." timeout message appears.

The default setting is 8 seconds. The most common use is to increase the timeout on slow computers so that the timeout message does not appear as frequently.

PersonalizationLog Add PersonalizationLog= "c:\personalization.txt" to siebel.cfg to view a log of all personalization activity, where c is the drive letter where you want to store the log. The log may assist in the process of debugging your rules, events, and actions.

ReportsDir Directory where reports are installed. Typically left blank.

ReportsODBCDataSource Name of ODBC data source used by Access reports.

RepositoryFile Name of the Siebel.SRF file to use.

RepositoryFile is different from the MainRepositoryName parameter. RepositoryFile is the physical file that is read that contains all runtime object definitions, while MainRepositoryName is used in cases where some part of the code must connect to the database to obtain information from the repository.

ScriptingDLL Name of the shared library that implements Siebel Visual Basic or Siebel eScript. If you are running a Unix server (AIX or Solaris) and plan on using eScript, set the value of ScriptingDLL to sscfjs.so.

SharedModeUsersDir Directory where user preference files are stored. Typically left blank. If setting SharedModeUsersDir, it must be set to a directory under a network shared drive, but it cannot be set to the shared drive itself.

For example, if \\yourserver\common is the network shared drive, you cannot set SharedModeUsersDir to \\yourserver\common. Instead, set SharedModeUsersDir to a directory under \common.

ShowMessageBar TRUE by default. This client parameter should be set to FALSE to remove the message box at the bottom of the Siebel application window.

SmallDataFont Use in the list applets when Siebel calls for a small font.


Name Description




Datasources B

Table B-2 lists DataSources in the Siebel Configuration file.

SmallFont Font to use when Siebel calls for a small font.

TempDir Directory where temporary files should be created.

Version Represents version of file. This parameter is for internal use only and is automatically maintained by Siebel Anywhere. When the customer creates an upgrade kit for the .cfg file, Siebel Anywhere increments this version string appropriately, based on the version information from the Upgrade Components screen.Note that when you perform a Siebel Anywhere upgrade, you must manually upgrade files from the upgraded Siebel client directory to the Siebel server directory.


Name Description

Table B-2. DataSources

Name Function

Local Defines local database name

Sample Defines sample database name

Server Defines Server database name

Gateway Defines Gateway

DataMart Defines the DataMart database name




Properties of DataSources B

Table B-3 lists the properties associated with the different DataSources. The previous table, Table B-2 on page B-7, defines defines each DataSource name. Each DataSource must have its own section that defines the properties of the DataSource. Sample DataSource sections are shown in “Sample DataSource Sections in the Siebel.cfg File” on page B-12.

Table B-3. Properties of DataSources (Sheet 1 of 5)

Name Comment

CaseInsensitive TRUE or FALSE. If TRUE, notifies the client to work with the database in case-insensitive mode.

Note that queries against fields of type DTYPE_ID are always case-sensitive, even if the CaseInsensitive parameter is set to TRUE.

ConnectString Database-dependent string that defines how to connect to the database. The -Q option hides the SQL Anywhere icon. The -c8 option indicates the cache size and the -m option indicates to the SQL Anywhere database engine to truncate the transaction log after each checkpoint.

ContactLogin TRUE or FALSE. If TRUE, indicates that the corresponding datasource uses contact login, rather than employee login. Because a contact user is generally not associated one-to-one with a database account, you must use a security adapter to support contact users.

If FALSE, the datasource is using employee login, rather than contact login.

DLL Name of .DLL file to use for the database connector code. They differ depending upon whether you are using Oracle, SQL Server, Sybase, and so on.

DockConnString ODBC source to the docking server. The DockConnString in the [local] section contains the machine name of the Enterprise Server, and is not an ODBC data source.

Docked TRUE or FALSE. Designates whether database is mobile or connected to server.

DockRecvTxnsPerCommit Number of transactions received by the mobile client before a commit is issued to the database. The default value for this parameter is 10. Change the setting to:

� A higher value if you have a fast network connection, such as a LAN. Increasing the value can provide better performance when synchronizing the mobile client with the server.

� A small value if you have a lower bandwidth network connection, such as a modem.

DockTxnsPerCommit Number of transactions processed before a commit is issued to the database.




EnterpriseServer Name of the Siebel Enterprise Server.

ExtensionType TRUE or FALSE. Determines if the data source shows up in the login dialog’s picklist of data sources to which to connect.

GatewayAddress Name of the Siebel Gateway Server.

Hidden TRUE or FALSE. Determines if the data source shows up in the Siebel login dialog’s picklist of data sources.

InsensitivityFactor Set to a positive integer value (default is 2). Only applies when the datasource’s CaseInsensitivity setting is TRUE. The value controls the number of characters in each string that will be treated as case-insensitive in a query. Not all database vendors support case-insensitivity efficiently, so this feature provides an approximate solution. Below is an example of the SQL WHERE clause generated when searching for an Opportunity named New when the InsensitivityFactor is set to 2.

WHERE

((S_OPTY.NAME LIKE ‘ne%’ OR

S_OPTY.NAME LIKE ‘Ne%’OR

S_OPTY.NAME LIKE ‘nE%’OR

S_OPTY.NAME LIKE ‘NE%’)

AND

UPPER(S_OPTY.NAME)=UPPER(‘New’))

The above example shows that all permutations of the first 2 letters of the string ‘New’ are checked. With a higher factor, the number of permutations grows exponentially, and performance will suffer.

InsUpdAllCols TRUE or FALSE. Ordinarily when Siebel generates INSERT or UPDATE statements to send to the database, the actual statement only contains the columns where data is present or has changed. When there are situations where we generate many statements on a particular table, the differences in the values being updated may cause us to not be able to use an array interface supported by the DBMS. When this feature is on (set to TRUE) all columns are present in all INSERT and UPDATE statements. This automatically enables 2 statements issued against the same table in the same business component as part of a batch operation to be able to use any existing array feature of the DBMS.


Name Comment




IntegratedSecurity TRUE or FALSE. Turns on the model where the user does not have to enter a database username and password: the operating system will authenticate the user instead. This is the property of a particular DataSource, although it is only supported for Oracle and MS SQL Server data sources. Can be set to TRUE or FALSE. Defaults to FALSE. If TRUE, it causes the Siebel client software to not prompt the user for a username/password. Instead, it uses the database server’s own authentication facilities to determine if that user should be allowed to login to the database. For Oracle, refer to the OPS$ and REMOTE_OS_AUTHENT features. For MS SQL Server, refer to Integrated Security.

InternalConnectString No information.

MaxCachedCursors Only applicable to MS SQL Server: Maximum number of cursors that will be allowed to be connected to the database at single time.

MaxCachedDataSets Denotes how many data sets will be held in memory, that is for List of Values or anything that has the Cache Data property available (BusComps).

MaxConnections Number of connections you can make to the Server.

MaxCursorSize MaxCursorSize:Sets the total number of rows that can be returned in a result set. While the value of MaxCursorSize affects every database, it is used only for IBM DB2/390.

NetworkPacketSize The size of the packet sent across the network. A datasource property for Sybase databases. Allows the TDS network packet size to be changed from the default of 512 bytes.

NonSQL TRUE or FALSE. Setting that indicates that the data source does not use an SQL DBMS to retrieve its data. This would only be used in conjunction with a specialized business component that we would build internally and would never be arbitrarily set by a customer.

Placeholder Used for internal testing purposes only.

PrefetchSize Number of records that the Siebel application will read up front as part of a query execution. This parameter is only intended to be used in conjunction with the MaxCursorSize parameter and must be set to the same value. If these two values are set, during the execution phase, the Siebel application will read that many records and will close the database cursor. While the value of PrefetchSize affects every database, it is used only for IBM DB2/390.

PrimaryEnterprise The name of the Enterprise Server you want to administer from the client machine. The PrimaryEnterprise parameter must be set to view or change information in the Server Administration Screens.


Name Comment




RequestComponent Name of the server component to which the Siebel client should connect. This should be set to BusIntMgr.

RequestServer If not using load balancing, this is the name of the physical Siebel Server that should service requests from this Siebel client.

ReverseFillThreshold When current query contains many rows it may be very inefficient to read sequentially through all of them if the user hits the End button. For this reason, we allow the customer to configure a threshold value where we will invert the current sort, re-execute the query, and fill our data buffers from the end. This is hidden from the user.

SearchCharacterSet No information.

SearchCheckStatus No information.

SearchConnectString How to connect to the search engine, such as Fulcrum.

SearchDefName No information.

SearchDisableViewer TRUE or FALSE. If TRUE, the viewer window is not displayed. This was intended for JPN version of Siebel 3.x where double-byte characters were not supported in the Fulcrum viewer.

SearchStyle No information.

SearchTermGenerator No information.

SearchThesaurus No information.

SecurityAdapter Optional. Set to LDAP in a datasource section to specify the Siebel-provided security adapter. This line must be included for each datasource for which you want to use a security adapter.

If you don’t set SecurityAdapter to anything, this indicates that you’re using the database for authentication. The value to which you set SecurityAdapter:

� Indicates the security adapter you’re using for authentication. If you’re not using the Siebel-provided security adapter, SecurityAdapter will be set to a value other than LDAP.

� Must be a valid value specified in the Security Adapters section, described in “Security Adapters” on page B-20.

See also “LDAP Parameters” on page B-21 for a description of other security adapter parameters.

Server Begin parameters for connecting to the Server database.


Name Comment




Sample DataSource Sections in the Siebel.cfg File The following example shows the Datasources section in the siebel.cfg file. The DataSources section contains only the name of each datasource:

[DataSources]

Local = Local

Sample = Sample

Server = Server

Gateway = Gateway

DataMart = DataMart

SqlStyle When generating SQL to send to a DBMS, there are times when you will need to construct the statement differently depending on the DBMS you are talking with. SqlStyle is the parameter that tells us what database we are talking with.

TableOwner In a database, tables are identified by both their owner and their name. When queries that reference tables are issued (all Siebel queries) the table owner must be included in those references (for example, SIEBEL.S_EVT_ACT where SIEBEL is the tableowner.

UpperCaseLogin The default is FALSE. If set to TRUE the login name of the user is converted to uppercase before it’s sent to the database for authentication. This value is applicable only if the database is used for authentication; the value of the parameter is ignored when SecurityAdapter is set to a non-empty value.

Use this parameter if you wish to enforce a policy of having all database accounts in uppercase on a case-sensitive database, but you don’t want users to worry about case when they type in their username.

Note that the value of UpperCaseLogin does not affect the password.


Name Comment




In addition, there is a separate parameter list for each datasource named in the DataSources section. The following example shows a sample list of parameters and values for the Local datasource:

[Local]

Docked = FALSE

ConnectString = E:\2822\sea\local\sse_data.dbf -Q -m

TableOwner = SIEBEL

DockedDBFilename = laptopusers

DLL = SSCDW55.DLL

SqlStyle = Oracle

MaxCachedCursors = 16

MaxCachedDataSets = 16

ReverseFillThreshold = 100

CaseInsensitive = FALSE

InsensitivityFactor = 2

DockTxnsPerCommit = 500

DockRecvTxnsPerCommit = 10

DockConnString = entsrvr

SearchStyle = Fulcrum

SearchConnectString = Fulcrum

SearchDefName = Fulcrum Sample




The following example shows a sample list of parameters and values for the Server datasource:

[Server]

Docked = TRUE

ConnectString = siebeldb

TableOwner = siebel

DLL = sscdo80.dll

SqlStyle = Oracle

MaxCachedCursors = 16

MaxCachedDataSets = 16

ReverseFillThreshold = 100

CaseInsensitive = FALSE

InsensitivityFactor = 2

FileSystem = \\ntsrv1\siebfile

SearchStyle = Fulcrum

SearchConnectString = CHANGE_ME

SearchDefName = Fulcrum Sample

GatewayAddress = siebgateway

EnterpriseServer = siebel

RequestComponent = SRMSynch

RequestServer = siebrequest

SecurityAdapter = LDAP

ContactLogin = FALSE




Actuate Reports Parameters B

Table B-4 defines Actuate Reports parameters.

Preload Parameters B

Table B-5 defines preload parameters.

Table B-4. Actuate Reports Parameters

Name Definition

ActuateDevWBDir Directory used in Tools to determine where Actuate Developer Workbench is located.

ActuateReportExportFileName File used in Tools to export all Actuate VB scripts to a flat file.

Table B-5. Preload Parameters

Name Description

[Preload] Specifies view(s) to load during startup of the application so that upon accessing the view for the first time the information is cached and appears more quickly.

View1 Name of the first view to be preloaded at startup.

View2 Name of the second view to be loaded at startup.

Viewn Name of the nth view to be loaded at startup.




Product Configurator Parameters B

Table B-6 defines Product Configurator parameters.

Table B-6. Product Configurator Parameters

Name Definition

ConfiguratorDLLName Name of third party .DLL.

ConfiguratorExeDir Directory of third party .exe.

ConfiguratorExeFileName Name of third party .exe.

ConfiguratorModelDir This is the directory where third party model files used for configuration will be searched if specified. Once this directory is specified, the user can specify only the filename in the configuration file without the path. This was developed for Calico Configurator and may not be utilized by anyone else.

ConfiguratorModelExportFileName The file name of the export of a configurator.




DataCleansing Parameters B

Table B-7 defines the parameters in the [DataCleansing] section of the client .cfg file.

NOTE: Data cleansing is not available for Siebel thin clients.

Table B-7. DataCleansing Parameters

Name Description

Enable Set this optional parameter to TRUE to turn on data cleansing on a client. Set to FALSE to disable data cleansing. The following are required to use the data cleansing feature:

� Data Quality license key

� Firstlogic software installed

Type Do not change the value from IdCentric.

Dir Set to the local directory where the Firstlogic executable (not Postal Dictionary) files reside. The Siebel dedicated client installation program may set this automatically if you installed Firstlogic prior to installing the Siebel client, but only if the Siebel installer detects the presence of Firstlogic, which depends on your system configuration.




DeDuplication Parameters B

Table B-8 defines the parameters in the [DeDuplication] section of the client .cfg file.

NOTE: Data deduplication is not available for Siebel thin clients.

Table B-8. DeDuplication Parameters

Name Description

Enable Set this optional parameter to TRUE to turn on data deduplication on a client. Set to FALSE to disable data deduplication. The following are required to use the data deduplication feature:

� Data Quality license key

� Firstlogic software installed

Type Do not change the value from IdCentric.

Dir Set to the local directory where the Firstlogic executable (not Postal Dictionary) files reside. The Siebel dedicated client installation program may set this automatically if you installed Firstlogic prior to installing the Siebel client, but only if the Siebel installer detects the presence of Firstlogic, which depends on your system configuration.




SAP Subsystem Parameters B

Table B-9 defines the [SAPSubsys] section parameters.

Table B-9. SAPSubsys Parameters

Name Definition

SAPIdocAllowedObjects This optional parameter specifies allowed integration objects for incoming IDOCs. Change this value to receive IDOCs corresponding to integration objects that are different from the default. The default value is:

Product - Receive SAP Material (IDOC Input),Account - Receive SAP Customer (IDOC Input)

SAPRfcConnectString This optional parameter defines the connect string for SAP name-value pairs, IDOC outbound and BAPI adapter. Change the values to connect to the appropriate SAP client and program ID if your application sends IDOCs or makes BAPI requests.

An example SAPRfcConnectString is DEST=destCLINET= 100 LANG=E

SAPRfcDestEntry This optional parameter defines the destination entry of type R in the saprfc.ini file (IDOC inbound). Change the value to listen on an RFC program ID to which you want to send IDOCs.

An example setting for SAPRfcDestEntry is

SAPRfcDestEntry=dest

SAPRfcPassword This optional parameter is the password for logging into the SAP system (IDOC outbound and BAPI adapter).

SAPRfcUserName This optional parameter is the username for logging into the SAP system (IDOC outbound and BAPI adapter).




Security Adapters B

Table B-10 provides information about the configuration parameter that must be specified for each datasource for which you are using a security adapter. An example of the Security Adapters section is shown in “Sample Security Adapters Section in the Siebel.cfg File.”

Sample Security Adapters Section in the Siebel.cfg FileIf you are using a security adapter with any of your datasources, you must specify a Security Adapters section in the siebel.cfg file. If you are using the security adapter provided by Siebel Systems, then your Security Adapters section in the siebel.cfg file would look like this:

[SecurityAdapters]

LDAP = LDAP

In addition to the Security Adapters section, you must specify a parameters section for each security adapter that you specify. The LDAP section parameters are described in the section “LDAP Parameters” on page B-21. The LDAP parameters section is valid for the security adapter provided by Siebel Systems.

Sample Security Adapters Section for Non-LDAP Security AdapterIf you are not using the security adapter provided by Siebel Systems, then your Security Adapters section could look like this:

[SecurityAdapters]

myadapter = myadapter

In the preceding example, myadapter represents the name of your security adapter.

If you are not using the security adapter provided by Siebel Systems, you must also specify a parameters section that is similar to the LDAP parameters section.

Table B-10. Security Adapter Configuration Parameter

Name Definition

LDAP LDAP specifies a security adapter supported by Siebel Systems. If you are using the Siebel-provided security adapter, then LDAP is the correct value.

If you are using another security adapter, the parameter name and value will be something other than LDAP.




LDAP Parameters B

Table B-11 provides information about the configuration parameters that must be specified for each datasource for which you are using the security adapter provided by Siebel Systems. An example of the LDAP section is shown in “Sample LDAP Section in the Siebel.cfg File” on page B-23.

Table B-11. LDAP Security Adapter Configuration Parameters (Sheet 1 of 2)

Name Description

BaseDN Required. The default = "", which should never be used. BaseDN represents the root of the sub-tree in the LDAP directory under which all users of interest are stored. For example: "ou=People, o=AKParker.com"

Users can be stored directly or indirectly below this DN. If administration through the Siebel client is supported and a new user is added to LDAP through the Siebel application it will be added directly under this DN.

CredentialsAttributeType Required. The default is credentials, and represents the attribute type for credentials. They are stored in the user entry under this attribute in LDAP.

See the Siebel Server Administration Guide for more information about credentials.

DllName Required, and specifies the dll to load which implements the security adapter functions. The value for LDAP is sscfldap.dll.

EncryptCredentialsPassword This parameter is optional, and the default value is FALSE. If TRUE, all passwords stored in credentials will be encrypted after reading them from the security adapter and before sending them to the database or other destination for authentication.

The encryption algorithm used for EncryptCredentialsPassword is the same as that used by the general configuration file parameter EncryptPassword.

PasswordAttributeType Required. The default is userPassword, and represents the attribute type for passwords in LDAP.

Use the default in almost every case.

Port Required, and the default is 389 if SslDatabase is not set. If SslDatabase is set, then the default is 636.

This value represents the port on the server machine through which LDAP is accessed. In most instances, use 389 for standard transmission and 636 for secure transmission.




RolesAttributeType Required. The default is roles, which is the attribute type for roles. The roles are stored in the user entry under this attribute in LDAP.

See the Siebel Server Administration Guide for more information about roles.

ServerName Required, the name of the machine on which the LDAP server is running, such as AKParkerserver.com.

SslDatabase Required, and the default = "". If empty, SSL is not being used.

If the value is not empty, it must be the absolute path of a valid Netscape 4.x cert7.db certificate database which contains a certificate for the LDAP server or the Certificate Authority used by the LDAP server.

See the Siebel Server Administration Guide for more information.

SupportsIntegratedAuthentication Optional, and the default value is FALSE. For LDAP this parameter must be FALSE.

If TRUE, the specified Security Adapter supports integrated authentication. This means that the user may not be required to enter a username and password and may be authenticated in some other way, such as through the operating system. If TRUE the Siebel client will attempt to use integrated authentication to authenticate with the security adapter.

Note that thin client never uses integrated authentication.

UsernameAttributeType Required. The default is uid, and represents the attribute type under which the username is stored.

For example, when user SADMIN attempts to log in, the LDAP search will be for uid=SADMIN.

Table B-11. LDAP Security Adapter Configuration Parameters (Sheet 2 of 2)

Name Description




Sample LDAP Section in the Siebel.cfg FileYou must specify an LDAP section in the siebel.cfg file for each Siebel-provided security adapter that you specify in each datasource. Here is a sample LDAP section:

[LDAP]

DllName = sscfldap.dll

ServerName = ldap.AKParker.com

Port = 389

BaseDN = "ou=People, o=AKParker.com"

UsernameAttributeType = uid

PasswordAttributeType = userPassword

CredentialsAttributeType = credentials

RolesAttributeType = roles

SslDatabase =




Internet Parameters B

Table B-12 defines Internet parameters.

Table B-12. Internet Parameters

Name Definition

TableOwner In a database, tables are identified by both their owner and their name. When Siebel issues queries that reference tables (all Siebel queries) you must include the table owner in those references (for example, SIEBEL.S_EVT_ACT where SIEBEL is the table owner).

SqlStyle When generating SQL to send to a DBMS, there are times when you must construct the statement differently depending on the DBMS to which you are talking. SqlStyle is the parameter that tells us what database we are talking to, such as Oracle, Sybase, and so on.


Limiting Views to the Thin or Dedicated Client C

Limiting Views to Thin Client or Dedicated Client . . . . . . . . . . . . . . . . .C-2

Administration of Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . .C-2

Configuration of Screen Views . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-2

Version 6.2, Rev. A Siebel Client Installation and Administration Guide C-1

Limiting Views to the Thin or Dedicated Client

Limiting Views to Thin Client or Dedicated Client

Limiting Views to Thin Client or Dedicated Client C

On occasion, it may make sense to limit certain views to users of one client or another.

Two approaches exist to limit user access to views. Those approaches are accomplished through one of the following methods:

� Administration of Responsibilities

� Configuration of Screen Views

Administration of Responsibilities C

In the Application Administration � Responsibilities view, remove the view from the responsibility of thin client users or dedicated client users.

This approach assumes that your application administrator has created different responsibilities for each type of Siebel client.

Configuration of Screen Views C

The Screen View object type has a property called Client Restriction that is used to configure the view (as used in that screen) as supporting all clients, thin client only, dedicated client only, or Windows-only. The valid settings for this property are as follows:

� NULL. All clients are supported for this view in this screen—dedicated client, mobile client, Thin Client for Windows, Java Thin Client, and HTML Thin Client.

� Dedicated Client Only. Refers to the Siebel dedicated client. Siebel thin clients are not supported for this view in this screen when this setting is selected.

� Thin Client Only. Refers to all the Siebel thin clients—Siebel HTML Thin Client, Siebel Java Thin Client, and Siebel Thin Client for Windows. Siebel dedicated client is not supported for this view in this screen.

� Win32 Only. Refers to Siebel dedicated client and Siebel Thin Client for Windows. Thin clients other than Thin Client for Windows are not supported for this view in this screen when this setting is selected.

You can change this setting, but you should not do so unless the view referenced by the screen view object definition has been altered to support the types of clients for which you are making the view available.

C-2 Siebel Client Installation and Administration Guide Version 6.2, Rev. A

Optimizing Thin Client Performance D

Application Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2

Server-Side Performance Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2

Version 6.2, Rev. A Siebel Client Installation and Administration Guide D-1

Optimizing Thin Client Performance

Application Performance

Application Performance D

To optimize the performance of your application, follow these guidelines:

� In Siebel Tools, create a separate application definition for the Web application instead of using an existing dedicated-client application.

For example, create Sales HTML Thin Client instead of using Siebel Sales.

� In your HTML Thin Client application definition, follow these guidelines:

� Reduce the number of objects—particularly the number of applets in a view and the number of fields in each applet. Specifically, do not include fields (and applets) that users don’t often need or that don’t apply to the Web.

� Do not define any view to have a list and a form accessing the same business component.

� In your templates themselves, avoid duplicating information on the same page. For example, do not place a list and a form referring to the same business component on one page. Avoid this even if you have a view with a list and a form accessing the same business component.

� In your templates and other Web pages, minimize the use of multimedia objects (such as graphics, audios, and videos).

Server-Side Performance Tips D

See the Siebel Server Administration Guide for information about disabling Find Fast, load balancing, and other server-side performance enhancements.

D-2 Siebel Client Installation and Administration Guide Version 6.2, Rev. A

UNIX-Supported Business Component Classes E

Business Component Classes Supported Under UNIX E

The UNIX Application Object Manager does not support all business component classes. If a business component is based on an unsupported class, you will be unable to display applets based on the business component, even though the applet class might be supported by the thin client in use.

The UNIX Support property in a class object definition (with an Object property value of Business Component) indicates whether the class is supported by the UNIX Application Object Manager. This property has a value of All or NULL. If All, business components based on this class are supported in the UNIX Application Object Manager. If NULL, business components with this class are not supported.

For information on viewing supported UNIX object manager business component classes, see the Siebel Tools Guide.

Version 6.2, Rev. A Siebel Client Installation and Administration Guide E-1

UNIX-Supported Business Component Classes

Business Component Classes Supported Under UNIX

E-2 Siebel Client Installation and Administration Guide Version 6.2, Rev. A

Index

AAccessDir parameter B-3accounts, creating mobile client 5-13ActiveX control 9-2Actuate parameters

ActuateDevWBDir B-15ActuateReportExportFileName B-15

ActuateDevWBDir parameter B-15ActuateReportExportFileName

parameter B-15Adobe Acrobat Reader

installing 4-4requirement 4-4

anti-virus software, client configuration 6-8

AppletTitleFont parameter B-3Application Object Manager 14-4

repository file 1-6TCP/IP protocol 1-6thin clients 1-6

ApplicationName parameter B-3ApplicationSplashText parameter B-3autodial preferences, mobile client 5-14

BBaseDN parameter B-21benefits

thin client 1-5business component classes

supported E-1UNIX E-1

CCaptionPrefix parameter B-3CaseInsensitive parameter B-8

cautioninstallation 4-4, 4-6Java Thin Client 10-5local transaction log 5-24mobile clients 5-24Oracle database icons 4-10remote component 5-24saving files 10-5Siebel Remote 5-24synchronizing 5-24

Central DispatchGateway Server address 4-9Request Server name 4-9

choosing a thin client 1-7client

Adobe Acrobat reader 4-4anti-virus software 6-8architecture 3-5dedicated client defined 1-3defined 1-3deployment differences diagram 1-4directory structure 4-14distinguishing thin and dedicated 1-3icons created during installation 4-16installing the Server Manager 4-7installing with the Compact Setup

option 4-7installing with the Custom Setup

option 4-7installing with the Typical Setup

option 4-7installing without Siebel VB

licensed 4-11logging on 5-2mobile client defined 1-3

Version 6.2, Rev. A Siebel Client Installation and Administration Guide 1

Index

ODBC data sources 4-17post-installation tasks 4-11pre-installation tasks 4-2removing 4-18testing Siebel Correspondence 4-13thin client defined 1-3traditional client defined 1-3verifying installation 4-11

client database, failure recovery procedure 5-12

ClientFileServSupport parameter B-3ClientRootDir parameter 5-9, B-3Colors parameter 10-10Compact Setup option, client

installation 4-7ComponentName parameter B-3configuration files

dedicated client 5-26editing 2-6HTML Thin Client 15-6Java Thin Client sample 10-6mobile client 5-9sample 2-3sample datasource section B-12sources of information 2-2

configuration parametersfinding A-2index A-2

configuration, anti-virus software 6-8ConfiguratorDLLName parameter B-16ConfiguratorExeDir parameter B-16ConfiguratorExeFileName parameter B-16ConfiguratorModelDir parameter B-16ConfiguratorModelExportFileName

parameter B-16configuring, HTML Thin Client 14-8connectivity

Siebel Remote 5-3TCP/IP for Siebel Remote 5-3

ConnectString parameter B-8ContactLogin parameter B-8CorrespODBCDataSource parameter B-3correspondence

enabling on Windows 95 4-13enabling on Windows 98 4-13

testing functionality 4-13Word 97 4-13

creatingaccounts 5-13mobile client user account 5-13

CredentialsAttributeType parameter B-21custom installer

creating 9-11packaging 9-15preparing administrator

workstation 9-11Custom Setup option

client installation 4-7Server Manager installation 4-7

Ddata cleansing parameters

Dir B-17Enable B-17Type B-17

data source. See ODBC data sourceDatabase Extract

directory tree 5-16docking 5-16running 5-15

database, client 5-12DataMart parameter B-7DataSource parameter 10-8, B-3DataSource section parameters B-7, B-8DateYearFormat parameter 10-8DecimalNumberScale parameter 10-8dedicated client

choosing a directory name 4-3configuration files 5-26database connectivity software 4-3default installation directory 4-7defined 3-2installing third-party software 4-4prerequisites 4-3removing 4-18

deduplication parametersDir B-18Enable B-18Type B-18

DefaultChartFont parameter B-3

2 Siebel Client Installation and Administration Guide Version 6.2, Rev. A

Index

DefaultFont parameter 10-10demonstration database, Siebel

client 4-12, 4-17deploying

Java Thin Client 8-6sample steps for Thin Client for

Windows 11-3Thin Client for Windows 8-6

differences between thin clients 1-7Dir parameter B-17, B-18directory name

choosing 4-3default 4-3

directory structure, client 4-14distributing

custom installer 9-16installer 9-16

DLL parameter B-8DllName parameter B-21DockConnString parameter 5-9, B-8Docked parameter B-8docking

Database Extract 5-15, 5-16directory tree 5-16failure recovery 5-12initializing local database 5-21

DockRecvTxnsPerCommit parameter B-8DockRepositoryName parameter 5-10, B-3DockTxnsPerCommit parameter 5-11, B-8documentation, additional Intro-3

Eediting configuration files

how to 2-6siebel.ini file 9-12

Enable parameter B-17, B-18EnableOLEAutomation parameter B-4EnablePersonalization parameter B-4EnableScripting parameter B-4EncryptPassword parameter B-4Enterprise Server parameter B-9ExtensionType parameter B-9

Ffailure recovery procedures 5-12features

HTML Thin Client 14-2thin client 1-7

FileExtensionMap parameters 10-9FileSystem parameter 5-11, B-4finding configuration parameters A-2font parameters

LargeDataFont B-5LargeFont B-5NavBarItemFont B-5NavBarSelectFont B-6NavBarTitleFont B-6SmallDataFont B-6SmallFont B-7

Fulcrum, installing SearchServer Desktop before client 4-5

GGateway parameter B-7Gateway Server address, Resonate Central

Dispatch 4-9GatewayAddress parameter B-9

Hhelp system 4-17HelpFile parameter B-4Hidden parameter B-9HideBackground parameter 9-12HoldExportOdbcConnection

parameter B-4HTML Thin Client

Application Object Manager 14-4architecture 14-3configuration files 15-6customizing 14-8diagram 14-3distributed installation 15-3installation 14-8, 15-6introduction 8-2, 14-4network security 16-3new features 14-2


Index

object manager 14-4pre-installation tasks 15-2Siebel Web Engine 14-4single-node installation 15-3templates 14-4troubleshooting 17-2, 17-3, 17-4user request 14-5

HTML thin clienttroubleshooting 17-2, 17-3

Iicons

Oracle database 4-10Siebel client 4-16

index of configuration parameters A-2initializing, local database 5-21InsensitivityFactor parameter B-9installation

caution 4-4, 4-6client 4-6, 10-2creating custom installer 9-11database connectivity software for

client 4-3dedicated client 4-6HTML Thin Client 14-8, 15-6Java Thin Client 10-4mobile client 4-6Thin Client for Windows 9-6

installer, creating custom 9-11InsUpdAllCols parameter B-9IntegratedSecurity parameter B-10internet parameters B-24introduction

clients 1-2diagram of different clients 1-2HTML Thin Client 8-2, 14-4Java Thin Client 8-2Siebel clients 1-2Thin Client for Windows 8-2

JJava Thin Client

access outside firewall 12-2applet classes supported 8-8

caution 10-5control types supported 8-9deploying 8-6example 8-4installation 10-4introduction 8-2launching 10-17pre-installation tasks 10-2removing 10-18sample configuration file 10-6saving files caution 10-5script types supported 8-10sharing configuration files 10-17starting 10-17supported applet classes 8-8supported control types 8-9supported platforms 10-2supported script types 8-10troubleshooting 13-1uninstalling 10-18user interface functionality 8-7Year 2000 compliance 10-11

JTCHelpURL parameter B-5

LLanguage parameter 9-12LargeDataFont parameter B-5LargeFont parameter B-5launching

Java Thin Client 10-17Thin Client for Windows 9-17

LDAP parameter B-20limiting views

administration C-2configuration of screen views C-2

local databaseinitializing 5-21mobile clients 3-3, 5-21transaction log 3-3warning 3-3

Local parameter B-7LocalDbODBCDataSource parameter B-5log files

event 4-11


Index

registry 4-11Siebel Web Engine 17-4

logging onclient 5-2Siebel client 4-11

MMainRepositoryName parameter B-5MaxCachedCursors parameter B-10MaxCachedDataSets parameter B-10MaxConnections parameter B-10Microsoft Windows 95, enabling Siebel

correspondence on 4-13Microsoft Word 97 4-13mobile client user account

authentication 5-13creating 5-13

mobile clientsaccounts 5-13background synchronization 3-3caution 5-24configuration files 5-9database connectivity software 4-3Database Extract 5-15default installation directory 4-7defined 3-2file system 3-3initializing local database 5-21installing third-party software 4-4local database 3-3position view validity 5-15prerequisites 4-3registering 5-14removing 4-18stand-alone synchronization 3-3starting server processes 5-17synchronizing instructions 5-26TCP/IP protocol 3-4

MS DOS file extensions 4-13MultiCurrency parameter B-5

NNavBarItemFont parameter B-5NavBarSelectFont parameter B-6NavBarTitleFont parameter B-6

Netscape plug-in, Windows Thin Client 9-2

network securityaccess outside firewall 12-2firewall configuration 16-3

NetworkPacketSize parameter B-10NoExtension parameter 10-10NonSQL parameter B-10

OODBC data sources, client 4-17OLEAutomationDLL parameter B-6OLEMessagePendingDelay parameter B-6online help system 4-17Oracle database

caution with icons 4-10icons 4-10

overview, synchronizing 5-22

PPackager Utility 4-7PasswordAttributeType parameter B-21performance enhancements

active fields configuration 6-7antivirus software 6-8application D-2configuring active fields 6-7docking transaction logging 6-7runtime docking transaction logging 6-7server-side tips 6-8, D-2Thin Client for Windows 9-20

PersonalizationLog parameter B-6Placeholder parameter B-10Port parameter B-21positions, listed in view 5-15post-installation tasks, client 4-11Preferences parameters 10-10preferences, autodial 5-14PrefetchSize parameter B-10pre-installation tasks

client 4-2HTML Thin Client 15-2Java Thin Client 10-2Thin Client for Windows 9-3

preload parameters B-15


Index

Rregistering mobile clients 5-14remote component

autodial preference 5-14caution 5-24

remote component server, setting up 5-13remote component user, setting up 5-13remote implementation, failure

recovery 5-12removing

dedicated client 4-18Java Thin Client 10-18Thin Client for Windows 9-20

reports parametersReportsDir B-6ReportsODBCDataSource B-6

ReportsDir parameter B-6ReportsODBCDataSource parameter B-6repository file, Application Object

Manager 1-6RepositoryFile parameter B-6RequestComponent parameter B-11RequestServer parameter B-11Resonate Central Dispatch

Gateway Server address 4-9Request Server name 4-9

ReverseFillThreshold parameter B-11RolesAttributeType parameter B-22RootDirectory parameter 9-7, 9-14rs405eng.exe 4-5running

Database Extract 5-15Transaction Merger 5-20Transaction Processor 5-18Transaction Router 5-19

Ssample database, Siebel client 4-17Sample parameter B-7SAPIdocAllowedObjects parameter B-19SAPRfcConnectString parameter B-19SAPRfcDestEntry parameter B-19SAPRfcPassword parameter B-19SAPRfcUserName parameter B-19

SAPSubsys parametersSAPIdocAllowedObjects B-19SAPRfcConnectString B-19SAPRfcDestEntry B-19SAPRfcPassword B-19SAPRfcUserName B-19

ScriptingDLL parameter B-6search parameters

SearchConnectString B-11SearchDisableViewer B-11

SearchConnectString parameter B-11SearchDisableViewer parameter B-11security adapters parameters

BaseDN B-21CredentialsAttributeType B-21DllName B-21LDAP B-20PasswordAttributeType B-21Port B-21RolesAttributeType B-22sample B-20, B-23SecurityAdapter B-11ServerName B-22SslDatabase B-22SupportsIntegratedAuthentication B-22UpperCaseLogin B-12UsernameAttributeType B-22

SecurityAdapter parameter B-11Server Manager, installing 4-7Server parameter B-7, B-11ServerName parameter B-22setting up

mobile client hardware 5-14mobile client software 5-14remote component server 5-13remote component users 5-13Siebel Remote server 5-13Siebel Remote users 5-13

setup.exe, client 4-6SharedModeUsersDir parameter B-6sharing

configuration files 9-10Java Thin Client files 10-17Thin Client start-up files 9-10

shortcuts, Thin Client for Windows 9-9


Index

ShowMessageBar parameter B-6Siebel client. See clientSiebel Marketing during installation 4-10Siebel program

logging on 5-2signing on without Siebel VB

licensed 4-11standard client installation 4-2

Siebel Remoteapplication server preferences 5-9autodial preferences 5-14caution 5-24connectivity 5-3dialog box 5-4local transaction log 5-24network connectivity 5-3preferences 5-9server processes 5-17starting Transaction Merger 5-20starting Transaction Processor 5-18starting Transaction Router 5-19TCP/IP 5-3

Siebel Remote server, setting up 5-13Siebel Remote users, setting up 5-13Siebel Sales and Service, icon 4-10Siebel technical support Intro-6 to Intro-7Siebel Web Engine 14-4siebel.ini file 9-12SmallDataFont parameter B-6SmallFont parameter B-7SQL Anywhere

demonstration database 4-12error messages 4-12sample database 4-12

SqlStyle parameter B-12, B-24SslDatabase parameter B-22stand-alone executable, Windows Thin

Client 9-2standard client installation, running 4-6starting, Java Thin Client 10-17SupportsIntegratedAuthentication

parameter B-22synchronization

background 3-3dialog box 5-4

options 5-3stand-alone 3-3

synchronizingcaution 5-24instructions 5-26mobile clients 5-22, 5-26overview 5-22workflow 5-22, 5-24

TTableOwner parameter 5-10, B-12, B-24technical support Intro-6 to Intro-7TempDir parameter B-7templates, HTML Thin Client 14-4Thin Client

Java example 8-4Windows example 8-3

thin clientApplication Object Manager 1-6benefits 1-5central management 1-5choosing 1-7configuration in Siebel Tools 1-5features 1-7major differences 1-7preferences stored on server 1-5reduced resources requirements 1-5share UI with dedicated 1-5

third-party softwareFulcrum 4-5installing for client 4-4requirements 4-4

transaction log 3-3Transaction Merger

running 5-20starting 5-20

Transaction Processorrunning 5-18starting 5-18

Transaction Routerrunning 5-19starting 5-19

troubleshootingconfiguration files 17-2dedicated client 7-1


Index

Java Thin Client 13-1log files 17-3, 17-4MaxCursorSize parameter 7-1object manager configuration 17-2returning more rows 7-1.srf and .cfg 17-3Thin Client for Windows 13-1Visual Basic 17-3Windows NT services 17-2

Type parameter B-17, B-18Typical Setup option, client

installation 4-7

Uuninstalling

client 4-18dedicated client 4-18Java Thin Client 10-18mobile client 4-18Thin Client for Windows 9-20

UNIXbusiness component classes E-1support E-1

updating, mobile clients 5-26UpperCaseLogin parameter B-12user interface functionality

Java Thin Client 8-7Thin Client for Windows 8-7

UsernameAttributeType parameter B-22users, mobile client 5-13

Vverifying configuration files, Thin Client for

Windows 9-9Version parameter B-7View1 parameter B-15View2 parameter B-15ViewN parameter B-15views

dedicated client only C-2limiting C-2thin client only C-2

WWelcome parameter 9-13Windows Thin Client

access outside firewall 12-2ActiveX control 9-2applet classes supported 8-8connect string samples 9-18control types supported 8-9custom installer 9-11deploying 8-6deployment scenario 11-2example 8-3installation 9-6introduction 8-2launching 9-17Netscape plug-in 9-2performance 9-20pre-installation tasks 9-3removing 9-20sample connect strings 9-18sample deployment 11-3script types supported 8-10shortcuts 9-9stand-alone executable 9-2starting 9-17supported applet classes 8-8supported control types 8-9supported script types 8-10troubleshooting 13-1uninstalling 9-20user interface functionality 8-7verifying configuration files 9-9

Word 97 (Microsoft) 4-13

YYear 2000 compliance 10-11


siebel 6 - clientad

Documents

adobe acrobat reader

program files siebel tclient

stringent security measures

object manager listens

java thin clienttroubleshooting

resonate central dispatch

side performance enhancements

side performance tipssee