In the database design above, according to the needs, I design role table, users table, document table, department table, message table, employ table.
在数据库的设计上面，根据系统的需要，设计了角色表、用户表、部门表、文档表、员工表、短信表。
There are lots of columns in this table definition, representing every data element defined in the response message.
在这个表定义中有很多个列，它们分别表示响应消息中定义的每个数据元素。
Table 3 lists the details of the message distribution in different workloads.
表3列示了不同工作负载中的消息分布的细节。
The event monitor converts the configuration information and the event data retrieved from the event queue table into a self-describing event message in a common base event (CBE) format.
这个事件监视器能将配置信息和从事件队列表所查询的事件数据转换到一个自解释的通用基础事件(CBE)格式事件消息中。
If a bar in the breakdown view is too short to see its full name, just select it and refer to the name in the prompt message box or the left-side table that's highlighted.
如果细分视图中的某栏太短而无法看到完整的名称，只需选择该栏并在提示消息框中或左侧高亮显示的表中查阅该名称。
The view can be referenced in the message flow in the same way as the original table.
在消息流程中，引用视图的方式与引用原来的表的方式相同。
Table 3 also shows that a user-defined error message is also returned.
表3还显示用户定义的错误消息也被返回。
Moving data between a database and a message — an application may need to move data from a JMS message to a database table or vise versa.
在数据库和消息之间移动数据——应用程序需要将数据从JMS消息移动到数据库表，或者相反。
For example, if a duplicate source table row matches exactly with the same target table row that has been updated, you will see the error message.
例如，如果复制已被更新的、与相同目标表行匹配的源表行，那么您将会看到错误消息。
Where a message flow only reads data from a table, consider using a read only view of that table.
当消息流仅从表读取数据时，请考虑使用表的只读视图。
Performing a SELECT statement on the table fetches the messages in the queue, and and doing an INSERT statement on the table sends the message.
在表上执行一条select语句就可以取得队列中的消息，而执行表上的insert语句就可以发送消息。
To get the big picture of what has changed in the new workloads, review table 3, which shows data from the perspective of recipients of mail and the message distribution therein.
表3 进一步描述了新工作负载中发生的变化，其中给出从邮件收件人角度看到的消息分布情况。
Table 3 lists the possible combinations and explains the resulting SOAP message body (the shaded cells represent the cases of the above examples).
表3列举了可能的结合，并解释了相应的消息体(阴影单元代表了上面实例的情况)。
Table 4 includes a few libraries for use in the message-oriented middleware category.
表4包括了用于面向消息中间件类别的一些库。
In the DB2 procedure example in Table 6, the SIGNAL statement is used to generate a user-defined SQLSTATE and a message that is returned to the caller through the SQLCA.
在表6的DB 2过程示例中，signal语句用于生成用户定义的SQLSTATE和一条消息，该消息通过SQLCA返回给调用方。
Table 2 lists the properties of a message stereotype.
表二列出了一个消息原型的属性。
Table 3 lists the properties of a message attachment stereotype.
表三列出了消息附件原型的属性。
The description of the classes contained in the message queue framework reference implementation package is shown in Table 4.
表4显示消息队列框架引用实现包中所包含的类的描述。
This structure includes the name of the destination queue and the reason why the message was put on the dead-letter queue. Table 3 lists the main fields in MQDLH.
该结构包含目标队列的名称和将消息放在死信队列上的原因。
The above message shows that there is a classic replicate, rep1, defined on the table (TAB).
上面的消息表明，在表(tab)上定义了一个普通复制rep1。
This information is used to route the message to its correct destination in the network. Table 2 lists some main fields in MQXQH.
该信息用于传送消息到网络中正确的目的地。
If a match is obtained, the information specified in the Data elements table properties is extracted and used to modify the incoming message.
如果找到了匹配项，将提取Dataelements表属性中指定的信息，并用于修改传入消息。
Whereas SELECT on receive table, deletes the message on the queue as well.
而receive表上的SELECT操作在取走消息的同时，还从队列中删除消息。
If there is more than one login for a user in the sysusers table, you see an output message in the results file and it lists all the logins that have the same username.
如果sysusers表中的某一用户有多个登录，您将在结果文件中看到一则输出消息，它会列出具有相同用户名的所有登录。
For reference purposes in understanding the attached message flow and code, Table 1 below summarises the inbound message data fields and their values.
为了理解本文附带的消息流和代码，表1对进入的消息的数据字段及其值进行了总结。
You'll see a table of {Target, Type, Value} triples that determine what elements in the message get set and to what value.
您将看到一个三元素表 {Target,Type,Value}，该表确定了消息中设置了哪些元素以及这些元素的值。
In the Message Headers table, select the to header and click Modify to put the to header in edit mode.
在MessageHeaders表格中选择Toheader并点击Modify，以将To header置于编辑模式。
The Database Interface Designer will produce a type tree that corresponds to the USER table, and notification message will be displayed.
DatabaseInterfaceDesigner将创建一个对应于user表的类型树并显示通知消息。
To enter the values manually, see Figure 40 for the location of the body of the Web service message in the Initial request parameters table.
要手动输入值，参考图40，查看Initialrequestparameters表中Web服务消息主体的位置。
Depending on the what type of access service provides (RPC vs. Messsaging), its contract is defined either in the form of interface (RPC) or message (Messaging) contract (see Table 1).
根据服务提供的访问类型(RPCvs .消息传递)，它的契约被定义成接口(RPC)或消息(消息传递)契约形式(参见表1)。
应用推荐