 |
| Main Menu | |
| Other Modules | |
| Who's Online | |
There are currently, guest(s) and member(s) that are online.
You are Anonymous user. You can register for free by clicking here | |
| User's Login | |
|
Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name. | |
| GameHighScores | |
| |
|
| | The comments are owned by the poster. We aren't responsible for their content. |
|
|
|
No Comments Allowed for Anonymous, please register |
|
Re: Apache Tomcat integration with WAS 4.0 (Score: 0)
by Anonymous on Friday, August 10 @ 08:09:12 EDT
Not registered user | The article says that the remote nodes were already running Apache.
However, I can imagine another use for this method. Set up multiple redundant Tomcats for availability, and have them access a WAS for EJB only. Does anyone know if such a setup will require extra WAS-licenses? |
| Root | Parent |
|
Re: Apache Tomcat integration with WAS 4.0 (Score: 1)
by fredt on Tuesday, September 04 @ 15:29:43 EDT
Not registered user | | There were a number of reasons for not using the WAS servlet engine, the biggest being the license cost of running a large number of WAS servlet nodes on the remote machines. Also we already had a Tomcat infrastructure in place on these remote machines doing other servlet work so this was a logical choice for the app. |
| Root | Parent |
|
|
|
