[jboss-svn-commits] JBL Code SVN: r23816 - labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_Failure_Recovery_Guide/pt-BR.

[jboss-svn-commits at lists.jboss.org]

Author: ldelima at redhat.com
Date: 2008-11-10 22:26:47 -0500 (Mon, 10 Nov 2008)
New Revision: 23816

Modified:
   labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_Failure_Recovery_Guide/pt-BR/Architecture_of_the_Recovery_Manager.po
Log:
proofread completed

Modified: labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_Failure_Recovery_Guide/pt-BR/Architecture_of_the_Recovery_Manager.po
===================================================================
--- labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_Failure_Recovery_Guide/pt-BR/Architecture_of_the_Recovery_Manager.po	2008-11-11 02:19:54 UTC (rev 23815)
+++ labs/jbosstm/enterprise/tags/EAP_4_3_0/Transactions_Failure_Recovery_Guide/pt-BR/Architecture_of_the_Recovery_Manager.po	2008-11-11 03:26:47 UTC (rev 23816)
@@ -8,7 +8,7 @@
 "Project-Id-Version: Architecture_of_the_Recovery_Manager\n"
 "Report-Msgid-Bugs-To: http://bugs.kde.org\n"
 "POT-Creation-Date: 2008-09-23 06:30+0000\n"
-"PO-Revision-Date: 2008-11-11 11:13+1000\n"
+"PO-Revision-Date: 2008-11-11 13:26+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"
@@ -1301,7 +1301,7 @@
 "content of the file used to store the status of the participant, to "
 "determine that status and print a message indicating if a recovery action is "
 "needed or not."
-msgstr ""
+msgstr "A função do Módulo de Recuperação em tal aplicativo consiste na leitura do contéudo do arquivo usado para armazenar o estatus do participante para determinar o status e imprimir a mensagem indicando se a ação de recuperação é necessária ou não."
 
 #. Tag: screen
 #: Architecture_of_the_Recovery_Manager.xml:401
@@ -1441,7 +1441,7 @@
 "Recovery Manager. To do so, we just need to add an entry in the "
 "<filename>RecoveryManager-properties.xml</filename> by adding a new property "
 "as follow:"
-msgstr ""
+msgstr "O módulo de recuperação deve ser implementado agora, com o objetivo de ser chamado pelo Gerenciador de Recuperação. Para isto, nós apenas precisamos adicionar uma entrada no <filename>RecoveryManager-properties.xml</filename> pela adição de uma nova propriedade conforme abaixo:"
 
 #. Tag: screen
 #: Architecture_of_the_Recovery_Manager.xml:405
@@ -1464,7 +1464,7 @@
 "Where &lt;i&gt; represent the new occurrence number that follows the last "
 "that already exists in the file. Once started, the Recovery Manager will "
 "automatically load the added Recovery module."
-msgstr ""
+msgstr "Onde &lt;i&gt; representa o novo número de ocorrência que segue o último que já existe no arquivo. Uma vez inicializado, o Gerenciador de Recuperação carregará automaticamente o módulo de Recuperção adicionado."
 
 #. Tag: para
 #: Architecture_of_the_Recovery_Manager.xml:410
@@ -1472,13 +1472,13 @@
 msgid ""
 "The source of the code can be retrieved under the trailmap directory of the "
 "JBossTS installation."
-msgstr ""
+msgstr "A fonte do código pode ser removida sob o diretório de instalação do JBossTS."
 
 #. Tag: title
 #: Architecture_of_the_Recovery_Manager.xml:415
 #, no-c-format
 msgid "Another scenario"
-msgstr ""
+msgstr "Outro cenário"
 
 #. Tag: para
 #: Architecture_of_the_Recovery_Manager.xml:416
@@ -1489,7 +1489,7 @@
 "describe how the build a recovery module. In case of the OTS protocol, let’s "
 "consider how a recovery module that manages recovery of OTS resources can be "
 "configured."
-msgstr ""
+msgstr "Conforme mencionado, o aplicativo básico presente acima não apresenta o processo completo para recuperar a falha, mas isto é apenas apresentado para descrever como construir um módulo de recuperação. Neste caso do protocolo OTS, vamos considerar como o módulo de recuperação que gerencia os recursos OTS podem ser configurados. "
 
 #. Tag: para
 #: Architecture_of_the_Recovery_Manager.xml:420
@@ -1502,7 +1502,7 @@
 "appropriate decision either by roll backing or committing. Asking the "
 "RecoveryCoordinator object to determine the status consists to invoke the "
 "replay_completion operation on the RecoveryCoordinator."
-msgstr ""
+msgstr "Para gerenciar a recuperação no caso da faha, a especificação OTS foi definida como protocolo de recuperação. Os participantes da Transação num status duvidoso podem usar o RecoveryCoordinator para determinar o status da transação. De acordo com o status da transação, estes participantes podem tomar decisão tanto pela reversão ou confirmação. A solicitação do objeto RecoveryCoordinator para determinar o status consiste na invocação da operação replay_completion no RecoveryCoordinator."
 
 #. Tag: para
 #: Architecture_of_the_Recovery_Manager.xml:423
@@ -1514,7 +1514,7 @@
 "during the Resource registration process. Retrieving such "
 "RecoveryCoordinator per resource means that it has been stored in addition "
 "to other information describing the resource."
-msgstr ""
+msgstr "Para cada Recurso OTS num status duvidoso, é bastante "
 
 #. Tag: para
 #: Architecture_of_the_Recovery_Manager.xml:426
@@ -1531,6 +1531,16 @@
 "status, an appropriate action would be taken (for instance, rollback the "
 "resource is the status is aborted or inactive)."
 msgstr ""
+"A recovery module dedicated to recover OTS Resources could have the "
+"following behavior. When requested by the recovery Manager on the first pass "
+"it retrieves from the disk the list of resources that are in the doubt "
+"status. During the second pass, if the resources that were retrieved in the "
+"first pass still remain in the disk then they are considered as candidates "
+"for recovery. Therefore, the Recovery Module retrieves for each candidate "
+"its associated RecoveryCoordinator and invokes the replay_completion "
+"operation that the status of the transaction. According to the returned "
+"status, an appropriate action would be taken (for instance, rollback the "
+"resource is the status is aborted or inactive)."
 
 #. Tag: title
 #: Architecture_of_the_Recovery_Manager.xml:431
@@ -1548,6 +1558,11 @@
 "TransactionStatusConnector obects each of which connects to a "
 "TransactionStatusManager object in an Application Process."
 msgstr ""
+"The TransactionStatusConnectionManager object is used by the recovery "
+"modules to retrieve the status of transactions and acts like a proxy for "
+"TransactionStatusManager objects. It maintains a table of "
+"TransactionStatusConnector obects each of which connects to a "
+"TransactionStatusManager object in an Application Process."
 
 #. Tag: para
 #: Architecture_of_the_Recovery_Manager.xml:435
@@ -1563,12 +1578,21 @@
 "transaction type to the TransactionStatusManager in order to retrieve the "
 "transactions status."
 msgstr ""
+"The transactions status is retrieved using the getTransactionStatus methods "
+"which take a transaction Uid and if available a transaction type as "
+"parameters. The process Uid field in the transactions Uid parameter is used "
+"to lookup the target TransactionStatusManagerItem host/port pair in the "
+"Object Store. The host/port pair are used to make a TCP connection to the "
+"target TransactionStatusManager object by a TransactionStatusConnector "
+"object. The TransactionStatusConnector passes the transaction Uid/"
+"transaction type to the TransactionStatusManager in order to retrieve the "
+"transactions status."
 
 #. Tag: title
 #: Architecture_of_the_Recovery_Manager.xml:440
 #, no-c-format
 msgid "Expired Scanner Thread"
-msgstr ""
+msgstr "Expired Scanner Thread"
 
 #. Tag: para
 #: Architecture_of_the_Recovery_Manager.xml:441
@@ -1579,6 +1603,10 @@
 "the ObjectStore. A number of scanner modules are dynamically loaded which "
 "remove long dead items for a particular type."
 msgstr ""
+"When the Recovery Manager initialises an expiry scanner thread "
+"ExpiryEntryMonitor is created which is used to remove long dead items from "
+"the ObjectStore. A number of scanner modules are dynamically loaded which "
+"remove long dead items for a particular type."
 
 #. Tag: para
 #: Architecture_of_the_Recovery_Manager.xml:444
@@ -1587,6 +1615,8 @@
 "Scanner modules are loaded at initialisation and are specified as properties "
 "beginning with"
 msgstr ""
+"Scanner modules are loaded at initialisation and are specified as properties "
+"beginning with"
 
 #. Tag: screen
 #: Architecture_of_the_Recovery_Manager.xml:447
@@ -1605,6 +1635,8 @@
 "All the scanner modules are called periodically to scan for dead items by "
 "the ExpiryEntryMonitor thread. This period is set with the property:"
 msgstr ""
+"All the scanner modules are called periodically to scan for dead items by "
+"the ExpiryEntryMonitor thread. This period is set with the property:"
 
 #. Tag: screen
 #: Architecture_of_the_Recovery_Manager.xml:451
@@ -1619,6 +1651,8 @@
 "All scanners inherit the same behaviour from the java interface "
 "<interfacename>ExpiryScanner</interfacename> as illustrated in diagram below:"
 msgstr ""
+"All scanners inherit the same behaviour from the java interface "
+"<interfacename>ExpiryScanner</interfacename> as illustrated in diagram below:"
 
 #. Tag: para
 #: Architecture_of_the_Recovery_Manager.xml:460
@@ -1627,6 +1661,8 @@
 "A scan method is provided by this interface and implemented by all scanner "
 "modules, this is the method that gets called by the scanner thread."
 msgstr ""
+"A scan method is provided by this interface and implemented by all scanner "
+"modules, this is the method that gets called by the scanner thread."
 
 #. Tag: para
 #: Architecture_of_the_Recovery_Manager.xml:463
@@ -1637,6 +1673,10 @@
 "in the Object Store for a period of time before they are deleted. This time "
 "is set by the property:"
 msgstr ""
+"The ExpiredTransactionStatusManagerScanner removes long dead "
+"TransactionStatusManagerItems from the Object Store. These items will remain "
+"in the Object Store for a period of time before they are deleted. This time "
+"is set by the property:"
 
 #. Tag: screen
 #: Architecture_of_the_Recovery_Manager.xml:466
@@ -1648,7 +1688,7 @@
 #: Architecture_of_the_Recovery_Manager.xml:467
 #, no-c-format
 msgid "(default 12 hours)"
-msgstr ""
+msgstr "(padrão 12 horas)"
 
 #. Tag: title
 #: Architecture_of_the_Recovery_Manager.xml:472
@@ -1667,6 +1707,12 @@
 "determine whether a transaction is still in progress, if so then recovery "
 "does not happen."
 msgstr ""
+"This represents the user transactional program. A Local transaction (hash) "
+"table, maintained within the running application process keeps trace of the "
+"current status of all transactions created by that application process, The "
+"Recovery Manager needs access to the transaction tables so that it can "
+"determine whether a transaction is still in progress, if so then recovery "
+"does not happen."
 
 #. Tag: para
 #: Architecture_of_the_Recovery_Manager.xml:476
@@ -1678,6 +1724,11 @@
 "TransactionStatusManager’ part of the Object Store file hierarchy and "
 "identified by the process Uid of the application process."
 msgstr ""
+"The transaction tables are accessed via the TransactionStatusManager object. "
+"On application program initialisation the host/port pair that represents the "
+"TransactionStatusManager is written to the Object Store in '../Recovery/"
+"TransactionStatusManager’ part of the Object Store file hierarchy and "
+"identified by the process Uid of the application process."
 
 #. Tag: para
 #: Architecture_of_the_Recovery_Manager.xml:479
@@ -1687,6 +1738,9 @@
 "retrieve the status of a transaction and a TransactionStatusConnector object "
 "is used to make a TCP connection to the TransactionStatusManager."
 msgstr ""
+"he Recovery Manager uses the TransactionStatusConnectionManager object to "
+"retrieve the status of a transaction and a TransactionStatusConnector object "
+"is used to make a TCP connection to the TransactionStatusManager."
 
 #. Tag: title
 #: Architecture_of_the_Recovery_Manager.xml:484
@@ -1706,6 +1760,13 @@
 "Any free port is used by the TransactionStatusManager by default, however "
 "the port can be fixed with the property:"
 msgstr ""
+"This object acts as an interface for the Recovery Manager to obtain the "
+"status of transactions from running HPTS application processes. One "
+"TransactionStatusManager is created per application process by the class com."
+"arjuna.ats.arjuna.coordinator.InitAction. Currently a tcp connection is used "
+"for communication between the RecoveryManager and TransactionStatusManager. "
+"Any free port is used by the TransactionStatusManager by default, however "
+"the port can be fixed with the property:"
 
 #. Tag: screen
 #: Architecture_of_the_Recovery_Manager.xml:488
@@ -1726,6 +1787,14 @@
 "TransactionStatusConnector, the transaction status is obtained from the "
 "local thransaction table and returned back to the TransactionStatusConnector."
 msgstr ""
+"On creation the TransactionStatusManager obtains a port which it stores with "
+"the host in the Object Store as a TransactionStatusManagerItem. A Listener "
+"thread is started which waits for a connection request from a "
+"TransactionStatusConnector. When a connection is established a Connection "
+"thread is created which runs a Service (AtomicActionStatusService) which "
+"accepts a transaction Uid and a transaction type (if available) from a "
+"TransactionStatusConnector, the transaction status is obtained from the "
+"local thransaction table and returned back to the TransactionStatusConnector."
 
 #. Tag: title
 #: Architecture_of_the_Recovery_Manager.xml:494
@@ -1741,6 +1810,9 @@
 "inheritance. Thus AtomicAction transactions are stored in file path ../"
 "StateManager/BasicAction/AtomicAction."
 msgstr ""
+"All objects are stored in a file path which is equivalent to their class "
+"inheritance. Thus AtomicAction transactions are stored in file path ../"
+"StateManager/BasicAction/AtomicAction."
 
 #. Tag: para
 #: Architecture_of_the_Recovery_Manager.xml:498
@@ -1751,4 +1823,8 @@
 "uses the process id to locate transaction status manager items when "
 "contacting the originator application process for the transaction status."
 msgstr ""
+"All objects are identified by a unique identifier Uid. One of the values of "
+"which is a process id in which the object was created. The Recovery Manager "
+"uses the process id to locate transaction status manager items when "
+"contacting the originator application process for the transaction status."