![mulesoft https keystore explorer mulesoft https keystore explorer](https://screenshots.macupdate.com/JPG/61342/61342_1554993927_scr_uc3.jpg)
The output from the execution is opened in the new tab in the Developer Console. If some significant failure occurs, you should see a popup window. To verify if the call works, click Execute. We make a call and wait for the response in line 6. What does this code do? We are going to call the GET operation on (line 3, 4). Map results = (Map) serializeUntyped(response.getBody()) Deserializes the JSON string into collections of primitive data types. Below I have registered exchange-portal-xapi application on dev environment. That means that we need to create as many entries as many Mule applications we are going to consume. As we are using the SLB, the application name is located in the subdomain. We need to provide at Remote Site Name and Remote Site URL. Next, find Remote Site Settings configuration.Once you login to your Salesforce click Setup.
![mulesoft https keystore explorer mulesoft https keystore explorer](https://mulesy.com/wp-content/uploads/2020/07/word-image-56.png)
Register remote siteīefore we try to connect with our MuleSoft application we need to register URI, so Salesforce enable outbound traffic. The first thing to do is to register a remote site. Is Salesforce able to consume my service? To do this, I write a simple APEX class to call our service. What is crucial to see is that the SLB has a CA-signed certificate for subdomains of cloudhub.io, whereas my application must be signed with a self-sign certificate. So how it works? Our APIs are published under and this is translated to : 8082. In the article Enable dedicated load balancer under own domain, I mentioned how DLB works. In order to run your application on CloudHub via Shared Load Balancer you are obligated to specify one of two values:Īnything else is prohibited, and your application won’t work properly. Case architecture MuleSoft application preparation Environment considerations Port configuration As you can see, I expose API for Salesforce using HTTPS protocols. Therefore, I will stick with the Shared Load Balancer (SLB). I didn’t purchase a Dedicated Load Balancer. I deploy all the Mule applications on CloudHub. Let’s see what we need to take into consideration when we expose our API via CloudHub and Shared Load Balancer. I will use the Salesforce playground that is available on the website. Is the calling system able to reach our API and receive a response? In this article, I will focus on the case when I expose API to Salesforce. Once we develop and deploy our MuleSoft applications, it is a good idea to test the connectivity.