• OpenKM.jar not generated

  • OpenKM has many interesting features, but requires some configuration process to show its full potential.
OpenKM has many interesting features, but requires some configuration process to show its full potential.
Forum rules: Please, before asking something see the documentation wiki or use the search feature of the forum. And remember we don't have a crystal ball or mental readers, so if you post about an issue tell us which OpenKM are you using and also the browser and operating system version. For more info read How to Report Bugs Effectively.
 #2008  by neil
 
Hi All,

When I am trying to Setup development environment for OpenKM I have followed all the steps defined on online manual but while creating OpenKM.ear folder to JBoss deployment folder it does not contain OpenKM.jar :( .
Is there anything more that I need to be done to solve this?
Error I am getting while running server is :

\"15:44:24,593 INFO [Server] Server Home Dir: F:\\OpenKM-3.0_JBoss-4.2.2.GA\\server
\\default
15:44:24,593 INFO [Server] Server Home URL: file:/F:/OpenKM-3.0_JBoss-4.2.2.GA/
server/default/
15:44:24,593 INFO [Server] Server Log Dir: F:\\OpenKM-3.0_JBoss-4.2.2.GA\\server\\
default\\log
15:44:24,593 INFO [Server] Server Temp Dir: F:\\OpenKM-3.0_JBoss-4.2.2.GA\\server
\\default\\tmp
15:44:24,593 INFO [Server] Root Deployment Filename: jboss-service.xml
15:44:25,890 INFO [ServerInfo] Java version: 1.5.0_17,Sun Microsystems Inc.
15:44:25,890 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_17-b04
,Sun Microsystems Inc.
15:44:25,890 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
15:44:28,203 INFO [Server] Core system initialized
15:44:37,203 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083
/
15:44:37,203 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour
ce:jboss-log4j.xml
15:44:38,765 INFO [TransactionManagerService] JBossTS Transaction Service (JTA
version) - JBoss Inc.
15:44:38,765 INFO [TransactionManagerService] Setting up property manager MBean
and JMX layer
15:44:39,375 INFO [TransactionManagerService] Starting recovery manager
15:44:39,593 INFO [TransactionManagerService] Recovery manager started
15:44:39,593 INFO [TransactionManagerService] Binding TransactionManager JNDI R
eference
15:44:50,921 INFO [EJB3Deployer] Starting java:comp multiplexer
15:44:53,031 INFO [STDOUT] no object for null
15:44:53,109 INFO [STDOUT] no object for null
15:44:53,171 INFO [STDOUT] no object for null
15:44:53,203 INFO [STDOUT] no object for {urn:jboss:bean-deployer}supplyType
15:44:53,234 INFO [STDOUT] no object for {urn:jboss:bean-deployer}dependsType
15:44:59,046 INFO [NativeServerConfig] JBoss Web Services - Native
15:44:59,046 INFO [NativeServerConfig] jbossws-native-2.0.1.SP2 (build=20071021
0837)
15:45:03,421 INFO [Embedded] Catalina naming disabled
15:45:04,625 INFO [AprLifecycleListener] The Apache Tomcat Native library which
allows optimal performance in production environments was not found on the java
.library.path: E:\\Java\\jdk1.5.0_17\\bin;.;C:\\WINDOWS\\system32;C:\\WINDOWS;C:\\WINDO
WS\\system32;C:\\WINDOWS;C:\\WINDOWS\\System32\\Wbem;E:\\Java\\jdk1.5.0_17\\bin;F:\\apach
e-ant-1.7.1\\bin;C:\\Program Files\\CVSNT\\
15:45:04,796 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0
.1-8080
15:45:04,843 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-80
09
15:45:04,843 INFO [Catalina] Initialization processed in 1419 ms
15:45:04,843 INFO [StandardService] Starting service jboss.web
15:45:04,843 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA
15:45:05,046 INFO [Catalina] Server startup in 206 ms
15:45:05,625 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-w
eb.deployer/ROOT.war/
15:45:08,656 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/
http-invoker.sar/invoker.war/
15:45:09,218 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../deploy/
jbossws.sar/jbossws-context.war/
15:45:09,515 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../
deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
15:45:12,156 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../dep
loy/management/console-mgr.sar/web-console.war/
15:45:13,656 INFO [MailService] Mail Service bound to java:/mail/OpenKM
15:45:14,015 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jboss-ha-local-jdbc.rar
15:45:14,093 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jboss-ha-xa-jdbc.rar
15:45:14,203 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jboss-local-jdbc.rar
15:45:14,312 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jboss-xa-jdbc.rar
15:45:14,453 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/jms/jms-ra.rar
15:45:14,546 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/mail-ra.rar
15:45:14,640 INFO [RARDeployment] Required license terms exist, view META-INF/r
a.xml in .../deploy/quartz-ra.rar
15:45:14,656 INFO [QuartzResourceAdapter] start quartz!!!
15:45:14,796 INFO [SimpleThreadPool] Job execution threads will use class loade
r of thread: main
15:45:14,843 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
15:45:14,843 INFO [RAMJobStore] RAMJobStore initialized.
15:45:14,859 INFO [StdSchedulerFactory] Quartz scheduler \'DefaultQuartzSchedule
r\' initialized from default resource file in Quartz package: \'quartz.properties\'

15:45:14,859 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
15:45:14,859 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUS
TERED started.
15:45:16,921 INFO [ConnectionFactoryBindingService] Bound ConnectionManager \'jb
oss.jca:service=DataSourceBinding,name=DefaultDS\' to JNDI name \'java:DefaultDS\'
15:45:17,921 INFO [A] Bound to JNDI name: queue/A
15:45:17,937 INFO Bound to JNDI name: queue/B
15:45:17,937 INFO [C] Bound to JNDI name: queue/C
15:45:17,937 INFO [D] Bound to JNDI name: queue/D
15:45:17,953 INFO [ex] Bound to JNDI name: queue/ex
15:45:17,984 INFO [testTopic] Bound to JNDI name: topic/testTopic
15:45:17,984 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
15:45:18,000 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic

15:45:18,000 INFO [testQueue] Bound to JNDI name: queue/testQueue
15:45:18,109 INFO [UILServerILService] JBossMQ UIL service available at : /127.
0.0.1:8093
15:45:18,218 INFO [DLQ] Bound to JNDI name: queue/DLQ
15:45:18,828 INFO [ConnectionFactoryBindingService] Bound ConnectionManager \'jb
oss.jca:service=ConnectionFactoryBinding,name=JmsXA\' to JNDI name \'java:JmsXA\'
15:45:19,593 INFO [ConnectionFactoryBindingService] Bound ConnectionManager \'jb
oss.jca:service=DataSourceBinding,name=OKMActivityDS\' to JNDI name \'java:OKMActi
vityDS\'
15:45:19,718 INFO [ConnectionFactoryBindingService] Bound ConnectionManager \'jb
oss.jca:service=DataSourceBinding,name=OKMAuthDS\' to JNDI name \'java:OKMAuthDS\'
15:45:19,781 INFO [ConnectionFactoryBindingService] Bound ConnectionManager \'jb
oss.jca:service=DataSourceBinding,name=OKMDashboardStatsDS\' to JNDI name \'java:O
KMDashboardStatsDS\'
15:45:19,859 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../dep
loy/jmx-console.war/
15:45:24,265 INFO [EARDeployer] Init J2EE application: file:/F:/OpenKM-3.0_JBos
s-4.2.2.GA/server/default/deploy/OpenKM.ear
15:45:35,031 ERROR [MainDeployer] Could not initialise deployment: file:/F:/Open
KM-3.0_JBoss-4.2.2.GA/server/default/deploy/OpenKM.ear
org.jboss.deployment.DeploymentException: Failed to find module file: OpenKM.jar

at org.jboss.deployment.EARDeployer.init(EARDeployer.java:295)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:872)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
tScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
canner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(A
bstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
upport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
eanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Thread.java:595)
15:45:35,046 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

--- Incompletely deployed packages ---
org.jboss.deployment.DeploymentInfo@b4696d8b { url=file:/F:/OpenKM-3.0_JBoss-4.2
.2.GA/server/default/deploy/OpenKM.ear }
deployer: org.jboss.deployment.EARDeployer@5cc942
status: null
state: FAILED
watch: file:/F:/OpenKM-3.0_JBoss-4.2.2.GA/server/default/deploy/OpenKM.ear
altDD: null
lastDeployed: 1233051335031
lastModified: 1233051324265
mbeans:


15:45:35,359 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8
080
15:45:35,421 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
15:45:35,562 INFO [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBos
s_4_2_2_GA date=200710221139)] Started in 1m:10s:953ms
15:56:51,609 INFO [Server] Runtime shutdown hook called, forceHalt: true
15:56:51,609 INFO [Server] JBoss SHUTDOWN: Undeploying all packages
15:56:51,609 INFO [TomcatDeployer] undeploy, ctxPath=/jmx-console, warUrl=.../d
eploy/jmx-console.war/
15:56:51,750 INFO [ConnectionFactoryBindingService] Unbound ConnectionManager \'
jboss.jca:service=DataSourceBinding,name=OKMDashboardStatsDS\' from JNDI name \'ja
va:OKMDashboardStatsDS\'
15:56:52,046 INFO [HypersonicDatabase] Database standalone closed clean
15:56:52,046 INFO [ConnectionFactoryBindingService] Unbound ConnectionManager \'
jboss.jca:service=DataSourceBinding,name=OKMAuthDS\' from JNDI name \'java:OKMAuth
DS\'
15:56:52,546 INFO [HypersonicDatabase] Database standalone closed clean
15:56:52,546 INFO [ConnectionFactoryBindingService] Unbound ConnectionManager \'
jboss.jca:service=DataSourceBinding,name=OKMActivityDS\' from JNDI name \'java:OKM
ActivityDS\'
15:56:53,718 INFO [HypersonicDatabase] Database standalone closed clean
15:56:53,765 INFO [ConnectionFactoryBindingService] Unbound ConnectionManager \'
jboss.jca:service=ConnectionFactoryBinding,name=JmsXA\' from JNDI name \'java:JmsX
A\'
15:56:53,796 INFO [testTopic] Unbinding JNDI name: topic/testTopic
15:56:53,796 INFO [securedTopic] Unbinding JNDI name: topic/securedTopic
15:56:53,796 INFO [testDurableTopic] Unbinding JNDI name: topic/testDurableTopi
c
15:56:53,796 INFO [testQueue] Unbinding JNDI name: queue/testQueue
15:56:53,812 INFO [A] Unbinding JNDI name: queue/A
15:56:53,812 INFO Unbinding JNDI name: queue/B
15:56:53,828 INFO [C] Unbinding JNDI name: queue/C
15:56:53,828 INFO [D] Unbinding JNDI name: queue/D
15:56:53,828 INFO [ex] Unbinding JNDI name: queue/ex
15:56:53,906 INFO [DLQ] Unbinding JNDI name: queue/DLQ
15:56:53,906 INFO [ConnectionFactoryBindingService] Unbound ConnectionManager \'
jboss.jca:service=DataSourceBinding,name=DefaultDS\' from JNDI name \'java:Default
DS\'
15:56:55,203 INFO [HypersonicDatabase] Database standalone closed clean
15:56:55,234 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUS
TERED shutting down.
15:56:55,234 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUS
TERED paused.
15:56:55,234 INFO [SimpleThreadPool] There are still 29 worker threads active.
See javadoc runInThread(Runnable) for a possible explanation
15:56:55,234 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUS
TERED shutdown complete.
15:56:55,484 INFO [MailService] Mail service \'java:/mail/OpenKM\' removed from J
NDI
15:56:55,484 INFO [TomcatDeployer] undeploy, ctxPath=/web-console, warUrl=.../d
eploy/management/console-mgr.sar/web-console.war/
15:56:55,687 INFO [Http11Protocol] Pausing Coyote HTTP/1.1 on http-127.0.0.1-80
80
15:56:55,703 INFO [AjpProtocol] Pausing Coyote AJP/1.3 on ajp-127.0.0.1-8009
15:56:56,703 INFO [StandardService] Stopping service jboss.web
15:56:56,734 INFO [Http11Protocol] Stopping Coyote HTTP/1.1 on http-127.0.0.1-8
080
15:56:56,781 INFO [AjpProtocol] Stopping Coyote AJP/1.3 on ajp-127.0.0.1-8009
15:56:56,843 INFO [TomcatDeployer] undeploy, ctxPath=/, warUrl=.../deploy/jboss
-web.deployer/ROOT.war/
15:56:56,843 INFO [TomcatDeployer] undeploy, ctxPath=/invoker, warUrl=.../deplo
y/http-invoker.sar/invoker.war/
15:56:56,843 INFO [TomcatDeployer] undeploy, ctxPath=/jbossws, warUrl=.../deplo
y/jbossws.sar/jbossws-context.war/
15:56:56,859 INFO [TomcatDeployer] undeploy, ctxPath=/jbossmq-httpil, warUrl=..
./deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
15:56:57,484 INFO [EARDeployer] Undeploying J2EE application, destroy step: fil
e:/F:/OpenKM-3.0_JBoss-4.2.2.GA/server/default/deploy/OpenKM.ear
15:56:57,484 INFO [EARDeployer] Undeployed J2EE application: file:/F:/OpenKM-3.
0_JBoss-4.2.2.GA/server/default/deploy/OpenKM.ear
15:56:57,921 INFO [TransactionManagerService] Stopping recovery manager
15:57:01,734 INFO [Server] Shutdown complete\"


Please help me ASAP

Regards
Neil M
 #2009  by jllort
 
1- on tab go to \"project archives\"
2- There\'s the openkm packaging ( can you see there OpenKM.jar ?)
3- Right click on OpenKM.jar and \"build archive full\" , you can do to OpenKM.war too
4- open your openkm.ear and take a look it.

Which ide are you using ? Eclipse Europa + jboss tools ( which version ? )
 #2010  by neil
 
Hi jollort,

FINALLY I am able to create OpenKM.ear Successfully.Thanks Alot :) .

Now tell me one thing If I want to make any changes to the java code for application behaviour not for application look do i need to follow the same process of creating OpenKM.ear folder again? and if not what is the procedure for this?Please let me know as soon as possible.

Regards
Neil M
 #2011  by jllort
 
AS you see on developer guide, I suggest other configuration for developement, really not creating OpenKM.ear file on eclipse workspace, setting OpenKM.ear as exploded folder directly to your deploy jboss file system and OpenKM.war exploded to OpenKM.ear

With this configuration, changes on your class files are automatically setting under deploy/OpenKM.ear ( jboss server ) and is not needed to made constants redeploying.

Other useful thing is changing gwt.xml files ( uncomment gecko -> then gwt only compile to firefox and compilation time is lower )

Normally you must not execute \"build OpenKM.ear or OpenKM.war\" any changes on your code makes in regenerating OpenKM.ear file ( normally configured refreshing each 5 seconds ), for it it\'s better setting exploded configuration, because during regeneration OpenKM.ear file ( build all ) eclipse blocked ( as you\'ve seen first time compilation could need 1-2 minutes to finishing con a normal computer ).

Sometimes when you change a bean, etc... you\'ll need to restarting jboss server, but are few cases.
 #2012  by neil
 
Hi Jillort,

If I am making any changes in code for application behavior, right now I am creating whole .ear file again and follow the whole process of exploding.So as you have mentioned in previous post can you tell me exact procedure for generating class files?

and one more thing If I want to make any changes in OpenKM interface where to find that code?
what is GWT shell? when it is required?Can you please brief me on that?And I am also planning to start another thread on the same issue?

Regards
Neil M
 #2015  by jllort
 
If you\'ve got \"project/ build automatically enabled\" ( eclipse main menus ), classes are compiled automatically.

UI is divided on two packages:
front -> es.git.openkm.frontend ( entrypoint at Main.java class )
administration -> es.git.openkm.backend ( entrypoint at Main.java class )

I not usually use GWT shell, normally I compile gwt ( run.sh or run.bat), at it\'s automatically deployed - copied - to jboss. ( I use shell only on to problematic errors, you must use as a browser, jboss must be running, to run shell simply go to run button / Open run dialog and select the \"GWT - OpenKM ( jboss )\" option), but as I said you normally don\'t need it, if more slower for developing. I suggest simply compile GWT and try with firefox ( remember to enable compilation only for gecko on Main.gwt.xml file)

About Us

OpenKM is part of the management software. A management software is a program that facilitates the accomplishment of administrative tasks. OpenKM is a document management system that allows you to manage business content and workflow in a more efficient way. Document managers guarantee data protection by establishing information security for business content.