Post on 20-May-2015
description
© 2014 IBM Corporation
1
2014
Insight comes to State FarmApril 2014
Modernizing/Simplifying Application
Enablement in IMS
Greg Vance
IMS Architectgvance@us.ibm.com
© 2014 IBM Corporation2
2014
Please note
IBM’s statements regarding its plans, directions, and intent are subject to change or
withdrawal without notice at IBM’s sole discretion.
Information regarding potential future products is intended to outline our general product
direction and it should not be relied on in making a purchasing decision.
The information mentioned regarding potential future products is not a commitment, promise,
or legal obligation to deliver any material, code or functionality. Information about potential
future products may not be incorporated into any contract. The development, release, and
timing of any future features or functionality described for our products remains at our sole
discretion.
Performance is based on measurements and projections using standard IBM
benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including
considerations such as the amount of multiprogramming in the user’s job stream,
the I/O configuration, the storage configuration, and the workload processed.
Therefore, no assurance can be given that an individual user will achieve results
similar to those stated here.
© 2014 IBM Corporation3
2014
IMS product investment
� Continue to deliver the
IMS value proposition– Minimize cost per transaction
– Superior reliability, availability
and serviceability (RAS)
� Core capabilities– Reduce path length, contention,
I/O…
– Reduce planned outages
– New pricing models
� Big Data & Analytics– Accelerate time to insight
� Cloud/Mobile– Rapidly enable/control cloud &
mobile access to IMS resources
� Leverage and extend the
value of your IMS
investment
� Expand and empower the
IMS talent population
� Open interfaces & Java
� Modern tooling for
administrators, developers
and DBAs
Strategic Intent Investment
© 2014 IBM Corporation4
2014
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
© 2014 IBM Corporation5
2014
IMS Open Database
Solution statement
� Extend the reach of IMS data– Offer scalable, distributed, and high-speed local access to IMS database resources
Value
� Business 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 differentiators
� Standards-based approach (Java Connector Architecture, JDBC, SQL, DRDA)
� Solution packaged with IMS
Enables new application design frameworks and patterns
� JCA 1.5 (Java EE)
� JDBC
© 2014 IBM Corporation6
2014
IMS Open Database
DRDA over TCP/IP
DRDA over TCP/IP
z/OS
z/OS
Open Systems (e.g.; LUW)
JavaEE
JDBC
DLI
Universaldrivers DRDA over TCP/IP
Universaldrivers
JavaEE
DLI
JDBC
Direct
© 2014 IBM Corporation7
2014
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
© 2014 IBM Corporation8
2014
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
© 2014 IBM Corporation9
2014
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 zEC12– 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
© 2014 IBM Corporation10
2014
IMS Open Database environment
LPAR Az/OS
IMS DBCTL
IMS
PC
Open Systems
Universal
DB
Resource
Adapter
J
C
A
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
O
D
B
A
ODBM
© 2014 IBM Corporation11
2014
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
O
D
B
A
DLI
JDBC
RYO DRDA Appl.
IMS DBCTL
IMS
PCSCI
O
D
B
A
IMS Universal drivers
LPAR A
IMS DBCTL
IMS
PCSCI
O
D
B
A
ODBM
IMS Connect
T
C
P
I
P
SCI
ODBM
ODBM
LPAR B
XCF
WAS z/OSUniversal
DB Resource
adapter
J
C
A
1.5
T
C
P
I
P
OD
BA
PCSCI
Traditional ODBA
DLI
JDBC
IMS Universal driversTraditional ODBA
JEE
Java SE
DRDA
© 2014 IBM Corporation12
201412
IMS JMP region performanceAggregate SDK, software and hardware improvements
Over 7x aggregate throughput improvement from 2009 to 2014 due
to the following enhancements
� Java version to version performance improvements
� IMS improvements
� Hardware improvements
� DASD improvements
© 2014 IBM Corporation13
201413
Business Challenge
– Required open systems access to IMS database assets
– Error-prone process to accomplish task
• Unloaded databases and did manual entry
into open system database
Solution
– Leverage IMS Open Database technology and the Universal JDBC driver Benefits
– Real-time access to data
– Confident decision making
– Trusted information
Who
– Caterpillar
• Core manufacturing
system managed
by IMS
© 2014 IBM Corporation14
2014
14
Business Challenge
– Introduce additional core services to support
new banking channels
– Impaired ability to deliver new functionSolution
– Introduce a new banking channel
implemented in Java using the
Universal JDBC and Universal DLI
drivers for IMS
– Deployment in CICS JCICS regions
– Initially no language interoperability
(pure Java)
• Future potential
Benefits
– Leverage abundant Java domain
knowledge in industry
– Dramatically decreased time to market
– IMS API consistency with relational
databases
Who
– Bank in US
• Several banking channels managed by IMS and written mostly in COBOL
© 2014 IBM Corporation15
2014
Business Drivers
– Modernize existing core banking framework to
build a highly integrated and optimized core
system in an SOA-based environment
– Expand with new components, based on new
architecture
– Integrate standard (Java) technology
Solution
– Leverage the IMS application server
and its Java capabilities
• Deployment in JVM-ready JMP regions
– Deep use of Java-COBOL language
interoperability to leverage and build
upon existing assets with new Java
technology
– Access DB2 z/OS using the DB2
JCC type 2 JDBC driver
– Access IMS DB using the IMS
Universal type 2 JDBC driver
Benefits
– Leverage abundant Java domain skills
and knowledge in the industry
– Dramatically improved time to market for
new services
– Easily maintainable topology for the next
several decades
– Stay on rock solid hardware/software
stack
© 2014 IBM Corporation16
2014
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
PSB
source PSBLIB
DBD
source DBDLIB
PSBGEN
DBDGEN
ACBGENIMS Explorer
IMS
© 2014 IBM Corporation17
2014
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
PSB
source
DBD
source
IMS
© 2014 IBM Corporation18
2014
Overview of IMS Catalog
�The IMS catalog contains information about IMS program
resources, database resources, and relevant application metadata
that IMS controls:– All program- and database-related information defined to the IMS database
system including databases, fields, segments, data types, and more
– Changes made to any of these resources when you create, alter, or delete any
IMS resource information will be reflected in the catalog
�The IMS catalog is a key component of the IMS growth strategy:– Simplification
– Integration
– Dynamic database
– Versioning
© 2014 IBM Corporation19
2014
Types of technical metadata and storage medium
� DB– PSB/DBD resources
• Database structure definitions• Physical database definitions• Segment definitions• Field definitions
– Application• Data types• Application defined fields• Encodings• Redefines• User defined types• Structures
� TM– MODBLKS resources
• Program definitions• Transaction definitions
– FORMAT resources*– Application*
• Input/output message definitions
Catalog
Repository
IMS database
VSAM
* It is our intention to store this metadata in the repository
© 2014 IBM Corporation20
2014
Catalog runtime access
IMS
Connect
DBDB
Catalog
IMS
ODBM
DR
WAS zCICSDB2 z
DRDA/TCPIP
SQL/DLI
SQL/DLI
DRDA DLI
UsersIMS Explorer
SQL/DLI
Tools
UniversalDrivers
(SQL/DLI/XML)
© 2014 IBM Corporation21
2014
Installation
� IMS provides PSBLIB and DBDLIB members for the catalog– User to run ACBGEN
– IMS internally handles the rest of the initialization process• MODBLKS creation (PDIR, DDIR)
• Loading of DMBs and PSBs into resident pools
� IMS provides utilities that will– Create the catalog database
– Load the catalog from a user ACBLIB
� IMS provides an option that does not require DBRC for the
catalog– Many customers have expressed that the DBRC requirement for HALDB
databases puts undesired burden on test system infrastructure
© 2014 IBM Corporation22
2014
Management
�Catalog supports all standard utilities for backup and recovery
�Catalog supports online reorg (it is a PHIDAM database)
�As part of initial catalog load process IMS will determine the size
of the catalog datasets– User can allocate or defer to IMS to allocate on their behalf
�DBRC is optional
© 2014 IBM Corporation23
2014
Coexistence
�Two models– A single catalog can be data shared among multiple IMS systems
– Single catalog per IMS system
�ACBLIB and catalog will remain in sync with one another– Managed by IMS
�Future– IMS will be configured to load (cold start) from either catalog or ACBLIB
© 2014 IBM Corporation24
2014
Catalog databaseHEADER
(RESOURCE HEADER)
SS(SENSEG)
PCB
PSB
SF(SENFLD)
PSBVENDPSBRMK(REMARKS)
PCBRMK(REMARKS)
SFRMK(REMARKS)
SSRMK(REMAKRS)
XDFLD
LCHILD
AREACAPXDBD SEGMDSET
(DATASET)
DBD
MAP(DFSMAP)
DBDRMK(REMARKS)
CAPXSEGM
CASE(DFSCASE)
LCHRMK(REMARKS)
SEGMRMK(REMARKS)
CMAR(DFSMARSH)
CPROP(PROPERTIES)
CFLD(FIELD)
DBDVEND
CFLDRMK(REMARKS)
CMARRMK(REMARKS)
DBDXREFDSETRMK(REMARKS)
AREARMK(REMARKS)
FLD(FIELD)
MAR(DFSMARSH)
FLDRMK(REMARKS)
PROP(PROPERTIES)
MARRMK(REMARKS)
MAPRMK(REMARKS)
CASERMK(REMARKS)
RESERVED RESERVED RESERVED
. . .RESERVED RESERVED RESERVED
RESERVED RESERVED
LCHIDX(INDEX NAME)
© 2014 IBM Corporation25
2014
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– Maps are intended to be interpreted at runtime by the Universal drivers and the proper
data elements are returned based on the runtime case of the segment instance– Example: Insurance segment mapped multiple ways depending on value of Policy Type
control field
-----
555 Disk
Drive Way,
95141
500K5Single
FamilyH
Red2K1989EscortFord----M
ColorValueYearModelMakeAddressValueRoomsProperty
Type
Policy
Type
© 2014 IBM Corporation26
2014
Dynamic database - Data Definition Language
�SQL incorporates DDL to modify the schema of a database
�Authoring DDL is straight-forward with sophisticated tooling support in the industry
�SQL/DDL can be used to update/add metadata in the catalog without the need of a GEN
– Directly update the catalog
� IMS can be notified of such an update and load the new definitions
� It is our intention to offer this type of dynamic definition for IMS
© 2014 IBM Corporation27
2014
IMS integration with Cognos BI 10.2.1
� IMS originally certified with Cognos 10.2 (LUW or z/OS) – One of three to be certified
– Supports IMS V12 and IMS V13
�Enhancement in Cognos 10.2.1 (release 9/2013)– IMS is now supported in Cognos BI z/OS deployments on WebSphere Application Server
– Allows for a more integrated solution with all of the speed expected from z/OS
Cognos on LUW or z/OS z/OS
Cognos
IMS
Universal
Database
Driver
TCPIP
TCPIP
IMS Connect
S
C
I
ODBM
S
C
I
ODBA
CTLIMS DBs
PC IMS
TCPIP
IMSCatalog
© 2014 IBM Corporation28
2014
Watson Explorer : visualization & discovery across all your data sources : “Integration at the glass”
Create unified view of ALL information for real-time monitoring
Identify areas of information risk & ensure data
compliance
Analyze customer information & data to unlock true
customer value
Increase productivity & leverage past work
increasing speed to market
Improve customer service & reduce
call times
Watson
ExplorerProviding unified, real-time access and fusion of big
data unlocks greater insight and ROI
Securely connect to and leverage data stored in DB2 for
z/OS & IMS
Help prioritize your System z big data integration and analytics projects
28
© 2014 IBM Corporation
2014
�Target Market� IMS TM and DB customers who would like to write or modify IMS COBOL
applications to access IMS data using SQL
�Challenge Addressed� Modernization of COBOL assets
� No SQL access to IMS data from IMS COBOL applications
�Solution Statement� Enable SQL calls from COBOL applications in addition to the current Java-based
solutions
�Business Value� Expands IMS database access for application and database developers
� Reduce application development cost by leveraging existing SQL skills
� Provide a consolidated native SQL engine as the foundation of existing and future
client exploitation
IMS 13 SQL support for COBOL
© 2014 IBM Corporation
2014
�SQL support for COBOL� Offer SQL as a query language for COBOL programs to access IMS database in addition to DLI
� SELECT/INSERT/UPDATE/DELETE
� EXEC SQLIMS as the interface to execute IMS SQL calls
�SQL processor in IMS� Process SQL calls natively by the IMS subsystem
� Provide a consolidated way for SQL processing
� Uses database metadata in IMS Catalog
�Support IMS TM/DB (MPP, IFP, BMP) and DBCTL BMP
Solution Highlights
© 2014 IBM Corporation
201431
�Consolidated SQL processor for both host (COBOL) and distributed applications
�Data Provider for Microsoft .NET is now available with IMS Enterprise Suite 3.1
z/OS
IMS DBDLI
SQL processor
Catalog
MetadataSQL
DRDA
MPP BMP IFP COBOL
Language
Inte
rface
IMS
JDBC
RYO
.NET
Language nterface
SQL ODBA / DRADistributed
Intended support
V13 support
Consolidated SQL processor
© 2014 IBM Corporation
2014
1. Include SQLIMSCA
2. Specify SQL statement in a COBOL variable
3. Declare host variable or structure for result data row
4. Declare a cursor for the statement name
5. Prepare the SELECT statement
6. Open the cursor
7. Fetch a row of data into host variable or structure.
8. Repeat previous step until not more data� When no more data, SQLIMSCODE=100
9. Handle any error
10.Close the cursor
Example: Coding Fixed-list SELECT
© 2014 IBM Corporation
2014
WORKING-STORAGE SECTION.
* Declare SQLIMSCA
EXEC SQLIMS INCLUDE SQLIMSCA END-EXEC.
* Declare COBOL variable for SQL statement and result data
01 SQL-STATEMENT
49 SQL-STATEMENT-LEN PIC S9(4) COMP.
49 SQL-STATEMENT-TEXTPIC X(100).
01 HOSPITAL-RESULT-ROW
05 HOSPLL PIC S9(3) BINARY.
05 HOSPCODE PIC X(12).
05 HOSPNAME PIC X(17).
PROCEDURE DIVISION.
* Declare Cursor for the Prepared Statement
EXEC SQLIMS
DECLARE CURSOR cursor-name for prepared-statement-name
END-EXEC.
* Load SQL statement in the COBOL variable
MOVE "SELECT HOSPLL,HOSPCODE,HOSPCODE FROM PCB01.HOSPITAL” TO
SELECT-STATEMENT-TXT.
Sample COBOL SQL
© 2014 IBM Corporation
2014
* Prepared SQL statement string for processing
EXEC SQLIMS
PREPARE prepared-statement-name FROM :SQL-STATEMENT
END-EXEC.
* Open Cursor
EXEC SQLIMS
OPEN cursor-name
END-EXEC.
* Execute SQL statement
* Fetch data from IMS into host variable until no more data is found
PERFORM FETCH-PROC
UNTIL SQLIMSCODE EQUAL 100.
:
FETCH-PROC.
EXEC SQLIMS
FETCH cursor-name INTO :HOSPITAL-RESULT-ROW
END-EXEC.
:
* Close Cursor
EXEC SQLIMS
CLOSE cursor-name
END-EXEC.
Sample COBOL SQL (Cont’d)
© 2014 IBM Corporation
2014
�Compile IMS SQL COBOL
application with IMS coprocessor
�Pre-process EXEC SQLIMS
statements in COBOL source
�Integrated with Enterprise COBOL
V5.1
�Specify ‘SQLIMS’ compiler option
to compile COBOL program with
IMS SQL calls
IMS coprocessor
IMS COBOL application source files with SQL
statements
Libraries Object files
COBOL Link
Executable Program
COBOL Compiler with IMS coprocessor
TranslateEXEC
SQLIMS
INCLUDEDFSLI000
© 2014 IBM Corporation36
2014
Database Versioning
� Allows application programs to use different versions of the same physical database– Multiple views of the physical data maintained in the IMS Catalog
� Provides the ability to assign user-defined version identifiers to different versions of an IMS database structure
� Enables structural changes to a database while providing multiple views of the physical IMS data to various
applications– Applies to Full Function DB, HALDB, Fast Path DEDB
– Supports database types: HDAM, HIDAM, PHDAM, PHIDAM, DEDB
� Database Versioning supports the following database structure changes– For all supported database types
• Increasing the length of a segment
• Adding a new field (or fields) to space at the end of a segment
� Benefits– Physical database structure can be changed without having to modify all the existing application programs using the database
– Applications referencing a new physical database structure can be brought online without affecting applications that use previous
database structures
– Applications not requiring sensitivity to the new physical database structure can continue to access the database without any
modifications or recompilation
© 2014 IBM Corporation37
2014
Sample Database Versioning Flow
DBJK21
DBJK22
DBJK23
Application
IMS
DBJK21 V3DBJK22 V3DBJK23 V3
ACBLI B
DBJK21 V0,V1,V2,V3DBJK22 V0,V1,V2,V3DBJK23 V0,V1,V2,V3
IMS Catalog
DBJK21 V3DBJK22 V3DBJK23 V3
DBDLIB
PSBJK
PSBLIB
PSBGEN
DBLEVL=CURR
--------------------------
PCB
--------------------------
DBJK21 V1
DBJK22
DBJK23 V2
PSB=PSBJK Source
DBJK21 V3
DBD Source
DBJK22 V3
DBJK23 V3
DBDGEN
PSBGEN
DBJK21 V3
DBJK22 V3
DBJK23 V3
DBJK21 V3
DBJK22 V2
DBJK23 V1
DLI
Retrieve DBJK22 & DBJK23 from Catalog
Active
ACBGEN
�
����
����
���� ����
����
Version “V3” of DBDs put into
ACBLIB & Catalog
Database Versioning
enabled -> data returned to app at V1,
V2 & V3 levels
����
DBJK21
DBJK22
DBJK23
INIT
VERSION(DBJK21=3,DBJK22=2,DBJK23=1)
37 IBM Confidential
© 2014 IBM Corporation38
201438
Customer Account – fixed length segment
Base
Account Number Member name Balance Credit Limit
Account Number Member name Balance Credit Limit Reward Points
Updated
� Segment length increased and new field “Reward Points” defined
� Existing applications do not need to be updated
� Existing applications do not have to know new field exists
� Existing applications do not update the new field
Database Versioning Example
© 2014 IBM Corporation39
2014IMS
ISPF
IMS Explorer for Administration
(Web Browser)
AdministratorsDevelopers
IMS Explorer for Development
(Eclipse)
IMS user interface enhancements
© 2014 IBM Corporation40
2014
IMS TM connectivity and integration
WebSphereApplication
Server or Java EE Server**
SOAP Gateway
DatapowerWebSphere
Message Broker
WebSphereEnterprise
Service Bus
IBM Process Server
WebSphereTransformation
Extender
Java EEJava EE
Enterprise Service Bus
BPMBPMWeb ServiceWeb Service
• Full SOA and Java EE Services
• Inbound and Outbound from IMS
• Direct IMS SOAP endpoint for Web Services
• Inbound and Outbound from IMS
• SOA appliances
• Fast Web services and XML transformat-ion
• Inbound to IMS
• Transform complex data types
• Inbound to IMS
Complex Data Transformation
Complex Data Transformation
• Business process automation and choreography
• Inbound and Outbound* from IMS
• Java based Enterprise Service Bus
• Inbound and Outbound* from IMS
• Interoperate heterogeneous services and data environments
• Inbound to IMS
Many IBM application servers already provide built-in support for IMS
transaction access today
*Additional coding may required. **Subset of functions supported with conditional support
© 2014 IBM Corporation41
2014
IMS Callout
�Enable IMS applications as Service Requesters– IMS Application can be an integration focal point in the enterprise
– Interoperate with business logic outside the IMS environment
– Callout to Java EE apps (EJB and MDB) and Web Services using WebSphere
Application Server and IMS TM Resource Adapter
– Callout to Web services providers (e.g. Microsoft .NET) using SOAP Gateway
– Callout to other applications
© 2014 IBM Corporation42
2014
IMS Callout
�Asynchronous Callout– IMS application invokes external applications without waiting for response.
• DL/I ISRT ALTPCB
• Destination can be – Another IMS application (program switch)
– An OTMA destination
» Sent to any OTMA clients, such as IMS Connect or WebSphere MQ
» TPIPE name specified via DRU exits or OTMA descriptor.
– Any response sent back is a new transaction
�Synchronous Callout– IMS application invokes external application and waits for the response.
• DL/I ICAL
• Supports timeout capability and large messages
• Secondary application is not in the same two-phase commit scope
– IMS application waits until the response is returned or the request receives a
timeout
– Callout response is sent back to the same transaction that initiated it
© 2014 IBM Corporation43
2014
Synchronous Program Switch� Extend IMS Synchronous Callout to allow DL/I ICAL to invoke another IMS Application
– DL/I ISRT continues to be used for asynchronous program switch� OTMA Descriptor enhanced to recognize an IMS transaction destination� Java programs can use the Java Message Service (JMS) API for synchronous program switch
Benefits� Provides a single DL/I call to request a synchronous service
regardless of where that service resides– Simplifies integration and improves usability
ICAL DEST1
ICAL TRANB
TRANAIMS CTL Region
IMS Connect
WebSphere
IMS TMRA
IMS SOAP
Gateway
TCP/IP
RYO appl
OTMA
MSG-Q
Destination Descriptor
TYPE(IMSCON)
TRANB
GU IOPCB
ISRT IOPCB
Destination Descriptor
TYPE(IMSTRAN)
1
23
4
56
7
GU, IOPCB
Applications can issue multiple ICALs to different destination TYPEs
Synchronous calloutSynchronous program switch
WebSphere
DataPower
© 2014 IBM Corporation44
2014
IMS and DataPower
� DataPower provides a standard WS façade to IMS
� REST and SOAP
� Exposes database content (information) and IMS transactions as a service
� Leverages extensive Web Services security and management capabilities of DataPower to more securely expose critical data to the enterprise
Data
Po
wer
REST & JSONover HTTPS
Mobile
devices
© 2014 IBM Corporation45
2014
Thank You!