ims application modernization - ims ug may 2012 stockholm, helsinki
DESCRIPTION
TRANSCRIPT
© 2012 IBM Corporation
IMS Application Modernization
Kyle Charlet
STSM, IMS SOA and [email protected]
© 2012 IBM Corporation2
Agenda
IMS modernization overview
IMS database solutions
IMS transaction management solutions
DataPower and IMS connectivity
IMS TM application development
IMS TM connectivity
© 2012 IBM Corporation3
IMS Modernization Solutions
Java
IMS
z/OS
TCP/IP
WebSphereTM/DB access
IMS TM and DBResourceAdapters
DataPower
IMS SOAPGateway
TM access
Universal JDBCdriver
DB access
Universal DLIdriver
Java API
TM AccessRYO
C API
Web 2.0(Mashup Center)
Catalog
IMS access anywhereStandards-based data server and TMOpen systems accessWeb services
© 2012 IBM Corporation4
IMS Open Database
Solution statementExtend the reach of IMS data
– Offer scalable, distributed, and high-speed local access to IMS database resources
ValueBusiness growth
– Allow more flexibility in accessing IMS data to meet growth challenges
Market positioning– Allow IMS databases to be processed as a standards-based data server
Key differentiatorsStandards-based approach (Java Connector Architecture, JDBC, SQL, DRDA)
Solution packaged with IMS
Enables new application design frameworks and patternsJCA 1.5 (Java EE)
JDBC
© 2012 IBM Corporation5
IMS Open Database
DRDA over TCP/IP
DRDA over TCP/IP
z/OS
IMS
IMS
z/OS
Open Systems (e.g.; LUW)
JavaEE
JDBC
DLI
Universaldrivers DRDA over TCP/IP
Universaldrivers
JavaEE
DLI
JDBC
Direct
© 2012 IBM Corporation6
Solution highlights – JEE deployment
Universal DB resource adapter
JCA 1.5– XA transaction support
• Manage multiple datasource connections in a single UOW– Local transaction support
• Manage multiple datasource connections each in their own UOW– Connection pooling
• Pool released connections for future use– Connection sharing– Multiple programming models available
• JDBC (Universal JDBC driver incorporated)• CCI with SQL interactions• CCI with DLI interactions
© 2012 IBM Corporation7
Solution highlights – JDBC
Universal JDBC driver Significant enhancements to classic JDBC offered in IMS 9 and IMS 10
– Standardized SQL support– XA transaction support (type 4)– Local transaction support (type 4)– Concurrency control
• Control release of distributed locks– Updatable result set support– Batching support
• Fetch multiple rows in a single network call– JDBC metadata discovery support
Standard SQL and metadata discovery enables significant integration opportunities for IMS
© 2012 IBM Corporation8
Solution highlights – DLI
Universal DLI driver
– Java implementation of DL/I API
– Complete DL/I support for database access
– All IMS command codes supported
– Can mix usage of JDBC and DLI drivers in the same application• SQL cannot always express what DLI offers
© 2012 IBM Corporation9
Open Database and the Universal drivers
Deep synergy with the IMS catalog– Direct access to IMS metadata in the catalog– Virtual and cloud deployment capabilities
• No longer file-system dependent for metadata– Industry-leading data type support
• Complex and flexible– Mapping support
Deep synergy with Java z/OS and z196– Significant performance improvements– Continued partnership with Java z/OS lab
Continued SQL standardization and support– Including similar connection parameters as DB2 for commonality across IBM
drivers– More to come
Continued integration across the IBM portfolio
© 2012 IBM Corporation10
Data types
Data types have multiple metadata elements– Application data type
• Universal drivers use application data type to present data to clients– Physical data type
• Universal drivers use physical data type to marshal/unmarshal data to and from the database– Example
• Application data type is DECIMAL(10,2) [decimal with precision 10 and scale 2]• Physical data type is a signed packed decimal (AD community doesn’t need to know this)
New data type support– Structs (nested n levels with no constraint on element data types)
• Accessed via SQL and DLI– Arrays (nested n levels with no constraint on element data types)
• Accessed via SQL and DLI– User-defined
• Name of UDT can be defined to the catalog and intended to be used at runtime by Universal drivers to marshal/unmarshal data
• Can be part of a Struct or Array element
© 2012 IBM Corporation11
Maps
Mapping support– A Map is metadata that describes how a field (or set of fields) are mapped for a
particular segment instance– Metadata captures the various cases and for each case defines the set of fields
to be used for that case– Maps can be defined to the catalog– Example
•Insurance segment mapped multiple ways depending on value of a ‘Policy Type’ field
-----555 Disk Drive Way, 95141500K5Single FamilyH
Red2K1989EscortFord----M
ColorValueYearModelMakeAddressValueRoomsProperty TypePolicy Type
© 2012 IBM Corporation12
Additional enhancementsSQL
– FETCH FIRST <n> ROWS ONLY– INNER JOIN <table2> ON <table1.col1> = <table2.col2>
Connection properties– currentSchema– maxRows– fetchSize– Tracing
• traceFile, traceFileAppend, traceDirectory, traceLevel
Variable length segment support– VL segments contain a two byte length (LL) field that will identify the size of the
segment instance– Universal Drivers are now sensitive to the LL field of a VL segment and will manage the
IO area of the segment instance on all CRUD calls
© 2012 IBM Corporation13
IMS Open Database environment
LPAR Az/OS
IMS DBCTL
IMS
PC
Open Systems
UniversalDB
Resource Adapter
JCA
1.5
T
C
P
I
P
WebSphere
S
O
A
P
LPAR B
LPAR C
XCF
DRDA
IMS Connect
T
C
P
I
P
SCI
SCI
ODBA
ODBM
© 2012 IBM Corporation14
IMS Open Database environment
Universal DB
Resource adapter
J
C
A
1.5
T
C
P
I
P
WebSphere
S
O
A
P
LPAR Az/OS
Open Systems
LPAR C
IMS DBCTL
IMS
PCSCI
ODBA
DLI
JDBC
RYO DRDA Appl.
IMS DBCTL
IMS
PCSCI
ODBA
IMS Universal drivers
LPAR A
IMS DBCTL
IMS
PCSCI
ODBA
ODBM
IMS Connect
T
C
P
I
P
SCI
ODBM
ODBM
LPAR BXCF
WAS z/OS Universal DB
Resource adapter
J
C
A
1.5
T
C
P
I
P
ODBA
PCSCI
Traditional ODBA
DLI
JDBC
IMS Universal driversTraditional ODBA
JEE
Java SE
DRDA
© 2012 IBM Corporation15
IMS 12 catalog
Trusted IMS metadata information
Comprehensive view of IMS database metadata (including application metadata) managed by IMS with standard access patterns (JDBC/SQL)
Offers metadata discovery and exchange via IMS Open Database and the IMS Explorer for Application Development
Scalable Open Database solution – large scale deployment into virtualized production and test environments
Enables broad IMS integration into the IBM and non-IBM portfolio of tools (OptimDevelopment Studio, Rational Asset Analyzer, InfoSphere Data Architect, etc)
ACBLIB
Catalog
PSBsource PSBLIB
DBDsource DBDLIB
PSBGEN
DBDGEN
ACBGENIMS Explorer
IMS
© 2012 IBM Corporation16
IMS catalog – intended support
PSBLIB
Catalog
• IMS DB changes start with catalog• IMS loads resource information from catalog• ACBLIB/PSBLIB/DBDLIB updates will be the by-product of catalog updates
• Tools that use these libraries can continue to operate, but should migrate to catalog
• PSB and DBD source can still be optionally generated from PSBLIB and DBDLIB
IMS ExplorerDDL
ACBLIB
DBDLIB
PSBsource
DBDsource
IMS
© 2012 IBM Corporation17
Dynamic database - Data Definition Language
SQL incorporates DDL to modify the schema of a databaseAuthoring DDL is straight-forward with sophisticated tooling support in the industrySQL/DDL can be used to update/add metadata in the catalog without the need of a GEN
–Directly update the catalogIMS can be notified of such an update and load the new definitionsIt is our intention to offer this type of dynamic definition for IMS
© 2012 IBM Corporation18IMS
ISPF
IMS Explorer for Administration(Web Browser)
AdministratorsDevelopers
IMS Explorer for Development(Eclipse)
IMS Modernization
© 2012 IBM Corporation19
IMS Explorer for Development
© 2012 IBM Corporation20
IMS Explorer For Development
© 2012 IBM Corporation21
IMS Explorer
• Catalog integration• zExplorer
integration• Advanced data type
support
• Logical & physical modeling
• Resource discovery• Model sharing
InfoSphere DataArchitect
Database Modeling & Creation
• Data privacy• Data management
Optim Designer
Governance
• Operational BI• Extending value of
IMS data
Cognos 10 BI
Analytics
Data Studio
• SQL authoring• pureQuery• Query explain
Access
IBM Portfolio Integration 2012-2013
•Physical modeling & resource discovery
•Database resource creation
© 2012 IBM Corporation22
IMS Modernization Solutions
Java
IMS
z/OS
TCP/IP
WebSphereTM/DB access
IMS TM and DBResourceAdapters
DataPower
IMS SOAPGateway
TM access
Universal JDBCdriver
DB access
Universal DLIdriver
Java API
TM AccessRYO
C API
Web 2.0(Mashup Center)
Catalog
IMS access anywhereStandards-based data server and TMOpen systems accessWeb services
© 2012 IBM Corporation23
Premier System z web service enablement through DataPower SOA appliances
IBM cross-brand initiative
Deep synergy between DataPower, System z, Rational and Common Transformation tooling to support DataPower as the premier System z gateway for IMS, CICS and DB2
Intended support for IMS DB access
Intended support for top-down service approach for inbound and outbound IMS transactional requests
XI52
XI50z
DataPower Processing Flow
Protocol transformation
WS Monitoring
Native z transports
Transaction distribution
Network-level HA and distribution
RACF-centric security
IMSCICS
DB2
© 2012 IBM Corporation24
Java dependent region deployment
Java dependent region resource adapterAllows new IMS transactions (JMP, JBP) to be written in Java and managed by the IMS transaction manager
Complete Java framework for applications operating in an IMS container– Message queue processing– Program switching
• Deferred and immediate– Transaction demarcation– GSAM support– Additional IMS call support necessary for IMS transactions
• INQY• INIT• LOG• Etc
Shipped with type 2 Universal drivers
© 2012 IBM Corporation25
Web services
(.NET, SAP, etc.)
IMS Enterprise
Suite SOAP Gateway
IMS Enterprise
Suite SOAP Gateway
IMSIMSIMS ConnectIMS
Connect
z/OS
HTTP / SOAP TCP/IP / XML
Windows/zLinux/zOS
SOAP Envelopewith XML message XML message IMS
message
Web containerSupports industry web service standards
–HTTP(S), SSL, SOAP 1.1, WSDL 1.1, WS-I BP 1.0, WS-SecurityAsynchronous and synchronous callout to Web Services providers
–Concurrency threading support
IMS Enterprise Suite SOAP Gateway
© 2012 IBM Corporation26
SOAP Gateway in Enterprise Suite V2.1
Supports IMS V12 and IMS V11
Supported platforms–z/OS–Linux on system Z–Microsoft Windows
Tooling support–Required versions of Rational Developer for System z
• RDz V8.0.2 or later is required–RDz V8.0.3 and later provides enhancements for the top-down web service provider scenario
© 2012 IBM Corporation27
Web service security enhancements
Java separation
Enhanced connection error recovery
On Windows, SOAP Gateway can run as a Windows Service
New features in V2.1
© 2012 IBM Corporation28
SAML 1.1 signed sender-vouches tokens
SAML 2.0 unsigned sender-vouches tokens– SAML 2.0 is a newer standard that introduces features such as
session management, attribute profiles, encryption, metadata specifications, and pseudonyms.
Web service security enhancements - inbound
© 2012 IBM Corporation29
Java separation
SOAP Gateway server can execute on a separately installed IBM SDK
Multiple SOAP Gateway server instances can share a single instance of the IBM SDK that is included in IMS Enterprise Suite
Java ships in Enterprise Suite V2.1 Base Services
© 2012 IBM Corporation30
Enhanced connection error recovery
Eliminates the need to restart SOAP Gateway when an IMS Connect outage occurs
Stale connections are refreshed under the covers
Requires the following:– IMS V12: APAR PM29137– IMS V11: APAR PM27324– The configuration of the HWSSMPL1 exit on IMS Connect
© 2012 IBM Corporation31
Futures
WS-Security–Inbound
- SAML 2.0 (signed)–Outbound
- SAML 1.1, 2.0 (unsigned)
Server Shutdown–Immediate–Graceful
• Process all in-flight messages and come down gracefully
© 2012 IBM Corporation32
Futures
Advanced installation support– Consistent installation story using IBM Installation Manager (IM) on all
supported platforms– Make the post-SMP installation process flexible using IM on z/OS
IMS transaction tracking support for SOAP Gateway– Provide server “Health Check” functionality using JMX monitoring
• Monitor JVM, connection resources, traffic, etc– Provide transaction tracking
• Allow client applications to pass in unique message ID or optionally generate it within SOAP Gateway• Propagate the transaction ID to IMS Connect and OTMA• Create transaction tracking log and/or send tracking information to other consumers
© 2012 IBM Corporation33
WebSphere and IMS TM Resource Adapter
WAS/WPS/WTX/WMB/WESB
IMS TMIMS TMresourceresourceadapteradapter
WebService
TCP/IP
WebComponent
EnterpriseBean
IMS Connect
IMS DB *
IMS
IMS App
Enable IMS applications as clients or web service requestorsAllows Java applications to invoke IMS transactions
Integrate with Java EE or WebSphere-based servers with built-in QoS support (2PC, connection pooling, security management)
Java EE Connector Architecture (JCA/J2C) compliant
Rational Application Developer (RAD) orWebSphere Integration Developer (WID)
IMS app Source (COBOL, PLI, C, MFS)
Generates
* Binary, text or XML data