Authors: Elias_Sha Skip navigation

Cloud Data Integration

4 Posts authored by: Elias_Sha

Written by:  Sumit Jain



After working extensively on Informatica Cloud, I have collected some to dos and guidelines of the Informatica Cloud product. You may know them before hand, but I thought to compile a list and share it with a wider audience:




1. Create a Naming Conventions document detailing the standard naming conventions for different types of Connections, Tasks, Taskflows and schedules within Informatica Cloud. All the developers should rigorously follow these naming conventions. It has been observed that when multiple people are working simultaneously, they tend to follow their own naming standards and at the end, there are lot of tasks and it is very difficult to identify tasks and administrator has to spend a good amount of time identifying the correct tasks.




2. Add meaningful description to all your tasks, connections, taskflows and schedules in such a way that they convey the purpose of their use and thus do not create confusion to other users.




3. The machine the Informatica Cloud Secure Agent runs on must always be on. It must not be in a sleep mode or in “idle”. This might be indicated when the Agent status fluctuates between an active/inactive state. Make sure this computer is on or re-install the agent on a computer that stays on continuously.




4. If you are using the CSV files as source or target, make sure that you match up the date format in the associated connection for flat files, by dropping down the Date Format list and choosing the matching format.


And If there isn’t a matching format in the drop down list, then you will need to explicitly format the date in Step 5 of Data Synchronization task by using a transformation function called TO_DATE.




5. If there is a requirement of performing a lookup on Salesforce objects, then do not create a direct lookup. A direct lookup on Salesforce object will call the Salesforce object for each record processed and thus performance will decrease considerably. Instead, write the data of Salesforce object in a flat file and then use the flat file for doing the lookup.




6. For incremental processing, use the “$LastRunTime” and “$LastRunDate” variables in conjunction with a source field of “date” type. Informatica Cloud supports and maintains these variables automatically. For example, if your source has a field called LASTMODIFIEDDATE, you could set up your filter such that LASTMODIFIEDDATE > $LastRunTime. If your schedule then runs the task on a daily basis, that means each day you will only have to deal with the new/changed records from the previous day, instead of worrying about ALL records.




7. If the Informatica Cloud Secure Agent is running on a linux or unix server, it will not support MS SQL Server as source or target.




8. In a multi-user environment where the number of tasks to be created is very high, create Views based on logical groups for viewing similar group task in a single task view. Similarly you can create views for connection and taskflows.




9. SYSDATE is the current datetime you can use to denote the current date and time.




10. Use logical operators like IIF and DECODE to encode conditional logic in the expression in Step 5 of Data Synchronization task.



This has been posted on the community page as well.


What are some of your best practices?

Please share with us on the comment section below.



Informatica Cloud Templates are repeatable data integration patterns and processes that can be easily used by a business user in a Custom Integration Task in Informatica Cloud Services (ICS) to execute a sophisticated logic.  These Templates have been developed by our partners, customers, independent developers, and us by leveraging the Informatica Cloud Platform (iPaaS). 


Informatica Cloud provides a number of these Templates to customers, community members, and partners as FREE downloads from the Informatica Cloud Marketplace.  Templates are a great way to jump start your productivity for common use cases, and there are currently more than 50 templates available so you have a successful deployment and save significant development time and effort.




These predefined integration and data management logic blocks cover everything from business processes to integration solutions between SaaS and any application.  The great thing about these Templates is that you can customize and tweak them for your specific use case or solution.  We’ve compiled a list of these Templates in the following community documents for your convenience. Many of these documents include the user guide for the Template as well.


Informatica Cloud Integration Templates Index 1


Informatica Cloud Integration Templates Index 2



There are new Templates added every day, so please check back with us often.


To start creating your own Templates, here is a good how-to guide:


We would love to crowd source the development of more Templates. If you have a specific use case or business process that could form the basis for a useful template, please post us your requirements and maybe someone form the Cloud Community of Independent Developers will pick up the challenge.

Written by :  Sumit Jain of Astadia orginally posted here:

Salesforce to Salesforce is a native feature to share data records in real time between two environments (orgs). For example, two business partners may want to collaborate by sharing accounts and opportunity data within their orgs. It is very easy to share the data using Salesforce to Salesforce feature.


In most scenarios, data can be shared using the standard user interface manually. A user creates an account in one org, clicks the external sharing button, selects the appropriate org connection and then shares the record. This involves some manual effort and when sales reps are working on lot of records, the manual sharing process can become a painful exercise and that may cause some user adoption issues in the long run.


There are two objects which are controlling the Salesforce to Salesforce feature at the backend:


  • PartnerNetworkConnection - Represents a Salesforce to Salesforce connection between Salesforce organizations
  • PartnerNetworkRecordConnection – Represents a record shared between two Salesforce Orgs using Salesforce to Salesforce.

Whenever the user shares a record using Salesforce to Salesforce, a record gets created in PartnerNetworkRecordConnection object.

Informatica Cloud can be used to make this integration between two Salesforce orgs seamless and automatic.  The process flow will be as follows:

  • User creates the records (which need to be shared) in his org.
  • As soon as the record is created, a workflow is kicked off which sends an outbound message.
  • This outbound message will initiate an Informatica Cloud task.
  • The Informatica Cloud task will insert the record details (created in setp -1) in the PartnerNetworkRecordConnection object.
  • As soon as the record gets created in PartnerNetworkRecordConnection, it is shared with the Partner Org.

Thus, the records created in one org are automatically shared to the Partner Org in near real time without any manual intervention.

Overall, the benefits of using Informatica Cloud are:

  • Data Synchronization achieved through the use of out of the box functionality.
  • Centralizes Integration Logic and no need of writing custom VF/Apex code for automating Salesforce to Salesforce feature.
  • Record Selection criteria for sharing can be easily defined using filters.
  • Exception handling of failed records can be set up to monitor the record sharing status.
  • Scalable approach.

So if you are considering implementing Salesforce to Salesforce feature to share records automatically, you can consider the Informatica Cloud approach as described above.




On Tuesday, March 5, 2013, Informatica Cloud reached an unprecedented new height by processing more than TWO billion transactions in a single day.  It was only one year ago that Informatica Cloud processed one billion transactions in a day.   To double that number within a year is phenomenal.  The exponential trajectory of growth is a testament to the technology platform and the people who built it and support it.  A big "Thank You!" to our customers, the cloud community members who use our products, and everyone who helped us get here.  BIG DATA Congratulations to Everyone!! 



Filter Blog

By date: By tag: