Self-study training: MuleSoft.U Development Fundamentals (Mule 4)

1. WT5 Deploying and Managing APIs

2. Agenda
● Describe the options for deploying Mule applications
● Deploy Mule applications to CloudHub
● Use API Manager to create and deploy proxies for APIs
● Use API Manager to restrict access to API proxies

3. WT 5-1: Deploy an application to CloudHub
1
2
3
4
5
Deploy app to CloudHub
Add your name to the end
of application name
Click

4. WT 5-1: Deploy an application to CloudHub
Copy app url
1
2
Response data is same as
one at Anypoint studio
destination param is not
implemented yet

5. WT 5-1: Deploy an application to CloudHub
Upload jar file with
destination
implementation
1
2
3
Select the jar provided
by MuleSoft
Destination param is
implemented

6. WT 5-2: Create and deploy an API proxy
1
2
Select API Manager

7. WT 5-2: Create and deploy an API proxy
1
2
3
4
Proxy app is deployed
and running
Implementation app is
running

8. WT 5-2: Create and deploy an API proxy
1
2Confirm proxy setting
Client apps access proxy
with the policies
Select API Manager

9. WT 5-2: Create and deploy an API proxy
Proxy is
added
Select Exchange

10. WT 5-2: Create and deploy an API proxy
1
2
3
Add label
4
Select Exchange
Select API Manager

11. WT 5-2: Create and deploy an API proxy
2
3
4
5
Copy proxy url
Add http://
Confirm consumer
endpoint is set
1

12. WT 5-2: Create and deploy an API proxy
Client app do not access
API implementation app
Proxy is available
because consumer
endpoint is set

13. WT 5-2: Create and deploy an API proxy
Dashboard shows request
by location, requests by
application, and so on
1
2
3

14. WT 5-3: Restrict API access with policies and SLAs
1
2
3
4
65
Change label for
Exchange

15. WT 5-3: Restrict API access with policies and SLAs
Try requests three times
within 1min and get
error message

16. WT 5-3: Restrict API access with policies and SLAs
1
2
3
4
5
Free SLA Silver SLA

17. WT 5-3: Restrict API access with policies and SLAs
1
2
3
6
5
4
Client must send client id and
secret at header

18. WT 5-3: Restrict API access with policies and SLAs
1
Change label
Get error because
id and secret is not
passed

19. WT 5-4: Request and grant access to a managed API
1
2
3
4

20. WT 5-4: Request and grant access to a managed API
1
2
53
4
Client id and token
for request

21. WT 5-4: Request and grant access to a managed API
1

22. WT 5-5: Add client ID enforcement to an API specification
1
2
Copy
3
4
Modify American-
flights-api.raml

23. WT 5-5: Add client ID enforcement to an API specification
1
2 3
4
Client_id and
client_secret fields are
shown
The modified API is not
published to Exchange so the
fields are not affected at
Exchange

24. WT 5-5: Add client ID enforcement to an API specification
1
2
3
6
5
4
The latest version is
1.0.2

25. WT 5-5: Add client ID enforcement to an API specification
1
2
3
4
5
Select latest
version
Confirm version
Confirm that two fields are shown in
Headers tab