IMS Integration Architecture in Short November 2018 · IMS Presentation Layer (MFS) –Description of input and output messages and device map –Not used in client/server implementations
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
� IMS Batch–BMPs Msg Driven or non Msg Driven –Standalone (no picture here)
� Access to Resource Managers (RM)– IMS database – Hierarchical data model–DB2 database – Relational data model–MQ Queues–Web Services using WOLA – WebSphere
Optimized Local Adapter–JSON/Rest using z/OS Connect–Rules using zRES & ODM
� IMS Presentation Layer (MFS) –Description of input and output
messages and device map–Not used in client/server implementations
B
D
P
IMS ConnectWMQ
Apps
IMS Transaction
Manager
IMS Data Comm.
APPC/IMS
APPC/MVS
VTAM(LU0 LU1 LU2 LU6.1 LU6.2) TCP/IP for zOSTelnet
WAS – WebSphere Application ServerWOLA - WebSphere z/OS Optimized Local AdaptersIIB – IBM Integration Bus (was WeSphere Message Broker)BPM - IBM Business Process Manager (BPM) Advanced
� An input layer processes the data coming from a client.
–At the end of this process we have an input area filled with EBCDIC characters.
� An orchestration layer analyses the input area and implements a sequence of calls to business logic.
–Usually subroutines ☺
� The business logic layer implements the service, directly calling resource managers
–To access and update data managed by DB2, VSAM, or IMS DB, or eventually send a message to MQ, taking care of delivery to the target resource manager.
� An output layer builds the data to be sent and finishes the unit of work.
–Options: Data is sent back to the client or sent to another IMS transaction (Prog to Prog)
–All updates are committed using the two phase commit protocol.
Build your Microservices on z/OS and benefit of multi-resources update consistency (two-phase
commit)
Leverage “Core z/OS Data” generated by current Apps
Provision your runtime environment on-demand (test, validation &
production)
Use case:Use case:Use case:Use case:Access local externalized Business RulesRequest API (local or remote)Request API (local or remote)Request API (local or remote)Request API (local or remote)Call Mathematical Algorithm / Score
�Asynchronous and synchronous callout capabilities
WAS – WebSphere Application ServerWOLA - WebSphere z/OS Optimized Local AdaptersIIB – IBM Integration Bus (was WeSphere Message Broker)RYO Server - .Net, BizTalk, Oracle SP, SAP, PayPal services, and any application server, etc.