Deck used in Pune Mule Meetup #16

1. [Pune-India]
[19th October 2019]
API Life Cycle
Service Mesh

2. All contents © MuleSoft Inc.
Agenda
2
• Introductions
• Service Mesh
• Complete Lifecycle of APIs
• Q&A
• What’s next
• Networking time

3. All contents © MuleSoft Inc. 3
Santosh
Ojha
Seemant
Jain
Mukesh Thakur Manish Yadav
Presenters, Organizers and You
A SHOW OF HANDS:
Who is new to this Meetup?
Shailendra
Malviya
Vikalp
Vishal Chaudhari

4. API Lifecycle from Design
to Publication

5. All contents © MuleSoft Inc. 5
Overall Process

6. All contents © MuleSoft Inc.
Design and Publish
6
• Design
– The process begins with the API Designer designing the API specifications in the
form of RAML using Design Center.
• Publish
– The API Designer is able to publish the API from Design Center by clicking on the
icon “Publish to Exchange“.

7. All contents © MuleSoft Inc.
Share and Discovery
7
• Share
– Now is the turn of the Admin to share it to other
people that don't belong to this business group.
– For the rest of the users, there are two options:
Sharing to specific users & via Public Portal.
• Discovery
– Discovery User
– Discovery Public

8. All contents © MuleSoft Inc.
Register API
8
• The key important information that is
returned is the values API Name and
API Version. The combination of these
two values uniquely identifies a unique
Instance in API Manager.
• This information is essential to link this
API Instance to the running application
that will implement the API, and allows
its management (apply policy,
statistics, alerts, etc..)

9. All contents © MuleSoft Inc.
Register API
9
• The link between the Mule Runtime (implementing the API) and the API Instance
(in API Manager) is done with the help of 4 different properties:
– API Name
– API Version
– client_id
– client_secret
• API Name and API Version will link to the particular instance that was registered
in the previous step in API Manager. The client_id and client_secret identifies the
Environment where the Mule Application is running.

10. All contents © MuleSoft Inc.
Pairing with Runtime
10
• Configuration Management and Deploy Mule Application
• Pairing
– In Anypoint studio

11. All contents © MuleSoft Inc.
Pairing with Runtime
11
• Manage API Instance
– Once the icon of the API Instance is green, the Mule Agent is connected and new
policies can be applied. The enforcement of those policies in the Mule Application
implementing the API will occur instantly.

12. All contents © MuleSoft Inc.
Request Access
12
• Apply Client ID Based Policies
• Request Access from an Internal User
• Approval Process
• Request Access from the Public Portal

13. All contents © MuleSoft Inc.
API Connector corresponding to API
13
• Once the data is entered, then the asset is created in Exchange as an API, and,
automatically, the corresponding API Connector is created in Exchange as well in
order to be able to consume that API from other mule applications. This connector
is obviously available in Exchange and Developers can download it and install it to
invoke to this API.
• Small demo.

14. Networking time
Introduce yourself to your neighbors!

15. All contents © MuleSoft Inc.
Take a stand !
15
• Nominate yourself for
the next meetup speaker
and suggest a topic as
well.

16. All contents © MuleSoft Inc.
What’s next
16
• Share:
– Invite your network to join: https://meetups.mulesoft.com/Pune/
• Feedback:
– Contact your organizers to suggest topics
– Contact MuleSoft at meetup@mulesoft.com for ways to improve the program
– Your feedback is fuel for us
• Our next meetup:
– Date: 23 Nov 2019
– Location: Hexaware Technologies, Hinjewadi
– Topic: TBD

17. See you next time
Please send topic suggestions to the organizer