对于此接口，适配器仅支持出站模式。
如果没有人敢挺身而出站反对霸凌，情况会更糟。
If no one has the courage to speak out against bullying, the situation will be worse.
接下来，定义流程入站和出站消息。
这种场景并不需要使用出站端点。
现在我们已经创建了出站服务。
遍历网络堆栈，以寻找出站调用。
什么是入站处理和出站处理？
清单4是预期的出站xml。
清单6是预期的出站xml。
此适配器仅支持出站模式。
下表说明了您为出站连接属性设置的值。
The following table explains the values that you set for the outbound connection properties.
此方法在出站流中调用。
图13显示了出站设置。
相关集使用来自入站或出站消息的值初始化。
Correlation sets are initialized with values from process inbound or outbound messages.
有两种出站映射场景。
为出站队列创建一个出站Q CF。
通用客户端接口定义出站模型中的记录及交互。
Common client interface defines records and interactions in the outbound model.
切换入站连接用户后，也切换了出站连接用户。
Whenever the inbound connection user is switched, the outbound connection user is also switched.
图2展示了出站请求的流程。
您的应用程序是否拥有可以方便出站通信的机制？
Does your application have a mechanism that you can use to facilitate outbound communication?
由出站自定义登录模块来进行标识映射和标识切换。
The identity mapping and the identity switch is performed by an outbound custom login module.
我们要在出站服务目的地中介中修改反向路由路径。
We'll modify the reverse routing path in the mediation on the outbound service destination.
出站事件（清单1）将这个值发送到高级监测模型。
The outbound event (in Listing 1) sends this value to the high-level monitor model.
在回答这些问题之前，我们需要学习出站服务的创建。
Before answering, we need to study outbound service creation.
这些数据结构用于为传入的和出站的流量存储内核数据。
These are used to store kernel data for incoming and outbound traffic.
清单5展示了插件代码自动创建的出站事件的事件定义。
Listing 5 shows the event definition for the outbound events automatically created by the plug-in code.
前面我们提到过，在创建出站服务时，向导还会创建导入。
As we mentioned earlier, when you create an outbound service, the wizard also creates an import.
取消为总线出站部署的总线服务和解压缩过滤器。
Undeploy the bus service and decompression filter for the bus off-ramp.
对于远程访问，每个代理都要求一个出站端口1918打开。
For remote access, each agent requires an outbound port 1918 to be opened.
有了这一设计，我们就有了入站服务和出站服务的单独中介。
With this design, we can have separate mediations for the inbound and outbound services.
应用推荐