在第20行上，请确保设置了正确的客户机模式。
这两种方法称为绑定模式和客户机模式。
The two approaches are called bindings mode and client mode. It is important to understand the differences, advantages, and disadvantages of each mode
所有客户机模式API调用都按以下三个步骤执行。
客户机模式还需要队列管理器上的SVRCONN通道定义。
Client mode also requires a SVRCONN channel definition on the queue manager.
客户机模式性能可能因网络负载，甚至断开连接的点的不同而不同。
Client mode performance can vary with network load, even to the point of breaking the connection.
XUL沿袭了HTML的极瘦客户机模式，但稍微让它变胖了一些。
XUL takes the very-thin-client model of HTML and thickens it up a bit.
scp——将定义为连接工厂的受管理对象设置为使用客户机模式。
JmsdemoJNDIclient.scp - administered object definitions with a connection factory set to use client mode.
绑定模式和客户机模式之间的消息客户机api中不存在任何差异。
There is no difference in the messaging client API between bindings mode and client mode.
存在一些接受客户机模式连接所需的WebSphereMQ配置详细信息。
There are a few WebSphere MQ configuration details required to accept a client mode connection.
您可以在绑定模式和客户机模式之间自由切换，而不会影响示例应用程序。
You can switch freely between bindings mode and client mode without affecting the sample application.
为了保证在网络上传输的消息的安全，必须将客户机模式配置为支持ssl和j2c身份验证别名。
To guarantee security of the messages traveling over the network, the client mode must be configured to support SSL and J2C authentication alias.
传输参数也是必需的，它通知JMS是使用客户机模式连接，还是使用绑定模式连接。
The transport parameter is also required and tells JMS whether to use a client or bindings mode connection. When client mode is used, the host, chan and port parameters must be specified
此参数的缺省值是启用；请注意，禁用它可能对队列管理器带来负面影响。尤其是在使用客户机模式连接时。
The default for this parameter is to enable it; be aware that disabling it can have adverse affects on the queue manager, especially when using client mode connections.
应用程序如何使用两种模式(绑定模式和客户机模式)中的任一模式附加到WebSphereMQ。
How an application can attach to WebSphere MQ using either of two modes, bindings and client.
在以客户机模式运行时，这一点尤其重要，因为从队列删除消息和通过网络将其发送到应用程序之间存在一个延迟。
This is especially important when running in client mode because there is latency between the message being removed from the queue and when it is delivered over the network to the application.
对于演示程序，提供了两个连接工厂目录定义，一个配置为绑定模式，另一个配置为客户机模式，如下所示。
For the demo program, two connection factory directory definitions are provided, one configured for bindings mode and another configured for client mode, as shown below.
使用绑定模式成功执行示例后，您可以重新回到此步骤，并使用客户机模式定义运行jmsadmin脚本。
After having successfully executed the sample using bindings mode, you can come back to this step and run the JMSAdmin script using the client mode definitions.
因此，当使用(或可能使用)客户机模式时，建议使用事务处理会话和代码显式commit和rollback方法调用。
It is therefore recommended to use transacted sessions and code explicit commit and rollback method calls when client mode is (or might be) used.
由于绑定模式不适合在此情况下使用，因此需要确保WebSphereMQ队列连接工厂配置为使用客户机模式进行通信。
Since the binding mode is not applicable in this situation, you need to ensure the WebSphere MQ queue connection factories are reconfigured to use the client mode for communication.
应用程序不需要知道是否通过客户机或绑定模式连接，也不需要知道队列管理器的名称。
The application does not need to know whether it is connecting via client or bindings mode, nor the name of the queue manager.
示例代码包括客户机和绑定模式的连接工厂，以演示如何实现二者。
The sample code includes connection factories for both client and bindings mode to demonstrate how to implement both.
将基于客户机模块使用的调用模式自动选择sca绑定所使用的基础协议。
The underlying protocol used by the SCA binding is selected automatically based on the invocation pattern used by the client module.
REST模式假定客户机想要创建、读取、更新和删除(CRUD)远程资源。
The rest pattern assumes that clients are interested in creating, reading, updating, and deleting (CRUD) remote resources.
ApacheSandesha提供了使用Axis为具有可靠消息传递的Web服务客户机提供的所有调用模式的功能。
Apache Sandesha provides the capability of utilizing all these invocation patterns that Axis provides for web service clients with reliable messaging.
在这种方法中，客户机以非阻塞模式将一个请求发送到一个web服务端点。
In this approach, a client sends a request to a web service endpoint in a non-blocking mode.
在此模式中，客户机(应用程序)向Web服务发送信息，且并不会等待响应。
In this pattern, the client (the application) sends information to the web service and does not wait for a response.
如果在DB 2或OracleWeb服务发送信息时出现延迟，SAP Web服务客户机将进入等待模式。
If there is a delay in the DB2 or Oracle Web service sending the information, the SAP Web service client goes into a waiting mode.
在该模式下，无论客户机实际上能否连接到服务器数据存储，客户机始终与本地数据库的数据进行交互。
In this pattern, the client always interacts with data from a local database regardless of whether or not the client can physically connect to the server data store.
由于不需要通知机制和侦听器组件，这个模式使得客户机实现更为简单。
This pattern results in a simpler client implementation, as the notification mechanism and listener components are not required.
由于图6所展示的这些客户机并不在无上限模式下，所以分区本身的设置就是正确的。
Because these clients shown in Figure 6 are not in uncapped mode, the partitions themselves are set correctly.
应用推荐