150 likes | 252 Views
High level overview of HUB upgrade and market release strategy June 2010. Two Versions of the MPCC MPCC 15.1 (existing test W2000 machine, but with Schema 8 installed on it) MPCC 16.0 (new W2003/XP machine with schema 8). IPT Process. IPT Strategy.
E N D
High level overview of HUB upgrade and market release strategy June 2010
Two Versions of the MPCC • MPCC 15.1 (existing test W2000 machine, but with Schema 8 installed on it) • MPCC 16.0 (new W2003/XP machine with schema 8)
IPT Strategy • To replicate the to-be situation, at least one MP is required to run IPT using MPCC 15.1 and, at the same time, at least one will use MPCC 16.0 This is a change to the process that was briefed at the November IGG
Schema Release • March 19th. Dispatch upgraded schema 8 and two CDs to each MP. • CD1 MPCC 15.1 • CD2 MPCC 16.0
By Thursday June 24th - Formal go/no-go confirmation from CER • Friday June 25th • 13.00 - Confirmation from RMDS • 18.00* - Market Participants are asked not to send in any Market Messages after this point • Saturday June 26th • Morning* - Application of changes • Afternoon* - Connectivity testing • All communications will be via RMDS over the cutover weekend * Times subject to validation through dress rehearsals
Hub Upgrade • Go/No-Go Decision prior to weekend • Hub Upgrade will precede the Market Release • Planned to involve TSO and MP1 in testing the hub upgrade • Therefore will require rollback plans for both their backend systems • On success, apply SAP transports to Central Market System – point of no return
Market Release • Consists of SAP IS-U transports, RMP Extranet changes and MPCC 15.1 upgrade • Any issues with the Market Release will be addressed through fixing forward i.e. application of corrective transport
MPCC 16.0 upgrade • Fallback is to switch production IP back to MPCC 15.1 in the event of a problem with MPCC 16.0