全部

1·We again used the order entry workload described briefly above.

我们再次使用前面简要描述过的订单输入工作负载。

2·Lotus Expeditor now has connectivity to the order entry server.

现在Lotus Expeditor连接到订单输入服务器。

3·The order entry application updates the order status to Received.

订单输入应用程序将订单状态更新为Received。

4·The Order Entry sample is really two separate interface samples.

Order Entry 示例实际上是两个单独的界面示例。

5·A basic Order Entry Server is also provided as part of the sample.

作为示例的一部分，同样提供了一个基本的Order Entry Server。

6·The components are automatically procured before the sales order entry.

这样组件在销售订单创建以前就自动获取了。

7·The order entry application then pulls all updates since the last successful sync.

然后，订单输入应用程序拉出自最后一次成功同步之后的所有更新。

8·If any ordered item cannot be fulfilled, the procedure rolls back the order entry.

如果有任何订购项没有得到满足，过程将回滚该订单条目。

9·The order entry application pushes all pending updates in the local database to the server.

订单输入应用程序将本地数据库中所有待解决的更新都推到服务器。

10·The order entry application writes custom code to exchange messages from and to WebSphere MQ.

订单输入应用程序通过编写定制代码与WebSphere MQ交换消息。