Back to Index |

How does BlueSky Integration Studio work?

BlueSky Integration Studio's architecture is extremely efficient. The system generates 100% VB.NET code no matter what your job design does. It then compiles that code for you into a true Executable giving it the best possible speed advantage. Along with that, you get the incredible features of the .NET framework related to memory management, managed code and garbage collection. The resulting executable is stored in a repository managed by the Personal or Enterprise Server software where you can then manage, run, and automate your integration tasks. All of this is done behind the scenes. For you, it’s a simple as clicking the compile button on the toolbar.

Given that BlueSky Integration Studio can compile a job into an executable, why not also then a component library? Absolutely! We carefully designed the job classes from the ground up to be stand alone, reusable class objects so that you can also compile the jobs into a .NET component .dll. You get the same exact code and speed from a compiled executable as you do from a compiled .dll, except now you can reference it right from your own custom .NET applications including VB.NET, C# and ASP.NET. We sometimes refer to these as Transportable Integration Objects.

And your next question would be... Can I have the code?! Heck, we spent all this time developing a great tool that has to generate the code for compilation, why not just give it to you! In the Enterprise Edition, BlueSky Integration Studio also has an option for generating a job to actual VB.NET code. This proves very useful in situations where the developer wants total control, or maybe is developing an off-the-shelf application and wants the code for the integration work to be embedded right into the application. It has also proven to be an invaluable learning tool for beginning .NET developers.

How does BlueSky Integration Studio move information?

The actual kernel functionality in each job is a very small, tight loop that ensures the job runs as fast as the machine and/or database can process each transaction. In the simplest terms, a job can be outlined in the following way:

For each Join Transformation Object in a job:

- Read data from the input data object stream

- Test the Filter code to ensure data should flow to each output data object stream

- Execute field-level function code (your VB.NET transformation code)

- Pass the resulting values to the output data object stream

- Generate a SQL statement, Bulk data, or File I/O write command and send it to the database or file.

© 2003 - 2007 Relational Solutions, Inc. - All rights reserved