DSPy a system for AI to Write Prompts and Do Fine Tuning
Z api overview
1. Open APIs for Z Assets
Using IBM z/OS Connect Enterprise Edition
2. • Change in Retail Store’s Role: Inspiration, purchase
point, pickup point, return locations
• 20% of sales and shipments to be picked up at retail
store
• Stores within Stores
• Seasonal Pop-Up Stores
Banking and Financial Services
• Expanding # of non-traditional competitor driving
disruption: Non-Bank entrants, New Payment
Models, New Lending Models, New Depositories
Government Insurers
RetailersAutomotive
• Adoption of mobile devices
• Geopolitical instability & terrorism
• Increased proliferation of social
media platforms & mobile devices
• Government Transparency
Usage-based Insurance:
• Pay-as-you-drive
• Pay-how-you-drive
• Manage-how-you-drive
• Telematics is disrupting the
Automotive Industry with Self-
Driving Automobiles, Vehicle Data,
Traffic/Accident/Weather data
Digital Transformation is required to meet the ongoing disruptions
facing industry markets
3. "We predict US companies alone will spend
nearly $3 billion on API management over
the next five years. Annual spend will
quadruple by the end of the decade, from
$140 million in 2014 to $660 million in 2020.
International sales will take the global market
over the billion dollar mark."
-Forrester, June 2015.
"Within 2 years, at least
one-third of Industry
Clouds will support
industry standard APIs,
helping companies
connect more easily and
securely, accelerating the
Digital Transformation
Economy.”
- IDC FutureScape: Worldwide Cloud 2018
Predictions
“In Three Years, 75% of
Organizations Will Have
Core Cloud API Strategies
as Part of Their Digital
Transformation Architectures
to Enable an API-Driven
Economy, with New Products
Built on Digital Platforms That
Orchestrate Information
Exchange Between Multiple
Organizations in Their
Ecosystems ”
- IDC FutureScape: Worldwide Cloud 2018
Predictions.
API Market Opportunity
§Forrester predicts that the API
Management market will be
$1B by 2019.
§Considering the IBM Z Application
Server market is roughly 20% of
the Application Platform market,
we can see an IBM Z API Market
opportunity of $200M.
4. 4
Key Drivers for APIs
Regulations
& Standards
Architectural
Simplification
Leverage new
digital and
cognitive
services
Participate in
the API
Economy
Business
Agility
• PSD2
• Open healthcare APIs
• Standardize integration layer on
REST / Json
• Simplified integration architecture
with reduced components.
• March towards microservices
architecture
• Enrich your z applications by
consuming cloud native services
• Watson – cognitive services
• Google – Location, etc.
• Payment gateway (apple pay)
• Partner APIs
• Publish APIs from your app
assets for wider consumption.
• Monetize application assets
• Make your z assets composable
• Faster response to market needs
5. API Centric Digital Transformation - opportunities
Enterprises are on a digital transformation path to stay relevant and respond to market needs in the quickest possible time.
APIs are at the center of digital transformation. These are some of the initiatives that will potentially require APIs to be created
for mainframe applications or data.
Position IBM z/OS Connect Enterprise Edition as the strategic and standard solution for one or more of these scenarios.
• Hybrid Applications, Cloud and micro services
• Move towards micro services architecture and expose services as APIs
• Consume partner APIs and other cloud based services (location, cognitive, etc)
• Service enablement of applications
• Refactor monolithic application into fine grained services and expose them as APIs
• Open API Initiatives (regulations)
• PSD2
• BIAN
• Open healthcare APIs
• APIfication / API economy
• Create an API channel to Z assets and monetize them
• Blockchain
• Integrate existing application assets with blockchain
• Data as a service
• Data is the new oil, and data on Z is invaluable! Expose them as APIs
• Make data available to system of insights (analytics engine)
7. IBM z/OS Connect Enterprise Edition
Extend application and data assets on the mainframe as APIs
Using IBM z/OS Connect Enterprise Edition
APIs to and from the mainframe Comprehensive subsystem support Point-and-click API creation
Try for yourself: ibm.biz/ibmztrialLearn more: ibm.biz/zosconnectdc
• IBM z/OS Connect Enterprise Edition provides a strategic solution to expose and consume open APIs to and from the
mainframe.
• It is a one stop solution providing a unified interface for all major subsystems and data on the mainframe
• Provides a easy and intuitive development and tooling interface that allows modern developers to easily create APIs on
the mainframe
• Open API descriptions allow standard access to mainframe based APIs using z/OS Connect.
• Works with any standard API management tooling.
11. 11
API enable Terminal based applications: HATS Integration
iSeries/zSerie
s
Integration Object
Java wrapper to
Macro
REST API
Map input/output
HATS Tooling (studio)
3270/5250
Stream Macro
Record
macro HATS
RESTful API
WAS/Liberty
HATS RuntimeDeploy
IBM Z /
iSeries
HATS Developer
.sar
zCEE
HATS
Deploy
zCEE Build toolkit
HATS swagger.json - i/o schema
HATS Runtime Server is
supported by zCEE via the
REST Service Provider
z/OS Connect EE
Server
Backend Systems
(CICS, IMS, DB, etc.)
14. IBM ADDI
14
IBM Application
Discovery
IBM Application Delivery
Intelligence
IBM Application
Discovery and Delivery
Intelligence
Application
Understanding -
Visualization of
Dependencies,
Flows, Usage
and Impacts
Continuous
Assessment and
Optimization of
Application
Complexity,
Transaction
Runtime and
Test Coverage
Cognitive
DevOps and
Continuous
Modernizatio
n for the
Digital
Transformatio
n
AD ADI ADDI
15. Reuse Existing Assets for
the API Economy
§Identify API Candidates
§Analyze the Impact of changing an API
§Trace SoE Consumers to SoR core
functionality and understand the Enterprise
Landscape
§Gain insight into Operations and link it to
changes as more APIs are developed
§Identify test conditions to ensure the
transformation does not impact Business
15
Accelerate APIfication
with ADDI
23. z/OS Connect EE
Things z/OS connect is not designed for…
• API Management
• Payload modification / transformation
• API / service orchestration
• Hosting Java business logic
• Protocol transformation
z/OS Connect
Enterprise Edition
24. IBM Client Center Montpellier
Hybrid Integration Architecture for IBM Z
Mobile
Partners
Cloud Apps
API Economy
IoT
Systems of Engagement
Channel
Applications
Integration
Layer
Consumers Systems of Record
XaaS On-Premise
z Systems
SecurityGateway
APIGateway
Enterprise
Application
Enterprise
Application
Cloud Affinity
Enterprise
Application
AccessLayer
Enterprise
Data
AdapterAdapter
Microservices
Applications
25. §Does a service interface already exist?
–You might already have SOAP web services running in the SOR that can be
reused by an API Gateway
–However exposing a REST interface directly might be more convenient and
streamlined
§What service granularity is exposed by the SoR application?
–It is possible that the granularity of the existing services will need to be
adapted e.g to perform service aggregation
§Do services need to be discovered?
–To facilitate fast and agile development of SOE applications (e.g mobile
apps), you need a way to allow developers to determine quickly what services
are available
Access Layer
26. §Is an ESB used in the existing application integration architecture?
–An ESB may already be used for data and protocol conversion, and may also have a governance role
in applying policies such as authentication, audit, logging, service versioning etc.
–Most ESBs have been enhanced in recent years to support REST/JSON
§How many types of service requesters and service providers need to be supported
by the application integration architecture?
–The value of an ESB is partly determined by the range of different service requesters and providers
that need to be integrated
§Does the mobile solution need to support asynchronous requests?
–An ESB is able to provide correlation for asynchronous invocations through a messaging engine
Integration Layer: Enterprise Service Bus
27. IBM Client Center Montpellier
API gateway considerations
• Do you need to make your business services more usable?
• APIs should be simple to look up from an easily browsable and searchable catalog
• Do you want to reach new markets, customers, and partners?
• By making core business functions available as APIs to business partners, a business can
reach more customers
• Do you need more control over who uses your business services?
• The API gateway can check the entitlement for the invoking application and the collected
audit data can then be analyzed and presented as a report for gaining insight into API
invocation
• Do you need to charge consumers for accessing your business services?
• The audit data that is collected by the API gateway can be used for charging
28. Security Gateway
• Is a security gateway used in the existing application integration architecture?
• A security gateway allows the decoupling of security policy from the underlying application
• Extending the security gateway to control access to APIs makes sense
• What are the specific security requirements of the hybrid application?
• Type of user (employee, client, partner, and so on)
• Type of device (cloud, mobile, IoT, and so on)
• Type of SoR services that are required by the service requester
• Authentication, authorization, and audit requirements
• Confidentiality and data integrity requirements
• Company and industry standards that must be respected
31. In the first 3 months 5500 new savings accounts were opened, with over $150M on deposit.
… delivery within 2
months!!
APIs can drive new revenue
“Opening a savings account went from 2-3 days to 218 milliseconds!”
From 2-3 days
to 218 milliseconds
z/OS Connect EE
Real-time account provisioning
Accelerated Account Servicing Experiment
able to deliver this type of capability to our customers real-time processing!
A Large Australian Bank
Accelerated Account Servicing Experiment
Business
Agility
33. Challenge: expose Z assets through a
common, consumable interface
Result: clients succeeding
enabling z assets as APIs
Provided 20 new APIs to their
core banking applications
“in half the time and for a fraction
of the cost that it used to require
for integration”
Solution: z/OS Connect EE provides RESTful APIs with
Swagger descriptions to data and applications on z Systems
Trusted core
systems including
CICS, IMS DB2
Exposed as
RESTful APIs with
z/OS Connect EE
Managed and
published through
API Connect
Delighted API consumers:
developers, business
partners and 3rd parties
• REFERENCES
o http://www.itnews.com.au/ne
ws/core-banking-overhaul-
still-off-the-agenda-at-anz-
bank-429979
o http://www.itnews.com.au/ne
ws/anz-bank-opens-up-its-
mainframe-439190
ANZ
Expose Z assets as APIs
Participate in
the API
Economy
34. Challenge: offer new client services quickly and easily with Z assets
z/OS Connect EE was explored
through an API Shack and 1 week
PoC. Development and the ATS
teams then helped plan a roadmap
for deployment.
Company achieved Digital
Transformation: revamping access to
their core services for through
standardized RESTful interfaces.
Insurance Company needed to
provide support for Apple Pay
alongside other 3rd party
payment options for their
billing teams.
The need The solution The result
A North American Based Insurance Co.
Enabling Apple Pay Leverage new
digital and
cognitive
services
35. IBM z/OS Connect Enterprise Edition
Business Differentiators
• Faster time to market – Extend your application as truly RESTful APIs with minimal application changes
• Reduced cost of development due to minimal changes in application resulting in saved $
• Simplified integration architecture leading to easier maintenance
• Saved cost of maintenance.
• Reduced cost of MIPS / Software with simplified architecture.
• z/OS Connect runtime, as an application of WebSphere Liberty can be offloaded to ZIIP saving MIPS.
• Note : APIs triggered by z/OS Connect run on ZIIP or GP based on the application. The z/OS
Connect runtime can be off-loaded to ZIIP.
• Leverage Mobile / Cloud pricing to save costs.
• Makes mainframe relevant to your future strategy as much as any of other platforms in the application
architecture.
36. Reference Papers
§ IBM z Systems: The heart of the mobile and API economy
– http://www.redbooks.ibm.com/Redbooks.nsf/RedbookAbstracts/redp5310.html?Open
§ Building an API bridge to your z Systems applications & data
– http://www.redbooks.ibm.com/Redbooks.nsf/RedbookAbstracts/redp5296.html?Open
§ IBM z Systems integration guide for the Mobile and API economy
– http://www.redbooks.ibm.com/Redbooks.nsf/RedpieceAbstracts/redp5319.html?Open