Post on 16-Apr-2017
IBM z/OS Connect Enterprise Edition V2.0Technical overview
rcjones@uk.ibm.com
Rob Jones, CICS strategy – z/OS Connect and API enablement
December 22nd, 2015
twitter.com/UkRobJones
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.
3
Agenda
• What’s new?
• z/OS product runtime: anatomy & set up
• z/OS Connect EE API Editor: workstation tooling
• A new pricing metric
• Further reading
Naturally RESTful APIs for z Systems
IBM z/OS Connect Enterprise Edition V2.0.0.0
5
CICS
IMS
WAS
MQ1
DB21
REST APIconsumers
z/OS
Create and deliver natural REST APIs for z Systems assets in a unified manner across z/OS subsystems with integrated auditing, security and scalability
IBM z/OS Connect Enterprise Edition10,000ft conceptual view
API Management
Mobile apps
Web apps
Cloud / Bluemix apps
1 per ENUS215-493 Statement of Direction
6
What is IBM z/OS Connect Enterprise Edition?
IBM z/OS Connect Enterprise Edition (EE) V2.0 is the latest evolution of z/OS Connect. z/OS Connect EE V2.0 is a priced offering, orderable via ShopzSeries as PID 5655-CEE.
z/OS Connect EE V2.0 includesA dedicated Liberty profile for z/OS
• GA release includes Liberty V8.5.5.7New Eclipse-based tooling for API composition with SWAGGER
• Delivered through IBM Explorer for z/OS V3.0 AquaThe WOLA service provider for access to CICS and BATCH
• Including the WOLA Liberty featureUtilities to generate service archives for use with CICS programs
• Creates JSON schemas as input for API compositionThe REST client for access to “3rd party” REST services
• e.g. JAX-RS applications hosted on WAS for z/OS
Announce (ENUS215-493) Dec 1st, 2015 – GA Dec 11th, 2015
Announcement letter ENUS215-493
ibm.biz/zosconnect20_announce
IBM intends to deliver IBM z/OS Connect Enterprise Edition (EE) components and technologies through continuous delivery of new features in the coming months.
IBM intends that a future release of IBM CICS Transaction Server for z/OS (CICS TS) will provide support for z/OS Connect EE to enable it to execute embedded within CICS TS.
IBM intends that a future release of IBM MQ for z/OS will provide support for both z/OS Connect and z/OS Connect EE.
IBM intends to update IBM System Automation for z/OS V3.5.0 to deliver a new sample policy to allow automated operations and restart of z/OS Connect and z/OS Connect EE.
IBM intends that a future release of IBM IMS Enterprise Suite will provide support for z/OS Connect EE.
IBM intends to offer IBM DB2 for z/OS Version 11, or later, with support for the external interface delivered in z/OS Connect EE V2.0, and DB2 RESTful API support that is fully integrated into the DB2 for z/OS Distributed Data Facility.
Statements of general direction ENUS215-493, December 1st, 2015
8
IBM IMS Enterprise Suite V3.2.1Delivers day-one support for z/OS Connect EE V2.0
IBM z/OS Connect Enterprise Edition (EE) V2.0 is the latest evolution of z/OS Connect. z/OS Connect EE V2.0 is a priced offering, orderable via ShopzSeries as PID 5655-CEE.
IMS Enterprise Suite V3.2.1 includes
IMS Mobile Feature Pack for z/OS Connect Enterprise Edition • The IMS mobile feature (service provider) for z/OS Connect EE,
enabling integration of IMS Transactions with z/OS Connect EE
IMS Explorer for Development• Support for generating service archives for use with IMS transactions
IMS Enterprise Suite 3.2 Knowledge Center
9
z/OS Connect EE vision statementsA unified end to end story for naturally RESTful APIs and z/OS subsystems
API compositionAn API developer can create a natural REST API using a selection of existing or new assets without being forced to write any new code in single common tooling experience
API deploymentAPI deployment can be automated by extending an existing enterprise change control process, or performed manually
API discoveryA standard user of the IBM APIM Portal can locate APIs hosted in z/OS Connect using business relevant context and place them under management without having to interact with any of the provider systems
What’s in a URI ? JSON-RPC style service vs. a “naturally RESTful” API (extreme example)
Basic service enablementURI conveys service, maybe method, payload can convey everything!
Create a new accountPOST /orders/createAccBODY name(Fred), address(…RESPONSE accNum=9999
Review status of an orderPOST /orders/orderStatusBODY accnum=9999,invoice=380ZRESPONSE result=Stock 5 days
Delete an accountPOST /orders/delAccountBODY accnum=9999RESPONSE result=OK
Modelling for naturally RESTful APIs HTTP verb conveys operation, URI conveys resource
Create a new accountPOST /orders?name=FredBODY address(…RESPONSE /orders?accnum=9999HTTP status 200Review status of an orderGET /orders?accnum=9999&invoice=380ZBODY <none>RESPONSE result=Stock 5 daysHTTP status 200Delete an accountDELETE /orders?accnum=9999RESPONSE <none>HTTP status 200
POST
GET
DELETE
What’s in a URI ? JSON-RPC style service vs. a “naturally RESTful” API (extreme example)
Basic service enablementURI conveys service, maybe method, payload can convey everything!
Create a new accountPOST /orders/createAccBODY name(Fred), address(…RESPONSE accNum=9999
Review status of an orderPOST /orders/orderStatusBODY accnum=9999,invoice=380ZRESPONSE result=Stock 5 days
Delete an accountPOST /orders/delAccountBODY accnum=9999RESPONSE result=OK
Modelling for naturally RESTful APIs HTTP verb conveys operation, URI conveys resource
Create a new accountPOST /orders?name=FredBODY address(…RESPONSE /orders?accnum=9999HTTP status 200Review status of an orderGET /orders?accnum=9999&invoice=380ZBODY <none>RESPONSE result=Stock 5 daysHTTP status 200Delete an accountDELETE /orders?accnum=9999RESPONSE <none>HTTP status 200
POST
GET
DELETE
“Related services” versus a RESTful APIConsumer view
z/OS Connect V1 SOR (CICS/IMS/MQ/…)Service A z-asset AREST service uri A
Service B z-asset BREST service uri B
Service C z-asset CREST service uri C
Service D z-asset DREST service uri D
Service-oriented view: independent collection of individual services
Consumer view z/OS Connect EE V2 SOR (CICS/IMS/MQ/…)
z-asset AREST API X uri + parms
z-asset BREST API X uri + parms
z-asset CREST API X uri + parms
z-asset DREST API X uri + parmsAP
I X S
WAG
GER
API m
appi
ng m
odel Service A
Service B
Service C
Service D
API-oriented view: a consistent REST API masking underlying asset composition
REST API designed independent of underlying z-assets
Service interface reflects underlying assets
REST service uri D Service D
13
SWAGGER pet store example http://petstore.swagger.io
14
IBM z/OS Connect Enterprise EditionComponent view – what comes in the box
z/OS Connect dedicated Liberty
z/OS Connect product
feature V2.0
service providerfeatures
WOLA
API composition tooling for Eclipse
RESTclient
API deployment scriptable interface
WOLA service provider is includedas a Liberty feature in the z/OS Connect EE product (+ the base WOLA feature)
REST client service providerallows integration of REST services, using z/OS Connect as a proxy
Angel The Liberty angel runtime is included with z/OS Connect EEProvides authorized services
Create API packages and iteratively deploy for testing
Automate deployment of API packages with target-specific customizations
SMF89 registration &usage records
15
IBM z/OS Connect Enterprise EditionComponent view – extending z/OS Connect EE
z/OS Connect dedicated Liberty
z/OS Connect product
feature V2.0
service providerfeatures
WOLA
API composition tooling for Eclipse
RESTclient
API deployment scriptable interface
WOLA service providerREST client service provider
Angel The Liberty angel runtime is included with z/OS Connect EEProvides authorized services
Create API packages and iteratively deploy for testing
Automate deployment of API packages with target-specific customizations
SMF89 registration &usage records
Extra SPs
CICS, MQ, DB2 plan to ship further service provider implementations for deployment with z/OS Connect EE
IMS Enterprise Suite 3.2.1includes IMS Mobile Feature Pack for z/OS Connect Enterprise Edition
IBM z/OS Connect Enterprise EditionAPI requests – API packages, mapping and transformation
Consumer view z/OS Connect EE V2 SoR
z-asset APOST
z-asset BGET
z-asset CPUT
z-asset DDELETE
API package
Create-service
Read-service
Update-service
Delete-service
/myapi/resource/{id}
HTTPHeaders
+ JSON
AP
I m
appi
ng
mod
el
Discover APIswith SWAGGER
description
Consumers can use SWAGGERto generate API client code
Service archive
SoR-specificutilities
containing e.g. CICS WSBind, IMS meta-data
Export API
z/OS Connect EE API editor
JSON / SoR
xforms
(.sar)
(.aar)
Import
z/OS product runtime anatomy
Post-SMP/E install, setup,and starting the server
z/OS Connect EE install anatomyPost-SMP/E install + creation of product read/write file system
/usr/lpp/IBM/zosconnect/v2r0 bin runtime
lib com.ibm.zosconnect
<zosconnect feature files>
wlp etc
/var/zosconnect
Not quite ready for first use…
SMP/E maintained, read-only
Read-write
z/OS Connect EE install anatomyAfter post-install script “zconsetup”
/usr/lpp/IBM/zosconnect/v2r0 bin runtime
lib com.ibm.zosconnect
<zosconnect feature files>
wlp etc
extensions
/var/zosconnect v2r0
extensions zosconnect.properties
Post-install: Create USS symlink After SMP/E install has completed, the post-install shell script zconsetup is used to create the extensions folder as a symlink to /var/zosconnect/v2r0/extension. This directory contains the Liberty feature properties files used at run-time for both z/OS Connect, and any additional Liberty product features (e.g. IMS mobile).
The target location of the extensions directory symlink is restricted to being /var/zosconnect/v2r0.
The z/OS Connect EE administrator must create the /var/zosconnect file system if it does not already exist.
symlink
Ready to create servers…
z/OS Connect EE install anatomyCreating server instances
/usr/lpp/IBM/zosconnect/v2r0 bin runtime
lib com.ibm.zosconnect
<zosconnect feature files>
wlp etc
extensions
/var/zosconnect v2r0
extensions zosconnect.properties
servers server1 server2
symlink
Server instancesBy convention, server instance directories are stored under /var/zosconnect/servers. This location can not be modified (*Known limitation*).
Note: Server directories are entirely independent of the extensions symlink and service provider properties files
z/OS Connect EE install anatomyAdditional Liberty product features
/usr/lpp/IBM/zosconnect/v2r0 bin runtime
lib com.ibm.zosconnect
<zosconnect feature files>
wlp etc
extensions
/var/zosconnect v2r0
extensions zosconnect.properties imsmobile-v2.properties mq-provider.properties db2-provider.properties isv-provider.properties
servers server1 server2
symlink
/usr/lpp/ims/r14 zoscon-SP
lib imsmobile-v2
<IMS SP feature files>
…
Additional product featuresIn this example, the IMS mobile service provider for z/OS Connect V2 is a Liberty product feature, maintained by an IMS SMP/E install. Alternatively it could be a feature-manager installed to a non-SMP/E maintained location on the z/OS UNIX file system.
Additional Liberty feature properties must specify the absolute path to their folder
containing lib/<feature name>
z/OS Connect EE install anatomyThe full picture!
/usr/lpp/IBM/zosconnect/v2r0 bin runtime
lib com.ibm.zosconnect
<zosconnect feature files>
wlp etc
extensions
/var/zosconnect v2r0
extensions zosconnect.properties imsmobile-v2.properties mq-provider.properties db2-provider.properties isv-provider.properties
servers server1 server2
Post-install: Create USS symlink After SMP/E install has completed, the post-install shell script zconsetup is used to create the extensions folder as a symlink to /var/zosconnect/v2r0/extension. This directory contains the Liberty feature properties files used at run-time for both z/OS Connect, and any additional Liberty product features (e.g. IMS mobile).
The target location of the extensions directory symlink is restricted to being /var/zosconnect/v2r0.
The z/OS Connect EE administrator must create the /var/zosconnect file system if it does not already exist.
symlink
Server instancesBy convention, server instance directories are stored under /var/zosconnect/servers. This location can not be modified (*Known limitation*).
Note: Server directories are entirely independent of the extensions symlink and service provider properties files
/usr/lpp/ims/r14 zoscon-SP
lib imsmobile-v2
<IMS SP feature files>
…
Additional product featuresIn this example, the IMS mobile service provider for z/OS Connect V2 is a Liberty product feature, maintained by an IMS SMP/E install. Alternatively it could be a feature-manager installed to a non-SMP/E maintained location on the z/OS UNIX file system.
Additional Liberty feature properties must specify the absolute path to their folder
containing lib/<feature name>
z/OS Connect EE runtimeA brief glimpse… server.xml created from the supplied template
z/OS Connect EE runtimeA brief glimpse… starting the z/OS Connect EE server
z/OS Connect EE API Editor
API composition
z/OS Connect EE API EditorEclipse based tooling delivered by Aqua
New Eclipse perspective for supported Eclipse 4.4-based runtimes:
• IBM Explorer for z/OS V3.0 Aqua• IBM IMS Explorer for Development V3.2• IBM CICS Explorer® V5.3
IBM z/OS Explorer V3.0 AquaComposite update site hosts compatible versions of Eclipse platforms & plugins
Release train delivering compatible versions of Eclipse platforms & plugins for IBM tooling on z/OS.
16 products on December 11th, 2015
http://mainframe.developer.ibm.com
z/OS Connect EE API EditorComposing an API from service archives Service
archive
SoR-specificutilities
containing e.g. CICS WSBind, IMS meta-data
Import SAR files to z/OS Connect EE API Editor
SoR-specific utilities for SAR generation
IMS Explorer for Development (shown)• IMS Transaction data xforms
BAQJS2LS / BAQLS2JS utilities (supplied)• CICS program data xforms
Ready for API composition….
z/OS Connect EE API EditorAPI composition: start with service archives
z/OS Connect EE API EditorAPI composition: mapping HTTP headers and JSON data
z/OS Connect EE API EditorAPI composition: export API package as API archive (AAR)
API archive includes generated SWAGGER 2.0
Upload the API archive to zFS and deploy using the apideploy command
z/OS Connect EE API EditorAPI composition: Generated SWAGGER (shown in SWAGGER editor)
A new pricing metric
Tiered, simultaneous instance-based pricing
34
What about pricing?
It is IBM’s intention that z/OS Connect EE will introduce an innovative new pricing model on z Systems.
“per instance” pricing metric
• Based upon the maximum number of active concurrent address spaces
• Tiered usage bands • provides increasing value as the size of an overall
deployment rises; low cost of entry for small projects
• Auditing is required through SMF89-2 records • hourly snapshots of the number of concurrent
instances, reports created with utility IFAURP
35
What about pricing?Value Unit exhibit VUE037 (from announcement letter ENUS215-493)
Number of Simultaneous Instances
VUs per Simultaneous Instance
1 to 4 1 VU per Simultaneous Instance
5 to 10 4 VUs + 0.6660 VUs per Simultaneous Instance > 4
11 to 20 8 VUs + 0.4000 VUs per Simultaneous Instance > 10
21 to 40 12 VUs + 0.2000 VUs per Simultaneous Instance > 20
41 to 100 16 VUs + 0.0660 VUs per Simultaneous Instance > 40
101 to 250 20 VUs + 0.0260 VUs per Simultaneous Instance > 100
251 to 500 24 VUs + 0.0160 VUs per Simultaneous Instance > 250
501 to 1000 28 VUs + 0.0080 VUs per Simultaneous Instance > 500
1001 to 3000 32 VUs + 0.0020 VUs per Simultaneous Instance > 1000
>3000 36 VUs + 0.0007 VUs per Simultaneous Instance > 3000
36
IFAURP usage reportsMaximum Concurrent Product Registrations – from SMF 89 Type 2
Measured Usage and S/390 Usage Pricing Charges Page 2IFAURP 4.1.2 Software Product Registration Report 14 DECEMBER 2015------------------- Customer No: ------------------- -------------- Software Vendor: IBM CORP --------------- ACME CICS COMPANY CELL BLOCK A HURSLEY, WINCHESTER Contact/Phone: MR WANNABE / +44 1962 815000 ---------------------------- Processor ---------------------------- Category Type-Serial Model Begin-End Dates ---------- ---------- --------------- ----------------- Machine 2964-8E8C7 NE1 13Dec15 - 14Dec15 2964 CEC 2964-8E8C7 7A5 13Dec15 - 14Dec15 ----------------- Maximum Concurrent Product Registrations ---------------------------------- Product ----------------------2015 2016 Name Feature Version Number L| Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec ---------------- ---------------- -------- -------- -|---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- Max MVS/ESA LPARs:| 1 - - - - - - - - - - - - Percent Missing Hours:| 97 - - - - - - - - - - - - | # 13Dec15 | | z/OS Connect z/OS Connect 02.00.00 5655-CEE F| 19# - - - - - - - - - - - - # 13Dec15 | | ============================================================= Notes ================================================================ # - Data not collected for a full month. N/A - Product registration counts are not available. (01) - Not eligible for Measured Usage charges.
//IFAURP EXEC PGM=IFAURP,REGION=0M,PARM='PRODUCT'//STEPLIB DD DSN=SYS1.SIFALIB,DISP=SHR
37
IFAURP usage reportsMaximum Concurrent Product Registrations – SMF 89 Type 2
Measured Usage and S/390 Usage Pricing Charges Page 2IFAURP 4.1.2 Software Product Registration Report 14 DECEMBER 2015------------------- Customer No: ------------------- -------------- Software Vendor: IBM CORP --------------- ACME CICS COMPANY CELL BLOCK A HURSLEY, WINCHESTER Contact/Phone: MR WANNABE / +44 1962 815000 ---------------------------- Processor ---------------------------- Category Type-Serial Model Begin-End Dates ---------- ---------- --------------- ----------------- Machine 2964-8E8C7 NE1 13Dec15 - 14Dec15 2964 CEC 2964-8E8C7 7A5 13Dec15 - 14Dec15 ----------------- Maximum Concurrent Product Registrations ----------------- ----------------------- Product ----------------------2015 2016 Name Feature Version Number L| Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec ---------------- ---------------- -------- -------- -|---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- Max MVS/ESA LPARs:| 1 - - - - - - - - - - - - Percent Missing Hours:| 97 - - - - - - - - - - - - | # 13Dec15 | | z/OS Connect z/OS Connect 02.00.00 5655-CEE F| 1# - - - - - - - - - - - - # 13Dec15 | | ============================================================= Notes ================================================================ # - Data not collected for a full month. N/A - Product registration counts are not available. (01) - Not eligible for Measured Usage charges.
----------------------- Product ----------------------2015Name Feature Version Number L| Dec---------------- ---------------- -------- -------- -|---- Max MVS/ESA LPARs:| 1 Percent Missing Hours:| 97 | # 13Dec15 | |z/OS Connect z/OS Connect 02.00.00 5655-CEE F| 19# # 13Dec15 | |============================================================= # - Data not collected for a full month.N/A - Product registration counts are not available.(01) - Not eligible for Measured Usage charges.
38
z/OS Connect EE – supplied interceptorsAuthorization and auditing
SAF/LDAP – Authorization interceptorControls access to both APIs and Services• Groups are identified in config
• Admin• Operators• Invokers
AuditSMF – Audit interceptorCreates one SMF 123 Type 1 record per request• API/Service called + URI• Request / Response Payload size, time stamps• Request ID• User ID + mapped user name
39
z/OS Connect EE – supplied interceptorsAuthorization and auditing
AuditSMF – SMF 123 Type 1 detail
Length Data Type Description4 Binary Version of this section of the SMF record8 Store Clock (STCK) Arrival date and time8 Store Clock (STCK) Completion date and time
64 Character Target URI (EBCDIC, right padded with blanks)
4 Binary Request payload length in bytes
64 Character API or Service name (EBCDIC, right padded with blanks)
8 Character Method (EBCDIC)4 Binary Response payload length in bytes
64 Character User name (EBCDIC, right padded with blanks)
23 Binary Request id (bytes, right padded with zeros)1 Boundary padding (zero)
64 Character Service grouping name (EBCDIC, right-padded with blanks)
8 Character Mapped user name (EBCDIC, right-padded with blanks)
40
z/OS Connect EE – supplied interceptorsRequest level logging
FileSystemLogger – Full request loggingProvides complete request level logging including request + response payload data
• Single log file (with rollover) per server• Human readable• Machine readable
41
Want to know more?z/OS Connect EE Knowledge Center
ibm.biz/zosconnect20_kc
Further information
Various additional topics
43
z/OS Connect EE V2.0 PerformanceA sneak preview of our z13-based performance report…
IBM intends to provide Lab-based performance summaries for z/OS Connect EE V2.0, with regular updates aligned with the product continuous delivery lifecycle…
44
What about z/OS Connect V1?
z/OS Connect V1 will continue to be available for service enablement, but does not include tooling or run-time support for APIs.
The following offerings will continue to include the z/OS Connect V1 Liberty feature:
• WebSphere Application Server for z/OS • IMS Enterprise Suite, Mobile Feature pack• CICS Transaction Server for z/OS
strongloop.com/strongblog/node-js-ibm-acquisition
Stop press! News from September 10th, 2015
Analytics for Monetization
Socialization
Subscription Management
Performance MetricsReal-time production
monitoringProfiler
Root cause CPU & Memory
StrongLoop Arc
API LIFECYCLE
IBM API Management
Build and Deploy
Automate Lifecycle
Policy Authoring & Management
Process ManagerScale APIs
SecurityAPI Gateway
Policy Enforcement
Discovery
API ComposerVisual modeling
StrongLoop Arc + IBM API Management = Full API Lifecycle
47
z/OS Connect support for node.js developers
Introducing the z/OS Connect for node.js project. Want to contribute to it’s evolution? It’s happening in the open…
JavaScript programmers eat and breathe JSON & REST; node.js is now the de-facto runtime framework used on the server. Today, node.js is available on many platforms, including Linux on z Systems.
github.com/zosconnect/zosconnect-node www.npmjs.com/package/zosconnect-node
A wrapper service for z/OS® Connect, enabling node applications to discover and access IBM z Systems resources that are service-enabled by z/OS® Connect.
ibm.biz/zAPI_Guide
Further information
Background readingIf you think RESTful is what happens on a Sunday afternoon…
Some useful online materials…
HTTP Basics (Nanyang Technological University)https://www3.ntu.edu.sg/home/ehchua/programming/webprogramming/HTTP_Basics.html
A useful primer in HTTP protocol basics
RESTful Web Services: A Tutorial (Dr. Dobbs)http://www.drdobbs.com/web-development/restful-web-services-a-tutorial/240169069
Very well constructed tutorial of RESTful concepts framed in terms of the HTTP protocol
Introducing JSONhttp://www.json.org/ - Brief technical summaryhttps://msdn.microsoft.com/en-us/library/bb299886.aspx - A little “old” (2007) but well written
Implementing IBM CICS JSON Web Services for Mobile Applicationshttp://www.redbooks.ibm.com/redbooks/pdfs/sg248161.pdf
z/OS Connect V1 update
z/OS Connect V1 has been updated with each Liberty fix pack since 855FP2
CICS TS V5.2 (APAR PI45532) + V5.3Based on CICS Liberty V8.5.5 FixPack 6/7, z/OS Connect V1.0
4Q15
IMS Enterprise Suite for z/OS, V3.2.1Based on Liberty V8.5.5 FixPack 7, z/OS Connect V1.0
4Q15
WAS z/OS V8.5.5 FixPack 8
Includes z/OS Connect V1.0 and V1.2
4Q15
What is the latest level for z/OS Connect V1?
IBM DB2 Accessories Suite for z/OS, V3.3Based on CICS Liberty V8.5.5 FixPack 7, z/OS Connect V1.0
4Q15
New!
IMS
HTTP server: WebSphere Liberty on z/OSData transform: CICS WSBind / IMS xform+bind metadataCICS integration: WebSphere Optimized Local Adapter
(WOLA)IMS integration: IMS Connect Batch integration: WOLA (not shown)
z/OS WebSphere Liberty
z/OS Connect z/OS Connect
z/OS Connect
JSON transform
WOLA
Binary data
CICS TSHTTP
JSON data
WOLA service provider
PROG A
JSON transform
JSON data
Binarydata
JSON transform
IMS Connect
IMS service provider
TRAN B
Binary data
z/OS Connect V1 topology #1: WAS z/OS Connect
HTTP server: IMS Mobile Feature PackDedicated WebSphere Liberty Profile for z/OS
Data transform: IMS xform+bind metadataIMS integration: IMS Connect
z/OS
IMS MFP (Liberty)
z/OS Connect z/OS Connect
z/OS Connect
JSON transform
IMS Connect
Binarydata
IMS HTTP
JSON data
IMS service provider
TRAN B
JSON transform
JSON data
Binarydata
z/OS Connect V1 topology #2: IMS Mobile Feature Pack (MFP)
HTTP server: CICS TS z/OS Connect Dedicated CICS Liberty JVM server
Data transform: WSBind filesCICS integration: Direct LINK
z/OS
CICS TS
z/OS Connect z/OS Connect
Liberty JVM server
JSON transform
Direct LINK
Binarydata
JSON data
z/OS Connect
PROG A
JSON transform
JSON data
Binarydata
Now available! CICS TS V5.3 includes embedded z/OS Connect V1
– Also available in CICS TS V5.2 via APAR PI25503+PI32451
HTTPS
z/OS Connect V1 topology #3: CICS TS z/OS Connect
Now available! IBM DB2 Accessories Suite for z/OS, V3.3 includes embedded z/OS
Connect V1– From December 11th, 2015 Announcement letter
ENUS215-381
z/OS Connect V1 topology #4: IBM DB2 Adapter for z/OS connect