Verifying an OBE Installation

Once you've built or installed and prepared OBE, there are several ways to verify that the installation of OBE is functioning correctly. First, you must select a configuration directory.

Select a Configuration

OBE comes with three configuration directories and provides shell scripts for switching between them. From the $OBE_HOME/bin directory, execute one of the following scripts:

staging to use the empty configuration that is provided for your own work. This is the default configuration.

examples

to use the examples configuration

tests

to use the test configuration

The configuration setting is persistent.

Start the Server

OBE provides convenience shell scripts for starting and stopping the application server. From the $OBE_HOME/bin directory, execute one of the following scripts:

startas to start the application server.

stopas

to stop the application server.

Start a Client

OBE provides a convenience script to start any arbitrary client. From the


    $OBE_HOME/bin

directory, execute:

obeclient <class-name> <args>...

where

<class-name>

is the name of the main class.

Run the JUnit Tests

From the $OBE_HOME/bin directory, execute the


    runtests

command (or launch it from your native OS graphical file explorer). The script has the following syntax:

runtests [-Dtest.name=<partial-test-name>]
    [all] [standalone]
    [internal] [server]

where:

all: runs all tests
standalone: runs standalone tests (those which do not require an application server)
internal: runs internal Cactus tests
server: runs the remote client API tests
single: runs a single test (named as ${test.name})

The internal and server tests require a running application server. If the server is not already running (as determined by pinging the URL


    ${cactus.contextURL}/ServletRedirector?Cactus_Service=RUN_TEST

), the tests.xml Ant script starts the server by executing the command ${as.bin}/${as.start}. When the tests have finished the server is shut down (if it was not already running) by calling


    ${as.bin}/${as.stop}

. The test results can then be viewed at


    $OBE_HOME/tests/results/html/index.html

. Note that running the tests selects the tests configuration.