The document summarizes an API lifecycle management meetup presented by MuleSoft. The meetup covered the full lifecycle of API management, including design, exchange, development and testing, deployment, API management, monitoring, and error handling. It provided demonstrations of MuleSoft's Anypoint Platform and its tools to support each stage of the API lifecycle. Attendees were invited to provide feedback and connect with other MuleSoft community members.

2. Feb 27, 2022 4:00 PM IST
Hyderabad & Indore MuleSoft
Meetup Present’s
API LifeCycle Management

3. A recording of this meetup will be uploaded to events page within 72 hours.
Questions can be submitted/asked at any time in the Chat/Questions & Answers Tab.
Make it more Interactive!!!
Share us the feedback! Rate this meetup session by filling feedback form at the end of the day.
We Love Feedbacks !!
Housekeeping
3

4. 4
● Introductions
● API Lifecycle Management
❑ Design
❑ Exchange
❑ Development and Unit Testing
❑ Deployment
❑ API Manager
❑ Monitoring
❑ Exception Handling
● Networking time
Agenda

5. Introductions
●About the Meetup Leaders
5
A SHOW OF HANDS:
Who is new to this Meetup?

6. ●About the Speaker :
Introductions
Soumya Rachuri,
MTS, Salesforce
6
Shivam Khandelwal,
MTS, Salesforce

7. Lifecycle API Management

8. Lifecycle of an application building block
On-premises/Hybrid
MuleSoft CloudHub 2.0 Anypoint Runtime Fabric

9. Mulesoft’s Anypoint Platform
Platform for Integration, APIs, and Automation
9
● Single solution for iPaaS
and a full life-cycle API
management
● Helps organizations
connect applications,
data and devices
● MuleSoft Anypoint
integration platform
ensures:
○ Accelerated
Delivery
○ Automated Security
○ Resilient
Operations
○ Future-proof
foundations

10. ● Design: Identify process and business
requirements, create logical data model,
translate into logical service, API groupings
● Simulate: Model API resources, model API
operations/methods, model request/response
payload/codes
● Feedback: Mock up the API, publish interactive
console, create notebook use cases, receive
developer feedback
● Validate: Modify API design as appropriate
based on developer feedback, continue to
validate
Design

11. ● Design Center provides the below tools:
● Create and document APIs using a
web-based interface
● Create API specification easily using
the context-aware shelf which auto-
populates with the appropriate methods,
resources, parameters, and security
components
● Use a mocking service to test and
validate APIs
● Publish an API specification to Anypoint
Exchange for use in API Manager,
Anypoint Studio
Design Center

12. Exchange
● Curated catalog of reusable assets
● Teams can publish, share, discover,
learn about, and reuse assets within
the organization
● Facilitates collaboration, boosts
productivity, and promotes standards

13. Demonstration

14. ● Critical piece in enabling a next-
generation enterprise
● Key part is enabling the
connectivity of hundreds or
thousands of APIs to a backend
as well as to each other
● Two steps in implementation
stage are building and testing
Implementation

15. Build
● User-friendly IDE for designing and
testing Mule applications
● Has pre built modules for common
integration requirements
○ Includes modules for querying
backend systems, routing events,
business transformation logic, and
error handling
● Access to hundreds of prebuilt
connectors, templates, examples, and
APIs built by MuleSoft
● Scaffold APIs from OpenAPI and RAML
specifications with APIkit
Anypoint Studio

16. Test
● Powerful application testing
framework built into Anypoint Studio
which enables developers to create,
design and run unit tests on APIs and
integrations
● Fully integrated with Maven and
Surefire for integration with DevOps
processes of continuous delivery and
deployment
● Minimizes manual work with auto-
generated tests and coverage reports
● Provides coverage reports metrics on
percentage execution of Mule
application by MUnit tests
MUnits

17. Demonstration

18. ● Critical to ensure application building
blocks are following best practices in
security and architectural governance
● Within this lifecycle stage are the following
steps:
○ Secure
○ Deploy
○ Monitor
○ Troubleshoot
○ Manage
Management

19. Runtime Manager
Deployment
● Interface to Anypoint Platform that
provides a unified view of
applications, servers, and APIs
● Can deploy, manage, and monitor
Mule applications in various
environments from one central
location, whether apps are deployed
in the cloud or on-premises

20. DevOps
Embracing modern DevOps-centric processes
and tooling is critical to reduce mean time-to-
production
Continuous integration and continuous
deployment (CI/CD) pipeline is a best practice
for DevOps teams.
CI/CD Process setup steps:
● Setup Jenkins and initialize a Git repo
● Configure the Mule Maven plugin
● Create Maven Settings File
● Create a Pipeline and Configure Jenkins
● Automate Git to trigger Jenkins jobs

21. Demonstration

22. API Manager
Govern and Secure
● Enables to manage, govern, and secure
APIs
● Apply pre-built or custom security policies
at runtime with no downtime
● Proxy existing services, group APIs
together to simplify consumption, and
secure APIs with a few clicks
● Improves the reliability, performance, and
overall value of APIs by analyzing and
detecting trends in performance, policy
violations, and user interactions.

23. Demonstration

24. Anypoint Monitoring
Monitor
● Monitor all APIs, integrations,
and microservices in real-time
● Speed up issue identification
and root-cause analysis with
customizable dashboards and
alerts, dependency mapping,
and instant access to historical
log data
● Drive business and technology
insights by measuring business
impact

25. Demonstration

26. Error Handling in Mule 4

27. Types of Errors
System Errors
Mule throws a system error when an exception occurs at the system level and no Mule event is
involved. A system error handler manages exceptions that occur:
● During application startup.
● When a connection to an external system fails.
Messaging Errors
Mule throws a messaging error (a Mule error) whenever a problem occurs within a flow of a Mule
app, where Mule events and the messages they contain are processed.

28. Error handling Scopes
Application Level Flow Level Processor Level

29. Handling Mule Messaging Errors
● Default Error Handler
● On Error Continue
● On Error Propagate
● Global Error handler

30. Default Error Handling for Messages
By default, unhandled messaging errors are logged and propagated. When a flow is processing a
Mule message that raises an error, the normal execution of the flow stops, and the process
transfers to the flow’s default error handler, which propagates the error.

31. On-Error Components
On Error Continue On Error Propagate

32. Demonstration

33. 34
● Share:
○ Tweet using the hashtag #MuleSoftMeetups #MuleSoftCommunity
○ Join Hyderabad Group: https://meetups.mulesoft.com/hyderabad
● Feedback:
○ Fill out the survey feedback and suggest topics for upcoming events
○ Contact MuleSoft at meetups@mulesoft.com for ways to improve the program
What’s next?

34. Quiz Time

35. 36
Join Kahoot

36. Q&A

37. Introduce yourself to your co-muley
Networking time

38. Thank You