You configure JTS transactions by running JBoss CLI commands. For your convenience, this quickstart batches the commands into a configure-jts-transactions.cli script provided in the root directory of this quickstart.

1. Before you begin, back up your server configuration file

   • If it is running, stop the {productName} server.

   • Back up the file: {jbossHomeName}/standalone/configuration/standalone-full.xml

   • After you have completed testing this quickstart, you can replace this file to restore the server to its original configuration.

2. Start the {productName} server with the standalone full profile, passing a unique node ID by typing the following command. Make sure you replace UNIQUE_NODE_ID_1 with a node identifier that is unique to both servers.

3. Start the {productName} server with the standalone full profile, passing a unique node ID, by typing the following command. Make sure you replace UNIQUE_NODE_ID_1 with a node identifier that is unique to both servers.

   $ {jbossHomeName}/bin/standalone.sh -c standalone-full.xml -Djboss.tx.node.id=UNIQUE_NODE_ID_1

   Note	For Windows, use the {jbossHomeName}\bin\standalone.bat script.

4. Review the configure-jts-transactions.cli file in the root of this quickstart directory. This script configures the server to use jts transaction processing.

5. Open a new terminal, navigate to the root directory of this quickstart, and run the following command, replacing {jbossHomeName} with the path to your server:

   $ {jbossHomeName}/bin/jboss-cli.sh --connect --file=configure-jts-transactions.cli

   Note	For Windows, use the {jbossHomeName}\bin\jboss-cli.bat script.

   You should see the following result when you run the script:

   The batch executed successfully
   process-state: restart-required

6. Stop the {productName} server.

After stopping the server, open the {jbossHomeName}/standalone/configuration/standalone-full.xml file and review the changes.

1. The orb initializers transactions attribute is changed from spec to full in the iiop-openjdk subsystem to enable JTS.

   <subsystem xmlns="{IiopOpenJdkSubsystemNamespace}">
       <initializers transactions="full" security="identity"/>
   </subsystem>

2. An empty <jts/> element is added to the end of the transactions subsystem to enable JTS.

   <subsystem xmlns="{TransactionsSubsystemNamespace}">
       <core-environment node-identifier="${jboss.tx.node.id}">
           <process-id>
               <uuid/>
           </process-id>
       </core-environment>
       <recovery-environment socket-binding="txn-recovery-environment" status-socket-binding="txn-status-manager"/>
       <jts/>
   </subsystem>

Make a copy of this {productName} directory structure to use for the second server.

Application server 1 must be now configured to use the PostgreSQL database created previously in the Configure the PostgreSQL Database for Use with this Quickstart section.

1. Make sure you start the PostgreSQL database. Unless you have set up the database to automatically start as a service, you must repeat the instructions "Start the database server" for your operating system every time you reboot your machine.

2. Follow the instructions to Add the PostgreSQL Module to the {productName} Server to the server 1 install only.

3. Follow the instructions to Configure the PostgreSQL Driver in the {ProductName} Server for the server 1 configuration. Make sure you pass the -Djboss.tx.node.id=UNIQUE_NODE_ID_1 on the command line when you start the first server to configure PostgreSQL.

1. Start the first {productName} server with the standalone full profile, passing a unique node ID, by typing the following command. Make sure you replace UNIQUE_NODE_ID_1 with the node identifier that you used when you previously started the server.

   $ {jbossHomeName}_1/bin/standalone.sh -c standalone-full.xml -Djboss.tx.node.id=UNIQUE_NODE_ID_1

   Note	For Windows, use the {jbossHomeName}_1\bin\standalone.bat script.

2. Open a new terminal, navigate to the root directory of this quickstart, and run the following command, replacing {jbossHomeName}_1 with the path to your server:

   $ {jbossHomeName}_1/bin/jboss-cli.sh --connect --file=remove-jts-transactions.cli

   Note	For Windows, use the {jbossHomeName}_1\bin\jboss-cli.bat script.

   This script removes the JTS configuration from the iiop-openjdk and transactions subsystems in the server configuration. You should see the following result when you run the script:

   The batch executed successfully
   process-state: restart-required
   {
       "outcome" => "success",
       "result" => undefined
   }

1. Start the first {productName} server with the standalone full profile, passing a unique node ID, by typing the following command. Make sure you replace UNIQUE_NODE_ID_1 with the node identifier that you used when you previously started the server.

   $ {jbossHomeName}_1/bin/standalone.sh -c standalone-full.xml -Djboss.tx.node.id=UNIQUE_NODE_ID_1

   Note	For Windows, use the {jbossHomeName}_1\bin\standalone.bat script.

2. To start the JBoss CLI tool, open a new terminal, navigate to the {jbossHomeName}_1 directory, and type the following:

   $ {jbossHomeName}_1/bin/jboss-cli.sh --connect

   Note	For Windows, use the {jbossHomeName}_1\bin\jboss-cli.bat script.

3. At the prompt, type the following commands.

   /subsystem=iiop-openjdk/:write-attribute(name=transactions,value=spec)
   /subsystem=transactions/:undefine-attribute(name=jts)
   /subsystem=transactions/:undefine-attribute(name=node-identifier)

4. You should see the following response after each command execution.

   {
       "outcome" => "success",
       "response-headers" => {
           "operation-requires-reload" => true,
           "process-state" => "restart-required"
       }
   }

1. Stop the server.

2. If you backed up the {jbossHomeName}/standalone/configuration/standalone-full.xml file, ,simply replace the edited configuration file with the backup copy.

3. If you did not make a backup copy, open the file {jbossHomeName}/standalone/configuration/standalone-full.`xml and disable JTS as follows:

   • Find the orb subsystem and change the configuration back to its original state.

     <subsystem xmlns="{IiopOpenJdkSubsystemNamespace}">
         <initializers transactions="spec" security="identity"/>
     </subsystem>

   • Find the transaction subsystem and remove the node-identifier attribute from the core-environment element. Also remove the <jts/> element.

     <subsystem xmlns="{TransactionsSubsystemNamespace}">
         <core-environment>
             <process-id>
                 <uuid/>
             </process-id>
         </core-environment>
         <recovery-environment socket-binding="txn-recovery-environment" status-socket-binding="txn-status-manager"/>
     </subsystem>

../shared-doc/run-the-quickstart-in-jboss-developer-studio.adoc