Identifying the .NET assembly at run time
The rules that govern how the .NET assembly is loaded from the integration node file system if it is not packaged in the BAR file.
About this task
Application domains
About this task
- The AppDomain name property of a .NET node specifies the application domain in which the assembly is to be loaded. If a DotNetAppDomain configurable service is defined with the same name as the AppDomain name of the node, the configurable service properties take precedence when the assembly is loaded. Such properties include the Application Base directory property.
- When an ESQL procedure invokes a .NET assembly, the signature of the procedure can specify the application domain in which the assembly must be loaded. If a DotNetAppDomain configurable service is defined with the name which is specified for the application domain in the signature of the ESQL procedure, the configurable service properties (for example the Application Base directory) take precedence when the assembly is loaded.
- The name of the application, if deployed within an IBM Integration Bus application
- The name of the integration server, if deployed in a flow which is not defined within an IBM Integration Bus application
Application base directory
About this task
- If the Application domain property refers to a configurable service,
the ApplicationBase property of the configurable
service is used. Use this approach in production environments. Note: The configurable service properties, including ApplicationBase, always take precedence even if you have deployed a .NET application domain containing the assemblies to the run time. In this situation, to ensure that the .NET assembly is loaded from the .appdomainzip and not from the Application Base directory, ensure that the configurable service ApplicationBase property is blank.
- If the Assembly name property of the .NET node (or equivalent part of the ESQL procedure signature) specifies an absolute location in the file system, this full directory path is used as the Application Base directory.
- If the Assembly name property of the .NET node (or equivalent part of the ESQL procedure signature) specifies just the name of the .dll file with no path, the integration node uses a subdirectory of the runtime integration node's work path for the Application Base directory. This directory might change; consider using one of the alternative approaches.
Assembly loading and the Global Assembly Cache
About this task
You have to restart the integration server if you want to reload or update a Strong-Named assembly.