WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Deploying .NET assemblies

.NET assemblies can be included in a broker archive (BAR) file, or loaded directly from your broker file system.

Include the .NET assembly in the BAR file by packaging it in a .NET application domain. The application domain is packaged as a .appdomainzip at the root level of the BAR file. The .NET assembly is deployed with any other resources in the application domain.

If the .NET application domain is associated with an application, you can deploy the referencing application. The .NET assemblies in the application domain are deployed with the application. Alternatively, you can deploy the .NET application domain separately.

Deploy the application domain by right-clicking on the object in the Broker Development view, or by dragging and dropping the application domain onto an execution group in the Brokers view.

If the .NET assembly is not included in the BAR file, and is loaded directly from the broker file system, the assembly is found in one of the following ways:
  • The absolute directory path specified on a .NET node Assembly name property, or specified on an ESQL function or procedure.
  • An override to the absolute directory path in a BAR file for the .NET node.
  • A DotNetAppDomain configurable service that overrides the absolute directory path.
  • Using advanced properties to search the global assembly cache (GAC).
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:47:58


Task topicTask topic | Version 8.0.0.7 | bc34204_