Element Details: Execute.Plugin+Call
 Back


Available in: Logi Info Source code name: Execute.PluginCall

A Plugin Call runs a method inside of a Plugin. A Plugin is a .NET or Java library assembly (a DLL or JAR) containing custom code that performs actions while each request is processed. Execute.PluginCalls can run your own custom .NET or Java code.

For a more detail on plug-ins see the following DevNet article.



ATTRIBUTES

Click attribute Name to drill down for more information.

NamePossible ValuesDescription
ID
UserDefined
(Required) The ID attribute is a pervasive attribute that uniquely identifies an element within a definition file. The ID needs to be a unique value within the definition.
PluginMethod
UserDefined
(Required) The name of the Plugin's method to be called.
PluginName
UserDefined
(Required) The filename of the plugin assembly, typically ending in ".dll" for .NET or a .class file in a .jar for Java. In .NET the assembly file should normally be located in the _Plugins folder, under the application root. In Java a standalone .class file goes in WEB-INF\classes under the application root. A .jar file containing. class files goes in WEB-INF\lib under the application root. You may also specify a complete absolute path to the assembly dll in .Net. This should not be done in Java. However, the full name of the Java class including package is necessary(i.e. com.logixml.plugins.SamplePlugin10).
PluginTypeName
UserDefined
(Required) The TypeName specifies the plugin's class that contains the method that will be called. The value consists of the dll's root namespace, ".", and the class name. For example: "LogiXML.SamplePlugin.Plugin". This attributes is required for .NET plugins, and is ignored for Java plugins.



PARENT ELEMENTS

Click element to drill down for more information.

Etl Job
If
If ETL Error
If File Exists
If Folder Exists Loop.Data Layer Rows


CHILD ELEMENTS

Click element to drill down for more information.

If ETL Error


 Back to top


 Chart Debug