1. HP Integrity Migration - Just do IT

2. CEKAB - a subsidiary of EDB nEDB acquired CEKAB in May 2007 nCEKAB corner stone in processing & switching nCEKAB provides POS&ATM terminal operator, acquiring, switching and issuing services nOver a billion transactions per year on HP Integrity, BASE24, and our own batch system Oslo Stockholm Copenhagen London Kiev

3. EDB - who are we? nEDB - 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 n5,200 employees in three business areas –IT Operations –Solutions –Application Services Oslo Stockholm Copenhagen London Kiev

4. Background to migration nContinuously growing business nDual 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 nInvest in the future, –not in old technology –each machine handles peak transaction throughput

5. The Dual Site project nPurchase three HP Integrity 16000, 2 for Production and 1 for Test nFind two new sites – at least 10 km apart nSet-up communication backbone nMigrate from S to I nMove applications across nInstall Golden Gate nMove Atalla boxes & Windows servers nGo-live

6. Dual Site solution – first draft CEKAB office Site Secondary Site Primary GoldenGate Replication Redundant Fibre Backbone > 10 km

7. What we feared prior to the project? nRemember 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 nWe 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

8. Was it plug & play? nHardware 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 nNew accelerator worked well nExcellent support from HP –Skilled personnel –Great assistance nSystem met our expectations

9. Go-live night was a success nCEKAB was first in the world to migrate Base24 from S to I nEarly to run Connect:Direct and MQ on HP Integrity nGo-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…

10. What went wrong at go-live? nCables had been incorrectly labeled nFormat2 –ZIP program for Format2 files failed –A few homegrown utilities did not work with Format2 or had not been upgraded nBatch programs –A few batch programs did not use CPU0-3 –Some had been moved across, but not recompiled nForgot to warm-boot change of X.25 address

11. What went wrong during the project? nCommunication –Too few Ethernet controllers ordered –Telco reluctant to install TokenRing at new sites. l Saved by IBM!- stopped supporting FEPs l SNASW (SNA/IP) replaced SNA/TokenRing –2 fiber interfaces in core-switches failed, detected weeks before go-live! nBatch 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

12. What we had not counted for? nMiscellaneous –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

13. What we did not do? nCEKAB 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

14. After go-live experiences nCustomers perceived go-live as a success and were impressed by the short down-time nHP Integrity will last many years, CPU utilization is still low nJava works better than before nBatch 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

15. So far each go-live has been a success nNovember 5 th, 2006 live on HP Integrity nFebruary 2007 2nd HP Integrity in production and GG Warm Stand-by nApril 2007 GG Hot Stand-by nSep 16 th, 2007, new version of GG and go-live of active-active with D24 nNov 5th first live traffic in secondary machine

16. Conclusions nCEKAB was first in the world to migrate Base24 from S to I nGo-live was successful, up and running after 1 hour and 17 minutes nMuch easier migration than K to S nNothing to be afraid of – almost plug & play nWe would to it again…

17. Questions Tommy Johansson tommy.johansson@cekab.se tommy.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