Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [stellation-res] Firebird installation on Windows

> -----Original Message-----
> From: stellation-res-admin@xxxxxxxxxxxxxxx
> [mailto:stellation-res-admin@xxxxxxxxxxxxxxx]On Behalf Of Jim Wright -
> IBM Research
> Sent: Thursday, April 24, 2003 2:45 PM
> To: stellation-res@xxxxxxxxxxxxxxx
> Subject: Re: [stellation-res] Firebird installation on Windows
>
>
> At 06:57 PM 4/21/2003, Jonathan Gossage wrote:
> >Once everything is installed, use either command line tools or
> ibaccess to
> >add whatever users you need. You get the master user called sysdba with a
> >password of masterkey for free as part of the installation. Then
> create the
> >Stellation database, either with ibaccess or using the technique
> used in the
> >merge tests build.xml. Once this is done you are ready to go.
> >
> >All of this is from memory so I hope there are no omissions.
>
> Jonathan,
>
> I've got Firebird running and have created a test database (and added a
> user 'stellation'),
> but I'm not clear on the specific details needed to access the
> Firebird db
> via Stellation.
>
> Could you give me the Firebird equivalent for the following
> PostgreSQL test
> script?
> (This is taken from "Building and Installing the Stellation Core
> Components" on
> our web site).
>
> PostgreSQL Test for Remote Mode =======================================
>
> [1] $ createdb tsvctest
> [2] $ tsvcadmin --location postgresql:tsvctest [--username stelUsername]
> --password stelPassword init
> [3] $ tsvcserver --database=postgresql:tsvctest --debug=1 --port=6060
> --log=$HOME/s.log &
>        # run server in background
> [4] $ cd test
> [5] $ ant -Drdbm=postgresql -Dmode=remote [-Dusername=stelUsername]
> -Dpassword=stelPassword [-Ddbusername=dbUsername]
> [-Ddbpassword=dbPassword]
>      # .... wait for tests to conclude
> [6] $ fg  # move server process to foreground
> [7]       # kill the server by typing control-C
> [8] $ dropdb tsvctest
>
> Firebird Test for Remote Mode =========================================
>
> ?????
>
> Firebird Test for Local Mode ===========================================
>
> ?????
>
> Thanks!
>
> Jim
>
OK, here's the drill.

1. Make sure the third party jars and the JDBC driver Jars are installed in
${user.home}/stellation/lib.

2. Copy org.eclipse.stellation.core/stellation.properties to
${user.home}/stellation. This is a properties file that is used with the
build script. You probably will not need to change the working copy.

3. Copy org.eclipse.stellation.core/test/stellation.test.properties to
${user.home}/stellation. Edit it as required to specify the database
parameters. This property file is used with the test script. Note that it
has been designed to support testing against multiple databases, but the
support for this in the scripts is not complete yet. You will definitely
need to edit this file. Incidentally this file determines whether you test a
local or remote server.

4. Run the following script to build Stellation.
   cd org.eclipse.stellation.core
   ant -f build-core.xml clean-build clean-install build install-client
install-server

This will build testing and release installations of Stellation server and
the command line client. The test stuff goes in
org.eclipse.stellation.core/build and the production stuff goes in
%SystemDrive%\Program Files\Stellation.

5. Make sure that %SystemDrive%\Program Files\Stellation\bin is in the PTH
environment variable.

6. Run the following script to test Stellation.
   cd org.eclipse.stellation.core\test
   ant

The results will grind out.

Regards

Jonathan




Back to the top