Use Case 3 – WebSphere Cast Iron Integration – MySQL and Salesforce.com

by Sudipta Deb | Mar 17, 2015 | Apex, cast iron, database, integration, mysql, Salesforce, WebSphere | 0 comments

Preface – This post is part of “WebSphere Cast Iron Cloud Integration with Salesforce.com” series.

Today I will post how you can use WebSphere Cast Iron for integrating MySQL with Salesforce. Toady, in this example, I will fetch records from MySQL Table and then create the Salesforce object based on that record. So READY, STEADY and GO!!

Note: I have used http://www.freemysqlhosting.net/ for creating free MySQL Database.

Use Case:
Below is the object structure –

MySQL table looks like  – 


Implementation:
Before we start implementing the above requirement, let’s create the Endpoints first.
Endpoint – FTP:

Endpoint – Salesforce:


So all set. Now we will configure the integration by putting activities inside the Orchestration.
Activity# 1: Database – Get Inserted Rows:
In this activity, I will fetch the inserted rows from the database. Below are the configuration details –

Activity# 2: Add If – Else Condition:
The requirement is – if the Airport Name is blank, then terminate the process, else do an upsert into Salesforce.com
The configuration is displayed below –

Activity# 3: Salesforce Upsert Objects:
Below are the configuration details for this step – 


We are done. The final Orchestration looks like –

Test the Integration –
It’s time to test the configuration. First we need to start the orchestration and we can do that from Orchestration | Start Orchestration.

After 5 seconds, if we see our Salesforce Airport object, we will be able to see that two records being created as shown below –

COOL!!!
If you follow the steps mentioned in this post, you will be able to configure this integration very easily. 
Please let me know if you need any details. Thanks.

Written by

Related Posts

Salesforce Cancels the “Permissions in Profiles” Retirement: What It Means for Admins and Architects

Salesforce Cancels the “Permissions in Profiles” Retirement: What It Means for Admins and Architects

For the last few years, Salesforce administrators, architects, and security teams have been preparing for a major platform change: the retirement of permissions managed directly through Profiles. Salesforce had previously announced plans to move organizations toward a Permission Set–led security model, with enforcement expected to begin around the Spring ’26 timeframe.

read more...

0 Comments

Leave a Reply