Shows to push REST APIs in IIB to APIm.

1. Unleash Your Enterprise Systems
with IBM Integration Bus and API Management
HIA-1922
Jack Carnes - carnesj@us.ibm.com
Lee Gavin - gavinlee@uk.ibm.com
WW Hybrid Cloud Integration

2. Please Note:
2
• 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
• Digital transformation
– Two speed IT
• What is API Management?
• REST enables APIs
• REST APIs in IIB
• Push REST service to API Management
• Demo
5

4. Digital Transformation

5. Uber, the world’s largest taxi company, owns no vehicles.
Facebook, the world’s most popular media owner, creates no content.
Alibaba, the most valuable retailer, has no inventory.
And Airbnb, the world’s largest accommodation provider, owns no real
estate. Something interesting is happening.
http://techcrunch.com/2015/03/03/in-the-age-of-disintermediation-the-battle-is-all-for-the-customer-interface/#.pgfhdr:o98A
Digital Transformation Timeline

6. Example of digital disruptor: Ride-sharing service Uber
• The entire user experience is unified on a mobile device
– Everything about the service is literally at the customer’s
fingertips
• The service operates with remarkable transparency
– Up front, you know when your car will arrive, what type of car it
is, the driver’s name, how many miles you have to travel, and
the total cost
• The company has eliminated considerable friction from
the process
– For instance, the service is billed automatically to your credit
card—no need to fumble for cash or even figure out a tip
• The company had a global strategy from day one
– More and more travel is global, and consumers want to use
services they’re familiar with and trust anywhere in the world
they go
8

7. Digital Transformation changes the game
 Differentiation based on product/service
 Individualized market segmentation based
on outside-in listening
 Emphasis on design and marketing
 Differentiation based on ecosystem value
 Dynamic customer understanding based on
constant collaboration
 Emphasis on rapid recomposition
Traditional economy
Everyone to Everyone
(E2E) economy
Differentiating capability
API
API
API
API
API
API
Shifting market
power
from suppliers to
consumers
10

8. Speed & Agility
Digital
Ecosystem
Fast
Speed
Integration & Scale
Core
Enterprise
Steady
Speed
Digital Transformation through Multi-Speed IT
Digital
•Timeframe: Days/Weeks
•Scope: Strategic
•Sponsor: CMO
•Budget: Thousands $
•Complexity: Low
•Buying behavior: Self service
Enterprise
•Timeframe:
Months/Years
•Scope: Strategic
•Sponsor: CIO
•Budget: Millions
•Complexity: High
•Buying behavior:
Human engagement

9. Deploy and Integrate Anywhere
CloudOn Premises
Process
Process
Interaction
Interaction
App
App
Access
Access
Systems of RecordSystems of Record Systems of InsightSystems of Insight
Cloud Services
Events
EventsAPIs
APIs
Security
SecurityData
Data
DataData
IoTIoT
RuntimesRuntimes
API MgmtAPI Mgmt
Event
Hub
Event
Hub
Gateway
SecurityMonitoring & Analytics
Info
Info
Partner
Partner
Enterprise Integration and MessagingEnterprise Integration and Messaging
Systems of EngagementSystems of Engagement
An enterprise architecture for multi-speed transformation
How to manage the
consumption of APIs across
the enterprise?
How to provide self-service
for internal & external
developers?
How to enforce security at
runtime?
How to throttle and provide
controlled access?
How to introduce change
with new versions?
How do I know who is using
my service and how much?

10. Why are APIs Important?
Websites
Connected
Appliances
Partners Websites/
Sensors
Internet TVs
Smartphones
Tablets
Game Consoles
Connected Cars
Millions 1993 - 2000
“…in 1993 and 1994 we
were deeming the web as
the next place for FedEx to
be.” -Thomas Wicinski, VP Digital
Marketing FedEx
APIs
Trillions 2013+
The way we reach customers has evolved

11. API Success Requires Addressing Needs of Multiple
Stakeholders
API Developer
 How do I assemble
APIs?
 How do I manage
security?
 Will the infrastructure
scale?
 How do I measure
performance?
App Developer
Where do I access APIs?
How do I understand the APIs?
How do I measure success?
API Product Manager
How can I rapidly release & update my APIs?
How do I publicize my API?
How do I measure success?
Operations
Lead
How do I manage all the API
Environments that are being
requested?
How can I scale each
environment?
How can I easily find and fix
issues?

12. Existing
Enterprise IT
Investments
Exposed
as APIs
Self Service
Consumed
by
Developers
To Develop
Innovative
Apps
Delivering
Differentiate
d Customer
Experiences
Unleash Enterprise Investments to Disrupt Competitors
API Economy Supply Chain
TH GS
IN
www

13. What is IBM API Management?

14. A single, comprehensive solution to design, secure, control,
publish, monitor & manage APIs
IBM API Management
Fully on-premise, multi-tenant solution, for API
providers
IBM DataPower
API Gateway for security, control, integration & optimized access
to a full range of Mobile, Web, API, SOA, B2B & Cloud workloads
On-premise privateOff-premise SaaS Off-premise dedicated Hybrid

15. An API Strategy To…
Securely expose
systems of
record
Apps and data
to Mobile, IoT, &
hybrid cloud
apps
Publish APIs to
expand brand
reach
Tap into
developer &
partner
ecosystems
Enable new
business
Monetize
existing and new
data &
algorithms
Speed
application
development
Via self service
library of
reusable APIs

16. Easily manage your APIs
• Design, secure, control, publish, monitor & manage
 Explore API documentation
 Provision application keys
 Self-service experience
Developer Portal API Manager Management Console
 Define and manage APIs
 Explore API usage with analytics
 Manage API user communities
 Provision system resources
 Monitor runtime health
 Scale the environment
IBM DataPower
Enforce runtime policies to control API traffic

17. The API Lifecycle
Share APIs with
several developer
communities
3
Create, assemble
and version an API
1
Analyze & Monitor
API usage 4
Secure, control, test
& scale the API
Manage Plans
2

18. API Developer: Create, Secure & Version APIs
• Simple interface accelerates iterative API development & deployment
 Intuitively define REST or SOAP APIs by
importing Swagger 2.0 or WSDL files
 Or discover from System z or service registry
(WSRR)
 Or rapidly assemble APIs via configuration, not
coding
 Search for, add custom tags to, and mark
favorite APIs for easier discovery
Define
API
Developer
Assemble
Meter
Secure
Deploy,
Test & Debug
Monitor
Scale
Version

19. Advanced Developer Portal capabilities out of the box

20. API Provider: “Productize” APIs using Plans
 Plans “productize” APIs
 Multiple APIs and
Resources per Plan
 Version your Plans
 Apply Rate Limit by Plan or
Resource
 Reject calls when limit
reached
 Introduce API Trial Use
 Free plans with limitations
can be made available
alongside premium plans
 For example, a free plan
might allow anyone to
subscribe and a premium
plan might require approval

21. API Provider: Gain Business Insights
 Pinpoint key market fluctuations and
find correlations related to your
business
 Analytics for both API provider and
application developer:
 Analyze performance of APIs
 Enables chargeback or billing for
API consumption

22. App Developer: Register application
Register new
application
Request security keys
with enhanced privacy
Deferred retrieval of
client secret

23. App Developer: Analyze App Performance
Monitor most active
applications and APIs
Developer
notifications for
reaching rate limit
thresholds

24. IT Admin: Manage Overall Environment*
 At-a-glance server
utilization metrics
 Management & Gateway
Server utilization - CPU,
Memory, Disk
 Usage over time
available by drilling down
* Not applicable to SaaS

25. REST Enables APIs

26. REST APIs
• Lightweight web service API based on HTTP
– Much simpler alternative to SOAP based web services
• Describes a set of resources
– Set of operations that can be called on those resources
• Operations
– Called from any HTTP client (available for most programming languages nowadays.
– Easily called from JavaScript code running in a web browser, or application code running on a
mobile device
32
REST API
Mobile
apps
Mobile
appsCloud
apps
Cloud
apps
Web
pages
Web
pages

27. REST APIs – Swagger
• Swagger specification
– Open standard for defining a REST API: http://swagger.io/
– Swagger 2.0 can be found at:
https://github.com/swagger-api/swaggerspec/blob/master/versions/2.0.md
• Swagger document
– Includes definitions of the resources, operations, and parameters in a REST API
– Can include JSON Schema that describes the structure of the request and response bodies to an operation
– Effectively REST API equivalent of a WSDL document for a SOAP web service
• Open source tooling
– Interacts with Swagger documents
– Interacts with REST APIs described by the documents
• Integration Bus supports Swagger 2.0
– In order to build a REST API in Integration Bus, you must develop and supply a Swagger 2.0 document that
describes the REST API you are going to build.
34

28. REST APIs In IIB

29. Batch Apps Data Process Packaged App
(SAP, PeopleSoft)
Adapter
SOAP/HTTP
ODBC/JDBC
MQ/JMS
Legacy (CICS /
IMS / Z)
File
External
Services
REST/HTTP
IBM Integration Bus
TCP/IP
APIAPIAPIAPI
IBM Integration Bus Accelerates Digital Transformation
37

30. Why use IBM Integration Bus?
IBM Integration Bus delivers enterprises with the capability to provide system connectivity and data transformation
spanning heterogeneous IT environments.
38
Universal Scalable
Intelligent Simple
“My organization’s applications run
on different hardware and
operating systems, and are written
in different programming
languages.”
“I want to integrate new applications
and systems to respond to business
needs as fast as possible”
“We want to gain insight and have
control over in-flight data for more
intelligent business decisions”
“We need a solution that can cope with
a wide range of hardware, software
and virtualized environments”

31. Using IIB to provide a REST API
• Introducing IIB’s new REST API first class construct
– Provides a simple way to receive JSON / HTTP and expose a
REST API
– Create a new REST API in the IIB Toolkit
– Drag and drop the REST API to deploy
– Administer REST APIs as a first class IIB construct in the Web UI
40

32. REST API Project
• New REST API Project
• Schemaless mapping
• Invoke integration directly from programs using an API
• Generate JavaScript API from a service
• Import Swagger 2.0 definitions, clients can use existing Swagger
tools and projects to retrieve Swagger definitions
• Patterns for rapid mobile development
41

33. REST APIs – new project wizard
43

34. REST APIs – REST API Description view
45

35. REST APIs – packaging and deployment
• REST APIs can be packaged into a BAR file and deployed to an integration server using
any of the standard mechanisms – either the Integration Toolkit, the command line, or the
Integration Java API.
• Once deployed, a REST API appears in the Integration Toolkit and web administration
interface as a REST API, under a new REST APIs category.
47

36. Testing REST Service using Test Client
49

37. REST APIs – web user interface
50

38. Push APIs to APIm

39. Where does IBM APIm and IIB fit?*
• IBM Integration Bus provides
universal connectivity
• Makes data from Systems of Record
available to Systems of
Engagement
– Typically accessed via a gateway
appliance when exposed publicly
Connected
Appliances
Partners Websites/
Sensors
Internet TVs
Tablets
Game
Consoles
Public Cloud
Analytics
Mainframe Back-office
Processes
CRM
Services
Databases
Private Cloud
DataPower
Gateway
Systems of Record Systems of EngagementDMZ
IBM
Integration
Bus
* Assumes on premise deployment
*

40. Easy Integration with IBM API Management
• Deployed IIB REST APIs can be pushed to API Management
from the IIB Toolkit
– Use IBM API Management to promote and monitor the usage of
the REST API
– Secure and authenticate access requests from external
applications
• In IBM APIM, begin by ensuring you have:
– A registered organization and email address for the API owner for
logging in to the IBM API Management console
– A sandbox environment defined, and network connectivity
• The IIB REST API is identified by the API Management
server using the Swagger Title
– REST API is created if it is a new definition
– If it already exists, then the latest revision
is replaced
54

41. Push REST interface to
APIm from Integration node
view
As an integration developer I can use the IIB Toolkit to
create an API and load it into the API Management catalog
without writing any code
Push to APIm
55

42. Demo

43. Demo Scenario
Soap UIDatabase
DataPower
Gateway
IBM
Integration
Bus
ACMEHR
Swagger JSON
DataPower
Configuration
WLM Policy
Standard Plan
ACMEHR
Premium
Plan

44. Thank You
Your Feedback is Important!
Access the InterConnect 2016 Conference Attendee
Portal to complete your session surveys from your
smartphone,
laptop or conference kiosk.