All client mode API calls execute in three steps.
所有客户机模式API调用都按以下三个步骤执行。
XA transactions are not available in client mode when using the base WebSphere MQ client.
在使用基础WebSphereMQ客户机时，XA事务在客户端模式中不可用。
Client mode performance can vary with network load, even to the point of breaking the connection.
客户机模式性能可能因网络负载，甚至断开连接的点的不同而不同。
Dynamic programming model: JAX-WS's dynamic client model is quite different from the JAX-RPC mode.
动态编程模型：JAX - WS的动态客户端模式与JAX - RPC模式差别很大。
There are a few WebSphere MQ configuration details required to accept a client mode connection.
存在一些接受客户机模式连接所需的WebSphereMQ配置详细信息。
In the in-process client mode, the entire redaction server runs as a part of the client application.
在进程内客户端模式中，整个编校服务器作为客户端应用程序的一部分运行。
Once the object is obtained, your program can use its methods in the same way as it does in the remote client mode.
获取对象后，您的程序可与在远程客户端模式下相同的方式使用它的方法。
A client mode connection is created by passing a string identifying a destination address to the Connector.open method.
通过将标识着目的地址的字符串传递到Connector. open方法来创建客户机方式连接。
In the remote client mode, a program on a remote (or local) client machine invokes the redaction server via a SOAP connection.
在远程客户端模式中，远程(或本地)客户端机器上的程序通过SOAP连接调用编校服务器。
There are two modes to use the redaction service from a custom application with the API: a remote client mode and an in-process client mode.
使用该API，可通过两种模式从自定义应用程序使用编校服务：远程客户端模式和进程内客户端模式。
The trick is in how you authenticate remotely connected users, applications connecting in client mode, and connections from other queue managers.
问题在于，您如何对远程连接用户、以客户端模式连接的应用程序以及来自其他队列管理器的连接进行身份验证。
It is therefore recommended to use transacted sessions and code explicit commit and rollback method calls when client mode is (or might be) used.
因此，当使用(或可能使用)客户机模式时，建议使用事务处理会话和代码显式commit和rollback方法调用。
But the bindings and client mode are fundamentally different because, in client mode, a channel exists between the application and the queue manager.
但是绑定和客户端模式是根本不同的，因为在客户端模式下，通道存在于应用程序和队列管理器之间。
To guarantee security of the messages traveling over the network, the client mode must be configured to support SSL and J2C authentication alias.
为了保证在网络上传输的消息的安全，必须将客户机模式配置为支持ssl和j2c身份验证别名。
When the queue manager and application server are hosted by different machines connected by a network, then a client mode connection is required.
当队列管理器和应用服务器由网络连接的不同计算机承载时，将需要客户端模式连接。
The two approaches are called bindings mode and client mode. It is important to understand the differences, advantages, and disadvantages of each mode
这两种方法称为绑定模式和客户机模式。
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.
使用绑定模式成功执行示例后，您可以重新回到此步骤，并使用客户机模式定义运行jmsadmin脚本。
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.
此参数的缺省值是启用；请注意，禁用它可能对队列管理器带来负面影响。尤其是在使用客户机模式连接时。
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.
对于演示程序，提供了两个连接工厂目录定义，一个配置为绑定模式，另一个配置为客户机模式，如下所示。
On the application side, it is possible to take a bindings mode application and run it in client mode without any changes, and in many cases, this is exactly what happened.
在应用程序端，可以接受绑定模式的应用程序，并在客户端模式下运行而不做任何更改，在许多情况下，这就是确切的实际做法。
You'll also find that if you're default mode is "client mode" you'll naturally perform at a higher level over time - it's like the old saying goes - people live up to expectations.
同样如果你与人沟通的模式是在用“客户模式”，那么你很自然地会表现出更高水平。这就像老话说的，心有多大就能走多远。
Even if the queue manager is co-located with the WebSphere Application Server, you must use client mode to communicate with it because bindings mode does not support SSL connections.
即使队列管理器与WebSphereApplicationServer运行在同一计算机上，您也必须使用客户端模式来进行通信，这是因为绑定模式并不支持SSL连接。
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.
由于绑定模式不适合在此情况下使用，因此需要确保WebSphereMQ队列连接工厂配置为使用客户机模式进行通信。
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
传输参数也是必需的，它通知JMS是使用客户机模式连接，还是使用绑定模式连接。
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.
在以客户机模式运行时，这一点尤其重要，因为从队列删除消息和通过网络将其发送到应用程序之间存在一个延迟。
The application does not need to know whether it is connecting via client or bindings mode, nor the name of the queue manager.
应用程序不需要知道是否通过客户机或绑定模式连接，也不需要知道队列管理器的名称。
If this really is a difference in kind, as I am arguing, the right approach would be to design client and binding mode applications differently.
正如我所主张的，如果这真的是种类上的差异，则正确的方法将是以不同的方式设计客户端和绑定模式应用程序。
If "bindings then client" transport mode is chosen, channel exits will only be driven if the bindings mode connection fails.
如果选择“绑定然后客户端”传输模式，则仅在绑定模式连接失败时，才驱动通道出口。
This mode gives a client application control over the redaction server life cycle.
此模式为客户端应用程序提供了对编校服务器生命周期的控制。
This mode gives a client application control over the redaction server life cycle.
此模式为客户端应用程序提供了对编校服务器生命周期的控制。
应用推荐