Attach 15.doc

Attachment 15 – Section J

PDPS Migration Acceptance Testing

The PDPS Application Support Team will perform the following migration acceptance tests with support from the vendor.

T1: The AAMVAnet™-PDPS link verification

This verification involves the network connectivity between the AAMVAnet™ network and the vendor’s network infrastructure. A stable connection between these components is expected with maximum data flow at the rate of 1.5Mbps.

Acceptance criteria: The connectivity should be stable with maximum speed of 1.5Mbps.

T2: Internal Network Connectivity/speed verification

Ensure the stability and the speed of the connections between the load balancer, physical servers, virtual application servers and SAN.

Acceptance criteria: The vendor’s internal network speed should be 1 Gbps/sec or more.

T3: SAN Verification

Acceptance criteria: Verify that the SAN is properly installed and configured for different servers. Make sure that SAN allocated to the database is accessible from the both database servers. Also the ‘local’ SAN allocated is accessible only from the required server. Verify the SAN allocation for the application servers.

T4: SAN Replication

Acceptance criteria: Ensure the proper replication of the SAN to the Disaster Recovery (DR) site.

T5: RAC verification

Acceptance criteria: Verify that the RAC is installed properly and configured to manage both database instances. Test the fail-over scenarios.

T6: Database Server Verification

Ensure that the installations on the database server are complete and correct including but not limited to the following:

· Unix installation with the required patch.

· User accounts setup.

· File permissions setup.

· NTP Server (for time synchronization) installation and configuration.

· Oracle 11g R2 installation

· Oracle listener configuration.

· OC4J installation

· APEX configuration.

· Oracle database instance creation and data migration.

Acceptance criteria: The OS is installed properly with the correct configuration of the memory, users, directory structures and permissions, Oracle installation/configuration and database migration.

T7: Tablespaces verification

Ensure that the number of tablespaces match the number of tablespaces in the current database. Also verify the size, objects and permissions of the tablespaces.

Acceptance criteria: The total number of tablespaces, size, permissions, and number of objects in the migrated database should match the current database.

T8: FTP testing

Acceptance criteria: Check that all of the FTP/SFTP configurations are setup properly in the new system; including the permissions for the application user account to read/write to the transferred files. Verify that the files can be transferred using FTP or SFTP between the states and PDPS. Also verify that the FileDetector (job that processes the files submitted by States) can process these files successfully.

T9: Stress tests/load tests

The PDPS application load test will be conducted by simulating the production loading conditions. The interactive message processing response is expected to be with in 2 seconds.

Acceptance criteria: The PDPS application should perform within the acceptable performance levels as indicated above.

T10: App Server Verification

Verify that the all the installations on the application server are complete and correct including but not limited to the following:

· Unix installation with the required patch.

· NTP installation and configuration.

· WebLogic Server installation/configuration.

· Oracle client installation.

· OS user verification.

· Files verification.

· Permissions verification.

Acceptance criteria: The OS should be properly installed with the configuration of the memory, users, directory structures and permissions as required in the Section C.3.3.2.

T11: Load Balancer testing

Acceptance criteria: Ensure that the load balancer distributes the HTTP requests evenly across the two application servers. Also test the incoming FTP connections to the primary database server, and also the transfer of FTP files to the secondary database Server upon unavailability of the primary database server.

T12: Failover testing

Acceptance criteria: The application is tested for continued operation under the following scenarios:

· Application server 1 is down and all other servers are up and running.

· Application server 2 is down and all other servers are up and running.

· Database server 1 is down and all other servers are up and running.

· Database server 2 is down and all other servers are up and running.

· Application server 1 and Database Server 1 are down and all other servers are up and running.

· Application server 1 and Database Server 2 are down and all other servers are up and running.

· Application server 2 and Database Server 1 are down and all other servers are up and running.

· Application server 2 and Database Server 2 are down and all other servers are up and running.

T13: APEX Verification

Acceptance criteria: Verify the APEX installation. Ensure that all PDPS UI Apex pages are accessible and are working correctly. Test the reports printing functionality.

T14: Test Database Server Verification

Acceptance criteria: Ensure all test databases are installed and configured correctly and data is migrated from the existing instances. Verify the clustered database configuration, UNIX accounts, files and permissions on the test servers as required in the Section C.3.3.1.

T15: Development Apex Verification

Acceptance criteria: Verify the development APEX installation. Ensure all UI Apex pages are accessible and are working correctly. Test the reports’ printing functionality.

T16: PDPS Application Testing

Acceptance criteria: Test all PDPS functions including but not limited to the following.

· Interactive Message Processing

· Batch Message Processing

· Daily Batch Process

· Hourly scheduled jobs

· Weekly scheduled jobs

· Delayed Search Process

· File Detector

· Data Purge Process

· Clean File Process

· Reports Generation

· Emails Process

· Apex Application

· Database monitoring scripts

T17: Help Desk Application testing

Acceptance criteria: Test the functionality of the Help Desk Application (HDA). Test the application and Apex (GUI) including, but not limited to the following features.

· Interactive Message Processing

· Batch Message Processing

· Daily batch process

· Hourly scheduled jobs

· Weekly scheduled jobs

· Data Purge process

· Reports generation

· Emails process

· Apex application

· Database monitoring scripts

T18: Windows testing -- users, permissions, CVS, Toad, Request Tracker, DOORS Acceptance criteria: Make sure that these tools are installed properly and data/users are migrated as stated in the Section C.3.2.3.