Trail map Introduction Installation Content About the Sample Application Deploying the Sample Application Atomic Transactions Business Activities Sample Application Source Code Where next? Navigation Start Trailmap Previous Next
| print this page
| email this page
Deploying the sample application To run the demonstration application, you must compile the source code; bundle it, along with the required metadata files, into appropriate deployment constructs and then deploy these into the application container. This process is somewhat involved, but fortunately is completely automated by an ant build script. To proceed, you will need to install ant (http://ant.apache.org/) to take advantage of the supplied build file. Version 1.6.1 or later of ant is recommended for this application. The application may not function correctly with versions prior to 1.5. Deploying into webMethods. This release has been tested against webMethods 5.0.2. N.B. The classpath used to run webMethods must be modified so that the stax-api.1.0.jar contained within this distribution is encountered prior to all other webMethods jars. Install webMethods. Edit the `<xts-home>/demo/webmethods.properties` file, replacing the `WEBMETHODS_HOSTNAME`, `WEBMETHODS_PORT`, `WEBMETHODS_URLSTUB`, `WEBMETHODS_DEPLOY_DIR` and `WEBMETHODS_HOME` variables to reflect the location of your webMethods installation Note: You will not have to do this part if you chose to initialise this information during install. Compile the application source, build the application archive file and deploy it into webMethods deploy directory by typing '`build.sh webmethods clean deploy`' on Unix or '`build.bat webmethods clean deploy`' on Windows Run the application from the deploy directory by using the webMethods runapp command. Invoke the demo client by browsing the URL (e.g.): `http://hostname:port/xts-demo/` This release of the demo application includes the ability to run the client against a mixture of backend webservices. The property files contain the URLs of the webservices, which can be changed to exercise any combination and demonstrate a distributed transaction. The services are started using the same mechanism as above. Each platform will be running its own copy of the webservices but the deployed client will access those services configured in the relevant property file. Using the application When invoked, the client will attempt to begin a transaction, reserve theatre tickets, a restaurant table and a taxi according to the parameters you have selected, then commit the transaction. It will log each step of its activity to the console window. As the transaction proceeds, each of the Web Services will pop up a window of its own in which its state and activity log can be seen. Some events in the service code are also logged to the console. The three server applications support a manual transaction control mode which you can use to simulate transaction failures. Use the Change Mode button on the server GUIs. Notice that the client throws an exception if the transaction is rolled back. [ Note: The manual commit mode overrides the normal availability checks in the services, so overbooking may occur. ] The following pages explain the two transaction models available in the XML Transaction , Atomic Transactions and Business Activities. Reading the following pages will help you understand the events taking place within the sample application.
Copyright 2002-2005 Arjuna Technologies All Rights Reserved. info@arjuna.com +44 191 243 0676