About this task
The .NET framework separates application assemblies to run
in a particular application domain that provides a scope for the resources
for an application. In
IBM® Integration Bus,
the integration server operating system process (DataFlowEngine) hosts
the CLR. Within this process, .NET assemblies can be executed within
multiple application domains if required.
- 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.
If no application domain is specified by the preceding methods,
the application domain in which the assembly is loaded is determined
by:
- 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
If the application domain is determined by the name of the application
or the name of the integration server, and a
DotNetAppDomain configurable
service is defined with the same name, the configurable service properties
(for example, the
Application Base directory)
take precedence when the assembly is loaded. If the application name
or integration server name includes space characters, these characters
are ignored when the application name or integration server name is
compared to the name of the configurable service.