最后，还有消息存储的选项。
将消息存储为字符会影响显示消息的方式。
The storing of messages as characters has implications for the way messages are displayed.
您可以使用下面的代码来把消息存储到会话中。
You use the following code to store the message into the session.
然后，将required消息存储到msg变量。
消息存储用于短期队列和存储-转发类型的架构当中。
Message storage is meant for short term queuing and store-and-forward type architectures.
接受默认消息存储“FileStore”并转到下一屏幕。
Accept the default message store as "File store" and go to the next screen.
SQS把每个消息存储在多台服务器上，从而提供冗余和高可用性。
Each of your messages is stored on multiple servers by SQS to provide redundancy and high availability.
您需要将接收到的消息存储在portletsession类型的对象中。
You need to store the received message in an object of type PortletSession.
如果消息目标离线，就把消息存储在磁盘上，当目标系统再次上线时可以继续处理消息。
If the message target is offline, the message is stored on disk so it can be processed once the target system is back online.
消息存储在队列里，MQ服务器允许您将消息加入到队列以及从队列中取走消息。
Messages are stored in queues, and MQ servers allow you to enqueue messages onto queues, and dequeue messages from them.
在前一部分中，您看到了如何将接收到的消息存储到portletsession类型的对象中。
In the previous section, you saw how to store the received message into an object of type PortletSession.
GIOP 1.1添加了对消息存储碎片的支持，GIOP 1.2添加了双向通信支持。
GIOP 1.1 added support for message fragmentation and GIOP 1.2 added support for bidirectional communication.
根据不同的缓存策略，它可能还需要注册阶段0协议来将日志消息存储到数据库中在事务完成之前。
Depending on caching strategy, it might also register for the phase zero protocol to flush log messages upon transaction completion.
您还可以选择消息存储类型(数据存储或文件存储)，以帮助提高性能并简化配置和管理工作。
You also have a choice of message store types (date store or file store), to help improve performance, and ease configuration and administration.
即便它们的集群解决方案也不能解决这个问题，因为这不是文件访问问题，而是文件内容(消息存储数据)问题。
Even their clustering solution doesn't help with this type of storage corruption because it's not file access, but file content (message store data) that's the problem.
将DB 29配置为与esb一起使用与我们的案例相关，因为我们在尝试使用日志中介将消息存储为xml格式。
Configuring DB2 9 for use with ESB becomes relevant in our case as we are attempting to use the logging mediation to store the message as XML.
Orders是分别发送的，并为稍后聚合为单个响应消息存储每个订单的响应，从而显示批处理请求中所有元素的状态。
Orders are sent individually, the response from each order being stored for later aggregation into a single response message, which shows the status of all the elements in the batch request.
上面的流程整体上提供了一种可靠消息传递机制：一个客户端发送一条日志请求，服务器在完成消息存储之后发送一条确认信息。
The flow described above principally provides a mechanism for reliable messaging: a client sends a logging request and the server sends an acknowledgement once it has persisted the message.
a MQ消息存储(AMQ Message Store)——这是一个嵌入式、事务性的消息存储，可用来进行快速、可靠的持久化。
AMQ message Store, which is an embeddable transactional message storage that can be used for fast and reliable persistence.
当客户机没有连接而不需要存储消息时，也应该将cleanstart 的值设置为true，这确保不将多余的消息存储在代理中。
True should also be used if the client does not require messages to be stored while it is not connected, this ensures that unnecessary messages do not get stored on a broker.
如果在使用SIB持久化消息传递时发现磁盘资源争用现象，并希望将消息存储库迁移到更快的远程磁盘驱动器，请遵循以下说明。
If you see disk contention when using sib persistent messaging and want to move the message store to a different, possibly faster disk location, follow the instructions here.
通常，服务质量(QoS)1或2(以后将有更多这样的服务质量级别)主题上的消息存储在当前没有连接的订阅服务器的代理中。
Generally, messages on topics with a Quality of Service (QoS) 1 or 2 (more on this later) are held on the broker for subscribers that are not currently connected.
如果用例需要将服务的消息存储在消息引擎中，并跨服务器重启，则需要在其SCDL中指定以下代码(对于“OrderStatusService”服务)。
A use case that requires messages for a service be stored in a message engine and persist across server restarts would need to specify the following in its SCDL (for the "OrderStatusService" service).
在这里，邮箱类似于实际生活中的邮箱，消息可以存储并供其他角色检索，以便处理。
A mailbox, in this case, is just like one in real life - messages can be stored and retrieved for processing by other actors.
可以使用两个新部件管理发送到目标服务的消息的存储和转发。
Two new widgets are used to manage the store and forward of messages sent to a target service.
当设备联机时，设备队列管理器会将消息从存储转发设备提取出来。
When a device comes online, the device queue manager pulls messages from the store-and-forward facility.
实际上，我们可以控制是存储整个控制消息以便传播，还是仅存储该消息的部分内容。
We actually can control whether the entire control message is stored for propagation or only a portion of the message.
这是WS - RM存储消息和序列状态的地方。
消息引擎具有其自身数据存储的专用控件，因此其他消息引擎不能链接到它的数据存储。
A message engine has exclusive control of its own data store, so no other message engine can be linked to that data store.
事件存储在JMS消息中。
应用推荐