LABS GALLERY: Jitterbit 3.0 Makes Quick Work of Integrating Disparate Apps, Data Sources

LABS GALLERY: Jitterbit 3.0 Makes Quick Work of Integrating Disparate Apps, Data SourcesBy Jason Brooks

The Jitterbit client made it easy for me to track the dependencies between the elements of my integration project.

I could set up e-mail messages and trigger them at any point in my integration operations.

Here you can see my test e-mail alert in action.

The Jitterbit client provides graphical representations of its integration operations.

After assembling my integration operations, I could schedule them to run from the Jitterbit server.

After setting up a schedule, I confirmed the times that my operation would run.

Kicking off a new integration operation starts with a dummy diagram to fill out.

I used Jitterbit 3.0 Enterprise MX to create users and groups, and to parcel out certain access rights to my project.

I had to specify the structure of my fixed-width text file manually.

With my data structure defined, I set out to map the fields from my text file source to my database target.

I could tap a Web service as a source by providing the service’s WSDL file.