nal wrote:
openbd works on myipaddress:8180/openbd

So far so good ... curious why 8180 and not the typical 8080. Doesn't matter, just wondered.

I need to have it working on mywebsite.com/ (not on a subfolder and a
funny port number)

Certainly.

Looking at this forum I tried to connect apache to tomcat but forgot
the idea after 2 nights with only trouble. Plesk control pannel has
its own apache config file all over the place and could not get it to
work.

Not having experience with Plesk unfortunately I can't help with that, but if you have direct access to the Apache config files this is really quite simple, particularly if you use mod_proxy. Sounds like it might not be worth the effort if Plesk is getting in your way that much though.

1) Can I just use tomcat as the server?

Absolutely--all you need to do is change the port Tomcat runs on from 8180 (or 8080 which would be the norm) to 80. Info here:
http://www.coreservlets.com/Apache-Tomcat-Tutorial/detailed-configuration.html#Change-Port

Just pay attention that you're changing the port for the HTTP/1.1 protocol since there are other connectors in the server.xml config file.

I though so but how do I turn myipadress:8180/openbd into mydomain.com
Do you have a real example for this in the server.xml file from
tomcat?

OK, so at this point with that change in your Tomcat server.xml you would have things running on port 80, but you'd still have the context path to contend with. This is easily solved again in the config file by setting up virtual hosts.

Honestly I've been using mod_proxy on my VPS so I'm by no means an expert on virtual hosting with Tomcat, but this looks like good information:
http://ex-parrot.com/~pete/tomcat-vhost.html

Basically you're just giving an alias (e.g. mysite.myserver.com) to a context path on Tomcat (e.g. myserver.com/mycontextpath) and it should do the rest.

I've been meaning to mess around with that anyway (eventually probably going to remove Apache from my VPS setup and just use either Tomcat or Jetty), so I'll try to get some time in the next day or so to dig in.

2) I tried using the jetty-openbd package too but it fails too. Jetty
starts on port 8080 but the example file dump.cfm cannot be found on
myipaddress:8080/dump.cfm (jetty 404 error)

Hmm ... that's odd. Not sure I have ideas on that one since I've run the Jetty build on several test machines without any problems. If you get the 404 error message from Jetty itself then that means Jetty's running of course. Maybe try changing the port Jetty runs on to port 80 (again, assuming you don't have anything else running on port 80):
http://tinyurl.com/6nkwnf

4 days of works and it is still now running. I am a bit despereate for
help at this stage.

We will absolutely get you up and running. It may take a bit of back and forth but this is all standard stuff, so we'll get it sorted!

--
Matt Woodward
[EMAIL PROTECTED]
http://www.mattwoodward.com/blog

Please do not send me proprietary file formats such as Word, PowerPoint, etc. 
as attachments.
http://www.gnu.org/philosophy/no-word-attachments.html

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to