Java[tm] Adventure Builder Reference Application

Java[tm] Adventure Builder Reference Application - V1.0 > Installing the Demo

This section describes how to install the Java(tm) Adventure Builder Reference application, version 1.0 (referred to as adventure builder)

System Requirements

Before installing the adventure builder, you need to download and install the following software:

1. Java 2 Platform, Standard Edition (J2SE^TM ), v1.4.2_02

download here

2. Java 2 Platform, Enterprise Edition (J2EE^TM) 1.4 SDK: download here

Note 1 : When downloading J2EE 1.4 Developer's Release, 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 Developer's Release 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.

Installing the Java (tm) Adventure Builder Reference application

NOTE : If you are using this application on an already installed instance of the J2EE 1.4 Developer's Release and you had already deployed the version of adventure builder that is present as part of the samples bundle of the J2EE 1.4 Developer's Release, 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.

To install the demo, follow these steps:

Unzip the distribution bundle (adventure-1_0.zip) into any directory.
Unzipping the distribution bundle creates a directory called adventure1.0 . The rest of this documentation refers to this directory as <adventure.home>.
Start Pointbase database and wait till it is up and running.
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
Start the J2EE server and wait till it is up and running.
If you are using Unix, open a shell prompt and enter these commands:
```
cd $J2EE_HOME/bin
asadmin start-domain --domain domain1
```
If you are using Windows, open a command prompt and enter these commands:
```
cd %J2EE_HOME%\bin
asadmin start-domain --domain domain1
```
Run asant using build.xml file to install and configure database resources.
If you are using Unix, open a shell prompt and enter these commands:
```
cd <adventure.home>/src
asant setup
```
If you are using Windows, open a command prompt and enter these commands:
```
cd <adventure.home>\src
asant setup
```
Run asant using build.xml file to deploy the applications.
If you are using Unix, open a shell prompt and enter these commands:
```
cd <adventure.home>/src
asant deploy-apps
```
If you are using Windows, open a command prompt and enter these commands:
```
cd <adventure.home>\src
     
asant deploy-apps
```

NOTE: Before redeploying, you must first execute the command asant undeploy-apps and asant unsetup to clean up the existing files resulted from the initial deployment.

Verifying  Deployment

As an optional step, you can use the Application Server Administration Tool to verify that the application has been registered.

To verify the registration of the application, do the following:

Execute the command asadmin list-components to look at applications deployed with a server instance. For example:

<install_dir>/bin/asadmin list-components --user <username> --password <password>

You will see the two Adventure Builder applications listed:

ConsumerWebsite <j2ee-application>

OPC <j2ee-application>

Bank <j2ee-application>

ActivitySupplier <j2ee-application>

LodgingSupplier <j2ee-application>

AirlineSupplier <j2ee-application>

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-components

If any of the above mentioned applications are present in the server, undeploy them using the following command :

asadmin undeploy <application name>