[jboss-svn-commits] JBL Code SVN: r34565 - in labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA: tasks and 1 other directory.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Fri Aug 6 01:43:44 EDT 2010
Author: misty at redhat.com
Date: 2010-08-06 01:43:44 -0400 (Fri, 06 Aug 2010)
New Revision: 34565
Added:
labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/concepts/about_this_guide.dita
labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/concepts/frontmatter.dita
labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/concepts/introduction.dita
labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/concepts/objectstore_management.dita
labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/concepts/runtime_information.dita
labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/tasks/preparing_to_shut_down_the_system_completely.dita
labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/tasks/starting_transaction_manager_in_inactive_state.dita
labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/tasks/stopping_creation_of_new_transactions.dita
Log:
Began work on Administration Guide
Added: labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/concepts/about_this_guide.dita
===================================================================
--- labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/concepts/about_this_guide.dita (rev 0)
+++ labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/concepts/about_this_guide.dita 2010-08-06 05:43:44 UTC (rev 34565)
@@ -0,0 +1,82 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "../dtd/concept.dtd">
+<concept id="basic" xml:lang="en-us">
+ <title>About This Guide</title>
+ <conbody>
+ <section>
+ <title>What This Guide Contains</title>
+ The Administration Guide contains information on how to use ArjunaCore 4.12.0.
+ </section>
+ <section>
+ <title>Audience</title>
+ This guide is most relevant to engineers who are responsible for administering ArjunaCore 4.12.0.
+ </section>
+ <section>
+ <title>Prerequisites</title>
+ You should have installed ArjunaCore 4.10.0.
+ </section>
+ <section>
+ <title>Document Conventions</title>
+ The following conventions are used in this guide:
+ <simpletable>
+ <sthead>
+ <stentry>Convention</stentry>
+ <stentry>Description</stentry>
+ </sthead>
+ <strow>
+ <stentry><i>Italic</i></stentry>
+ <stentry>In paragraph text, <i>italic</i> identifies the titles of documents that are
+ being referenced. When used in conjunction with the <codeph>Code</codeph> text
+ described below, italics identify a variable that should be replaced
+ by the user with an actual value.</stentry>
+ </strow>
+ <strow>
+ <stentry><b>Bold</b></stentry>
+ <stentry>Emphasizes items of particular importance.</stentry>
+ </strow>
+ <strow>
+ <stentry><codeph>Code</codeph></stentry>
+ <stentry>Text that represents program code.</stentry>
+ </strow>
+ <strow>
+ <stentry>
+ <menucascade>
+ <uicontrol>File</uicontrol>
+ <uicontrol>Open</uicontrol>
+ </menucascade>
+ </stentry>
+ <stentry>A path to a function or dialog box within an interface. For
+ example,
+ <menucascade><uicontrol>File</uicontrol><uicontrol>Open</uicontrol></menucascade>
+ indicates that you should select the Open function from the file
+ menu.</stentry>
+ </strow>
+ <strow>
+ <stentry>( ) and |</stentry>
+ <stentry>Parentheses enclose optional items in command syntax. The vertical bar (pipe) separates syntax items in a list of choices. For example, any of the following three items can be entered in this syntax: persistPolicy (Never | OnTimer | OnUpdate | NoMoreOftenThan)</stentry>
+ </strow>
+ <strow>
+ <stentry><note type="note"></note> or <note type="warning"></note></stentry>
+ <stentry>A note highlights important supplemental information. A
+ warning highlights procedures or information that is necessary to avoid
+ damage to equipment, damage to software, loss of data, or invalid test
+ results.</stentry>
+ </strow>
+ </simpletable>
+ </section>
+
+ <section>
+ <title>Additional Documentation</title>
+ <ul>
+ <li>ArjunaCore 4.12.0 Release Notes: Provides latebreaking information about ArjunaCore 4.12.0.</li>
+ <li>ArjunaCore 4.12.0 Installation Guide: This guide provides instructions for installing ArjunaCore 4.12.0.</li>
+ <li>ArjunaCore 4.12.0 Programmer’s Guide: Provides guidance for writing applications. </li>
+ </ul>
+ </section>
+
+ <section>
+ <title>Contacting Us</title>
+ Questions or comments about ArjunaCore 4.12.0 should be directed to our support team.
+ </section>
+ </conbody>
+</concept>
Added: labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/concepts/frontmatter.dita
===================================================================
--- labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/concepts/frontmatter.dita (rev 0)
+++ labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/concepts/frontmatter.dita 2010-08-06 05:43:44 UTC (rev 34565)
@@ -0,0 +1,59 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "../dtd/concept.dtd">
+<concept id="frontmatter" xml:lang="en-us">
+ <title>ArjunaCore Administration Guide</title>
+ <abstract>
+ The Administration Guide contains information on how to use ArjunaCore 4.12.0.
+ </abstract>
+ <prolog>
+ <author type="creator">Mark Little</author>
+ <author type="creator">Andrew Dinn</author>
+ <author type="creator">Jonathan Halliday</author>
+ <author type="contributor">Misty Stanley-Jones</author>
+
+ <source href="http://jboss.org">JBoss.org</source>
+ <copyright>
+ <copyryear year="2009" />
+ <copyrholder>JBoss, Inc.</copyrholder>
+ </copyright>
+ <critdates>
+ <created date="2009-06-16" />
+ <revised modified="2010-08-04" />
+ </critdates>
+ <permissions view="all" />
+
+ <metadata>
+ <audience type="administrator" job="using" experiencelevel="general" />
+ <category>Administration</category>
+ <keywords>
+ <keyword>Administration</keyword>
+ <keyword>Maintenance</keyword>
+ <keyword>Configuration</keyword>
+ </keywords>
+ <prodinfo>
+ <prodname>ArjunaCore</prodname>
+ <vrmlist>
+ <vrm version="4.12.0" release="2009-06-08" />
+ </vrmlist>
+ <platform>Linux</platform>
+ <platform>UNIX</platform>
+ <platform>Microsoft Windows Server</platform>
+ </prodinfo>
+<!-- <othermeta></othermeta>-->
+ </metadata>
+ </prolog>
+ <conbody>
+ <section>
+ <title>Authors</title>
+ <ul>
+ <li>Mark Little</li>
+ <li>Andrew Dinn</li>
+ <li>Jonathan Halliday</li>
+ </ul>
+ </section>
+ <section>
+ <title>Copyright</title>
+ Copyright 2009 JBoss, Inc.
+ </section>
+ </conbody>
+</concept>
Added: labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/concepts/introduction.dita
===================================================================
--- labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/concepts/introduction.dita (rev 0)
+++ labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/concepts/introduction.dita 2010-08-06 05:43:44 UTC (rev 34565)
@@ -0,0 +1,81 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "../dtd/concept.dtd">
+<concept id="arjuna_core_introduction" xml:lang="en-us">
+ <title>Introduction</title>
+
+
+<prolog>
+ <author type="creator">JBoss, Inc.</author>
+ <author type="contributor">Misty Stanley-Jones</author>
+ <publisher>Red Hat Engineering Content Services</publisher>
+ <copyright>
+ <copyryear year="2010"/>
+ <copyrholder>JBoss.org</copyrholder>
+ </copyright>
+ <critdates>
+ <created date="2010"/>
+ <revised modified="2010-Aug-06"/>
+ </critdates>
+ <metadata>
+ <keywords>
+ <indexterm>security</indexterm>
+ <indexterm>object store</indexterm>
+ <indexterm>limitations</indexterm>
+ </keywords>
+ <prodinfo>
+ <prodname>ArjunaCore</prodname>
+ <vrmlist>
+ <vrm version="4.12.0"/>
+ </vrmlist>
+ </prodinfo>
+ </metadata>
+ </prolog>
+
+
+ <conbody>
+ <p>
+ Apart from ensuring that the run-time system is executing normally, there is little continuous administration needed for the ArjunaCore software. There are a few points however, that should be made:
+ </p>
+ <ul>
+ <li>
+ <p>
+ The present implementation of the ArjunaCore system provides no security or protection for data. The objects stored in the ArjunaCore object store are (typically) owned by the user who ran the application that created them. The Object Store and Object Manager facilities make no attempt to enforce even the limited form of protection that Unix/Windows provides. There is no checking of user or group IDs on access to objects for either reading or writing.
+ </p>
+ </li>
+ <li>
+ <p>
+ Persistent objects created in the Object Store never go away unless the StateManager.destroy method is invoked on the object or some application program explicitly deletes them. This means that the Object Store gradually accumulates garbage (especially during application development and testing phases). At present we have no automated garbage collection facility. Further, we have not addressed the problem of dangling references. That is, a persistent object, A, may have stored a Uid for another persistent object, B, in its passive representation on disk. There is nothing to prevent an application from deleting B even though A still contains a reference to it. When A is next activated and attempts to access B, a run-time error will occur.
+ </p>
+ </li>
+ <li>
+ <p>
+ There is presently no support for version control of objects or database reconfiguration in the event of class structure changes. This is a complex research area that we have not addressed. At present, if you change the definition of a class of persistent objects, you are entirely responsible for ensuring that existing instances of the object in the Object Store are converted to the new representation. The ArjunaCore software can neither detect nor correct references to old object state by new operation versions or vice versa.
+ </p>
+ </li>
+ <li>
+ <p>
+ Object store management is critically important to the transaction service.
+ </p>
+ </li>
+ </ul>
+
+ <!-- SAMPLE LINKS
+ <related-links>
+ <link href="../concepts/soapproxy.dita" format="dita" type="concept">
+ <linktext>SOAPProxy</linktext>
+ </link>
+<link href="../tasks/configure_soap.dita" format="dita" type="task">
+ <linktext>Configuring SOAP</linktext>
+ </link>
+
+ </related-links>
+ -->
+
+
+
+
+
+
+ </conbody>
+
+</concept>
Added: labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/concepts/objectstore_management.dita
===================================================================
--- labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/concepts/objectstore_management.dita (rev 0)
+++ labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/concepts/objectstore_management.dita 2010-08-06 05:43:44 UTC (rev 34565)
@@ -0,0 +1,67 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "../dtd/concept.dtd">
+<concept id="objectstore_management" xml:lang="en-us">
+ <title>ObjectStore Management</title>
+
+
+<prolog>
+ <author type="creator">JBoss, Inc.</author>
+ <author type="contributor">Misty Stanley-Jones</author>
+ <publisher>Red Hat Engineering Content Services</publisher>
+ <copyright>
+ <copyryear year="2010"/>
+ <copyrholder>JBoss.org</copyrholder>
+ </copyright>
+ <critdates>
+ <created date="2010"/>
+ <revised modified="2010-Aug-06"/>
+ </critdates>
+ <metadata>
+ <keywords>
+ <indexterm>security</indexterm>
+ <indexterm>object store</indexterm>
+ <indexterm>limitations</indexterm>
+ </keywords>
+ <prodinfo>
+ <prodname>ArjunaCore</prodname>
+ <vrmlist>
+ <vrm version="4.12.0"/>
+ </vrmlist>
+ </prodinfo>
+ </metadata>
+ </prolog>
+
+
+ <conbody>
+ <p>
+ Within the transaction service installation, the object store is updated regularly whenever transactions are created, or when <apiname>Transactional Objects for Java</apiname> is used.
+ </p>
+ <p>
+ In a failure free environment, the only object states which should reside within the object store are those representing objects created with the <apiname>Transactional Objects for Java</apiname> API. However, if failures occur, transaction logs may remain in the object store until crash recovery facilities have resolved the transactions they represent.
+ </p>
+ <p>
+ As such it is very important that the contents of the object store are not deleted without due care and attention, as this will make it impossible to resolve in doubt transactions.
+ </p>
+ <p>
+ In addition, if multiple users share the same object store it is important that they realise this and do not simply delete the contents of the object store assuming it is an exclusive resource.
+ </p>
+ <!-- SAMPLE LINKS
+ <related-links>
+ <link href="../concepts/soapproxy.dita" format="dita" type="concept">
+ <linktext>SOAPProxy</linktext>
+ </link>
+<link href="../tasks/configure_soap.dita" format="dita" type="task">
+ <linktext>Configuring SOAP</linktext>
+ </link>
+
+ </related-links>
+ -->
+
+
+
+
+
+
+ </conbody>
+
+</concept>
Added: labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/concepts/runtime_information.dita
===================================================================
--- labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/concepts/runtime_information.dita (rev 0)
+++ labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/concepts/runtime_information.dita 2010-08-06 05:43:44 UTC (rev 34565)
@@ -0,0 +1,58 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "../dtd/concept.dtd">
+<concept id="arjuna_core_runtime_information" xml:lang="en-us">
+ <title>ArjunaCore runtime information</title>
+
+
+<prolog>
+ <author type="creator">JBoss, Inc.</author>
+ <author type="contributor">Misty Stanley-Jones</author>
+ <publisher>Red Hat Engineering Content Services</publisher>
+ <copyright>
+ <copyryear year="2010"/>
+ <copyrholder>JBoss.org</copyrholder>
+ </copyright>
+ <critdates>
+ <created date="2010"/>
+ <revised modified="2010-Aug-06"/>
+ </critdates>
+ <metadata>
+ <keywords>
+ <indexterm>security</indexterm>
+ <indexterm>object store</indexterm>
+ <indexterm>limitations</indexterm>
+ </keywords>
+ <prodinfo>
+ <prodname>ArjunaCore</prodname>
+ <vrmlist>
+ <vrm version="4.12.0"/>
+ </vrmlist>
+ </prodinfo>
+ </metadata>
+ </prolog>
+
+
+ <conbody>
+ <p>
+ Compile time configuration information is available via the <codeph>com.arjuna.common.util.ConfigurationInfo</codeph> class. Runtime configuration is embodied in the various <codeph><name>EnvironmentBean</codeph> classes, see the configuration section of the user guide. These beans have corresponding MBean interfaces and may be linked to JMX for remote inspection of the configuration if desired.
+ </p>
+ <!-- SAMPLE LINKS
+ <related-links>
+ <link href="../concepts/soapproxy.dita" format="dita" type="concept">
+ <linktext>SOAPProxy</linktext>
+ </link>
+<link href="../tasks/configure_soap.dita" format="dita" type="task">
+ <linktext>Configuring SOAP</linktext>
+ </link>
+
+ </related-links>
+ -->
+
+
+
+
+
+
+ </conbody>
+
+</concept>
Added: labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/tasks/preparing_to_shut_down_the_system_completely.dita
===================================================================
--- labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/tasks/preparing_to_shut_down_the_system_completely.dita (rev 0)
+++ labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/tasks/preparing_to_shut_down_the_system_completely.dita 2010-08-06 05:43:44 UTC (rev 34565)
@@ -0,0 +1,113 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<!-- This document was created with Syntext Serna Free. -->
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd" []>
+<task id="preparing_to_shut_down_system_completely" xml:lang="en-us">
+
+ <title>Preparing to shut down the system completely</title>
+
+ <prolog>
+ <author type="creator">JBoss, Inc.</author>
+ <author type="contributor">Misty Stanley-Jones</author>
+ <publisher>Red Hat Engineering Content Services</publisher>
+ <copyright>
+ <copyryear year="2010"/>
+ <copyrholder>JBoss.org</copyrholder>
+ </copyright>
+ <critdates>
+ <created date="2010"/>
+ <revised modified="2010-Aug-06"/>
+ </critdates>
+ <metadata>
+ <keywords>
+ <indexterm>Search</indexterm>
+ <indexterm>Terms</indexterm>
+ <indexterm>Here</indexterm>
+ </keywords>
+ <prodinfo>
+ <prodname>ArjunaCore</prodname>
+ <vrmlist>
+ <vrm version="4.12.0"/>
+ </vrmlist>
+ </prodinfo>
+ </metadata>
+ </prolog>
+
+ <taskbody>
+
+ <context>
+ <p>
+ Before you can shut down the system completely, you need to terminate the background transaction reaper.
+ </p>
+
+ </context>
+
+ <steps>
+
+ <step>
+ <cmd>
+ If you are creating transactions with timeouts, prevent the creation of new transactions using <codeph>TxControl.disable</codeph>.
+ </cmd>
+ </step>
+ <step>
+ <cmd>
+ Call <codeph>TransactionReaper.terminate</codeph>.
+ </cmd>
+ <info>
+ This method takes a boolean parameter: if <state value="true" /> then the method will wait for the normal timeout periods associated with any transactions to expire before terminating the transactions; if <state value="false" /> then transactions will be forced to terminate (rollback or have their outcome set such that they can only ever rollback) immediately.
+ </info>
+ <note>
+ If you indent to restart the recovery manager after having terminated it, then you must use the terminate method with asynchronous behavior set to <state value="false" />.
+ </note>
+ </step>
+ </steps>
+
+ <result>
+ <p>
+ You can now safely shut down the transaction manager's host system.
+ </p>
+ </result>
+
+ </taskbody>
+
+ <!-- LOTS OF SAMPLE RELATED LINKS
+ <related-links>
+
+ <link href="../concepts/database.dita" format="dita" type="concept">
+ <linktext>Database and Message Store</linktext>
+ </link>
+
+ <link href="../concepts/messagestore.dita" format="dita" type="concept">
+ <linktext>Message Store</linktext>
+ </link>
+
+ <link href="../concepts/registry.dita" format="dita" type="concept">
+ <linktext>Service Registry</linktext>
+ </link>
+
+ <link href="../concepts/databaseschema.dita" format="dita" type="concept">
+ <linktext>Database Schema</linktext>
+ </link>
+
+ <link href="../concepts/persistencelayer.dita" format="dita" type="concept">
+ <linktext>Persistence Layer</linktext>
+ </link>
+
+ <link href="../concepts/serviceregistry.dita" format="dita" type="concept">
+ <linktext>Service Registry</linktext>
+ </link>
+
+ <link href="../concepts/sql.dita" format="dita" type="concept">
+ <linktext>Structured Query Language</linktext>
+ </link>
+
+ <link href="../references/databasesettings.dita" format="dita" type="reference">
+ <linktext>Database Settings</linktext>
+ </link>
+
+ <link href="../tasks/extensions.dita" format="dita" type="task">
+ <linktext>Configuring Extensions</linktext>
+ </link>
+
+ </related-links>
+ -->
+</task>
Added: labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/tasks/starting_transaction_manager_in_inactive_state.dita
===================================================================
--- labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/tasks/starting_transaction_manager_in_inactive_state.dita (rev 0)
+++ labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/tasks/starting_transaction_manager_in_inactive_state.dita 2010-08-06 05:43:44 UTC (rev 34565)
@@ -0,0 +1,101 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<!-- This document was created with Syntext Serna Free. -->
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd" []>
+<task id="basic" xml:lang="en-us">
+
+ <title>Starting the transactin manager in an inactive state</title>
+
+ <prolog>
+ <author type="creator">JBoss, Inc.</author>
+ <author type="contributor">Misty Stanley-Jones</author>
+ <publisher>Red Hat Engineering Content Services</publisher>
+ <copyright>
+ <copyryear year="2010"/>
+ <copyrholder>JBoss.org</copyrholder>
+ </copyright>
+ <critdates>
+ <created date="2010"/>
+ <revised modified="2010-Aug-06"/>
+ </critdates>
+ <metadata>
+ <keywords>
+ <indexterm>Search</indexterm>
+ <indexterm>Terms</indexterm>
+ <indexterm>Here</indexterm>
+ </keywords>
+ <prodinfo>
+ <prodname>ArjunaCore</prodname>
+ <vrmlist>
+ <vrm version="4.12.0"/>
+ </vrmlist>
+ </prodinfo>
+ </metadata>
+ </prolog>
+
+ <taskbody>
+
+ <context>
+ <p>
+ By default the transaction manager starts up in an active state such that new transactions can be created immediately.
+ </p>
+
+ </context>
+
+ <steps>
+
+ <step>
+ <cmd>If you wish to have more control over this it is possible to set the <option>CoordinatorEnvironmentBean.startDisabled</option> configuration option to <boolean state="yes" />.</cmd>
+
+ </step>
+ </steps>
+
+ <result>
+ <p>
+ No transactions can be created until the transaction manager is enabled via a call to <codeph>TxControl.enable</codeph>
+ </p>
+ </result>
+
+ </taskbody>
+
+ <!-- LOTS OF SAMPLE RELATED LINKS
+ <related-links>
+
+ <link href="../concepts/database.dita" format="dita" type="concept">
+ <linktext>Database and Message Store</linktext>
+ </link>
+
+ <link href="../concepts/messagestore.dita" format="dita" type="concept">
+ <linktext>Message Store</linktext>
+ </link>
+
+ <link href="../concepts/registry.dita" format="dita" type="concept">
+ <linktext>Service Registry</linktext>
+ </link>
+
+ <link href="../concepts/databaseschema.dita" format="dita" type="concept">
+ <linktext>Database Schema</linktext>
+ </link>
+
+ <link href="../concepts/persistencelayer.dita" format="dita" type="concept">
+ <linktext>Persistence Layer</linktext>
+ </link>
+
+ <link href="../concepts/serviceregistry.dita" format="dita" type="concept">
+ <linktext>Service Registry</linktext>
+ </link>
+
+ <link href="../concepts/sql.dita" format="dita" type="concept">
+ <linktext>Structured Query Language</linktext>
+ </link>
+
+ <link href="../references/databasesettings.dita" format="dita" type="reference">
+ <linktext>Database Settings</linktext>
+ </link>
+
+ <link href="../tasks/extensions.dita" format="dita" type="task">
+ <linktext>Configuring Extensions</linktext>
+ </link>
+
+ </related-links>
+ -->
+</task>
Added: labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/tasks/stopping_creation_of_new_transactions.dita
===================================================================
--- labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/tasks/stopping_creation_of_new_transactions.dita (rev 0)
+++ labs/jbosstm/trunk/ArjunaCore/docs/user_guide/Administration_Guide/DITA/tasks/stopping_creation_of_new_transactions.dita 2010-08-06 05:43:44 UTC (rev 34565)
@@ -0,0 +1,105 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<!-- This document was created with Syntext Serna Free. -->
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd" []>
+<task id="basic" xml:lang="en-us">
+
+ <title>Stopping the creation of new transactions</title>
+
+ <prolog>
+ <author type="creator">JBoss, Inc.</author>
+ <author type="contributor">Misty Stanley-Jones</author>
+ <publisher>Red Hat Engineering Content Services</publisher>
+ <copyright>
+ <copyryear year="2010"/>
+ <copyrholder>JBoss.org</copyrholder>
+ </copyright>
+ <critdates>
+ <created date="2010"/>
+ <revised modified="2010-Aug-06"/>
+ </critdates>
+ <metadata>
+ <keywords>
+ <indexterm>Search</indexterm>
+ <indexterm>Terms</indexterm>
+ <indexterm>Here</indexterm>
+ </keywords>
+ <prodinfo>
+ <prodname>ArjunaCore</prodname>
+ <vrmlist>
+ <vrm version="4.12.0"/>
+ </vrmlist>
+ </prodinfo>
+ </metadata>
+ </prolog>
+
+ <taskbody>
+
+ <context>
+ <p>
+ It is possible to stop the creation of new transactions at any time.
+ </p>
+
+ </context>
+
+ <steps>
+
+ <step>
+ <choices>
+ <choice>
+ <p>To allow recovery to continue, call <codeph>TxControl.disable</codeph>.></p>
+ <p>
+ Transactions that are currently executing will not be affected. By default recovery will be allowed to continue and the transaction system will still be available to manage recovery requests from other instances in a distributed environment. See the Failure Recovery Guide for further details. <!-- Add xref -->
+ </p>
+ </choice>
+ <choice>
+ <p>If you wish to disable recovery as well as remove any resources it maintains, then you can pass <codeph>true</codeph> to <codeph>TxControl.disable</codeph>. The default is to use <codeph>false</codeph>.
+ </p>
+ </choice>
+ </choices>
+ </step>
+ </steps>
+
+ </taskbody>
+
+ <!-- LOTS OF SAMPLE RELATED LINKS
+ <related-links>
+
+ <link href="../concepts/database.dita" format="dita" type="concept">
+ <linktext>Database and Message Store</linktext>
+ </link>
+
+ <link href="../concepts/messagestore.dita" format="dita" type="concept">
+ <linktext>Message Store</linktext>
+ </link>
+
+ <link href="../concepts/registry.dita" format="dita" type="concept">
+ <linktext>Service Registry</linktext>
+ </link>
+
+ <link href="../concepts/databaseschema.dita" format="dita" type="concept">
+ <linktext>Database Schema</linktext>
+ </link>
+
+ <link href="../concepts/persistencelayer.dita" format="dita" type="concept">
+ <linktext>Persistence Layer</linktext>
+ </link>
+
+ <link href="../concepts/serviceregistry.dita" format="dita" type="concept">
+ <linktext>Service Registry</linktext>
+ </link>
+
+ <link href="../concepts/sql.dita" format="dita" type="concept">
+ <linktext>Structured Query Language</linktext>
+ </link>
+
+ <link href="../references/databasesettings.dita" format="dita" type="reference">
+ <linktext>Database Settings</linktext>
+ </link>
+
+ <link href="../tasks/extensions.dita" format="dita" type="task">
+ <linktext>Configuring Extensions</linktext>
+ </link>
+
+ </related-links>
+ -->
+</task>
More information about the jboss-svn-commits
mailing list