gemini re-platforming project user readiness testing overview june 2012
DESCRIPTION
Gemini Re-platforming Project User Readiness Testing Overview June 2012. Introduction. - PowerPoint PPT PresentationTRANSCRIPT
Gemini Re-platforming ProjectUser Readiness Testing Overview
June 2012
The purpose of this presentation is to provide recommendations to Gemini System External Users on areas to test when participating in GRP User Readiness Testing including technical guidance on how to amend the command file on User’s API Clients as discussed at the May UKLC.
Introduction
External User Testing & Cutover Plan
Build Preparation
OCT NOV DECJAN2012
FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DECJAN2013
FEB MAR APR MAY JUN JUL AUG SEP
K E Y
WinterPeriod
Confidence
Start-up
Infrastructure Build & OAT1
Evn. Build Prep.
Environment Build
App. Porting
UT Prep.
Application Porting & Unit Test
System TestingST
Prep.
System Integration Testing
SIT Prep.
Perf.Test
PT Prep.
OAT2OAT2
RecommendedReadinessTesting
Recommended Readiness Testing Preparation
User Acceptance TestingUAT Prep.
Implementation Planning Dress RehearsalsCO
Early Life Support12 wks
Recommended External User Testing
GRP/IAP Project Activities
CO
CutoverPreparation
OptionalFunctionalTesting
Optional External User Testing
Optional Functional Testing Preparation
Recommended readiness testing required for validating External User connectivity to upgraded Gemini infrastructure.
Optional functional testing to provide additional assurances of no functional change within Gemini (Registration of participation required).
Cutover to upgraded Gemini.
Plan and implement necessary changes required for readiness testing. Plan and prepare business users for readiness testing.
External User Test Requirements
GRP is replacing technology not re-writing the application; the Gemini service will be unchanged, system functionality will remain ‘as is’ and the look and feel of screens will remain the same.
The GRP Project Team have conducted extensive testing of the new Gemini design through Build, System Testing and comprehensive User Acceptance Testing is planned for a period of 3 months starting late August 2012.
Gemini functionality is known to be unaffected. As consequence of the infrastructure upgrade and relocation to Xoserve’s data centres, it is recommended that all external users participate in the readiness testing stage of the project.
Recommended Readiness Tests External Users will be required to make minor amendments to a
command file on their API Clients to enable connection to the re-platformed system (refer to Appendix 1) and further changes will be required to establish connectivity to the new Gemini environment (refer to Appendix 2)
Xoserve recommends all External Users to perform the following tests during Readiness Testing (test cases shall be provided):1. On-line screen access and printout
2. API connectivity and run
3. File transfer
4. IX and XP1 connectivity
5. Connection to legacy Gemini and re-platformed Gemini
Optional Functional Tests
• Gemini functionality is known to be unaffected, therefore there is no requirement for External Users to conduct Gemini functionality testing.
• GRP will provide support to registered external users wishing to conduct optional functional tests to gain additional assurance and confidence.
• Optional Functional Testing is planned from 21st January 2013 – 1st March 2013.
External User Testing Registration
• Xoserve welcomes External Users working with the GRP Project Team to define a range of tests to be performed during Readiness Testing.
• Users are invited to register their participation in Readiness Testing by contacting .box.xoserve.GRPcommunications.com by 1st September 2012.
• Users requiring additional assurances and wish to participate in Optional Functional Testing are invited to discuss and register their participation by contacting .box.xoserve.GRPcommunications.com by 1st August 2012.
Next Steps
GRP will provide an update at the UK Link Committee every month until Post Implementation Support is complete. The current schedule of GRP topics for discussion is as follows:
July 2012 – Implementation Cut-over (initial discussions) August 2012 – Implementation Cut-over (commencement of
approval process)
If you have queries, please contact Andy Earnshaw on 0121 623 2820 or Andrew Boyton on 0121 623 2363.
Appendix 1 Amendments on API Clients
In preparation for User Readiness Testing and Implementation, amendments to the command file on API Clients need to be made
• All existing URL references shall be replaced with geminints.com for production access (see examples below):
• Java Client .bat file or windows shortcut example:java exit.api.client.Invoker -user API100 -password ******** -url URLREF -schemaUrl URLREF
• VB API (header) Client example:Set objXMLHTTP = New msxml.XMLHTTPRequeststrAPIUrl = “URL REF port>/<API_URL>“
Appendix 2Readiness Testing Changes
During the Readiness Testing Preparation stage of the project the following changes will need to be made. Further details will be provided in the Gemini Readiness Connectivity Guide.
Network• New firewall rules to allow secure access to Gemini Production,
Disaster Recovery and Shipper Trials environments. • Network and IP address routing to establish network links between
the external site and the Gemini Service.• DNS settings to resolve URLs and IP address.
User P/C’s• Creation of shortcuts and icons• Citrix client installation on all User P/C’s for remote on-line access• Deployment of developed APIs to all User P/C’s