This is done as explained in Listing 2.
这是如清单2中所示完成的。
As explained previously, XM does not mix documents and style sheets.
正如前面所解释的那样，XM不会将文档和样式表混在一起。
Backup the database using the backup command as explained previously.
像前面解释的那样，使用backup命令备份数据库。
The discussion in this section is exactly the same as explained above.
本小节的讨论与上面的阐述完全相同。
The connector type to use, RMI or SOAP; RMI is recommended as explained below.
欲使用的连接器类型，RMI或soap；根据下面所阐述的，建议使用rmi。
For events, you can define page-switching cross-page wires, as explained above.
对于事件，正如前面所解释的，您可以定义页面切换跨页面连接。
Check the algorithm as explained in global default values and global maximum values.
检查全局缺省值和全局最大值中说明的算法。
As explained in Part 1, the name of the application is the default palette group name.
正如第1部分所阐述的，这个应用软件的名称就是默认工具板的名称。
As explained earlier, the example XML code from Listing 2 is in human readable format.
正如前面所解释的，清单2中的示例XML代码是一种可读的格式。
The H5N1 virus is also of particular concern for human health, as explained below.
如下所述，H5N1病毒还特别关系到人类健康。
You can "weave" the contracts at load time, as explained in the AspectJ documentation.
可以在装入时 “织入”合约，正如AspectJ文档中所解释的。
Configure the hosts file as explained above according to the use case you wish to test.
根据您希望测试的用例，按照上面的说明配置主机文件。
You might need to temporarily stop automatic synchronization, as explained earlier.
您可能需要暂时地停止自动的同步化，如前面介绍的那样。
I scan the puzzle for words both horizontally and vertically, as explained earlier.
如前所述，我既扫描水平方向上的单词，也扫描垂直方向上的单词。
As explained in Adding a new device, you need to decide which situation fits your needs.
在添加新设备中已说明，您需要决定哪种情况适合您的需求。
As explained earlier, CAI provides a mechanism to store contents in different files.
正如之前所述的，CAI提供一个机制来在不同的文件中存储目录。
Instead, a federation layer is involved, as explained in more detail in the next section.
相反，正如接下来的小节中要详细解释的那样，这里使用一个联邦层。
Statistics are your best source of information, and as explained, information is critical.
统计是你最好的信息来源，前面已经解释过，信息是至关重要的。
They come into the picture again in the final process of rules maintenance as explained next.
在规则维护的最后过程中再次牵涉到规则部署，下面将对此进行说明。
As explained, constraint patterns can be instantiated from this view using each item's context menu.
如说明，在此视图中可以利用每项的环境菜单实例化约束模式。
As explained later in this article, there are other ways that this integration could be enabled.
正如本文稍后所讲，有进行集成的其他方法。
There are five transaction types submitted by the clients in defined proportions as explained above.
按照前面解释的比例，客户机提交5种类型的事务。
As explained in this comic, there's 85.4 trillion cubic feet of methane hydrate buried under Alaska.
正如这本喜剧所表明的那样，在美国阿拉斯加的地下，埋藏有85.4万亿立方英尺的甲烷水合物。
Configure the paths to disk using MSJ as explained under Configuring paths to disks and load balancing.
按照配置磁盘路径和负载均衡中介绍的方法使用MS J配置磁盘路径。
As explained in Section 2.2.1 the TM1 server will connect to the LDAP server to verify the user credentials.
正如2.2.1节中解释的，TM 1服务器将连接LDAP服务器以检查用户凭证。
As explained in the earlier section, you need to turn off caching to get your updated city choices to display.
如同在早先章节中所说明的，您需要关闭缓存以显示更新的城市选择。
As explained earlier, increasingly users think of their data in terms of characters of various national languages.
正如之前解释的那样，越来越多的用户根据不同国家语言的字符来考虑数据。
As explained in the previous section, in this example setup, each DS4500 presents its disks to only two hosts.
如上一节所介绍的，在本例的设置中，每个DS4500只将它的磁盘展示给两个主机。
As explained previously there is a risk of the journal becoming corrupted possibly causing file system corruption.
如上所述，不一致的事务日志有可能导致文件系统的崩溃。
Two disks for the transaction log of the messaging database, again, these two should be striped as explained above.
两个磁盘用于消息传递数据库的事务日志，同样，这两个磁盘应该采用上述带状设置。
应用推荐