1 / 10

Gemini Re-platforming Project User Readiness Testing Overview June 2012

Gemini Re-platforming Project User Readiness Testing Overview June 2012. Introduction.

ahmed-freeman
Download Presentation

Gemini Re-platforming Project User Readiness Testing Overview June 2012

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Gemini Re-platforming ProjectUser Readiness Testing OverviewJune 2012

  2. Introduction 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.

  3. External User Testing & Cutover Plan

  4. 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.

  5. 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): • On-line screen access and printout • API connectivity and run • File transfer • IX and XP1 connectivity • Connection to legacy Gemini and re-platformed Gemini

  6. 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.

  7. 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.

  8. 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.

  9. 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.XMLHTTPRequest • strAPIUrl = “URL REF port>/<API_URL>“

  10. 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

More Related