Transcript Slide 1

IBM Software Group
Accessing IMS Transactions through
WebSphere and the IMS TM Resource
Adapter
Hélène Lyon
South-Europe IMS Technical Leader
[email protected]
© 2007 IBM Corporation
IBM Software Group
IMS Architecture
 IMS Transaction
 No presentation layer
VTAM
Telnet
(LU0 LU1 LU2 LU6.1 LU6.2)
 Access to Resource Managers (RM)
IMS DB, DB2, MQ
 Very simple design
B
Get Input Message
RM calls
ISRT Output Message
 IMS Database
 Hierarchical design
 JDBC access
D
APPC/MVS
I
M
S
DB2
 Description of input and output
messages and device map
 Not used in client/server
implementations
2
DB2
Stored
Proc.
IMS Message
Queues
Appl. B
 IMS MFS
IMS
Connect
MFS P
T
M
 XML datastore
P
WMQ
TCP/IP for zOS
D
...
Appl. B
IMS Database Manager
WMQ
D
D
z/OS
© 2007 IBM Corporation
IBM Software Group
Agenda

Overview of JCA and IMS TM Resource Adapter
 Socket Connections & Socket Types
 Connection Management
 Security Management
 Transaction Management

Last enhancements
 Supermember
 Hold queue management
PurgeAsyncOutput and ReRoute and Retrieve
Alternate destination

Some IMS V10 Enhancements
 SOA Composite Application
 Accessing SOA applications from IMS (Callout)
3
© 2007 IBM Corporation
IBM Software Group
J2EE Architecture
 Java 2 Platform, Enterprise Edition
 A standards-based architecture to enable development of multi-tier distributed applications
 J2EE Connector Architecture (J2C/JCA)
 Enables standard API use for all access to any EIS
Web Container
EJB
Container
RMI / IIOP
HTTP / HTTPS
Web
Browser
Client
Graphic Here
Servlets
JSPs
J2EE Core Services
4
EJBs
JDBC / JCA Resource Adapters
 Simplifies application component development
Enterprise
Information
System
(e.g. IMS)
© 2007 IBM Corporation
IBM Software Group
J2EE Connector Architecture
J2EE Server
Web
Component
Enterprise
Bean
The application
API
CCI
Application
Contract
Managers:
• Transaction
• Connection
• Security
5
SPI
System
Contracts
Resource
Adapter
EIS
© 2007 IBM Corporation
IBM Software Group
JCA - IMS Resource Adapter
SOAP
Other
WAS
B
IMS
TM resource
Adapter
DB2
TCP/IP
IMS
Connect
O
T
M
A
IMS
Appls. B
D
IMS
DB
 IMS Connector for Java (renamed to IMS TM Resource Adapter)
 Provides connectivity to IMS Transactions
With an option to use a global transaction scope between the 2 business logic parts
(distributed Two-Phase Commit)
 Solution Benefits
 The “Direct Connection” Choice!
Prereqs installation of IMS Connect
No changes to IMS applications
 The “Strategic” option for IMS Lab
 From any WebSphere platform, z/OS or distributed with J2EE Quality of Services
http://www-306.ibm.com/software/data/db2imstools/imstools/imsjavcon.html
6
© 2007 IBM Corporation
IBM Software Group
JCA - IMS Resource Adapter …
WebSphere Application Server
Windows / AIX / Solaris / Linux / zLinux / HP_UX and z/OS
IMS
Web
Service
Web
Component
Managers:
• Connection
• Transaction
• Security
Enterprise
Bean
IMS
Connect
CCI
O
T
IMS App
M
A
Application
Contract
IMS DB
IMS
SPI
System
Contracts
IMS TM
Resource
Adapter
IMS
Connect
TCP/IP
or Local
Option
O
T
M
A
IMS App
DB2
IMS DB
7
© 2007 IBM Corporation
IBM Software Group
IMS TM Resource Adapter – Flexible and Scalable
Windows / AIX / Solaris /
Linux
andWebSphere
z/OS
z/OS1
XCF
IMS
Connect
Application
Server
IMS Resource
Adapter
IMS
Connect
IMS
B
D
IMS
B
D
IMS
B
D
z/OS2
WebSphere
Application
Server
IMS Resource
Adapter
Linux for System z
WebSphere
Application
Server
IMS Resource
Adapter
IMS
Connect
TCP/IP
XCF
Local
TCP/IP or Local Option
Local Option has been
stabilized and no new future
enhancements
8
© 2007 IBM Corporation
IBM Software Group
IMS TM Resource Adapter – Features at a glance
 Supports J2EE Connector
Architecture (JCA) 1.0 & 1.5
 Supports various types of interactions
and programming models with IMS
 Invokes IMS transactions or commands
Conversational and non-Conversational
MFS, COBOL, C, *PLI
 SendRev, Send Only
 Retrieve Asynchronous output
Options for handling undelivered output
messages: purge or reroute
Single no wait, single wait
 Commit mode 1 or 0 processing
 SyncLevel none or Confirm
 Alternate Client ID
 Connection Management
 Connection pooling
 Handles execution or socket timeouts
 Transaction Management
 Global z/OS RRS transaction support
and Distributed XA transaction support
with Two Phase Commit
 Security Management
 J2EE EIS Sign-on
 SSL, RACF key ring
 Enhancements in complex
environment
 Sysplex distributor environment
 zWAS 64 bit support. for local option
(soon)
 Callout (V10)
 Make IMS application as a client to
access J2EE applications
9
© 2007 IBM Corporation
IBM Software Group
Socket Connections
 In a managed environment, all socket connections between IMS TMRA
and IMS Connect are persistent:
 Reusable connections available from connection pools
 Connection is disconnected when
Error occurred (except execution timeout), or,
Cleaned up by connection manager based on connection pool properties
 Two types of persistent socket connections
Shareable persistent (recommended)
– IMS TM Resource Adapter generates clientID
Dedicated persistent *
– Client application provides socket identifier using IMSInteractionSpec property clientID
 In a non-managed environment, connections are disconnected after each
interaction
 There is no pooling of connection
 Connection cannot be reused
*Dedicated Connections will be stabilized and no new enhancements. Recommend to use Sharable connections
10
© 2007 IBM Corporation
IBM Software Group
Socket Connections …
WebSphere
Application
Server
IMS
TM
RA
Duplicate
ClientId
IMS
Connect
Dedicated persistent
CLIENT01
CLIENT01
Shareable persistent
HWSABC01
HWSXYZ05
HWS22Q0T
11
© 2007 IBM Corporation
IBM Software Group
Connection Management
 Connection Pooling
 Connections expensive to create
 Connection Manager creates pool for each Connection Factory
 Unused connection objects returned to pool for re-use
 Connection Management Properties
 Specify how application server manages pool
Purge policy specifies how to purge connections when communications error is
detected – EntirePool or FailingConnectionOnly
Minimum connections
Maximum connections
Reap time
Unused timeout
Aged timeout
12
© 2007 IBM Corporation
IBM Software Group
Types of Interactions
 Invoking IMS Transaction or Commands
 Send_Receive or Send Only
 Execution and Socket timeouts
 Retrieve Asynchronous Output Message (Resume Tpipe)
 Retrieve asynchronous output messages from IMS OTMA Asynchronous Hold Queue
 IMSRequestType
 IMS_REQUEST_TYPE_IMS_TRANSACTION
Non-conversational transactions
IMS conversational
 IMS_REQUEST_TYPE_IMS_COMMAND
 IMS_REQUEST_TYPE_MFS_TRANSACTION *
Message Format Service (MFS)
* Not currently supported in RAD
13
© 2007 IBM Corporation
IBM Software Group
Types of Interactions …
 Commit Modes
 Send-then-commit (Commit Mode 1)
Used to run non-recoverable IMS transaction
 Commit-then-send (Commit Mode 0)
Allows clients to run IMS transaction with recoverable output message
ACK/NAK is sent internally by IMS TM Resource Adapter
CM1
CM0
ClientID
Socket type
IMS Interaction Verb
SyncLevel
N/A
(internally
generated)
Shareable
persistent
SYNC_SEND_RECEIVE
None or
Confirm
N/A
(internally
generated)
Shareable
persistent
SYNC_SEND_RECEIVE
SYNC_SEND
SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAIT or
SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_WAIT
Userspecified
clientID
Dedicated
persistent
SYNC_SEND_RECEIVE
SYNC_SEND
SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAIT or
SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_WAIT
Syncpt*
Confirm
* Not externalize – used only when transactionality requested
14
© 2007 IBM Corporation
IBM Software Group
Types of Interactions …
 Send-Then-Commit Flow (CM1)
CLIENT
Sync
Level of
NONE
Send transaction
input
IMS
Transaction inserted to
SMB
Ouput Sent
(No response requested)
Commit Confirmed sent
(Synchpoint has completed)
CLIENT
Sync
Level of
CONFIRM
Send transaction
input
IMS
Transaction inserted to
SMB
Ouput Sent
Response requested
MPP
GU, IOPCB.
ISRT,IOPCB...
Synchpoint Starts
Synchpoint
Completes
MPP
GU, IOPCB.
ISRT,IOPCB...
Synchpoint Starts
Wait …
ACK
15
Commit Confirmed sent
(Synchpoint has
completed)
Synchpoint Completes
© 2007 IBM Corporation
IBM Software Group
Types of Interactions …
 Commit-Then-Send Flow (CM0)
CLIENT
Send transaction
input
IMS
Transaction inserted to
SMB
ACK
MPP
GU, IOPCB
...
ISRT,IOPCB
...
Synchpoint Starts
Synchpoint Completes
Ouput enqueued to TPIPE
Output sent with
response requested
ACK
Output dequeued
16
© 2007 IBM Corporation
IBM Software Group
Security Management
 J2EE provides end-to-end security model for J2EE applications to access
EIS securely
 IMS TM Resource Adapter supports
 Authentication: User ID and Password
Application Component - Component-Managed Sign-on
Application Server - Container-Managed Sign-on
 Encryption using SSL
Provides reliable, secure communication between IMS TM Resource Adapter and IMS
Connect
– End user’s userID or password not used for SSL security
17
© 2007 IBM Corporation
IBM Software Group
Security Management - EIS Sign-on
WebSphere Application Server
z/OS
(Windows, AIX, Solaris, Linux, Linux for z/OS, z/OS)
Security
Manager
Enterprise
Bean
Res-auth = Container
Pass User ID and
Password of Containermanaged authentication
alias to IMS Resource
Adapter
IMS
Resource
Adapter
Send User ID and
Password to IMS Connect
18
RACF
IMS
IMS
Connect
OTMA
If RACF = Y, call RACF
to authenticate User ID
and Password
© 2007 IBM Corporation
IBM Software Group
Security Management - WAS z/OS Thread Identity
z/OS
WebSphere Application Server z/OS
Enterprise
Bean
Res-auth = Container
RunAs = Caller or
System or
Role
Security
Manager
Pass the already
authenticated Security
Token of Run-As
Identity to IMS
Resource Adapter
IMS
Resource
Adapter
Send Security Token to
IMS Connect
19
Authenticate
UserID
with RACF
RACF
IMS
IMS
Connect
OTMA
Local
Option
Bypass authentication
as user is already
verified
© 2007 IBM Corporation
IBM Software Group
Transactionality
 Capability that allows IMS transactions to participate as a resource in two-phase
commit external transactions
 Requires a syncpoint coordinator
RRS on z/OS and/or an external coordinator,
e.g.,IBM WAS (Websphere Application Server)
 Requires client code that uses IMS TMRA
 Local Environment
 WAS, IMS Connect, IMS, and RRS must be in the same
z/OS image **
WAS
Server
platform +
IC4J
Protocol
Global
Trans
Distributed
TCP/IP
YES*
zLINUX
TCP/IP on
Hipersockets
YES*
z/OS
TCP/IP
YES*
z/OS
Local Option
YES **
 Distributed environment (Global XA transaction)
 IMS Connect, RRS and IMS must all exist in the same z/OS image *
 Remote environments use XA
 IMS Connect
Acts as an extension to RRS and is the SDRM (Server Distributed Syncpoint Manager)
Assists RRS in communicating with other syncpoint coordinators
Acts as the CRM (Communications Resource Manager)
20
© 2007 IBM Corporation
IBM Software Group
Transactionality – Distributed XA 2PC Commit
z/OS
WebSphere Application Server
Resource Recovery
Service (RRS)
(Windows, AIX, Solaris, Linux, Linux for z/OS, z/OS)
Transaction
Manager
Enterprise
Bean
1. Uses IMS RA
to invoke IMS
transaction
Single
unit of
work
Debit $100
from Checking
Credit $100
to Savings
XA
SPI
System
Contracts
IMS
Resource
Adapter
IMS
OTMA
Checking
Account
TCP/IP
2. Executes SQL
stmts to DB2
3. Commits the Unit of work.
Transaction AttributeWAS Transaction Manager,
coordinates the unit of work
= TX_REQUIRED
with IMS and DB2 using XA
and two phase commit.
21
IMS
Connect
DB2
Saving
Account
© 2007 IBM Corporation
IBM Software Group
Transactionality – z/OS RRS 2PC Commit
z/OS
WebSphere Application Server z/OS
Enterprise
Bean
Single
unit of
work
Transaction
Manager
IMS
Connect
1. Uses IMS RA
to invoke IMS
transaction
Debit $100
from Checking
Credit $100
to Savings
IMS
Resource
Adapter
IMS
OTMA
Checking
Account
Local
Option
2. Executes SQL
stmts to DB2
3. Commits the Unit of work.
Transaction AttributeWAS Transaction Manager,
using RRS, coordinates the
= TX_REQUIRED
unit of work with IMS and DB2
using two phase commit.
22
Resource Recovery
Service (RRS)
DB2
Saving
Account
© 2007 IBM Corporation
IBM Software Group
Timeouts
 Socket Timeout
 Execution Timeout
 Time IMS TM Resource Adapter waits for
IMS Connect to return transaction output
 Time IMS Connect waits for IMS to
return transaction output.
 Used for network problems
 Used for IMS hangs
 Per interaction
 Per interaction.
 Encompasses Execution Timeout
Execution
IMS TM
Resource
Adapter
IMS
Connect
IMS
Router
Socket
23
© 2007 IBM Corporation
IBM Software Group
Agenda

Overview of JCA and IMS TM Resource Adapter
 Socket Connections & Socket Types
 Connection Management
 Security Management
 Transaction Management

Last enhancements
 Supermember
 Hold queue management
PurgeAsyncOutput and ReRoute and Retrieve
Alternate destination

Some IMS V10 Enhancements
 SOA Composite Application
 Accessing SOA applications from IMS (Callout)
24
© 2007 IBM Corporation
IBM Software Group
IMS OTMA Hold Queues
 An OTMA Client can request, at Client Bid time, that OTMA allows each TPIPE to
have a “special” queue, normally referred to as a Hold Queue
 Requested by IMS Connect
 Hold Queues are for Commit Mode 0 only
 Used when a message can not be immediately delivered
 A message on a hold queue will only be sent by IMS when explicitly requested with a RESUME
TPIPE from the client
 Hold Queue is used in following cases
 OTMA client (or its remote client) returns a negative acknowledgement to IMS
 Input to OTMA specifies “Send Only”, but IMS application creates a reply
 An IMS application creates a message - other than the reply message itself - for an OTMA
destination using an Alternate PCB
 The name that identifies a Hold Queue has two components
 The OTMA Client name
 A Remote Client ID which equals the TPIPE name
 In other words, each OTMA Client has its own Hold Queues in IMS
 To retrieve a message on a hold queue, the remote client must issue the RESUME
TPIPE request through the OTMA client to which it is queued
25
© 2007 IBM Corporation
IBM Software Group
Asynchronous Output – Super Member
 A super member is a special OTMA member to keep the IMS Connect
asynchronous messages for a set of IMS Connects
 SMEMBER= on the HWS statement
 Benefit
 IMS asynchronous output messages are sharable for a set of IMS Connects.
 The end users are not aware of this feature.
 Ensures asynchronous output messages available to any instance of IMS Connect running
in a Parallel Sysplex environment
IMS
IMS
IMS Connect A
Member A
(async msgs)
??
IMS Connect A
(with
supermember)
Member A
(async msg)
SuperMember
IMS Connect B
IMS Connect B
Member B
(async msgs)
26
(with
supermember)
Member B
(async msg)
© 2007 IBM Corporation
IBM Software Group
Asynchronous Output – Super Member …
Client Application
RECEIVE_ASYNCOUTPUT
COMMIT MODE=0
CLIENT ID=ABC
Sysplex
Distributor
ABC
IMS Connect
IMS Connect
TMEMBER = ICON1
SMEMBER = XYZ
ABC
With
Super Member
Support
ICON1
IMSA
TMEMBER = ICON2
SMEMBER = XYZ
Hold queue or
Reroute queue
ICON2
IMSB
ABC.ICON1.IMSA
ABC.XYZ
27
© 2007 IBM Corporation
IBM Software Group
Asynchronous Messages – Purge or Reroute
 Asynchronous messages appears on a hold queue when
 Undelivered commit mode 0 output messages (e.g. during timeout or secondary
outputs)
 Secondary output from program-to-program switch (primary interaction can be
Commit Mode 1 or Commit Mode 0)
 Application inserts to ALT PCB
 Handling
 Purge
The output is discarded from the current queue (OTMA TPIPE)
This is the default option
 Reroute
The output is moved from the current queue to a user specified destination
Can be retrieved asynchronously
 Retrieving
 Two modes: Single no wait, single wait
Dedicated Client name vs Alternate Client ID
28
© 2007 IBM Corporation
IBM Software Group
Asynchronous Messages – Purge or Reroute …
Earlier
Support
Client application
ABC
SEND_RECEIVE
COMMIT MODE=0
CLIENTID=ABC
Sysplex
ABC
Distributor
ABC
IMS Connect
TMEMBER=ICON1
ICON1
IMSA
IMS Connect
TMEMBER=ICON2
Hold or Reroute
queue
ICON2
IMSB
ABC.ICON1.IMSA
ABC.ICON2.IMSB
29
© 2007 IBM Corporation
IBM Software Group
Asynchronous Messages – Purge or Reroute …
 New options supported on shareable persistent socket connections only
 PurgeAsyncOutput
 IMSInteractionSpec property: purgeAsyncOutput
TRUE (default) means purge undeliverable CommitMode 0 output
FALSE means queue undeliverable CommitMode 0 output to:
– “reRoute” Tpipe if specified, or
– Tpipe with name of shareable persistent socket connection
 reRoute
 Used only when purgeAsyncOutput is FALSE
 IMSInteractionSpec properties: reRoute and reRouteName
TRUE causes undelivered Commit Mode 0 output to be queued to Tpipe whose name
matches specified reRouteName
FALSE (default) causes undelivered Commit Mode 0 output to be queued to Tpipe
whose name matches generated clientID of shareable persistent socket connection
30
© 2007 IBM Corporation
IBM Software Group
Asynchronous Messages – Retrieve
 Use Interaction Verb SYNC_RECEIVE_ASYNCOUTPUT_xx
 Two modes
 SINGLE
Retrieves one message per interaction if a message available at the time of the
request
 SINGLE_WAIT
Retrieves one message per interaction
Will wait for a specified time for message to appear on the hold queue
 Specify hold queue name
 using the Client ID property with dedicated connection
 using the Alternate Client ID (reRoute Name) property with sharable connections
31
© 2007 IBM Corporation
IBM Software Group
Asynchronous Messages – Alternate Client ID Support
 When WAS application issues a RESUME TPIPE, it can use a shareable
socket and specify an Alternate Client ID
 Enables application to use a shareable socket to retrieve asynchronous
output messages that are queued to any specified clientID
 undelivered CM0 output
 ALTPCB output messages
 Simplifies writing of server application (“listener”) that retrieves
messages for one or more hold queues
 With this support, it is now possible to use shareable sockets in every
case, and so avoid problems associated with Sysplex Distributor
 IMS V10 adds new security check for RESUME TPIPE
 Check the userid associated with input message is authorised to access specified
TPIPE (alternate client ID)
32
© 2007 IBM Corporation
IBM Software Group
Asynchronous Messages – Alternate Client ID Support …
 In this example, a SEND_ONLY transaction is used to create a message on a hold
queue, which is then retrieved by exploiting the alternate clientID support
 CM0 and Shareable sockets used in both cases
Java Client
execute()
IMS TM Resource
Adapter
SYNC_Send_Only
send
Reroute=CLIENT1
IMS
Connect
SOCKET ID
HWSABC01
IMS
TPIPE
HWSABC01
Appl
Pgm1
IOPCB
execute() SYNC_RECEIVE_ASYNCOUTPUT
send
For CLIENT1
receive
Output
MSG1
Java Client
ACK
Output
MSG1
SOCKET ID
HWSABC02
TPIPE
HWSABC02
HOLDQ
CLIENT1
• MSG1
Retrieve options are “Single wait ” or “Single no wait”
33
© 2007 IBM Corporation
IBM Software Group
Other Related Enhancements
 OTMA provides Flood Control (PK04461 for V8, PK04463 for V9)
 Partial retrofit of an IMS V10 enhancement
 /START TMEMBER member_name INPUT nnnnn
Where nnnnn is maximum number of messages from the OTMA client that can be in
process
 TPIPE Storage Clean Up (PQ99983 for V8, PK00386 for V9)
 A Tpipe will be removed if is has been IDLE for two consecutive checkpoints
34
© 2007 IBM Corporation
IBM Software Group
Agenda

Overview of JCA and IMS TM Resource Adapter
 Socket Connections & Socket Types
 Connection Management
 Security Management
 Transaction Management

Last enhancements
 Supermember
 Hold queue management
PurgeAsyncOutput and ReRoute and Retrieve
Alternate destination

Some IMS V10 Enhancements
 SOA Composite Application
 Accessing SOA applications from IMS (Callout)
35
© 2007 IBM Corporation
IBM Software Group
 IMS SOA composite business application support
 Asynchronous Callout to EJB
 Enterprise Workload Manager (EWLM)
 Ping support
 CM0 Ignore PURG
 Resume Tpipe Security
 RACF Mixed Case Password
36
© 2007 IBM Corporation
IBM Software Group
ITRA - IMS 10 enhancements
 Asynchronous Callout
 Allows IMS application to act as a client by issuing ISRT ALTPCB to send the callout request
 Conversational Composite Business Application
 Ability to create conversational business process application
 Enterprise Workload Manager (EWLM)
 Ability to track workflow from WAS
LLLL | IRM | OTMA User Data (EWLM 64 byte correlator) | LLZZ TRANCODE data | EOM
 RACF Password Change
 Ability to change RACF password after expiration
LLLL | IRM | OTMA | LLZZ HWSPWCH old-password/new-password1/new-password2 | EOM
 Ping
 Determine IMS Connect availability
 CM0 Ignore PURG
 Provides CM1 and CM0 consistent output message processing
 Resume TPipe Security
 Authorized retrieval on output messages
37
© 2007 IBM Corporation
IBM Software Group
IMS Callout Support
 IMS Applications can call an external application
 ALTPCB ISRT (for asynchronous processing only in IMS
or APPC)
 MQ calls
 TCP/IP sockets calls
 APPC calls
 Use caution when executing synchronously
 Ties up region and its associated control blocks, and potentially holds locks on DB
data
 Some customers have been asking for additional techniques typical of
web based solutions
 First provided in IMS V10
38
© 2007 IBM Corporation
IBM Software Group
IMS V10 Callout Support
IMS
Asynchronous outbound support from IMS applications using ALTPCB
1. Asynchronous Callout to EJB

Customer provides “listener code” in JCA EJB application
2. Asynchronous Callout to Message Driven Bean (MDB)

Use JCA 1.5 inbound architecture support – MDB acts as listener, and
calls appropriate service or routine

End-to-end tooling available
z/OS
Initiating
Client
IMS
Application
Callout
Another Txn
3. Outbound Web Services support in IMS SOAP Gateway

IMS SOAP Gateway acts as listener and calls Web Service

WDz tooling used to read WebService Description and generate IMS
message definition and XML transformation routine
In each case, a reply from the called service will be processed by a
new IMS transaction
Any
platform
IMS Resource
Adapter
EJB /
Web Service
39
© 2007 IBM Corporation
IBM Software Group
IMS V10 Callout Support …
IMS
WAS
(IMS TM
Resource
Adapter)
•IMS Connect clients
BMP trans, MSC, ISC
Non-IMS Connect
input trans from MQ via
OTMA, SNA via APPC,
LU0, LU6.2 or Terminal
IMS
Application 1
ISRT
ALTPCB
IMS
Application 2
output
MDB
Resume
Tpipe with
Alternate
Client ID
Hold
Q
OTMA
Destination
Routing
EJB
OTMA
Resume
Tpipe
Security
IMS
Connect
IMS SOAP
Gateway
Web
Service
Other callout alternatives: MQ, DB2, APPC, JMP/IIOP
40
© 2007 IBM Corporation
IBM Software Group
SOA Composite Business Applications (IMS V10)
 For IMS conversations
 Conversation ID uncoupled from
Process
Loan App
connection
 Supports easy integration of IMS
conversational transactions into SOA
Composite Business Applications
developed in WID
Complete
Loan
Credit
Check
Decline
Loan App
 Better support for connection sharing
and management
41
© 2007 IBM Corporation
IBM Software Group
How do I get IMS TM Resource Adapter?
 Rational Application Developer v 6.0
 http://www.ibm.com/developerworks/rational/products/rad/
 WebSphere Integration Developer v 6.0
 http://www.ibm.com/software/integration/wid/
 IMS Integration Suites
 http://www.ibm.com/software/data/ims/toolkit/
 Access to information and download runtimes for:
IMS TM Resource Adapter
IMS MFS Solutions
IMS SOAP Gateway
 Articles of interest
 http://www.ibm.com/developerworks/rational/library/05/0920_nigul/
Generating a J2C bean using RAD
42
© 2007 IBM Corporation
IBM Software Group
Final Thoughts
 Service Oriented Architecture has revolutionized the way business is
done
 Standard interfaces and qualities of service inherent in SOA have made integration of
IT assets and heterogeneous systems a reality
 IMS is well positioned as a major player in this space with a variety of
technologies that project IMS assets into the SOA foundation model
 IMS JDBC and XML-DB/XQuery
 IMS DB resource adapter
 IMS TM resource adapter
 IMS SOAP Gateway
 Additional web services support for MFS based transactions
43
© 2007 IBM Corporation
IBM Software Group
More on application development tools
44
© 2007 IBM Corporation
IBM Software Group
Development Tools Transitioning from the past
Integration developers using WSAD-IE today
would likely transition to WID
• J2EE/Integration Developer
• Build Integration applications
• Use JCA 1.0 IMS Resource
Adapter
• Deploy to WAS
• Integration Developer
• Compose Business Integration
solutions
• Use JCA 1.5 IMS Resource
Adapter
• Deploy to WebSphere Process
Server
WSAD-IE v 5.1.1
• Java/J2EE developer
• Build J2EE applications
J2EE developers using WSAD-IE today
would likely transition to RAD
45
• Use JCA 1.0 or 1.5 IMS
Resource Adapter
• Deploy J2EE apps to WAS
© 2007 IBM Corporation
IBM Software Group
Rapid Application Development
46
© 2007 IBM Corporation
IBM Software Group
RAD - J2C Feature
1. Map the message

Generate Data binding classes for data
transformation

Transform Java/Web Service data types
to IMS application data types
2. Build the Bean

Generate Java classes for interaction

Connect and invoke IMS transaction
3. Wrap the app
47

Wrap Java classes as J2EE or Web
Service

Make your IMS transaction accessible
as Web Services or from J2EE
application
© 2007 IBM Corporation
IBM Software Group
RAD - J2C Feature - Mapping the message
‘Green screen’
48
COBOL copybook
© 2007 IBM Corporation
IBM Software Group
RAD - J2C Feature - Wrapping the Web Service
Java data binding
49
WSDL
© 2007 IBM Corporation
IBM Software Group
Service Component Architecture
 Based on J2EE
 Service Components
 Service Data Objects
 Programming model for building
business processes in a service
oriented way
 Value
SDO
Service
Component
 Lowers the barriers for a developer to
enter the world of SOA and become
productive
 J2EE and Web Service skills not
required to create sophisticated business
applications
 Makes the experienced J2EE developers
more productive.
50
© 2007 IBM Corporation
IBM Software Group
WebSphere Integration Developer (WID) Tooling
Enterprise
Discovery
Import
Test
&
Deploy
Configure
51
Wire
© 2007 IBM Corporation
IBM Software Group
WebSphere Integration Developer (WID) Tooling …
 Simplify and accelerate the
development of integrated
applications
 Implements Service Component
Architecture technology and business
process choreography
 Industry-standard service-oriented
architecture
52
© 2007 IBM Corporation
IBM Software Group
WID - Building a Web Service
1.
2.
3.
Map the message
4.
Integrate into a flow (business
process)
Build the bean
Wrap the application as a web
service
Service (IMS)
Service (JavaMail)
Service (J2EE)
Service (JavaMail)
53
© 2007 IBM Corporation