Good day all,

Is there anyone out there running a similar configuration that can offer some guidance on our the Tomcat issue? We are wondering if a single webserver will handle the demand when we implement ESS and MSS.

Background info:
We are a Windows shop. Distributed 8.03 Lawson environment. 2 node SQL cluster, 2 node App cluster, webserver and a crystal reporting server. Hardware is beefy.
Approximatley 3500 users distributed across three shifts.
We are still in "implementation phase". We have gone live with Payroll and Procurement. We are using RSS. Someone dropped a bug in the bosses ear that Tomcat will break down at around 100 concurrent connections. We expect around 350.
I'm a new Law Admin and I don't know nadda about Tomcat and find the website confusing, so I'm having difficulty finding any information to substantiate the claim or dispute it.

just in need a little guidance :nix:

Thanks in advance!

If you re worried about dropping connections between IIS and Tomcat, you could always increase the number of maxProcessors for your AJP13 Coyote Connector (see Lawson KB article http://kmcollections.lawson.com/KMDOCS/GSC...TM?docid=100008 for an explanation of how to configure this). The number of concurrent users that you expect is fairly small, however, so you could probably get by with the default setting of 75 processors.

What you shoould make sure of is that you have the correct ESP level and ESS version to be able to support pooled DME. ESS makes extensive use of DME calls, and you don't want these done as CGI, lest you hammer your app server. Lawson 8.0.3's use of an RMI server to pool native DME processes isn't as scalable as a true J2EE architecture, but it's better than CGI.

Thank you for your reply. The article was quite helpful in regards to the configuration settings. I believe based on what I've been able to find out that our configuration settings are fine. We have a DME pool and we are set witht he default 75 connectors. However, being that I'm new at this, I'm having difficulty in finding any documentation in regards to how many concurrent users a single Lawson web server should be able to handle, so upper management still has me digging for answers.

I have a follow up question if I may:

What has been your experience with the number of concurrent users a single web server can handle?

In my experience, an IIS/Tomcat combo can handle a lot of concurrent Lawson 8.0.3 users. Having too many users will create problems with many J2EE applications, because each active session comsumes a lot of memory. Lawson 8.0.3, however, stores nothing with sessions.

I'll give you some numbers. In any given day our Tomcat servlet container handles about 400,000 requests from about 1000 PCs. The busiest 5 minute period will see about 4500 request, or an average of 15/second.

That's great information! Just what I was I was looking for.

Thanks for our input!