I have been able to get a 2.0.1 install running with jetty and McKoi by
install 2.0.0 with jetty and McKoi.
install 2.0.1 with jetty and McKoi onto the same directory (overwriting files).
2.0.0 gets McKoi setup properly, 2.0.1 will leave McKoi alone if it exists but installs the other things.
This method works on FC4 and on FC3
pgrzeszc@anonymised.com wrote:
I've been poking around to find out what's going on with the install, but can't seem to find the crux of the problem.
This time I'm using Linux FC3 with java 1.4.2_10, Tomcat 5.5.12 and Oracle 10g.
Geonetwork webapp installs, but I cannot log in and the sample metadata does not show up. No matter what I do, the database connection does not work.
I did copy the appropriate driver - ojdbc14.jar - into WEB-INF/lib.
config.xml file seems to have the wrong settings set by the install program. Even though I checked the Oracle radio button during install, the McKoi section is enabled and customized with the Oracle settings like this:
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
<!-- mckoi standalone -->
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --><resource enabled="true">
<name>main-db</name>
<provider>jeeves.resources.dbms.DbmsPool</provider>
<config>
<user>[username]</user>
<password>[passwd]</password>
<driver>oracle.jdbc.driver.OracleDriver</driver>
<url>jdbc:oracle:thin:@someserver.uwindsor.ca:1521:orcl</url>
should not this line be
<url>jdbc:oracle:thin:@someserver.uwindsor.ca:1521/orcl</url>
from oracle.com
For the JDBC Thin Driver, or Server-side Thin Driver:
ods.setURL("jdbc:oracle:thin:@<database>");
where <database> is either a string of the form
//<host>:<port>/<service_name>, or a SQL*net name-value pair.
your log below indicated that the Oracle driver is being used but is not connecting to the SID. That hints to the url error above.
<poolSize>4</poolSize>
</config>
<activator class="org.fao.geonet.activators.McKoiActivator">
<configFile>WEB-INF/db/db.conf</configFile>
</activator>
</resource>
I think that the oracle section should be enabled instead, so I edited it - looks the same as above, but removed the mckoiactivator. I suppose the first section is treated as an oracle section because what matters is the values filled in, but the McKoiActivator should not be there for sure if I'm using Oracle.
Make sure that only one resource named main-db is enabled.
The Activator element looks to me to be McKoi specific and would not be needed for other drivers.
Interestingly, the install program populates the database no problem.
I don't think it's a network communication problem because I've got all these on one machine. Also, disabling firewall did not help.
<snip>
C.