Automating the 52N SOS install?

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Automating the 52N SOS install?

Derek Hohls
The 52N wiki gives very clear instructions for the installation of the 52N SOS (4.3):

https://wiki.52north.org/bin/view/SensorWeb/SensorObservationServiceIVDocumentation#2_Installing_the_Webapp

The navigation and screens via the Tomcat manager are also very clear and easy to follow.

However, I would like to create an automated install via a shell script that makes use of, for example, pre-configured settings files, and does not require any user interaction (via Tomcat GUI or command-line prompts).

The reason for this is that we are deploying into a Docker.  Any code not deployed via a build process (or via script commands at container start-up) is lost when the container is re-run or rebuilt.  The other advantage of automation is that anyone else can easily run the same install to replicate exactly the same instance on their own machine.

Is there a guide anywhere on the wiki that covers this use-case?  If not, how would I go about it?

Thanks
Derek



--
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard.
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.


This message has been scanned for viruses and dangerous content by MailScanner,
and is believed to be clean.


Please consider the environment before printing this email.

_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines

Reply | Threaded
Open this post in threaded view
|

Re: Automating the 52N SOS install?

Carsten Hollmann
Hi Derek,

you can build a pre-configured 52N SOS by using the maven profiles
"configure-datasource" and "use-default-settings" defined in
SOS/webapp/pom.xml.

To skip the installation the "datasource.properties" file should be
available in the [TOMCAT_HOME]/webapps/[SOS_NAME]/WEB-INF folder of the
deployed instance. Template files of the datasource.properties can be
found in the 52N SOS sources folder SOS/misc/conf.

If the "configuration.db" file is contained in the
[TOMCAT_HOME]/webapps/[SOS_NAME] folder, the 52N SOS loads the settings
from this file during the start-up. If the file is not available the
default values defined in the code are used.

Best,
Carsten

Am 06.07.2015 um 16:02 schrieb Derek Hohls:

> The 52N wiki gives very clear instructions for the installation of the
> 52N SOS (4.3):
>
> https://wiki.52north.org/bin/view/SensorWeb/SensorObservationServiceIVDocumentation#2_Installing_the_Webapp
>
> The navigation and screens via the Tomcat manager are also very clear
> and easy to follow.
>
> However, I would like to create an automated install via a shell script
> that makes use of, for example, pre-configured settings files, and does
> not require any user interaction (via Tomcat GUI or command-line prompts).
>
> The reason for this is that we are deploying into a Docker.  Any code
> not deployed via a build process (or via script commands at
> container start-up) is lost when the container is re-run or rebuilt.
>   The other advantage of automation is that anyone else can easily run
> the same install to replicate exactly the same instance on their own
> machine.
>
> Is there a guide anywhere on the wiki that covers this use-case?  If
> not, how would I go about it?
>
> Thanks
> Derek
>
>
>
> --
> This message is subject to the CSIR's copyright terms and conditions,
> e-mail legal notice, and implemented Open Document Format (ODF) standard.
> The full disclaimer details can be found at
> http://www.csir.co.za/disclaimer.html.
>
>
> This message has been scanned for viruses and dangerous content by
> *MailScanner* <http://www.mailscanner.info/>,
> and is believed to be clean.
>
>
> Please consider the environment before printing this email.
>
>
> _______________________________________________
> SWE mailing list
> [hidden email]
> http://list.52north.org/mailman/listinfo/swe
> http://sensorweb.forum.52north.org
> Please respect our mailing list guidelines:
> http://52north.org/resources/mailing-lists-and-forums/guidelines
>

--
Carsten Hollmann

52°North Initiative for Geospatial Open Source Software GmbH
Martin-Luther-King-Weg 24
48155 Münster, Germany

E-Mail: [hidden email]
Fon: +49 (0)-251-396371-35
Fax: +49 (0)-251-396371-11
http://52north.org/
Twitter: @FiveTwoN

General Managers: Dr. Albert Remke, Dr. Andreas Wytzisk
Local Court Muenster HRB 10849
_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines
Reply | Threaded
Open this post in threaded view
|

Re: Automating the 52N SOS install?

Daniel Nüst - 52N
Am 07/07/2015 um 08:36 schrieb Carsten Hollmann:

> you can build a pre-configured 52N SOS by using the maven profiles
> "configure-datasource" and "use-default-settings" defined in
> SOS/webapp/pom.xml.
>
> To skip the installation the "datasource.properties" file should be
> available in the [TOMCAT_HOME]/webapps/[SOS_NAME]/WEB-INF folder of the
> deployed instance. Template files of the datasource.properties can be
> found in the 52N SOS sources folder SOS/misc/conf.
>
> If the "configuration.db" file is contained in the
> [TOMCAT_HOME]/webapps/[SOS_NAME] folder, the 52N SOS loads the settings
> from this file during the start-up. If the file is not available the
> default values defined in the code are used.

Just for my understanding I have... many questions:

The information in the datasource.properties is not inclcuded in the
configuration.db - right?

And to have a completely pre-configured SOS not using the default
values, you have to provide both configuration.db and a
datasource.properties file?

What is the easiest way to create the configuration.db? Is there a unit
test that Derek could run, or is the best way to install and configure
the SOS locally, and then copy and paste the configuration.db file?

How does this relate to the configuration import and export feature of
the admin DB? Could he also just put the exportet settings into
[TOMCAT_HOME]/webapps/[SOS_NAME]/WEB-INF ?


/Daniel

>
> Am 06.07.2015 um 16:02 schrieb Derek Hohls:
>> The 52N wiki gives very clear instructions for the installation of the
>> 52N SOS (4.3):
>>
>> https://wiki.52north.org/bin/view/SensorWeb/SensorObservationServiceIVDocumentation#2_Installing_the_Webapp
>>
>>
>> The navigation and screens via the Tomcat manager are also very clear
>> and easy to follow.
>>
>> However, I would like to create an automated install via a shell script
>> that makes use of, for example, pre-configured settings files, and does
>> not require any user interaction (via Tomcat GUI or command-line
>> prompts).
>>
>> The reason for this is that we are deploying into a Docker.  Any code
>> not deployed via a build process (or via script commands at
>> container start-up) is lost when the container is re-run or rebuilt.
>>   The other advantage of automation is that anyone else can easily run
>> the same install to replicate exactly the same instance on their own
>> machine.
>>
>> Is there a guide anywhere on the wiki that covers this use-case?  If
>> not, how would I go about it?
>>
>> Thanks
>> Derek
>>
>>
>>
>> --
>> This message is subject to the CSIR's copyright terms and conditions,
>> e-mail legal notice, and implemented Open Document Format (ODF) standard.
>> The full disclaimer details can be found at
>> http://www.csir.co.za/disclaimer.html.
>>
>>
>> This message has been scanned for viruses and dangerous content by
>> *MailScanner* <http://www.mailscanner.info/>,
>> and is believed to be clean.
>>
>>
>> Please consider the environment before printing this email.
>>
>>
>> _______________________________________________
>> SWE mailing list
>> [hidden email]
>> http://list.52north.org/mailman/listinfo/swe
>> http://sensorweb.forum.52north.org
>> Please respect our mailing list guidelines:
>> http://52north.org/resources/mailing-lists-and-forums/guidelines
>>
>


--
Daniel Nüst
52°North Initiative for Geospatial Open Source Software GmbH
Martin-Luther-King-Weg 24
48155 Münster, Germany
E-Mail: [hidden email]
Fon: +49-(0)-251–396371-36
Fax: +49-(0)-251–396371-11

http://52north.org/
Twitter: @FiveTwoN

General Managers: Dr. Albert Remke, Dr. Andreas Wytzisk
Local Court Muenster HRB 10849
_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines
Reply | Threaded
Open this post in threaded view
|

Re: Automating the 52N SOS install?

Carsten Hollmann
Hi Daniel,

> Just for my understanding I have... many questions:
>
> The information in the datasource.properties is not inclcuded in the
> configuration.db - right?

Yes, that's right.

> And to have a completely pre-configured SOS not using the default
> values, you have to provide both configuration.db and a
> datasource.properties file?

Yes.

> What is the easiest way to create the configuration.db? Is there a unit
> test that Derek could run, or is the best way to install and configure
> the SOS locally, and then copy and paste the configuration.db file?

The best way is to install and configure, and the copy and paste the
configuration.db file.

> How does this relate to the configuration import and export feature of
> the admin DB? Could he also just put the exportet settings into
> [TOMCAT_HOME]/webapps/[SOS_NAME]/WEB-INF ?

No, the exported settings can be imported only at the beginning of the
installation.

Best,
Carsten
_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines
Reply | Threaded
Open this post in threaded view
|

Re: Automating the 52N SOS install?

Derek Hohls
Hi Carsten

I am just coming back to this again, so I hope you don't more questions now.

As I said previously, my primary use case is for the 52N SOS to be running in a Docker container.  The key issue in such a deployment is to persist data between rebuilds/restarts.  The way to do this is to create a "mount" between internal files/directories and external ones.  So what I really need to know is which files and/or directories are relevant for the SOS (after configuration) to ensure that all changes are persisted (excluding actual database files, as these are already handled via a second container).

If I get a working method, I'd be happy to share it here for you to use (and improve) if needed.

Thanks
Derek
 

>>> Carsten Hollmann <[hidden email]> 07/08/15 8:41 AM >>>
Hi Daniel,

> Just for my understanding I have... many questions:
>
> The information in the datasource.properties is not inclcuded in the
> configuration.db - right?

Yes, that's right.

> And to have a completely pre-configured SOS not using the default
> values, you have to provide both configuration.db and a
> datasource.properties file?

Yes.

> What is the easiest way to create the configuration.db? Is there a unit
> test that Derek could run, or is the best way to install and configure
> the SOS locally, and then copy and paste the configuration.db file?

The best way is to install and configure, and the copy and paste the
configuration.db file.

> How does this relate to the configuration import and export feature of
> the admin DB? Could he also just put the exportet settings into
> [TOMCAT_HOME]/webapps/[SOS_NAME]/WEB-INF ?

No, the exported settings can be imported only at the beginning of the
installation.

Best,
Carsten
_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines

--
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard.
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.

This message has been scanned for viruses and dangerous content by MailScanner,
and is believed to be clean.

Please consider the environment before printing this email.


--
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard.
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.


This message has been scanned for viruses and dangerous content by MailScanner,
and is believed to be clean.


Please consider the environment before printing this email.

_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines

Reply | Threaded
Open this post in threaded view
|

Re: Automating the 52N SOS install?

Carsten Hollmann
Hi Derek,

> As I said previously, my primary use case is for the 52N SOS to be
> running in a Docker container.  The key issue in such a deployment is to
> persist data between rebuilds/restarts.  The way to do this is to create
> a "mount" between internal files/directories and external ones.  So what
> I really need to know is which files and/or directories are relevant for
> the SOS (after configuration) to ensure that all changes are persisted
> (excluding actual database files, as these are already handled via a
> second container).

Here are the files (with folder) that are created during installation.

The database configuration file:
[WEBAPP_NAME]\WEB-INF\datasource.properties

The configuration (Settings) file:
[WEBAPP_NAME]\configuration.db

The local SOS cache is persisted in the file [WEBAPP_NAME]\cache.tmp .
If this file is missing, the SOS creates the cache during the startup.

If you have changed the logging configuration (admin interface) and this
should be persisted, you can find the file here:
[WEBAPP_NAME]\WEB-INF\classes\logback.xml

These are the files that were created or are modifiable by the SOS.

> If I get a working method, I'd be happy to share it here for you to use
> (and improve) if needed.

That would be great. Thanks.

Best,
Carsten


> Thanks
> Derek
>
>>>> Carsten Hollmann <[hidden email]> 07/08/15 8:41 AM >>>
> Hi Daniel,
>
>  > Just for my understanding I have... many questions:
>  >
>  > The information in the datasource.properties is not inclcuded in the
>  > configuration.db - right?
>
> Yes, that's right.
>
>  > And to have a completely pre-configured SOS not using the default
>  > values, you have to provide both configuration.db and a
>  > datasource.properties file?
>
> Yes.
>
>  > What is the easiest way to create the configuration.db? Is there a unit
>  > test that Derek could run, or is the best way to install and configure
>  > the SOS locally, and then copy and paste the configuration.db file?
>
> The best way is to install and configure, and the copy and paste the
> configuration.db file.
>
>  > How does this relate to the configuration import and export feature of
>  > the admin DB? Could he also just put the exportet settings into
>  > [TOMCAT_HOME]/webapps/[SOS_NAME]/WEB-INF ?
>
> No, the exported settings can be imported only at the beginning of the
> installation.
>
> Best,
> Carsten
> _______________________________________________
> SWE mailing list
> [hidden email]
> http://list.52north.org/mailman/listinfo/swe
> http://sensorweb.forum.52north.org
> Please respect our mailing list guidelines:
> http://52north.org/resources/mailing-lists-and-forums/guidelines
>
> --
> This message is subject to the CSIR's copyright terms and conditions,
> e-mail legal notice, and implemented Open Document Format (ODF) standard.
> The full disclaimer details can be found at
> http://www.csir.co.za/disclaimer.html.
>
> This message has been scanned for viruses and dangerous content by
> MailScanner,
> and is believed to be clean.
>
> Please consider the environment before printing this email.
>
>
> --
> This message is subject to the CSIR's copyright terms and conditions,
> e-mail legal notice, and implemented Open Document Format (ODF) standard.
> The full disclaimer details can be found at
> http://www.csir.co.za/disclaimer.html.
>
>
> This message has been scanned for viruses and dangerous content by
> *MailScanner* <http://www.mailscanner.info/>,
> and is believed to be clean.
>
>
> Please consider the environment before printing this email.
>

--
Carsten Hollmann

52°North Initiative for Geospatial Open Source Software GmbH
Martin-Luther-King-Weg 24
48155 Münster, Germany

E-Mail: [hidden email]
Fon: +49 (0)-251-396371-35
Fax: +49 (0)-251-396371-11
http://52north.org/
Twitter: @FiveTwoN

General Managers: Dr. Albert Remke, Dr. Andreas Wytzisk
Local Court Muenster HRB 10849
_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines
Reply | Threaded
Open this post in threaded view
|

Re: Automating the 52N SOS install?

Javier Ruiz Aranguren
Hi, Derek:

In addition to Carsten answer, I would say that it is simpler (and more cloud oriented) to redeploy these files with each Docker provision than having a mounted container for storing those.
The only permanent data that must be preserved is the database one.

Please give us updates on your progress, we are also very interested in deploying 52North/SOS as a container.

Regards.
Reply | Threaded
Open this post in threaded view
|

Re: Automating the 52N SOS install?

AndyMuc
In reply to this post by Carsten Hollmann
Hi,

I tried your instructions (two years later), but unfortunately I am not
successful.

My goal is to have an automated deployment of a (from me) preconfigured SOS.

I use your docker images from [1] or respectively I did my own setup, which
is inspired of the docker-compose.yml located in the 52N SOS source tree
(see [3] and [4]).

I understood your approach as follows:

1) Deploy an unconfigured SOS
2) Configure SOS via WEB GUI
3) Backup the generated datasource.properties and configuration.db and throw
the deployment away
4) Build an image (see [2] and [3]) where the two files from step 3 are
copied to their respective locations
5) Run a container from that image and enjoy a configured SOS

When I follow my instruction above, I have indeed a configured SOS (Settings
are as configured in step 2). However I cannot insert any sensor (see [4]
and [5] )

Do you have help for me?

Best regards
Andreas

[1] https://hub.docker.com/r/52north/sos/
------------
[2]

FROM tomcat:8-jre8-alpine

ENV TZ=Europe/Berlin
ENV JPDA_ADDRESS=8000
ENV JPDA_TRANSPORT=dt_socket

RUN ln -snf /usr/share/zoneinfo/$TZ /etc/localtime && echo $TZ >
/etc/timezone
ADD 52n-sos-webapp.war /usr/local/tomcat/webapps/52n-sos-webapp.war
RUN mkdir /usr/local/tomcat/webapps/52n-sos-webapp && unzip
/usr/local/tomcat/webapps/52n-sos-webapp.war -d
/usr/local/tomcat/webapps/52n-sos-webapp
ADD configuration.db
/usr/local/tomcat/webapps/52n-sos-webapp/configuration.db
ADD datasource.properties
/usr/local/tomcat/webapps/52n-sos-webapp/WEB-INF/datasource.properties
ADD tomcat-index.html /usr/local/tomcat/webapps/ROOT/index.html

CMD ["catalina.sh", "jpda", "run"]

------------
[3]

version: '3'
services:
  db:
    image: mdillon/postgis:9.5
    ports:
      - 5432:5432
    environment:
      - POSTGRES_USER=postgres
      - POSTGRES_PASSWORD=mypassword
      - POSTGRES_DB=sos
    container_name: testing-db
  sos:
    build: sos/
    ports:
      - 8080:8080
      - 8000:8000
    links:
      - db:postgres
    depends_on:
      - db
    container_name: testing-sos

------------
[4]

<?xml version="1.0" encoding="UTF-8"?>
<ows:ExceptionReport xmlns:ows="http://www.opengis.net/ows/1.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="2.0.0"
xsi:schemaLocation="http://www.opengis.net/ows/1.1
http://schemas.opengis.net/ows/1.1.0/owsAll.xsd">
  <ows:Exception exceptionCode="NoApplicableCode">
    <ows:ExceptionText>Error while inserting sensor data into database!
[EXCEPTION]:
could not extract ResultSet</ows:ExceptionText>
  </ows:Exception>
</ows:ExceptionReport>

------------
[5]
testing-db | ERROR:  relation "public.proceduredescriptionformat" does not
exist at character 120
testing-db | STATEMENT:  select this_.procedureDescriptionFormatId as
procedur1_34_0_, this_.procedureDescriptionFormat as procedur2_34_0_ from
public.proceduredescriptionformat this_ where
this_.procedureDescriptionFormat=$1
testing-db | ERROR:  current transaction is aborted, commands ignored until
end of transaction block
testing-db | STATEMENT:  SELECT 1
testing-sos | 31-Aug-2017 12:27:50.700 INFO [GT authority factory disposer]
org.geotools.referencing.factory.DeferredAuthorityFactory.disposeBackingStore
Disposing class
org.geotools.referencing.factory.epsg.ThreadedHsqlEpsgFactory backing store
testing-db | ERROR:  relation "public.observableproperty" does not exist at
character 310
testing-db | STATEMENT:  select this_.observablePropertyId as
observab1_23_0_, this_.identifier as identifi2_23_0_, this_.codespace as
codespac3_23_0_, this_.name as name4_23_0_, this_.codespaceName as
codespac5_23_0_, this_.description as descript6_23_0_, this_.disabled as
disabled7_23_0_, this_.hiddenChild as hiddenCh8_23_0_ from
public.observableproperty this_
testing-db | ERROR:  current transaction is aborted, commands ignored until
end of transaction block
testing-db | STATEMENT:  SELECT 1
testing-db | ERROR:  relation "public.featureofinterest" does not exist at
character 63
[..]



--
Sent from: http://sensorweb.forum.52north.org/
_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines
Reply | Threaded
Open this post in threaded view
|

Re: Automating the 52N SOS install?

Derek Hohls
Hi Andreas

Did you check your operation settings e.g. at http://localhost:8080/sos/admin/operations  (change to your server & port)?

By default, InsertSensor & InsertObservation are turned off.


>>> AndyMuc <[hidden email]> 08/31/17 7:45 PM >>>
Hi,

I tried your instructions (two years later), but unfortunately I am not
successful.

My goal is to have an automated deployment of a (from me) preconfigured SOS.

I use your docker images from [1] or respectively I did my own setup, which
is inspired of the docker-compose.yml located in the 52N SOS source tree
(see [3] and [4]).

I understood your approach as follows:

1) Deploy an unconfigured SOS
2) Configure SOS via WEB GUI
3) Backup the generated datasource.properties and configuration.db and throw
the deployment away
4) Build an image (see [2] and [3]) where the two files from step 3 are
copied to their respective locations
5) Run a container from that image and enjoy a configured SOS

When I follow my instruction above, I have indeed a configured SOS (Settings
are as configured in step 2). However I cannot insert any sensor (see [4]
and [5] )

Do you have help for me?

Best regards
Andreas

[1] https://hub.docker.com/r/52north/sos/
------------
[2]

FROM tomcat:8-jre8-alpine

ENV TZ=Europe/Berlin
ENV JPDA_ADDRESS=8000
ENV JPDA_TRANSPORT=dt_socket

RUN ln -snf /usr/share/zoneinfo/$TZ /etc/localtime && echo $TZ >
/etc/timezone
ADD 52n-sos-webapp.war /usr/local/tomcat/webapps/52n-sos-webapp.war
RUN mkdir /usr/local/tomcat/webapps/52n-sos-webapp && unzip
/usr/local/tomcat/webapps/52n-sos-webapp.war -d
/usr/local/tomcat/webapps/52n-sos-webapp
ADD configuration.db
/usr/local/tomcat/webapps/52n-sos-webapp/configuration.db
ADD datasource.properties
/usr/local/tomcat/webapps/52n-sos-webapp/WEB-INF/datasource.properties
ADD tomcat-index.html /usr/local/tomcat/webapps/ROOT/index.html

CMD ["catalina.sh", "jpda", "run"]

------------
[3]

version: '3'
services:
db:
image: mdillon/postgis:9.5
ports:
- 5432:5432
environment:
- POSTGRES_USER=postgres
- POSTGRES_PASSWORD=mypassword
- POSTGRES_DB=sos
container_name: testing-db
sos:
build: sos/
ports:
- 8080:8080
- 8000:8000
links:
- db:postgres
depends_on:
- db
container_name: testing-sos

------------
[4]

<?xml version="1.0" encoding="UTF-8"?>
<ows:ExceptionReport xmlns:ows="http://www.opengis.net/ows/1.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="2.0.0"
xsi:schemaLocation="http://www.opengis.net/ows/1.1
http://schemas.opengis.net/ows/1.1.0/owsAll.xsd">
<ows:Exception exceptionCode="NoApplicableCode">
<ows:ExceptionText>Error while inserting sensor data into database!
[EXCEPTION]:
could not extract ResultSet</ows:ExceptionText>
</ows:Exception>
</ows:ExceptionReport>

------------
[5]
testing-db | ERROR: relation "public.proceduredescriptionformat" does not
exist at character 120
testing-db | STATEMENT: select this_.procedureDescriptionFormatId as
procedur1_34_0_, this_.procedureDescriptionFormat as procedur2_34_0_ from
public.proceduredescriptionformat this_ where
this_.procedureDescriptionFormat=$1
testing-db | ERROR: current transaction is aborted, commands ignored until
end of transaction block
testing-db | STATEMENT: SELECT 1
testing-sos | 31-Aug-2017 12:27:50.700 INFO [GT authority factory disposer]
org.geotools.referencing.factory.DeferredAuthorityFactory.disposeBackingStore
Disposing class
org.geotools.referencing.factory.epsg.ThreadedHsqlEpsgFactory backing store
testing-db | ERROR: relation "public.observableproperty" does not exist at
character 310
testing-db | STATEMENT: select this_.observablePropertyId as
observab1_23_0_, this_.identifier as identifi2_23_0_, this_.codespace as
codespac3_23_0_, this_.name as name4_23_0_, this_.codespaceName as
codespac5_23_0_, this_.description as descript6_23_0_, this_.disabled as
disabled7_23_0_, this_.hiddenChild as hiddenCh8_23_0_ from
public.observableproperty this_
testing-db | ERROR: current transaction is aborted, commands ignored until
end of transaction block
testing-db | STATEMENT: SELECT 1
testing-db | ERROR: relation "public.featureofinterest" does not exist at
character 63
[..]



--
Sent from: http://sensorweb.forum.52north.org/
_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines


This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard.
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.

Please consider the environment before printing this email.
_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines