名称——注册和控制用户出口的活动状态。
Name — To register and control the active state of the user exit.
在点(4)处，在事务结束时调用了用户出口。
At point (4), the user exit in invoked at the end of the transaction.
您可以指定相关逻辑以清理在用户出口中分配的资源。
You can specify the logic to cleanup the resources that are allocated in the user exit.
用户出口不是事务的一部分，并在事务完成以后被调用。
The user exit is not part of the transaction and is invoked after the transaction has completed.
我们建议采用以下逐步方法来设置和测试这个用户出口。
We recommend a step-by-step approach to setting up and testing the user exit, as follows.
接下来在点(3)处，在节点处理完成后调用了用户出口。
Next, at point (3), the user exit is invoked after the node processing is completed.
请注意，即使没有任何事务处理完成，也会调用用户出口。
Please note that the user exit is invoked even if no transactional processing is completed.
在点(1)处，紧跟在节点传播消息之前调用了用户出口。
At point (1), the user exit is invoked just before the node propagates the message.
该参数还表示用户出口程序应该用于归档和检索日志文件。
This parameter also indicates that a user exit program should be used to archive and retrieve the log files.
如果没有任何用户出口是活动的，则此功能对性能没有影响。
If no user exits are active then this feature has no effect on performance.
该参数使数据库管理器调用用户出口程序来归档和检索日志。
This parameter causes the database manager to call a user exit program for archiving and retrieving logs.
用户出口API在用户定义的c节点api中提供。
The user exit APIs are provided inside the C user-defined node APIs.
如果您构建了一个自己的自定义用户出口程序，也请告诉我们。
Please let us know if you build a custom user exit program of your own.
此函数在执行组加载用户出口 .lel 可加载文件时调用。
This function is called when the execution group loads the user exit .lel loadable file.
用户出口对消息组装做出的任何更改都将对后续的用户出口可见。
Any changes made to the message assembly by a user exit will be visible to subsequent user exits.
用户出口并不仅限于内置节点，它们适用于所有用户定义的插件节点。
User exits are not limited to built-in nodes, they are applicable to all user defined plug-in nodes.
最灵活的方法是使用一个用户出口，比如本文描述的用户出口。
The most flexible way is a user exit, like the one described in this article.
随后在点 (2) 处，在消息传播到该节点进行处理时调用了用户出口。
Subsequently, at point (2), the user exit is invoked when the message is propagated to the node for processing.
每个用户出口应该实现BipCpi.h头文件中定义的两个必备函数。
Every user exits should implement two mandatory functions defined in BipCpi.h header file.
MessageBroker只能通过此扩展名确定要加载的用户出口模块。
Message Broker understands only this extension to identify the user exit modules to load.
在MessageBroker中，用户出口仅支持使用c或c++编程语言。
In Message Broker, user exits are supported only in C or C + + programming language.
编写用户出口以后，对其进行编译并使其对MessageBroker可用。
After the user exits are written, they are compiled and made available to Message Broker.
这个用户出口的每次调用都会生成一个新的跟踪文件，因此在生产中不要开启跟踪功能。
Each invocation of the user exit will generate a new trace file, so please don't leave trace on in production.
用户出口是用户或供应商提供的可由MessageBroker调用的函数。
User exits are user or vendor-provided functions that can be invoked by Message Broker. These invocations can be triggered by the following events
API包括可以在用户出口中调用的实用工具函数，以及必须在用户出口中实现的函数。
The API consists of utility functions that can be invoked from user exits and functions that are mandatory to be implemented inside user exits.
如果注册并激活了用户出口，则性能会受到影响，具体取决于那些出口中的用户代码的性能。
If user exits are registered and activated then performance is affected depending on the performance of the user's code within those exits.
对于这其中每个事件，MessageBroker允许您使用用户出口访问特定的信息。
For each of these events, Message Broker lets you use the user exits to access specific information.
用户必须在为用户出口路径配置的目录上使用主机系统文件访问控制，以确保库不容易受到攻击。
The user must use the host systems file access controls on the directory configured for user Exits Path to ensure that the library is not vulnerable.
对于本文，我们开发了一个样例用户出口程序(参见下载部分)来将进入的警报转换为SNMP陷阱。
For this article, we developed a sample user exit program (see the Download section) to convert incoming alerts into SNMP traps.
它允许您在消息通过消息流传递时调用用户出口中的自定义代码，从而在消息生命周期中的某个点跟踪消息。
It lets you track message at certain points in their life cycle by invoking custom code from user exits while the message is passing through the message flow.
应用推荐