which involved specifying my text
file to database intentions, selecting the text file source I’d just
configured, and then creating a new text structure definition
to describe how the data in the source file had to be divvied
up into rows and columns.
This step got a bit tedious because although the Jitterbit
client offered to suggest a text structure based on a sample
source document, the client was unable to come up with one
on its own. Instead, I had to specify the start and end character
positions for each column by hand, consulting a separate text
editor to get those positions from my source sample.
Fortunately, once I’d defined the text structure for my
source, I could use it in other operations simply by choosing
it from a drop-down menu of sources saved along with my
project. For each element I used or created, I could consult
a “dependent objects” dialog that would keep me aware of
what other elements in my project relied upon the component in question.
If I wanted to export any set of project elements for use in
another project, I could wrap up those elements in the form
of a Jitterpak, which I could then import into another project
or even share with other Jitterbit users through the Trading
Post section of the company’s Website.
With my data source in place, I turned to the target
side of the equation by configuring my new integration
operation with a Postgres database and table to receive
my stats.
When I reviewed Talend Open Studio a few months back,
I was able to instruct the product to create a new table to
receive my data. With Jitterbit, I had to create the table in
Postgres on my own first.
After creating and configuring a target table, I used the
Jitterbit client to set up my source-to-target data mapping and
jump into an initial test of my new integration operation.
Once I confirmed that my operation worked as expected, I
deployed it to the Jitterbit server. There, the operation ran
according to whatever schedule I chose for it from the client’s
scheduling dialog.
In addition to its integration project creation tools, the
Jitterbit client provides a slate of administrative functions,
including access to relevant server, operation and debug
logs; views into the status of Jitterbit servers, process queues
and scheduled events; as well as a user console with which
I could divvy up access to very specific portions of projects
on a per-user or per-group level. ;
I could set up e-mail messages and trigger them at any point
in my integration operations.
The Jitterbit client provides graphical representations of its
integration operations.
Executive Editor Jason Brooks can be reached at jbrooks@eweek.
com.
After assembling my integration operations, I could schedule
them to run from the Jitterbit server.
This story can be found online at:
