[jboss-cvs] JBossAS SVN: r94325 - projects/docs/enterprise/5.0/Getting_Started_Guide/zh-CN.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Sun Oct 4 21:52:38 EDT 2009
Author: xhuang at jboss.com
Date: 2009-10-04 21:52:38 -0400 (Sun, 04 Oct 2009)
New Revision: 94325
Modified:
projects/docs/enterprise/5.0/Getting_Started_Guide/zh-CN/The_JBoss_Server_A_Quick_Tour.po
Log:
update
Modified: projects/docs/enterprise/5.0/Getting_Started_Guide/zh-CN/The_JBoss_Server_A_Quick_Tour.po
===================================================================
--- projects/docs/enterprise/5.0/Getting_Started_Guide/zh-CN/The_JBoss_Server_A_Quick_Tour.po 2009-10-05 01:37:17 UTC (rev 94324)
+++ projects/docs/enterprise/5.0/Getting_Started_Guide/zh-CN/The_JBoss_Server_A_Quick_Tour.po 2009-10-05 01:52:38 UTC (rev 94325)
@@ -1,17 +1,18 @@
+# translation of The_JBoss_Server_A_Quick_Tour.po to
# translation of Start_Stop_Server.po to
# Language /home/remote/xhuang/JBEAP420/JBAS translations for JBEAP package.
-# Copyright (C) 2007, 2008 Free Software Foundation, Inc.
+# Copyright (C) 2007, 2008, 2009 Free Software Foundation, Inc.
#
# Automatically generated, 2007.
-# Xi HUANG <xhuang at redhat.com>, 2007, 2008.
+# Xi HUANG <xhuang at redhat.com>, 2007, 2008, 2009.
msgid ""
msgstr ""
-"Project-Id-Version: Start_Stop_Server\n"
+"Project-Id-Version: The_JBoss_Server_A_Quick_Tour\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-09-14 00:28+0000\n"
-"PO-Revision-Date: 2009-10-04 21:38+1000\n"
+"PO-Revision-Date: 2009-10-05 11:52+1000\n"
"Last-Translator: Xi HUANG <xhuang at redhat.com>\n"
-"Language-Team: <zh at li.org>\n"
+"Language-Team: <en at li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
@@ -25,15 +26,15 @@
#. Tag: title
#: The_JBoss_Server_A_Quick_Tour.xml:33
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Server Structure"
-msgstr "目录结构"
+msgstr "服务器结构"
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:34
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Now that you’ve downloaded JBoss and have run the server for the first time, the next thing you will want to know is how the installation is laid out and what goes where. At first glance there seems to be a lot of stuff in there, and it’s not obvious what you need to look at and what you can safely ignore for the time being. To remedy that, we’ll explore the server directory structure, locations of the key configuration files, log files, deployment and so on. It’s worth familiarizing yourself with the layout at this stage as it will help you understand the JBoss service architecture so that you’ll be able to find your way around when it comes to deploying your own applications."
-msgstr "让我们探讨 JBoss 企业级应用程序平台的目录结构并帮助你理解如何进行安装。熟悉目录的结构以及关键配置文件、日志文件、部署文件等的位置是很有用的。这将帮助你理解 JBoss 服务架构，在部署自己的应用程序时能得心应手。"
+msgstr "现在你已经下载了 JBoss 且第一次运行了服务器，下面要了解的事情是如何进行安装以及文件的不同位置。内容看起来好像很多，你也不清楚哪些是应该了解的而哪些是可以忽略的。为了弥补这一点，我们将探讨 JBoss 企业级应用程序平台的目录结构、关键配置文件的位置、日志文件、部署等。熟悉目录的结构以及关键配置文件、日志文件、部署文件等的位置是很有用的。这将帮助你理解 JBoss 服务架构，在部署自己的应用程序时能得心应手。"
#. Tag: title
#: The_JBoss_Server_A_Quick_Tour.xml:46
@@ -43,9 +44,9 @@
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:47
-#, fuzzy, no-c-format
+#, no-c-format
msgid "When the JBoss Server is running, you can get a live view of the server by going to the JMX console application at <ulink url=\"http://localhost:8080/jmx-console\"></ulink>."
-msgstr "当 JBoss 服务器运行时，你可以通过 <ulink url=\"http://localhost:8080/jmx-console\"></ulink> 访问 JMX 控制台来获得服务器的活动视图。你应该可以看到和 <xref linkend=\"The_JMX_Console-View_of_the_JMX_Management_Console_Web_Application\"/> 类似的页面。"
+msgstr "当 JBoss 服务器运行时，你可以通过 <ulink url=\"http://localhost:8080/jmx-console\"></ulink> 访问 JMX 控制台来获得服务器的活动视图。"
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:50
@@ -97,15 +98,15 @@
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:87
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Hot-deployable services are those which can be added to or removed from the running server. These are placed in the <literal>JBOSS_DIST/jboss-as/server/<instance-name>/deploy</literal> directory. Let’s have a look at a practical example of hot-deployment of services in JBoss."
-msgstr "可热部署的服务是那些可以向运行中的服务器添加和删除的服务。它们位于 <literal>JBOSS_DIST/jboss-as/server/<instance-name>/deploy</literal> 目录。在了解服务器配置细节之前，让我们看看一个 JBoss 热部署的示例。"
+msgstr "可热部署的服务是那些可以向运行中的服务器添加和删除的服务。它们位于 <literal>JBOSS_DIST/jboss-as/server/<instance-name>/deploy</literal> 目录。让我们看一个 JBoss 热部署的示例。 "
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:90
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Start JBoss if it isn’t already running and take a look at the <filename>server/production/deploy</filename> directory. Remove the <filename>mail-service.xml</filename> file and watch the output from the server:"
-msgstr "启动 JBoss 并进入 <literal>server/default/deploy</literal> 目录，删除 <literal>mail-service.xml</literal> 文件并观察服务器的输出："
+msgstr "启动 JBoss 并进入 <literal>server/production/deploy</literal> 目录，删除 <literal>mail-service.xml</literal> 文件并观察服务器的输出："
#. Tag: programlisting
#: The_JBoss_Server_A_Quick_Tour.xml:92
@@ -115,18 +116,18 @@
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:94
-#, fuzzy, no-c-format
+#, no-c-format
msgid ""
"Then replace the file and watch JBoss re-install the service: <programlisting>\n"
"13:58:54,331 INFO [MailService] Mail Service bound to java:/Mail\n"
"</programlisting> This is hot-deployment in action."
-msgstr "然后再将这个文件还原，我们可以看到 JBoss 重新安装了这个服务：<programlisting>13:58:54,331 INFO [MailService] Mail Service bound to java:/Mail</programlisting>。这就是热部署的一个实例。"
+msgstr "然后再将这个文件还原，我们可以看到 JBoss 重新安装了这个服务：<programlisting>13:58:54,331 INFO [MailService] Mail Service bound to java:/Mail</programlisting>。这就是热部署的一个实例。 "
#. Tag: title
#: The_JBoss_Server_A_Quick_Tour.xml:100
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Hot-deployment configurations"
-msgstr "JBoss 里服务的热部署"
+msgstr "热部署的配置"
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:101
@@ -254,9 +255,9 @@
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:139
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Now that we have examined the JBoss server, we will take a look at some of the main configuration files and what they are used for. All paths are relative to the server configuration directory (<filename class=\"directory\">server/default</filename>, for example)."
-msgstr "我们已经检查了 JBoss 服务器，现在让我们看看一些主要的配置文件以及用处。所有的路径都是性对于服务器配置目录的（如，<filename class=\"directory\">server/production</filename>）。"
+msgstr "我们已经查看了 JBoss 服务器，现在让我们看看一些主要的配置文件以及用处。所有的路径都是性对于服务器配置目录的（如，<filename class=\"directory\">server/default</filename>）。"
#. Tag: title
#: The_JBoss_Server_A_Quick_Tour.xml:143
@@ -316,9 +317,9 @@
#. Tag: title
#: The_JBoss_Server_A_Quick_Tour.xml:170
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Bootstrap Configuration"
-msgstr "服务器配置"
+msgstr "Bootstrap 配置"
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:171
@@ -328,15 +329,15 @@
#. Tag: title
#: The_JBoss_Server_A_Quick_Tour.xml:174
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Legacy Core Services"
-msgstr "核心服务"
+msgstr "旧的核心服务"
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:175
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The legacy core services specified in the <filename>conf/jboss-service.xml</filename> file are started just after server starts up the microcontainer. If you have a look at this file in an editor you will see MBeans for various services including logging, security, JNDI, JNDIView etc. Try commenting out the entry for the <literal>JNDIView</literal> service."
-msgstr "服务器启动时，<filename>conf/jboss-service.xml</filename> 文件里指定的核心服务将首先启动。如果你用一个编辑器查看这个文件，你将看到不同服务的 MBean，如日志、安全性、JNDI、JNDIView 等等。注释关于 <literal>JNDIView</literal> 服务的条目。"
+msgstr "服务器启动时，<filename>conf/jboss-service.xml</filename> 文件里指定的旧的核心服务将在微容器启动后启动。如果你用一个编辑器查看这个文件，你将看到不同服务的 MBean，如日志、安全性、JNDI、JNDIView 等等。注释关于 <literal>JNDIView</literal> 服务的条目。"
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:179
@@ -390,25 +391,25 @@
#: The_JBoss_Server_A_Quick_Tour.xml:192
#, no-c-format
msgid "In JBoss <literal>log4j</literal> is used for logging. If you are not familiar with the <literal>log4j</literal> package and would like to use it in your applications, you can read more about it at the Jakarta web site (<ulink url=\"http://jakarta.apache.org/log4j/\"></ulink>)."
-msgstr ""
+msgstr "在 JBoss 里，<literal>log4j</literal> 用于日志。如果你不熟悉 <literal>log4j</literal> 包但希望在应用程序里使用它，你可以在 Jakarta 网站（<ulink url=\"http://jakarta.apache.org/log4j/\"></ulink>）获得更多信息。"
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:195
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Logging is controlled from a central <filename>conf/jboss-log4j.xml</filename> file. This file defines a set of appenders specifying the log files, what categories of messages should go there, the message format and the level of filtering. By default, JBoss produces output to both the console and a log file (<filename>log/server.log</filename>)."
-msgstr "日志是通过 <filename>conf/log4j.xml</filename> 文件进行集中控制的。这个文件定义了一系列的 appender、日志文件、各个类别的信息应该记录的位置、信息格式以及过滤级别。在缺省情况下，JBoss 把输出同时发送到控制台和一个日志文件（<filename class=\"directory\">log</filename> 目录下的 <filename>server.log</filename>）。"
+msgstr "日志是通过 <filename>conf/log4j.xml</filename> 文件进行集中控制的。这个文件定义了一系列的 appender、日志文件、各个类别的信息应该记录的位置、信息格式以及过滤级别。在缺省情况下，JBoss 把输出同时发送到控制台和一个日志文件（<filename>server.log</filename>）。"
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:198
-#, fuzzy, no-c-format
+#, no-c-format
msgid "There are 6 basic log levels used: <literal>TRACE</literal>, <literal>DEBUG</literal>, <literal>INFO</literal>, <literal>WARN</literal>, <literal>ERROR</literal> and <literal>FATAL</literal>. The logging threshold on the console is <literal>INFO</literal>, which means that you will see informational messages, warning messages and error messages on the console but not general debug and trace messages. In contrast, there is no threshold set for the <filename>server.log</filename> file, so all generated logging messages will be logged there."
-msgstr "我们可以使用 5 个日志级别：<literal>DEBUG</literal>、<literal>INFO</literal>、<literal>WARN</literal>、<literal>ERROR</literal> 和 <literal>FATAL</literal>。控制台上的日志级别极限是 <literal>INFO</literal>，这意味着你将看到信息性的消息、警告消息和错误消息，但你看不到通常的调试消息。相反，<filename>server.log</filename> 就没有设置日志极限，所以所有产生的日志消息都会在此记录。"
+msgstr "我们可以使用 6 个日志级别：<literal>TRACE</literal>、<literal>DEBUG</literal>、<literal>INFO</literal>、<literal>WARN</literal>、<literal>ERROR</literal> 和 <literal>FATAL</literal>。控制台上的日志级别极限是 <literal>INFO</literal>，这意味着你将看到信息性的消息、警告消息和错误消息，但你看不到通常的调试消息。相反，<filename>server.log</filename> 就没有设置日志极限，所以所有产生的日志消息都会在此记录。"
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:201
-#, fuzzy, no-c-format
+#, no-c-format
msgid "If things are going wrong and there doesn’t seem to be any useful information in the console, always check the <filename>server.log</filename> file to see if there are any debug messages which might help you to track down the problem. However, be aware that just because the logging threshold allows debug messages to be displayed, that doesn't mean that all of JBoss will produce detailed debug information for the log file. You will also have to boost the logging limits set for individual categories. Take the following category for example."
-msgstr "如果出现了问题但控制台上却看不到任何有用的信息，请记得查看 <filename>server.log</filename> 文件里的调试信息，这可以帮助你追踪问题。然而，正是因为设置的日志极限允许调试信息的显示，这意味着所有的 JBoss 服务都将在这个日志文件里输出详细调试信息。你不得不为单独的类别设定日志限制。我们以下面的类别为例。"
+msgstr "如果出现了问题但控制台上却看不到任何有用的信息，请记得查看 <filename>server.log</filename> 文件里的调试信息，这可以帮助你追踪问题。然而，正是因为设置的日志极限允许调试信息的显示，这意味着所有的 JBoss 服务都将在这个日志文件里输出详细调试信息。你不得不为单独的类别设定日志限制。我们以下面的类别为例。 "
#. Tag: programlisting
#: The_JBoss_Server_A_Quick_Tour.xml:204
@@ -428,7 +429,7 @@
#: The_JBoss_Server_A_Quick_Tour.xml:205
#, no-c-format
msgid "This limits the level of logging to <literal>INFO</literal> for all JBoss classes, apart from those which have more specific overrides provided. By default the root logger in the <filename>jboss-log4j.xml</filename> is set to <literal>INFO</literal>. This effectively means that any <literal>TRACE</literal> or <literal>DEBUG</literal> logger from any logger categories will not be logged in any files or the console appender. This setting is controlled through the <property>jboss.server.log.threshold</property> property. By default this is <literal>INFO</literal>. If you were to change this to <literal>DEBUG</literal>, it would produce much more detailed logging output. In order to change this there are two options:"
-msgstr ""
+msgstr "除了那些定义了更详细的覆盖的 JBoss 类，这把所有类的日志级别限制为 <literal>INFO</literal>。在缺省情况下，<filename>jboss-log4j.xml</filename> 里的 root logger 被设置为 <literal>INFO</literal>。这表示任何 logger 类别里的 <literal>TRACE</literal> 或 <literal>DEBUG</literal> 都不会登记在任何文件或控制台 appender 里。这个设置通过 <property>jboss.server.log.threshold</property> 属性进行控制。它缺省为 <literal>INFO</literal>。如果你想把它修改为 <literal>DEBUG</literal>，它将产生详细得多的日志输出。有两个方法可以修改它："
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:210
@@ -472,13 +473,13 @@
#: The_JBoss_Server_A_Quick_Tour.xml:221
#, no-c-format
msgid "The <filename>JBOSS_DIST/jboss-as/server/<instance-name>/conf/jboss-log4j.xml</filename> is scanned every 60 seconds (by default) to check for any changes. Changing this file does not require a server restart as the changes will be hot deployed within the next 60 seconds following the change."
-msgstr ""
+msgstr "每隔 60 秒（缺省）就可以扫描 <filename>JBOSS_DIST/jboss-as/server/<instance-name>/conf/jboss-log4j.xml</filename> 里的任何改动。修改这个文件不要求服务器重启，这是因为改动会在 60 秒之内被热部署。"
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:227
-#, fuzzy, no-c-format
+#, no-c-format
msgid "As another example, let’s say you wanted to set the output from the container-managed persistence engine to <literal>DEBUG</literal> level and to redirect it to a separate file, <filename>cmp.log</filename>, in order to analyze the generated SQL commands. You would add the following code to the <filename>conf/jboss-log4j.xml</filename> file:"
-msgstr "作为另外一个例子：假设为了分析所产生的 SQL 命令，你想把容器管理的持久化引擎的输出设置为 <literal>DEBUG</literal> 级别并重定向到一个单独的文件 <literal>cmp.log</literal>。你需要把下列的代码添加到 <filename>log4j.xml</filename> 文件里："
+msgstr "作为另外一个例子：假设你想把容器管理的持久化引擎的输出设置为 <literal>DEBUG</literal> 级别并重定向到一个单独的文件 <literal>cmp.log</literal>。为了分析所产生的 SQL 命令，你需要把下列的代码添加到 <filename>conf/jboss-log4j.xml</filename> 文件里："
#. Tag: programlisting
#: The_JBoss_Server_A_Quick_Tour.xml:230
@@ -526,7 +527,7 @@
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:234
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The file appender is set up to produce a new log file every day rather than producing a new one every time you restart the server or writing to a single file indefinitely. The current log file is <filename>cmp.log</filename>. Older files have the date they were written added to their filenames. Please note that the <filename class=\"directory\">log</filename> directory also contains HTTP request logs which are produced by the web container."
msgstr "这个文件 appender 被设置为每天产生一个新的日志文件，而不是每次重启服务器时产生或者一直写入到单一的文件里。当前的日志文件是 <filename>cmp.log</filename>，而旧的文件名里含有写入的日期。你将注意到 <filename class=\"directory\">log</filename> 目录也包含 web 容器产生的 HTTP 请求日志。"
@@ -534,7 +535,7 @@
#: The_JBoss_Server_A_Quick_Tour.xml:237
#, no-c-format
msgid "By default the <filename>server.log</filename> appender is configured to retain log messages between server restarts. This is controlled by the <property>Append</property> property on the <literal>FILE</literal> appender which corresponds to the <filename>server.log</filename> file. By default this property is set to true; if you want the <filename>server.log</filename> contents to be wiped out on server restarts then you can edit the <filename>JBOSS_DIST/jboss-as/server/<instance-name>conf/jboss-log4j.xml</filename> file to set this property value to false. For example:"
-msgstr ""
+msgstr "在缺省情况下，<filename>server.log</filename> appender 被配置为在服务器重启时获取日志消息。这是由 <literal>FILE</literal> appender 上的 <property>Append</property> 属性控制的，它对应 <filename>server.log</filename> 文件。这个属性缺省为 true，如果你想在服务器重启时清除 <filename>server.log</filename> 的内容，你需要编辑 <filename>JBOSS_DIST/jboss-as/server/<instance-name>conf/jboss-log4j.xml</filename> 文件把这个属性设置为 false。例如："
#. Tag: programlisting
#: The_JBoss_Server_A_Quick_Tour.xml:240
@@ -546,6 +547,11 @@
" <param name=\"Append\" value=\"false\"/>\n"
" ..."
msgstr ""
+"<appender name=\"FILE\" class=\"org.jboss.logging.appender.DailyRollingFileAppender\">\n"
+" <errorHandler class=\"org.jboss.logging.util.OnlyOnceErrorHandler\"/>\n"
+" <param name=\"File\" value=\"${jboss.server.log.dir}/server.log\"/>\n"
+" <param name=\"Append\" value=\"false\"/>\n"
+" ..."
#. Tag: title
#: The_JBoss_Server_A_Quick_Tour.xml:244
@@ -555,15 +561,15 @@
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:245
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The security domain information is stored in the file <filename>conf/login-config.xml</filename> as a list of named security domains, each of which specifies a number of JAAS <footnote><para> The Java Authentication and Authorization Service. JBoss uses JAAS to provide pluggable authentication modules. You can use the ones that are provided or write your own if you have more specific requirements. </para> </footnote> login modules which are used for authentication purposes in that domain. When you want to use security in an application, you specify the name of the domain you want to use in the application’s JBoss-specific deployment descriptors, <filename>jboss.xml</filename> (used in defining jboss specific configurations for an application) and/or <filename>jboss-web.xml</filename> (used in defining jboss for a Web application. We'll quickly look at how to do this to secure the JMX Console application which ships with JBoss."
-msgstr "安全域信息作为命名的安全域列表存放在 <filename>login-config.xml</filename> 文件里，每个指定了许多 JAAS <footnote><para> Java 验证和授权服务。 JBoss 使用 JAAS 来提供可插拔的验证模块。你可以使用这些或是根据自己的特定需要编写自己的模块。</para> </footnote> 和在该域里用于验证目的的登录模块。当你希望在应用程序里使用安全性时，你可以在该程序的和 JBoss 相关的部署描述符 <filename>jboss.xml</filename> 和/或 <filename>jboss-web.xml</filename> 里指定域的名字。我们将快速浏览一下如何用这个办法来设置 JMX 控制台应用程序的安全性。"
+msgstr "安全域信息作为命名的安全域列表存放在 <filename>login-config.xml</filename> 文件里，每个指定了许多 JAAS <footnote><para> Java 验证和授权服务。 JBoss 使用 JAAS 来提供可插拔的验证模块。你可以使用这些或是根据自己的特定需要编写自己的模块。</para> </footnote> 和在该域里用于验证目的的登录模块。当你希望在应用程序里使用安全性时，你可以在该程序的和 JBoss 相关的部署描述符 <filename>jboss.xml</filename>（为应用程序定义 JBoss 专有的配置）和/或 <filename>jboss-web.xml</filename>（为 Web 应用程序定义 JBoss 专有的配置）里指定域的名字。我们将快速浏览一下如何用这个办法来设置 JMX 控制台应用程序的安全性。"
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:251
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Almost every aspect of the JBoss server can be controlled through the JMX Console, so it is important to make sure that, at the very least, the application is password protected. Otherwise, any remote user could completely control your server. To protect it, we will add a security domain to cover the application. This can be done in the <filename>jboss-web.xml</filename> file for the JMX Console, which can be found in <filename class=\"directory\">deploy/jmx-console.war/WEB-INF/</filename> directory. Uncomment the <literal>security-domain</literal> in that file, as shown below."
-msgstr "在《安装指南》里我们提及了 JMX 控制台。JBoss 服务器差不多每一个方面都可以通过 JMX 控制台来控制，所以你至少要确保它是有密码保护的。否则，任何远程用户都可以完全地控制你的服务器。为了保护它，我们将添加一个安全域。<footnote><para>如果你的 JBoss 是用图形化安装程序安装的并设置了 JMX 安全性，你将不需要取消这些部分的注释，因为它们已经是没有注释的。此外，admin 的密码将设置为任何你指定的密码。</para> </footnote> 这可以通过 <filename class=\"directory\">deploy/jmx-console.war/WEB-INF/</filename> 目录里 JMX 控制台的 <filename>jboss-web.xml</filename> 文件里进行设置。如下所示，取消 <literal>security-domain</literal> 部分的注释。"
+msgstr "JBoss 服务器差不多每一个方面都可以通过 JMX 控制台来控制，所以你至少要确保它是有密码保护的。否则，任何远程用户都可以完全地控制你的服务器。为了保护它，我们将添加一个安全域。<这可以通过 <filename class=\"directory\">deploy/jmx-console.war/WEB-INF/</filename> 目录里 JMX 控制台的 <filename>jboss-web.xml</filename> 文件里进行设置。如下所示，取消 <literal>security-domain</literal> 部分的注释。"
#. Tag: programlisting
#: The_JBoss_Server_A_Quick_Tour.xml:261
@@ -633,9 +639,9 @@
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:267
-#, fuzzy, no-c-format
+#, no-c-format
msgid "That's great, but where do the user names and passwords come from? They come from the <literal>jmx-console</literal> security domain we linked the application to. We have provided the configuration for this in the <filename>conf/login-config.xml</filename>."
-msgstr "这很不错，但用户名和密码从哪而来呢？它们来自应用程序链接到的 <literal>jmx-console</literal> 安全域。我们已经在 <filename>conf/login-config.xml</filename> 里提供了相应的配置。"
+msgstr "这很不错，但用户名和密码从哪而来呢？它们来自应用程序链接到的 <literal>jmx-console</literal> 安全域。我们已经在 <filename>conf/login-config.xml</filename> 里提供了相应的配置。 "
#. Tag: programlisting
#: The_JBoss_Server_A_Quick_Tour.xml:271
@@ -671,9 +677,9 @@
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:273
-#, fuzzy, no-c-format
+#, no-c-format
msgid "This configuration uses a simple file based security policy. The configuration files are found in the <filename class=\"directory\">conf/props</filename> directory of your server configuration. The usernames and passwords are stored in the <literal>conf/props/jmx-console-users.properties</literal> file and take the form \"<literal>username=password</literal>\". To assign a user to the <literal>JBossAdmin</literal> group add \"<literal>username=JBossAdmin</literal>\" to the <literal>jmx-console-roles.properties</literal> file (additional roles on that username can be added comma separated). The existing file creates an <literal>admin</literal> user with the password <literal>admin</literal>. For security, please either remove the user or change the password to a stronger one."
-msgstr "这个配置使用了一个简单的基于文件的安全策略。配置文件可以在你的服务器配置的 <filename class=\"directory\">conf/props</filename> 目录里找到。用户名和密码存放在 <literal>jmx-console-users.properties</literal> 文件里，格式为 \"<literal>username=password</literal>\"。要分配一个用户给 <literal>JBossAdmin</literal> 组，可以在 <literal>jmx-console-roles.properties</literal> 文件里添加 \"<literal>username=JBossAdmin</literal>\"。现有的文件会创建一个密码为 <literal>admin</literal> 的用户 <literal>admin</literal>。基于安全考虑，请删除这个用户或是设置更复杂的密码。"
+msgstr "这个配置使用了一个简单的基于文件的安全策略。配置文件可以在你的服务器配置的 <filename class=\"directory\">conf/props</filename> 目录里找到。用户名和密码存放在 <literal>conf/props/jmx-console-users.properties</literal> 文件里，格式为 \"<literal>username=password</literal>\"。要分配一个用户给 <literal>JBossAdmin</literal> 组，可以在 <literal>jmx-console-roles.properties</literal> 文件里添加 \"<literal>username=JBossAdmin</literal>\"。现有的文件会创建一个密码为 <literal>admin</literal> 的用户 <literal>admin</literal>。基于安全考虑，请删除这个用户或是设置更复杂的密码。"
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:276
@@ -683,15 +689,15 @@
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:277
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Since the username and password are session variables in the web browser you may need to restart your browser to use the login dialog window."
-msgstr "既然用户名和密码是 web 浏览器里的会话变量，你可能需要关闭浏览器并重新打开才可以看到登录对话框。"
+msgstr "既然用户名和密码是 web 浏览器里的会话变量，你可能需要关闭浏览器并重新打开才可以看到登录对话框。 "
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:282
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The JMX Console isn't the only web based management interface to JBoss. There is also the Web Console. Although it's a Java applet, the corresponding web application can be secured in the same way as the JMX Console. The Web Console is in the file <filename>deploy/management/console-mgr.sar/web-console.war.</filename>. The only difference is that the Web Console is provided as a simple WAR file instead of using the exploded directory structure that the JMX Console did. The only real difference between the two is that editing the files inside the WAR file is a bit more cumbersome."
-msgstr "JMX 控制台不是 JBoss 唯一的基于 web 的管理界面。Web 控制台也是其中之一。虽然它是一个 Java applet，对应的 web 应用程序也可以用和 JMX 控制台相同的方法进行安全设定。Web 控制台对于的应用程序是 <filename>deploy/management/web-console.war</filename>。唯一的区别是，Web 控制台是用简单的 WAR 文件形式来提供的，而不是使用 JMX 控制台所采用的展开的目录结构。而真正的区别是编辑 WAR 文件里的文件会更为麻烦。"
+msgstr "JMX 控制台不是 JBoss 唯一的基于 web 的管理界面。Web 控制台也是其中之一。虽然它是一个 Java applet，对应的 web 应用程序也可以用和 JMX 控制台相同的方法进行安全设定。Web 控制台对于的应用程序是 <filename>deploy/management/console-mgr.sar/web-console.war</filename>。唯一的区别是，Web 控制台是用简单的 WAR 文件形式来提供的，而不是使用 JMX 控制台所采用的展开的目录结构。而真正的区别是编辑 WAR 文件里的文件会更为麻烦。"
#. Tag: title
#: The_JBoss_Server_A_Quick_Tour.xml:288
@@ -701,57 +707,60 @@
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:289
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The non-core, hot-deployable services are added to the <filename class=\"directory\">deploy</filename> directory. They can be either XML descriptor files, <filename>*-service.xml, *-jboss-beans.xml</filename>, MC <filename>.beans</filename> archive, or JBoss Service Archive (SAR) files. SARs contains an <filename>META-INF/jboss-service.xml</filename> descriptor and additional resources the service requires (for example, classes, library JAR files or other archives), all packaged up into a single archive. Similarly, a <filename>.beans</filename> archive contains a <filename>META-INF/jboss-beans.xml</filename> and additional resources."
-msgstr "非核心的、可热部署的服务也被添加到 <filename class=\"directory\">deploy</filename> 目录里。它们可以是 XML 描述符文件 <filename>*-service.xml</filename>，或是 JBoss 服务归档文件（Service Archive, SAR）。SAR包含 XML 描述符文件和该服务需要的其他资源（如类、库 JAR 文件或其他归档文件），所有东西都打包至单一归档文件。"
+msgstr "非核心的、可热部署的服务也被添加到 <filename class=\"directory\">deploy</filename> 目录里。它们可以是 XML 描述符文件 <filename>*-service.xml</filename>，或是 JBoss 服务归档文件（Service Archive, SAR）。SAR包含 XML 描述符文件和该服务需要的其他资源（如类、库 JAR 文件或其他归档文件），所有东西都打包至单一归档文件。类似地，<filename>.beans</filename> 归档包含一个 <filename>META-INF/jboss-beans.xml</filename> 以及其他的资源。"
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:292
-#, fuzzy, no-c-format
+#, no-c-format
msgid "Detailed information on all these services can be found in the <emphasis>JBoss Enterprise Application Platform: Aministration and Configuration Guide</emphasis>, which also provides comprehensive information on server internals and the implementation of services such as JTA and the J2EE Connector Architecture (JCA)."
-msgstr "这些服务的详细信息可以在<emphasis>《JBoss 企业版应用程序平台：服务器配置指南》</emphasis>里找到，这本书也提供服务器内部以及服务的实施如 JTA 和 J2EE Connector Architecture（JCA）等方面的综合信息。"
+msgstr "这些服务的详细信息可以在<emphasis>《JBoss 企业版应用程序平台：管理和配置指南》</emphasis>里找到，这本书也提供服务器内部以及服务的实施如 JTA 和 J2EE Connector Architecture（JCA）等方面的综合信息。"
#. Tag: title
#: The_JBoss_Server_A_Quick_Tour.xml:299
#, no-c-format
msgid "The Service Binding Manager"
-msgstr ""
+msgstr "Service Binding Manager"
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:300
#, no-c-format
msgid "JBoss server uses various ports for the services that it provides (for example, port 8080 for HTTP, 1099 for JNDI). The Service Binding Manager (SBM) service provides a centralized location where settings for all services that need to bind to ports can be configured. SBM can be used to configure different sets of port bindings for a server instance. A system property on the SBM controls which named set (for example, ports-default, ports-01) is used by a particular server instance. If you want to run multiple server instances on the same system then you can configure the SBM on each instance to use a different named binding set. You can even use SBM to switch to a different binding set (for example, 8180 port for HTTP instead of the default 8080) for a server instance."
-msgstr ""
+msgstr "JBoss 服务器对于它提供的服务使用不同的端口（如：用于 HTTP 的 8080 ，JNDI 的 1099）。服务绑定管理者（SBM）服务提供一个中心位置让所有需要绑定端口的服务进行配置。SBM 可以用于配置服务器实例的不同端口绑定集。SBM 的一个系统属性控制特殊的服务器实例使用哪个命名集合（如 ports-default、ports-01）。如果你想在同一机器上运行多个服务器实例，你可以在每个实例上配置 SBM 以使用不同的命名绑定集合。你甚至可以对于服务器实例使用 SBM 来切换到不同的绑定集（如用于 HTTP 的 8080 ，JNDI 的 1099）。"
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:303
#, no-c-format
msgid "In a typical configuration, the <literal>ports-default</literal> set uses the standard ports (for example, JNDI on port 1099), with <literal>ports-01</literal> increasing each port value by 100 (for example, JNDI on 1199), <literal>ports-02</literal> by 200 and so on."
-msgstr ""
+msgstr "在典型的配置里，<literal>ports-default</literal> 集使用标准端口（如端口 1099 上的 JNDI），<literal>ports-01</literal> 对每个端口值增加 100（如 1199 上的 JNDI），而 <literal>ports-02</literal> 则增加 200 等。 "
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:306
#, no-c-format
msgid "SBM is configured through the <filename>$JBOSS_DIST/jboss-as/server/bindingservice.beans/META-INF/bindings-jboss-beans.xml</filename> file. The configuration of the <classname>ServiceBindingManager</classname> involves three primary elements :"
-msgstr ""
+msgstr "SBM 是通过 <filename>$JBOSS_DIST/jboss-as/server/bindingservice.beans/META-INF/bindings-jboss-beans.xml</filename> 文件进行配置的。<classname>ServiceBindingManager</classname> 的配置包括三个主要的元素："
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:311
#, no-c-format
msgid "A set of beans containing standard (default) binding configuration data. These are the base values (for example, JNDI on 1099) used to drive <literal>ports-default</literal>, <literal>ports-01</literal> and so on."
-msgstr ""
+msgstr "一系列包含标准（缺省）绑定配置数据的 bean。它们是用于驱动 <literal>ports-default</literal>、<literal>ports-01</literal> 的基本值（如 1099 上的 JNDI）。"
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:316
#, no-c-format
msgid "A number of beans defining <classname>ServiceBindingSets</classname>, for example, <literal>ports-default</literal>, <literal>ports-01</literal>, <literal>ports-02</literal>. The sets of standard bindings are combined with each of these, along with an offset value (for example, 100 for <literal>ports-01</literal>) that should be applied to the standard port values to create the binding values for that set."
-msgstr ""
+msgstr "许多定义了 <classname>ServiceBindingSets</classname> 的 bean，如 <literal>ports-default</literal>、<literal>ports-01</literal>、 <literal>ports-02</literal>。标准绑定的集合彼此进行组合，加上应用到标准端口值上 offset 值（如对 <literal>ports-01</literal> 使用 100）以创建用于该集合的绑定值。"
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:321
#, no-c-format
msgid "The <classname>ServiceBindingManager</classname> service bean itself. This has the standard bindings and the <classname>ServiceBindingSets</classname> injected into it. It is also configured with the name of the binding set the particular server instance should use. The name of the binding set to be used is configurable from the command line by using the system property <property>jboss.service.binding.set</property>. The default value is <literal>ports-default</literal>."
msgstr ""
+"<classname>ServiceBindingManager</classname> 服务 bean 自身。这具有标准绑定且注入 <classname>ServiceBindingSets</classname>。 "
+"它也配置有特殊服务器实例应该使用的绑定集的名称。所使用的绑定集的名称是可从命令行用系统属性 <property>jboss.service.binding.set</property> 进行配置的。"
+"它的缺省值是 <literal>ports-default</literal>。"
#. Tag: programlisting
#: The_JBoss_Server_A_Quick_Tour.xml:324
@@ -765,22 +774,29 @@
" </parameter>\n"
" ..."
msgstr ""
+"<bean name=\"ServiceBindingManagementObject\" class=\"org.jboss.services.binding.managed.ServiceBindingManagementObject\">\n"
+" <constructor>\n"
+" <!-- The name of the set of bindings to use for this server -->\n"
+" <parameter>\n"
+" ${jboss.service.binding.set:ports-default}\n"
+" </parameter>\n"
+" ..."
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:325
#, no-c-format
msgid "To switch to a different set of ports than the ones used by default, you can start the server by passing the <property>-Djboss.service.binding.set</property> property to the run command as follows:"
-msgstr ""
+msgstr "要切换至不同的端口集，你可以把 <property>-Djboss.service.binding.set</property> 参数传递到 run 命令来启动服务器："
#. Tag: programlisting
#: The_JBoss_Server_A_Quick_Tour.xml:328
#, no-c-format
msgid "./run.sh -Djboss.service.binding.set=ports-01"
-msgstr ""
+msgstr "./run.sh -Djboss.service.binding.set=ports-01"
#. Tag: para
#: The_JBoss_Server_A_Quick_Tour.xml:329
#, no-c-format
msgid "This will instruct the server to use the group of ports configured in the <literal>ports-01</literal> binding set."
-msgstr ""
+msgstr "这将引导服务器使用 <literal>ports-01</literal> 绑定集里的端口组。"
More information about the jboss-cvs-commits
mailing list