i have downloaded the latest OpenKM4.0 and JBoss 4.2.3 bundle and attempted to set this up on a WinXP box. I have downloaded and installed the latest JDK from java and when i run the run.bat file the website starts running. When i go to http://localhost:8080/ i get a JBoss welcome screen, but when i attempt to go to http://localhost:8080/openkm i get a 404 not found error. Any ideas as to what is happening?
Because information matters
New OpenKM User
- 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.
Yes , context is case sensitive, you must write /OpenKM with capitalized characters
Amazing! Thanks for the quick reply. Anyway to change this? i haven't run into a Web Server that has been picky about case when it comes to virtual directories before? Could i move this over to tomcat?
You must not change OpenKM to openkm because in code there's some dependencies about this url.
That's understandable, I would like to use this software to point externally and would like to give my users a very clean URL to go to. I know that in other web server software configs you can specify that certain URL requests can get redirected to a different URL. I.E. let say i want to set up the URL http://DMS.domain.com/ to point to the OpenKM server. I then would use the Web service to translate http://dms.domain.com/ to http://dms.domain.com:8080/OpenKM/. Its ok if the users see this true address, i just want a nice clean URL to direct traffic to. Should i move this to the Configuration forum instead?
There're several ways to doing it.
1- Configure jboss to running on port 80 ( solves intranet and extranet ) collision with microsoft IIS !!!
2- Configure NAT in router 80 -> 8080 ( solves extranet )
3- Configure apache proxy ( solves intranet and extranet )
In linux is more easy configuring apache, in windows it'll some little more difficult.
Which do you select ?
1- Configure jboss to running on port 80 ( solves intranet and extranet ) collision with microsoft IIS !!!
2- Configure NAT in router 80 -> 8080 ( solves extranet )
3- Configure apache proxy ( solves intranet and extranet )
In linux is more easy configuring apache, in windows it'll some little more difficult.
Which do you select ?
I am going to go with option 1. I will let you know how that turns out. The machine this is running on has no conflicts with port 80.
The recommended option is "Configure apache proxy" because is the most flexible and extended one.
if you wnat to change jboss port go to
Code: Select all
and change 8080 to 80
%jboss%/server/default/deploy/jboss-web.deployer/server.xml Code: Select all
<Connector port="8080" address="${jboss.bind.address}"
maxThreads="250" maxHttpHeaderSize="8192"
emptySessionPath="true" protocol="HTTP/1.1"
enableLookups="false" redirectPort="8443" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true" />Anyway you will have problems accesing to http://your-ip:80/ because there are some JBoss services actived by default and anybody can access to them and make modifications to your JBoss installation. Bad idea if you plan to expose this JBoss installation to world-wide-web.
As says pavila, for security reasons is better installing apache proxy with jboss
Since i am using this on a Windows XP machine, I configured IIS to redirect all port 80 requests to the OpenKM logon page. So far my test machine has been working very well, I want to put this into production and go live at the end of this week but i am still struggling to get the notifications to work. Is there a good guide i could use to start me on setting this up?
Here notifications are well explained.
Before put on a production environment, ensure you're doing backup well ( with jboss stopped ). Test you backup.
Before put on a production environment, ensure you're doing backup well ( with jboss stopped ). Test you backup.
Thanks for the pointer. I had read that page before, but i hadn't updated the right fields. so my first test on this was to notify one user and that worked fine. Then i added two users, one user was an internal employee here at my company, the other was a gmail address. The notification didn't get to either users. Next i tried adding two users, both internal employees. That worked to both. Next i tried just one user, the one user was a yahoo address. That didn't go through either.
Is this in issue with JBoss, or with our Exchange server?
Also, i had the email setup to come from DMS@domain.com but it came through as administrator@domain.com. Any ideas there?
Is this in issue with JBoss, or with our Exchange server?
Also, i had the email setup to come from DMS@domain.com but it came through as administrator@domain.com. Any ideas there?
1- in mail-ds.xml enable debug mode and take a look at server.log looking for a possible error
2- The problem in could be in your exchange server, take look on both logs, some message must be showed ( error or warning while sending to this domain ). If you can send into your company domain and not to outside, I think could be a problem in the exchange account or exchange server configuration.
It'll be interesting for us how you've configured IIS to proxy OpenKM ( some little screenshots and little text it'll be great to include in our installation wiki ).
2- The problem in could be in your exchange server, take look on both logs, some message must be showed ( error or warning while sending to this domain ). If you can send into your company domain and not to outside, I think could be a problem in the exchange account or exchange server configuration.
It'll be interesting for us how you've configured IIS to proxy OpenKM ( some little screenshots and little text it'll be great to include in our installation wiki ).