[jboss-cvs] JBossAS SVN: r89639 - projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon Jun 1 23:56:26 EDT 2009
Author: ldelima at redhat.com
Date: 2009-06-01 23:56:25 -0400 (Mon, 01 Jun 2009)
New Revision: 89639
Modified:
projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/J2EE_Additional_Services.po
Log:
translation ongoing
Modified: projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/J2EE_Additional_Services.po
===================================================================
--- projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/J2EE_Additional_Services.po 2009-06-02 03:21:01 UTC (rev 89638)
+++ projects/docs/enterprise/4.3.3/Server_Configuration_Guide/pt-BR/J2EE_Additional_Services.po 2009-06-02 03:56:25 UTC (rev 89639)
@@ -9,7 +9,7 @@
"Project-Id-Version: J2EE_Additional_Services\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2009-01-20 02:37+0000\n"
-"PO-Revision-Date: 2009-06-01 16:58+1000\n"
+"PO-Revision-Date: 2009-06-02 13:56+1000\n"
"Last-Translator: Leticia de Lima <ldelima at redhat.com>\n"
"Language-Team: Brazilian Portuguese <en at li.org>\n"
"MIME-Version: 1.0\n"
@@ -271,6 +271,15 @@
"literal> file when running with the <literal>default</literal> configuration "
"file set."
msgstr ""
+"<emphasis role=\"bold\">URLList</emphasis>: a comma separated list of URL "
+"strings from which to load properties file formatted content. If a component "
+"in the list is a relative path rather than a URL it will be treated as a "
+"file path relative to the <literal><jboss-dist>/server/<config></"
+"literal> directory. For example, a component of <literal>conf/local."
+"properties</literal> would be treated as a file URL that points to the "
+"<literal><jboss-dist>/server/production/conf/local.properties</"
+"literal> file when running with the <literal>default</literal> configuration "
+"file set."
#. Tag: para
#: J2EE_Additional_Services.xml:126
@@ -435,6 +444,15 @@
"<literal>conf/jboss-service.xml</literal>. The set of configurable "
"attributes it supports include:"
msgstr ""
+"With all of the independently deployed services available in JBoss, running "
+"multiple instances on a given machine can be a tedious exercise in "
+"configuration file editing to resolve port conflicts. The binding service "
+"allows you centrally configure the ports for multiple JBoss instances. After "
+"the service is normally loaded by JBoss, the <literal>ServiceConfigurator</"
+"literal> queries the service binding manager to apply any overrides that may "
+"exist for the service. The service binding manager is configured in "
+"<literal>conf/jboss-service.xml</literal>. The set of configurable "
+"attributes it supports include:"
#. Tag: para
#: J2EE_Additional_Services.xml:167
@@ -443,7 +461,7 @@
"<emphasis role=\"bold\">ServerName</emphasis>: This is the name of the "
"server configuration this JBoss instance is associated with. The binding "
"manager will apply the overrides defined for the named configuration."
-msgstr ""
+msgstr "<emphasis role=\"bold\">ServerName</emphasis>: Este é o nome da configuração do servidor que esta instância do JBoss é associada. O gerenciador binding aplicará as substituições definidas para a configuração nomeada. "
#. Tag: para
#: J2EE_Additional_Services.xml:172
@@ -456,6 +474,8 @@
"literal>. The factory provides a <literal>ServicesStore</literal> instance "
"responsible for providing the names configuration sets."
msgstr ""
+"<emphasis role=\"bold\">StoreFactoryClassName</emphasis>: Este é o nome da classe que implementa a interface <literal>ServicesStoreFactory</literal>. Você poderá fornecer a sua implementação ou usar o armazenamento padrão XML baseado <literal>org.jboss.services.binding.XMLServicesStoreFactory</"
+"literal>. A criação fornece uma instância <literal>ServicesStore</literal> responsável pelo fornecimento dos conjuntos da configuração de nomes. "
#. Tag: para
#: J2EE_Additional_Services.xml:177
@@ -624,7 +644,7 @@
"The <literal>AttributeMappingDelegate</literal> class is an implementation "
"of the <literal>ServicesConfigDelegate</literal> that expects a "
"<literal>delegate-config</literal> element of the form:"
-msgstr "A classe <literal>AttributeMappingDelegate</literal> é uma implementação dos <literal>ServicesConfigDelegate</literal> que espera um elemento<literal>delegate-config</literal> de forma:"
+msgstr "A classe <literal>AttributeMappingDelegate</literal> é uma implementação dos <literal>ServicesConfigDelegate</literal> que espera um elemento <literal>delegate-config</literal> de forma:"
#. Tag: programlisting
#: J2EE_Additional_Services.xml:235
@@ -1268,7 +1288,7 @@
"the thread context class loader. Note that allowing this is generally a "
"security risk as it allows access to server configuration files which may "
"contain security settings."
-msgstr ""
+msgstr "<emphasis role=\"bold\">DownloadResources</emphasis>: Um aviso indicando se que o servidor deve tentar baixar os recurso do arquivo sem-classe usando o carregador da classe do contexto de segmentação. Perceba que a permissão disto é geralmente um risco de segurança uma vez que isto permite acesso aos arquivos de configuração do servidor que possa conter as configurações de segurança."
#. Tag: para
#: J2EE_Additional_Services.xml:335
@@ -1477,6 +1497,9 @@
"literal> and classes with a constructor that accepts a <literal>String</"
"literal> as its sole argument are supported."
msgstr ""
+"<emphasis role=\"bold\">SchedulableArgumentTypes</emphasis>: Um vírgula separada da lista dos tipos de argumento para o construtor da classe de implementação. Isto será usado para encontrar o construtor correto através da reflexão. Apenas tipos de dados primitivos, <literal>String</"
+"literal> e classes com um construtor que aceita um <literal>String</"
+"literal> assim como o próprio argumento são suportados. "
#. Tag: para
#: J2EE_Additional_Services.xml:412
@@ -1489,6 +1512,8 @@
"<literal>SchedulableMBean</literal> the <literal>SchedulableMBeanMethod</"
"literal> must also be specified."
msgstr ""
+"<emphasis role=\"bold\">SchedulableMBean</emphasis>: Especifica o nome JMX <literal>ObjectName</literal> inteiramente qualificado do MBean esquematizado a ser chamado. Caso o MBean não esteja disponível, ele não será chamado, mas as repetições restantes serão decrementada. Quando usando <literal>SchedulableMBean</literal> o <literal>SchedulableMBeanMethod</"
+"literal> deve também ser especificado."
#. Tag: para
#: J2EE_Additional_Services.xml:417
@@ -1498,7 +1523,7 @@
"operation name to be called on the schedulable MBean. It can optionally be "
"followed by an opening bracket, a comma separated list of parameter "
"keywords, and a closing bracket. The supported parameter keywords include:"
-msgstr ""
+msgstr "<emphasis role=\"bold\">SchedulableMBeanMethod</emphasis>: Especifica o nome da operação a ser chamadp no MBean esquematizado. Isto pode opcionalmente ser sguido pelo colchete de abertura, uma lista de vírgula separada das palavras-chaves de parâmetro e um colchete de fechamento. As palavras chaves do parâmetro suportadas incluem:"
#. Tag: para
#: J2EE_Additional_Services.xml:422
@@ -1506,7 +1531,7 @@
msgid ""
"<literal>NOTIFICATION</literal> which will be replaced by the timers "
"notification instance (javax.management.Notification)"
-msgstr ""
+msgstr "<literal>NOTIFICATION</literal> que serão substituídas pela instância da notificação dos cronômetros (javax.management.Notification)"
#. Tag: para
#: J2EE_Additional_Services.xml:427
@@ -1514,7 +1539,7 @@
msgid ""
"<literal>DATE</literal> which will be replaced by the date of the "
"notification call (java.util.Date)"
-msgstr ""
+msgstr "<literal>DATE</literal> que será substituído pela data da chamada da notificação (java.util.Date)"
#. Tag: para
#: J2EE_Additional_Services.xml:432
@@ -1522,7 +1547,7 @@
msgid ""
"<literal>REPETITIONS</literal> which will be replaced by the number of "
"remaining repetitions (long)"
-msgstr ""
+msgstr "<literal>REPETITIONS</literal> pelos quais serão substituídos pelo número das repetições restantes (longo)"
#. Tag: para
#: J2EE_Additional_Services.xml:437
@@ -1530,7 +1555,7 @@
msgid ""
"<literal>SCHEDULER_NAME</literal> which will be replaced by the "
"<literal>ObjectName</literal> of the <literal>Scheduler</literal>"
-msgstr ""
+msgstr "<literal>SCHEDULER_NAME</literal> pelo qual será substituído pelo <literal>ObjectName</literal> do <literal>Scheduler</literal>"
#. Tag: para
#: J2EE_Additional_Services.xml:442
@@ -1538,7 +1563,7 @@
msgid ""
"Any fully qualified class name which the <literal>Scheduler</literal> will "
"set to null."
-msgstr ""
+msgstr "Qualquer nome da classe inteiramente qualificada pelo qual o <literal>Scheduler</literScheduleral> configurará para nulo."
#. Tag: para
#: J2EE_Additional_Services.xml:449
@@ -1550,7 +1575,7 @@
"<literal>ObjectName</literal>. The following is an example of configuring a "
"<literal>Scheduler</literal> to call a <literal>Schedulable</literal> "
"implementation as well as a configuration for calling a MBean."
-msgstr ""
+msgstr " "
#. Tag: programlisting
#: J2EE_Additional_Services.xml:452
@@ -1601,6 +1626,8 @@
"The <literal>SchedulableClass</literal><literal>org.jboss.book.misc.ex2."
"ExSchedulable</literal> example class is given below."
msgstr ""
+"The <literal>SchedulableClass</literal><literal>org.jboss.book.misc.ex2."
+"ExSchedulable</literal> example class is given below."
#. Tag: programlisting
#: J2EE_Additional_Services.xml:456
@@ -1680,7 +1707,7 @@
#: J2EE_Additional_Services.xml:457
#, no-c-format
msgid "Deploy the timer SAR by running:"
-msgstr ""
+msgstr "Deploy the timer SAR by running:"
#. Tag: programlisting
#: J2EE_Additional_Services.xml:460
@@ -1695,6 +1722,8 @@
"The server console shows the following which includes the first two timer "
"invocations, separated by 60 seconds:"
msgstr ""
+"The server console shows the following which includes the first two timer "
+"invocations, separated by 60 seconds:"
#. Tag: programlisting
#: J2EE_Additional_Services.xml:464
@@ -1724,9 +1753,9 @@
#. Tag: title
#: J2EE_Additional_Services.xml:470
-#, fuzzy, no-c-format
+#, no-c-format
msgid "The Timer Service"
-msgstr "O Serviço Tomcat"
+msgstr "O Serviço Cronômetro"
#. Tag: para
#: J2EE_Additional_Services.xml:471
@@ -1736,6 +1765,9 @@
"Timer</literal>) which can send notifications at predetermined times. The a "
"timer MBean can be instantiated within JBoss as any other MBean."
msgstr ""
+"The JMX standard defines a timer MBean (<literal>javax.management.timer."
+"Timer</literal>) which can send notifications at predetermined times. The a "
+"timer MBean can be instantiated within JBoss as any other MBean."
#. Tag: programlisting
#: J2EE_Additional_Services.xml:474
@@ -1758,6 +1790,12 @@
"them into JMX notifications more suitable for other services. The "
"<literal>TimerService</literal> MBean takes the following attributes:"
msgstr ""
+"A standard JMX timer doesn't produce any timer events unless it is asked "
+"to. To aid in the configuration of the timer MBean, JBoss provides a "
+"complementary <literal>TimerService</literal> MBean. It interacts with the "
+"timer MBean to configure timer events at regular intervals and to transform "
+"them into JMX notifications more suitable for other services. The "
+"<literal>TimerService</literal> MBean takes the following attributes:"
#. Tag: para
#: J2EE_Additional_Services.xml:480
@@ -1789,6 +1827,11 @@
"<literal>msec</literal>, <literal>sec</literal>, <literal>min</literal> and "
"<literal>h</literal>."
msgstr ""
+"<emphasis role=\"bold\">TimerPeriod</emphasis>: This is the time period "
+"between notification. The time period is in milliseconds, unless otherwise "
+"specified with a unit like \"30min\" or \"4h\". Valid time suffixes are "
+"<literal>msec</literal>, <literal>sec</literal>, <literal>min</literal> and "
+"<literal>h</literal>."
#. Tag: para
#: J2EE_Additional_Services.xml:495
@@ -1862,6 +1905,11 @@
"that wants to receive this periodic notifications can subscribe to the "
"notification."
msgstr ""
+"This MBean configuration configures the <literal>jboss.monitor:"
+"name=Heartbeat,type=Timer</literal> timer to generate a <literal>jboss."
+"monitor.heartbeat</literal> notification every 60 seconds. Any service that "
+"that wants to receive this periodic notifications can subscribe to the "
+"notification."
#. Tag: para
#: J2EE_Additional_Services.xml:512
@@ -1874,6 +1922,12 @@
"for any events generated by the heartbeat timer used in the previous "
"examples."
msgstr ""
+"As an example, JBoss provides a simple <literal>NotificationListener</"
+"literal> MBean that can listen for a particular notification and log a log "
+"message when an event is generated. This MBean is very useful for debugging "
+"or manually observing notifications. The following MBean definition listens "
+"for any events generated by the heartbeat timer used in the previous "
+"examples."
#. Tag: programlisting
#: J2EE_Additional_Services.xml:515
@@ -1913,6 +1967,15 @@
"The following listing shows how we can limit notifications to only the "
"<literal>jboss.monitor.heartbeat</literal> type the timer service configured."
msgstr ""
+"The <literal>subscription-list</literal> element lists which MBeans the "
+"listener should listen to. Notice that the MBean we are listening to is the "
+"name of the actual timer MBean and not the <literal>TimerService</literal> "
+"MBean. Because the timer might generate multiple events, configured by "
+"multiple <literal>TimerService</literal> instances, you may need to filter "
+"by notification type. The <literal>filter</literal> element can be used to "
+"create notification filters that select only the notification types desired. "
+"The following listing shows how we can limit notifications to only the "
+"<literal>jboss.monitor.heartbeat</literal> type the timer service configured."
#. Tag: programlisting
#: J2EE_Additional_Services.xml:519
@@ -1956,6 +2019,11 @@
"written in any bean shell scripting language. The ScriptingListener accepts "
"has the following parameters."
msgstr ""
+"As an example of a slightly more interesting listener, we'll look at the "
+"ScriptingListener. This listener listens for particular events and then "
+"executes a specified script when events are received. The script can be "
+"written in any bean shell scripting language. The ScriptingListener accepts "
+"has the following parameters."
#. Tag: para
#: J2EE_Additional_Services.xml:525
@@ -1965,6 +2033,9 @@
"script is written in. This should be <literal>beanshell</literal>, unless "
"you have loaded libraries for another beanshell compatible language."
msgstr ""
+"<emphasis role=\"bold\">ScriptLanguage</emphasis>: This is the language the "
+"script is written in. This should be <literal>beanshell</literal>, unless "
+"you have loaded libraries for another beanshell compatible language."
#. Tag: para
#: J2EE_Additional_Services.xml:530
@@ -1974,6 +2045,9 @@
"evaluate. It is good practice to enclose the script in a CDATA section to "
"minimize conflicts between scripting language syntax and XML syntax."
msgstr ""
+"<emphasis role=\"bold\">Script</emphasis>: This is the text of the script to "
+"evaluate. It is good practice to enclose the script in a CDATA section to "
+"minimize conflicts between scripting language syntax and XML syntax."
#. Tag: para
#: J2EE_Additional_Services.xml:535
@@ -1997,6 +2071,12 @@
"that the beanshell script has a reference to the MBean server and can "
"execute operations against other MBeans."
msgstr ""
+"The following example illustrates the use of the <literal>ScriptingListener</"
+"literal>. When the previously configured timer generates a heartbeat "
+"notification, the beanshell script will execute, printing the current memory "
+"values to STDOUT. (This output will be redirected to the log files) Notice "
+"that the beanshell script has a reference to the MBean server and can "
+"execute operations against other MBeans."
#. Tag: programlisting
#: J2EE_Additional_Services.xml:543
@@ -2058,12 +2138,17 @@
"notifications that could be generated from a timer. Additionally, any MBean "
"can be coded to listen for timer-generated notifications."
msgstr ""
+"Of course, you are not limited to these JBoss-provided notification "
+"listeners. Other services such as the barrier service (see <xref linkend="
+"\"Additional_Services-The_BarrierController_Service\"/>) receive and act on "
+"notifications that could be generated from a timer. Additionally, any MBean "
+"can be coded to listen for timer-generated notifications."
#. Tag: title
#: J2EE_Additional_Services.xml:550
#, no-c-format
msgid "The BarrierController Service"
-msgstr ""
+msgstr "The BarrierController Service"
#. Tag: para
#: J2EE_Additional_Services.xml:551
@@ -2077,6 +2162,13 @@
"<literal>serviceB.start()</literal> is called before <literal>serviceA.start"
"()</literal>."
msgstr ""
+"Expressing dependencies between services using the <depends> tag is a "
+"convenient way to make the lifecycle of one service depend on the lifecycle "
+"of another. For example, when <literal>serviceA</literal> depends on "
+"<literal>serviceB</literal> JBoss will ensure the <literal>serviceB.create()"
+"</literal> is called before <literal>serviceA.create()</literal> and "
+"<literal>serviceB.start()</literal> is called before <literal>serviceA.start"
+"()</literal>."
#. Tag: para
#: J2EE_Additional_Services.xml:554
@@ -2089,6 +2181,12 @@
"operations are exposed so you cannot simply express a dependency like: if "
"JBoss is fully started then start my own service."
msgstr ""
+"However, there are cases where services do not conform to the JBoss "
+"lifecycle model, i.e. they don't expose create/start/stop/destroy "
+"lifecycle methods). This is the case for <literal>jboss.system:type=Server "
+"MBean</literal>, which represents the JBoss server itself. No lifecycle "
+"operations are exposed so you cannot simply express a dependency like: if "
+"JBoss is fully started then start my own service."
#. Tag: para
#: J2EE_Additional_Services.xml:557
@@ -2102,6 +2200,13 @@
"started. So putting a dependency on this MBean, if we want to hit a webpage "
"through Tomcat, will do no good."
msgstr ""
+"Or, even if they do conform to the JBoss lifecycle model, the completion of "
+"a lifecycle method (e.g. the <literal>start</literal> method) may not be "
+"sufficient to describe a dependency. For example the <literal>jboss.web:"
+"service=WebServer</literal> MBean that wraps the embedded Tomcat server in "
+"JBoss does not start the Tomcat connectors until after the server is fully "
+"started. So putting a dependency on this MBean, if we want to hit a webpage "
+"through Tomcat, will do no good."
#. Tag: para
#: J2EE_Additional_Services.xml:560
@@ -2118,6 +2223,16 @@
"implement more complex dependencies. This technique has been generalized "
"with the barrier controller service."
msgstr ""
+"Resolving such non-trivial dependencies is currently performed using JMX "
+"notifications. For example the <literal>jboss.system:type=Server</literal> "
+"MBean emits a notification of type <literal>org.jboss.system.server.started</"
+"literal> when it has completed startup, and a notification of type "
+"<literal>org.jboss.system.server.stopped</literal> when it shuts down. "
+"Similarly, <literal>jboss.web:service=WebServer</literal> emits a "
+"notification of type <literal>jboss.tomcat.connectors.started</literal> when "
+"it starts up. Services can subscribe to those notifications in order to "
+"implement more complex dependencies. This technique has been generalized "
+"with the barrier controller service."
#. Tag: para
#: J2EE_Additional_Services.xml:563
@@ -2128,6 +2243,10 @@
"notification in the system. It uses the received notifications to control "
"the lifecycle of a dynamically created MBean called the barrier."
msgstr ""
+"The barrier controller is a relatively simple MBean service that extends "
+"<literal>ListenerServiceMBeanSupport</literal> and thus can subscribe to any "
+"notification in the system. It uses the received notifications to control "
+"the lifecycle of a dynamically created MBean called the barrier."
#. Tag: para
#: J2EE_Additional_Services.xml:566
@@ -2141,6 +2260,13 @@
"will be started and stopped in tandem with the Barrier. When the barrier "
"controller is undeployed the barrier is destroyed."
msgstr ""
+"The barrier is instantiated, registered and brought to the create state when "
+"the barrier controller is deployed. After that, the barrier is started and "
+"stopped when matching notifications are received. Thus, other services need "
+"only depend on the barrier MBean using the usual <literal><depends></"
+"literal> tag, without having to worry about complex lifecycle issues. They "
+"will be started and stopped in tandem with the Barrier. When the barrier "
+"controller is undeployed the barrier is destroyed."
#. Tag: para
#: J2EE_Additional_Services.xml:569
@@ -2156,6 +2282,15 @@
"notification is originating (because your listener can have many active "
"subscriptions)."
msgstr ""
+"The notifications of interest are configured in the barrier controller using "
+"the <literal>SubscriptionList</literal> attribute. In order to identify the "
+"starting and stopping notifications we associate with each subscription a "
+"handback string object. Handback objects, if specified, are passed back "
+"along with the delivered notifications at reception time (i.e. when "
+"<literal>handleNotification()</literal> is called) to qualify the received "
+"notifications, so that you can identify quickly from which subscription a "
+"notification is originating (because your listener can have many active "
+"subscriptions)."
#. Tag: para
#: J2EE_Additional_Services.xml:572
@@ -2168,6 +2303,12 @@
"barrier controller. Thus we can have more than one notifications triggering "
"the starting or stopping of the barrier."
msgstr ""
+"So we tag the subscriptions that produce the starting/stopping notifications "
+"of interest using any handback strings, and we configure this same string to "
+"the <literal>StartBarrierHandback</literal> (and "
+"<literal>StopBarrierHandback</literal> correspondingly) attribute of the "
+"barrier controller. Thus we can have more than one notifications triggering "
+"the starting or stopping of the barrier."
#. Tag: para
#: J2EE_Additional_Services.xml:575
@@ -2182,6 +2323,14 @@
"to the console starting and stopping messages, so we know when the service "
"gets activated/deactivated."
msgstr ""
+"The following example shows a service that depends on the Tomcat connectors. "
+"In fact, this is a very common pattern for services that want to hit a "
+"servlet inside tomcat. The service that depends on the Barrier in the "
+"example, is a simple memory monitor that creates a background thread and "
+"monitors the memory usage, emitting notifications when thresholds get "
+"crossed, but it could be anything. We've used this because it prints out "
+"to the console starting and stopping messages, so we know when the service "
+"gets activated/deactivated."
#. Tag: programlisting
#: J2EE_Additional_Services.xml:578
@@ -2350,12 +2499,20 @@
"literal> operations on the barrier controller. The attribute "
"<literal>BarrierStateString</literal> indicates the status of the barrier."
msgstr ""
+"If you hot-deploy this on a running server the Barrier will be stopped "
+"because by the time the barrier controller is deployed the starting "
+"notification is already seen. (There are ways to overcome this.) However, if "
+"you re-start the server, the barrier will be started just after the Tomcat "
+"connectors get activated. You can also manually start or stop the barrier by "
+"using the <literal>startBarrier()</literal> and <literal>stopBarrier()</"
+"literal> operations on the barrier controller. The attribute "
+"<literal>BarrierStateString</literal> indicates the status of the barrier."
#. Tag: title
#: J2EE_Additional_Services.xml:585
#, no-c-format
msgid "Exposing MBean Events via SNMP"
-msgstr ""
+msgstr "Exposing MBean Events via SNMP"
#. Tag: para
#: J2EE_Additional_Services.xml:586
@@ -2367,6 +2524,11 @@
"versions may offer support for full agent get/set functionality that maps "
"onto MBean attributes or operations."
msgstr ""
+"JBoss has an SNMP adaptor service that can be used to intercept JMX "
+"notifications emitted by MBeans, convert them to traps and send them to SNMP "
+"managers. In this respect the snmp-adaptor acts as a SNMP agent. Future "
+"versions may offer support for full agent get/set functionality that maps "
+"onto MBean attributes or operations."
#. Tag: para
#: J2EE_Additional_Services.xml:589
@@ -2379,6 +2541,12 @@
"can then be configured to intercept the notification and map it onto an SNMP "
"traps. The adaptor uses the JoeSNMP package from OpenNMS as the SNMP engine."
msgstr ""
+"This service can be used to integrate JBoss with higher order system/network "
+"management platforms (HP OpenView, for example), making the MBeans visible "
+"to those systems. The MBean developer can instrument the MBeans by producing "
+"notifications for any significant event (e.g. server coldstart), and adaptor "
+"can then be configured to intercept the notification and map it onto an SNMP "
+"traps. The adaptor uses the JoeSNMP package from OpenNMS as the SNMP engine."
#. Tag: para
#: J2EE_Additional_Services.xml:592
@@ -2390,6 +2558,11 @@
"Inside the snmp-adaptor.sar directory, there are two configuration files "
"that control the SNMP service."
msgstr ""
+"The SNMP service is configured in <literal>snmp-adaptor.sar</literal>. This "
+"service is only available in the <literal>all</literal> configuration, so "
+"you'll need to copy it to your configuration if you want to use it. "
+"Inside the snmp-adaptor.sar directory, there are two configuration files "
+"that control the SNMP service."
#. Tag: para
#: J2EE_Additional_Services.xml:597
@@ -2399,6 +2572,9 @@
"traps. The content model for this file is shown in <xref linkend="
"\"_Exposing_MBean_Events_via_SNMP-The_schema_for_the_SNMP_managers_file\"/>."
msgstr ""
+"<emphasis role=\"bold\">managers.xml</emphasis>: configures where to send "
+"traps. The content model for this file is shown in <xref linkend="
+"\"_Exposing_MBean_Events_via_SNMP-The_schema_for_the_SNMP_managers_file\"/>."
#. Tag: para
#: J2EE_Additional_Services.xml:602
@@ -2410,6 +2586,11 @@
"\"_Exposing_MBean_Events_via_SNMP-"
"The_schema_for_the_notification_to_trap_mapping_file\"/>."
msgstr ""
+"<emphasis role=\"bold\">notifications.xml</emphasis>: specifies the exact "
+"mapping of each notification type to a corresponding SNMP trap. The content "
+"model for this file is shown in <xref linkend="
+"\"_Exposing_MBean_Events_via_SNMP-"
+"The_schema_for_the_notification_to_trap_mapping_file\"/>."
#. Tag: para
#: J2EE_Additional_Services.xml:607
@@ -2419,6 +2600,9 @@
"adaptor.sar/META-INF/jboss-service.xml</literal>. The configurable "
"parameters are:"
msgstr ""
+"The <literal>SNMPAgentService</literal> MBean is configured in <literal>snmp-"
+"adaptor.sar/META-INF/jboss-service.xml</literal>. The configurable "
+"parameters are:"
#. Tag: para
#: J2EE_Additional_Services.xml:612
@@ -2460,6 +2644,9 @@
"jboss.jmx.adaptor.snmp.agent.TrapFactory</literal> implementation class that "
"takes care of translation of JMX Notifications into SNMP V1 and V2 traps."
msgstr ""
+"<emphasis role=\"bold\">TrapFactoryClassName</emphasis>: The <literal>org."
+"jboss.jmx.adaptor.snmp.agent.TrapFactory</literal> implementation class that "
+"takes care of translation of JMX Notifications into SNMP V1 and V2 traps."
#. Tag: para
#: J2EE_Additional_Services.xml:632
@@ -2485,13 +2672,13 @@
#: J2EE_Additional_Services.xml:643
#, no-c-format
msgid "The schema for the SNMP managers file"
-msgstr ""
+msgstr "The schema for the SNMP managers file"
#. Tag: title
#: J2EE_Additional_Services.xml:651
#, no-c-format
msgid "The schema for the notification to trap mapping file"
-msgstr ""
+msgstr "The schema for the notification to trap mapping file"
#. Tag: para
#: J2EE_Additional_Services.xml:658
@@ -2504,4 +2691,10 @@
"<literal>SnmpAgentService</literal> and <literal>TrapdService</literal> are "
"not dependent on each other."
msgstr ""
+"<literal>TrapdService</literal> is a simple MBean that acts as an SNMP "
+"Manager. It listens to a configurable port for incoming traps and logs them "
+"as DEBUG messages using the system logger. You can modify the log4j "
+"configuration to redirect the log output to a file. "
+"<literal>SnmpAgentService</literal> and <literal>TrapdService</literal> are "
+"not dependent on each other."
More information about the jboss-cvs-commits
mailing list