Test Schedule PPT V3

8/6/2019 Test Schedule PPT V3

http://slidepdf.com/reader/full/test-schedule-ppt-v3 1/196

Num Domain Test ID

1 Security

2 Security

3 Security

4 Security

5 Security

6 Security

7 Security

8 Security

9 Security

10 Security

11 Security

12 Security

13 Security

14 Security

15 Availability

16 Availability

SEC01

SEC02

SEC03

SEC04

SEC05

SEC06

SEC07

SEC08

SEC09

SEC10

SEC11

SEC12

SEC13

SEC14

AV01

AV02



17 Availability

18 Availability

19 Availability

20 Availability

21 Availability

22 Availability

23 Availability

24 Load Balancing RR



AV03

AV04

AV05

AV06

AV07

AV08

AV09

LOA01

LOA02

LOA03

http://e/Local%20Settings/Temp/notesEA312D/AV08R.xls




27 Session Management








35 Connectivity

SES01

SES02

SES03

SES04

SES05

SES06

SES07

SES08

CON01



36 Connectivity

37 Connectivity

38 Connectivity

39 Connectivity

40 Connectivity

41 Connectivity

42 Connectivity

43 Connectivity

44 Connectivity

45 Connectivity

46 Connectivity

47 Connectivity

48 Connectivity

49 Connectivity

50 Connectivity

CON02

CON03

CON04

CON05

CON06

CON07

CON08

CON09

CON10

CON11

CON12

CON13

CON14

CON15

CON16



51 Connectivity

52 Fail Over

53 Fail Over

54 Fail Over

55 Fail Over

56 Deployment

57 Deployment

58 Deployment

59 Deployment

60 Deployment

61 Deployment

62 Deployment

63 Deployment

CON17

FO01

FO02

FO03

FO04

DEP01

DEP02

DEP03

DEP04

DEP05

DEP06

DEP07

DEP08



64 Deployment

65 Deployment

66 Deployment

67 Deployment

68 Maintainability MAI01

69 Maintainability MAI02

70 Caching CAC01

71 Caching CAC0272 Caching CAC03

73 Caching CAC04

74 Caching CAC05

75 End to End Share to Smart DAT01

DEP09

DEP10

DEP11

DEP12



Test Description Prerequisite

This test is to demonstrate that all view access will be via https

User has Admin Access to the Siebel Web Server 0

0

Platform must be up and running.

This test is to demonstrate that SSL encryption is used by the thin client(web browser) for accessing the Webserver and Siebel Server

SSL must be implementedbeforehand on the Test plateformbefore we can proceed with this test.

This test is to demonstrate that an error message will be displayed to theuser where an incorrect password has beeen entered.

Admin Data must be already loadedinto the Test plateform in order totest different user logins.

This test is to demonstrate that an error message will be displayed to theuser where an incorrect User ID has been entered.

Admin Data must be already loadedinto the Test plateform in order totest different user logins.

This test is to demonstrate that different views are accessible depending of the login used to connect to the application.

Admin Data must be already loadedinto the Test plateform in order totest views allocation mechanism.

User ID and Password granted withaccess to specific views only.

This test is to ensure that password data for Anonymous and Webupdateaccounts are not stored in clear in the eapps.cfg file.

The platform must be up andrunning.

This test is to ensure that passwords for standard Siebel accounts haveproperly been modified.

The platform must be up andrunning.

This test is to validate the proper setting of the plateform in order to allowusers to change their password.

Depending of the authetication modeimplemented, certain settings maybe necessary to allow passwordchange by users.

This test checks the status of SSL encrypted SISNAPI communicationbetween the Web servers and the Siebel Servers.

This test is to validate the proper settings of the ADSI/LDAP authenticationprocess.

Requires the ADSI/LDAP loginauthentication mode to beimplemented.

This test is to validate that the various Siebel Services are run under acommon specific Domain account.

Have System Admin rights on eachof the servers or at list be able to listrunning services from the controlpannel.

This test is to validate the inability to connect directly to the File System and

to the DB from a Web Client workstation.

Requires a network and workstation

set-up similar to ones used on thetarget architecture.

This test is to verify that an error will be displayed on login page if an invalidanonymous credential is provided in the eapps.cfg file.

This is to verify that the Gateway Server is accessible from the variousservers of the enterprise.

All Siebel Server Components areinstalled on the platform

This is to verify that the name server service is running on the SiebelGateway Server

Siebel Gateway Server is up andservices are running



Database must be available

All Siebel Services are available



This test is to verify that the server administration view can be accessedfrom the web client

Siebel Gateway Server is up andservices are running. Warning! Thereis a major technical difference in theway certain admin views areaccessed depending if it is from adedicated or thin web client. In thefirst case, a direct connection (no FWie) is required between the

workstation and the Siebel Gateway.

This test is to verify that the load balancing configuration file can begenerated by typing the command LBCONFIG at the console command line

Siebel Gateway Server is up andservices are running

This test is to verify ODBC Data source Connectivity for Oracle in awindows environment

This test is to verify that an error will be displayed if the web server portentry is incorrect in the eapps.cfg file

This test is to verify that an error will be displayed if the virtual directorieshave not been created on the web server.

This test is to verify that an error 'page not found 'will be displayed if aninvalid user name exists.

This test is to verify that a blank page will be displayed if the passwordsettings are incorrect.

This test is to verify that a blank pagewill be displayed if the http portsettings are incorrect

This test is designed to confirm the proper routing between OM's of newincoming sessions.

Requires an admin access to LoadBalancing application in order totrace in real time the routing of newsessions. Also requires access tovarious log files on Siebel and WebServers.

This test is designed to confirm that the NLB equipment placed in front of the Web Servers properly routes incoming sessions to each of the webservers.

Ability to connect from numerousworkstations possibly with differentIP addresses depending of the IProuting strategy chosen.

This test is to verify that the load balancing configuration file can begenerated by typing the command LBCONFIG at the console command line

F5 load balancer is installed andproperly tuned to route requests toSiebel Servers OM.



This test is to verify the timeout setting of the plateform. Platform up and running.

This test is to verify that at the start of the user session an Initial Request iscreated and maintained whilst the user performs the business process of Stock Validation and Error Correction script.

Test team has Admin Access to theall servers of the platform, User dataand specific credentials must beloaded into the application prior totesting. A complete use case mustbe provided in order to complete thetest. A HTTP monitoring tool must beinstalled on the test workstation, and

log level and log events must bechanged at the enterprise level inorder to track navigation inside theOM processes log files.

This test is to verify that at the start of the user session an Initial Request iscreated and maintained whilst the user performs one of the BusinessProcess Scripts.

Object Manager Logging level set to4

This test is to analyse the network data consumption during a typicalbusiness process for one user.

Platform up and running. A networkmonitoring and analysis tool must beinstalled on a test workstation inorder to mesure the bandwidth. Acomplete business case must bedefined, along with adequatecredentials and preloaded user data.

This test is to verify the status of the session on all the different servers incase of a browser window closure without proper logout.

Platform up and running. Adminrights on the servers of the platform.

Remote access tool and socketlisting tool for IIS are required.

This test is to verify the behaviour change between cookie and cookie-lessmodes of the client's browser during the execution of a Business criticalprocess.

Platform up and running. Ability tomodify Internet Explorer privacysettings on the workstation. User data and credentials must bepreloaded into the application inorder to play the use case, as well asa step by step description of the caseitself.

This test is to verify the amount of DB transactions during a typical Businessprocess.

Platform up and running. Ability tomonitor transactions on the DB.

Verify the proper settings of the IIS thread mode for connections with theSiebel Servers.

The platform must be up andrunning. We need to access the WebServers in order to validate certainparameters in IIS.

This test is to verify that each element of the connection process arerequired to enable connection of a thin client

All required components of theplatform must be set-up prior totesting



This test is used to verify that the F5 load balancer is properly installed.

This test is to verify the succesful set-up of all connection brokers.

This test is to verify that the http local Deamon of a Mobile Client is onlyaccessible localy.

Require a typical target mobile clientworkstation. The server must be set-up in order to allow the creation andthe management of remote users.

This test is to verify that the Siebel Wireless Gateway is accessible from ahandheld device.

This test is to verify that the Siebel Gateway is accessible from externalnetwork.

Requires that the various networkgateways are properly set-up

This is to verify that the Gateway Server is accessible from the variousservers of the enterprise.


This test is used to verify that round robbing load balancing is dependent of the application aliases definition in the eapps.cfg

Test platform needs to be up andrunning.

This test is used to verify that the F5 load balancer can access the SiebelServers and be accessed by the Web Servers.

The test platform must be set-up andrunning.


This test is to verify the proper execution of various Server Manager Commands.



Siebel Gateway Server is up andservices are running. Warning! Thereis a major technical difference in theway certain admin views areaccessed depending if it is from adedicated or thin web client. In thefirst case, a direct connection (no FWie) is required between theworkstation and the Siebel Gateway.

This test is used to demonstrate the operability of a command line batchexecution.

Requires a sample asynchronousbatch process to test with expectedresults and means of validation.

This test is to verify that the Siebel Gateway server is properly set-up andrunning.


Requires a precise list of all

managed components and their localisation (including port numbersof components)

This test is to verify that the server manager is properly monitoring andmanage the various servers, components and tasks of the plateform.

Requires a precise list of allmanaged components and their localisation.

This test is to verify Oracle ODBC Data Source Connectivity from all SiebelServers.

Proper ODBC Drivers must havebeen installed on the Siebel servers.Detailed parameters for ODBCconnection may be required(NLS_LANG & SORT_ORDER).

This test is to verify the accessibility of the File System by all the FileSystem Manager Component.

Requires a precise list of allmanaged components and their localisation.



All components are available.


Existing Services are up and running

Existing Service are up and running

This test is to verify that the web client supports HTTP 1.1 protocol

This test is to verify that only the required application web aliases (virtualdirectories in IIS) are activated on the platform and that the parameters areproperly tuned between IIS and SWSE.

Requires that the different IISservers and related eapps.cfg fileshave been properly tuned on theplateform.

This test is to verify that the Fail Over mechanism Oracle Fail Safe isproperly running on the DB server.

Requires 2 instances of DB server with Fail Safe service running.

This test is to verify that the MSCS services are properly installed andrunning.

Requires the MSCS are installed andare running on the specified servers.

This test is to verify the redundancy of the web servers. This test is to verifythe behaviour of an existing session in case of a web server crash.

Have the web servers runningbehind a NLB equipment or similar device, routing clients sessionseither to one or the other IIS.

This test is to verify that the Siebel Servers are properly set-up in order toallow automatic resilient processing in case of anomaly on one of theservers of the enterprise. This test is also to verify the behaviour of anexisting session in case of an OM crash, by getting Asserts and normallogs.

Need to have a properly set-upenvironement with a stableapplication and technicalcomponents as in Production.

This test is to demonstrate that when the Database is unavailable - an error will be displayed when the user attempts to access the database.

Have Database rollback segmentsproperly tuned, and a full backupavailable in case on DB crashrequiring a full restore.

This test is to demonstrate that when the File System Shared Directory isunavailable - documents, file attachments and images will not be madeavailable.

FSM Components properly set-up onthe platform, in accordance with theFile System access rights andnetwork settings (firewall opening

and IP routing)

This test is to demonstrate that when the File System Manager componentis not enabled requests that use the FSM will return an error message

This test is to demonstrate that when the File System Manager componentis not enabled requests that use the FSM will return an error message

This test is to demonstrate that a Siebel User can log into the siebelapplication when the Gateway Name Server has been disabled

The Siebel Gateway must beproperly backed up

This test is to verify that when the Siebel Servers are unavailable - the user will receive an HTTP error message on attempting to log into the SiebelApplication

This test is to demonstrate that when the Web Servers are unavailable - anerror will be displayed to the user and the Siebel Application will beunavailable.

Internet explorer is available anduser can access IE settings.



This test is to verify that all Siebel Gateway Name Services have started.

This test is to verify that all Siebel Server Services have started.

This test is to verify that Microsoft IIS virtual diectories have been createdon the Siebel Web Server

You must have installed all keySiebel Enterprise Server components, including the SiebelGateway Name Server, at least oneSiebel Server, and the DatabaseConfiguration Utilities.and configured the Siebel GatewayName Server, created and

configured the SiebelEnterprise, created the SWSE logicalprofile, and configured the SiebelServer.

All Siebel Components have beeninstalled. This test must be reviewedto take into account MSCS on theGateway platform.

All Siebel Components have beeninstalled

This test is to validate the proper set-up of the Internet Browser on a targetworkstation running a web client.

Reauires to have Browser HealthCheck activated on the plateformand have a workstation identical towhat will be used in production.



Aprox. Duration Status Comment Order Execution Date

3h Reviewed

1h Reviewed

1h Reviewed

1h Reviewed

Redondant

1h Reviewed

1h Reviewed

Redondant

1h Reviewed

3h TBC

3h TBC

1h Reviewed

1h Reviewed

1h Reviewed

Changed Changed to CON05

Redondant

Not sure that SSL is implementedbetween Web Servers Web Browsers

Not sure that SSL is implementedbetween Web Servers and SiebelServers

Not sure that ADSI authentication isimplemented




Changed Changed to LOA03






2h Reviewed

1h Reviewed

Draft Needs to be clarified



3h Reviewed

Draft Needs to be clarified

3h Reviewed Applicable to load testing scenario

2h Reviewed

2h Reviewed

2h Reviewed

3h Reviewed

3h Reviewed

TBC Needs to be clarified in terms of targetarchitecture.



2h Reviewed

TBC

1h Reviewed

2h Reviewed

2h Reviewed

1h Reviewed

1h Reviewed

1h Reviewed

1h Reviewed

2h Reviewed

1h Reviewed

1h Reviewed

1h Reviewed

2h Reviewed

2h Reviewed

Not sure that the Wirelessfunctionnality will be implemented.



2h Reviewed

3h Reviewed

2h Reviewed

3h Reviewed Applicable to load testing scenario.

3h TBC Applicable to load testing scenario.

1h Reviewed

2h Reviewed

Redondant

Redondant

1h Reviewed

2h Reviewed

1h Reviewed

1h Reviewed

Oracle Fail Safe Technology only runsunder MS Operating Systems ansMSCS clusters. The target database issupposed to run a Unix DB server.

Needs to be clarified in terms of targetarchitecture.



Redondant

1h Reviewed

1h Reviewed

2h TBC

TBC

TBC

TBC

TBCTBC

TBC

TBC

TBC



LOA01 TBD MAI01 CAC01

MAI02 CAC02

SES03 CAC03

SES04 CAC04

SES05 CAC05

DEP09

Totals 8 9 2 1 12 5 5

SEC01 AV01 CreateOrder -SiebelServer 1

DEP01 SES01

SEC02 AV02 CreateOrder -SiebelServer 2

DEP02 SES02

SEC03 AV03 CreateOrder -Database DEP03

SEC04 AV04 DEP04

SEC05 AV05 DEP05

SEC06 AV06 DEP06

SEC07 AV07 DEP07

SEC08 AV08 DEP08

AV09DEP10.1

DEP11.1

DEP12.1

T e s t

D e s

c r i p t i o

n

S e c u r i t y

A v a i l a b i l i t y

F a i l O

v e r u s i n g

A d a p t e d F

u n c t i o n a l T

e s t S c r i p t s

L o a d

B a l a n c i n g

R R

D o c u m e n t a t i o n

D e p l o y m e n t

M a i n t a i n a b i l i t y

S e s s i o n M a n a g e m

e n t

C a c h i n g

http://e/Local%20Settings/Temp/notesEA312D/SEC01R.xls


http://e/Local%20Settings/Temp/notesEA312D/DEP01R.xls

http://e/Local%20Settings/Temp/notesEA312D/SES01R.xls
























http://e/Local%20Settings/Temp/notesEA312D/DEP10.1R.xls



































1

DAT01 - CreateService RequestRecord

E n d t o

E n d

S h a

r e t o S m a

r t



Port number

Https 443

Http 80

LDAP/ADSI Secured 636

LDAP/ADSI Standard 389

Oracle listener 1521

UDP Port for Windows FS 137-138TCP Port for Windows FS 139

Gateway 2320

Object Manager

SCBroker 2321

Remote server 40400



Test Description Pre Conditions Post Conditi Acceptance Custom Custom Custom

Test Step Test Step Description Notes Expected Re Actual Resul

DEP01.1

DEP01.2 Select the Contacts Screen

DEP01.3

DEP01.4 Shut down the database server

DEP01.5 Select the Contact Tab

DEP01.6 Enter CTRL +Shift+A

Back to Total Page

This test is to demonstrate thatwhen the Database is unavailable- an error will be displayed whenthe user attempts to access thedatabase.

Have Database rollbacksegments properly tuned, and afull backup available in case onDB crash requiring a full restore.

Log onto Siebel Application withadministrator User ID andPassword as defined in theConfiguration table.

Siebel HomePage isdisplayed

ContactScreen isdisplayedshowingavailablerecords

Select the account record VIPHOLLAND B.V as displayed inthe Accounts columns of theContact Screen or as the accountrecord as indicated in theConfiguration Table.

The Accountis selectedand thedetailedrecord isdisplayed.

Thedatabaseserver is shutdown therecordselected inthe previousstep iscurrentlydisplayed

Contact Tabis selectedand norecords areavailable

Screen viewsare notdisplayed

and error isdisplayed tothe user -DatabaseUnavailable.



DEP01.7

DEP01.8

DEP01.9

Stop all the platform and restartthe servers in the following order:-DB Server and File System-Siebel Servers-F5 Load Balancing-Web Servers-Http Load Balancing

The platformis restarted.

Wait few minutes for the servicesto restart properly, then try toreconnect to the applicationusing the same credential thanbefore.

Siebel HomePage isdisplayed.

Access the same account andcheck that you find the sameinformation than before.

Account isnot corrupted



Custom Comments

Siebel Ref

Warning this is a very pertubativetest. Shutting down the databasebefore any Siebel Server maylead to technical problems suchas orphan records and data

corruption.





Test Description Pre Conditions Post Conditi Acceptance

Test Step Test Step Description Notes Expected Re

DEP02.1

DEP02.2 Press Ctrl+Shift+A

DEP02.3

DEP02.4

Back to Total Page

This test is to demonstrate that when the File SystemShared Directory is unavailable - documents, fileattachments and images will not be made available.

FSM Components properly set-up on theplatform, in accordance with the File Systemaccess rights and network settings (firewallopening and IP routing)

Log onto Siebel Application with SiebelAdministrator type credentials.

Siebel HomePage is

displayed

The Site Mapis displayedshowing thevariousviews

Go to Contacts View and select a record. Selectthe Send Letter Option form the File Menu inorder to generate a letter to this contact. Launchthe generation and check that the status iscompleted before proceeding.

User isdirected totheCorrespondence Menuwhere adocumentrecord iscreateddisplayingcreated datetime stampand Statusas InProgress.

Once the document is generated, try to edit itusing the hyperlink of the completed record.

MS Wordopens withthe newgenerateddocument init, fetchedfrom theSiebel FileSystem.



DEP02.5

DEP02.6

DEP02.7

DEP02.8

On the server where the File System Share ishosted, open a Windows Explorer session. FileSystem should be only accessible by adminaccounts and FSM components, not directly bythe users. Remove the read rights of the FSMcomponents and apply the changes.

File systemis notaccessibleby FSMcomponentsanymore.

Back on the Siebel Session, Navigate to the SiteMap by typing Ctrl +Shft+A and select theCorrespondence Tab. Select the document thathas just been generated and try to open it againwith MS Word. An error message should appear.

Thegenerateddocument,which isstored on thefile system,is notaccessibleanymore.

Return to the server where the File System ishosted and rollback the user rights.

User rightsare restored.

Back in Siebel, try to edit the same generateddocument again.

Documentopensproperly inMS Word.



Custom Custom Custom Custom Comments

Actual Resul Siebel Ref

Warning thisis a verypertubativetest,especially if

Remoteservers areactive asthey mayrequire toaccess theFs on aregular basis.





Test Description Pre Conditions Post Conditi Acceptance Custom Custom



DEP03.1

DEP03.2 Press Ctrl+Shift+A < enter>

DEP03.3

DEP03.4

DEP03.5

DEP03.6

DEP03.7 Select the Personal Template Tabs

Back to Total Page

This test is to demonstrate that whenthe File System Manager component isnot enabled requests that use the FSMwill return an error message

Log onto Siebel Application withadministrator User ID and Passwordas defined in the Configurationtable.

SiebelSplashScreen isdisplayed

The Screenview isdisplayedshowing thevariousviews

Select the Send Letter Option formthe File Menu

User isdirected to

theCorrespondence Menuwhere arecord iscreateddipslayingcreated datetime stampand Statusas InProgress

Click the back button in the browser

or the site map button to return tothe Screen View

The Screen

view isdisplayedshowing thevariousscreen views

Using Windows explorer disable theFile System or Unshare the drivethat File system directory is held onthe siebel server

File systemisdisconnected

Navigate to the Site Map Menu Ctrl+Shft+A and select theCorrespondence Tab.

This cannotbe selectedand theCorresponde

nce view isdisabled

An Error isdisplayedwhen thePersonalTemplateTab isselected.



Custom Custom

Siebel Ref



Test Descrip Pre Conditio Post Conditi Acceptance Custom Custom Custom Custom

Test Step Notes Expected Re Actual Resul Siebel Ref

DEP04.1

DEP04.2

DEP04.3

Back to Total Page

This test is todemonstratethat whenthe FileSystem

Manager component isnot enabledrequests thatuse the FSMwill return anerror message

Allcomponentsare available.

Test StepDescription

Log ontoSiebelApplicationwithadministrator User ID andPassword asdefined intheConfigurationtable.

SiebelSplashScreen isdisplayed

PressCtrl+Shift+A< enter>

The Screenview isdisplayedshowing thevariousviews

Select theSend Letter Option formthe FileMenu

User isdirected totheCorrespondence Menuwhere arecord iscreateddipslayingcreated datetime stampand Statusas InProgress



DEP04.4

DEP04.5

DEP04.6

DEP04.7

Click theback buttonin thebrowser or the site mapbutton toreturn to theScreen View

The Screenview isdisplayedshowing thevariousscreen views

UsingWindowsexplorer disable theFile Systemor Unsharethe drive thatFile systemdirectory isheld on thesiebel server

File systemisdisconnected

Navigate tothe Site MapMenu Ctrl+Shft+A andselect theCorrespondence Tab.

This cannotbe selectedand theCorrespondence view isdisabled

Select thePersonalTemplate

Tabs

An Error isdisplayedwhen the

PersonalTemplateTab isselected.



Test DescriptPre Conditio Post Conditi Acceptance Custom Custom Custom Custom Custom


DEP05.6

DEP05.1

DEP05.2

Back to Total Page

This test is todemonstratethat a SiebelUser can loginto the

siebelapplicationwhen theGatewayName Server has beendisabled

The SiebelGatewaymust beproperlybacked up

Warning thisis a verypertubativetest that canrequire the

completereinstallationof theplatform


Using a

remoteaccess toolto connecton theGatewayServer, stopthe SiebelGatewayNameService.

Gateway

Name Server is disabled

Beforestarting thistest, a

backup of thesiebns.datfile must bemade.Connect tothe SiebelGatewayServer andmake abackup copyof this file.

Thesiebns.datfile is

backed-up

Log ontoSiebeleServiceapplicationwithadministrator user ID andPassword

Siebel HomePage isdisplayed



DEP05.3

DEP05.4

DEP05.5

DEP05.6

PressCtrl+Shift+A

The Site Mapis displayedshowing thevariousviews

Click onServer AdministrationConfiguration

The Server AdministrationConfigurationmenu view isdisplayed as

Administration - Server ConfigurationEnterpriseExplorer EnterprisesComponentDefinitionsComponentGroups

SystemAlertsServersComponentsEventsParametersParameters

Log out of the siebelapplication -File >Logoutor Ctrl+Shift+x

User islogged out of the siebelapplication -and theSiebel FrontPage SplashScreen isdisplayed

Using aremote

access toolto connecton theGatewayServer, stopthe SiebelGatewayNameService.

GatewayName Server

is disabled



DEP05.7

DEP05.8 Site Map is displayed

DEP05.9

DEP05.10

DEP05.11

Log into theSiebelApplicationby enteringUser Id andUser Password asdefined in

theConfigurationTable Press<enter>

User is ableto log intothe Siebelapplication ,an error message isnot displayedto the user

on thescreen

Navigate tothe Site Mapmenu or pressCTRL+Shift+A

Select

Administration Server Configuration>ComponentDefinition >

The

componentdefinitionscreen isdisplayed

Attempt toadd a newcomponentdefinition byselecting theNew Button

The 'New'button isdisabled andthe user cannot add anewcomponent

Attempt tostart acomponentthat hasbeendisabled byselecting thestart buttonon thecomponentdefinitionscreen

The 'Start'button isdisabled andthe user cannot starta component



DEP05.12

DEP05.13

DEP05.14

Log out of the siebelapplicationby selecting- File>Logout fromthe menu or press

Ctrl+Shift+x

User islogged out of the siebelapplication -and theSiebel FrontPage SplashScreen is

displayed

Restart theSiebelGatewayService nowand redo thesame testagain.

Newcomponent isadded.Existingcomponent isstarted.

Stop the

Gatewayservice androll back thebacked upversion of thesiebns.datfile. Restartthe SiebelGatewayService;Check thatthemodificationsmade abovewithcomponents

do notappear anymore.

The platform

configurationis back to itsstate prior tothe test.





DEP06.1

DEP06.2

Back to Total Page

This test is toverify thatwhen theSiebelServers are

unavailable -the user willreceive anHTTP error message onattempting tolog into theSiebelApplication

ExistingServices areup andrunning

Test Step

Description

Log ontoSiebelApplicationwithadministrator User ID andPassword.

The SiebelHome Pageis displayed

PressCtrl+Shift+Ato access theSite Map.

The Site Mapis displayed



DEP06.3

DEP06.4

DEP06.5

Click onServer AdministrationConfiguration.

The Server AdministrationConfigurationmenu view isdisplayed as

Administratio

n - Server ConfigurationEnterpriseExplorer EnterprisesComponentDefinitionsComponentGroupsSystemAlertsServersComponentsEventsParametersParameters

Log out of the siebelapplication -File >Logoutor Ctrl+Shift+x.

User islogged out of the siebelapplication -and theSiebel loginPage isdisplayedagain.

Using aremoteaccess tool,access allservershosting anObjectManager,and shutdown theSiebel

Services oneach one of theseservers.

SiebelServices areshutdown oneach server hosting anOM.



DEP06.6

DEP06.7

DEP06.8

Try to loginto theSiebelApplicationby enteringUser Id andPassword asdefined in

theConfigurationTable.

User logsinto theSiebelapplication ,an HTTPerror message isdisplayed

'PageCannot beFound'

Using thesame remoteaccess tools,restart theSiebelservices onthe servershosting OM.

All Siebelservices of the platformare backonline.

Once this isdone, do arestart of theloadbalancingservice, andalso of theIIS serviceson the webservers. Tryto connect totheapplicationagain.

The loginpage isaccessibleagain.



Test Description Pre Conditions Post Conditi Acceptance Criteria Custom Custom

Test Step Test Step Description Notes Expected Results Actual Resul

DEP07.1 Siebel Home Page is displayed

DEP07.2 Press Ctrl+Shift+A

DEP07.3

DEP07.4 Click on Components

DEP07.5

DEP07.6 User is logged on the web server.

DEP07.7

DEP07.8

DEP07.9 The platform is back online.

Back to Total Page

This test is to demonstrate thatwhen the Web Servers areunavailable - an error will bedisplayed to the user and theSiebel Application will be

unavailable.

Existing Service are upand running

Log onto SiebelApplication withadministrator User IDand Password asdefined in theConfiguration table.

The Site Map is displayed showingthe available screen views.

Click on Administration

- Server Configuration

The Administration - Server

Configuration details are displayed.

The siebel server componentscreen is displayed.

Now exit from theSiebel Application - bypressing CTRL+Shift+xor select from the menutitle bar File > Logout

User is logged out of theapplication.

Log on to the WebServers using re+oteqccess tool.

Stop the IIS services onthe web servers

The web server(s) are shut down.No more trqffic is treated.

Try to log onto SiebelApplication withadministrator User IDand Password asdefined in theConfiguration table.

No page is displayed. After acertain time out period, an error message is displayed by the webbrowser stating that the server isunavailable.

Restart the web serversand redo the test after waiting a minute or twofor the services toprocess requests again.



Custom Custom

Siebel Ref



Test Description Pre Conditions Post Conditi Acceptance Criteria Custom


DEP08.1

Back to Total Page

This test is to verify that the web clientsupports HTTP 1.1 protocol

Internet explorer is available and user can access IE settings.

Verify that the WebClient supportsHTTP 1.1 protocol by clicking onTools > Internet Options> Advanced .Scroll down and enable the checkbox Use HTTP 1.1

The Web Browser support for HTTP 1.1 protocol is enabled.



Custom Custom Custom

Siebel Ref



Test Description Pre Conditions Post Conditi Acceptance

Test Step Test Step Description Notes Expected Re

DEP09.1

DEP09.2

DEP09.3 Double Click Websites in the right panel

DEP09.4 Double Click default Websites in the right panel

Back to Total Page

This test is to verify that Microsoft IIS virtualdiectories have been created on the Siebel WebServer

You must have installed all key SiebelEnterprise Server components, including theSiebelGateway Name Server, at least one SiebelServer, and the Database Configuration

Utilities.and configured the Siebel Gateway NameServer, created and configured the SiebelEnterprise, created the SWSE logical profile,and configured the Siebel Server.

On the Microsoft IIS machine, navigate toControl Panel > Administrative Tools > InternetInformation Service

IIS Screen isdisplayed

Double-click machine_name (local computer)in the left panel.

All the virtualdirectoriescreated onthis machinewill be listedin the rightpanel



Custom Custom Custom Custom




Test Description Pre Conditions Post Conditi Acceptance Custom Custom Custom

Test Step Test Step Description Notes Expected Re Actual ResulDEP10.1

DEP10.2

DEP10.3

DEP10.4

DEP10.5

Back to Total Page

This test is to verify that allSiebel Gateway NameServices have started.

All Siebel Components have beeninstalled. This test must be reviewed totake into account MSCS on the Gatewayplatform.

On the servers hosting the Gatewayservice navigate to the Control Panel >Administrative Tools and select Services

The servicescreen is inview anddisplays theavailableservices.

Scroll down the list and identify theSiebel Gateway Name Server Service

SiebelGatewayName Server Servicescreen isdisplayed

Double Click on the Siebel GatewayName Service

Servicepopupwindow isdisplayed.

Check the Service Status: startup modeshould be set to automatic and theservice account used to start it shouldbe a domain specific account.

ServiceStatusdisplaysStatusStarted usingspecificdomainaccount, andstartup modeautomatic.

Check the Service Status to see if it isstarted.

SiebelGatewayService isstarted.



Custom

Siebel Ref





DEP11.1

DEP11.2

DEP11.3

DEP11.4

DEP11.5 Check that the service is started.

Back to Total Page

This test is to verify that all SiebelServer Services have started.

All Siebel Components have beeninstalled

For each of the Siebel Servers of the platform, Navigate to theControl Panel > AdministrativeTools and select Services

The servicescreen is inview anddisplays theavailableservices.

Scroll down the list and identify theSiebel Server Service.

SiebelServer Servicescreen isdisplayed.

Double Click on the Siebel serviceto edit it.

Servicepopup

window isdisplayed.

Check the Service Status. It shouldbe already running, using a specificdomain service account, and itsstartup mode should be set toAutomatic.

ServiceStatusdisplaysStatusStarted usingspecificdomainaccount, andstartup modeautomatic.

SiebelService isstarted.



Custom Custom

Siebel Ref





Back to Total Page

This test is to validate the proper set-up of the Internet Browser on atarget workstation running a webclient.

Reauires to have Browser HealthCheck activated on the plateformand have a workstation identical towhat will be used in production.



Custom Custom

Siebel Ref



Test Description Pre Conditions Custom Custom

Steps Test Desc Notes Expected Re Actual Resul Pass / Fail

CON01.1CON01.2

Back to Total PagePostConditions

AcceptanceCriteria



Custom Custom Comments

Data Input Siebel Ref Siebel Reference



Test Description Pre Conditions Acceptance Criteria Custom Custom

Steps Test Desc Notes Expected Results Actual Resul Pass / Fail

CON02.1 A new remote user is created.

CON02.2 New DB template is generated.

CON02.3 New user DB is created.

CON02.4 Login screen appears.

CON02.5

CON02.6

Back to Total Page

PostConditions

This test is to verify that the httplocal Deamon of a Mobile Clientis only accessible localy.

Require a typical targetmobile client workstation.The server must be set-up

in order to allow thecreation and themanagement of remoteusers.

From a workstation,connected to the testplatform, using SiebelAdministration credentials,define a user as a remotein Remote UsersAdministration Screen.

Launch a Generate NewDB task in order to createa new DB Template

Now launch a DB Extracttask for the user that willbe used for this test.

Logout from theapplication typingCtrl+Shift+X

Now using a workstationsimilar to the one used inproduction to run Mobileclients, connect to theapplication, using the"Local" profile.

The user specific DB preparedduring the previous steps indownloaded on theworkstation. When finishedcreating the local DB, the user will automatically get

connected to it.

Running ipconfig inprompt mode, take note of all network details for thisuser workstation.

IP configuration is writtendown.



CON02.7

CON02.8

From another workstation,launch an IE windows.Type in a Siebel URLstarting with the IPaddress of the user workstation.

An error message appears, thecomputer is unreachable.

From the user workstation,run a network port audit tosee if any of the portsused by Siebel localdeamon is opened. Thiscan be done either byrunning a specific utility, or by using web sitesdedicated to this task.

All Siebel reserved ports areclosed to incoming traffic.





Warning, incase of previous DBextraction, anew DBgenerationwill lead allexistingremote userstoredownloadtheir localDB.






Steps Test Desc Notes Expected Re Actual Resul Pass / Fail Data Input Siebel Ref Siebel Reference

Back to Total Page

TestDescription

PreConditions

PostConditions

AcceptanceCriteria

This test is toverify thatthe Siebel

WirelessGateway isaccessiblefrom ahandhelddevice.



Test Description Pre Conditions Custom Custom Custom

Steps Test Desc Notes Expected Re Actual Resul Pass / Fail Data Input Siebel Ref

CON04.1

CON04.2

Back to Total Page

PostConditions

AcceptanceCriteria

This test is to verify thatthe Siebel Gateway isaccessible from external

network.

Requires that the variousnetwork gateways areproperly set-up

On the test environment,take note of the detailed IPconfiguration of theGateway server. If this is aMCS cluster, take alldetailed IP configuration of both servers AND of thecluster.

IPconfigurations are writtendown.

From a remote location,similar to where the Mobiles

users will connect from(public network?), try totelnet the Gatewayaccessing its default port. If it is a cluster, only the VIPneeds to be accessible.

The Telenetsession asks

for a login.The Gatewayis accessible.



Custom Comments

Siebel Reference



Test Description Pre Conditions Custom Custom

Steps Test Desc Notes Expected Re Actual Resul Pass / Fail

CON05.1

CON05.2

CON05.3

CON05.4

CON05.5

CON05.6

Back to Total Page

PostConditions

AcceptanceCriteria

This is to verify that theGateway Server is accessiblefrom the various servers of

the enterprise.


Connect to each Siebel server of theEnterprise and try to access the siebelgateway service by typing in a DOScommand window - telnet ip address AND specific port number where ipaddress and port are defined in theconfiguration table.

The Gatewayanswers tothe telentrequest.

On server reponse at prompt, Enter User ID and Password

User is nowconnected tothe Siebel

GatewayService

Connect to the Siebel Gateway Server locally or with a re+ote access tool.

User is nowconnected tothe SiebelGatewayService

In the Control Panel, go to the Serviceslist.

A list of services isdisplayed.

Look for the Siebel Gateway service inthe list. It should be running, in automaticlaunch mode and launched by a specificDomain account.

The SiebelGatewayservice isrunning inautomaticmode andlaunched bya specificDomain user.

Navigate to the \gtwysrvr\ADMIN on theSiebel Gateway server.

The promptchangesto\gtwysrvr\ADMIN.



CON05.7 Check to see if the siebns.dat file exists. Thesiebns.datfile ispresent.





Onlypossiblelocaly on theserver or withAdministration pack for Windowsfrom aworkstationor withspecial toolsto seeprocessesremotely.



Need tomake abackup taskof thesiebns.dat



Test Description Pre Conditions Post Conditions Acceptance Criteria Custom Custom

Steps Test Desc Notes Expected Results Actual Resul Pass / Fail

CON06.1

CON06.2

CON06.3

CON06.4

CON06.5

CON06.6

CON06.7

CON06.8

Back to Total Page

This test is used to verify that roundrobbing load balancing is dependentof the application aliases definition inthe eapps.cfg

Test platform needs to beup and running.

Using a remote accesstool, connect to the loadbalancer server management screen inorder to see routedsessions in real time.

The load balancer displays a list of routedsessions.

From a workstation usedfor testing, connect to theapplication using an aliasthat will be used inproduction and that relieson load balancing. Anycredential may be used.

Siebel Home Page isdisplayed.

Validate that this newsession is listed in theload balancer management screen.

The new session islisted as being routedby the load balancer.

Edit the eapps.cfg file onboth the web servers andcreate a specific aliaswhich points directly toone of the OM servers of the platform. Apply the

changes to the webservers by restarting theIIS services.

A new specific aliaswas created allowing adirect connection to oneof the OM servers.

Connect to the applicationusing the new alias.

The Siebel Home Pageis displayed.

Go back to themanagement screen of the load balancer, no newsession should appear there.

No new session isrouted by the loadbalancer using thisspecific alias.

Disconnect from theapplication TypingCtrl+Shift+X

Siebel login screenappears.

Disable the alias createdin the eapps.cfg on allwebservers and applychanges by restarting theIIS services.

Platform is back to loadbalancing strategy.







Test Description Pre Conditions Post Conditions Acceptance Criteria

Steps Test Desc Notes Expected Results

CON07.1

CON07.2

CON07.3

CON07.4

CON07.5

Back to Total Page

This test is used to verify thatthe F5 load balancer canaccess the Siebel Servers andbe accessed by the Web

Servers.

The test platform must be set-up and running.

Using a remote access tool,connect to the server hostingthe load balancer.

Connected to the loadbalancer.

From this server, try to telnetall siebel servers hostingObject Managers componentson their default port.

Each server acknowledge andoffers a login prompt.

Disconnect from the loadbalancer server.

Disconnected from theload balancer server.

On each of the server hostingan Object Manager component, connect using aremote access tool.

Connected on eachserver hosting an OMcomponent.

From each one of theseservers, try to telnet the server hosting the load balancer onits default port.

The LB server acknowledge andoffers a login prompt.




Actual Result Pass / Fail Data Input Siebel R Siebel Reference




Steps Test Desc Notes Expected Results

CON08.1 A login page appears.

CON08.2

CON08.3

Back to Total Page

This test is used to verify that theF5 load balancer is properlyinstalled.

Test platform needs to be upand running.

Access the Load Balancer Admin Page using InternetEplorer

Log into the admin page of theload balancer.

The Load Balancer Admin Application isdisplayed,

Go to the list of nodes andcheck that all Siebel Serversrunning OMs are listed thereand have a green status.

All Siebel Servers running OMs arelisted and ready to receive traffic.




Actual ResulPass / Fail Data Input Siebel Ref Siebel Reference



Test Description Pre Conditions Acceptance Criteria Custom

Steps Test Desc Notes Expected Results Actual Resul

CON09.1

CON09.2

CON09.3

CON09.4

CON09.5

Back to Total Page

PostConditions

This test is to verify the proper execution of various Server Manager Commands.


From a test workstation with adedicated client installed, or from aserver of the platform through remoteaccess, launch a DOS promptwindows.

DOS prompt windowsappears.

Go to siebel_server_root\bin andlaunch the server manager by typinga command similar to srvrmgr /ggateway1 /e enterprise1 /s server1 /usadmin /p sadmin

The prompt changes todisplay the currentconnection status of theserver manager utility(srvrmgr:server_name>)

List the servers by typing the

following command: list servers

The list of the servers of the

enterprise is displayed.

List the active components of theplatform by typing the followingcommand: list component

The list of the componentsof the platform is displayed.

Disconnect from the server manager by typing: exit Then close the Dosprompt windows.

Dos prompt windows isclosed.



Custom Custom Custom Comments

Pass / Fail Data Input Siebel Ref Siebel Reference



Test Description Pre Conditions Post Conditi Acceptance Criteria

Test Step Test Step Description Notes Expected Results

CON10.1 Siebel Splash Screen is displayed

CON10.2

CON10.3

CON10.4

Back to Total Page


Siebel Gateway Server is up andservices are running. Warning!There is a major technical differencein the way certain admin views areaccessed depending if it is from a

dedicated or thin web client. In thefirst case, a direct connection (noFW ie) is required between theworkstation and the SiebelGateway.

Log onto Siebel eService withSiebel Administrator responsability(SADMIN type)

Press Ctrl+Shift+A to access thesite map

The Site Map is displayed showing thevarious views

Go to the View Administration /Configuration

The Server AdministrationConfiguration menu view is displayedas Administration - Server ConfigurationEnterprise Explorer EnterprisesComponent DefinitionsComponent GroupsSystem AlertsServersComponentsEventsParametersParameters

Click in the history back button(Siebel bouton not the IE bouton) inorder to come back to the Server Admin default View

The Screen view is displayed showingthe various views



CON10.5

CON10.6 The siebns.dat file is present

Go to the View Administration /Server Management

Administration - Server Management :-Administration - Server ManagementComponentsState ValuesStatisticsTasksEnterprisesServers

LogSessionsStatisticsTasksSessionsLogParametersState ValuesStatisticsTasksLogParametersState ValuesStatistics

Check to see if the siebns.dat fileexists







Point to verify : the specified file should belisted in a list applet





CON11.1 Prompt from remote server appears.

CON11.2 Siebel Home Page appears.

CON11.3 Siebel Login Page appears.

CON11.4 Files are copied to the server.

CON11.5

CON11.6

CON11.7 Siebel Home Page appears.

Back to Total Page

This test is used to demonstratethe operability of a commandline batch execution.

Requires a sample asynchronous batchprocess to test with expected results andmeans of validation.

From a test workstation with a dedicatedclient installed, or from a server of theplatform through remote access, launcha DOS prompt windows.

Depending of the batch treatment to beexecuted, check the status of the data tobe modified by connecting to theapplication.

Logout of the application by typing Ctrl-Shift-X

Copy the required files to the server that

will be running the batch treatment (ie.Where the Workflow Components Groupis hosted).

Go to siebel_server_root\bin and launchthe server manager by typing acommand similar to srvrmgr /g gateway1/e enterprise1 /s server1 /u sadmin /psadmin

The prompt changes to display thecurrent connection status of the server manager utility (srvrmgr:server_name>).

Type in the command to launch theasynchronous batch process to betested: start task for componentcomponent_alias_name server siebel_server_name withparameter_alias_name1=value1,parameter_alias_name2=value2

Prompt is displayed at the end of thetreatment and a log file is generated.

Depending of the batch treatment to beexecuted, check the status of the datamodified by connecting to theapplication.



Custom Custom Custom

Actual Result



Custom Comments

Siebel Ref



Test Descrip Pre Conditions Post Conditi Acceptance Criteria Custom Custom


CON12.1 Connected to each server of the platform

CON12.2

Back to Total Page

This test is toverify thatthe SiebelGateway

server isproperly set-up andrunning.


Using a remote access tool,connect to each of the servers of the platform

On each of theses server, type atelnet:port to check if the Gatewayservice is properly listening to onthe specified address:port

The Gateway is communicating properlywith each of the servers of the platform.




Siebel Ref




Test Step Test Step Description Notes Expected Results Actual Result

CON13.1

CON13.2

CON13.3

Back to Total Page

This test is to verify thesuccesful set-up of allconnection brokers.

Requires a precise list of all managedcomponents and their localisation(including port numbers of components)

Connect by remote access to one of theSiebel servers of the platform.

Connected to one of the servers

On this server launch a DOS promptwindows.

DOS prompt windowsis displayed.

Inside this DOS prompt windows, try totelnet each of the servers of the platform.Type: telnet IP:port in order to check if the connection broker service is listeningon the port numbers supplied to thetesting team.

The server answersby offering a loginprompt.




Siebel Ref




Test Step Test Step Description Notes Expected Results Actual Result

CON14.1

CON14.2

CON14.3

CON14.4

Back to Total Page

This test is to verify thatthe server manager isproperly monitoring andmanage the variousservers, components and

tasks of the plateform.

Requires a precise list of all managed componentsand their localisation.

Connect to theapplication using a SiebelAdministrator credentials.

Siebel Home PageAppears.

Go to the Site Map bytyping Ctrl+Shift+A

The Siebel Site Map isdisplayed.

Go to the Server Administration Screen

Server AdministrationScreen appears.

List the different servers,

component groups,components and tasks,and check their proper parameters against thelist that has beentransmitted to the testingteam.

The current tets

platform configuration issimilar to what has beenspecified.




Siebel Ref



Test Description Pre Conditions Post Conditi Acceptance Cri

Test Step Test Step Description Notes Expected ResulCON15.1

CON15.2

CON15.3

CON15.4

CON15.5

CON15.6

Back to Total Page

This test is to verify Oracle ODBC DataSource Connectivity from all SiebelServers.

Proper ODBC Drivers must have been installed onthe Siebel servers. Detailed parameters for ODBCconnection may be required (NLS_LANG &SORT_ORDER).

Connect on all Siebel Servers of the plateformusing a re+ote access tool. Navigate to the ControlPanel / Administrative Tools / Data Sources ODBC

The ODBC DataSources Panelis displayed

On the ODBC datasource Administrator ScreenDialogue box , select the system DSN tab

List of all DSNis displayed

Select the datasource used to connect to the TestEnvironment DB and check the values specified.

The selectedData source isdisplayed andthe values arecorrect.

Try to establish an ODBC connection to the DB -Click the Test Connect Button, using an active DBaccount.

A popupwindow confirmthe proper connection tothe DB

Launch the registry editor Regedit. In the windowsregistry locate the following keys:local_machine/software/odbc /odbc.ini/name_dsn

Options for theODBC DSN aredisplayed

Verify that the following registry keys are set asshown - Packet Size=0 EnableScrollabeCursors=0columnAsChar=1 ColumnSizeAsCharacter=1

Parameters arecorrect




Actual Result Siebel Ref Comments

May require tospecify a special

NLS_LANG &SORT_ORDERparameters here.Check with DevTeam.



Test DescriptPre Conditio Post Conditi Acceptance Custom Custom Custom Custom Comments


CON16.1

CON16.2

CON16.3

CON16.4

CON16.5

Back to Total Page

This test is toverify theaccessibilityof the FileSystem by all

the FileSystemManager Component.

Requires aprecise list of all managedcomponentsand their

localisation.


On each of the server hosting theFSMcomponent,connect

using aremoteaccess tool.

Connected toeach of theservershosting FSMcomponent.

Open a newwindowsexplorer session.

Newwindowsexplorer session isopen.

Type in thenetworkaddress of the Siebel

File System.

The contentof the FileSystemshared disk

space isdisplayed.

Try to createa newdirectory isthis shareddisk space.

A newdirectory iscreated.

Delete thisdirectory.

Directory isdeleted



Test Descrip Pre Conditio Post Conditi Acceptance Custom Custom Custom Custom Comments


CON17.1

CON17.2

Back to Total Page

This test is toverify thatonly therequiredapplication

web aliases(virtualdirectories inIIS) areactivated onthe platformand that theparametersare properlytunedbetween IISand SWSE.

Requires thatthe differentIIS serversand relatedeapps.cfg

files havebeenproperlytuned on theplateform.


On each of the WebServers, goto the IIScontrolpanel. List allvirtualdirectoriescreated in

IIS.

The list of virtualserversappears inIIS.

Check thatonly requiredvirtualdirectorieshave beenactivated.

Onlyrequiredvirtualdirectoriesareactivated.



CON17.3

CON17.4

For each of the virtualdirectory,check itsindividualparameter,especialy if itis a custom

created one.Compare itto a standardSiebelgeneratedone.

Each virtualdirectory setof parameter is checkedagainstandardSiebelcreated one.

Now againfor each of the webservers, edittheeapps.cfg fileand checkthat thealiases for Siebelapplicationsare properlyin tuned andin phase(portnumbers,type of IISthread, SSLactivation,target dll...)

with thevirtualdirectoriesfrom IIS.

Eapps.cfgfile isproperly set-up in phasewith virtualdirectories inIIS.



Test Description Pre Conditions Post Conditions

Test Step Test Step Description Notes

FO01.1

FO01.2

FO01.3

Back to Total Page

This test is to verify that the Fail Over mechanism Oracle Fail Safe is properlyrunning on the DB server.

Requires 2 instances of DB server with Fail Safe service running.



Acceptance Criteria Custom Custom Custom Custom Comments

Expected Results Actual Result Siebel Ref





FO02.1

FO02.2

FO02.3

FO02.4 The primary node has changed.

FO02.5

FO02.6

FO02.7

Back to Total Page

This test is to verify that theMSCS services are properlyinstalled and running.

Requires the MSCS are installed and arerunning on the specified servers.

Connect to the Siebel application usingstandard user credentials.

The Siebel Home page isdisplayed.

Using remote access tool, connect to theMSCS primary server, and display thecluster management tool.

The list of clustered servicesappears.

Still connected to the Siebel application,navigate randomly through the screens.

The application is respondingnormally.

On the MSCS admin panel, swithc theprimary node between the servers.

With the session still opened, continuethe navigation inside the Siebelapplication.

The cluster switch does notaffect the application behaviour.

On the MSCS cluster, check thegenerated log file, indicating the switch of primary node, it will have to be monitoredin Production.

The log file on the MSCSprimary node indicates a switchof the primary node.

Disconnect from the Siebel application bytyping Ctrl+Shift+X

The Siebel login screen isdisplayed.









FO03.1

FO03.2

FO03.3

FO03.4 Stop the IIS services.

FO03.5

FO03.6

Back to Total Page

This test is to verify the redundancy of the web servers. This test is to verifythe behaviour of an existing session incase of a web server crash.

Have the web servers running behind a NLBequipment or similar device, routing clients sessionseither to one or the other IIS.

Connect to the Siebel application using anycredential, through a web client session (IE).

By connecting to the web servers by using a remoteaccess tool and by editing the SWSE log files, identifywhich web server is actually being used by theopened session.

While still connected to the Siebel application, on theweb server dealing with the session, go to ControlPanel / Advanced / Services.

Wait a few seconds, then go back to your open Siebelsession in IE windows, and try to navigate to another screen.

Analyse the log files generated on the other webserver to see how was handled the switch.



Acceptance Criteria Custom Custom Custom Custom


The Siebel Home Page is displayed.

List of Services installed on the web server.

The IIS services are stopped.

The navigation is still possible.

The web server dealing with the new session isidentified.

Log file starts after the switch between webservers was made.



Comments



Test Description Pre Conditions Post Conditi Acceptance Criteri


FO04.1

FO04.2

FO04.3

FO04.4

FO04.5

FO04.6

FO04.7

FO04.8

FO04.9

FO04.10

Back to Total Page

This test is to verify that the Siebel Servers are properlyset-up in order to allow automatic resilient processing incase of anomaly on one of the servers of the enterprise.This test is also to verify the behaviour of an existing

session in case of an OM crash, by getting Asserts andnormal logs.

Need to have a properly set-upenvironement with a stable application andtechnical components as in Production.

Using Internet Explorer, connect to theSiebel application using any credential.

The Siebelapplicationappears.

Using a remote acces tool, connect to theweb servers. Edit the SWSE log files andidentify which web server and OM is used toprocess the current session.

The connectionpath is identifiedby editing theSWSE log file.

With the session still open in InternetExplorer, access the active Object Manager

server using a remote access tool. Edit theOM log file in order to confirm the Processand Task Ids.

The server runningthe Object

Manager isaccessed.

Using remote access tool or the dedicatedadministration web page, logon to the loadbalancing application and locate the routedsession.

The currentsession isdisplayed in theload balancer administrationpage.

Within the Internet Browser, try to navigaterandomly in the application.

Randomnavigation ispossible with noerror messages.

Back on the OM server, launch the taskmanager, locate the siebel process and kill i twhile the session is still open in the InternetExplorer session.

The Siebel OMprocess is killed.

Go back to the browser window after a fewseconds and try to proceed with somerandom navigation.

The navigation stillworks withoutserviceinterruption.

On the web servers, by analysing the logfiles, locate the new OM server used by theongoing session.

A new OM is usedto process theongoing session.

On the administration page of the loadbalancer, locate the routing information of

the killed OM. Also check out the new routeto the new OM created after the first onewas killed. See what has happened andanalyse the log files.

The load manager should exclude the

killed OM from itsroutinginformation.

On the first server where the OM was killed,restart the Siebel Services from the controlpanel. Make sure it restarts properly bylooking at the log files.

The first OM isrestarted properly.



FO04.11

FO04.12

Using another Internet Explorer windows,connect again to the Siebel application, if required several times in order for thesession to be handled by this first OM. UseSWSE log files to check the taqrget OMused by the new session.

A new session isopened on the firstOM.

Check in the Administration page of the loadbalancer that this OM has properlyreintegrated the load balancing strategy.

The OM is back inthe paltform and isused by the loadbalancer to routenew sessions.





Expectedbehaviour of

thiscomponent isstillunknowned.







SES01.1

SES01.2

SES01.3

SES01.4

SES01.5

SES01.6

SES01.7

SES01.8

SES01.9

SES01.10

SES01.11

SES01.12

SES01.13 Set the source status field to 'Good'

SES01.14 Set the Destination Location to 'External Location'

SES01.15 Set the Destination Availability to Allocated

SES01.16 Set the Destination Status field to Good

SES01.17 Set the Cause Type field to Wrong Quantity

SES01.18 Set the Commit Field Value to True

SES01.19

SES01.20 Logout of the application

Back to Total Page

This test is to verify that at the startof the user session an InitialRequest is created and maintainedwhilst the user performs thebusiness process of Stock Validation

and Error Correction script.

Test team has Admin Access to the all servers of the platform, User data and specific credentials must be loaded into the application prior to testing. A complete use case must be provided in order to completethe test. A HTTP monitoring tool must be installed on the testworkstation, and log level and log events must be changed at the

enterprise level in order to track navigation inside the OM processeslog files.

Connect to web servers and to the servers of the platfrom (using GUIor server manager) and adapt log levels and log events to what isrequired for the following test.

Log into Siebel Application entering User credentials supplied in theconfiguration table.

Using a HTTP monitoring tool, check that the HTTP messagegenerated for the new session contains SISNAPI specific header (consisting of the Siebel Enterprise server name and component

name)

On the web servers, navigate to the SWSE log file and browse for theObject Manager Session Information -ObjMgrSessionInfo. Only oneof the web servers deal with the user session.

Switch back to the Siebel Application and continue with step 2 of thescript User clicks on Site Map->Selects Inventory transactions->Inventory Transactions

Navigate to the SWSE log file and browse for the Object Manager Business Component Log - ObjMgrBusCompLog

Switch to the Siebel Application and continue with of the script. User

clicks on the New Tab to create a new record.From the drop down menu select the value for Type field to'Adjustment'.

From the drop down menu select the value for Product field to'Product'.

From the drop down menu select the value for Quantity field to'Quantity'.

From the drop down menu select the value for Source Location fieldto 'External'.

Set the value for the Source Availability field to Allocated'

Need to find out the correct step after this , as the step in the CAPGEMINI script appears to be incorrect.



SES01.21

SES01.22

SES01.23 Lower log levels on the SWSE and Entreprise

Navigate to the SWSE log file and check that each of the actionsperformed above have been written to the log file.

Go to the OM server executing the session, analyse the OM log filespecific to the user session. Check that the server log file contains thesession id created and identified in step 1 and that the session hasbeen maintained throughout the use case.





Log levels are modified on the SWSE and on the Entreprise.

The value of the Type Field is set to 'Adjustment'

The value of the Quantity Field is set to 'Quantity'

The value of the Source Location Field is set to 'External'

The value of the Source Availability Field is set to 'Allocated'

Source status field is set to 'Good'

Destinatiion Location is set to External Location

Destination Availability set to Allocated

Destination Status field is set to Good

Cause Type field is set to Wrong Type

Commit field value is set to True

Siebel login page is displayed again.

User logs onto the siebel application and the front page of the siebelapplication should be displayed

The new request will contain the HTTP header consisting of theSiebel Enterprise server name and component name

The Object Manager Session Information should display the currentuser session , Task ID ,PID , Time Stamp and Siebel Server Name

The Inventory Transactions list applet view should be displayedwith the fields displayed populated.

An entry of type ObjMgrBusCompLog - event type al ias should bewritten to the log file.

A new record will be created and the following fields will not be

populated

The value of the Product Field is set to 'Product' as identified in theconfiguration table.



SWSE log file contains information about the user navigation.

Log levels are back to normal.

The log file for the OM process contains detailed navigationinformation.



Comments

What we are testing here is the fact that the overall Busines Processis made under the same Task ID (TID) on one Object Manager Processes Instance (Server # + PID) for all the duration of theBusiness process. If connection pooling is implemented between theOM servers and the Oracle DB, the session analysis stops at the OM

level for logical reaons (pool of shared connections).

Warning, it will very likely be necessary to have a specific position /responsabilities to undertake all the business steps of this process.Usually Admin login cannot do all the tasks a business user can.

How do you get the SISNAPI message? Do you mean you get theSISNAPI specific header from HTTP message between the client andthe web server or the SISNAPI message between the web server and

the Siebel server?

In the SWSE log file, the server # used for each user session is anarbitrary numerical value generated by Siebel at installation time andreferenced in the siebns.dat; So we need a list of all these server numbers by using a Server Manager command line. We still need theSWSE log to trace back to the correct OM server PID and log file.

Need to validate the ObjMgrBusCompLog; Usually this session logrelated to a Component is on the server executing the PID.



Logs for this type listing operations are located on the server runningthe instance of the OM on which the user is connected. A set of specific log parameters need to be turned on (different from log level)to get the proper output, meaning a list of steps realised by the user within the GUI. The level of details may not be sufficient to "see" alloperations, but it is possible in case of doubt to compare this set of steps with the same type of log file recorded beforehand on aDedicated Web Client in Connected Mode.





SES02.1

SES02.2

Back to Total Page

This test is toverify that atthe start of the user session an

InitialRequest iscreated andmaintainedwhilst theuser performsone of theBusinessProcessScripts.

ObjectManager Logging levelset to 4

The term"session"may be moreapropriatethan

"request".Setting loglevel is finebut only tellsthe"richeness"of the logsgenerated,not it´scontent;Some "Eventlogging"options alsoneed to beactivated atthe sametime.


Set theSessionMonitor=True in the SWE

section of theeapps.cfg file

SessionMonitor=True in the SWEsection of the

eapps.cfg file

Reboot theSiebelApplicationServers

ApplicationServer Rebooted

Need toconfirm theneed toreboot theSiebelServers?May need areboot of theWeb Server as well.



SES02.3

SES02.4

Log intoSiebelApplicationentering user id and password assupplied inthe

configurationtable.

User logsonto thesiebelapplicationand theHome pageof the Siebelapplication

should bedisplayed

May requirespecific aloginassociated toa user withdefinedposition /responsabiliti

es in order todo theBusinessprocessentirely.

Wait adefinedmoment of time (2minutes for instance)

and launchanother browser window andlog intoSiebelApplicationagainentering thesame user idand password asabove.

User logsonto thesiebelapplicationand the frontpage of the

siebelapplicationshould bedisplayed ,there arenow twoinstances of the siebelapplicationhome pagerunning.

The delaybeforelaunching thesecondsession willbe useful to

differentiatethe twosessionseasily bylooking at thetotalconnectiontime.



SES02.5

SES02.6

Openanother window andconnectusing aSiebelAdministrator Responsabili

ty. Go to theserver adinistrationpages, getthe sessionID and checktheir individualstatus;Alternatively,a server manager commandlines can beused fromone of theservers or

from aworkstationwith adedicatedweb clientinstalled.

Session ID'sfrom theServer Manager GUI interfaceare displayedas -

Process anyof thebusinesshigh priorityscripts for example -CreateOrder ,CreateServiceRequests



SES02.7

SES02.8

SES02.9

SES02.10

Navigate tothe SWSEstats page byentering thefollowing urlin a newsession of the web

browser -http://host/application/_stats.swe?Verbose=High&Reset=True

The SWEstatisicalpagedisplays theSystemStats,Applications,Current

Sessions - 2users ,Locks, andCurrentOperationsProcessingstatisticalcategoriesand thenresets allnoncounter and currentoperationalstatistics

Compare thesessions idsand statusesids from theServer Manager GUI interfaceand thatdisplayedfrom theSWE statspage,

Session ID 'sshould beidentical.

Session IDare never identical.

Close theSWSE statspage

SWSE statspage isclosed.

Log out of the twoinstances of the Siebelapplication -File > Logout, File >Logout.

User islogged out of the twoinstances of the SiebelApplication.



SES02.11 Navigate tothe SWSEstats page byentering thefollowing urlin a newsession of the web

browser -http://host/application/_stats.swe?Verbose=High&Reset=True

The SWEstatisicalpage isdisplays theSystemStats,Applications,and the

previoussessionentries areremoved.





SES03.1

Back to Total Page

This test is toanalyse thenetwork dataconsumptionduring a

typicalbusinessprocess for one user.

Platform upand running.A networkmonitoringand analysis

tool must beinstalled on atestworkstationin order tomesure thebandwidth. Acompletebusinesscase must bedefined,along withadequatecredentialsandpreloadeduser data.


On a specificmonitoringworkstation,install thenetwork

monitoringtool and set itup tomeasuretrafficbetween theWS IPaddress andthe Server IPaddress;

Monitoringservice upand runningreqdy to logbandwidth;



SES03.2

SES03.3

Take note of the IPaddressesfrom thedifferentlocations youwish to test;Om servers,

web servers,loadbalancers,workstation...Input thisvalues intothemonitoringtool in order to mesurebandwidth.

Themonitoringtool is set-upin order tomeasurebandwidth.

Make surethat the logfile of themonitoringapplication isempty.

Themonitoringsystem for thebandwidth isready torecord point-to-pointtraffic.

The first timea user connects tothe Siebelapplication, alarge plugin(calledSiebelframwork) isdownloadedinto IE. Inorder tomeasure thisextrabandwidthconsumption,it is importantto remove it

from the IEplugins list.

Siebelframeworkplugin isremovedfrom IEplugins.



SES03.4

SES03.5

SES03.6

Start torecord thetraffic.

Themonitoringtool starts torecordbandwidth.

On themonitoring

workstation,log into theSiebelapplicationusing user credentials,and run acompletecriticalbusinessprocess.Finish thescript byproperlyclosing theIE session.

The businessscript data

bandwidthhas beenrecorded.

Use themonitoringtool to get aconsolidatedvalue for thebandwidthused duringthe businessscript,

Bandwidthduring thisbusinessscript isanalysed.





SES04.1

Back to Total Page

This test is toverify thetimeoutsetting of theplateform.

Platform upand running.


On the WebServers of the platform,edit the timeout setting intheeapps.cfgfile. It mustbe identicalon all webservers. EAI

specificconnectionaliases mayhave shorter time outvalues.

Time Outparameter isidenticalbetween webservers.



SES04.2

SES04.3

SES04.4

SES04.5

Log into theapplicationusing aSiebelAdministrator account.Check theSISNAPI

session timeout valuesfor theObjectManagers.These valuesshould besimilar or longer thanwhat is foundin the eappseven if theydon´t applyto the samepart of thesession. EAIOM may

have shorter SISNAPIsession timeout.

Time Outparameter for SISNAPIconnectionsis identicalbetweenOms.

Logout of theapplication

Siebel loginscreenappears.

If applicablecheck thevalues for time outparameterson the F5loadbalancingapplication.They shouldbe identicalto the onesfound on theOms.

Time Outparametersare identicalto the onesfound on theOms.

Connect nowusing atypical User credentials.

Siebel HomePageappears.



SES04.6

SES04.7

Leave thesession openfor anamount of time shorter by a fewseconds thanthe time out

set in theeapps.cfg file(may bespecific to anapplicationalias). Thenperform anykind of navigationsuch as adrill down.

Navigationshouldcontinuewithout error messagerelated totime outparameters.

Now leavethe sessionopen for anamount of timeexceeding bya fewseconds thetime out setin theeapps.cfgfile. Thenperform anykind of navigation

such as adrill down.

An error messagepops upsaying thatsession hastimed out.





SES05.1

Back to Total Page

This test is toverify thestatus of thesession onall the

differentservers incase of abrowser windowclosurewithoutproper logout.

Platform upand running.Admin rightson theservers of

the platform.Remoteaccess tooland socketlisting tool for IIS arerequired.


Login to theapplicationusing atypical user credentials.

Siebel HomePageappears.



SES05.2

SES05.3

Using aremoteaccess utility,access theweb serversand identifiyon which onethe session

is actuallyprocessed byanalysing theSWSE logfiles. Alsoidentify theObjectManager incharge of thesession. Alsoit is possibleto look at thesocketcreated toconnect tothe OM fromthe web

server usinganother tool.

The sessionis traced onone of theweb servers,

Using aremoteacces utility,access theOMprocessingthe sessionand edit thelog files for the OMprocess.

The sessionis traced onone of theOM servers.



SES05.4

SES05.5

SES05.6

SES05.7

Optionnaly,with the helpof a DBA,and if connectionpooling is notactivated, itmay be

possible totrace thesession onthe DB byusing thePID.

The sessionis traced onthe DB.

In the Siebelapplication,go to theContactscreen andadd a new

contact.

A newcontact iscreated.

Start tocreate asecond oneand in themiddle of theprocess,close thebrowser windowwithoutlogging out.

The windowis closedwithoutlogging out.

Go back tothe webserver,refresh thelog file andthe list of opensockets.There shouldbe a ghostsessionremainingfrom our previousconnection.

A ghostsession isstill openbetween theweb server and the OMdealing withthe session.



SES05.8

SES05.9

Now do thesame withthe OM, aghostsessionshould bestill runningwith the

same TaskID and PID.

A ghostsession isstill openbetween theweb server and the OMdealing withthe session.

Monitor thisghostsession untillit disepears,and comparethe timerequired for this time outto occur against theparametersset in

eapps.cfg fileand OMSISNAPItime outparameters

Time out for ghostsession issimilar toexistingparameters.





SES06.1

SES06.2

Back to Total Page

This test is toverify thebehaviour changebetween

cookie andcookie-lessmodes of theclient'sbrowser during theexecution of a Businesscriticalprocess.

Platform upand running.Ability tomodifyInternet

Explorer privacysettings ontheworkstation.User dataandcredentialsmust bepreloadedinto theapplication inorder to playthe use case,as well as astep by stepdescription of

the caseitself.


OpenInternetExplorer andgo to InternetOptions /PrivacySettings /AdvancedPrivacySettings.Make surecookiehandling isenabled.

Securitysettings aredisplayedcookies areaccepted.

Connect tothe SiebelApplicationusing atypical user credentials.




SES06.3

SES06.4

SES06.5

SES06.6

SES06.7

SES06.8

Go to thecookiedirectory andlook at thenewlycreatedcookies.

A new cookieis created for the Siebelsession.

Inside theapplication,run aBusinessCriticalProcess.

The usecase is raninto theapplication.

Logout fromtheapplicationby typingCtrl-Shift-X

The loginpageappearsagain.

Go back tothe cookie

directory for InternetExplorer.

The sessionspecific

cookieshould havedisapeared.

OpenInternetExplorer andgo to InternetOptions /PrivacySettings /AdvancedPrivacySettings.

Make surecookiehandling isdisablednow.

Cookiehandling isdisabled.

Connect tothe SiebelApplicationusing atypical user credentials.




SES06.9

SES06.10

SES06.11

Inside theapplication,run aBusinessCriticalProcess.Take note of all functional

differences inthe porcess.

The usecase is raninto theapplication.

Logout fromtheapplicationby typingCtrl-Shift-X

The loginpageappearsagain.

OpenInternetExplorer andgo to InternetOptions /PrivacySettings /AdvancedPrivacySettings.Make surecookiehandling isenabled.

Securitysettings aredisplayedcookies areaccepted.





SES07.1

SES07.2

SES07.3

Back to Total Page

This test is toverify theamount of DBtransactions

during atypicalBusinessprocess.

Platform upand running.Ability tomonitor transactions

on the DB.


Start themonitoringprocess onthe DB. Listall connectedusers withthere

respectivePID in order to trace backthe OM fromwhere thesession isopened. If noADSIautheticationis used withSiebel, onlyfew users(SIEBEL,GUESTCSTandSADMIN)should be

connected.

A list of active usersis displayed.

On thetestingworkstation,connect totheapplication

using atypical user credentials.


Check that anew sessionhas openedon the DB.

Thetransactionmonitoringstarts on theDB.



SES07.4

SES07.5

SES07.6

Run the usecase for atypicalBusinessProcess.

New recordsare created,existingrecords aremodified.

When theuse case isfinished,logout fromtheapplication.

The loginscreenappears.

Stoprecordingtransactionsfor thecorresponding session onthe DB. Thesession maystill be openfor a moment

after the user disconnects.

Thetransactionshave beenrecorded andcan now beanalysed.





SES08.1

SES08.2

SES08.3

Back to Total Page

Verify theproper settings of the IISthread mode

for connectionswith theSiebelServers.

The platformmust be upand running.We need toaccess the

Web Serversin order tovalidatecertainparametersin IIS.


For each of

the webservers,using remoteaccess,connect tothe controlpanel /Admin tools /IIS controlpanel

IIS control

panel isdisplayed.

For each of the virtualdirectories

existing inIIS, doubleclick on it inorder toaccess itsdetailedparameters.

A detailedparameterspopup

windowappears.

Click on theadvancedtab for IISsessiontuning

Advancedparametersappears.

To beconfirmed



SES08.4

SES08.5

SES08.6

SES08.7

SES08.8

Make surethe sessiontype for eachvirtualdirectory isproperly set-up accordingto Siebel

recommandations.

Session typeis inaccordanceto Siebelrecommandation.

Apply thechanges byrestarting IISservices

IIS servicesare restarted.

Launch asessionmonitoringtool in order to display IISthreads as

they arecreated.

A list of allIIS threadsappears.

Connect tothe Siebelapplicationusing astandarduser credentials.

A new threadis created.

Run a typicaluse case intotheapplication

whilemonitoringthe number andbehaviour of corresponding threadsopened byIIS on theweb server.

Threads arecreated andclosed downas the user

connects andthen logoutof theapplication.




Test Step Test Step Description Notes Expected ResultsSEC01.1

SEC01.6

SEC01.9

SEC01.2 Siebel Splash Screen is displaye

Back to Total Page

This test is to demonstrate that SSLencryption is used by the thin client (webbrowser) for accessing the Webserver andSiebel Server

SSL must be implemented beforehand on theTest plateform before we can proceed with thistest.

On each of the web servers, edit the eapps.cfgand check the proper parameters in the section[connmgmt]. Check that the application aliasesin this file are set-up with SSL URLs. Check onall Siebel servers that the entry 'SecureBrowse'in the 'SWE' section of the siebel.cfg file is setto "True"

The [connmgmt] section of each file is properly set-up. Applicationare properly set-up with SSL URLentry 'Secure Browser' in the 'SWof the siebel.cfg file is set to "True

Check that the default port setting is 443 - bytyping the following command netstat -a | grep443 at the DOS prompt while being connectedby remote access or telnet on the webserver.Do this on all web servers.

Displays all connections and listeon 443. The telnet allows to checproper instantiation of the SSL powebserver.

Also from the workstation on the command line,do a "telnet 443" toward both the webserversand the load balancing http equipment (requireIP adresses of both of these 2 servers and the

VIP of the load balancing equipment).

Telnet 443 responds on both servon the NLB (Network Load Balan

Log onto Siebel Application with administrator User ID and Password as defined in theResponsibilities table. Say OK to any certificatevalidation.



SEC01.3 The Site Map is displayed

SEC01.4

SEC01.5 The application displays an error

SEC01.7 The Screen Views are displayed

SEC01.8 User is logged out of the Siebel A

Once on the Home Page, type CTRL+Shift+Ato call the Site Map

Check in the Web browser that the URL startwith "https://" and is secure with a smallpadlock down right.

The URL starts with "https://" anddisplays down on the right hand browser window.

Try to force the http prefix by removing the "s"letter

Back Type CTRL+Shift+A to acces the SiteMap

Log out of the Siebel Application by typingCTRL+Shift+x



Custom Custom Comment

Siebel Ref Siebel.cfg file may be has a different name onthe target plateform.

Below, sample parameters for eapps.cfg

[connmgmt]CACertFileName =d:\siebel\admin\cacertfile.pemCertFileName = d:\siebel\admin\certfile.pemKeyFileName = d:\siebel\admin\kefile.txtKeyFilePassword = ^s*)Jh!#7PeerAuth = TRUEPeerCertValidation = FALSE

siebel.ssl.None.None://gtwyname/siebel/SSEObjMgr_enu

Need to be local or connected by telnet to do anetstat. Also may require Admin Tools on NTbox for the netstat executable.

This test should be done prior to go live fromvarious clients locations as routes may need tobe opened through corporate firewalls.






Test Step Test Step Description NotesSEC02.1

SEC02.2

SEC02.3

SEC02.4

Back to Total Page

This test is to demonstrate that an error message will be displayed to the user wherean incorrect password has beeen entered.

Admin Data must be already loaded into theTest plateform in order to test different user logins.

Log onto Siebel Application with administrator User ID and Password as defined in theConfiguration table.

Press the CTRL+Shift+A to access the SiteMap

Log out of the Siebel Application -CTRL+Shift+x

Attempt to log onto the Siebel Application withadministrator User ID and invalid password




Expected Results Actual Result Siebel Ref Siebel Splash Screen is displayed

The Site Map is displayed

User is logged out of the Siebel Application.

User enters correct User Id and incorrectpassword - An error is displayed on thescreen - Invalid Password. Please renter correct password.





SEC3.2

SEC3.3

SEC3.4

SEC3.5

Back to Total Page

This test is to demonstrate that an error message will be displayed to the user wherean incorrect User ID has been entered.

Admin Data must be already loaded into theTest plateform in order to test different user logins.

Log onto Siebel Application with administrator User ID and Password as defined in theConfiguration table.



Attempt to log onto the Siebel Application withincorrect administrator User ID and correctpassword

Check the error message in the log files stored

in the Log Directory for the error message




Expected Results Actual Result Siebel Ref Siebel Splash Screen is displayed

The Site Map is displayed


User enters correct User Id and incorrectpassword - An error message is displayedon the screen - Invalid User ID . Pleasereenter correct User ID

The log file should contain an entry eventtype alias Generic log with the user log indetails





SEC04.1

SEC04.2

SEC04.3

SEC04.4

SEC04.5

SEC04.6 Press CTRL +SHIFT+X

Back to Total Page

This test is to demonstrate that different viewsare accessible depending of the login used toconnect to the application.

Admin Data must be already loaded into theTest plateform in order to test views allocationmechanism.

Log onto Siebel Application with User ID andPassword as defined in the Configuration table.



Log onto Siebel Application with Administrator User ID and Password as defined in theConfiguration table.







Exit from application.

User ID and Password are authenticatedagainst ADSI/LDAP server. Users isgranted access and only the views thathave been defined for the user to accessare displayed.

User is granted access only to the viewsthat have been defined for the user toaccess will be displayed on the Site Map.

User is granted access only to the viewsthat have been defined for the user toaccess will be displayed on the Site Map.

User is granted access and All views thathave been defined for the user to accesswill be displayed.





SEC05.1

SEC05.2 Reboot the Web Server

SEC05.3

Check the URL in the Web browser

SEC05.4

SEC05.5 Select the Accounts

SEC05.6

SEC05.7

SEC05.8

SEC05.9

Back to Total Page

This test is to demonstrate that all viewaccess will be via https

User ID and Password granted with access tospecific views only.

Set the parameter ' SecureBrowse' in the swe

log file = True

Log onto Siebel Application with User ID andPassword as defined in the Configuration table.



Log onto Siebel Application with Administrator User ID and Password as defined in theConfiguration table.







WebServer Rebooted

Siebel Splash Screen is displayed




The entry SecureBrowse= True in the

SWE log file has been set

The web browser should display https:\\pathname , where pathname is defined asServer IP address and location

User ID and Password are authenticatedagainst ldap LIGHT WEIGHT DIRECTORYACCESS PROTOCOL - User is grantedaccess and Only the views that have beendefined for the user to access will be

displayed.

The Accounts View is selected via httpaccess.

User ID and Password are authenticatedagainst ldap LIGHT WEIGHT DIRECTORYACCESS PROTOCOL - User is grantedhttps access and all views that have beendefined for the user to access will be

displayed.




The platform must be up and running.


SEC06.2

SEC06.3

Back to Total Page

This test is to ensure that password data for Anonymous and Webupdate accounts are notstored in clear in the eapps.cfg file.

On the siebel web server navigate to theeapps.cfg file found in the bin directory

Check that the setting for encrypted passwordis set to true .ie EncryptedPassword=True

Check that the values for AnonPassword etWebUpdatePassword are encrypted





EncryptedPassword=True

User navigates to the eapps.cfg file under the bin directory.

Values for AnonPassword andWebUpdatePassword are encrypted.




The platform must be up and running.


SEC07.1

Back to Total Page

This test is to ensure that passwords for standard Siebel accounts have properly beenmodified.

User attempts to log into the Siebel Applicationwith several standard User ID : SADMIN,GUESTCST, LDAP, SIEBEL, each time with apassword similar to the login





Error Message displayed - Please enter correct User ID and Password for each try.





SEC08.1

SEC08.2

SEC08.3 Reboot the Siebel Web Server

SEC08.4

SEC08.5 Type in the Password in the Password Field

Back to Total Page

User has Admin Access to the Siebel WebServer

On the siebel web server navigate to theeapps.cfg file found in the bin directory

Check that the setting for encrypted passwordis set to true .ie EncryptedPassword=True

Log into the Siebel Web Server in User Namein the User Name Field





EncryptedPassword=True

Siebel web server Reboots

User Name is is displayed in clear text

User navigates to the eapps.cfg file under

the bin directory

Password entered in the Password Field inencrypted





SEC09.2 Type Ctrl+Sht+A to access the Site Map

SEC09.3 Click on the Admin View.

SEC09.4

SEC09.5 Type Ctrl+Sht+X to logout

SEC09.6

Back to Total Page

This test is to validate the proper setting of theplateform in order to allow users to changetheir password.

Depending of the authetication modeimplemented, certain settings may benecessary to allow password change by users.

Connect to the Siebel application using a User login as specified in the responsibilites page

In the password field, type a new password andconfirm it.

Login with the same user ID and the newpassword.





The Site Map is displayed.

The Admin View is displayed.

The new password is confirmed.

The login page is displayed again

The Siebel Home page is displayed into thebrowser window.

The Siebel Home page is displayed into thebrowser window.



Comments

Check the name of the view where a user canmodify his password





SEC10.1

SEC10.2

SEC10.3

SEC10.4

SEC10.5

Back to Total Page

This test checks the status of SSL encryptedSISNAPI communication between the Webservers and the Siebel Servers.









SEC11.1SEC11.2

SEC11.3

SEC11.4

SEC11.5

Back to Total Page

This test is to validate the proper settings of the ADSI/LDAP authentication process.

Requires the ADSI/LDAP login authenticationmode to be implemented.









SEC12.1

SEC12.2

SEC12.3

SEC12.4

Back to Total Page

This test is to validate that the various SiebelServices are run under a common specificDomain account.

Have System Admin rights on each of the serversor at list be able to l ist running services from thecontrol pannel.

For each Siebel server of the plateform, connectto the service list of the Control Panel, usingremote access tools or System Tools.

Verify that the Siebel Specific services run under the same Domain account on all the servers

For each of the Web server, connect the sameway and check the Domain account used to runIIS services.

For each other server of the plateform (Actuate,Load Balancing...) do the same test and verifythat each time a specific Domain account is usedto run the different services.





The list of all services with status appears

The same Domain account is used to startthe Siebel Services on all servers of theplateform

The IIS services are run with the sameDonmain account on the different WebServers

Specific Domain accounts are used to runeach one of the different services.





SEC13.1

SEC13.2

Back to Total Page

This test is to validate the inability to connectdirectly to the File System and to the DB froma Web Client workstation.

Requires a network and workstation set-upsimilar to ones used on the target architecture.

From the workstation from a DOS commandwindow, run the following command in order totest the connectivity to the DB server : telnetport number of the Oracle listener

Open a file explorer window and type the URLof the File System in the address bar.





No answer must be received showing thatthe listener is not open to direct querriesfrom the end users sub-network

An error message appears of the type : Thespecified network share or drive isunreachable.





SEC14.1

SEC14.2

SEC14.3

Back to Total Page

This test is toverify that anerror will bedisplayed onlogin page if

an invalidanonymouscredential isprovided intheeapps.cfgfile.

Platformmust be upand running.


Try toconnect totheapplicationby callingone of thespecifiedURL.

Login pageappears.

Now edit theeapps.cfg fileon all webservers.Modify thelogin usedfor anonymouslogin(GUESTCST) on bothdefault andspecificaliasessections.

The loginused for anonymouslogin ismodified.

Restart theweb servers

and try toconnect totheapplicationby callingone of thespecifiedURL.

An error page is

displayed.



SEC14.4

SEC14.5

Now againon all webservers, edittheeapps.cfg fileon all webservers. Putback the

standardlogin for anonymouslogin, butchange thepassword.Warning, if the passwordis encrypted,copy it in asafe place aswe will needto put it backafter thistest. Oncethe passwordis modified,

save the fileand restartthe IIS.

Standardanonymouspassword isput backagain, badpassword isspecified. Anerror page

appearswhenaccessingtheapplication.

Analyse thelog file of theSWSE as itshows whatproblemswasencounteredwith usefulerror codes.

SWSE error codes areanalysed.



SEC14.6

Roll back thechanges byediting againtheeapps.cfgand puttingback theoriginal

password.Restart theweb serversand try toaccess thespecifiedURL.

Login pageappears.




Steps Test Desc Notes

AV01.1

AV01.2

AV01.3

AV01.4 In the Control Panel, go to the Services list.

AV01.5

AV01.6

AV01.7

Back to Total Page

This is to verify that the Gateway Server isaccessible from the various servers of theenterprise.

All Siebel Server Components are installed onthe platform

Connect to each Siebel server of the Enterpriseand try to access the siebel gateway service bytyping in a DOS command window - telnet ipaddress AND specific port number where ipaddress and port are defined in theconfiguration table.

On server reponse at prompt, Enter User IDand Password

Connect to the Siebel Gateway Server locallyor with a re+ote access tool.

Look for the Siebel Gateway service in the list.

It should be running, in automatic launch modeand launched by a specific Domain account.

Navigate to the \gtwysrvr\ADMIN on the SiebelGateway server.

Check to see if the siebns.dat file exists.




Expected Results Actual Result Pass / Fail Data InpuSiebel Ref Siebel Refer The Gateway answers to the telent request.

A list of services is displayed.

The prompt changes to \gtwysrvr\ADMIN.

The siebns.dat file is present.

User is now connected to the SiebelGateway Service

User is now connected to the SiebelGateway Service

The Siebel Gateway service is running inautomatic mode and launched by a specificDomain user.



Comments

nce

Need to make a backup task of the siebns.dat

Only possible localy on the server or withAdministration pack for Windows from aworkstation or with special tools to seeprocesses remotely.





AV02.1

AV02.2

AV02.3 Select the Process Tab

AV02.4

AV02.5

AV02.6

Back to Total Page

This is to verify that the name server service isrunning on the Siebel Gateway Server

Siebel Gateway Server is up and services arerunning

Telnet on to the siebel gateway service - telnetip address where ip address is defined in theconfiguration table, enter User ID andPassword

Press simultaneously the CTRL ALT DEL keys

Check to see if the Name Server Servicesiebsvc.exe is present

Navigate to the \gtwysrvr\ADMIN on the SiebelGateway server

Check to see if the siebns.dat file exists





The Windows Task Manager is displayed

A list of processes running are displayed.

The prompt changes to \gtwysrvr\ADMIN

The siebns.dat file is present

The User Name and Password aredisplayed

The Name Server Service siebsvc.exe ispresent



Comments

Redondant test with AV01R





AV03.1

AV03.2 Press Ctrl+Shift+A to access the site map

AV03.3 Go to the View Administration / Configuration

AV03.4

AV03.5

Back to Total Page

This test is to verify that the server administration view can be accessed from theweb client

Siebel Gateway Server is up and services arerunning. Warning! There is a major technicaldifference in the way certain admin views areaccessed depending if it is from a dedicated or thin web client. In the first case, a direct

connection (no FW ie) is required between theworkstation and the Siebel Gateway.

Log onto Siebel eService with SiebelAdministrator responsability (SADMIN type)

Click in the history back button (Siebel boutonnot the IE bouton) in order to come back to theServer Admin default View

Go to the View Administration / Server Management



AV03.6 Check to see if the siebns.dat file exists






The Site Map is displayed showing thevarious views

The Server Administration Configurationmenu view is displayed asAdministration - Server ConfigurationEnterprise Explorer

EnterprisesComponent DefinitionsComponent GroupsSystem AlertsServersComponentsEventsParametersParameters

The Screen view is displayed showing thevarious views

Administration - Server Management :-Administration - Server ManagementComponentsState ValuesStatisticsTasksEnterprisesServersLogSessionsStatisticsTasksSessionsLogParameters

State ValuesStatisticsTasksLogParametersState ValuesStatistics



The siebns.dat file is present



Comments



Point to verify : the specified file should belisted in a list applet




Test Step Test Step Description NotesAV04.1

AV04.2

AV04.3

AV04.3.1

AV04.4

AV04.5

AV04.6 Return to the CLI - Command Line Interface

AV04.7

AV04.8

AV04.9

Back to Total Page

This test is to verify that the load balancingconfiguration file can be generated by typingthe command LBCONFIG at the consolecommand line

Siebel Gateway Server is up and services arerunning

On a server of the Enterprise by remoteaccess, or on a workstation with dedicated webclient and server manager installed, open aDOS session by selecting START >RUN andtype CMD in the Open drop down list andselect ok

At the DOS prompt navigate to the \binsubdirectory within the Siebel Server rootdirectory ie cd \siebel_server_root\bin

At the DOS prompt type srvrmgr /ssiebel_server where siebel_server name is thename of the Siebel Server on which we aregoing to launch the commands (this name is

specified in the configuration table) and pressenter

Enter SADMIN type login information in order tostart the srvmgr session on the target server

Type the following command at the dos prompt- startup appserver siebel_server_name

Check that the specified Siebel Server hasstarted by examining the processes in windowsTask Manager Ctr Alt Del and selecting theprocess tab

Type at the command line interface - generatelbconfig and hit <enter> key

Check that the Lbconfig file has been stored inthe admin subdirectory of the Siebel Server installation directory as \sieble\eapps\admin

Review the contents of the generatedlbconfig.txt file to verify that virtual server definitions do not include any Siebel Serversthat will not participate in load balancing




Expected Results Actual Result Siebel Ref The DOS session is now visible

The siebel server starts

Command Line Interface prompt is visible.

The IB Config file is generated

The DOS prompt should change to indicatethat you are now in thesiebel_server_root\bin directory.

The Siebel Server Manager program hasstarted and the dos prompt changes tosvrmgr:siebel_server where thesiebel_server is the name specified in the

configuration tables

The Server Manager component -ServerMgr.exe file should be shown asrunning as a process.

Lbconfig file is stored in Siebel Server installation directory as\sieble\eapps\admin

The virtual server definitions do not includeany Siebel Servers that will not participatein load balancing




Database must be available


AV05.1

AV05.2

AV05.3

AV05.4

AV05.5

AV05.6

Back to Total Page

This test is to verify ODBC Data sourceConnectivity for Oracle in a windowsenvironment

Navigate to the Control Panel >PerformanceMaintenance >Administrative Tools>DataSources ODBC

On the ODBC datasource Administrator ScreenDialogue box , select the system DSN tab

Select the datasource labeled as and click thconfigure

To test the ODBC connection - Click the TestConnect Button

In the windows registry locate the followingregistry enrty key - hkey-local-machinesoftware odbc odbc.ini name_dsn

Verify that the following registry keys are set asshown - Packet Size=0EnableScrollabeCursors=0 columnAsChar=1ColumnSizeAsCharacter=1





The DOS session is now visible

The siebel server starts

Command Line Interface prompt is visible.

The DOS prompt should change to indicatethat you are now in thesiebel_server_root\bin directory.

The Siebel Server Manager program hasstarted and the dos prompt changes tosvrmgr:siebel_server where thesiebel_server is the name specified in theconfiguration tables

The Server Manager component -ServerMgr.exe file should be shown asrunning as a process.






AV06.1

AV06.2

AV06.3

AV06.4

Back to Total Page

This test is to verify that an error will bedisplayed if the web server port entry isincorrect in the eapps.cfg file

Edit the value of the Web Server port entryunder the SWSE section of the eapps.cfgconfig file by changing this value to a nonexistent port number

Save the changes in the eapps.cfg file andrestart the web server

Log into the Siebel Client and enter Usernameand Password

Launch the siebel web client by entering theuser id and password specified and pressingthe enter key





Current Web server entry is edited

User logs into the Siebel Client

Page cannot be displayed

Eapps.cfg file changes are saved and WebServer is rebooted



Comments

Port number change requires much morechanges;-IIS port-Firewalls and Network routing-Various Siebel Parameters such as eapps.cfg






AV07.1

AV07.2

AV07.3

AV07.4

Back to Total Page

This test is to verify that an error will bedisplayed if the virtual directories have notbeen created on the web server.

On each of the Web servers, connect to the IISAdministration Panel

Remove the path pointing to the virtual webentries under the SWSE section of theeapps.cfg config file.

Save the eapps.cfg file and restart the webserver so the changes take effect.

Launch the siebel web client by entering theuser id and password specified and pressingthe enter key.





List of all IIS services appears

Page cannot be displayed

Current virtual directories on the webserver are removed

eapps.cfg file changes saved and webserver restarted.



Comments

The operation described here will block accessto the Siebel Server but not to the web server.Disabling application aliases requires changesin both IIS and eapps.cfg file.






AV08.1

AV08.2

AV08.3

Back to Total Page

This test is to verify that an error 'page notfound 'will be displayed if an invalid user name exists.

Edit the http entry under the default settings of the eapps.cfg file by entering an invalidusername

Save the eapps.cfg file and reboot the webserver for changes take effect.






http entry edited

Page Not Found error is displayed

eapps.cfg file is saved and web server isrebooted.





AV09.1

AV09.2

AV09.3

Back to Total Page

This test is to verify that a blank page will bedisplayed if the password settings areincorrect.

This test is to verify that a blank page will bedisplayed if the http port settings are incorrect

Edit the http entry under the default settings of the eapps.cfg file by entering an invalidpassword.

Save the eapps.cfg file and reboot the webserver for changes take effect.






Page Not Found error is displayed

http entry edited with an invalid portaddress

eapps.cfg file is saved and web server isrebooted.





LOA01.1

LOA01.2

Back to Total Page

This test isdesigned toconfirm theproper routing

betweenOM's of newincomingsessions.

Requires anadminaccess toLoadBalancing

application inorder to tracein real timethe routing of newsessions.Also requiresaccess tovarious logfiles onSiebel andWebServers.


Using remoteaccess or managementpanel,access theF5 loadbalancingapplication.

The list of routedsessionsappears.

Connect totheapplicationusing atypical user credentials.

The SiebelHome Pageappears.



LOA01.3

LOA01.4

LOA01.5

According tothe routinginformationdisplayed onthe F5 loadbalancer or by analysingthe SWSE

log file, pickthe OMserver executing thesession andedit the logfile of thespecific OMprocess.

Routinginformation isdisplayed onF5 and thedetailedinformation isaccessibleon the OM

server executing thesession.

Usinganother InternetExplorer window,connectanother timeto theapplication,using either the samelogin or adifferent one.

Siebel homepage isdisplayedagain,

Going backto the loadmanager,another OMserver isaddressed toopen a newsession. Onthis server,edit the logfile for thespecific OMprocess.

Routinginformation isdisplayed onF5 and thedetailedinformation isaccessibleon the OMserver executing thesession.



LOA01.6 Open asmanysessions aswanted totest thatindividualsessions areproperly

routed. AllOM serversshould beaddressedstatisticaly inaccordancewith the rulesestablishedfor the F5loadbalancer,

Other sessions areopened androuted toother OMserversdepending of the rules

establishedon the F5loadbalancer.





LOA01.1

LOA01.2

Back to Total Page

This test isdesigned toconfirm thatthe NLBequipment

placed infront of theWeb Serversproperlyroutesincomingsessions toeach of theweb servers.

Ability toconnect fromnumerousworkstationspossibly with

different IPaddressesdepending of the IP routingstrategychosen.


Connect totheapplicationusing atypical user credentialsfrom atestingworkstation.Take note of the networkparametersof theworkstation.

The SiebelHome Pageappears.

By analysingthe SWSElog files,identify theweb server on which theconnection isrouted.

Theconnection isdirected to aspecific webserver.



LOA01.3

LOA01.4

Depending of the NLBcriterias for routing,connect totheapplicationusing either

another workstationwith another IP address(fixed IProuting), or with thesame one(dynamic IProuting).

Siebel homepage isdisplayedagain,

By analysing

the SWSElog files,identify theweb server on which theconnection isrouted.

The

connection isdirected to aspecific webserver.





LOA03.1

Back to Total Page

This test is toverify thatthe loadbalancingconfiguration

file can begenerated bytyping thecommandLBCONFIGat theconsolecommandline

F5 loadbalancer isinstalled andproperlytuned to

routerequests toSiebelServers OM.

Test Step

Description

On a server of theEnterprise byremoteaccess, or ona workstationwithdedicatedweb clientand server manager installed,open a DOSsession by

selectingSTART>RUN andtype CMD inthe Opendrop downlist andselect ok

The DOSsession isnow visible



LOA03.2

LOA03.3

LOA03.4

LOA03.5

At the DOSpromptnavigate tothe \binsubdirectorywithin theSiebelServer root

directory iecd\siebel_server_root\bin

The DOSpromptshouldchange toindicate thatyou are nowin thesiebel_server

_root\bindirectory.

At the DOSprompt typesrvrmgr /ssiebel_server wheresiebel_server name is thename of theSiebelServer onwhich we aregoing tolaunch thecommands(this name isspecified intheconfigurationtable) andpress enter

The SiebelServer Manager program hasstarted andthe dospromptchanges tosvrmgr:siebel

_server where thesiebel_server is the namespecified intheconfigurationtables

Enter Server Administrator typecredentiqls inorder to startthe srvmgr session onthe targetserver

Logged asSADMIN or similar account.

Return to theCLI -

CommandLineInterface

CommandLine

Interfaceprompt isvisible.



LOA03.6

LOA03.7

Type at thecommandline interface- generatelbconfig andhit <enter>key

The IBConfig file isgenerated

Check thatthe Lbconfigfile has beenstored in theadminsubdirectoryof the Siebel

Server installation

Lbconfig fileis stored inSiebelServer installationdirectoryas\sieble\eapps\admin

Documents

Test Schedule PPT V3