MuleSoft Facts I Know Now

These are random facts I compiled as I was studying for my certification exam for MuleSoft Associate.

  1. Postman mainly makes REST requests. Postman makes SOAP requests too but is frequently called a REST client. Postman is actually a tool that handles any calls sent over HTTP. Since SOAP is agnostic with regards to the underlying transport protocol, Postman easily handles SOAP calls too. (source)
  2. Polling: actively retrieve messages from an external resource, most message processors in Mule are triggered when called by a previous element in a flow. (source)
  3. Flow variables and invocation properties are the same thing.
  4. You can’t put HTTP in an asynchronous block because HTTP is always waiting for a response since it’s a request-response kind of deal.
  5. Outbound properties are part of the Mule message response
  6. Inbound properties are part of the Mule message request
  7. When you publish your REST API on API Exchange, you are giving two things: API Portal (documentation) and the REST API.
  8. You can make your API secure in two ways: by using HTTPs (instead of HTTP) and by using authentication like OAuth2 (instead of no authentication being required).
  9. The source is the starting end. Java has a main method so the compiler always reads there first, but a MuleSoft app might have many different HTTP listeners, so just remember to use the correct path when you are trying to call a certain flow to start your application.
  10. Cloudhub routes all requests to your application domain URL on port 80 to an endpoint with the matching path that was configured with a host of and port 8081. 80 is always routed to 8081.

Leave a Reply

Your email address will not be published. Required fields are marked *