tDotNETInstantiate Standard properties - Cloud

These properties are used to configure tDotNETInstantiate running in the Standard Job framework.

The Standard tDotNETInstantiate component belongs to the DotNET family.

The component in this framework is available in all Talend products.

Basic settings

Dll to load	Type in the path, or browse to the DLL library containing the classe(es) of interest or enter the assembly's name to be used. For example, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 for an OleDb assembly.
Fully qualified class name(i.e. ClassLibrary1.NameSpace2.Class1)	Enter a fully qualified name for the class of interest.
Value(s) to pass to the constructor	Click the plus button to add one or more values to be passed to the constructor for the object. Or, leave this table empty to call a default constructor for the object. The valid value(s) should be the parameters required by the class to be used.

Advanced settings

tStatCatcher Statistics	Select this check box to collect log data at the component level.

Global Variables

Global Variables	INSTANCE: the instance of a .NET object. This is an After variable and it returns an object. ERROR_MESSAGE: the error message generated by the component when an error occurs. This is an After variable and it returns a string. This variable functions only if the Die on error check box is cleared, if the component has this check box. A Flow variable functions during the execution of a component while an After variable functions after the execution of the component. To fill up a field or expression with a variable, press Ctrl+Space to access the variable list and choose the variable to use from it. For more information about variables, see Using contexts and variables.

INSTANCE: the instance of a .NET object. This is an After variable and it returns an object.

ERROR_MESSAGE: the error message generated by the component when an error occurs. This is an After variable and it returns a string. This variable functions only if the Die on error check box is cleared, if the component has this check box.

A Flow variable functions during the execution of a component while an After variable functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl+Space to access the variable list and choose the variable to use from it.

For more information about variables, see Using contexts and variables.

Usage

Usage rule	This component can be used as a start component in a flow or an independent subJob. To use this component, you must first install the runtime DLLs, for example janet-win32.dll for Windows 32-bit version and janet-win64.dll for Windows 64-bit version, from the corresponding Microsoft Visual C++ Redistributable Package. This allows you to avoid errors like the UnsatisfiedLinkError on dependent DLL. So ensure that the runtime and all of the other DLLs which the DLL to be called depends on are installed and their versions are consistent among one another. Note: The required DLLs can be installed in the System32 folder or in the bin folder of the Java runtime to be used. If you need to export a Job using this component to run it outside Talend Studio, you have to specify the runtime container of interest by setting the -Djava.library.path argument accordingly. For users of Talend solutions with ESB, to run a Job using this component in ESB Runtime, you need to copy the runtime DLLs to the `%KARAF_HOME%/lib/wrapper/` directory.

Usage rule

This component can be used as a start component in a flow or an independent subJob.

To use this component, you must first install the runtime DLLs, for example janet-win32.dll for Windows 32-bit version and janet-win64.dll for Windows 64-bit version, from the corresponding Microsoft Visual C++ Redistributable Package. This allows you to avoid errors like the UnsatisfiedLinkError on dependent DLL.

So ensure that the runtime and all of the other DLLs which the DLL to be called depends on are installed and their versions are consistent among one another.

Note: The required DLLs can be installed in the System32 folder or in the bin folder of the Java runtime to be used. If you need to export a Job using this component to run it outside Talend Studio, you have to specify the runtime container of interest by setting the -Djava.library.path argument accordingly. For users of Talend solutions with ESB, to run a Job using this component in ESB Runtime, you need to copy the runtime DLLs to the %KARAF_HOME%/lib/wrapper/ directory.