Date post: | 11-Jun-2015 |
Category: |
Technology |
Upload: | jefpear |
View: | 50 times |
Download: | 1 times |
IMS in the Connected WorldWhy You Should Pay Attention!
Dusty Rivers
GT Software
March 11, 2014
Session 14778
6/19/2014 2
IMS
IMS systems for banks
(ATM, loans,
account management)
IMS systems for insurance
(Claims &
policy management)
IMS systems for
manufacturing
IMS systems for finance IMS systems for medical
IMS is the system of record
• 75% of Fortune 1000 companies use IMS
• Thousands of companies globally use IMS
• Most users are not aware that information on their applications come from IMS
IMS and Fortune companies
IMS and architects
The very reliability and transparency of IMS systems can make it nearly invisible to architects.
• Not using IMS to the fullest advantage
• They are not aware they can integrate new technology with IMS data and transactions.
• They may recommend other options, not knowing they can integrate without changing the underlying IMS applications
IMS roadblocks(perceived!)
• IMS is not agile
• Multiple systems and interfaces
• Integration will be a challenge
• Legacy Data
• “IMS is Old”
Today’s business needs
• Web self-service, mobile/cloud, BYOD
• Real-time access to enterprise data residing on any platform
• Integrated views of related information
• Customer and business focused IT
• Build and deploy apps rapidly
• Industry standards
• Integration between Mainframe & distributed systems
• Common tools & skills
• Big Data????
IMS modernization
Modernization Scenarios:
• Using IMS data via ODBC/JDBC/Web Services
• Using existing IMS transactions (business logic)
• Using conversational IMS transactions
• Using combinations of both
• Using IMS in conjunction with distributed systems
• Using IMS as a Client(*)
• IMS Database Manager (DB)
• IMS Transaction Manager (TM)
Good questions
• Can I get IMS data for use in the new systems?
• Can I get IMS transactions easily incorporated into the new systems?
• What about the others (CICS, IDMS/DC, IDEAL, NATURAL, etc.?)
Today’s IT Challenge
Enable IMS and distributed environments
to seamlessly interact via industry standards to enable
strategic state-of-the-art business applications
Ivory® Service Architect™
• Rapid
• Lightweight development tools
• No coding or code generation
• Proven
• Banking, Insurance, Manufacturing
• Thousands of services, millions of transactions
• Service Enable IMS transactions
• Including support for IMS conversational
• Support for MFS as service definition
• LTERM name if needed
• Composite service support
• MFS Mod 3
• Variable Length/Multiple Segment Output(*)
• Outbound Support to any remote system(*)
• Multiple Protocol Support (out of the Box)
• SOAP support for IMS
• REST support for IMS
• JSON support
• Message “chunking”
IMS & Ivory® Service Architect
Input
13
Input
Output
14
Trancode(IVTNO)
Input
Output
(LL,ZZ,Trancode,DATA)
Intput
REST and SOAP(Web Services)
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:s0="urn:ims2TNS">
<soap:Body>
<s0:getInfo>
<s0:inCommand>display</s0:inCommand>
<s0:inLastName>smith</s0:inLastName>
</s0:getInfo>
</soap:Body>
</soap:Envelope
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns1="urn:ims2TNS">
<soap:Body>
<getInfoResponse xmlns="urn:ims2TNS">
<outDataType>
<outLastName>SMITH</outLastName>
<outFirstName>MARY</outFirstName>
<outExtension>265</outExtension>
<outZipCode>30022</outZipCode>
</outDataType>
</getInfoResponse>
</soap:Body>
</soap:Envelope>
<?xml version="1.0" encoding="utf-8" ?>
- <getinfoResponse>
- <outDataType>
<outLastName>SMITH</outLastName>
<outFirstName>MARY</outFirstName>
<outExtension>265</outExtension>
<outZipCode>30022</outZipCode>
</outDataType>
</getinfoResponse
http://gtzdev.gtsoftware.com:20180/soap/ims2?RESTRequest=getinfo
&inCommand=display&inLastName=smith
SOAP REST
Input
Output
IMS interfaces
*
IMS interfaces
IvoryServer
Mainframe
Windows, Linux
SOAP/REST/JSON/JCAHTTP or MQ Requestor /
Provider
Requestor
IMSControlRegion
OTMA
IMS
Connect
IMSConnect
z/OS
Linux on Z
IMS Connect
IMS DB
Ivory Server
IvoryServer
IvoryServer
IvoryServer
Ivory®Data Hub™
Ivory runtime architecture
Mainframe
DB2 IMS/DB VSAM ADABAS IDMS/DB CA/DB
ODBC/JDBCSOAP/REST,JSON, JCA
Applications Web Services
Integrating Mainframe data
MobileBanking, Agents
WebStock trading,
Self-service, Portals
Packaged ApplicationsCRM, SAP, Oracle, Billing
Mainframe integration challenges
IMS
• New Mainframe applications leveraging standards
Use standards
• New services can leverage industry
standards (IFX, SWIFT, ACORD, etc.)
• Applications can use company specified
standards and mappings (XSD’s, WSDL)
• Services can easily be mapped in Ivory®
Studio that will handle difficult data types.
• No coding or code generated
• Rapid iteration gets the job done
• One click deployment
• Deployed to Mainframe (CICS, Started task, z/Linux) or off-platform(Windows or Linux)
• Leverages z/Linux and specialty engines to slash costs
At the speed of the customer
• IMS can easily be used as a client
• IMS applications can interface with new applications with knowing SOAP or XML
• No new software needed
• IMS can rapidly call distributed systems
Summary
IMS systems for banks
(ATM, loans,
account management)
IMS systems for insurance
(Claims &
policy management)
IMS systems for
manufacturing
IMS systems for finance IMS systems for medical
IMS is the system of record
Their view of IMS !!!
IMS
Our view of IMS !!!
IMS