JavaTM Adventure Builder Reference application - Version 1.0.1 > Installing the Demo |
This section describes how to install the JavaTM Adventure Builder Reference application, version 1.0.1 (referred to as adventure builder)
System RequirementsBefore installing the adventure builder, you need to download and install the following software:
2. Java 2 Platform, Enterprise Edition (J2EE TM) 1.4 SDK: download here
Note 1 : When downloading J2EE 1.4 SDK , you have the choice to download and install a bundle that comes with J2SE v1.4.2_02. If you choose this approach, you need not download and install J2SE 1.4.2_02 separately.
Note 2 : You also have the choice to
download and install J2EE 1.4 SDK without any J2SE
version bundled with it. If you choose this approach, ensure that the
J2SE version you use is J2SE v1.4.2_02.
NOTE 3 : If you are using this application on an already installed instance of the J2EE 1.4 SDK and you had already deployed the version of adventure builder that is present as part of the samples bundle of the J2EE 1.4 SDK, you have to undeploy all the adventure builder components completely before performing the instruction listed below. For instruction on uninstalling the Adventure Builder components, see the next section of this document.
Environment VariablesYou need to set the J2EE_HOME environment variable to setup the adventure builder. The scripts that invoke Ant look for the version of ant included with the J2EE 1.4 SDK. Ant 1.5.3 or greater will work but it is recommened to make these settings if you are not familiar with Ant.
Your PATH must include the following directories as the first two elements.
For Unix:NOTE : If you are using this application on an already installed instance of the J2EE 1.4 SDK and you had already deployed the version of adventure builder that is present as part of the samples bundle of the J2EE 1.4 SDK, you have to undeploy all the adventure builder components completely before performing the instructions listed below. For instructions on uninstalling the adventure builder components, see the next section of this document.
To install the demo, follow these steps:
Unzipping the distribution bundle creates a directory called adventure1.0.1 . The rest of this documentation refers to this directory as <adventure.home>.
If you are using Unix, open a shell prompt and enter these commands:
cd $J2EE_HOME/pointbase/tools/serveroption
sh startserver.sh
If you are using Windows, open a command prompt and enter these commands:
cd %J2EE_HOME%\pointbase\tools\serveroption
startserver.bat
If you are using Unix, open a shell prompt and enter these commands:
cd $J2EE_HOME/binIf you are using Windows, open a command prompt and enter these commands:
asadmin start-domain domain1
cd %J2EE_HOME%\bin
asadmin start-domain domain1
Property Name | Description | Examples |
j2ee.server.name | Host name of the server where the J2EE 1.4 SDK is installed | localhost |
j2ee.server.username | The name of admin user you entered while installing the J2EE 1.4 SDK | admin |
j2ee.server.password | The password you entered for the admin user while installing the J2EE 1.4 SDK | <your password> |
j2ee.adminserver.port |
The port number for admin server
you selected at the time of installation of the J2EE 1.4 SDK |
4848 |
If you are using Unix, open a shell prompt and enter these commands:
cd <adventure.home>/projectIf you are using Windows, open a command prompt and enter these commands:
asant setup
cd <adventure.home>/project
asant setup
If you are using Unix, open a shell prompt and enter these commands:
cd <adventure.home>/projectIf you are using Windows, open a command prompt and enter these commands:
asant deploy
cd <adventure.home>/project
asant deploy
After installing the adventure builder, you can start using it.
Uninstalling the Demo
First check if you have already deployed versions of adventure builder in your server by entering the following command and ensure that no application with name ConsumerWebsite or OPC or Bank or ActivitySupplier or LodgingSupplier or AirlineSupplier is present :
asadmin list-componentsIf any of the above mentioned applications are present in the server, undeploy them using the following command :
asadmin undeploy <application name>