Set up the event store database.
设置事件存储数据库。
Events are temporarily placed in an event store database.
事件被暂时存放在事件存储数据库中。
The adapter polls the event store and retrieves a batch of events.
适配器将轮询事件库并检索一组事件。
The event store table gets populated when one of the database triggers runs.
当其中一个数据库触发器运行时，将填充事件存储表。
Figure 6 shows the event store table after running the database creation scripts.
图6显示了运行数据库创建脚本后的事件存储表。
The events that failed to deliver are marked as “-1” in the column name “Event_Status” of the event store table.
交付失败的事件将在事件库表的 “Event_Status”列中标记为 “-1”。
To use the inbound adapter, you first need to set up the event store, which is where inbound data is temporarily stored.
要使用入站适配器，需要先设置事件存储库，这是暂时存储入站数据的地方。
The change causes a trigger or another automated mechanism, to update the event store with information about the change.
更改会造成触发器或其他自动机制使用与更改相关的信息更新事件库。
Event stores are conceptually simpler than full RDBMS solutions, and it's easy to scale up from an in-memory list of events to a full-featured event store.
事件存储器从概念上讲比全功能的关系型数据库解决方案要更简单，而且他可以很容易地从内存中的事件集合扩展到全功能的事件存储器。
The WebSphere Adapter for JDBC User Guide (see the Resources Section) explains the fields in the event store table, but let's take a quick look at how this table will be used.
WebSphereAdapterfor JDBC用户指南(请参见参考资料部分)说明了事件存储表中的字段，现在让我们简单地了解一下如何使用此表。
The WebSphere Adapter for JDBC User Guide (see the Resources Section) explains the fields in the event store table, but let's take a quick look at how this table will be used.
WebSphereAdapterfor JDBC用户指南(请参见参考资料部分)说明了事件存储表中的字段，现在让我们简单地了解一下如何使用此表。
应用推荐