I have set up at my company, (besides our legacy JDE system) an array of 4 JDE EnterpriseOne apps servers (soon to be put on a load balancer (LB)) 6 JAS servers (already loadbalanced) , one back-end database and, of course, the ever-present deployment server. With this configuration we can take any JAS server off the LB and reboot it or do work on it. Likewise, we'll soon do the same with the apps servers, meaning that (in mid-day or anytime 24/7) we can take a couple apps servers off the production to deploy packages to them, and then add them back onto the LB. This is a true horizontally scaled JDE ERP system. Instead of apps security server PD01 or PD02, etc, all OCMs point to PD00, which in turn crosses over to the load-balanced apps servers. Same with the JAS servers. Also, all apps servers, in their JDE.ini, share the same printqueue folder and we've sorted out the print job table with triggers to handle changes in how this works. JDE published a VERY limited doc on this in June 2003. They told us, recently, however, that this solution is NO LONGER supported without their people coming on site to do the set up. All this runs in the Windows and SQL-2000 world, but we're planning to move off to Linux and Oracle's so-called "Red Stack" solution with the production database also running on Oracle 10g. When we move over to a horizontally scaled Linux-based Oracle Transaction Server and Oracle database, we should have no trouble scaling out to 10,000 users.