Attach a DotNet Application Domain policy to one or more .NET nodes in a message flow to define .NET configuration or specify the location of the .NET assembly to load.
You use the .NETInput node to retrieve data from sources like MSMQ, files, or databases, by accessing the data through .NET code. You use a .NETCompute node to build output messages and interact with Microsoft .NET Framework (.NET) or Component Object Model (COM) applications. You can use a DotNet Application Domain policy to control, at run time, the location from which assemblies are loaded, and an XML configuration file that is used to configure the domain.
To attach a DotNet Application Domain policy to a .NET node, set the AppDomain name property of the .NETInput or .NETCompute node to the name of the policy, in the format {policyProjectName}:policyName. You must deploy this policy before the associated message flow is started.
Property | Property name in .policyxml file | Value |
---|---|---|
Application base | ApplicationBase | This property specifies the base directory for the application domain from which assemblies
are loaded. Note: The policy properties, including Application base, always take precedence
even if you have deployed a .NET application domain that contains 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 this
Application base property of the policy is blank.
Value type: String |
Shadow copy files | ShadowCopyFiles | This property controls whether assemblies for this application domain are loaded in place, or
copied into a private location and loaded from there. An assembly that is loaded in place is locked
while it is being used and cannot be updated dynamically. Set this property to
true (the default) or false. Value type: Boolean |
Private BIN path | PrivateBinPath | This property provides a semicolon-separated list of sub-directories below the Application
Base that are probed for assemblies, in addition to the Microsoft defaults. Value type: String |
Configuration file | ConfigurationFile | This property identifies an XML configuration file that is used to configure the domain. This
property is a published format from Microsoft. It is used
to set container and application-specific properties and is loaded when the application domain is
initialized. The value can specify a base name or a fully qualified path. The base name is acquired
from the Application Base directory. Value type: String |
Private BIN path probe | PrivateBinPathProbe | This property specifies whether the Application Base directory is probed for assemblies. If
the property is set to false (the default), only the sub-directories that are
specified in the Private BIN path property and any Microsoft defaults are probed. Value type: Boolean |
Disallow code download | DisallowCodeDownload | This property controls whether the .NET application domain can download dependent code from
outside the computer where IBM® App Connect
Enterprise is installed. If the property is
set to true (the default), remote download is not allowed. Value type: Boolean |
Allow hot swap deploy | AllowHotSwapDeploy | This property specifies whether the application domain can be reloaded by changing the
assemblies on disk under the Application Base without needing to redeploy the message flow. For
example, if the Application base property specifies the output location of a Microsoft Visual Studio build, rebuilding the assembly in Microsoft Visual Studio will cause the integration server to pick up the newly
built assembly automatically. Set this property to false on a production system
to ensure that the assemblies cannot be changed accidentally in production. Note that this setting
only takes effect if the Shadow copy files property is set to
true. By default, this property is set to true. Value type: Boolean |
Use work path for shadow copy cache | UseBrokerWorkpathForShadowCopyCache | This property specifies the location that is used for shadow copying of assemblies. If you
set this property to true, the integration node working directory is used. If
you set the property to false (the default), a location under the home
directory of the ID that runs the service is used. Value type: Boolean |