Meaningless Drivel is fun!
The moose likes Tomcat and the fly likes 2 Tomcat Server One Internal One External Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Tomcat
Bookmark "2 Tomcat Server One Internal One External" Watch "2 Tomcat Server One Internal One External" New topic

2 Tomcat Server One Internal One External

Lars Ulrich Goebels

Joined: Jan 14, 2013
Posts: 2
I have a big problem.
Please watch my attached picture to see what i mean.
I have website there is a calculator its form with fields.
I send this form via jquery(ajax) to the web server because my second tomcat server is not visible in the internet but there is my rule engine that creates all the rule for this calculator.
So I need to Talk from one tomcat to an other one where on is visible in the internet and one not.
How to solve this Problem?

Hope you know what I mean!



Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 17417

This can go in a couple of directions.

I don't actually recommend connecting Tomcat directly to the Internet. In order to work with the standard HTTP and HTTPS ports (80 and 443), Tomcat must run as a privileged user, which is a security exposure. Better to use a safer proxy such as Apache httpd and have all the Tomcat stuff internal. So ideally, all of the code you need could then be in a single webapp internally, proxied via Apache or Squid or something.

That's probably not possible without major surgery on the apps. So the next best thing is to set up a communications channel between the webapps. The most flexible option would be to have the first app make web services calls to the second app. However, since you're on an internal network, where you can use certain mechanisms that are difficult-to-impossible to use on the open Internet. The 2 most likely candidates for me would be RMI or EJB (and EJB is basically an extension of RMI).

Tomcat doesn't implement either EJB or RMI natively the way full-stack servers such as JBoss do, but you can add such functionality to individual applications by incorporating the right libraries.

Another option is available if you haven't coded yourself specifically into a webapp architecture, and that's to replace the internal Tomcat's functions with a standard RMI server. If you don't actually need all the functionality of a web server, that can make things a little more lightweight. I used to work with a system that had the primary webapp offload long-running tasks to an RMI service.

An IDE is no substitute for an Intelligent Developer.
I agree. Here's the link:
subject: 2 Tomcat Server One Internal One External
It's not a secret anymore!