Histórico da Página

<div id="main-content" class="wiki-content group">
	<h1 id="Configuraçãodotempodetransação-Índice">Index</h1>
	<p>
		<style type='text/css'>/*<![CDATA[*/
div.rbtoc1412695412969 {
	padding: 0px;
}
div.rbtoc1412695412969 ul {
	list-style: none;
	margin-left: 0px;
}
div.rbtoc1412695412969 li {
	margin-left: 0px;
	padding-left: 0px;
}
/*]]>*/
</style>
	<div class='toc-macro rbtoc1412695412969'>
		<ul class='toc-indentation'>
			<li><span class='TOCOutline'>1</span> <a
				href='#Configuraçãodotempodetransação-Objetivo'>Objective</a></li>
			<li><span class='TOCOutline'>2</span> <a
				href='#Configuraçãodotempodetransação-Transação'>Transaction</a>
				<ul class='toc-indentation'>
					<li><span class='TOCOutline'>2.1</span> <a
						href='#Configuraçãodotempodetransação-AlterarotempodetransaçãonoFluig'>Change
							TOTVS Fluig Platform transaction time</a></li>
				</ul></li>
		</ul>
	</div>
	</p>
	<h1 id="Configuraçãodotempodetransação-Objetivo">Objective</h1>
	<p>The objective of this article is to describe the procedure for
		changing TOTVS Fluig Platform default transaction time.</p>
	<h1 id="Configuraçãodotempodetransação-Transação">Transaction</h1>
	<p>A transaction is a unit of work containing one or more
		operations that share resources and that has ACID properties.</p>
	<p>The ACID acronym stands for atomicity, consistency, isolation
		and durability. Each property corresponds to:</p>
	<ul>
		<li>Atomicity: a transaction is atomic, i.e., the entire
			operation performed by the transaction must be put into effect or no
			part of the operation should be carried out;</li>
		<li>Consistency: when a transaction is completed, the entire
			system must be in a stable and consistent condition;</li>
		<li>Isolation: different transactions should be isolated;</li>
		<li>Durability: the operations performed by a transaction are
			persistent after being "committed". After being put into effect,
			changes made by the transaction will not be lost even in case of
			server failure.</li>
	</ul>
	<h3 id="Configuraçãodotempodetransação-AlterarotempodetransaçãonoFluig">Change
		TOTVS Fluig Platform transaction time</h3>
	<p>Fluig<p>TOTVS Fluig Platform transaction time change is performed in the
		INSTALACAO_FLUIG/jboss/standalone/configuration/standalone.xml file.</p>
	<p>&#160;</p>
	<div class="code panel pdl" style="border-width: 1px;">
		<div class="codeContent panelContent pdl">
			<pre class="theme: Confluence; brush: java; gutter: false"
				style="font-size: 12px;">       &lt;subsystem xmlns="urn:jboss:domain:transactions:1.3">
            &lt;core-environment>
                &lt;process-id>
                    &lt;uuid/>
                &lt;/process-id>
            &lt;/core-environment>
            &lt;recovery-environment socket-binding="txn-recovery-environment" status-socket-binding="txn-status-manager"/>
            &lt;coordinator-environment default-timeout="300"/>
        &lt;/subsystem></pre>
		</div>
	</div>
	<p>&#160;</p>
	<p>Fluig’s<p>TOTVS Fluig Platform’s default transaction time is 300 seconds. In order to
		change the transaction time, just replace the default value and
		restart Fluig service.</p>
	<p>&#160;</p>
	<div class="aui-message warning shadowed information-macro">
		<p class="title">Important</p>
		<span class="aui-icon icon-warning">Icon</span>
		<div class="message-content">
			<p>Fluig<p>TOTVS Fluig Platform default transaction time should be sufficient to perform
				a conventional transaction. Before increasing Fluig transaction
				time, check the fact that resulted in this decision.</p>
			<p>
				<strong>For example,</strong> review customization or integration
				performed in the workflow process events. Customization
				optimizations can reduce the time required to perform a transaction.
			</p>
		</div>
	</div>
</div>