websphere datapower v6 support for ims - kiesslich … · ims synchronous callout to datapower ims...
TRANSCRIPT
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.
Disclaimer
The WebSphere DataPower Integration Appliance is a purpose built hardware platform for delivering rapid data transformations for cloud and mobile applications, secured and scalable business integration, and edge of network security gateway in a single drop-in appliance.
3
Business Value Provided
4
Business Value Provided
• Target Market
– DataPower and IMS Users
• Challenge Addressed
– Enable IMS synchronous callout applications as service
consumer on DataPower in addition to current support of IMS
application as service provider
– Introduce IMS to the list of DBMS supported by DataPower
5
Business Value Provided
• Solution Statement
– The most recent DataPower firmware enable connectivity with IMS
as both service consumer and provider of any web or HTTP
services.
• Business Value
– Enable IMS synchronous callout applications to use Websphere
DataPower Integration Appliance
• Core business of service-oriented architecture (SOA)
• Serve areas of business-to-business (B2B) connectivity
• web application proxying.
– Advanced application caching, rapid integration with cloud-based
systems, and more
– Expand the target market of DataPower and provide a solution for
those IMS Customers interested in adopting this technology
• IMS Connect Send/Receive Support
– enables a direct connection to an IMS transaction
• IMS ICAL Synchronous Callout Support (new)
– enables access from IMS transaction to external service
• IMS Database Support (new)
– enables a direct connection to an IMS database
Solution Highlights
7
Prerequisites for IMS synchronous callout
• Software requirements
– IMS V12
– IMS Connect
– IBM WebSphere DataPower Firmware 6.0.0.0 or higher
• Hardware requirements
- IBM WebSphere DataPower appliance XI52, XI50B, XB62
• Tooling
– WebSphere Transformation Extender (WTX)
Provides mapping between different data formats. WTX maps can
be built as deployable artifact for DataPower, providing data
transformation between IMS callout bytes and XML data for web
services.
A WTX map can be set using a DataPower-specified variable, then
called within XSL code in a DataPower policy.
8
Prerequisites for IMS DB
• Software requirements
– IMS V12, IMS Catalog, ODBM and SCI
– IMS Connect
– IBM WebSphere DataPower Firmware 6.0.0.0 or higher
DataPower Models for IMS solutions
DataPower Models
supporting 6.0 release
IMS TM synchronous
callout support
XI52, XI50B, XB62
IMS TM provider
support
XI50, XI52, XI50B,
XI50Z, XB62
IMS DB support XG45, XI52, XI50B,
XB62
12
Solution Highlights – Database access
• Enables a direct connection from DataPower to access an IMS
database
13
Dependencies – Database access
• IMS Connect
– ODACCESS statement in HWSCFGxx member of a
concatenated PROCLIB data set
• IMS V12
– IMS Catalog to access to metadata of IMS programs and
databases resources .
14
Configuration – Database access
1. Create a Multi-Protocol Gateway Configuration
2. Configure a “SQL Data Source” object (DB connection
only)
3. Configure the Backend URL
4. Define a MPG “Policy”. Create one or more “Rule”(s) for
the policy
5. Apply the changes, and save the configuration
15
Solution Highlights - Callout
• The IMS callout connection is a DataPower “Front Side Handler”
that can retrieve IMS callout messages and send response data.
• The handler internally creates one or more IMS Connect
dedicated persistent socket connections to the host system
• The handler communicates with IMS Connect via a new
DataPower dedicated user message exit, HWSDPWR1
Architecture: IMS Synchronous Callout to DataPower
IMS V12
IMS application 1
:
ICAL
(synchronous)
IMS
Connect
TPIPE
DataPower V6.0
on XI52, XI50B, XI50Z, XB62
External
services Routing/
data
transformation
Resume
tpipe
ACK
request
Response
IMS Callout front side
handler
Sends
ICAL
responses
Retrieve
ICAL
requests
ACK
18
IMS Synchronous Callout to DataPower
IMS Application
ICAL A (Xid*)
ICAL B (Yid*)
ICAL C (Zid*) * 8 bytes unique service id
Each descriptor:
- Member, TPIPE
- Adapter, Converter
- Timeout
Descriptors
OTMA
IMS
Connect
DataPower
resume
TPIPE
bytes
IMS
External
Service
X
Y
Z
request bytes
with service id
response
bytes
COBOL copybook/
PLI import
for
ICAL request/response
A, B, C
WebSphere
Transformation
Extender (WTX) Schema
from
services
X, Y, Z
deploy
import /
generate
type
tree
request/
response
In XML
IMS
Callout
front side
handler
WTX generated
Maps for
A-X, B-Y, C-Z
WTX generated
Maps for
A-X, B-Y, C-Z
WTX generated
Maps for
A-X, B-Y, C-Z
Bottom-up or meet-in-middle
mapping
Transform rule: (user
defined XSL can
select a map based
on service id)
19
Dependencies - Callout
• IMS Connect
– DataPower User Exit Installation - Object Code Only user exit
HWSDPWR1 (new)
• Specified in the EXIT= parameter of the TCP/IP statement in the IMS
Connect configuration file (HWSCFGxx).
– V13 PTF UK97704
– V12 PTF UK91544
• IMS
• DL/I ICAL user can specify a 1-to-8 byte mapname as the first 8 bytes in
AIBUTKN so that this ID can be included in the OTMA state data in the
callout message. The ID can be used as a unique service identifier for
data transformation mapping and service routing
– V13 (already available as base code)
– V12 PTF UK82636 (PM73135) AIB MAP name field
20
Configuration - Callout
1. Create a Multi-Protocol Gateway (MPG) Configuration
2. Configure IMS Callout Front Side Handler
3. Configure the Backend URL
4. Define a MPG “Policy”. Create one or more “Rule”(s) for
the policy
5. Apply the changes, and save the configuration