all presentation
TRANSCRIPT
etiSafoG
577MBI
T24 ArchitectureProduction Site
Channels LayerBranch Internet Mobile ATM/POS
ECX ATS SWIFT Reuters
Web Layer
Connectivity Layer
T24 Application Layer
Database Layer
Data Center:- Production Site
IBM Power 795 IBM Power 775
250 RAM32 core process
29 TB
Shared StorageIBM System Storage DS8800
End User
W eb Brow sersMozilla Firefox Microsoft Internet Explorer
Google Chrome
Opera Apple Safari
Devices
OS
W eb Layer
Technology Configuration
IBM W ebSphere Edge Server
IBM's Network DispatcherLoad balancingFailover clusters, or HA clusters
Advisors:-Determine the "best" HTTP server
High Availability:-heartbeats
No Single points of failure
IBM WebSphere W ebSphere Application Server(W AS)
IBM HTTP ServerApplication ServerHosting the Java application4 IHS Servers2 Profiles per/server200 sessions @ a time180 seconds timeoutPrimary OnlyRouting is based on weights
T24 Browser Servlet
T24 BrowserTC Client
8 Instances of TC Client
W eb Layer
Backup Server 10.1.6.18 Primary Server
P
http://10.1.6.18:9095/PROD//servlet/Brow serServlet
Clustered
IBM Web-Sphere Application Server(WAS)
Home for login pages
P P P P
Connectivity Layer
Technology
IBM WebSphere MQ (Message Queue)Guaranteed message delivery from the T24browser/TC Client to TC Server
Configuration
M ulti-instance queue m anagers;One queue m anger per/server
REQUEST.QUEUEREPLY.QUEUE
A B A B A B A B
OUT IN OUT IN
Connectivity LayerWAS with 8 TC Client profiles
P P
MQ Servers
T24 Application Layer
Technology
TAFC:-providing an environment to execute programsTCServer:- the listener of T24 from the outside worldT24 Binaries:- T24 applicationOracle ClientDirect Connect Driver Oracle (DCD)50 session per/serverConfigured to MQTCServer timeout 60 seconds
Configuration
Two T24 Application Servers5 TCServer instancesSWIFTReutersECX (Local Clearing)ATS (Local Clearing)ATM and POSARC-IB (Internet)ARC-MOBILEGX-ReportAlert (CORBAN)
T24 Application Layer
MQ Manager 12 MQ Manager 15
TCServer 10 TCServer 14
XM L Brow ser <---> OFS
tSS ---> Posting Transaction
P PClassic access to T24T24 OperationsCOB initiation and m onitoringJshell Access:- Explicit DB access
Jshell Access Jshell Access
Database Layer
Technology
Oracle Database 11gReal Application Cluster (RAC)Enterprise ConsoleActive sync
Database Layer
ECX (Ethiopian Commodity Exchange ) Interface
ATM Interface
SWIFT Interface
2
3
4
Migration Overview• Data migration is the process of transferring data betweenstorage types, formats, or computer systems.
• It is a key element to consider when adopting any newsystem .
• It is usually performed programmatically to achieve anautomated migration , freeing up human resources fromtedious tasks.
• Why Data migration required? When organizations or individuals change computersystems or upgrade to new systems, or when systemsmerge.
Commercial Bank of Ethiopia Page 1
Data Migration Phases• Before deployment of new system data m igration gothrough phases which are commonly repeated severaltimes. The phases are: Design Extraction Cleansing Load Verification
Commercial Bank of Ethiopia Page 2
The way forward … Then• To achieve an effective data m igration the team followedan E (T) L process
• E (T) L processExtract, Transform and LoadExtract from the legacy systemTransform it to the desired goalLoad it to specific environment
Commercial Bank of Ethiopia Page 3
Extract• Definition of where actual data exists• Determ ination of how the data in the system are stored(i.e. flat files, files, or tables)
• data is read from the old system• Extraction of needed data from their respective repository.
Commercial Bank of Ethiopia Page 4
Transform• Data mapping between the source and target structure• Mapping included referring to documentation thatspecifically identifies fields from the legacy system mappedto fields in the new system
• Developing our own M igration Conversion Tool• Developed using M icrosoft Visual Studio, C#programming language
• Necessary translation of data or data cleansing done• To improve data quality automated and manual datacleaning was commonly performed
• Obsolete or redundant information elim inated inorder to match the requirements of the new system .
• In general, the data cleansing process manipulates,or cleans, the legacy data so it conforms to the newsystem 's requirements
Commercial Bank of Ethiopia Page 5
Load• Determ ination of on which environment to load• Environment prerequisite check
• Availability of user ID with necessary privileges• Availability of M igration tools (Mapping Definitionsand services)
• Existence of System Parameters• Moving the transformed (Readymade) data to the to beloaded environment
• Loading the readymade data within the given time frametable
Commercial Bank of Ethiopia Page 6
Commercial Bank of Ethiopia Page 7
Challenges• Data Volume• Data Quality• Data Completeness• Frequent Business Requirement change• Given time frame table
Commercial Bank of Ethiopia Page 8
Migration Trials• Before GO-LIVE in order to make the M igrationConversion Tool perfect and to fam iliarize the teamwith M igration Conversion Tool, simulatedenvironments, and migration procedures more than 20migrations were done.
• The 20+ migrations were done on differentenvironments:UAT (User Acceptance Test) environmentsMigration environmentsBranch Dress Rehearsal environments
Commercial Bank of Ethiopia Page 9
Migration Summary Post GO-LIVE
• More than 25,000,000 Records M igratedCommercial Bank of Ethiopia Page 10