一个API出口拦截绑定模式调用。
这两种方法称为绑定模式和客户机模式。
The two approaches are called bindings mode and client mode. It is important to understand the differences, advantages, and disadvantages of each mode
绑定模式下的身份验证。
出于上面列出的原因，只要有可能，就请使用绑定模式。
For the reasons outlined above, use bindings mode whenever possible.
scp——将定义为连接工厂的受管理对象设置为使用绑定模式。
JmsdemoJNDIbindings.scp - administered object definitions with a connection factory set to use bindings mode.
示例代码包括客户机和绑定模式的连接工厂，以演示如何实现二者。
The sample code includes connection factories for both client and bindings mode to demonstrate how to implement both.
绑定模式和客户机模式之间的消息客户机api中不存在任何差异。
There is no difference in the messaging client API between bindings mode and client mode.
取消绑定模式还适用于类似于电子表格的表或稀疏填充的表。
Unbound mode is also suited for spreadsheet-like or sparsely populated tables.
在本地绑定模式连接中，主体是与连接到队列管理器的进程相关联的帐户。
For a local bindings mode connection, the principal is the account associated with the process that is connecting to the queue manager.
您可以在绑定模式和客户机模式之间自由切换，而不会影响示例应用程序。
You can switch freely between bindings mode and client mode without affecting the sample application.
因为绑定模式连接使用共享内存，所以不存在与网络连接上的传输关联的开销。
Because the bindings mode connection USES Shared memory, there is no overhead associated with transport over a network connection.
然后代理使用绑定模式与队列管理器对话，从而代表应用程序执行api调用。
The agent then talks to the queue manager using bindings mode, performing API calls on behalf of 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 "bindings then client" transport mode is chosen, channel exits will only be driven if the bindings mode connection fails.
传输参数也是必需的，它通知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
如果有用户或应用程序以绑定模式连接(使用共享内存)，操作系统将使用ID和密码对其进行身份验证。
If there are users or applications connecting in bindings mode (using Shared memory), the operating system will authenticate them using an ID and a password.
对于演示程序，提供了两个连接工厂目录定义，一个配置为绑定模式，另一个配置为客户机模式，如下所示。
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.
当处于绑定模式时，为了能够在按绑定列对控件进行排序时保留未绑定列的值，此模式是必需的。
This is necessary to maintain the values of unbound columns in bound mode when the control is sorted by bound columns.
正如我所主张的，如果这真的是种类上的差异，则正确的方法将是以不同的方式设计客户端和绑定模式应用程序。
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.
远程应用程序通过SVRCONN通道建立连接与本地应用程序采用绑定模式建立连接所需的权限是相同的。
The authorizations that are granted are the same for a remote application connecting over a SVRCONN channel as they are for a local application connecting in bindings mode.
应用程序如何使用两种模式(绑定模式和客户机模式)中的任一模式附加到WebSphereMQ。
How an application can attach to WebSphere MQ using either of two modes, bindings and client.
在绑定模式中，JMS应用程序必须在与队列管理器相同的主机上运行，它们将使用进程间通讯(IPC)协议进行通信。
In bindings mode, a JMS application must run on the same host machine as the queue manager, and they will communicate using Inter-Process Communication (IPC) protocols.
请将这与绑定模式下的断开连接做一下比较，后者几乎由队列管理器立即检测，然后回滚事务，通常是在几毫秒之内。
Compare this to a broken connection in bindings mode that is detected almost immediately by the queue manager, which then rolls back the transaction, typically within a few milliseconds.
如果选择了bindings - then - client传输模式，那么只有在绑定模式连接失败时才使用通道出口。
If the bindings-then-client transport mode is chosen, channel exits will only be driven if the bindings mode connection fails.
由于绑定模式不适合在此情况下使用，因此需要确保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.
在应用程序端，可以接受绑定模式的应用程序，并在客户端模式下运行而不做任何更改，在许多情况下，这就是确切的实际做法。
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.
在mq队列管理器与WebSphereApplicationServer运行于同一节点的配置中，使用绑定模式可提供性能优势。
In configurations where the MQ queue manager is running on the same node as WebSphere Application Server, using bindings mode offers a performance advantage.
即使队列管理器与WebSphereApplicationServer运行在同一计算机上，您也必须使用客户端模式来进行通信，这是因为绑定模式并不支持SSL连接。
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.
我们也许需要创建更多的模式绑定，这取决于我们想生成的组件和服务的数量。
Depending on the number of components and services we want to generate, we may need to create many more pattern bindings.
应用推荐