Hi Michael,
Good to hear it worked. Issues can be logged at https://github.com/geonetwork/core-geonetwork/issues.
Cheers,
Aaron.
-----Original Message-----
From: Michael Schulz [mailto:mandschulz@anonymised.com]
Sent: Monday, 17 August 2015 7:00 PM
To: geonetwork-users@lists.sourceforge.net
Subject: Re: [GeoNetwork-users] GN3 JNDI Postgis configuration
Hi Aaron,
thanks a lot, that obviously did the trick. I'll continue now to try and migrate our existing 2.10 db. This first success was on an empty db, but is very promising.
Not sure, but should I file this as an issue/bug somewhere?
Cheers, Michael
2015-08-15 15:35 GMT+02:00 Michael Schulz <mandschulz@anonymised.com>:
Hi Aaron,
thanks a lot for your answer, I'll try your suggestions... actually
the one thing I didn't do so far is adding the additional bean in
jndi-postgis-datasource.xml.
Cheers, Michael
2015-08-15 8:19 GMT+02:00 Aaron Sedgmen <Aaron.Sedgmen@anonymised.com>:
Hi Michael,
I came up against the same problem and got it to work with the
following
steps:
Ensure you have a jndi resource configuration in the servlet
container connecting to your postgres/postgis database (looks like you have this).
Uncomment the import statement for jndi-postgis-datasource in
WEB-INF/config-node/srv.xml, commenting out the import that was
previously uncommented (looks like you've done this).
In the WEB-INF/config-db/jndi-postgres-postgis.xml file, add the
following bean configuration (I put it immediately before the jdbcDataSource bean):
<bean id="jpaVendorAdapterDatabaseParam" class="java.lang.String">
<constructor-arg value="POSTGRESQL"/>
</bean>
Again in the WEB-INF/config-db/jndi-postgres-postgis.xml file, append
the resource name as defined in the jndi resource configuration (in
my case
jdbc/geonetwork3) to the value of the jndiName in the jdbcDataSource
bean
configuration:
<property name="jndiName" value="java:/comp/env"/>
becomes
<property name="jndiName"
value="java:/comp/env/jdbc/geonetwork3"/>
I didn't configure anything in the jdbc.properties file, as the jndi
resource on the servlet container should handle all the db connection
stuff.
With GN 2.10.x you had to define some connection details in GN's DB
configuration file when using a jndi data source as I believe this
was required by the geotools libraries used in certain GN functions.
This may be the case too with GN 3, which could require db settings
in jdbc.properties, although I'm yet to come across any issues. Pity
if it is the case as it kind of defeats the purpose of using a jndi
data source.
Hope this is of some help.
Cheers,
Aaron.
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/GN3-JNDI-Postgis-configuration-tp
5219324p5219847.html Sent from the GeoNetwork users mailing list
archive at Nabble.com.
---------------------------------------------------------------------
--------- _______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork
--
-----------------------------------------------------------
Michael Schulz
Johann-Sebastian-Bach-Str. 32
79104 Freiburg
--
-----------------------------------------------------------
Michael Schulz
Johann-Sebastian-Bach-Str. 32
79104 Freiburg
------------------------------------------------------------------------------
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
Geoscience Australia Disclaimer: This e-mail (and files transmitted with it) is intended only for the person or entity to which it is addressed. If you are not the intended recipient, then you have received this e-mail by mistake and any use, dissemination, forwarding, printing or copying of this e-mail and its file attachments is prohibited. The security of emails transmitted cannot be guaranteed; by forwarding or replying to this email, you acknowledge and accept these risks.
-------------------------------------------------------------------------------------------------------------------------
Hi, maybe create a dedicated section on the new doc
https://github.com/geonetwork/doc/blob/develop/en/maintainer-guide/installing/configuring-database.rst
?
Contributions are welcomed.
Thanks.
Francois
2015-08-18 1:47 GMT+02:00 <Aaron.Sedgmen@anonymised.com>:
Hi Michael,
Good to hear it worked. Issues can be logged at
https://github.com/geonetwork/core-geonetwork/issues.
Cheers,
Aaron.
-----Original Message-----
From: Michael Schulz [mailto:mandschulz@anonymised.com]
Sent: Monday, 17 August 2015 7:00 PM
To: geonetwork-users@lists.sourceforge.net
Subject: Re: [GeoNetwork-users] GN3 JNDI Postgis configuration
Hi Aaron,
thanks a lot, that obviously did the trick. I'll continue now to try and
migrate our existing 2.10 db. This first success was on an empty db, but is
very promising.
Not sure, but should I file this as an issue/bug somewhere?
Cheers, Michael
2015-08-15 15:35 GMT+02:00 Michael Schulz <mandschulz@anonymised.com>:
> Hi Aaron,
>
> thanks a lot for your answer, I'll try your suggestions... actually
> the one thing I didn't do so far is adding the additional bean in
> jndi-postgis-datasource.xml.
>
> Cheers, Michael
>
>
> 2015-08-15 8:19 GMT+02:00 Aaron Sedgmen <Aaron.Sedgmen@anonymised.com>:
>
>> Hi Michael,
>>
>> I came up against the same problem and got it to work with the
>> following
>> steps:
>>
>> Ensure you have a jndi resource configuration in the servlet
>> container connecting to your postgres/postgis database (looks like you
have this).
>>
>> Uncomment the import statement for jndi-postgis-datasource in
>> WEB-INF/config-node/srv.xml, commenting out the import that was
>> previously uncommented (looks like you've done this).
>>
>> In the WEB-INF/config-db/jndi-postgres-postgis.xml file, add the
>> following bean configuration (I put it immediately before the
jdbcDataSource bean):
>>
>> <bean id="jpaVendorAdapterDatabaseParam" class="java.lang.String">
>> <constructor-arg value="POSTGRESQL"/>
>> </bean>
>>
>> Again in the WEB-INF/config-db/jndi-postgres-postgis.xml file, append
>> the resource name as defined in the jndi resource configuration (in
>> my case
>> jdbc/geonetwork3) to the value of the jndiName in the jdbcDataSource
>> bean
>> configuration:
>>
>> <property name="jndiName" value="java:/comp/env"/>
>>
>> becomes
>>
>> <property name="jndiName"
>> value="java:/comp/env/jdbc/geonetwork3"/>
>>
>> I didn't configure anything in the jdbc.properties file, as the jndi
>> resource on the servlet container should handle all the db connection
>> stuff.
>> With GN 2.10.x you had to define some connection details in GN's DB
>> configuration file when using a jndi data source as I believe this
>> was required by the geotools libraries used in certain GN functions.
>> This may be the case too with GN 3, which could require db settings
>> in jdbc.properties, although I'm yet to come across any issues. Pity
>> if it is the case as it kind of defeats the purpose of using a jndi
>> data source.
>>
>> Hope this is of some help.
>>
>> Cheers,
>>
>> Aaron.
>>
>>
>>
>> --
>> View this message in context:
>> http://osgeo-org.1560.x6.nabble.com/GN3-JNDI-Postgis-configuration-tp
>> 5219324p5219847.html Sent from the GeoNetwork users mailing list
>> archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> --------- _______________________________________________
>> GeoNetwork-users mailing list
>> GeoNetwork-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geonetwork-users
>> GeoNetwork OpenSource is maintained at
>> http://sourceforge.net/projects/geonetwork
>>
>
>
>
> --
> -----------------------------------------------------------
> Michael Schulz
>
> Johann-Sebastian-Bach-Str. 32
> 79104 Freiburg
>
>
--
-----------------------------------------------------------
Michael Schulz
Johann-Sebastian-Bach-Str. 32
79104 Freiburg
------------------------------------------------------------------------------
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork
Geoscience Australia Disclaimer: This e-mail (and files transmitted with
it) is intended only for the person or entity to which it is addressed. If
you are not the intended recipient, then you have received this e-mail by
mistake and any use, dissemination, forwarding, printing or copying of this
e-mail and its file attachments is prohibited. The security of emails
transmitted cannot be guaranteed; by forwarding or replying to this email,
you acknowledge and accept these risks.
-------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork