Siebel Client Installation Guide - 21Gradi



CONFIDENTIAL

eService Program

Siebel Server Installation Guide

Revision Date: 17/12/2001

Version: 0.1

Document Information and Revision History

|File Name |Siebel Server Installation guide.doc |

|Original Author(s) |Wong Kah Hoe |

|Current Revision Author(s) | |

|Version |Date |Author(s) |Revision Notes |

|0.1 |18/8/2001 |Wong Kah Hoe |Document Created |

|REVIEWS & AUTHORISATIONS | | |

|Reviewed/Approved By |Responsibility |Date |

| | | |

| | | |

| | | |

| | | |

| | | |

TABLE OF CONTENTS

Place your cursor on the LINE BELOW to create the Table of Contents (

Go to; Insert/Table of Contents and press return!

DO not delete this line! There is a "bookmark" embedded here

1 Introduction 5

1.0 Purpose 5

1.1 Scope 5

1.2 Reference 5

1.3 Document Structure 5

2 Installation Pre-requisite 7

3 Installation Procedures 8

4 Oracle Client Installation 9

4.0 Oracle 8.1.5 Client Installation 9

4.1 Oracle 8.1.5 Client configuration 9

4.2 Configuration Used 10

4.2.1 Phase 2 Environments 10

4.2.2 Phase 3 Environments 11

5 Environment Parameters 12

6 Resonate Installation 13

6.0 Installation 13

7 Siebel Gateway Installation and Configuration 14

7.0 Installation 14

7.1 Patch 14

8 Siebel Server Installation and Configuration 15

8.0 Installation 15

8.1 Patch 16

8.2 Configuration 16

9 Siebel Web Plug-in Installation and Configuration 18

9.0 Installation 18

9.1 Patch 19

9.2 Configuration 19

10 IIS4 Installation 20

10.0 Installation 20

10.1 Configuration 20

10.1.1 Development/SIT environment 20

10.1.2 UAT/Production environment 20

11 Netscape Directory Server Installation and Configuration 22

11.0 Installation 22

11.1 Configuration for Siebel to work with LDAP 23

11.1.1 Server cfg 23

11.1.2 SWEApp eapps.cfg 23

11.1.3 Siebel Server 24

11.1.4 Netscape Directory Server 24

12 Single Sign On 26

12.0 Configuration 26

12.0.1 Server Application cfg 26

12.0.2 SWEApp eapps.cfg 26

Introduction

1 Purpose

This document describes the processes and standards to be followed by the individual who will install Siebel Servers in the Development Environment.

2 Scope

This document is designed to be an installation guide only. The scope of the document covers the installation and configuration requirements for Siebel Server within the Development Environment.

3 Reference

|Ref. |Document Title |Author |Date |

|1. |Siebel Server Installation Guide, Siebel 2000 Version 6.0, 10PA1-IN00-06000 |Siebel |April 2000 |

| |(SrvrInst.pdf) | | |

|2. |Siebel Server Administration Guide, Siebel 2000 Version 6.0, 10PA1-AG00-06000 |Siebel |April 2000 |

| |(SrvrAdm.pdf) | | |

|3. |Siebel eCommunications and eEnergy .COM Application Guide, Siebel 2000 version 6.0, |Siebel |August 2000 |

| |80PA1-EB00-06010 (CandEDotCom.pdf) | | |

|4. |Siebel Server Administration Guide, Siebel 2000 Version 6.0, 10PA1-AG00-06000 |Siebel |April 2000 |

| |(SrvrAdm.pdf) | | |

|5. |Environment Matrix.xls |CGEY |December 2001 |

4 Document Structure

This document is divided into a number of sections:

|Installation Prerequisite |Describes the Software Pre-installation requirement |

|Installation Procedures |Overview of Installation steps |

|Environment Parameters |Describes the various environment parameters used |

|Oracle Client Installation |Describes the installation of Oracle Client and configuration |

|Resonate Installation |Describe the installation of Resonate 2.2 |

|Siebel Gateway Installation |Describes the installation of Siebel Gateway |

|Siebel Server Installation and |Describes the installation and configuration of Siebel Server |

|Configuration | |

|Siebel Eapps Installation and |Describes the installation of Siebel Eapps |

|Configuration | |

|IIS 4 installation |Describe the installation of IIS 4 |

|Netscape Directory Server Installation |Describes the installation and configuration of Netscape Directory Server and |

|and Configuration |configuration required on Siebel Server to work with Netscape Directory Server |

|Single Sign On |Describe the Single Sign On configuration required for Netscape Directory Server and|

| |Siebel Server |

Installation Pre-requisite

The information below is required prior to installing:

1) Create the Siebel Service Owner network domain account with Administrator rights.

a) Set the Siebel Service Owner account (esersv2) with the following advanced user rights for each server (Reference Error! Reference source not found. Page 2-19 Step 3):

Log on as a Service

Act as part of the operating system

Replace a process Level Token

b) Add the User Rights of Login as a Service for the Siebel Service Owner.

c) Create the Siebel Monitoring network domain account (esermn2), do NOT set administrative privileges for this account and ensure it has user privileges (Reference Siebel Server Installation Guide Page 2-21).

2) Virtual Cluster Server IP

3) Primary Cluster IP

4) Secondary Cluster IP

Installation Procedures

Please refer to Siebel Server Installation Guide Siebel 2000 (SrvrInst.pdf) for detail installation procedures.

Oracle Client Installation

1 Oracle 8.1.5 Client Installation

The version of Oracle Client that is required is 8.1.5. Run Setup.exe from Oracle installation directory.

Follow the following steps:

1. (Welcome Screen) Click “Next”

2. (File Location Screen) Click “Next” (use default directory, e.g. C:\Oracle\Ora81)

3. (Available Product Screen) Select “Oracle8I Client 8.1.5.0.0” and then click “Next”

4. (Installation Types Screen) Select “Typical (267MB)” then click “Next”

5. (Summary Screen) Click “Install”

6. Click “Cancel” when the configuration for Oracle NET8 appears

7. Click “Yes” when prompted (Exit popup)

2 Oracle 8.1.5 Client configuration

Check with your Database Administrator for the following and modify each entry appropriately:

1. Net Service Name (e.g. ESUAT..AU)

2. Protocol to use (e.g. TCP/IP)

3. Host Name (e.g. vus620.in..au)

4. Port Number (e.g. 1521)

5. Database SID (e.g. ESUAT)

When you have gathered the above information, run “Net8 Easy Config” (Start -> Programs -> Oracle – OraHome81 -> Network Administration -> Net8 Easy Config).

Follow the following steps:

1. (Welcome Screen) Select “Create” under Actions and key in Net Service Name, click “Next”

2. (Protocol Screen) Select TCP/IP (Internet Protocol), click “Next”

3. (Protocol Setting Screen) Enter Host Name and Port Number, click “Next”

4. (Service Screen) Enter the Database SID, click “Next”

5. Click on Test, ignore the error. Click on “Change Login” and key in the correct login name and password (e.g. username = SADMIN, password = SADMIN). Click “Next” when completed.

6. Click “Finish” and the setup for Oracle client is completed.

When done verify that there is a connectivity to the Database server by logging in via SQL*Plus logging as “SYSTEM” and password “MANAGER” and database connect string set to the Database SID above.

3 Configuration Used

1 Phase 2 Environments

1 ESRV1 Development Environment

1. Net Service Name = ESRV1..AU

2. Protocol to use = TCP/IP

3. Host Name = vus620.in..au

4. Port Number = 1521

5. Database SID = ESRV1

2 ESRV2 Development Environment

1. Net Service Name = ESRV2..AU

2. Protocol to use = TCP/IP

3. Host Name = vus620.in..au

4. Port Number = 1521

5. Database SID = ESRV2

3 ESRV3 Development Environment

1. Net Service Name = ESRV3..AU

2. Protocol to use = TCP/IP

3. Host Name = vus620.in..au

4. Port Number = 1521

5. Database SID = ESRV3

4 UAT Environment

1. Net Service Name = EUAT..AU

2. Protocol to use = TCP/IP

3. Host Name = vus620.in..au

4. Port Number = 1521

5. Database SID = ESUAT

5 ESD2 Development Environment

1. Net Service Name = ESD2..AU

2. Protocol to use = TCP/IP

3. Host Name = vus620.in..au

4. Port Number = 1521

5. Database SID = ESD2

2 Phase 3 Environments

1 ESD3 Development Environment

1. Net Service Name = ESD3..AU

2. Protocol to use = TCP/IP

3. Host Name = vus630.in..au

4. Port Number = 1521

5. Database SID = ESD3

2 ESS3 SIT Environment

1. Net Service Name = ESS3..AU

2. Protocol to use = TCP/IP

3. Host Name = vus630.in..au

4. Port Number = 1521

5. Database SID = ESS3

3 UAT Environment

1. Net Service Name = ESU3..AU

2. Protocol to use = TCP/IP

3. Host Name = vus769.in..au

4. Port Number = 1521

5. Database SID = ESU3

4 Pre-Production Environment

1. Net Service Name = ESERVP..AU

2. Protocol to use = TCP/IP

3. Host Name = vus121.in..au

4. Port Number = 1521

5. Database SID = ESERVP

5 Production Environment

1. Net Service Name = ESERVP..AU

2. Protocol to use = TCP/IP

3. Host Name = vus121.in..au

4. Port Number = 1521

5. Database SID = ESERVP

Environment Parameters

Before installating the Siebel Servers, verify that following information are available

1. Type of Setup (e.g. Typical)

2. Directory to install the client (e.g. c:\sea601\)

3. Database Server type (e.g. Oracle Enterprise Server 8.1.5)

4. Database you will be using (Database SID), should be one of the setting in section 3.2 Configuration Used.

5. Table Owner (default is “siebel”)

6. Gateway Server Name

7. Enterprise Server Name

8. Siebel Server Name (Siebel Server Name) (e.g. 14_SVR)

9. File System Location (e.g. \\NTTOA0014\FS)

Please refer to “Environment Parameter Matrix.xls” for parameter setting on various environments.

Resonate Installation

1 Installation

Before installing the Resonate Server, verify that required components are installed/available:

1. Two NICs on the Server

2. Resonate VIP

3. Gateway VIP

4. Microsoft Loopback Adapter

5. Resonate Administration Mode Account

6. Resonate Monitor Mode Account

7. Also refer to “Part 1 – Installing Central Dispatch and the Siebel Gateway Server” of SrvrInst.pdf for detail options and configurations.

From the Resonate Server Installation Directory (e.g. \Siebel Server 6.0.1\Thirdpty\enu\resonate\winnt)

1. Double-click Setup.exe

2. (Welcome Screen) Click “Next”

3. (Select Destination Directory Screen) Click “Browse…” to change the Destination Folder, otherwise click “Next” to accept default directory (e.g. “C:\Program Files\Resonate”)

4. (Select Components Screen) Select all three components: Central Dispatch Note, Dispatch Manager and Dispatch Command and then click “Next”

5. (Configure MS Loopback Adapter Screen) Select “Yes, …” and then click “Next” to continue

6. (Assign VIPs Screen) Click on “Add” to add Resonate then click “Next” to continue

7. (Bind RXPVNIC Screen) Select the NIC to bind to resonate and then click “Next” to continue

8. (Configure Network Memory Buffers Screen) Click “Next” to continue

9. (Identify User Accounts Screen) Enter the Administrator Mode Username and the Monitor Mode Username and then click “Next” to continue

10. (Specify Agent Port Screen) Click “Next” to continue

11. (Start Copying Files Screen) Click “Next”

12. (Setup Complete Screen) Click “Finish”

13. (Setup Complete Screen) Select “Yes, …” and then click “Finish”

Siebel Gateway Installation and Configuration

1 Installation

Before installing the Siebel Gateway Server, verify that required components are installed/available:

1. Resonate (if required)

2. Gateway VIP

3. Administrator account which can Logon as a service

4. Ensure that the Environment Parameters is available for the environment which you will be connecting to (Refer to section 4 – Environment Parameters). Also refer to “Part 1 – Installing Central Dispatch and the Siebel Gateway Server” of SrvrInst.pdf for detail options and configurations.

From the Siebel Gateway Server Installation Directory (e.g. \Siebel Server 6.0.1\gtwysrvr\)

1. Double-click Setup.exe

2. (Welcome Screen) Click “Next”

3. (Question Screen) If Resonate is installed, this screen will not appear. Click “Yes” to continue

4. (Select Destination Directory Screen) Click “Browse…” to change the Destination Folder, otherwise click “Next” to accept default directory (e.g. “c:\sea601\gtwysrvr” or d:\sea601\gtwysrvr)

5. (Gateway Server NT Account Information Screen) In Account key in the Administrator Account (e.g. account-01\administrator) and password and then click “Next”

6. (Gateway Server NT Services Screen) Make sure that Start Automatically check box is checked if resonate is not installed, (is resonate is installed, Start Automatically should be unchecked) and then click “Next”

7. (Start Copying Files Screen) Click “Next”

8. (Event Log Screen) Click “Next”

9. (Setup Complete Screen) Click “Finish”

2 Patch

You need to patch Siebel Gateway Server to version 6.0.1.4. and 6.0.1.24

From the Siebel Gateway Server Patch 4 Installation Directory (e.g. \Siebel Patch 6.0.1.4\Server\gtwysrvr and \Siebel_patch_6.0.1.24\Windows Server\gtwysrvr)

1. Double-click Setup.exe

2. (Welcome Screen) Click “Next”

3. (Select Destination Directory Screen ), click “Browse…” to change the Destination Folder or click “Next” to use the default directory (e.g. “c:\sea601\gtwysrvr” or d:\sea601\gtwysrvr)

4. (Event Log Screen) Check and note down any critical errors such as installation of DLL fails etc and inform the environment team. Click “Next”

5. (Setup Complete Screen) Click “Finish”

Repeat the above for patch 6.0.1.24.

Siebel Server Installation and Configuration

1 Installation

Before installing the Siebel Server, verify that required components are installed/available:

1. Resonate (if required)

2. Gateway VIP

3. Enterprise Server Name

4. Siebel Server Name

5. Database SID

6. Make sure that the Gateway service is started before proceed to server installation

7. Ensure that the Environment Parameters is available for the environment which you will be connecting to (Refer to section 4 – Environment Parameters). Also refer to “Part 2 – Installing the Siebel Server” of SrvrInst.pdf for detail options and configurations.

From the Siebel Server Installation Directory (e.g. \Siebel Server 6.0.1\siebsrvr\)

1. Double-click Setup.exe

2. (Welcome Screen) Click “Next”

3. (Question Screen) If Resonate is installed, click “No” otherwise click “Yes” to continue

4. (Start the Siebel Gateway Server Screen) Make sure that the Gateway Server is started and then click “Next”

5. (Setup Type Screen) Select Custom installation. Click “Browse…” to change the Destination Folder, otherwise click “Next” to accept default directory (e.g. “c:\sea601\siebsrvr” or d:\sea601\siebsrvr)

6. (Select Components Screen) Check that the selected components are Object Manager Component, Object Manager Help Files, Siebel Executable Files and Object Configuration Templates and then click “Next”

7. (Gateway Server Address Screen) Enter the Gateway VIP (or the Gateway Server name) and then click “Next”

8. (Enterprise Server Information Screen) Enter the Name of the Enterprise Server and then click “Next”

9. (Siebel Server Information Screen) Enter the Name of the Siebel Server and then click “Next”

10. (Siebel Server NT Service Screen) Make sure that Start Automatically check box is checked and then click “Next”

11. (Synchronization Port Assignment Screen) Use default value (40400) and then click “Next”

12. (eBriefings and eContent Services Screen) Select “Neither” and then click “Next”

13. (Java Thin Client Help File URL) Click “Next”

14. (Start Copying Files Screen) Click “Next”

15. (Event Log Screen) Click “Next”

16. (Setup Complete Screen) Click “Finish”

2 Patch

You need to patch Siebel Server to version 6.0.1.4. and 6.0.1.24

From the Siebel Server Patch 4 Installation Directory (e.g. \Siebel Patch 6.0.1.4\Server\siebsrvr and \Siebel_patch_6.0.1.24\Windows Server\siebsrvr)

1. Double-click Setup.exe

2. (Welcome Screen) Click “Next”

3. (Select Destination Directory Screen ), click “Browse…” to change the Destination Folder or click “Next” to use the default directory (e.g. “c:\sea601\siebsrvr” or d:\sea601\siebsrvr)

4. (Event Log Screen) Check and note down any critical errors such as installation of DLL fails etc and inform the environment team. Click “Next”

5. (Setup Complete Screen) Click “Finish”

Repeat the above for patch 6.0.1.24.

3 Configuration

In most cases the client configuration used is stored in file with extension .cfg stored in e.g. \sea601\siebsrvr\bin directory. A typical cfg file that we used is siebel.cfg.

All cfg files has the following sections:

[Siebel]

[DataSources]

[Local]

[Sample]

[Server]

[SearchAdmin]

[DataMart]

[Gateway]

[ActuateReports]

[Preload]

[CTI]

[ProductConfigurator]

[DataCleansing]

[DeDuplication]

[CCA]

[PricingCache]

[SalesTax]

[SAPSubsys]

[SecurityAdapters]

[LDAP]

We only (mainly) do changes in the section in bold above and leave other section with the default values. Please refer to “Server Parameter Matrix.xls for the parameters setting for each environments.

Siebel Web Plug-in Installation and Configuration

1 Installation

Before installing the Siebel Web Plug-in, verify that required components are installed/available:

1. Siebel Gateway Server Host (Gateway Server VIP, e.g. 123.121.12.3)

2. Siebel Gateway Port (e.g. 2320)

3. Siebel Enterprise Server Name (e.g. xxx_ENT)

4. Siebel Server Name (e.g. xxx_SVR)

5. Object Manager to use

6. Microsoft Internet Information Server (IIS4) installed

7. Netscape Directory Server installed

8. Directory to install the Plug-in (e.g. c:\sea601\SWEApps)

9. LDAP Server Name (full domain name, e.g dirServer.in..au)

10. Port (e.g. 389)

11. Base DN (e.g. "ou=People, o=in..au")

From the Siebel Siebel Web Plug-in Installation Directory (e.g. \Siebel Server 6.0.1\eappweb\)

1. Double-click Setup.exe

2. (Welcome Screen) Click “Next”

3. (Select Destination Directory Screen), click “Next” to accept default directory. To change the installation directory, click on “Browse” and change the directory accordingly.

4. (Load Balancing Screen), select “Yes” and click “Next”

5. (Gateway and Enterprise server information Screen) Enter the Gateway VIP for Gateway Server Host, Gateway Port (e.g. 2320) and Enterprise Server Name (e.g. xxx_ENT) and click “Next”

6. (Siebel Server Information Screen) Enter the Siebel Server Name (e.g. xxx_SVR) and click “Next”

7. (Connection Protocol Screen) Select “TCP/IP” and click “Next”

8. (Encryption Type Screen) Select “none” and click “Next”

9. (Compression Method Screen) Select “none” and click “Next”

10. (Anonymous user account for anonymous Employee Login Screen) type in SADMIN for Username, and SADMIN for password and click “Next”

11. (Anonymous user account for anonymous Contact Login Screen) type in SADMIN for Username, and SADMIN for password and click “Next”

12. (Error Level and Logging Screen) Select “Error only” and click “Next”

13. (Event Log Screen) Click “Next”

14. (Setup Complete Screen) Click “Finish”

2 Patch

You need to patch Siebel Web Plug-in to version 6.0.1.4. and 6.0.1.24

From the Siebel Web Plug-in Patch 6.0.1.4 Installation Directory (e.g Siebel Patch 6.0.1.4\Windows Server\eappweb)

1. Double-click Setup.exe

2. (Welcome Screen) Click “Next”

3. (Select Destination Directory Screen ), click “Browse…” to change the Destination Folder to “c:\sea601\SWEApp” (or d:\sea601\SWEApp) and then click “Next”

4. (Event Log Screen) Check and note down any critical errors such as installation of DLL fails etc and inform the environment team. Click “Next”

5. (Setup Complete Screen) Click “Finish”

Repeat the above for patch 6.0.1.24.

3 Configuration

The configuration of Siebel Web Plug-in lies in the eapps.cfg file.

The cfg file has the following sections:

[swe]

[defaults]

[/ebriefings]

[/ebriefings_w]

[/echannel]

[/partnerfinder]

[/wpsales]

[/wpserv]

[/eai]

[/ecustomer]

[/emarketing]

[/esales]

[/eservice]

[/eservice/public]

[/etraining]

We only (mainly) do changes in the section in bold above and leave other section with the default values.

IIS4 Installation

1 Installation

From the NT Option Pack 4 Directory (e.g. \NTServerOptionPackSetupFiles)

1. Double-click Setup.exe

2. (Setup Screen) Click “Yes”

3. (End User License Agreement Screen) Click “Agree”

4. (Installation Option Screen) Click “Custom”

5. (Select Components Screen) Click “Next

6. (Directory of Various component Screen) Click “Browse…” to change the Destination Folder, otherwise click “Next” to accept default directory (e.g. “C:\Inetpub\….”)

7. (Microsoft Transaction Server 2.0 Screen) Click “Browse…” to change the Destination Folder, otherwise click “Next” to accept default directory (e.g. “C:\Program Files\Mts”)

8. (Transaction Server Configuration Screen) Click “Next”

9. (Microsoft Index Server Screen) Click “Browse…” to change the Destination Folder, otherwise click “Next” to accept default directory (e.g. “C:\Inetpub”)

10. (Microsoft SMTP Service Screen) Click “Browse…” to change the Destination Folder, otherwise click “Next” to accept default directory (e.g. “C:\Inetpub\Mailroot”)

11. (Setup Complete Screen) Click “Finish”

12. (System Setting Change Screen) Select “Yes” to restart the system

2 Configuration

1 Development/SIT environment

In MMC (Microsoft Management Console), make sure that the Siebel Application that is required is running

2 UAT/Production environment

In MMC (Microsoft Management Console), stop all default services. Create the following services:

1. eservice..au

• IP address: 222.12.143.148, port: 80

• SSL IP address: 222.12.143.148, port: 80

• Host Header Name: eservice..au

• Home Dirtectory: D:\eservice..au

2. eservicewap..au

• IP address: 222.12.143.148, port: 80

• SSL IP address: 222.12.143.148, port: 80

• Host Header Name: eservicewap..au

• Home Dirtectory: D:\eservicewap..au

Copy the configuration from the default configuration created by Siebel Web Plug-in to the above services, e.g. eservice to eservice..au and wpserv to eservicewap..au.

Netscape Directory Server Installation and Configuration

1 Installation

Before installing the Siebel Web Plug-in, verify that required components are installed/available:

1. Directory to install the Server (e.g. c:\Netscape\Server4)

2. LDAP Server Name (full domain name, e.g dirServer.in..au)

3. Port (e.g. 389)

4. Base DN (e.g. "ou=People, o=in..au")

5. Administrator ID and password

6. Administration domain

From the Netscape Directory Server Installation Directory (e.g. \Netscape Directory Server\)

1. Double-click d412eiu.exe

2. (Welcome Screen) Click “Next”

3. (Software License Agreement Screen) Click “Yes”

4. (Select Server or Console Installation Screen) Select Netscape Server and click “Next”

5. (Select Installation Type Screen) Select Custom and click “Next”

6. (Choose Installation Directory Screen), click “Next” to accept default directory. To change the installation directory, click on “Browse” and change the directory accordingly

7. (Select Products Screen) Select Netscape Server Products Core Components, Netscape Directory Suite and Administration Services and click “Next”

8. (SNMP Is Running Screen) If SNMP is running you will get this screen. Click “OK”. If stopping SNMP service failed, you need to exit the installation and stop the SNMP service and related services manually and start from step 1

9. (Configuration Directory Server Screen) Select “This instance will be the configuration directory server” and click “Next”

10. (Directory to store data Screen) Select “Store data in this directory server” and click “Next”

11. (General Settings Screen) Use default and click “Next”

12. (Configuration Directory Server Administrator Screen) Enter Administrator user Name and password and click “Next”

13. (Administration Domain Settings Screen) Enter the appropriate administration domain and click “Next”

14. (Directory Manager Settings Screen) Enter password and click “Next”

15. (Replication configuration Screen) Keep default and click “Next”

16. (Populate Database Screen) Keep default and click “Next”

17. (Disable Schema Checking Screen) Click “Next”

18. (Administration Server IP Address Screen) Enter the IP address (usually the server IP address) and click “Next”

19. (Administration Port Screen) Enter the Port Number to use or use default port and click “Next”

20. (Configuration Summary Screen) Click “Next”

21. (Setup Complete Screen) Select “Restart Computer” and click “Finish”

2 Configuration for Siebel to work with LDAP

In order for Siebel to work with LDAP, you need to configure the following:

1. The application cfg (in Server, e.g. eservice.cfg)

2. The SWEApp cfg (eapps.cfg)

3. Siebel Server and

4. Netscape Directory Server

1 Server cfg

In order for a contact user to be authenticated by LDAP, make the following changes to the appropriate application cfg:

[Server]

SecurityAdapter = LDAP

ContactLogin = TRUE

[SecurityAdapters]

LDAP = LDAP

[LDAP]

DllName = sscfldap.dll

ServerName = dirServerName.in..au

Port = 389

BaseDN = "ou=People, o=in..au"

UsernameAttributeType = uid

PasswordAttributeType = userPassword

CredentialsAttributeType = mail

RolesAttributeType = roles

Note:

dirServerName is the Name os the server that hosts the Directory Server.

2 SWEApp eapps.cfg

In order for a user to be authenticated by LDAP, add AnonUserName = LDAPUSER, AnonPassword = LDAPUSER to the application section that require LDAP authentication for example:

[/wpserv]

AnonUserName = LDAPUSER

AnonPassword = LDAPUSER

……………

[/eai]

AnonUserName = LDAPUSER

AnonPassword = LDAPUSER

……………

[/eservice]

AnonUserName = LDAPUSER

AnonPassword = LDAPUSER

……………

[/eservice/public]

AnonUserName = LDAPUSER

AnonPassword = LDAPUSER

……………

3 Siebel Server

In order for a contact user to be authenticated by LDAP, make the following changes to Siebel Server:

• In System Preference, set SecExternalUserAdministration to FALSE.

• Create the following responsibilities

1. Registered Customer WAP/Web

2. Unregistered Visitor WAP/Web

And add appropriate views to these responsibilities

• Create an employee called CUSTOMER with the following profile

1. Last Name: Registered Customer

2. First Name: Registered Customer

3. Responsibility: Registered Customer WAP/Web

4. Position: Siebel Administrator

5. Sub Division: Siebel Administrator

6. Organization: Default Organization

Add Registered Customer to Employees list in Registered Customer WAP/Web responsibility

• Create an employee called GUEST with the following profile

1. Last Name: Unregistered Visitor

2. First Name: Unregistered Visitor

3. Responsibility: Unregistered Visitor WAP/Web

4. Position: Siebel Administrator

5. Sub Division: Siebel Administrator

6. Organization: Default Organization

Add Unregistered Visitor to Employees list in Unregistered Visitor WAP/Web responsibility

• Add LDAPUSER with the following profile to Contact

1. Last Name: LDAPUSER

2. First Name: LDAPUSER

3. Login Name: LDAPUSER

4. Employee Login Name: CUSTOMER

5. New Employee Login Name: CUSTOMER

4 Netscape Directory Server

In order for a user to be authenticated by LDAP, make the following changes to the Directory Server:

• Set Access Permission in People, by modifying/adding “Allow self entry modification” ACI as follow:

Allow, anyone, any, any, all

• Create the following user under People

1. LDAPUSER with the following profile:

First Name: LDAPUSER

Last Name: LDAPUSER

Common Name: LDAPUSER

User ID: LDAPUSER

Password: LDAPUSER

E-mail: type=SERVER username=SADMIN password=SADMIN

2. GUEST with the following profile:

First Name: GUEST

Last Name: GUEST

Common Name: GUEST

User ID: GUEST

Password: GUEST

E-mail: type=SERVER username=SADMIN password=SADMIN

Single Sign On

1 Configuration

In order for Single Sign On to work (with Siteminder), the following configuration is added to the Server application sfg and SWEApp eapps.cfg:

1 Server Application cfg

Add the following parameter to the appropriate cfg file:

[LDAP]

ApplicationUser = administrator

ApplicationPassword = administrator

SingleSignOn = TRUE

TrustToken = HELLO

2 SWEApp eapps.cfg

Add the following parameter to the application section of the cfg file:

SingleSignOn = TRUE

TrustToken = HELLO

UserSpec = SIEBELUSER

UserSpecSource = Header

-----------------------

[pic]

in Confidence

in Confidence

1

[pic]

2

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download