When chaining Operations to execute consecutively, you might use Targets to “stage” data for the Source of the next Operation (or for reading or appending multiple times during various chained Operations). In many cases, these ‘staged” files are only needed during the Operation execution (or temporarily). This is the purpose of the Jitterbit Source or Target Temporary Storage component. In this short post, I share some best practices for and nuances of the Temporary Storage component. Continue reading “Using Temporary Storage Files”
Throughout integration data pipelines, small amounts of data are stored for re-use in computer memory. These are typically called variables – in Jitterbit, also known as Data Elements. This paper discusses variable concepts with the Jitterbit integration platform.
Variables have a type and scope. Because variables can be seen throughout data integration designs, it’s important to name variables with a convention that assists with a better understanding of their purpose and use. Note, Jitterbit variable names are case-insensitive. By using a naming convention for variable types or purpose, the Formula Builder filtering and alphabetic sorting feature accelerate access and comprehension. This will allow you to more quickly find and manage your relevant variable names “by type”.
We begin by discussing some critical variable types. Continue reading “Managing Data Elements (Variables)”
Error-handling, or event-handling, is an important requirement for any data integration project. Determining the events and “handling the encountered events” is a key design aspect in a robust design. Precise, detailed and meaningful reports enable efficient analysis of the captured events by the business and IT teams.
In this first of two installments, we describe best practices for handling unexpected and expected events within Jitterbit. Included are logging, validation and notification methods depending upon severity. Continue reading “Capturing Events & Errors for Effective Analysis (Part 1)”
In this second of two installments, we continue with the notification of events & errors and the Handle Event Script used in the previous installment. We also propose techniques for (counter) threshold checks and restart-ability practices that will ease maintenance tasks. Continue reading “Capturing Events & Errors for Effective Analysis (Part 2)”