WebSphere WebSphere Business Integration Message Service Clients for C/C++ Version 1.2.7 and .NET Version 1.2.6 Operating Systems: AIX, Linux, Solaris, Windows

Managed and unmanaged operations in .NET

Managed code is executed exclusively within the .NET common language runtime environment and is wholly dependent on the services provided by that runtime. An application is classed as unmanaged if any part of the application runs or calls services outside of the .NET common language run time environment.

Certain advanced functionality cannot currently be supported within the managed .NET environment.

If your application requires some functionality that is not currently supported in the fully managed environment, then you can change your application to use the unmanaged environment without requiring substantial change to your application. However, you should note that the XMS stack makes use of unmanaged code when this selection is made.

Connections to a WebSphere MQ queue manager

Managed connections to WMQ (WMQ_CM_CLIENT) do not support: Channel exits, SSL connections, XA Transactions, Non-TCP communications, and Channel compression. However, these exceptions might be supported by using an unmanaged connection (WMQ_CM_CLIENT_UNMANAGED). Refer to the WebSphere MQ Using .NET manual for in-depth information.

If you create a connection factory from an administered object in an unmanaged environment, you must manually change the value for the connection mode to XMSC_WMQ_CM_CLIENT_UNMANAGED .

Connections to a WebSphere service integration bus messaging engine

Connections to a WebSphere service integration bus messaging engine that require the use of the SSL protocol (including HTTPS) are not currently supported as managed code.

Related reference
XMSC_WMQ_CONNECTION_MODE

Concept topic

Terms of Use | Rate this page

Last updated: 18 Jun 2008

© Copyright IBM Corporation 2005, 2008. All Rights Reserved.