Test Schedule PPT V3

Num Domain 1 Security
Test ID SEC01
2 Security
SEC02
3 Security
SEC03
4 Security
SEC04
5 Security 6 Security 7 Security 8 Security 9 Security
SEC05 SEC06 SEC07 SEC08 SEC09
10 Security 11 Security 12 Security
SEC10 SEC11 SEC12
13 Security
SEC13
14 Security 15 Availability 16 Availability
SEC14 AV01 AV02
17 Availability
AV03
18 Availability 19 Availability 20 Availability 21 Availability 22 Availability 23 Availability
AV04 AV05 AV06 AV07 AV08 AV09
24 Load Balancing RR
LOA01
LOA02
LOA03
27 Session Management
SES01
28 Session Management 29 Session Management
SES02 SES03
SES04 SES05
32 Session Management
SES06
SES07 SES08
35 Connectivity
CON01
36 Connectivity
CON02
37 Connectivity 38 Connectivity 39 Connectivity 40 Connectivity 41 Connectivity 42 Connectivity 43 Connectivity 44 Connectivity
CON03 CON04 CON05 CON06 CON07 CON08 CON09 CON10
45 Connectivity
CON11
46 Connectivity 47 Connectivity
CON12 CON13
48 Connectivity
CON14
49 Connectivity
CON15
50 Connectivity
CON16
51 Connectivity
CON17
52 Fail Over
FO01
53 Fail Over
FO02
54 Fail Over
FO03
55 Fail Over
FO04
56 Deployment
DEP01
57 Deployment
DEP02
58 Deployment 59 Deployment 60 Deployment 61 Deployment 62 Deployment 63 Deployment
DEP03 DEP04 DEP05 DEP06 DEP07 DEP08
64 Deployment
DEP09
65 Deployment
DEP10
66 Deployment 67 Deployment
DEP11 DEP12
68 Maintainability 69 Maintainability 70 Caching 71 Caching 72 Caching 73 Caching 74 Caching 75 End to End Share to Smart
MAI01 MAI02 CAC01 CAC02 CAC03 CAC04 CAC05 DAT01
Test Description
This test is to demonstrate that SSL encryption is used by the thin client (web browser) for accessing the Webserver and Siebel Server
Prerequisite
SSL must be implemented beforehand on the Test plateform before we can proceed with this test. Admin Data must be already loaded into the Test plateform in order to test different user logins. Admin Data must be already loaded into the Test plateform in order to test different user logins.
This test is to demonstrate that an error message will be displayed to the user where an incorrect password has beeen entered.
This test is to demonstrate that an error message will be displayed to the user where an incorrect User ID has been entered.
This test is to demonstrate that different views are accessible depending of Admin Data must be already loaded the login used to connect to the application. into the Test plateform in order to test views allocation mechanism.
This test is to demonstrate that all view access will be via https
User ID and Password granted with access to specific views only. The platform must be up and running. The platform must be up and running. 0 Depending of the authetication mode implemented, certain settings may be necessary to allow password change by users.
This test is to ensure that password data for Anonymous and Webupdate accounts are not stored in clear in the eapps.cfg file. This test is to ensure that passwords for standard Siebel accounts have properly been modified. User has Admin Access to the Siebel Web Server This test is to validate the proper setting of the plateform in order to allow users to change their password.
This test checks the status of SSL encrypted SISNAPI communication between the Web servers and the Siebel Servers. This test is to validate the proper settings of the ADSI/LDAP authentication process. This test is to validate that the various Siebel Services are run under a common specific Domain account. Requires the ADSI/LDAP login authentication mode to be implemented.
Have System Admin rights on each of the servers or at list be able to list running services from the control pannel.
This test is to validate the inability to connect directly to the File System and Requires a network and workstation to the DB from a Web Client workstation. set-up similar to ones used on the target architecture. This test is to verify that an error will be displayed on login page if an invalid Platform must be up and running. anonymous credential is provided in the eapps.cfg file. This is to verify that the Gateway Server is accessible from the various servers of the enterprise. This is to verify that the name server service is running on the Siebel Gateway Server All Siebel Server Components are installed on the platform Siebel Gateway Server is up and services are running
This test is to verify that the server administration view can be accessed from the web client
Siebel Gateway Server is up and services are running. Warning! There is a major technical difference in the way certain admin views are accessed depending if it is from a dedicated or thin web client. In the first case, a direct connection (no FW ie) is required between the workstation and the Siebel Gateway.
This test is to verify that the load balancing configuration file can be Siebel Gateway Server is up and generated by typing the command LBCONFIG at the console command line services are running This test is to verify ODBC Data source Connectivity for Oracle in a windows environment This test is to verify that an error will be displayed if the web server port entry is incorrect in the eapps.cfg file This test is to verify that an error will be displayed if the virtual directories have not been created on the web server. This test is to verify that an error 'page not found 'will be displayed if an invalid user name exists. This test is to verify that a blank page will be displayed if the password settings are incorrect. Database must be available All Siebel Services are available All Siebel Services are available All Siebel Services are available This test is to verify that a blank page will be displayed if the http port settings are incorrect Requires an admin access to Load Balancing application in order to trace in real time the routing of new sessions. Also requires access to various log files on Siebel and Web Servers.
This test is designed to confirm the proper routing between OM's of new incoming sessions.
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 web servers.
Ability to connect from numerous workstations possibly with different IP addresses depending of the IP routing strategy chosen.
This test is to verify that the load balancing configuration file can be F5 load balancer is installed and generated by typing the command LBCONFIG at the console command line properly tuned to route requests to Siebel Servers OM.
This test is to verify that at the start of the user session an Initial Request is Test team has Admin Access to the created and maintained whilst the user performs the business process of all servers of the platform, User data Stock Validation and Error Correction script. and specific credentials must be loaded into the application prior to testing. A complete use case must be provided in order to complete the test. A HTTP monitoring tool must be installed on the test workstation, and log level and log events must be changed at the enterprise level in order to track navigation inside the OM processes log files.
This test is to verify that at the start of the user session an Initial Request is Object Manager Logging level set to created and maintained whilst the user performs one of the Business 4 Process Scripts. This test is to analyse the network data consumption during a typical business process for one user. Platform up and running. A network monitoring and analysis tool must be installed on a test workstation in order to mesure the bandwidth. A complete business case must be defined, along with adequate credentials and preloaded user data.
This test is to verify the timeout setting of the plateform. This test is to verify the status of the session on all the different servers in case of a browser window closure without proper logout.
Platform up and running. Platform up and running. Admin rights on the servers of the platform. Remote access tool and socket listing tool for IIS are required.
This test is to verify the behaviour change between cookie and cookie-less modes of the client's browser during the execution of a Business critical process.
Platform up and running. Ability to modify Internet Explorer privacy settings on the workstation. User data and credentials must be preloaded into the application in order to play the use case, as well as a step by step description of the case itself.
This test is to verify the amount of DB transactions during a typical Business Platform up and running. Ability to process. monitor transactions on the DB. Verify the proper settings of the IIS thread mode for connections with the Siebel Servers. The platform must be up and running. We need to access the Web Servers in order to validate certain parameters in IIS.
This test is to verify that each element of the connection process are required to enable connection of a thin client
All required components of the platform must be set-up prior to testing
This test is to verify that the http local Deamon of a Mobile Client is only accessible localy.
Require a typical target mobile client workstation. The server must be setup in order to allow the creation and the management of remote users.
This test is to verify that the Siebel Wireless Gateway is accessible from a handheld device. This test is to verify that the Siebel Gateway is accessible from external network. This is to verify that the Gateway Server is accessible from the various servers of the enterprise. Requires that the various network gateways are properly set-up All Siebel Server Components are installed on the platform
This test is used to verify that round robbing load balancing is dependent of Test platform needs to be up and the application aliases definition in the eapps.cfg running. This test is used to verify that the F5 load balancer can access the Siebel Servers and be accessed by the Web Servers. This test is used to verify that the F5 load balancer is properly installed. This test is to verify the proper execution of various Server Manager Commands. This test is to verify that the server administration view can be accessed from the web client The test platform must be set-up and running. Test platform needs to be up and running. Test platform needs to be up and running. Siebel Gateway Server is up and services are running. Warning! There is a major technical difference in the way certain admin views are accessed depending if it is from a dedicated or thin web client. In the first case, a direct connection (no FW ie) is required between the workstation and the Siebel Gateway.
This test is used to demonstrate the operability of a command line batch execution.
Requires a sample asynchronous batch process to test with expected results and means of validation.
This test is to verify that the Siebel Gateway server is properly set-up and running. This test is to verify the succesful set-up of all connection brokers.
Test platform needs to be up and running. Requires a precise list of all managed components and their localisation (including port numbers of components) Requires a precise list of all managed components and their localisation.
This test is to verify that the server manager is properly monitoring and manage the various servers, components and tasks of the plateform.
This test is to verify Oracle ODBC Data Source Connectivity from all Siebel Proper ODBC Drivers must have Servers. been installed on the Siebel servers. Detailed parameters for ODBC connection may be required (NLS_LANG & SORT_ORDER).
This test is to verify the accessibility of the File System by all the File System Manager Component.
Requires a precise list of all managed components and their localisation.
This test is to verify that only the required application web aliases (virtual Requires that the different IIS directories in IIS) are activated on the platform and that the parameters are servers and related eapps.cfg files properly tuned between IIS and SWSE. have been properly tuned on the plateform.
This test is to verify that the Fail Over mechanism Oracle Fail Safe is properly 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 and running.
Requires the MSCS are installed and are running on the specified servers.
This test is to verify the redundancy of the web servers. This test is to verify Have the web servers running the behaviour of an existing session in case of a web server crash. behind a NLB equipment or similar device, routing clients sessions either to one or the other IIS.
This test is to verify that the Siebel Servers are properly set-up in order to allow automatic resilient processing in case 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 and normal logs.
Need to have a properly set-up environement with a stable application and technical components as in Production.
This test is to demonstrate that when the Database is unavailable - an error Have Database rollback segments will be displayed when the user attempts to access the database. properly tuned, and a full backup available in case on DB crash requiring a full restore.
This test is to demonstrate that when the File System Shared Directory is unavailable - documents, file attachments and images will not be made available.
FSM Components properly set-up on the platform, in accordance with the File System access rights and network settings (firewall opening and IP routing)
This test is to demonstrate that when the File System Manager component is not enabled requests that use the FSM will return an error message This test is to demonstrate that when the File System Manager component is 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 siebel application when the Gateway Name Server has been disabled
All components are available.
All components are available.
The Siebel Gateway must be properly backed up
This test is to verify that when the Siebel Servers are unavailable - the user Existing Services are up and running will receive an HTTP error message on attempting to log into the Siebel Application This test is to demonstrate that when the Web Servers are unavailable - an Existing Service are up and running error will be displayed to the user and the Siebel Application will be unavailable. This test is to verify that the web client supports HTTP 1.1 protocol Internet explorer is available and user can access IE settings.
This test is to verify that Microsoft IIS virtual diectories have been created on the Siebel Web Server
You must have installed all key Siebel Enterprise Server components, including the Siebel Gateway Name Server, at least one Siebel Server, and the Database Configuration Utilities. and configured the Siebel Gateway Name Server, created and configured the Siebel Enterprise, created the SWSE logical profile, and configured the Siebel Server.
This test is to verify that all Siebel Gateway Name Services have started.
All Siebel Components have been installed. This test must be reviewed to take into account MSCS on the Gateway platform.
This test is to verify that all Siebel Server Services have started. This test is to validate the proper set-up of the Internet Browser on a target workstation running a web client.
All Siebel Components have been installed Reauires to have Browser Health Check activated on the plateform and have a workstation identical to what will be used in production.
Aprox. Duration Status 3h Reviewed
Comment
Not sure that SSL is implemented between Web Servers Web Browsers
Order
Execution Date
1h
Reviewed
1h
Reviewed
1h
Reviewed
Redondant 1h 1h 1h Reviewed Reviewed Redondant Reviewed
3h 3h 1h
TBC TBC Reviewed
Not sure that SSL is implemented between Web Servers and Siebel Servers Not sure that ADSI authentication is implemented
1h
Reviewed
1h
Reviewed Changed Redondant

Changed to CON05
Changed
Changed to CON10
Changed Changed Changed Changed Changed Changed
Changed to LOA03
Changed to CON15 Changed to CON17 Changed to CON17 Changed to CON18 Changed to CON18
2h
Reviewed
1h
Reviewed
Draft
Needs to be clarified
3h
Reviewed
Draft 3h Reviewed
Needs to be clarified
Applicable to load testing scenario
2h 2h
Reviewed Reviewed
2h
Reviewed
3h 3h
Reviewed Reviewed
TBC
Needs to be clarified in terms of target architecture.
2h
Reviewed
TBC 1h 2h 2h 1h 1h 1h 1h Reviewed Reviewed Reviewed Reviewed Reviewed Reviewed Reviewed
Not sure that the Wireless functionnality will be implemented.
2h
Reviewed
1h 1h
Reviewed Reviewed
1h
Reviewed
2h
Reviewed
2h
Reviewed
2h
Reviewed
3h
Reviewed
Oracle Fail Safe Technology only runs under MS Operating Systems ans MSCS clusters. The target database is supposed to run a Unix DB server.
2h
Reviewed
Needs to be clarified in terms of target architecture.
3h
Reviewed
Applicable to load testing scenario.
3h
TBC
Applicable to load testing scenario.
1h
Reviewed
2h
Reviewed
Redondant Redondant 1h 2h 1h 1h Reviewed Reviewed Reviewed Reviewed
Redondant
1h
Reviewed
1h 2h
Reviewed TBC
TBC TBC TBC TBC TBC TBC TBC TBC
Fu nc tio
na
lT es tS
cr ip ts
ed
da pt
ag em en
Se cu ri Fa ty i A l Ov va e ila r u bi si lit ng y A
bi lit y
ci n
ip ti o
ti o
m en ta
al an
oy m en
M an
es cr
ai na
si o
in g
Te st D
M ai nt
oc u
ac h
ep l
SEC01
AV01
SEC02
AV02
Create Order Siebel Server 1 Create Order Siebel Server 2 Create Order Database
LOA01
TBD
DEP01
MAI01
SES01
CAC01
DEP02
MAI02
SES02
CAC02
SEC03 SEC04 SEC05 SEC06 SEC07 SEC08
AV03 AV04 AV05 AV06 AV07 AV08 AV09
DEP03 DEP04 DEP05 DEP06 DEP07 DEP08

DEP09
SES03 SES04 SES05
CAC03 CAC04 CAC05
DEP10.1 DEP11.1 DEP12.1
Totals
12
En d
Lo a
Se s
to
En d
Sh a
re
to
Sm
in g
ac h
En d
DAT01 - Create Service Request Record
to
En d
Sh a
re
to
Sm ar t
Https Http LDAP/ADSI Secured LDAP/ADSI Standard Oracle listener UDP Port for Windows FS TCP Port for Windows FS Gateway Object Manager SCBroker Remote server
Port number 443 80 636 389 1521 137-138 139 2320 2321 40400
Back to Total Page

Test Description This test is to demonstrate that when the Database is unavailable - an error will be displayed when the user attempts to access the database. Pre Conditions Have Database rollback segments properly tuned, and a full backup available in case on DB crash requiring a full restore. Post Conditions Acceptance Criteria Custom Custom Custom
Test Step DEP01.1
Test Step Description Log onto Siebel Application with administrator User ID and Password as defined in the Configuration table. Select the Contacts Screen
Notes
Expected Results Result Actual Siebel Home Page is displayed Contact Screen is displayed showing available records The Account is selected and the detailed record is displayed.
DEP01.2
DEP01.3
Select the account record VIP HOLLAND B.V as displayed in the Accounts columns of the Contact Screen or as the account record as indicated in the Configuration Table.
DEP01.4
Shut down the database server
The database server is shut down the record selected in the previous step is currently displayed
DEP01.5
Select the Contact Tab
Contact Tab is selected and no records are available
DEP01.6
Enter CTRL +Shift+A
Screen views are not displayed and error is displayed to the user Database Unavailable.
DEP01.7
Stop all the platform and restart the servers in the following order: -DB Server and File System -Siebel Servers -F5 Load Balancing -Web Servers -Http Load Balancing
The platform is restarted.
DEP01.8
Wait few minutes for the services to restart properly, then try to reconnect to the application using the same credential than before. Access the same account and check that you find the same information than before.
Siebel Home Page is displayed.
DEP01.9
Account is not corrupted
Custom
Comments Warning this is a very pertubative test. Shutting down the database before any Siebel Server may lead to technical problems such as orphan records and data corruption.
Siebel Ref
Back to Total Page

Test Description Pre Conditions Post Conditions Acceptance Criteria This test is to demonstrate that when the File System FSM Components properly set-up on the Shared Directory is unavailable - documents, file platform, in accordance with the File System attachments and images will not be made available. access rights and network settings (firewall opening and IP routing)
Test Step DEP02.1
Test Step Description Log onto Siebel Application with Siebel Administrator type credentials. Press Ctrl+Shift+A
Notes
Expected Results Siebel Home Page is displayed The Site Map is displayed showing the various views
DEP02.2
DEP02.3
Go to Contacts View and select a record. Select the Send Letter Option form the File Menu in order to generate a letter to this contact. Launch the generation and check that the status is completed before proceeding.
User is directed to the Corresponde nce Menu where a document record is created displaying created date time stamp and Status as In Progress.
DEP02.4
Once the document is generated, try to edit it using the hyperlink of the completed record.
MS Word opens with the new generated document in it, fetched from the Siebel File System.
DEP02.5
On the server where the File System Share is hosted, open a Windows Explorer session. File System should be only accessible by admin accounts and FSM components, not directly by the users. Remove the read rights of the FSM components and apply the changes.
File system is not accessible by FSM components anymore.
DEP02.6
Back on the Siebel Session, Navigate to the Site Map by typing Ctrl +Shft+A and select the Correspondence Tab. Select the document that has just been generated and try to open it again with MS Word. An error message should appear.
The generated document, which is stored on the file system, is not accessible anymore.
DEP02.7
Return to the server where the File System is hosted and rollback the user rights. Back in Siebel, try to edit the same generated document again.
User rights are restored. Document opens properly in MS Word.
DEP02.8
Custom
Custom
Custom
Custom
Comments Warning this is a very pertubative test, especially if Remote servers are active as they may require to access the Fs on a regular basis.
Actual Result
Siebel Ref
Back to Total Page

Test Description Pre Conditions Post Conditions Acceptance Criteria Custom Custom This test is to demonstrate that when All components are available. the File System Manager component is not enabled requests that use the FSM will return an error message
Test Step DEP03.1
Test Step Description Log onto Siebel Application with administrator User ID and Password as defined in the Configuration table. Press Ctrl+Shift+A < enter>
Notes
Expected Results Result Actual Siebel Splash Screen is displayed The Screen view is displayed showing the various views User is directed to the Corresponde nce Menu where a record is created dipslaying created date time stamp and Status as In Progress
DEP03.2
DEP03.3
Select the Send Letter Option form the File Menu
DEP03.4
Click the back button in the browser or the site map button to return to the Screen View
The Screen view is displayed showing the various screen views
DEP03.5
Using Windows explorer disable the File System or Unshare the drive that File system directory is held on the siebel server Navigate to the Site Map Menu Ctrl +Shft+A and select the Correspondence Tab.
File system is disconnected This cannot be selected and the Corresponde nce view is disabled An Error is displayed when the Personal Template Tab is selected.
DEP03.6
DEP03.7
Select the Personal Template Tabs
Custom
Custom
Siebel Ref
Back to Total Page

Test Description Conditions Pre Post Conditions Acceptance Criteria Custom This test is to All demonstrate components that when are available. the File System Manager component is not enabled requests that use the FSM will return an error message Custom Custom Custom
Test Step
Test Step Notes Description Log onto Siebel Application with administrator User ID and Password as defined in the Configuration table.
Expected Results Result Actual
Siebel Ref
DEP04.1
Siebel Splash Screen is displayed
DEP04.2
Press Ctrl+Shift+A < enter>
The Screen view is displayed showing the various views User is directed to the Corresponde nce Menu where a record is created dipslaying created date time stamp and Status as In Progress
DEP04.3
Select the Send Letter Option form the File Menu
DEP04.4
Click the back button in the browser or the site map button to return to the Screen View
The Screen view is displayed showing the various screen views
DEP04.5
Using Windows explorer disable the File System or Unshare the drive that File system directory is held on the siebel server
File system is disconnected
DEP04.6
Navigate to the Site Map Menu Ctrl +Shft+A and select the Corresponde nce Tab.
This cannot be selected and the Corresponde nce view is disabled
DEP04.7
Select the Personal Template Tabs
An Error is displayed when the Personal Template Tab is selected.
Back to Total Page

Test Description Conditions Pre Post Conditions Acceptance Criteria Custom This test is to demonstrate that a Siebel User can log into the siebel application when the Gateway Name Server has been disabled The Siebel Gateway must be properly backed up Custom Custom Custom Custom Warning this is a very pertubative test that can require the complete reinstallation of the platform
Test Step
Test Step Notes Description Using a remote access tool to connect on the Gateway Server, stop the Siebel Gateway Name Service.
Siebel Ref
DEP05.6
Gateway Name Server is disabled
DEP05.1
Before starting this test, a backup of the siebns.dat file must be made. Connect to the Siebel Gateway Server and make a backup copy of this file.
The siebns.dat file is backed-up
DEP05.2
Log onto Siebel eService application with administrator user ID and Password
Siebel Home Page is displayed
DEP05.3
Press Ctrl+Shift+A
The Site Map is displayed showing the various views
DEP05.4
Click on Server Administratio n Configuration
The Server Administratio n Configuration menu view is displayed as Administratio n - Server Configuration Enterprise Explorer Enterprises Component Definitions Component Groups System Alerts Servers Components Events Parameters Parameters
DEP05.5
Log out of the siebel application File >Logout or Ctrl+Shift+x
User is logged out of the siebel application and the Siebel Front Page Splash Screen is displayed
DEP05.6
Using a remote access tool to connect on the Gateway Server, stop the Siebel Gateway Name Service.
Gateway Name Server is disabled
DEP05.7
Log into the Siebel Application by entering User Id and User Password as defined in the Configuration Table Press <enter>
User is able to log into the Siebel application , an error message is not displayed to the user on the screen
DEP05.8
Navigate to the Site Map menu or press CTRL+Shift+ A Select Administratio n Server Configuration >Component Definition >
Site Map is displayed
DEP05.9
The component definition screen is displayed
DEP05.10
Attempt to add a new component definition by selecting the New Button
The 'New' button is disabled and the user cannot add a new component
DEP05.11
Attempt to start a component that has been disabled by selecting the start button on the component definition screen
The 'Start' button is disabled and the user cannot start a component
DEP05.12
Log out of the siebel application by selecting - File >Logout from the menu or press Ctrl+Shift+x
User is logged out of the siebel application and the Siebel Front Page Splash Screen is displayed
DEP05.13
Restart the Siebel Gateway Service now and redo the same test again.
New component is added. Existing component is started.
DEP05.14
Stop the Gateway service and roll back the backed up version of the siebns.dat file. Restart the Siebel Gateway Service; Check that the modifications made above with components do not appear anymore.
The platform configuration is back to its state prior to the test.
Back to Total Page

Test Description Conditions Pre Post Conditions Acceptance Criteria Custom 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 Siebel Application Existing Services are up and running Custom Custom Custom
Test Step
Test Step Notes Description Log onto Siebel Application with administrator User ID and Password.
Siebel Ref
DEP06.1
The Siebel Home Page is displayed
DEP06.2
Press Ctrl+Shift+A to access the Site Map.
The Site Map is displayed
DEP06.3
Click on Server Administratio n Configuration .
The Server Administratio n Configuration menu view is displayed as Administratio n - Server Configuration Enterprise Explorer Enterprises Component Definitions Component Groups System Alerts Servers Components Events Parameters Parameters
DEP06.4
Log out of the siebel application File >Logout or Ctrl+Shift+x.
User is logged out of the siebel application and the Siebel login Page is displayed again.
DEP06.5
Using a remote access tool, access all servers hosting an Object Manager, and shut down the Siebel Services on each one of these servers.
Siebel Services are shutdown on each server hosting an OM.
DEP06.6
Try to log into the Siebel Application by entering User Id and Password as defined in the Configuration Table.
User logs into the Siebel application , an HTTP error message is displayed 'Page Cannot be Found'
DEP06.7
Using the same remote access tools, restart the Siebel services on the servers hosting OM.
All Siebel services of the platform are back online.
DEP06.8
Once this is done, do a restart of the load balancing service, and also of the IIS services on the web servers. Try to connect to the application again.
The login page is accessible again.
Back to Total Page

Test Description Pre Conditions Post Conditions Acceptance Criteria Custom Custom This test is to demonstrate that Existing Service are up when the Web Servers are and running unavailable - an error will be displayed to the user and the Siebel Application will be unavailable. Test Step DEP07.1 Test Step Description Notes Log onto Siebel Application with administrator User ID and Password as defined in the Configuration table. Press Ctrl+Shift+A Expected Results Siebel Home Page is displayed Actual Result
DEP07.2
The Site Map is displayed showing the available screen views. The Administration - Server Configuration details are displayed. The siebel server component screen is displayed. User is logged out of the application.
DEP07.3
Click on Administration - Server Configuration Click on Components Now exit from the Siebel Application - by pressing CTRL+Shift+x or select from the menu title bar File > Logout
DEP07.4 DEP07.5
DEP07.6
Log on to the Web Servers using re+ote qccess tool. Stop the IIS services on the web servers Try to log onto Siebel Application with administrator User ID and Password as defined in the Configuration table. Restart the web servers and redo the test after waiting a minute or two for the services to process requests again.
User is logged on the web server.
DEP07.7
The web server(s) are shut down. No more trqffic is treated. No page is displayed. After a certain time out period, an error message is displayed by the web browser stating that the server is unavailable.
DEP07.8
DEP07.9
The platform is back online.
Custom
Custom
Siebel Ref
Back to Total Page

Test Description This test is to verify that the web client supports HTTP 1.1 protocol Test Step DEP08.1 Pre Conditions Internet explorer is available and user can access IE settings. Test Step Description Verify that the WebClient supports HTTP 1.1 protocol by clicking on Tools > Internet Options> Advanced . Scroll down and enable the check box Use HTTP 1.1 Notes Expected Results The Web Browser support for HTTP 1.1 protocol is enabled. Actual Result Post Conditions Acceptance Criteria Custom
Custom
Custom
Custom
Siebel Ref
Back to Total Page

Test Description This test is to verify that Microsoft IIS virtual diectories have been created on the Siebel Web Server Pre Conditions You must have installed all key Siebel Enterprise Server components, including the Siebel Gateway Name Server, at least one Siebel Server, and the Database Configuration Utilities. and configured the Siebel Gateway Name Server, created and configured the Siebel Enterprise, created the SWSE logical profile, and configured the Siebel Server. Post Conditions Acceptance Criteria
Test Step DEP09.1
Test Step Description On the Microsoft IIS machine, navigate to Control Panel > Administrative Tools > Internet Information Service Double-click machine_name (local computer) in the left panel. Double Click Websites in the right panel Double Click default Websites in the right panel
Notes
Expected Results IIS Screen is displayed
DEP09.2 DEP09.3 DEP09.4
All the virtual directories created on this machine will be listed in the right panel
Custom
Custom
Custom
Custom
Actual Result
Siebel Ref
Back to Total Page

Test Description This test is to verify that all Siebel Gateway Name Services have started. Test Step DEP10.1 Pre Conditions All Siebel Components have been installed. This test must be reviewed to take into account MSCS on the Gateway platform. Test Step Description On the servers hosting the Gateway service navigate to the Control Panel > Administrative Tools and select Services Notes Expected Results Result Actual The service screen is in view and displays the available services. Post Conditions Acceptance Criteria Custom Custom Custom
DEP10.2
Scroll down the list and identify the Siebel Gateway Name Server Service
Siebel Gateway Name Server Service screen is displayed
DEP10.3
Double Click on the Siebel Gateway Name Service
Service popup window is displayed. Service Status displays Status Started using specific domain account, and startup mode automatic.
DEP10.4
Check the Service Status: startup mode should be set to automatic and the service account used to start it should be a domain specific account.
DEP10.5
Check the Service Status to see if it is started.
Siebel Gateway Service is started.
Custom
Siebel Ref
Back to Total Page

Test Description This test is to verify that all Siebel Server Services have started. Test Step DEP11.1 Pre Conditions All Siebel Components have been installed Test Step Description For each of the Siebel Servers of the platform, Navigate to the Control Panel > Administrative Tools and select Services Notes Expected Results Result Actual The service screen is in view and displays the available services. Post Conditions Acceptance Criteria Custom Custom
DEP11.2
Scroll down the list and identify the Siebel Server Service.
Siebel Server Service screen is displayed. Service popup window is displayed. Service Status displays Status Started using specific domain account, and startup mode automatic.
DEP11.3
Double Click on the Siebel service to edit it.
DEP11.4
Check the Service Status. It should be already running, using a specific domain service account, and its startup mode should be set to Automatic.
DEP11.5
Check that the service is started.
Siebel Service is started.
Custom
Custom
Siebel Ref
Back to Total Page

Test Description This test is to validate the proper set-up of the Internet Browser on a target workstation running a web client. Pre Conditions Reauires to have Browser Health Check activated on the plateform and have a workstation identical to what will be used in production. Post Conditions Acceptance Criteria Custom Custom
Test Step
Test Step Description
Notes
Custom
Custom
Siebel Ref
Back to Total Page

Test Description Pre Conditions Post Conditions Acceptance Custom Criteria Custom
Steps CON01.1 CON01.2
Test Desc
Notes
Expected Results ResultPass / Fail Actual
Custom
Custom
Comments
Data Input
Siebel Ref
Siebel Reference
Back to Total Page

Test Description Pre Conditions Post Conditions Acceptance Criteria Custom Custom
This test is to verify that the http Require a typical target local Deamon of a Mobile Client mobile client workstation. is only accessible localy. The server must be set-up in order to allow the creation and the management of remote users.
Steps CON02.1
Test Desc From a workstation, connected to the test platform, using Siebel Administration credentials, define a user as a remote in Remote Users Administration Screen.
Notes
Expected Results A new remote user is created.
Actual ResultPass / Fail
CON02.2
Launch a Generate New DB task in order to create a new DB Template
New DB template is generated.
CON02.3
Now launch a DB Extract task for the user that will be used for this test. Logout from the application typing Ctrl+Shift+X Now using a workstation similar to the one used in production to run Mobile clients, connect to the application, using the "Local" profile.
New user DB is created.
CON02.4
Login screen appears.
CON02.5
The user specific DB prepared during the previous steps in downloaded on the workstation. When finished creating the local DB, the user will automatically get connected to it.
CON02.6
Running ipconfig in prompt mode, take note of all network details for this user workstation.
IP configuration is written down.
CON02.7
From another workstation, launch an IE windows. Type in a Siebel URL starting with the IP address of the user workstation. From the user workstation, run a network port audit to see if any of the ports used by Siebel local deamon is opened. This can be done either by running a specific utility, or by using web sites dedicated to this task.
An error message appears, the computer is unreachable.
CON02.8
All Siebel reserved ports are closed to incoming traffic.
Custom
Custom
Comments
Data Input
Siebel Ref
Siebel Reference
Warning, in case of previous DB extraction, a new DB generation will lead all existing remote users to redownload their local DB.
Back to Total Page

Test Pre Description Conditions This test is to verify that the Siebel Wireless Gateway is accessible from a handheld device. Post Conditions Acceptance Custom Criteria Custom Custom Custom Comments
Steps
Test Desc
Notes
Expected Results ResultPass / Fail Actual
Data Input
Siebel Ref
Siebel Reference
Back to Total Page

Test Description Pre Conditions Post Conditions Acceptance Custom Criteria Custom Custom
This test is to verify that Requires that the various the Siebel Gateway is network gateways are accessible from external properly set-up network.
Steps CON04.1
Test Desc On the test environment, take note of the detailed IP configuration of the Gateway server. If this is a MCS cluster, take all detailed IP configuration of both servers AND of the cluster. From a remote location, similar to where the Mobiles users will connect from (public network?), try to telnet the Gateway accessing its default port. If it is a cluster, only the VIP needs to be accessible.
Notes
Expected Results ResultPass / Fail Actual IP configuration s are written down.
Data Input
Siebel Ref
CON04.2
The Telenet session asks for a login. The Gateway is accessible.
Custom
Comments
Siebel Reference
Back to Total Page

Test Description Pre Conditions Post Conditions Acceptance Custom Criteria Custom
This is to verify that the All Siebel Server Components are Gateway Server is accessible installed on the platform from the various servers of the enterprise.
Steps CON05.1
Test Desc Connect to each Siebel server of the Enterprise and try to access the siebel gateway service by typing in a DOS command window - telnet ip address AND specific port number where ip address and port are defined in the configuration table. On server reponse at prompt, Enter User ID and Password
Notes
Expected Results ResultPass / Fail Actual The Gateway answers to the telent request.
CON05.2
User is now connected to the Siebel Gateway Service
CON05.3
Connect to the Siebel Gateway Server locally or with a re+ote access tool.
User is now connected to the Siebel Gateway Service
CON05.4
In the Control Panel, go to the Services list. Look for the Siebel Gateway service in the list. It should be running, in automatic launch mode and launched by a specific Domain account.
A list of services is displayed. The Siebel Gateway service is running in automatic mode and launched by a specific Domain user.
CON05.5
CON05.6
Navigate to the \gtwysrvr\ADMIN on the Siebel Gateway server.
The prompt changes to \gtwysrvr\AD MIN.
CON05.7
Check to see if the siebns.dat file exists.
The siebns.dat file is present.
Custom
Custom
Comments
Data Input
Siebel Ref
Siebel Reference
Only possible localy on the server or with Administratio n pack for Windows from a workstation or with special tools to see processes remotely.
Need to make a backup task of the siebns.dat
Back to Total Page

Test Description Pre Conditions Post Conditions Acceptance Criteria Custom Custom This test is used to verify that round Test platform needs to be robbing load balancing is dependent up and running. of the application aliases definition in the eapps.cfg Steps CON06.1 Test Desc Using a remote access tool, connect to the load balancer server management screen in order to see routed sessions in real time. From a workstation used for testing, connect to the application using an alias that will be used in production and that relies on load balancing. Any credential may be used. Notes Expected Results The load balancer displays a list of routed sessions. Actual ResultPass / Fail
CON06.2
CON06.3
Validate that this new session is listed in the load balancer management screen. Edit the eapps.cfg file on both the web servers and create a specific alias which points directly to one of the OM servers of the platform. Apply the changes to the web servers by restarting the IIS services.
The new session is listed as being routed by the load balancer. A new specific alias was created allowing a direct connection to one of the OM servers.
CON06.4
CON06.5
Connect to the application using the new alias. Go back to the management screen of the load balancer, no new session should appear there. Disconnect from the application Typing Ctrl+Shift+X Disable the alias created in the eapps.cfg on all webservers and apply changes by restarting the IIS services.
The Siebel Home Page is displayed. No new session is routed by the load balancer using this specific alias.
CON06.6
CON06.7
Siebel login screen appears. Platform is back to load balancing strategy.
CON06.8
Custom
Custom
Comments
Data Input
Siebel Ref
Siebel Reference
Back to Total Page

Test Description Pre Conditions Post Conditions Acceptance Criteria This test is used to verify that The test platform must be setthe F5 load balancer can up and running. access the Siebel Servers and be accessed by the Web Servers. Steps CON07.1 Test Desc Using a remote access tool, connect to the server hosting the load balancer. From this server, try to telnet all siebel servers hosting Object Managers components on their default port. Notes Expected Results Connected to the load balancer. Each server acknowledge and offers a login prompt.
CON07.2
CON07.3
Disconnect from the load balancer server. On each of the server hosting an Object Manager component, connect using a remote access tool. From each one of these servers, try to telnet the server hosting the load balancer on its default port.
Disconnected from the load balancer server. Connected on each server hosting an OM component. The LB server acknowledge and offers a login prompt.
CON07.4
CON07.5
Custom
Custom
Custom
Custom
Comments
Actual Result
Pass / Fail
Data Input
Siebel Ref iebel Reference S
Back to Total Page

Test Description Pre Conditions Post Conditions Acceptance Criteria This test is used to verify that the Test platform needs to be up F5 load balancer is properly and running. installed. Steps CON08.1 Test Desc Access the Load Balancer Admin Page using Internet Eplorer Log into the admin page of the load balancer. Go to the list of nodes and check that all Siebel Servers running OMs are listed there and have a green status. Notes Expected Results A login page appears.
CON08.2 CON08.3
The Load Balancer Admin Application is displayed, All Siebel Servers running OMs are listed and ready to receive traffic.
Custom
Custom
Custom
Custom
Comments
Actual ResultPass / Fail
Data Input
Siebel Ref
Siebel Reference
Back to Total Page

Test Description Pre Conditions Post Conditions Acceptance Criteria Custom
This test is to verify the proper execution of various Server Manager Commands. Steps CON09.1
Test platform needs to be up and running. Test Desc From a test workstation with a dedicated client installed, or from a server of the platform through remote access, launch a DOS prompt windows. Go to siebel_server_root\bin and launch the server manager by typing a command similar to srvrmgr /g gateway1 /e enterprise1 /s server1 /u sadmin /p sadmin Notes Expected Results DOS prompt windows appears. Actual Result
CON09.2
The prompt changes to display the current connection status of the server manager utility (srvrmgr:server_name>)
CON09.3
List the servers by typing the following command: list servers List the active components of the platform by typing the following command: list component Disconnect from the server manager by typing: exit Then close the Dos prompt windows.
The list of the servers of the enterprise is displayed. The list of the components of the platform is displayed. Dos prompt windows is closed.
CON09.4
CON09.5
Custom
Custom
Custom
Comments
Pass / Fail
Data Input
Siebel Ref
Siebel Reference
Back to Total Page

Test Description This test is to verify that the server administration view can be accessed from the web client Pre Conditions Siebel Gateway Server is up and services are running. Warning! There is a major technical difference in the way certain admin views are accessed depending if it is from a dedicated or thin web client. In the first case, a direct connection (no FW ie) is required between the workstation and the Siebel Gateway. Post Conditions Acceptance Criteria
Test Step CON10.1
Test Step Description Log onto Siebel eService with Siebel Administrator responsability (SADMIN type) Press Ctrl+Shift+A to access the site map Go to the View Administration / Configuration
Notes
Expected Results Siebel Splash Screen is displayed
CON10.2 CON10.3
The Site Map is displayed showing the various views The Server Administration Configuration menu view is displayed as Administration - Server Configuration Enterprise Explorer Enterprises Component Definitions Component Groups System Alerts Servers Components Events Parameters Parameters
CON10.4
Click in the history back button (Siebel bouton not the IE bouton) in order to come back to the Server Admin default View
The Screen view is displayed showing the various views
CON10.5
Go to the View Administration / Server Management
Administration - Server Management :Administration - Server Management Components State Values Statistics Tasks Enterprises Servers Log Sessions Statistics Tasks Sessions Log Parameters State Values Statistics Tasks Log Parameters State Values Statistics
CON10.6
Check to see if the siebns.dat file exists
The siebns.dat file is present
Custom
Custom
Custom
Custom
Comments
Actual Result
Siebel Ref
Point to verify : the specified file should be listed in a list applet
Back to Total Page

Test Description Pre Conditions Post Conditions Acceptance Criteria This test is used to demonstrate Requires a sample asynchronous batch the operability of a command process to test with expected results and line batch execution. means of validation.
Test Step CON11.1
Test Step Description From a test workstation with a dedicated client installed, or from a server of the platform through remote access, launch a DOS prompt windows.
Notes
Expected Results Prompt from remote server appears.
CON11.2
Depending of the batch treatment to be executed, check the status of the data to be modified by connecting to the application. Logout of the application by typing CtrlShift-X Copy the required files to the server that will be running the batch treatment (ie. Where the Workflow Components Group is hosted). Go to siebel_server_root\bin and launch the server manager by typing a command similar to srvrmgr /g gateway1 /e enterprise1 /s server1 /u sadmin /p sadmin Type in the command to launch the asynchronous batch process to be tested: start task for component component_alias_name server siebel_server_name with parameter_alias_name1=value1, parameter_alias_name2=value2 Depending of the batch treatment to be executed, check the status of the data modified by connecting to the application.
Siebel Home Page appears.
CON11.3 CON11.4
Siebel Login Page appears. Files are copied to the server.
CON11.5
The prompt changes to display the current connection status of the server manager utility (srvrmgr:server_name>).
CON11.6
Prompt is displayed at the end of the treatment and a log file is generated.
CON11.7
Custom
Custom
Custom
Actual Result
Custom
Comments
Siebel Ref
Back to Total Page

Test Description Conditions Pre This test is to Test platform needs to be up and verify that running. the Siebel Gateway server is properly setup and running. Post Conditions Acceptance Criteria Custom Custom
Test Step CON12.1
Test Step Description Using a remote access tool, connect to each of the servers of the platform On each of theses server, type a telnet:port to check if the Gateway service is properly listening to on the specified address:port
Notes
Expected Results Connected to each server of the platform
Actual Result
CON12.2
The Gateway is communicating properly with each of the servers of the platform.
Custom
Custom
Comments
Siebel Ref
Back to Total Page

Test Description This test is to verify the succesful set-up of all connection brokers. Test Step CON13.1 CON13.2 Pre Conditions Requires a precise list of all managed components and their localisation (including port numbers of components) Test Step Description Connect by remote access to one of the Siebel servers of the platform. On this server launch a DOS prompt windows. Inside this DOS prompt windows, try to telnet each of the servers of the platform. Type: telnet IP:port in order to check if the connection broker service is listening on the port numbers supplied to the testing team. Notes Expected Results Connected to one of the servers DOS prompt windows is displayed. The server answers by offering a login prompt. Actual Result Post Conditions Acceptance Criteria Custom Custom
CON13.3
Custom
Custom
Comments
Siebel Ref
Back to Total Page

Test Description Pre Conditions Post Conditions Acceptance Criteria Custom Custom This test is to verify that Requires a precise list of the server manager is all managed components properly monitoring and and their localisation. manage the various servers, components and tasks of the plateform.
Test Step CON14.1
Test Step Description Connect to the application using a Siebel Administrator credentials. Go to the Site Map by typing Ctrl+Shift+A Go to the Server Administration Screen List the different servers, component groups, components and tasks, and check their proper parameters against the list that has been transmitted to the testing team.
Notes
Expected Results Siebel Home Page Appears.
Actual Result
CON14.2 CON14.3 CON14.4
The Siebel Site Map is displayed. Server Administration Screen appears. The current tets platform configuration is similar to what has been specified.
Custom
Custom
Comments
Siebel Ref
Back to Total Page

Test Description Pre Conditions Post Conditions Acceptance Criteria This test is to verify Oracle ODBC Data Proper ODBC Drivers must have been installed on Source Connectivity from all Siebel the Siebel servers. Detailed parameters for ODBC Servers. connection may be required (NLS_LANG & SORT_ORDER). Test Step CON15.1 Test Step Description Connect on all Siebel Servers of the plateform using a re+ote access tool. Navigate to the Control Panel / Administrative Tools / Data Sources ODBC On the ODBC datasource Administrator Screen Dialogue box , select the system DSN tab Select the datasource used to connect to the Test Environment DB and check the values specified. Notes Expected Results The ODBC Data Sources Panel is displayed List of all DSN is displayed The selected Data source is displayed and the values are correct. A popup window confirm the proper connection to the DB
CON15.2
CON15.3
CON15.4
Try to establish an ODBC connection to the DB Click the Test Connect Button, using an active DB account.
CON15.5
Launch the registry editor Regedit. In the windows registry locate the following keys: local_machine/software/odbc /odbc.ini/name_dsn Verify that the following registry keys are set as shown - Packet Size=0 EnableScrollabeCursors=0 columnAsChar=1 ColumnSizeAsCharacter=1
Options for the ODBC DSN are displayed Parameters are correct
CON15.6
Custom
Custom
Custom
Custom
Comments
Actual Result
Siebel Ref
Comments
May require to specify a special NLS_LANG & SORT_ORDER parameters here. Check with Dev Team.
Back to Total Page

Test Description Conditions Pre Post Conditions Acceptance Criteria Custom This test is to verify the accessibility of the File System by all the File System Manager Component. Requires a precise list of all managed components and their localisation. Custom Custom Custom Comments
Test Step
Test Step Notes Description On each of the server hosting the FSM component, connect using a remote access tool.
Siebel Ref
CON16.1
Connected to each of the servers hosting FSM component.
CON16.2
Open a new windows explorer session.
New windows explorer session is open. The content of the File System shared disk space is displayed. A new directory is created.
CON16.3
Type in the network address of the Siebel File System.
CON16.4
Try to create a new directory is this shared disk space.
CON16.5
Delete this directory.
Directory is deleted
Back to Total Page

Test Description Conditions Pre Post Conditions Acceptance Criteria Custom This test is to verify that only the required application web aliases (virtual directories in IIS) are activated on the platform and that the parameters are properly tuned between IIS and SWSE. Requires that the different IIS servers and related eapps.cfg files have been properly tuned on the plateform. Custom Custom Custom Comments
Test Step
Test Step Notes Description On each of the Web Servers, go to the IIS control panel. List all virtual directories created in IIS.
Siebel Ref
CON17.1
The list of virtual servers appears in IIS.
CON17.2
Check that only required virtual directories have been activated.
Only required virtual directories are activated.
CON17.3
For each of the virtual directory, check its individual parameter, especialy if it is a custom created one. Compare it to a standard Siebel generated one.
Each virtual directory set of parameter is checked again standard Siebel created one.
CON17.4
Now again for each of the web servers, edit the eapps.cfg file and check that the aliases for Siebel applications are properly in tuned and in phase (port numbers, type of IIS thread, SSL activation, target dll...) with the virtual directories from IIS.
Eapps.cfg file is properly setup in phase with virtual directories in IIS.
Back to Total Page

Test Description This test is to verify that the Fail Over mechanism Oracle Fail Safe is properly running on the DB server. Test Step FO01.1 FO01.2 FO01.3 Pre Conditions Requires 2 instances of DB server with Fail Safe service running. Test Step Description Notes Post Conditions
Acceptance Criteria
Custom
Custom
Custom
Custom
Comments
Expected Results
Actual Result
Siebel Ref
Back to Total Page

Test Description This test is to verify that the MSCS services are properly installed and running. Pre Conditions Requires the MSCS are installed and are running on the specified servers. Post Conditions Acceptance Criteria
Test Step FO02.1 FO02.2
Test Step Description Connect to the Siebel application using standard user credentials. Using remote access tool, connect to the MSCS primary server, and display the cluster management tool. Still connected to the Siebel application, navigate randomly through the screens. On the MSCS admin panel, swithc the primary node between the servers. With the session still opened, continue the navigation inside the Siebel application. On the MSCS cluster, check the generated log file, indicating the switch of primary node, it will have to be monitored in Production. Disconnect from the Siebel application by typing Ctrl+Shift+X
Notes
Expected Results The Siebel Home page is displayed. The list of clustered services appears. The application is responding normally. The primary node has changed. The cluster switch does not affect the application behaviour. The log file on the MSCS primary node indicates a switch of the primary node. The Siebel login screen is displayed.
FO02.3
FO02.4 FO02.5
FO02.6
FO02.7
Custom
Custom
Custom
Custom
Comments
Actual Result
Siebel Ref
Back to Total Page

Test Description Pre Conditions Post Conditions This test is to verify the redundancy of Have the web servers running behind a NLB the web servers. This test is to verify equipment or similar device, routing clients sessions the behaviour of an existing session in either to one or the other IIS. case of a web server crash.
Test Step FO03.1
Test Step Description Connect to the Siebel application using any credential, through a web client session (IE). By connecting to the web servers by using a remote access tool and by editing the SWSE log files, identify which web server is actually being used by the opened session.
Notes
FO03.2
FO03.3
While still connected to the Siebel application, on the web server dealing with the session, go to Control Panel / Advanced / Services. Stop the IIS services. Wait a few seconds, then go back to your open Siebel session in IE windows, and try to navigate to another screen. Analyse the log files generated on the other web server to see how was handled the switch.
FO03.4 FO03.5
FO03.6
Acceptance Criteria
Custom
Custom
Custom
Custom
Expected Results The Siebel Home Page is displayed.
Actual Result
Siebel Ref
The web server dealing with the new session is identified.
List of Services installed on the web server.
The IIS services are stopped. The navigation is still possible.
Log file starts after the switch between web servers was made.
Comments
Back to Total Page

Test Description Pre Conditions Post Conditions Acceptance Criteria This test is to verify that the Siebel Servers are properly Need to have a properly set-up set-up in order to allow automatic resilient processing in environement with a stable application and case of anomaly on one of the servers of the enterprise. technical components as in Production. This test is also to verify the behaviour of an existing session in case of an OM crash, by getting Asserts and normal logs. Test Step FO04.1 Test Step Description Using Internet Explorer, connect to the Siebel application using any credential. Using a remote acces tool, connect to the web servers. Edit the SWSE log files and identify which web server and OM is used to process the current session. Notes Expected Results The Siebel application appears. The connection path is identified by editing the SWSE log file.
FO04.2
FO04.3
With the session still open in Internet Explorer, access the active Object Manager server using a remote access tool. Edit the OM log file in order to confirm the Process and Task Ids. Using remote access tool or the dedicated administration web page, logon to the load balancing application and locate the routed session.
The server running the Object Manager is accessed.
FO04.4
The current session is displayed in the load balancer administration page. Random navigation is possible with no error messages. The Siebel OM process is killed.
FO04.5
Within the Internet Browser, try to navigate randomly in the application.
FO04.6
Back on the OM server, launch the task manager, locate the siebel process and kill it while the session is still open in the Internet Explorer session. Go back to the browser window after a few seconds and try to proceed with some random navigation. On the web servers, by analysing the log files, locate the new OM server used by the ongoing session. On the administration page of the load balancer, locate the routing information of the killed OM. Also check out the new route to the new OM created after the first one was killed. See what has happened and analyse the log files.
FO04.7
The navigation still works without service interruption. A new OM is used to process the ongoing session. The load manager should exclude the killed OM from its routing information.
FO04.8
FO04.9
FO04.10
On the first server where the OM was killed, restart the Siebel Services from the control panel. Make sure it restarts properly by looking at the log files.
The first OM is restarted properly.
FO04.11
Using another Internet Explorer windows, connect again to the Siebel application, if required several times in order for the session to be handled by this first OM. Use SWSE log files to check the taqrget OM used by the new session.
A new session is opened on the first OM.
FO04.12
Check in the Administration page of the load balancer that this OM has properly reintegrated the load balancing strategy.
The OM is back in the paltform and is used by the load balancer to route new sessions.
Custom
Custom
Custom
Custom
Comments
Actual Result
Siebel Ref
Expected behaviour of this component is still unknowned.
Back to Total Page

Test Description This test is to verify that at the start of the user session an Initial Request is created and maintained whilst the user performs the business process of Stock Validation and Error Correction script. Pre Conditions 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 complete the test. A HTTP monitoring tool must be installed on the test workstation, and log level and log events must be changed at the enterprise level in order to track navigation inside the OM processes log files. Test Step Description Connect to web servers and to the servers of the platfrom (using GUI or server manager) and adapt log levels and log events to what is required for the following test. Log into Siebel Application entering User credentials supplied in the configuration table. Notes Post Conditions
Test Step SES01.1
SES01.2
SES01.3
Using a HTTP monitoring tool, check that the HTTP message generated 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 the Object Manager Session Information -ObjMgrSessionInfo. Only one of the web servers deal with the user session.
SES01.4
SES01.5
Switch back to the Siebel Application and continue with step 2 of the script 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 field to 'External'. Set the value for the Source Availability field to Allocated' Set the source status field to 'Good' Set the Destination Location to 'External Location' Set the Destination Availability to Allocated Set the Destination Status field to Good Set the Cause Type field to Wrong Quantity Set the Commit Field Value to True Need to find out the correct step after this , as the step in the CAP GEMINI script appears to be incorrect. Logout of the application
SES01.6 SES01.7 SES01.8 SES01.9 SES01.10 SES01.11 SES01.12 SES01.13 SES01.14 SES01.15 SES01.16 SES01.17 SES01.18 SES01.19 SES01.20
SES01.21
Navigate to the SWSE log file and check that each of the actions performed above have been written to the log file.
SES01.22
Go to the OM server executing the session, analyse the OM log file specific to the user session. Check that the server log file contains the session id created and identified in step 1 and that the session has been maintained throughout the use case. Lower log levels on the SWSE and Entreprise
SES01.23
Acceptance Criteria
Custom
Custom Custom
Custom
Expected Results Log levels are modified on the SWSE and on the Entreprise.
Actual Result
Siebel Ref
User logs onto the siebel application and the front page of the siebel application should be displayed
The new request will contain the HTTP header consisting of the Siebel Enterprise server name and component name
The Object Manager Session Information should display the current user session , Task ID ,PID , Time Stamp and Siebel Server Name
The Inventory Transactions list applet view should be displayed with the fields displayed populated. An entry of type ObjMgrBusCompLog - event type alias should be written to the log file. A new record will be created and the following fields will not be populated The value of the Type Field is set to 'Adjustment' The value of the Product Field is set to 'Product' as identified in the configuration table. 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.
SWSE log file contains information about the user navigation.
The log file for the OM process contains detailed navigation information.
Log levels are back to normal.
Comments What we are testing here is the fact that the overall Busines Process is made under the same Task ID (TID) on one Object Manager Processes Instance (Server # + PID) for all the duration of the Business process. If connection pooling is implemented between the OM 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 the SISNAPI specific header from HTTP message between the client and the 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 an arbitrary numerical value generated by Siebel at installation time and referenced in the siebns.dat; So we need a list of all these server numbers by using a Server Manager command line. We still need the SWSE log to trace back to the correct OM server PID and log file.
Need to validate the ObjMgrBusCompLog; Usually this session log related to a Component is on the server executing the PID.
Logs for this type listing operations are located on the server running the 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" all operations, but it is possible in case of doubt to compare this set of steps with the same type of log file recorded beforehand on a Dedicated Web Client in Connected Mode.
Back to Total Page

Test Description Conditions Pre Post Conditions Acceptance Criteria Custom This test is to verify that at the start of the user session an Initial Request is created and maintained whilst the user performs one of the Business Process Scripts. Object Manager Logging level set to 4 Custom Custom Custom Comments The term "session" may be more apropriate than "request". Setting log level is fine but only tells the "richeness" of the logs generated, not its content; Some "Event logging" options also need to be activated at the same time.
Test Step
Test Step Notes Description Set the Session Monitor=Tru e in the SWE section of the eapps.cfg file
Siebel Ref
SES02.1
Session Monitor=Tru e in the SWE section of the eapps.cfg file
SES02.2
Reboot the Siebel Application Servers
Application Server Rebooted
Need to confirm the need to reboot the Siebel Servers? May need a reboot of the Web Server as well.
SES02.3
Log into Siebel Application entering user id and pass word as supplied in the configuration table.
User logs onto the siebel application and the Home page of the Siebel application should be displayed
May require specific a login associated to a user with defined position / responsabiliti es in order to do the Business process entirely.
SES02.4
Wait a defined moment of time (2 minutes for instance) and launch another browser window and log into Siebel Application again entering the same user id and pass word as above.
User logs onto the siebel application and the front page of the siebel application should be displayed , there are now two instances of the siebel application home page running.
The delay before launching the second session will be useful to differentiate the two sessions easily by looking at the total connection time.
SES02.5
Open another window and connect using a Siebel Administrator Responsabili ty. Go to the server adinistration pages, get the session ID and check their individual status; Alternatively, a server manager command lines can be used from one of the servers or from a workstation with a dedicated web client installed.
Session ID's from the Server Manager GUI interface are displayed as -
SES02.6
Process any of the business high priority scripts for example Create Order , Create Service Requests
SES02.7
Navigate to the SWSE stats page by entering the following url in a new session of the web browser http://host/ap plication/_sta ts.swe? Verbose=Hig h&Reset=Tru e
The SWE statisical page displays the System Stats, Applications, Current Sessions - 2 users , Locks, and Current Operations Processing statistical categories and then resets all noncounter and current operational statistics
SES02.8
Compare the sessions ids and statuses ids from the Server Manager GUI interface and that displayed from the SWE stats page,
Session ID 's should be identical.
Session ID are never identical.
SES02.9
Close the SWSE stats page Log out of the two instances of the Siebel application File > Logout , File > Logout.
SWSE stats page is closed. User is logged out of the two instances of the Siebel Application.
SES02.10
SES02.11
Navigate to the SWSE stats page by entering the following url in a new session of the web browser http://host/ap plication/_sta ts.swe? Verbose=Hig h&Reset=Tru e
The SWE statisical page is displays the System Stats, Applications, and the previous session entries are removed.
Back to Total Page

Test Description Conditions Pre Post Conditions Acceptance Criteria Custom This test is to analyse the network data consumption during a typical business process for one user. Platform up and running. A network monitoring and analysis tool must be installed on a test workstation in order to mesure the bandwidth. A complete business case must be defined, along with adequate credentials and preloaded user data. Custom Custom Custom Comments
Test Step
Test Step Notes Description On a specific monitoring workstation, install the network monitoring tool and set it up to measure traffic between the WS IP address and the Server IP address;
Siebel Ref
SES03.1
Monitoring service up and running reqdy to log bandwidth;
SES03.2
Take note of the IP addresses from the different locations you wish to test; Om servers, web servers, load balancers, workstation... Input this values into the monitoring tool in order to mesure bandwidth.
The monitoring tool is set-up in order to measure bandwidth.
SES03.3
Make sure that the log file of the monitoring application is empty.
The monitoring system for the bandwidth is ready to record pointto-point traffic.
The first time a user connects to the Siebel application, a large plugin (called Siebel framwork) is downloaded into IE. In order to measure this extra bandwidth consumption, it is important to remove it from the IE plugins list.
Siebel framework plugin is removed from IE plugins.
SES03.4
Start to record the traffic.
The monitoring tool starts to record bandwidth. The business script data bandwidth has been recorded.
SES03.5
On the monitoring workstation, log into the Siebel application using user credentials, and run a complete critical business process. Finish the script by properly closing the IE session.
SES03.6
Use the monitoring tool to get a consolidated value for the bandwidth used during the business script,
Bandwidth during this business script is analysed.
Back to Total Page

Test Description Conditions Pre Post Conditions Acceptance Criteria Custom This test is to Platform up verify the and running. timeout setting of the plateform. Custom Custom Custom Comments
Test Step
Test Step Notes Description On the Web Servers of the platform, edit the time out setting in the eapps.cfg file. It must be identical on all web servers. EAI specific connection aliases may have shorter time out values.
Siebel Ref
SES04.1
Time Out parameter is identical between web servers.
SES04.2
Log into the application using a Siebel Administrator account. Check the SISNAPI session time out values for the Object Managers. These values should be similar or longer than what is found in the eapps even if they dont apply to the same part of the session. EAI OM may have shorter SISNAPI session time out.
Time Out parameter for SISNAPI connections is identical between Oms.
SES04.3
Logout of the application If applicable check the values for time out parameters on the F5 load balancing application. They should be identical to the ones found on the Oms.
Siebel login screen appears. Time Out parameters are identical to the ones found on the Oms.
SES04.4
SES04.5
Connect now using a typical User credentials.
SES04.6
Leave the session open for an amount of time shorter by a few seconds than the time out set in the eapps.cfg file (may be specific to an application alias). Then perform any kind of navigation such as a drill down.
Navigation should continue without error message related to time out parameters.
SES04.7
Now leave the session open for an amount of time exceeding by a few seconds the time out set in the eapps.cfg file. Then perform any kind of navigation such as a drill down.
An error message pops up saying that session has timed out.
Back to Total Page

Test Description Conditions Pre Post Conditions Acceptance Criteria Custom This test is to verify the status of the session on all the different servers in case of a browser window closure without proper logout. Platform up and running. Admin rights on the servers of the platform. Remote access tool and socket listing tool for IIS are required. Custom Custom Custom Comments
Test Step
Test Step Notes Description Login to the application using a typical user credentials.
Siebel Ref
SES05.1
SES05.2
Using a remote access utility, access the web servers and identifiy on which one the session is actually processed by analysing the SWSE log files. Also identify the Object Manager in charge of the session. Also it is possible to look at the socket created to connect to the OM from the web server using another tool.
The session is traced on one of the web servers,
SES05.3
Using a remote acces utility, access the OM processing the session and edit the log files for the OM process.
The session is traced on one of the OM servers.
SES05.4
Optionnaly, with the help of a DBA, and if connection pooling is not activated, it may be possible to trace the session on the DB by using the PID.
The session is traced on the DB.
SES05.5
In the Siebel application, go to the Contact screen and add a new contact.
A new contact is created.
SES05.6
Start to create a second one and in the middle of the process, close the browser window without logging out.
The window is closed without logging out.
SES05.7
Go back to the web server, refresh the log file and the list of open sockets. There should be a ghost session remaining from our previous connection.
A ghost session is still open between the web server and the OM dealing with the session.
SES05.8
Now do the same with the OM, a ghost session should be still running with the same Task ID and PID.
A ghost session is still open between the web server and the OM dealing with the session.
SES05.9
Monitor this ghost session untill it disepears, and compare the time required for this time out to occur against the parameters set in eapps.cfg file and OM SISNAPI time out parameters
Time out for ghost session is similar to existing parameters.
Back to Total Page

Test Description Conditions Pre Post Conditions Acceptance Criteria Custom This test is to verify the behaviour change between cookie and cookie-less modes of the client's browser during the execution of a Business critical process. Platform up and running. Ability to modify Internet Explorer privacy settings on the workstation. User data and credentials must be preloaded into the application in order to play the use case, as well as a step by step description of the case itself. Custom Custom Custom Comments
Test Step
Test Step Notes Description Open Internet Explorer and go to Internet Options / Privacy Settings / Advanced Privacy Settings. Make sure cookie handling is enabled.
Siebel Ref
SES06.1
Security settings are displayed cookies are accepted.
SES06.2
Connect to the Siebel Application using a typical user credentials.
SES06.3
Go to the cookie directory and look at the newly created cookies. Inside the application, run a Business Critical Process. Logout from the application by typing Ctrl-Shift-X Go back to the cookie directory for Internet Explorer.
A new cookie is created for the Siebel session.
SES06.4
The use case is ran into the application.
SES06.5
The login page appears again.
SES06.6
The session specific cookie should have disapeared.
SES06.7
Open Internet Explorer and go to Internet Options / Privacy Settings / Advanced Privacy Settings. Make sure cookie handling is disabled now.
Cookie handling is disabled.
SES06.8
Connect to the Siebel Application using a typical user credentials.
SES06.9
Inside the application, run a Business Critical Process. Take note of all functional differences in the porcess.
The use case is ran into the application.
SES06.10
Logout from the application by typing Ctrl-Shift-X Open Internet Explorer and go to Internet Options / Privacy Settings / Advanced Privacy Settings. Make sure cookie handling is enabled.
The login page appears again.
SES06.11
Security settings are displayed cookies are accepted.
Back to Total Page

Test Description Conditions Pre Post Conditions Acceptance Criteria Custom This test is to verify the amount of DB transactions during a typical Business process. Platform up and running. Ability to monitor transactions on the DB. Custom Custom Custom Comments
Test Step
Test Step Notes Description Start the monitoring process on the DB. List all connected users with there respective PID in order to trace back the OM from where the session is opened. If no ADSI authetication is used with Siebel, only few users (SIEBEL, GUESTCST and SADMIN) should be connected.
Siebel Ref
SES07.1
A list of active users is displayed.
SES07.2
On the testing workstation, connect to the application using a typical user credentials.
SES07.3
Check that a new session has opened on the DB.
The transaction monitoring starts on the DB.
SES07.4
Run the use case for a typical Business Process.
New records are created, existing records are modified.
SES07.5
When the use case is finished, logout from the application. Stop recording transactions for the correspondin g session on the DB. The session may still be open for a moment after the user disconnects.
The login screen appears.
SES07.6
The transactions have been recorded and can now be analysed.
Back to Total Page

Test Description Conditions Pre Post Conditions Acceptance Criteria Custom Verify the proper settings of the IIS thread mode for connections with the Siebel Servers. The platform must be up and running. We need to access the Web Servers in order to validate certain parameters in IIS. Custom Custom Custom Comments
Test Step
Test Step Notes Description For each of the web servers, using remote access, connect to the control panel / Admin tools / IIS control panel
Siebel Ref
SES08.1
IIS control panel is displayed.
SES08.2
For each of the virtual directories existing in IIS, double click on it in order to access its detailed parameters.
A detailed parameters popup window appears.
SES08.3
Click on the advanced tab for IIS session tuning
Advanced parameters appears.
To be confirmed
SES08.4
Make sure the session type for each virtual directory is properly setup according to Siebel recommanda tions.
Session type is in accordance to Siebel recommanda tion.
SES08.5
Apply the changes by restarting IIS services Launch a session monitoring tool in order to display IIS threads as they are created. Connect to the Siebel application using a standard user credentials. Run a typical use case into the application while monitoring the number and behaviour of correspondin g threads opened by IIS on the web server.
IIS services are restarted.
SES08.6
A list of all IIS threads appears.
SES08.7
A new thread is created.
SES08.8
Threads are created and closed down as the user connects and then logout of the application.
Back to Total Page

Test Description This test is to demonstrate that SSL encryption is used by the thin client (web browser) for accessing the Webserver and Siebel Server Test Step SEC01.1 Pre Conditions Post Conditions Acceptance Criteria SSL must be implemented beforehand on the Test plateform before we can proceed with this test. Test Step Description Notes On each of the web servers, edit the eapps.cfg and check the proper parameters in the section [connmgmt]. Check that the application aliases in this file are set-up with SSL URLs. Check on all Siebel servers that the entry 'SecureBrowse' in the 'SWE' section of the siebel.cfg file is set to "True" Custom Custom
Expected Results Actual Result The [connmgmt] section of each eapps.cfg file is properly set-up. Application aliases are properly set-up with SSL URLs. The entry 'Secure Browser' in the 'SWE' section of the siebel.cfg file is set to "True"
SEC01.6
Check that the default port setting is 443 - by typing the following command netstat -a | grep 443 at the DOS prompt while being connected by remote access or telnet on the webserver. Do this on all web servers.
Displays all connections and listening ports on 443. The telnet allows to check the proper instantiation of the SSL port on the webserver.
SEC01.9
Also from the workstation on the command line, do a "telnet 443" toward both the webservers and the load balancing http equipment (require IP adresses of both of these 2 servers and the VIP of the load balancing equipment).
Telnet 443 responds on both servers and on the NLB (Network Load Balancing).
SEC01.2
Log onto Siebel Application with administrator User ID and Password as defined in the Responsibilities table. Say OK to any certificate validation.
Siebel Splash Screen is displayed
SEC01.3 SEC01.4
Once on the Home Page, type CTRL+Shift+A to call the Site Map Check in the Web browser that the URL start with "https://" and is secure with a small padlock down right. Try to force the http prefix by removing the "s" letter Back Type CTRL+Shift+A to acces the Site Map Log out of the Siebel Application by typing CTRL+Shift+x
The Site Map is displayed The URL starts with "https://" and a padlock displays down on the right hand of the browser window. The application displays an error page The Screen Views are displayed User is logged out of the Siebel Application.
SEC01.5 SEC01.7 SEC01.8
Custom
Custom
Comment
Siebel Ref Siebel.cfg file may be has a different name on the target plateform. Below, sample parameters for eapps.cfg [connmgmt] CACertFileName = d:\siebel\admin\cacertfile.pem CertFileName = d:\siebel\admin\certfile.pem KeyFileName = d:\siebel\admin\kefile.txt KeyFilePassword = ^s*)Jh!#7 PeerAuth = TRUE PeerCertValidation = FALSE siebel.ssl.None.None://gtwyname/siebel/SSEO bjMgr_enu
Need to be local or connected by telnet to do a netstat. Also may require Admin Tools on NT box for the netstat executable.
This test should be done prior to go live from various clients locations as routes may need to be opened through corporate firewalls.
Back to Total Page

Test Description This test is to demonstrate that an error message will be displayed to the user where an incorrect password has beeen entered. Test Step SEC02.1 Pre Conditions Admin Data must be already loaded into the Test plateform in order to test different user logins. Test Step Description Log onto Siebel Application with administrator User ID and Password as defined in the Configuration table. Press the CTRL+Shift+A to access the Site Map Log out of the Siebel Application CTRL+Shift+x Attempt to log onto the Siebel Application with administrator User ID and invalid password Notes Post Conditions
SEC02.2 SEC02.3 SEC02.4
Acceptance Criteria
Custom
Custom
Custom
Custom
Actual Result
Siebel Ref
The Site Map is displayed User is logged out of the Siebel Application. User enters correct User Id and incorrect password - An error is displayed on the screen - Invalid Password. Please renter correct password.
Back to Total Page

Test Description This test is to demonstrate that an error message will be displayed to the user where an incorrect User ID has been entered. Test Step SEC3.1 Pre Conditions Admin Data must be already loaded into the Test plateform in order to test different user logins. Test Step Description Log onto Siebel Application with administrator User ID and Password as defined in the Configuration table. Press the CTRL+Shift+A to access the Site Map Log out of the Siebel Application CTRL+Shift+x Attempt to log onto the Siebel Application with incorrect administrator User ID and correct password Notes Post Conditions
SEC3.2 SEC3.3 SEC3.4
SEC3.5
Check the error message in the log files stored in the Log Directory for the error message
Acceptance Criteria
Custom
Custom
Custom
Custom
Actual Result
Siebel Ref
The Site Map is displayed User is logged out of the Siebel Application. User enters correct User Id and incorrect password - An error message is displayed on the screen - Invalid User ID . Please reenter correct User ID
The log file should contain an entry event type alias Generic log with the user log in details
Back to Total Page

Test Description Pre Conditions Post Conditions This test is to demonstrate that different views Admin Data must be already loaded into the are accessible depending of the login used to Test plateform in order to test views allocation connect to the application. mechanism. Test Step SEC04.1 Test Step Description Log onto Siebel Application with User ID and Password as defined in the Configuration table. Notes
SEC04.2
Press the CTRL+Shift+A to access the Site Map
SEC04.3 SEC04.4
Log out of the Siebel Application CTRL+Shift+x Log onto Siebel Application with Administrator User ID and Password as defined in the Configuration table. Press the CTRL+Shift+A to access the Site Map Press CTRL +SHIFT+X
SEC04.5
SEC04.6
Acceptance Criteria
Custom
Custom
Custom
Custom
Expected Results User ID and Password are authenticated against ADSI/LDAP server. Users is granted access and only the views that have been defined for the user to access are displayed. User is granted access only to the views that have been defined for the user to access will be displayed on the Site Map. User is logged out of the Siebel Application. User is granted access only to the views that have been defined for the user to access will be displayed on the Site Map. User is granted access and All views that have been defined for the user to access will be displayed. Exit from application.
Actual Result
Siebel Ref
Back to Total Page

Test Description This test is to demonstrate that all view access will be via https Test Step SEC05.1 SEC05.2 SEC05.3 Pre Conditions User ID and Password granted with access to specific views only. Test Step Description Set the parameter ' SecureBrowse' in the swe log file = True Reboot the Web Server Log onto Siebel Application with User ID and Password as defined in the Configuration table. Check the URL in the Web browser Notes Post Conditions
SEC05.4
Press the CTRL+Shift+A to access the Site Map
SEC05.5 SEC05.6 SEC05.7
Select the Accounts Log out of the Siebel Application CTRL+Shift+x Log onto Siebel Application with Administrator User ID and Password as defined in the Configuration table. Press the CTRL+Shift+A to access the Site Map
SEC05.8
SEC05.9
Log out of the Siebel Application CTRL+Shift+x
Acceptance Criteria
Custom
Custom
Custom
Custom
Expected Results The entry SecureBrowse= True in the SWE log file has been set WebServer Rebooted Siebel Splash Screen is displayed
Actual Result
Siebel Ref
The web browser should display https:\\ pathname , where pathname is defined as Server IP address and location User ID and Password are authenticated against ldap LIGHT WEIGHT DIRECTORY ACCESS PROTOCOL - User is granted access and Only the views that have been defined for the user to access will be displayed.
The Accounts View is selected via http access. User is logged out of the Siebel Application. Siebel Splash Screen is displayed
User ID and Password are authenticated against ldap LIGHT WEIGHT DIRECTORY ACCESS PROTOCOL - User is granted https access and all views that have been defined for the user to access will be displayed.
User is logged out of the Siebel Application.
Back to Total Page

Test Description Pre Conditions Post Conditions This test is to ensure that password data for The platform must be up and running. Anonymous and Webupdate accounts are not stored in clear in the eapps.cfg file. Test Step SEC06.1 SEC06.2 Test Step Description On the siebel web server navigate to the eapps.cfg file found in the bin directory Check that the setting for encrypted password is set to true .ie EncryptedPassword=True Check that the values for AnonPassword et WebUpdatePassword are encrypted Notes
SEC06.3
Acceptance Criteria
Custom
Custom
Custom
Custom
Expected Results User navigates to the eapps.cfg file under the bin directory. EncryptedPassword=True
Actual Result
Siebel Ref
Values for AnonPassword and WebUpdatePassword are encrypted.
Back to Total Page

Test Description Pre Conditions Post Conditions This test is to ensure that passwords for The platform must be up and running. standard Siebel accounts have properly been modified. Test Step SEC07.1 Test Step Description User attempts to log into the Siebel Application with several standard User ID : SADMIN, GUESTCST, LDAP, SIEBEL, each time with a password similar to the login Notes
Acceptance Criteria
Custom
Custom
Custom
Custom
Expected Results Error Message displayed - Please enter correct User ID and Password for each try.
Actual Result
Siebel Ref
Back to Total Page

Test Description User has Admin Access to the Siebel Web Server Test Step SEC08.1 SEC08.2 Test Step Description On the siebel web server navigate to the eapps.cfg file found in the bin directory Check that the setting for encrypted password is set to true .ie EncryptedPassword=True Reboot the Siebel Web Server Log into the Siebel Web Server in User Name in the User Name Field Type in the Password in the Password Field Notes Pre Conditions Post Conditions
SEC08.3 SEC08.4 SEC08.5
Acceptance Criteria
Custom
Custom
Custom
Custom
Expected Results User navigates to the eapps.cfg file under the bin directory EncryptedPassword=True
Actual Result
Siebel Ref
Siebel web server Reboots User Name is is displayed in clear text Password entered in the Password Field in encrypted
Back to Total Page

Test Description Pre Conditions Post Conditions This test is to validate the proper setting of the Depending of the authetication mode plateform in order to allow users to change implemented, certain settings may be their password. necessary to allow password change by users. Test Step SEC09.1 Test Step Description Connect to the Siebel application using a User login as specified in the responsibilites page Type Ctrl+Sht+A to access the Site Map Click on the Admin View. In the password field, type a new password and confirm it. Type Ctrl+Sht+X to logout Login with the same user ID and the new password. Notes
SEC09.2 SEC09.3 SEC09.4 SEC09.5 SEC09.6
Acceptance Criteria
Custom
Custom
Custom
Custom
Expected Results The Siebel Home page is displayed into the browser window. 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 the browser window.
Actual Result
Siebel Ref
Comments
Check the name of the view where a user can modify his password
Back to Total Page

Test Description This test checks the status of SSL encrypted SISNAPI communication between the Web servers and the Siebel Servers. Test Step SEC10.1 SEC10.2 SEC10.3 SEC10.4 SEC10.5 Test Step Description Notes Pre Conditions Post Conditions
Acceptance Criteria
Custom
Custom
Custom
Custom
Expected Results
Actual Result
Siebel Ref
Back to Total Page

Test Description This test is to validate the proper settings of the ADSI/LDAP authentication process. Test Step SEC11.1 SEC11.2 SEC11.3 SEC11.4 SEC11.5 Pre Conditions Requires the ADSI/LDAP login authentication mode to be implemented. Test Step Description Notes Post Conditions
Acceptance Criteria
Custom
Custom
Custom
Custom
Expected Results
Actual Result
Siebel Ref
Back to Total Page

Test Description This test is to validate that the various Siebel Services are run under a common specific Domain account. Test Step SEC12.1 Pre Conditions Have System Admin rights on each of the servers or at list be able to list running services from the control pannel. Test Step Description For each Siebel server of the plateform, connect to the service list of the Control Panel, using remote 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 same way and check the Domain account used to run IIS services. For each other server of the plateform (Actuate, Load Balancing...) do the same test and verify that each time a specific Domain account is used to run the different services. Notes Post Conditions
SEC12.2
SEC12.3
SEC12.4
Acceptance Criteria
Custom
Custom
Custom
Custom
Expected Results The list of all services with status appears
Actual Result
Siebel Ref
The same Domain account is used to start the Siebel Services on all servers of the plateform The IIS services are run with the same Donmain account on the different Web Servers Specific Domain accounts are used to run each one of the different services.
Back to Total Page

Test Description Pre Conditions Post Conditions This test is to validate the inability to connect Requires a network and workstation set-up directly to the File System and to the DB from similar to ones used on the target architecture. a Web Client workstation. Test Step SEC13.1 Test Step Description From the workstation from a DOS command window, run the following command in order to test the connectivity to the DB server : telnet port number of the Oracle listener Notes
SEC13.2
Open a file explorer window and type the URL of the File System in the address bar.
Acceptance Criteria
Custom
Custom
Custom
Custom
Expected Results No answer must be received showing that the listener is not open to direct querries from the end users sub-network
Actual Result
Siebel Ref
An error message appears of the type : The specified network share or drive is unreachable.
Back to Total Page

Test Description Conditions Pre Post Conditions Acceptance Criteria Custom This test is to Platform verify that an must be up error will be and running. displayed on login page if an invalid anonymous credential is provided in the eapps.cfg file. Custom Custom Custom
Test Step
Test Step Notes Description Try to connect to the application by calling one of the specified URL. Now edit the eapps.cfg file on all web servers. Modify the login used for anonymous login (GUESTCST ) on both default and specific aliases sections.
Siebel Ref
SEC14.1
Login page appears.
SEC14.2
The login used for anonymous login is modified.
SEC14.3
Restart the web servers and try to connect to the application by calling one of the specified URL.
An error page is displayed.
SEC14.4
Now again on all web servers, edit the eapps.cfg file on all web servers. Put back the standard login for anonymous login, but change the password. Warning, if the password is encrypted, copy it in a safe place as we will need to put it back after this test. Once the password is modified, save the file and restart the IIS.
Standard anonymous password is put back again, bad password is specified. An error page appears when accessing the application.
SEC14.5
Analyse the log file of the SWSE as it shows what problems was encountered with useful error codes.
SWSE error codes are analysed.
SEC14.6
Roll back the changes by editing again the eapps.cfg and putting back the original password. Restart the web servers and try to access the specified URL.
Login page appears.
Back to Total Page

Test Description This is to verify that the Gateway Server is accessible from the various servers of the enterprise. Steps AV01.1 Pre Conditions All Siebel Server Components are installed on the platform Test Desc Connect to each Siebel server of the Enterprise and try to access the siebel gateway service by typing in a DOS command window - telnet ip address AND specific port number where ip address and port are defined in the configuration table. Notes Post Conditions
AV01.2 AV01.3 AV01.4 AV01.5
On server reponse at prompt, Enter User ID and Password Connect to the Siebel Gateway Server locally or with a re+ote access tool. In the Control Panel, go to the Services list. Look for the Siebel Gateway service in the list. It should be running, in automatic launch mode and launched by a specific Domain account. Navigate to the \gtwysrvr\ADMIN on the Siebel Gateway server. Check to see if the siebns.dat file exists.
AV01.6 AV01.7
Acceptance Criteria
Custom
Custom
Custom
Custom
Expected Results The Gateway answers to the telent request.
Actual Result Pass / Fail Data Input iebel Ref S
Siebel Reference
User is now connected to the Siebel Gateway Service User is now connected to the Siebel Gateway Service A list of services is displayed. The Siebel Gateway service is running in automatic mode and launched by a specific Domain user. The prompt changes to \gtwysrvr\ADMIN. The siebns.dat file is present.
Comments
Siebel Reference
Only possible localy on the server or with Administration pack for Windows from a workstation or with special tools to see processes remotely.
Need to make a backup task of the siebns.dat
Back to Total Page

Test Description Pre Conditions Post Conditions This is to verify that the name server service is Siebel Gateway Server is up and services are running on the Siebel Gateway Server running Test Step AV02.1 Test Step Description Telnet on to the siebel gateway service - telnet ip address where ip address is defined in the configuration table, enter User ID and Password Press simultaneously the CTRL ALT DEL keys Select the Process Tab Check to see if the Name Server Service siebsvc.exe is present Navigate to the \gtwysrvr\ADMIN on the Siebel Gateway server Check to see if the siebns.dat file exists Notes
AV02.2 AV02.3 AV02.4 AV02.5 AV02.6
Acceptance Criteria
Custom
Custom
Custom
Custom
Expected Results The User Name and Password are displayed
Actual Result
Siebel Ref
The Windows Task Manager is displayed A list of processes running are displayed. The Name Server Service siebsvc.exe is present The prompt changes to \gtwysrvr\ADMIN The siebns.dat file is present
Comments Redondant test with AV01R
Back to Total Page

Test Description Pre Conditions Post Conditions This test is to verify that the server Siebel Gateway Server is up and services are administration view can be accessed from the running. Warning! There is a major technical web client difference in the way certain admin views are accessed depending if it is from a dedicated or thin web client. In the first case, a direct connection (no FW ie) is required between the workstation and the Siebel Gateway.
Test Step AV03.1
Test Step Description Log onto Siebel eService with Siebel Administrator responsability (SADMIN type) Press Ctrl+Shift+A to access the site map Go to the View Administration / Configuration
Notes
AV03.2 AV03.3
AV03.4
Click in the history back button (Siebel bouton not the IE bouton) in order to come back to the Server Admin default View Go to the View Administration / Server Management
AV03.5
AV03.6
Check to see if the siebns.dat file exists
Acceptance Criteria
Custom
Custom
Custom
Custom
Actual Result
Siebel Ref
The Site Map is displayed showing the various views The Server Administration Configuration menu view is displayed as Administration - Server Configuration Enterprise Explorer Enterprises Component Definitions Component Groups System Alerts Servers Components Events Parameters Parameters
The Screen view is displayed showing the various views Administration - Server Management :Administration - Server Management Components State Values Statistics Tasks Enterprises Servers Log Sessions Statistics Tasks Sessions Log Parameters State Values Statistics Tasks Log Parameters State Values Statistics
The siebns.dat file is present
Comments
Point to verify : the specified file should be listed in a list applet
Back to Total Page

Test Description This test is to verify that the load balancing configuration file can be generated by typing the command LBCONFIG at the console command line Test Step AV04.1 Pre Conditions Siebel Gateway Server is up and services are running Post Conditions
Test Step Description On a server of the Enterprise by remote access, or on a workstation with dedicated web client and server manager installed, open a DOS session by selecting START >RUN and type CMD in the Open drop down list and select ok At the DOS prompt navigate to the \bin subdirectory within the Siebel Server root directory ie cd \siebel_server_root\bin At the DOS prompt type srvrmgr /s siebel_server where siebel_server name is the name of the Siebel Server on which we are going to launch the commands (this name is specified in the configuration table) and press enter Enter SADMIN type login information in order to start 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 has started by examining the processes in windows Task Manager Ctr Alt Del and selecting the process tab Return to the CLI - Command Line Interface Type at the command line interface - generate lbconfig and hit <enter> key Check that the Lbconfig file has been stored in the admin subdirectory of the Siebel Server installation directory as \sieble\eapps\admin Review the contents of the generated lbconfig.txt file to verify that virtual server definitions do not include any Siebel Servers that will not participate in load balancing
Notes
AV04.2
AV04.3
AV04.3.1
AV04.4
AV04.5
AV04.6 AV04.7 AV04.8
AV04.9
Acceptance Criteria
Custom
Custom
Custom
Custom
Expected Results The DOS session is now visible
Actual Result
Siebel Ref
The DOS prompt should change to indicate that you are now in the siebel_server_root\bin directory. The Siebel Server Manager program has started and the dos prompt changes to svrmgr:siebel_server where the siebel_server is the name specified in the configuration tables
The siebel server starts
The Server Manager component ServerMgr.exe file should be shown as running as a process. Command Line Interface prompt is visible. The IB Config file is generated Lbconfig file is stored in Siebel Server installation directory as \sieble\eapps\admin The virtual server definitions do not include any Siebel Servers that will not participate in load balancing
Back to Total Page

Test Description This test is to verify ODBC Data source Connectivity for Oracle in a windows environment Test Step AV05.1 Pre Conditions Database must be available Post Conditions
Test Step Description Navigate to the Control Panel >Performance Maintenance >Administrative Tools>Data Sources ODBC On the ODBC datasource Administrator Screen Dialogue box , select the system DSN tab Select the datasource labeled as and click th configure
Notes
AV05.2
AV05.3
AV05.4 AV05.5
To test the ODBC connection - Click the Test Connect Button In the windows registry locate the following registry enrty key - hkey-local-machine software odbc odbc.ini name_dsn Verify that the following registry keys are set as shown - Packet Size=0 EnableScrollabeCursors=0 columnAsChar=1 ColumnSizeAsCharacter=1
AV05.6
Acceptance Criteria
Custom
Custom
Custom
Custom
Expected Results The DOS session is now visible
Actual Result
Siebel Ref
The DOS prompt should change to indicate that you are now in the siebel_server_root\bin directory. The Siebel Server Manager program has started and the dos prompt changes to svrmgr:siebel_server where the siebel_server is the name specified in the configuration tables The siebel server starts The Server Manager component ServerMgr.exe file should be shown as running as a process. Command Line Interface prompt is visible.
Back to Total Page

Test Description This test is to verify that an error will be displayed if the web server port entry is incorrect in the eapps.cfg file Pre Conditions All Siebel Services are available Post Conditions
Test Step AV06.1
Test Step Description Edit the value of the Web Server port entry under the SWSE section of the eapps.cfg config file by changing this value to a non existent port number Save the changes in the eapps.cfg file and restart the web server Log into the Siebel Client and enter Username and Password Launch the siebel web client by entering the user id and password specified and pressing the enter key
Notes
AV06.2 AV06.3 AV06.4
Acceptance Criteria
Custom
Custom
Custom
Custom
Expected Results Current Web server entry is edited
Actual Result
Siebel Ref
Eapps.cfg file changes are saved and Web Server is rebooted User logs into the Siebel Client Page cannot be displayed
Comments Port number change requires much more changes; -IIS port -Firewalls and Network routing -Various Siebel Parameters such as eapps.cfg
Back to Total Page

Test Description This test is to verify that an error will be displayed if the virtual directories have not been created on the web server. Pre Conditions All Siebel Services are available Post Conditions
Test Step AV07.1 AV07.2
Test Step Description On each of the Web servers, connect to the IIS Administration Panel Remove the path pointing to the virtual web entries under the SWSE section of the eapps.cfg config file. Save the eapps.cfg file and restart the web server so the changes take effect. Launch the siebel web client by entering the user id and password specified and pressing the enter key.
Notes
AV07.3 AV07.4
Acceptance Criteria
Custom
Custom
Custom
Custom
Expected Results List of all IIS services appears Current virtual directories on the web server are removed eapps.cfg file changes saved and web server restarted. Page cannot be displayed
Actual Result
Siebel Ref
Comments The operation described here will block access to the Siebel Server but not to the web server. Disabling application aliases requires changes in both IIS and eapps.cfg file.
Back to Total Page

Test Description This test is to verify that an error 'page not found 'will be displayed if an invalid user name exists. Test Step AV08.1 Pre Conditions All Siebel Services are available Post Conditions
Test Step Description Edit the http entry under the default settings of the eapps.cfg file by entering an invalid username Save the eapps.cfg file and reboot the web server for changes take effect. Launch the siebel web client by entering the user id and password specified and pressing the enter key.
Notes
AV08.2 AV08.3
Acceptance Criteria
Custom
Custom
Custom
Custom
Expected Results http entry edited
Actual Result
Siebel Ref
eapps.cfg file is saved and web server is rebooted. Page Not Found error is displayed
Back to Total Page

Test Description This test is to verify that a blank page will be displayed if the password settings are incorrect. Test Step AV09.1 Pre Conditions This test is to verify that a blank page will be displayed if the http port settings are incorrect Test Step Description Edit the http entry under the default settings of the eapps.cfg file by entering an invalid password. Save the eapps.cfg file and reboot the web server for changes take effect. Launch the siebel web client by entering the user id and password specified and pressing the enter key. Notes Post Conditions
AV09.2 AV09.3
Acceptance Criteria
Custom
Custom
Custom
Custom
Expected Results http entry edited with an invalid port address eapps.cfg file is saved and web server is rebooted. Page Not Found error is displayed
Actual Result
Siebel Ref
Back to Total Page

Test Description Conditions Pre Post Conditions Acceptance Criteria Custom This test is designed to confirm the proper routing between OM's of new incoming sessions. Requires an admin access to Load Balancing application in order to trace in real time the routing of new sessions. Also requires access to various log files on Siebel and Web Servers. Custom Custom Custom Comments
Test Step
Test Step Notes Description Using remote access or management panel, access the F5 load balancing application.
Siebel Ref
LOA01.1
The list of routed sessions appears.
LOA01.2
Connect to the application using a typical user credentials.
The Siebel Home Page appears.
LOA01.3
According to the routing information displayed on the F5 load balancer or by analysing the SWSE log file, pick the OM server executing the session and edit the log file of the specific OM process.
Routing information is displayed on F5 and the detailed information is accessible on the OM server executing the session.
LOA01.4
Using another Internet Explorer window, connect another time to the application, using either the same login or a different one.
Siebel home page is displayed again,
LOA01.5
Going back to the load manager, another OM server is addressed to open a new session. On this server, edit the log file for the specific OM process.
Routing information is displayed on F5 and the detailed information is accessible on the OM server executing the session.
LOA01.6
Open as many sessions as wanted to test that individual sessions are properly routed. All OM servers should be addressed statisticaly in accordance with the rules established for the F5 load balancer,
Other sessions are opened and routed to other OM servers depending of the rules established on the F5 load balancer.
Back to Total Page

Test Description Conditions Pre Post Conditions Acceptance Criteria Custom 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 web servers. Ability to connect from numerous workstations possibly with different IP addresses depending of the IP routing strategy chosen. Custom Custom Custom Comments
Test Step
Test Step Notes Description Connect to the application using a typical user credentials from a testing workstation. Take note of the network parameters of the workstation.
Siebel Ref
LOA01.1
The Siebel Home Page appears.
LOA01.2
By analysing the SWSE log files, identify the web server on which the connection is routed.
The connection is directed to a specific web server.
LOA01.3
Depending of the NLB criterias for routing, connect to the application using either another workstation with another IP address (fixed IP routing), or with the same one (dynamic IP routing).
Siebel home page is displayed again,
LOA01.4
By analysing the SWSE log files, identify the web server on which the connection is routed.
The connection is directed to a specific web server.
Back to Total Page

Test Description Conditions Pre Post Conditions Acceptance Criteria Custom This test is to verify that the load balancing configuration file can be generated by typing the command LBCONFIG at the console command line F5 load balancer is installed and properly tuned to route requests to Siebel Servers OM. Custom Custom Custom
Test Step
Test Step Notes Description On a server of the Enterprise by remote access, or on a workstation with dedicated web client and server manager installed, open a DOS session by selecting START >RUN and type CMD in the Open drop down list and select ok
Siebel Ref
LOA03.1
The DOS session is now visible
LOA03.2
At the DOS prompt navigate to the \bin subdirectory within the Siebel Server root directory ie cd \siebel_serve r_root\bin
The DOS prompt should change to indicate that you are now in the siebel_server _root\bin directory.
LOA03.3
At the DOS prompt type srvrmgr /s siebel_server where siebel_server name is the name of the Siebel Server on which we are going to launch the commands (this name is specified in the configuration table) and press enter
The Siebel Server Manager program has started and the dos prompt changes to svrmgr:siebel _server where the siebel_server is the name specified in the configuration tables
LOA03.4
Enter Server Administrator type credentiqls in order to start the srvmgr session on the target server
Logged as SADMIN or similar account.
LOA03.5
Return to the CLI Command Line Interface
Command Line Interface prompt is visible.
LOA03.6
Type at the command line interface - generate lbconfig and hit <enter> key
The IB Config file is generated
LOA03.7
LOA03.8
Check that the Lbconfig file has been stored in the admin subdirectory of the Siebel Server installation directory as \sieble\eapps \admin Review the contents of the generated lbconfig.txt file to verify that virtual server definitions do not include any Siebel Servers that will not participate in load balancing
Lbconfig file is stored in Siebel Server installation directory as \sieble\eapps \admin
The virtual server definitions do not include any Siebel Servers that will not participate in load balancing

Test Schedule PPT V3

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Test Schedule PPT V3

Caricato da

Copyright:

Formati disponibili

Num Domain 1 Security

5 Security 6 Security 7 Security 8 Security 9 Security

SEC05 SEC06 SEC07 SEC08 SEC09

10 Security 11 Security 12 Security

SEC10 SEC11 SEC12

14 Security 15 Availability 16 Availability

SEC14 AV01 AV02

18 Availability 19 Availability 20 Availability 21 Availability 22 Availability 23 Availability

AV04 AV05 AV06 AV07 AV08 AV09

28 Session Management 29 Session Management

30 Session Management 31 Session Management

33 Session Management 34 Session Management

37 Connectivity 38 Connectivity 39 Connectivity 40 Connectivity 41 Connectivity 42 Connectivity 43 Connectivity 44 Connectivity

CON03 CON04 CON05 CON06 CON07 CON08 CON09 CON10

58 Deployment 59 Deployment 60 Deployment 61 Deployment 62 Deployment 63 Deployment

DEP03 DEP04 DEP05 DEP06 DEP07 DEP08

MAI01 MAI02 CAC01 CAC02 CAC03 CAC04 CAC05 DAT01

All required components of the platform must be set-up prior to testing

Requires a precise list of all managed components and their localisation.

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

All components are available.

All components are available.

The Siebel Gateway must be properly backed up

Aprox. Duration Status 3h Reviewed

Redondant 1h 1h 1h Reviewed Reviewed Redondant Reviewed

TBC TBC Reviewed

Reviewed Changed Redondant

Changed Changed Changed Changed Changed Changed

Applicable to load testing scenario

Needs to be clarified in terms of target architecture.

TBC 1h 2h 2h 1h 1h 1h 1h Reviewed Reviewed Reviewed Reviewed Reviewed Reviewed Reviewed

Not sure that the Wireless functionnality will be implemented.

Needs to be clarified in terms of target architecture.

Applicable to load testing scenario.

Applicable to load testing scenario.

Redondant Redondant 1h 2h 1h 1h Reviewed Reviewed Reviewed Reviewed

TBC TBC TBC TBC TBC TBC TBC TBC

SEC03 SEC04 SEC05 SEC06 SEC07 SEC08

AV03 AV04 AV05 AV06 AV07 AV08 AV09

DEP03 DEP04 DEP05 DEP06 DEP07 DEP08

SES03 SES04 SES05

CAC03 CAC04 CAC05

DEP10.1 DEP11.1 DEP12.1

DAT01 - Create Service Request Record

Back to Total Page

Test Step DEP01.1

Shut down the database server

Select the Contact Tab

Contact Tab is selected and no records are available

Enter CTRL +Shift+A

The platform is restarted.

Siebel Home Page is displayed.

Account is not corrupted

Back to Total Page

Test Step DEP02.1

File system is not accessible by FSM components anymore.

User rights are restored. Document opens properly in MS Word.

Back to Total Page

Test Step DEP03.1

Select the Send Letter Option form the File Menu

The Screen view is displayed showing the various screen views

Select the Personal Template Tabs

Back to Total Page

Expected Results Result Actual