170 likes | 496 Views
HP Integrity Migration - Just do IT. Stockholm. Oslo. Copenhagen. London. Kiev. CEKAB - a subsidiary of EDB. EDB acquired CEKAB in May 2007 CEKAB corner stone in processing & switching CEKAB provides POS&ATM terminal operator, acquiring, switching and issuing services
E N D
HP Integrity Migration - Just do IT
Stockholm Oslo Copenhagen London Kiev CEKAB - a subsidiary ofEDB • EDB acquired CEKAB in May 2007 • CEKAB corner stone in processing & switching • CEKAB provides POS&ATM terminal operator, acquiring, switching and issuing services • Over a billion transactions per year on HP Integrity, BASE24, and our own batch system
Stockholm Oslo Copenhagen London Kiev EDB - who are we? • EDB - Nordic leadership • No 1 in Norway and No 5 in Sweden • No 2 in Outsourcing in Nordic countries • No 1 in Bank solutions in Nordics • 5,200 employees in three business areas • IT Operations • Solutions • Application Services
Background to migration • Continuously growing business • Dual site decision - 24/7/365 is the reality • CEKAB has used Tandem and BASE24 since 1986 • Reliable hardware, software and vendors • Strategic decision to continue co-operation in a 24/7/365 world • Invest in the future, • not in old technology • each machine handles peak transaction throughput
The Dual Site project • Purchase three HP Integrity 16000,2 for Production and 1 for Test • Find two new sites – at least 10 km apart • Set-up communication backbone • Migrate from S to I • Move applications across • Install Golden Gate • Move Atalla boxes & Windows servers • Go-live
Dual Site solution – first draft Site Primary Site Secondary > 10 km GoldenGate Replication Redundant Fibre Backbone CEKAB office
Remember K to S migration? Huge infrastructure changes, everything had to be touched Migration from Sages to SWAN-boxes No support of X.21 CISC to RISC processor We feared RISC to EPIC would be like CISC to RISC CEKAB was on BASE24 V6.4 and ACI had tested HP Integrity on V6.5 Long down-time to move CAFs across Testing communication is difficult in test environment Start up from PC We didn’t want to be first What we feared prior to the project?
Was it plug & play? • Hardware migration was a piece of cake • S => I is a small technology step compared to K => S • “Only” a switch to a new powerful processor • New accelerator worked well • Excellent support from HP • Skilled personnel • Great assistance • System met our expectations
Go-live night was a success • CEKAB was first in the world to migrate Base24 from S to I • Early to run Connect:Direct and MQ on HP Integrity • Go-live was successful, up and running after 1 hour and 17 minutes. • Golden Gate replication from old to new machine minimized the outage • HW worked fine • Communication controllers worked fine • 3rd party SW worked fine • Own batch system worked fine • But we are all humans – especially at 5 AM…
What went wrong at go-live? • Cables had been incorrectly labeled • Format2 • ZIP program for Format2 files failed • A few homegrown utilities did not work with Format2 or had not been upgraded • Batch programs • A few batch programs did not use CPU0-3 • Some had been moved across, but not recompiled • Forgot to warm-boot change of X.25 address
What went wrong during the project? • Communication • Too few Ethernet controllers ordered • Telco reluctant to install TokenRing at new sites. • Saved by IBM!- stopped supporting FEPs • SNASW (SNA/IP) replaced SNA/TokenRing • 2 fiber interfaces in core-switches failed, detected weeks before go-live! • Batch programs – became a problem • Could not move COBOL programs across, had to be accelerated with new accelerator, OCA. Unforeseen tests as a result • Recompile Cobol programs once more when High Pin had to be used
What we had not counted for? • Miscellaneous • Debugger did not work with Format2 • Switch from Inspect to Visual inspect • Long time to get a fix for MQ • Insufficient experience of 3rd party programs • Internal view – it is an technical project • OS upgrade three times, from H06.04 to H06.07
What we did not do? • CEKAB did not follow recommendations to upgrade current OS version to G06.27 on the S-machine before moving software across to HP Integrity. • This was abandon, due to cost and time constraints. • It turned out well
After go-live experiences • Customers perceived go-live as a success and were impressed by the short down-time • HP Integrity will last many years, CPU utilization is still low • Java works better than before • Batch file creation and delivery is faster. • File creation is faster due to rapid I/O and powerful CPUs • File delivery time has decreased substantially due to the communication hardware upgrade
So far each go-live has been a success • November 5th, 2006 live on HP Integrity • February 2007 2nd HP Integrity in production and GG Warm Stand-by • April 2007 GG Hot Stand-by • Sep 16th, 2007, new version of GG and go-live of active-active with D24 • Nov 5th first live traffic in secondary machine
Conclusions • CEKAB was first in the world to migrate Base24 from S to I • Go-live was successful, up and running after 1 hour and 17 minutes • Much easier migration than K to S • Nothing to be afraid of – almost plug & play • We would to it again…
Questions Tommy Johanssontommy.johansson@cekab.se www.cekab.se “HP was the obvious partner. We have a long history of working with HP, so it was a safe choice for us. We trust the people and the hardware is extremely reliable.”Sissel Johnsen, Manager of production and operations, CEKAB