Back to Index |

References

BlueSky Integration Studio allows you to reference external .NET components either from a 3rd party, or your own custom .NET component class libraries. Below are some reasons why you would want to reference external components:

| If you want to use the .NET Data Provider object for your specific database and you have a .NET component provided by the database vendor, you will need to reference it prior to using it. You also must include the corresponding Import statement. For instance, Oracle offer a .NET component called ODP.NET (Oracle Data Provider) which is highly optimized to work specifically with an Oracle database. You can download the component through Oracle's web site for free. See example below of referencing the ODP.NET data provider.
| You can written a few class library that contains custom logic pertaining to your specific business. If those custom classes are compiled in a Component library (.dll), you can reference your custom classes from anywhere within your job.
| You have purchased or downloaded a custom component from a 3rd party vendor that you would like to use in your job. Maybe its a reporting component that you want to use to output a report after your job runs, or telnet control so you can automate jobs on a Unix system...

You can get to the references window by selecting the Build->References menu option. This window will import all the available .NET components found on your server you are connected to. You can select an existing component that is listed in the GAC, or reference it directly by clicking the browse button.

NOTE: There are instances where a component may be in the GAC (Global Assembly Cache), but cannot be found at compile-time. If you find that BlueSky Integration Studio is unable to find the component, simply reference it directly by clicking the Browse button and selecting the .NET component .dll file.

Note the selected item above. The system is referencing the ODP.NET (Oracle Data Provider) .NET component, this allows the job to use and reference Oracle databases using the .NET Data Provider object. To reference this component, I simply chose the Browse button and selected the Oracle.DataAccess.dll in the Oracle directory.

Many of the large database vendors are beginning to either include .NET Data Providers with their database software, or making them available for download from their web sites.

Click OK.

Now that you've referenced the .NET Component, click on the Imports option on the Build menu to reference this component in the job's program code.

See also: Imports

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