Back to Index |

Compiling Jobs

BlueSky Integration Studio offers 3 deployment options.

- Server Executable Jobs (.exe)

Let BlueSky Integration Studio manage your integration jobs! BlueSky Integration Studio compiles your design into a true .NET executable and stores it in the server repository. There are no code interpreters here to slow things down! BlueSky Integration Studio jobs are fast, compiled executables taking full advantage of the .NET Framework’s managed code and memory features. Once your job is compiled you have complete control in the Job Control window to Run your job, check output logs, schedule your job and even monitor its progress in real-time!

- .NET Component (.dll)

Stop hand-coding your data processing logic! In BlueSky Integration Studio, you simply design your process, compile it to a .NET component and reference it from your code. Not only will your data processing logic be done in record time, but also maintenance down the road will be much faster. Want to make a change? Simply open your design, make your change, re-compile, and update the component in your .NET application’s directory! You don't even have to re-compile your application!

- Source code (available in the Enterprise Editions)

Your a developer, we understand! You want complete control over your software and you need to understand, and have control over every part of it. Who are we to limit you? BlueSky Integration Studio will give you every line of code for any integration job you can design. How does this thing work anyway? See for yourself – we have no secrets! BlueSky Integration Studio generates every line of VB.NET code for you. No proprietary external components or libraries are used. How did we write that Excel file? How do we use XML Serialization to output objects on the fly? How did your job send that e-mail? .... you can see it and use it all!

How does the compilation process work?

BlueSky Integration Studio breaks the design down into logical classes based on each object. It then calculates a complex decision tree to understand the process flow of your design and generates highly optimized code specific to the design. The server then compiles the code to a true .NET executable (.exe), .NET component (.dll), or outputs the actual source code (Enterprise only), depending on the deployment option you selected. All executables, components and source codes are royalty-free!

The Menu and toolbar options

The Build menu contains all of the deployment options. They are also located right on the toolbar for quick access. Here is a description of each option:

Option | Description
Job Documentation | This option will automatically document your entire job for you, saving you countless hours of hand documenting you processes.
Pre-compile | The Pre-compilation function is done automatically prior to every type of build process. You can also run in manually from this menu option. Pre-compile is basically just a pre-check of the job to capture the obvious errors and warnings. For instance, if you forgot to enter the ColumnLayout of one of the data objects. Typically, the pre-compile doesn't stop you from attempting to compile your job anyway, it is simply there as a mechanism to warn you of potential problems.
Executable | The build Executable process breaks your job down and generates a highly optimized program based on the job design. It then compiles the program into a true .NET executable program (.exe) and manages it in the BlueSky Integration Studio repository where you can automate and manage its execution.
Component | The build Component process also breaks your job down and generates a highly optimized component class based on the job design. You can then save this component to your local development machine and reference it directly from your own .NET applications. Methods are built into the component to give you complete control over its execution including things like Run, Stop, Reset, GetLogs, GetStatistics, SetParameterValue, etc... See Using a Job component in your .NET application
Source Code | The source code option, which is available only in the Enterprise Edition of BlueSky Integration Studio, allows you to generate a job directly into VB.NET code. This is the actual code that is used to generate either the Executable or Component above. Many customers find this useful for embedding a job directly into their custom software saving them hours and hours of hand coding. Our education customers love it because their students can break the code down and gain valuable insight into VB.NET programming methods. You can also pull out specific classes, such as the Mail Object, Data object, logging classes to use in your own programs royalty free.
Execution Path | Each BlueSky Integration Studio design can contain just one, or multiple Join objects. The Join object is the core progress of the specific integration task with each job. The execution path option generates the decision tree for the job and displays the order in which the Join object processes will run. The execution path is also done automatically as part of every build process for you.
References | BlueSky Integration Studio can be configured to reference external components including 3rd party component libraries, or your own custom class libraries. This give you the ability to add functionality to the BlueSky Integration Studio system and make it better to fit your exact transformation needs.
Imports | Once you reference an external component library, you can insert an Import statement which will be included in your job. For instance, if you create a class library which contains a namespace of MyCompany.MyStuff you can include the line Import MyCompany.MyStuff so that you can reference the classes in the class library directly, rather than always having to type the full canonical name. For instance, if your library contains a class named UPCClass, instead of having to reference it as MyCompany.MyStuff.UPCClass you could simply use UPCClass directly.

Compiling a job

Compiling your job is extremely easy! BlueSky Integration Studio does the work for you, you simply need to select the deployment option. Once your job is designed:

- Select the deployment option from either the Build menu, or the toolbar. The first thing that will occur is a quick pre-compile of the design. This will check your job for obvious errors prior to compilation.

- If you have pre-compile warnings, you should click the View Warnings button to view the warnings. The pre-validation checks typically will not stop you from attempting to compile your job, it is simply a mechanism to warn you of obvious potential problems.

- Click the Compile button. BlueSky Integration Studio will generate your job program and compile it.

- If you chose the Executable option, your executable program will be placed in the BlueSky Integration Studio repository where you can begin using it immediately from the Job Control window.

- If you chose the Component option, BlueSky Integration Studio will prompt you to select a directly on your local machine to download the component to, including any external referenced supporting files and the parameter file if necessary. (See Using a Job component in your .NET application)

- The source code option will bring up the Windows Save dialog box where you can select a filename and path for the source code. You can name the file anything you would like, however normally you will want to name the file with a .vb extension for easy import into your .NET project if necessary.

Viewing Pre-compile warnings

If you job does contain pre-compile warnings you can view them by clicking the View Warnings button, or by selecting the Build->Pre-compile option on the menu. The window will tell you exactly which object and properties contains the warnings. For instance below, the job has no ColumnLayout set on the "My Budget Excel File" object, and the "SQL Server in Cleveland" object requires that the Action property be set to something other than None because it is an output object.

Simply fix the errors and warnings, then re-compile.

<<Prev

Designing the process flow
Defining Properties
Mapping and Transformation
Compiling Jobs

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