WebSphere MQ 7.0 .NET API入门与配置指南

5星 · 超过95%的资源需积分: 9 7 浏览量更新于2024-07-28 1 收藏 441KB PDF 举报

本文档是针对WebSphere MQ 7.0版本的.NET API的详细指南，专为.NET开发者设计。WebSphere MQ 是IBM公司提供的一种消息中间件，它在企业级应用中扮演着关键角色，通过支持可靠的消息传递和异步通信，确保了系统的高可用性和性能。该文档的第二版发布于2009年1月，适用于WebSphere MQ 7.0及后续版本，直到有新版本更新说明。文档开篇强调在使用前务必阅读注意事项，包括版权信息和对美国政府用户的规定，可能受到GSA ADP Schedule合同约束。内容分为多个章节，涵盖了丰富的知识点： 1. 用户指南：这部分引导读者如何入门，介绍了WebSphere MQ 在.NET中的作用，比如它是如何提供的类库，以及开发人员可以使用的连接选项。这包括了如何配置队列管理器以接受来自TCP/IP客户端的连接，这对于设置网络环境和与MQ进行通信至关重要。 2. 安装：文档详细解释了如何在.NET环境中安装和设置WebSphere MQ，包括可能遇到的步骤和配置要求，确保开发人员能够顺利集成MQ到他们的项目中。 3. 使用WebSphere MQ .NET类：这部分深入讨论了如何实际使用WebSphere MQ提供的.NET API，如创建连接、发送和接收消息、管理队列等核心功能。作者还可能提供了示例应用程序，展示了这些API在实际项目中的应用，帮助读者理解和掌握其用法。 4. 配置细节：对于每个功能，文档都提供了具体的配置步骤和最佳实践，例如设置安全选项、优化性能参数等，以便开发人员根据项目需求进行个性化设置。 5. 图表和表格：文档中包含了许多图形和表格，用于辅助解释复杂的概念或列出关键配置参数，使学习过程更加直观和易于理解。通过阅读这份文档，.NET开发者可以全面了解如何在WebSphere MQ 7.0中高效地构建和管理消息传递系统，无论是新手还是经验丰富的开发者，都能从中找到所需的信息。

6 WebSphere MQ: Using .NET

WebSphere MQ classes for .NET class library

WebSphere MQ classes for .NET is a set of classes that enable .NET applications to

interact with WebSphere MQ.

They represent the various components of WebSphere MQ which your application

uses, such as queue managers, queues, channels and messages.

For details of these classes, see “The WebSphere MQ .NET classes and interfaces”

on page 27

Writing WebSphere MQ .NET programs

To use WebSphere MQ classes for .NET to access WebSphere MQ queues, you

write programs in any language supported by .NET containing calls that put

messages onto, and get messages from, WebSphere MQ queues.

This chapter provides information to assist with writing applications to interact

with WebSphere MQ systems. For details of individual classes, see “The

WebSphere MQ .NET classes and interfaces” on page 27.

Connection differences

The way you program for WebSphere MQ .NET has some dependencies on the

connection modes you want to use.

Managed client connections

When WebSphere MQ classes for .NET are used as a managed client, it is similar

to a client bindings connection, but has a number of differences.

The following features are not available:

v Channel compression

v SSL support

v XA transactions

v Channel exit chaining

If you try to use these features with a managed client, it will return an

MQException. If the error is detected at the client end of a connection, it will use

reason code MQRC_ENVIRONMENT_ERROR. If it is detected at the server end,

the reason code returned by the server will be used.

Channel exits written for a non-managed client do not work. You must write new

exits specifically for the managed client. Check that there are no invalid channel

exits specified in your client channel definition table (CCDT).

Communication is supported only over TCP/IP.

When you stop a queue manager using the endmqm command, a

server-connection channel to a .NET managed client can take longer to close than

server-connection channels to other clients.

If you use the trace facility, you cannot choose to trace specific threads or

processes.

For general information on WebSphere MQ clients, see WebSphere MQ Clients.

8 WebSphere MQ: Using .NET

Defining which connection type to use

The connection type is determined by the setting of the connection name, channel

name, the customization value NMQ_MQ_LIB and the property

MQC.TRANSPORT_PROPERTY.

You can specify the connection name as follows:

v Explicitly on an MQQueueManager constructor:

public MQQueueManager(String queueManagerName, MQLONG Options, string Channel,

string ConnName)

public MQQueueManager(String queueManagerName, string Channel, string ConnName)

v By setting the properties MQC.HOST_NAME_PROPERTY and, optionally,

MQC.PORT_PROPERTY in a hashtable entry on an MQQueueManager

constructor:

public MQQueueManager(String queueManagerName, Hashtable properties)

v As explicit MQEnvironment values

MQEnvironment.Hostname

MQEnvironment.Port(optional).

v By setting the properties MQC.HOST_NAME_PROPERTY and, optionally,

MQC.PORT_PROPERTY in the MQEnvironment.properties hashtable.

You can specify the channel name as follows:

v Explicitly on an MQQueueManager constructor:

public MQQueueManager(String queueManagerName, MQLONG Options, string Channel,

string ConnName)

public MQQueueManager(String queueManagerName, string Channel, string ConnName)

v By setting the property MQC.CHANNEL_PROPERTY in a hashtable entry on an

MQQueueManager constructor:

public MQQueueManager(String queueManagerName, Hashtable properties)

v As an explicit MQEnvironment value

MQEnvironment.Channel

v By setting the property MQC.CHANNEL_PROPERTY in the

MQEnvironment.properties hashtable.

You can specify the transport property as follows:

v By setting the property MQC.TRANSPORT_PROPERTY in a hashtable entry on

an MQQueueManager constructor:

public MQQueueManager(String queueManagerName, Hashtable properties)

v By setting the property MQC.TRANSPORT_PROPERTY in the

MQEnvironment.properties hashtable.

Select the connection type you require by using one of the following values:

MQC.TRANSPORT_MQSERIES_BINDINGS - connect as server

MQC.TRANSPORT_MQSERIES_CLIENT - connect as non-XA client

MQC.TRANSPORT_MQSERIES_XACLIENT - connect as XA client

MQC.TRANSPORT_MQSERIES_MANAGED - connect as non-XA managed

client

You can set the customization value NMQ_MQ_LIB to explicitly choose the

connection type as shown in the following table

Chapter 2. Programming with WebSphere MQ classes for .NET 9

NMQ_MQ_LIB value Connection type

mqic.dll Connect as a non-XA client

mqicxa.dll Connect as an XA client

mqm.dll Connect as a server

managed Connect as a non-XA managed client

Note: Values of mqic32.dll and mqic32xa.dll are accepted as synonyms of mqic.dll and

mqicxa.dll for comatibility with earlier releases.

If you choose a connection type which is unavailable in your environment, for

example you specify mqic32xa.dll and don’t have XA support, WebSphere MQ

.NET throws an exception.

Setting NMQ_MQ_LIB to ″managed″ causes the client to use managed WebSphere

MQ problem diagnostics, .NET data conversion, and other managed low-level

WebSphere MQ functions.

All other values for NMQ_MQ_LIB cause the .NET process to use unmanaged

WebSphere MQ problem diagnostics and data conversion, and other unmanaged

low-level WebSphere MQ functions (assuming a WebSphere MQ client or server is

installed on the system).

WebSphere MQ .NET chooses the connection type as follows:

1. If MQC.TRANSPORT_PROPERTY is specified, it connects according to the

value of MQC.TRANSPORT_PROPERTY.

Note, however, that setting MQC.TRANSPORT_PROPERTY to

MQC.TRANSPORT_MQSERIES_MANAGED does not guarantee that the client

process runs managed. Even with this setting, the client is not managed in the

following cases:

v If another thread in the process has connected with

MQC.TRANSPORT_PROPERTY set to something other than

MQC.TRANSPORT_MQSERIES_MANAGED.

v If NMQ_MQ_LIB is not set to ″managed″, problem diagnostics, data

conversion and other low-level functions are not fully managed (assuming a

WebSphere MQ client or server is installed on the system).

2. If a connection name has been specified without a channel name, or a channel

name has been specified without a connection name, it throws an error.

3. If both a connection name and a channel name have been specified:

v If NMQ_MQ_LIB is set to mqic32xa.dll, it connects as an XA client.

v If NMQ_MQ_LIB is set to managed, it connects as a managed client.

v Otherwise it connects as a non-XA client.

4. If NMQ_MQ_LIB is specified, it connects according to the value of

NMQ_MQ_LIB.

5. If a WebSphere MQ server is installed, it connects as a server.

6. If a WebSphere MQ client is installed, it connects as a non-XA client.

7. Otherwise, it connects as a managed client.

Client configuration files

A WebSphere MQ classes for .NET client application can use a client configuration

file in the same way as any other WebSphere MQ client.

10 WebSphere MQ: Using .NET

剩余164页未读，继续阅读

nsdwn

粉丝: 7
资源: 2

WebSphere MQ 7.0 .NET API入门与配置指南

WebSphere MQ V7.0：特性与增强详解

IBM MQ for .NET开发实战指南

WebSphere MQ Java 教程文档

websphere mq 7.0新功能介绍

WebSphere MQ 7.0nd 64bit 安装情况总结

WebSphere MQ7.0配置与测试（java 源码,含图）

IBM MQ 7.0全部帮助文档

IBM MQ for .net开发文档

IBM WebSphere Portal 7.0 API

WebSphere MQ V7.0 jar

最新资源