Anypoint Platform

→ It is the cloud of MuleSoft.

1)Design Center – Here you can design your mule application or API specifications

API Specifications:
→ API’s Specifications will be created in RAML.
→ RAML is nothing but the contract b/w producer and consumer.
→ To create RAML we have 2 tools in design center – Visual Editor & Code Editor.

Visual Editor : It is user friendly, here you can create RAML by selecting required nodes,Here you
are not required to write code, code will be automatically generated.
→ You have a window – EDIT RAML in visual editor, there you can view your RAML code.

Code Editor: Here you can write RAML code your self, and it will provide suggestions.

**→ Mocking Service – if you enable this you can see your API summary, it will be in top right corner
of the editor.

→ Once You are done with API specification creation, you need to publish it to Exchange. Publish to
Exchange option is available in design center

API Fragment :
→ An API fragment is a RAML document that has a version and an identifier, but it is not a complete
RAML specification.
→ An API fragment is one of the following types
• Trait
• Resources
• Type
• Security scheme
• Example
• Annotation Type.

Mule Application:
→ You can create your application flow in design center.

2)Exchange:
→It is a place where you can store all the resources which were created and tested by developer and
connectors which are reusable. Any body can use them who has access to it.
→Re usability of an asset is the main theme of it.
→Here Exchange is used to discover and share reusable API’s, connectors & Templates.

3) Access Management :
→ Used to grant access to the anypoint Platform tools for custom roles.
→ It deals with user access to Anypoint Platform tools based on his role.
→ Mulesoft has some Default roles, which we cannot change.
I.e we have 2 types of Roles In access management – Default & Custom
4)API Manager:
→ API Manager is a component of Anypoint platform for Managing API’s.
API Defination, API Portal & API Status
→ Used to apply policies & SLA’s
→ You can create a portal for your API using API Manager
→ Policies –
EX:
Rate limiting: Number of requests in the given time
Oauth 2.0
Simple Security Manager

→ SLA Tires

5) Runtime Manager:
→ It is nothing but cloud hub
→ It manages and Monitor your deployments, It can manages cloud & on premises deployments.

Runtime Manage → choose Environment (Design & Sandbox)→ Select Sandbox → Then click on
Deploy Application → Select required fields and you need to select Deployment Target(cloud Hub
or On Premises serve) & select worker size and workers

Insights:
→It is one of the option available during Deployment in Runtime Manager.
→ In Studio, you have Custom Business Event component.
- You need to configure business events here,
→ Once you are done with the Business events configuration in Custom Business Events component,
Insights will track them display the status.

Cloud Environment:
→ It is Cloud Hub.
2 ways:
→ From Studio, right click on your project, click on Anypoint Platform → Deploy to Cloud.
→ From Runtime Manager, from Application Tab → click on Deploy application.
→ Here you need to select Runtime version, Worker size & Number of workers.
RunTime Version: Version of your Mule where the application is developed.
Worker Size : It deals with VCores & Heap memory. It is mainly related to CPU usage of your deployed
application
Workers: Worker is a dedicated instance of Mule that runs your application/API
→ Workers are responsible for executing business logic in each application.
→ If you deploy an application with more than one worker, CloudHub automatically load-balances
incoming traffic across your allocated workers.

Note:
→ Only running applications count for workers usage.
→ Stopped applications do not consume vCore availability.
→ You have an option called Automatic Restart application when not responding. If you check it, cloud
hub automatically restarts your application when the monitoring system discovers a problem with your
application. If it is not checked, cloud hub produces all the log messages, notifications and any configured
alerts, but takes no action to restart the application.

Hybrid Environment:
→ Here Deployments are done in On Premises server/clusters/nodes, which can be monitored from
cloud.
→ AMC token concept is used to connect on premises(standalone) servers to cloud hub.
AMC – Anypoint Management Console
→ Mule Soft guys gives you AMC tokens, you need to run it in the standalone servers, then the servers will
automatically connect to Mule RunTime Manager & register there.

Server Registration using AMC Token:

Standalone Server file→ /bin → right click and open command prompt → run the code copied form
runtime manager servers tab. → Server created successfully to runtime manager.

→ Deployments will done in runTime, those will be automatically get downloaded to local servers residing
in on-Premises.
→ You need to add Client ID & Client Secret to the WRAPPER.CONF file of standalone server.

================================= =============

Q. How the flows will be created in anypoint studio ?

→ While building new project, In project settings window, you have an option called APIkit settings
check it and add API components
API Defination :
1.Design center
2.Browse files
3.API Manager

→ Once you selected RAML file, API router will automatically create flows based resource type defined in
RAML.

Q.API Proxy

→ It is used to mask original URL

Q. API gateway

→ API gate way will check the masked Url first, then it will go to the original URL and display the API

Q)Can we set policies in the API proxy?

→ In Design center, you an option called Mocking service , you need to enable it.

Q) Another way to create RAML

Q) What is API Auto Discovery ?

→ This allows API manager to manage an API that represents HTTP endpoints.
→ It is used to link HTTP resources to its API definition in API manager.
→ If you use this in your studio applications, all your endpoints will be registered in Mule cloud.
→ It expects
in 3.x – API Name, API Version & Flow Name
In 4.x – API ID & Flow Name

Q) Performance Tuning in mule ?

Q)Cloud Hub Architecture?

→ Cloud Hub is a Integration Platform As A Service(IPaaS)

Integration Applications: These are the applications that you create and deploy to CloudHub to perform
Integration logic for your Business

1. Runtime Management Console: It is the face of CloudHub, allowing you to deploy and monitor
integrations.

2.Platform Services: This includes CloudHub Insights, alerting, logging, Account Management,
Worker Management, Load Balancing and others.

3.Worker Clouds: This is the cloud of Mule Instance that runs your integration application.