Normally we install under Ubuntu server without problems.
Well, when you start jboss, there\'s some error on log ? ( server/default/log/server.log )
We\'re interested first on running under 8080 port, error 500 and must investigate why appears.
Normally we install under Ubuntu server without problems.
Well, when you start jboss, there\'s some error on log ? ( server/default/log/server.log )
We\'re interested first on running under 8080 port, error 500 and must investigate why appears.
Username and password might be okmAdmin / admin I can\'t understand why you can not login ( the capitalized A is mandatory )
It\'s a jboss problem. Try the question on a jboss forum I think you\'ll find there the solution or the origin of the problem.
To change logo ( images ) must edit OpenKM.war into OpenKM.ear ( deploy directory with jboss stoped ) and overwrite images ( it\'s easy to locate them ).
About changing okm:root name now it\'s so difficult because it\'s hard code.
You must stop jboss, edit OpenKM.ear file contents under deploy directory as I said, and then restart jboss, not editing the temporary jboss files.
If you want to report some bugs to us, you can use contact form.
Thanks for your support.
Yes, On a disaster you need to recover all repository, disaster in OpenKM is a hard disk corruption. In this case you must recover entire repository. Us we use Rsync to making backups. Since now we\'ve not found with need to recover a single file for OpenKM problem. Really deleting file needs twice ...
You\'ve got something more on this jboss ?
E:/openkm/server/default/deploy/wel.war }
Because wel.war is not a OpenKM war file ?
Well we\'re on holidays johaneques, consider be patient. About your OpenKM version you\'ve donwloaded the last community version ? if you\'ve downloaded it the login might be okmAdmin/admin It\'s a clean installation ? Take a look at log while openkm is starting to see possible problems ? Have you c...
Tomcat server is embeded on jboss you might change ports on jboss to run both. But first for testing it could be better stopping your tomcat installation and run jboss to discover if it\'s the problem.
After it, you can change jboss port, but first try to run with yur tomcat stopped.
Si los puertos estan ocupados efectivamente tienes o bien que cambiar los puertos o parar los servicios que estan ocupando estos puertos en caso de colisión con lo que esta utilizando jboss. Para modificar los puertos tienes que modificar el fichero server.xml que esta en jboss_home/server/default/d...
Yes, Signital signature is planned and studied how must be implemented. Is an enhancement studied but not yet planned when we\'ll do it.
I\'ve seen something strange in your jboss log: 15:27:15,218 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production enviro nments was not found on the java.library.path: C:\\Program Files\\Java\\jdk1.5.0\\bin;.;C:\\WINDOWS\\system32;C:\\WINDOWS;C:...
Si estas en linux, desde la consola haz un \"tail -f server.log\" para ver las trazas del servidor jboss, si estas en windows arranca el jboss desde la consola y así veras el log. Si modificas el mail-service.xml, pon el debug=on y así veras que es lo que esta pasando. Recuerda que para co...
De hecho la configuración con la que viene OpenKM es la mejor en cuanto a rendimiento, tener los ficheros en bases de datos ya hemos indicado en varios post que produce importantes perdidas de rendimiento al incrementarse el tiempo que necesita el servidor para proporcionar el fichero ( al final el ...