Documente Academic
Documente Profesional
Documente Cultură
INTEGRATION – DATA
PUMPS
Mainframe
Database
1. Scheduled tasks run on Mainframe to extract data from the operational database
tables in CLASS and POSH and populate “staging” tables with a status flag.
Intermediary
Staging Datastore
(Mainframe)
2. Scheduled tasks (mostly crons) run on Java servers to read from the staging
tables, write to IMR and update staging table status flag. Also clean up old data.
Data Pump Primarily “Class Data Pump” and “ACL Datapump”.
(Non Mainframe)
3. Data is written into IMR (or Pega or other database). Further processes within
the estate carry out checks and processes. (MrACL2, WsGen)
IMR
1. Brokers still enter data via UI on the Mainframe into CLASS DB. It populates a “staging” table for copying data
2. The Data Pump is triggered to run and reads from the staging tables, into memory. It then inserts data into IMR DB
3. An ECF User checks the IMR and sees the “pumped” data.
4. 5. Users of other platforms (ECF2-CAS and the Xpresso Tablet App) also see the data on IMR
7 July, 2014 Xchanging Platform Refresh Programme © 2014 Xchanging Ltd 3
Data Pumps – Typical Flow Start
Initialisation
This is the process of the simple Main Loop – while bRunning flag TRUE and retryCount < retryMax
The rewrite will combine the two Iterate over the linkedHashList
into one process with better retry Reset
Is the
DB record locked
for processing
If
bRunning Shut
Sleep for set delay
(more to down
do)
Admin
combined to run in conjunction
New WorkspaceDTO
Group exists
processTransaction
validateTransaction
with the class data pump which
identifies new claims in the first createPolicy workspace if not found
processCmrRequestQueue
CmrRequestQueue lockQueue
processEach Req Req Req
Request
To commence development a single Linux VM with 2G RAM requires access to the two databases
Connectivity to the CMS API for WsGen can be stubbed initially.
CASA Mainframe B
P
CDW U
R
F Company DDF ATTUNITY CDW
O L Class S
C A XCS Class
CDC ODS I
E M FAC XOL CLASS
S E and TREATY ETL N
S C BATCH CDW E
ENQUIRY
P I other PROCESS ADS S
R C Settlement
S
VTAM LINK
O S Security
C Reference POSH SDW O
E
S
ETL B
SHARED
S
W LORS VOLUME J
P A
LORS E
R L LIDS SDW SDW C
O N ODS ADS
C U
LIDS BATCH T
E ENQUIRY
T PROCSS S
S
S C Settlement other BRIO
I Security
C Reference
S CICS WEB DDF BRIO
TDW
Web
Account Premium Data Multiple times a day PROCESS
Enquiry
Claims Data Once a day
PROCESS
Other Data
ALL CORE SYSTEMS
Attunity would then become a “Tolerate” interface for the foreseeable future
CICS Web should be investigated further as a more standard, lightweight integration method with all
integration to be routed via the Fuse ESB
We also need to prove that CICS Web can be used to invoke REST services on Fuse ESB
We should see if CICS Web can be implemented on Flame (currently it is only on Walnut)
We can look at meeting the ECF requirements for calling non-Mainframe services from the MF
Can the CICS transactions that are currently wrapped by Attunity be called via CICS Web instead?
Media formats could be extended from standard XML or JSON to include Text (i.e. EDI-style messages)
O S Security
C Reference POSH SDW O
E
S
ETL B
SHARED
S
W LORS VOLUME J
P A
LORS E
R L LIDS SDW SDW C
O N ODS ADS
C U
LIDS BATCH T
E ENQUIRY
T PROCSS S
S
S C Settlement other BRIO
I Security
C Reference
S CICS WEB DDF BRIO
TDW
Web
Account Premium Data Multiple times a day PROCESS
Enquiry
Claims Data Once a day
PROCESS
Other Data
ALL CORE SYSTEMS
Combine Class data pump, WsGen, ACL and MRACL2 into a single camel route rather than four separate jobs. I
have termed this a “Data Pipeline” to distinguish it from data pumps. Note that each component service is
loosely-coupled and reusable, especially important for the CMIS service to create workspace, folders, etc
7 July, 2014 Xchanging Platform Refresh Programme © 2014 Xchanging Ltd 11
Data Pumps Roadmap