Create a new directory c:\jaspa4h2 and extract the jaspa4h2_win.zip file into this new directory.

After extracting the file you should see something like:

Figure 3.1. jaspa4h2 folder

It can be done in two different ways:

a) Copying files in System folder

Copy the files in the path c:\jaspa4h2\bin\ to your windows system directory. If your system directory is c:\windows\system32 then you will have:

b) Adding a Directory to the Path

Alternatively, you can setup the system PATH variable to point out to c:\jaspa4h2\bin. To change the system environment variables, follow these steps:

Figure 3.2. A new variable in the System Path

Open a command prompt shell and run the following command:

h2

	Depending on your firewall configuration, a confirm pop up could ask if you want to allow the connection, click Yes

Result of starting the H2 server:

In this step you are going to create a new database (myfirstjapadb) and to execute the file jaspa.sql into it to make it spatial. Open a command prompt shell and run the following command:

h2runscript -url jdbc:h2:tcp://localhost/~/myfirstjaspadb -user sa -password 123 -script c:\jaspa4h2\sql\jaspa.sql -showResults 

You can use any H2 client. We are going to use the default H2 client. Open a command prompt shell and run the following command:

h2console

An Internet browser should open, and you have to set up the connection parameters with the following values:

	The character ~ is an alias of the user directory. In Linux, it refers to the home directory. In Windows XP, it refers to C:\documents and settings\user\ In Windows Vista and Windows 7, it refers to C:\Users\user\

Figure 3.3. Connection to H2 Web Client

Once you have connected to the H2 Web Client, you should see something similar to the next screenshot.

Figure 3.4. H2 Web Client

To check that your installation was successful you can use the following SQL sentence.

SELECT jaspa_full_version(); 
--Jaspa should return something like that ->
JASPA (JAva SPAtial) For H2="0.1 RC1" JTS="1.11.0 forjaspa" GeoTools="2.7-M1" JRE="1.6.0_18"

For this step you will need root privileges.

Create a new directory /opt/jaspa4h2/ . Extract the jaspa4h2_i586.tar.gz file into this new directory.

After the extraction, you should see something like:

In a shell (with root privileges), run the following commands:

ln -s /opt/jaspa4h2/bin/shp2jaspah2 /usr/bin/shp2jaspah2 
ln -s /opt/jaspa4h2/bin/jaspah22shp /usr/bin/jaspah22shp
ln -s /opt/jaspa4h2/bin/h2 /usr/bin/h2 
ln -s /opt/jaspa4h2/bin/h2console /usr/bin/h2console 
ln -s /opt/jaspa4h2/bin/h2script /usr/bin/h2script 
ln -s /opt/jaspa4h2/bin/h2runscript /usr/bin/h2runscript 

In a shell run the following command:

h2

In this step, you are going to create a new database (myfirstjapadb) and to execute the file jaspa.sql into it to make it spatial.

In a shell run the following command:

h2runscript -url jdbc:h2:tcp://localhost/~/myfirstjaspadb -user sa -password 123 -script /opt/jaspa4h2/sql/jaspa.sql -showResults 

You can use any H2 client. We are going to use the default H2 client. Open a command prompt shell and run the following command:

h2console

An Internet browser should open, and you have to set up the connection parameters with the following values:

	The character ~ is an alias of the user directory. In Linux, it refers to the home directory. In Windows XP, it refers to C:\documents and settings\user\ In Windows Vista and Windows 7, it refers to C:\Users\user\

Figure 3.5. Connection to H2 Web Client

Once you have connected to the H2 Web Client, you should see something similar to the next screenshot.

Figure 3.6. H2 Web Client

To check that your installation was successful you can use the following SQL sentence.

SELECT jaspa_full_version(); 
--Jaspa should return something like that ->
JASPA (JAva SPAtial) For H2="0.1 RC1" JTS="1.11.0 forjaspa" GeoTools="2.7-M1" JRE="1.6.0_18" 

Create a new directory c:\jaspa4pg .

Extract the jaspa zip file into this directory, jaspa4pg8.4_win.zip (if your PostgreSQL version is 8.4) jaspa4pg8.3_win.zip (if your PostgreSQL version is 8.3).

After extract the file you should see something like:

To change the system environment variables, follow these steps:

	You must not delete or overwrite the paths that are already in the Path variable! Also, make sure you don't have an extra "\" at the end of the paths

Figure 3.8. A new variable in the System Path

Optional: if the PostgreSQL/bin path is not included in the Path variable is a good idea to include it too. For that, you have to find out where is PostgreSQL installed on your computer (e.g C:\Program Files\PostgreSQL\8.4\bin or C:\Program Files\PostgreSQL\9.0\bin)

Locate the file postgresql.conf . It is located under the directory data, on your PostgreSQL cluster installation Example: C:\Program Files\PostgreSQL\8.4\data\postgresql.conf

Open the file jaspa4pg/doc/html/pgconf-wint.txt and add its content to the end of the postgresql.conf file. Lines to be added

Stop and start the PostgreSQL server service to re-read the postgresql.conf file (Start Button / All Programs / Postgresql 8.4 / Stop Service & Start Button / All Programs / Postgresql 8.4 / Start Service)

Open a command prompt shell Run each of the following commands (the system will ask you the postgresql password):

createdb -U postgres jaspatemplate 
psql -U postgres -f C:\jaspa4pg\sql\pljavainstall.sql -d jaspatemplate 
psql -U postgres -f C:\jaspa4pg\sql\jaspa.sql -d jaspatemplate 

Now you have a jaspa template ready to create easily as many new jaspa spatial database as you want. Let's create our first jaspa spatial database called myfirstjaspadb

createdb -U postgres -T jaspatemplate myfirstjaspadb

To check everything is fine you can use the following SQL sentence. Connect to the new database using any postgresql client (psql, pgadmin3, etc.) and execute:

SELECT jaspa.jaspa_full_version(); 
--Jaspa should return something like that ->
JASPA (JAva SPAtial) For PostgreSQL="0.1 RC1" JTS="1.11.0 forjaspa" GeoTools="2.7-M1" JRE="1.6.0_18" 

For this step you will need root privileges Create a new directory /opt/jaspa4pg .

Extract to this new directory the jaspa tar file, jaspa4pg8.4_i586.tar.gz (if your PostgreSQL version is 8.4) or jaspa4pg8.3_i586.tar.gz (if your PostgreSQL version is 8.3).

After extracting the file you should see something like:

Locate the file postgresql.conf. The location of this file depends on your Linux distribution and how your PostgreSQL server is configured. For instance,

Edit the postgresql.conf file, with root privileges, by adding to the end of it the content of the file jaspa4pg/doc/html/pgconf-i586.txt. Lines to be added

Edit the file ld.so.conf , with root user privileges, located in /etc/ld.so.conf and add the following lines at the end of it.

/opt/jaspa4pg/jre/liblink
/opt/jaspa4pg/jre/liblink/client
/opt/jaspa4pg/jre/liblink/server
/opt/jaspa4pg/jre/liblink/native_threads

In a shell, run the following commands:

ldconfig 
ln -s /opt/jaspa4pg/bin/shp2jaspapg /usr/bin/shp2jaspapg
ln -s /opt/jaspa4pg/bin/jaspapg2shp /usr/bin/jaspapg2shp

With root user privileges: Stop and start the PostgreSQL server service:

Open a command prompt shell Run each of the following commands (the system will ask you the postgres password):

createdb -U postgres jaspatemplate 
psql -U postgres -f /opt/jaspa4pg/sql/pljavainstall.sql -d jaspatemplate 
psql -U postgres -f /opt/jaspa4pg/sql/jaspa.sql -d jaspatemplate 

Now you have a jaspa template ready to create easily as many new jaspa spatial database as you want. Let's create our first jaspa spatial database called myfirstjapadb.

createdb -U postgres -T jaspatemplate myfirstjaspadb

To check everything went fine you can enter into the new database using any postgresql client (psql, pgadmin3, etc.) and execute the following sentence:

SELECT jaspa_full_version(); 
--Jaspa should return something like that ->
JASPA (JAva SPAtial) For PostgreSQL="0.1 RC1" JTS="1.11.0 forjaspa" GeoTools="2.7-M1" JRE="1.6.0_18"

JASPA for PostgreSQL and for H2 stores spatial functions and metadata tables into the schema jaspa.

PostgreSQL

In PostgreSQL the schemas to look in is automatically specified in the postgresql.conf file.

H2

In H2 database you can specify the schema to look in with the connection parameter JDBC URL. For instance:

If you leave out "SCHEMA_SEARCH_PATH=PUBLIC,JASPA", you have to indicate that jaspa spatial functions are located in the schema jaspa. Example:

SELECT jaspa.ST_IsClosed(jaspa.ST_GeomFromText('LINESTRING (0 0, 10 20, 30 20,0 0)'));

or alternatively, you can set the schema_search_path parameter in each session:

SET SCHEMA_SEARCH_PATH=PUBLIC,JASPA;
SELECT ST_IsClosed(ST_GeomFromText('LINESTRING (0 0, 10 20, 30 20,0 0)'));

Use the command 'shp2jaspapg' (PostgreSQL) o 'shp2jaspah2' (H2), the same way you use 'shp2pgsql' in PostGIS. Please refer to Section 3.2, “Shp Converter” for further information.

PostgreSQL. The way to create an spatial index is slightly different: use the function ST_PGBox

create index idx_puntos_funcion on puntos using gist (ST_PGBox(geom));

The use of spatial indexes is the same in PostGIS and Jaspa4PG - select count(*) from puntos p1, puntos p2 where (p1.geom && p2.geom);

H2 does not support spatial indexes at this moment. Please refer to Section 7, “Spatial indexes” for further information.