SFDC / Integration Blog

Anypoint Studio must be connected to Anypoint platform to perform following activities: Deploy an API to Cloudhub environment Publish/consume assets from Exchange Download RAML from Design Center The steps to connect to Anypoint platform through the studio are outlined below:  Traverse through Window>Preferences>Authentication Click on Add button in Authentication settings Click on Configure button in the User login page, which will open up Authentication method window. Choose Anypoint Platform unless authentication is performed through external identity provider like Okta, Ping Identity etc... If an external identity provider is used as an authentication mechanism, then select External identity option and enter the organization domain id Provide anypoint user credentials in Anypoint sigin page to get the user account added to the Authentication settings Organization domain id can be obtained from the user profile by logging in to Anypoint platform through browser. Note: ...

MuleSoft CloudHub platform offers multiple worker sizes to deploy APIs. The worker sizes range from slice of a vCore to full sized vCores. It is often sufficient to deploy APIs to slice of a vCore like 0.1 or 0.2 rather than to a one full vCore, unless the API is CPU intensive or the deployed application consists of many complex APIs packaged as a bundle. Most of us know that MuleSoft workers are AWS EC2 instances behind the scenes, but what we may not know is how CPU is utilized in a slice of vCore and what could be the possible implications of using a slice of vCore. The below table shows the various worker sizes and their corresponding EC2 instance types. Burstable Performance Instances: Instances providing slicing of vCores are called burstable performance instances. In these instances, full CPU utilization is achieved when an instance reaches baseline utilization percentage defined for the instance type. What happens when an instance hits baseline utilization percentage? Burstable...