Академический Документы
Профессиональный Документы
Культура Документы
IMS Architecture
IMS Transaction
No presentation layer
Access to Resource Managers (RM)
IMS Database
D
VTAM
Hierarchical design
JDBC access
I
M
S
IMS
Connect
DB2
Stored
Proc.
MFS P
IMS Message
Queues
Appl.
IMS MFS
Description of input and output
messages and device map
Not used in client/server
implementations
WMQ
T
M
XML datastore
Telnet
DB
2
Appl. B
...
IMS Database
Manager
WMQ
z/OS
Agenda
Last enhancements
Supermember
Hold queue management
PurgeAsyncOutput and ReRoute and Retrieve
Alternate destination
J2EE Architecture
Java 2 Platform, Enterprise Edition
A standards-based architecture to enable development of multi-tier distributed applications
Web Container
EJB
Container
Graphic Here
Servlets
RMI / IIOP
HTTP / HTTPS
Web
Browser
Client
JSPs
EJBs
Enterprise
Information
System
(e.g. IMS)
The application
API
CCI
Application
Contract
Managers:
Transaction
Connection
Security
SPI
System
Contracts
Resource
Adapter
EIS
WAS
IMS
TM resource
Adapter
TCP/IP
IMS
Connect
O
T
M
A
IMS
Appls. B
DB2
IMS
DB
Solution Benefits
The Direct Connection Choice!
Prereqs installation of IMS Connect
No changes to IMS applications
The Strategic option for IMS Lab
http://www-306.ibm.com/software/data/db2imstools/imstools/imsjavcon.html
From any WebSphere
platform, z/OS or distributed with J2EE Quality of Services
2007 IBM Corporation
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
z/OS1
XCF
IMS
Connect
Application
Server
IMS Resource
Adapter
IMS
Connect
IMS
IMS
IMS
z/OS2
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
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
Callout (V10)
Make IMS application as a client to
access J2EE applications
2007 IBM Corporation
Socket Connections
In a managed environment, all socket connections between IMS TMRA
and IMS Connect are persistent:
Dedicated persistent *
Client application provides socket identifier using IMSInteractionSpec property clientID
Socket Connections
WebSphere
Application
Server
IMS
TM
RA
Duplicate
ClientId
IMS
Connect
Dedicated persistent
CLIENT01
CLIENT01
Shareable persistent
HWSABC01
HWSXYZ05
HWS22Q0T
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
Types of Interactions
Invoking IMS Transaction or Commands
Send_Receive or Send Only
Execution and Socket timeouts
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)
Types of Interactions
Commit Modes
Send-then-commit (Commit Mode 1)
Used to run non-recoverable IMS transaction
CM1
CM0
ClientID
Socket type
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
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
ACK
IMS
Transaction inserted to
SMB
Ouput Sent
Response requested
Commit Confirmed sent
(Synchpoint has completed)
MPP
GU, IOPCB.
ISRT,IOPCB...
Synchpoint Starts
Synchpoint
Completes
MPP
GU, IOPCB.
ISRT,IOPCB...
Synchpoint Starts
Wait
Synchpoint Completes
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
Output dequeued
Security Management
J2EE provides end-to-end security model for J2EE applications to access
EIS securely
z/OS
Enterprise
Enterprise
Bean
Bean
Res-auth = Container
Security
Security
Manager
Manager
RACF
RACF
IMS
IMS
Resource
Resource
Adapter
Adapter
Send User ID and
Password to IMS Connect
IMS
IMS
Connect
Connect
IMS
OTMA
Security
Security
Manager
Manager
Authenticate
UserID
with RACF
IMS
IMS
Resource
Resource
Adapter
Adapter
Send Security Token to
IMS Connect
Local
Option
RACF
RACF
IMS
IMS
Connect
Connect
IMS
OTMA
Bypass authentication
as user is already
verified
Transactionality
Capability that allows IMS transactions to participate as a resource in two-phase
commit external transactions
Local Environment
WAS, IMS Connect, IMS, and RRS must be in the same
z/OS image **
WAS
Server
platform +
IC4J
Distributed
Protocol
Global
Trans
TCP/IP
YES*
zLINUX
TCP/IP on
Hipersockets
YES*
z/OS
TCP/IP
YES*
z/OS
Local Option
YES **
Resource
ResourceRecovery
Recovery
Service
(RRS)
Service (RRS)
Transaction
Transaction
Manager
Manager
Enterprise
Enterprise
Bean
Bean
1. Uses IMS RA
to invoke IMS
transaction
Single
unit of
work
Debit $100
from Checking
Credit $100
to Savings
2. Executes SQL
stmts to DB2
XA
IMS
IMS
Connect
Connect
SPI
System
Contracts
IMS
IMS
Resource
Resource
Adapter
Adapter
z/OS
IMS
OTMA
TCP/IP
Checking
Account
DB2
DB2
Saving
Account
Enterprise
Enterprise
Bean
Bean
Single
unit of
work
Transaction
Transaction
Manager
Manager
IMS
IMS
Connect
Connect
1. Uses IMS RA
to invoke IMS
transaction
Debit $100
from Checking
Credit $100
to Savings
Resource
ResourceRecovery
Recovery
Service
(RRS)
Service (RRS)
IMS
IMS
Resource
Resource
Adapter
Adapter
z/OS
IMS
OTMA
Local
Option
Checking
Account
2. Executes SQL
stmts to DB2
DB2
DB2
Saving
Account
Timeouts
Socket Timeout
Execution Timeout
Per interaction
Per interaction.
IMS TM
Resource
Adapter
IMS
Connect
IMS
Router
Socket
Agenda
Last enhancements
Supermember
Hold queue management
PurgeAsyncOutput and ReRoute and Retrieve
Alternate destination
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
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
IMSConnectA
MemberA
(asyncmsgs)
??
IMS Connect A
(with
supermember)
MemberA
(asyncmsg)
SuperMember
IMSConnectB
IMSConnectB
MemberB
(asyncmsgs)
(with
supermember)
MemberB
(asyncmsg)
IMS Connect
TMEMBER = ICON1
SMEMBER = XYZ
ICON1
IMSA
ABC
Sysplex
Distributor
ABC
IMS Connect
TMEMBER = ICON2
SMEMBER = XYZ
Hold queue or
Reroute queue
With
Super Member
Support
ICON2
IMSB
ABC.ICON1.IMSA
ABC.XYZ
2007 IBM Corporation
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
ABC
Sysplex
ABC
Distributor
Earlier
Support
ABC
IMS Connect
TMEMBER=ICON1
ICON1
IMSA
IMS Connect
TMEMBER=ICON2
Hold or Reroute
queue
ICON2
IMSB
ABC.ICON1.IMSA
ABC.ICON2.IMSB
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
Java Client
execute()
IMS TM Resource
Adapter
send
SYNC_Send_Only
Reroute=CLIENT1
IMS
Connect
SOCKET ID
HWSABC01
IMS
TPIPE
HWSABC01
Appl
Pgm1
IOPCB
execute() SYNC_RECEIVE_ASYNCOUTPUT
For CLIENT1
send
receive
Output
MSG1
Java Client
ACK
Output
MSG1
SOCKET ID
HWSABC02
TPIPE
HWSABC02
HOLDQ
CLIENT1
MSG1
Agenda
Last enhancements
Supermember
Hold queue management
PurgeAsyncOutput and ReRoute and Retrieve
Alternate destination
Ping
Determine IMS Connect availability
z/OS
Initiating
Client
IMS
Application
Callout
Another Txn
Use JCA 1.5 inbound architecture support MDB acts as listener, and
calls appropriate service or routine
End-to-end tooling available
Any
platform
IMS Resource
Adapter
EJB /
Web Service
IMS
Application 1
(IMS TM
Resource
Adapter)
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
Process
Loan App
connection
Complete
Loan
Credit
Check
Decline
Loan App
Articles of interest
http://www.ibm.com/developerworks/rational/library/05/0920_nigul/
Generating a J2C bean using RAD
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
WSAD-IE v 5.1.1
n
io
t
ra
g
te
In D)
e I
er (W
h
Sp per
b
e lo
W eve
D
R
De atio
ve na
lo l A
pe p
r ( p lic
RA a
D tion
)
Integration Developer
Compose Business Integration
solutions
Use JCA 1.5 IMS Resource
Adapter
Deploy to WebSphere Process
Server
Java/J2EE developer
Build J2EE applications
Use JCA 1.0 or 1.5 IMS
Resource Adapter
Deploy J2EE apps to WAS
COBOL copybook
WSDL
Value
SDO
Service
Component
Enterprise
Discovery
Import
Test
&
Deploy
Configure
Wire
Industry-standard service-oriented
architecture
2.
3.
4.
Service (IMS)
Service (JavaMail)
Service (J2EE)
Service (JavaMail)
2007 IBM Corporation