tco prod te020 testcases_draft1a

TE.020 Unit Test Script


AIM


The Corporate Office, DubaiTest Cases for OracleAS and RAC ImplementationAuthor:

Creation Date:Sept 24, 2006

Last Updated:Oct 31, 2006

Document Ref:

Version:Draft 1A

Note: Title, Subject, Last Updated Date, Reference Number, and Version are marked by a Word Bookmark so that they can be easily reproduced in the header and footer of documents. When you change any of these values, be careful not to accidentally delete the bookmark. You can make bookmarks visible by selecting Tools->OptionsView and checking the Bookmarks option in the Show region.Approvals:Wassim HamwiDirector Solution Delivery, TCO

Ravindran SubbiahManager ITSS, TCO

Note: To add additional approval lines, press [Tab] from the last cell in the table above.

autotext "PIC Oracle Logo" \* Mergeformat

Copy Number_____

Note: You can delete any elements of this cover page that you do not need for your document. For example, Copy Number is only required if this is a controlled document and you need to track each copy that you distribute.

Document Control

Change Record

1DateAuthorVersionChange Reference

24-Sep-06Srinivas KalyanDraft 1ANo Previous Document

Reviewers

NamePosition

SundarajanArchitect, TCO

Saravanan OmprakashPM, Oracle Consulting

Mahesh RaoArchitect, Oracle Consulting

Distribution

Copy No.NameLocation

1 Library MasterProject Library

2 Project Manager

3

4

Note: The copy numbers referenced above should be written into the Copy Number space on the cover of each distributed copy. If the document is not controlled, you can delete this table, the Note To Holders, and the Copy Number label from the cover page.

Note To Holders:

If you receive an electronic copy of this document and print it out, please write your name on the equivalent of the cover page, for document control purposes.

If you receive a hard copy of this document, please write your name on the front cover, for document control purposes.

Contents

iiDocument Control

4Introduction

5Purpose

6Test Cases for Application Server components

6Infrastructure Real Application Clusters

9Identity Management Oracle Internet Directory

11Identity Management Single Sign-On Server

13Synchronization UM OID

14Synchronization AD OID, Windows Native Authentication

16Integration Oracle E-Business Suite and OID

18Open And Closed Issues For This Deliverable

18Open Issues

18Closed Issues

Note: To update the table of contents, put the cursor anywhere in the table and press [F9]. To change the number of levels displayed, select the menu option Insert>Index and Tables, make sure the Table of Contents tab is active, and change the Number of Levels to a new value.

Introduction

This document details the test cases along with the expected results for the implementation of

Oracle Real Application Server Deployment

Oracle AS Infrastructure Deployment over High Availability

SSO & OID integration with Ebusiness Suite

UM- OID synchronization

AD-OID synchronization

WNA-SSO integration

Purpose

This document addresses the following with respect to the Oracle Application Server and oracle eBusiness Suite Test scenarios to validate the following Oracle Stack implementation.

Oracle Identity management

Oracle Application Server EE

Oracle eBusiness Suite

Test Cases for Application Server components

Infrastructure Real Application Clusters

Test cases for CRS:

Before performing these test cases, login as oracle software owner on RAC node and set environment to CRS by running $/home/oracle/crs.env file. Perform below steps on all RAC nodes (Pebpid01 & Pebpid02).

Step #TaskExpected ResultActual Results

1. Verify CRS processes.

$ps ef | grep crsShows CRS processes.

2. Verify CRS status.

$crs_stat -tDumps the information for each resource.

3. Verify the nodes of the cluster.

$olsnodesShould return all the nodes of the cluster.

Test cases for Database:

Before performing these test cases, login as oracle software owner on RAC node and set environment to DB by running $/home/oracle/db.env file. Perform steps 1 8 on all RAC nodes (Pebpid01 & Pebpid02). The commands listed in this section are specific to node1. When performing these activities on the other node replace the hostname to node2. Ensure that the RAC CRS services are up and running before starting these test cases.


1. Verify listener processes.

$ps ef|grep tnsShows listener processes.

2. Verify Database processes.

$ps ef|grep pmonShows database pmon processes.

3. Verify DB instance status.

$srvctl status instance -d PINFRA i PINFRA1Shows database instance up.

4. Verify Node apps status.

$srvctl status nodeapps n pebpid01Show listener, VIP, ONS and GSD are up.

5. Verify DB instance shutdown.

$srvctl stop instance -d PINFRA i PINFRA1Database successful shutdown.

6. Verify Node apps shutdown.

$srvctl stop nodeapps n pebpid01Node apps successful shutdown.

7. Verify Node apps startup.

$srvctl start nodeapps n pebpid01Node apps successful startup.

8. Verify DB instance startup.

$srvctl start instance -d PINFRA i PINFRA1Database successful startup.

9. TAF test

From an oracle client login to database using SQLPLUS as system user.

$sqlplus sys/@PINFRA as sysdba

Run the following query

SQL>select * from v$instance;On the database server connect to the instance returned in the previous query as sysdba user.

$sqlplus / as sysdba

Run the following query from client window

SQL>select * from dba_objects;

From the server SQL session issue the following command while the previous query returning the results. This should be performed parallel i.e. while the query returning results in the client session

SQL>shutdown abort;After the completion of dba_objects query, run the following command to find out the current instance details.

SQL>select * from v$instance;Should connect to one of the RAC database instance.

Should give you the instance details. Either PINFRA1 or PINFRA2Should connect the instance.

Query returns the list of objects in the database. Its long running query.

The instance would be aborted but the query should continue on the client SQL session.

Now it should show the other (2nd) RAC instance details.

Identity Management Oracle Internet Directory Test cases for OID:

Before performing these test cases, login as oracle software owner on OID node and set environment to OID by running $/home/oracle/oid.env file. Perform below steps on all OID nodes (Pebpid01 & Pebpid02). Ensure that the RAC database services are up and running before starting these test cases.


1. Verify OID & HTTP server component status.

$opmnctl statusShows OID & HTTP_Server components are up.

2. Verify Enterprise Manager status.

$emctl status iasconsoleShows Enterprise Manager is running.

3. Verify Enterprise Manager shutdown.

$emctl stop iasconsoleSuccessful shutdown.

4. Verify DIP Server component shutdown.

$oidctl connect=PINFRA server=odisrv instance=1 configset=1 stop

Note: DIP server can run only on one server at a time. If it is up on the other node this step will fail on this node.Successful shutdown.

5. Verify OID component shutdown.

$opmnctl stopproc ias-component=OIDSuccessful shutdown.

6. Verify OPMN shutdown.

$opmnctl stopallSuccessful shutdown.

7. Verify OPMN startup.

$opmnctl startSuccessful shutdown.

8. Verify OID component startup.

$opmnctl startproc ias-component=OIDSuccessful startup.

9. Verify DIP Server component startup.

$oidctl connect=PINFRA server=odisrv instance=1 configset=1 start

Note: DIP server can run only on one server at a time. If it is started on this the same step on the other node will fail.Successful startup.

10. Verify Enterprise Manager startup.

$emctl start iasconsoleSuccessful startup.

11. Verify ldapbind.

$ldapbind -p 389 -D "cn=orcladmin" -w Bind successful.

12. Login to Enterprise Manager website from Internet Explorer as ias_admin and click on "UAT_OID.pebpid01.dubaiworld.ae link.

http://pebpid01.dubaiworld.ae:1156/Shows OID is up on pebpid01.

13. Login to Enterprise Manager website from Internet Explorer as ias_admin and click on "UAT_OID.pebpid02.dubaiworld.ae link.

http://pebpid02.dubaiworld.ae:1156/Shows OID is up on pebpid02.

14. Repeat the steps 1-13 on the other node

15. Verify ldapbind through Hardware Load Balancer

$ldapbind -p 389 -D "cn=orcladmin" -w Bind successful.

16. Verify ldapbind through Hardware Load Balancer while only one OID server is up

Stop one of the OID server and run

$oidctl connect=PINFRA server=odisrv instance=1 configset=1 stop$ldapbind -p 389 -D "cn=orcladmin" -w Bind successful.

17. Verify ldapbind through Hardware Load Balancer while only one OID server is up

Stop the other OID server and run

$oidctl connect=PINFRA server=odisrv instance=1 configset=1 stop$ldapbind -p 389 -D "cn=orcladmin" -w Bind successful.

Identity Management Single Sign-On Server Test cases for SSO servers:

Before performing these test cases, login as oracle software owner on SSO node and set environment to SSO by running $/home/oracle/sso.env file. Perform below steps on all SSO nodes (Pebpid01 & Pebpid02). Ensure that the RAC database and OID services are up and running before starting these test cases.


1. Verify OC4J_SECURITY & HTTP server components status.

$opmnctl statusShows OC4J_SECURITY & HTTP_Server components are up.

2. Verify Enterprise Manager status.

$emctl status iasconsoleShows Enterprise Manager is running.

3. Verify Enterprise Manager shutdown.

$emctl stop iasconsoleSuccessful shutdown.

4. Verify HTTP_Server shutdown.

$opmnctl stopproc ias-component=HTTP_ServerSuccessful shutdown.

5. Verify OC4J_SECURITY component shutdown.

$opmnctl stopproc ias-component=OC4JSuccessful shutdown.

6. Verify OPMN shutdown.

$opmnctl stopallSuccessful shutdown.

7. Verify OPMN startup.

$opmnctl startSuccessful shutdown.

8. Verify HTTP_Server startup.

$opmnctl startproc ias-component=HTTP_ServerSuccessful startup.

9. Verify OC4J_SECURITY component startup.

$opmnctl startproc ias-component=OC4JSuccessful startup.

10. Verify Enterprise Manager startup.

$emctl start iasconsoleSuccessful startup.

11. Login to Enterprise Manager website from Internet Explorer as ias_admin and click on "Inet_ASSSO.ossosrv1.dubaiworld.ae link.

http://pebpid01.dubaiworld.ae:1810/Shows HTTP and OC4J is up.

12. Login to below link from Internet Explorer as orcladmin and click Administer SSO partner applications.

http://dwcpsso.dubaiworld.ae:6789/pls/orassoShows all applications that are registered with SSO.

13. Login to below link from Internet Explorer as orcladmin.

http://dwcpsso.dubaiworld.ae :6789/oiddasWill give you the administrator privilege to create, modify and delete user details

14. Try to login as orcladmin by clicking Login link in OIDDAS home page and provide its password in the login screen.

User will login to OIDDAS as orcladmin

15. Create a test user (e.g. demouser) and logout from OIDDAS.

User created successfully

16. In Internet Explorer open SSO URL http://dwcpsso.dubaiworld.ae:6789/pls/orassoClick login link and provide the test user credentials (created in step 3).User will see SSO home page.

17. Click on the Logout linkUser will see SSO logout page.

Synchronization UM OID Test cases for UM-OID Synchronization:

Ensure that the all OracleAS services including DIP agent are up and running before starting these test cases. Make sure that the UM database is up and running.


1. After initial synchronization login to http://dwcpsso.dubaiworld.ae:6789/oiddas as orcladmin with company name as DubaiTrade, click on directory tab then click on the go button.Should display all synchronized users from UM in OID.

2. In the http://dwcpsso.dubaiworld.ae:6789 /oiddas, login as one of the synchronized users by providing the correct user name and passwordShould be able to login

3. Repeat step 3 with incorrect passwordShould not be able to login

4. Insert one row into the users table and then login as orcladmin, check if the user existsThe user should be listed

5. Login as user freshly synchronized, repeat step 2 and 3 for this userShould be able to login when correct password is provided

6. Now disable this user in the database and then try to login as this userShould not be able to login

7. Choose a user randomly, change the password for the user in the database, Then try to login as this user with the old passwordShould not be able to login

8. Repeat Step 8 with the changed passwordShould be able to login

9. Delete the user in OID, the user will not be deleted in the database, after sometime check if the user has been recreatedThe user should not be recreated

10. Insert a record with user_name =35 characters, also login as that userThe user should get synchronized and should be able to login

11. Insert a record with null passwordThe user should be synchronized but should not be able to login

Synchronization AD OID, Windows Native Authentication Test cases for AD-OID Synchronization:

Ensure that the all OracleAS services including DIP agent are up and running before starting these test cases. Make sure that the AD server is up and running.


1. Create a user in Active directory and login to http://dwcpsso.dubaiworld.ae:6789/oiddas as orcladmin. Search for user you created in AD.The user should be synced to OID

2. Login to windows system using any user synced from AD to OID

Check for browser setting

Tool ( Internet options ( Advanced

In the security section, select Enable integrated windows authentication

Tools ( internet options ( security ( local intranet ( click sites

Add http://dwcpsso.dubaiworld.ae:6789 Tools ( internet options ( security ( local intranet ( click custom level

In the user authentication section ( select automatic logon in intranet zoneBrowser setting should be OK

3. Open any application server URL which are protected by SSO

http://dwcpsso.dubaiworld.ae:6789/oiddasClick login link. The User should be logged into without asking for username and passwordUser logged in without asking for username and password

4. Click LogoutUser logged out successfully

5. Check fallback login

From any windows desktop which is not logged into Active Directory Domain, login to

http://dwcpsso.dubaiworld.ae:6789/oiddasClick Login

You will see SSO screen or HTTP basic authentication screen depending on OS, browser version and browser configuration

Login as AD_DOMAIN\ADUSERNAME and ADPASSWORD

Login successfully

For ad users, you need to specify the domainameAD users login using

\username and password

Integration Oracle E-Business Suite and OID Test cases for EBS & OID Integration:

Ensure that the all OracleAS services including DIP agent are up and running before starting these test cases. Make sure that the AD server is up and running.


1. Create a user in eBusiness suite to use the link-on-the-fly option.

http://dwcp.dubaiworld.ae/OA_HTML/AppsLocalLogin.jspLogin as sysadmin and create the user with company name (DT) appending. Assign a role to the user.User created in eBS with a role.

2. Login to eBusiness suite through

http://dwcp.dubaiworld.ae/oa_servlets/AppsLoginProvide user credentials in SSO login page.User will be prompted for eBS username and password after successful SSO login

3. Provide eBS username and password after the above step (2)

User will login to eBS successfully and see their responsibilities.

4. Click LogoutUser will be logged out successfully

5. Login to eBusiness suite through

http://dwcp.dubaiworld.ae/oa_servlets/AppsLoginProvide the same user credentials that are specified in the step 2 in SSO login page.This time user will login successfully without prompting for the eBS username and password. You will see logged in user eBS responsibilities.

6. Create a user in eBusiness suite to use the link-on-the-fly option.

http://dwcp.dubaiworld.ae/OA_HTML/AppsLocalLogin.jspLogin as sysadmin and create the user with company name (DW) appending. Assign a role to the user.User created in eBS with a role.

7. Login to windows desktop using any user synced from AD to OID and access eBusiness suite through

http://dwcp.dubaiworld.ae/oa_servlets/AppsLoginClick on LoginUser will be prompted for eBS username and password after successful SSO login

8. Provide eBS username and password after the above step

User will login to eBS successfully and see their responsibilities.

9. Click LogoutUser will be logged out successfully

10. Login to eBusiness suite again through

http://dwcp.dubaiworld.ae/oa_servlets/AppsLoginThis time user will login successfully without prompting for the eBS username and password. You will see logged in user eBS responsibilities.

Open And Closed Issues For This Deliverable

Note: Add open issues that you identify while writing or reviewing this document to the open issues section. As you resolve issues, move them to the closed issues section and keep the issue ID the same. Include an explanation of the resolution.

When this deliverable is complete, any open issues should be transferred to the project- or process-level Risk and Issue Log (PJM.CR.050) and managed using a project level Risk and Issue Form (PJM.CR.050). In addition, the open items should remain in the open issues section of this deliverable, but flagged in the resolution column as being transferred.

Open Issues

IDIssueResolutionResponsibilityTarget DateImpact Date

Closed Issues

IDIssueResolutionResponsibilityTarget DateImpact Date

Test Cases for Application Server components 2 If > 1 10 of 18 = - Sec1 17 iii 10 of 18 = - Sec1 17

Test CasesFile Ref: TCO PROD TE020 Testcases_Draft1A.doc

tco prod te020 testcases_draft1a

Documents