Pros/Cons of one server or 3 servers for Lawson system

Pros for 3 separate servers (or 4):
1. Separation of duties. You know whether it's a server error or a resource issue.
2. Everything is clean cut. You know what code or applications are being used to control that part of the application
3. Licensing. Certain applications cost are dependent on the number of cores/CPUs in use on that server. We limit the number of cores we use for Oracle because the database is on a separate server with only 2 cores.
4. Easier to backup, replace, scale vertically or horizontally.
5. Allows you to lock users out of unnecessary access to certain servers.

Cons:
1. Network connectivity (even when they are all on the same physical box)- or at least logical network connectivity.
2. Applying portal patches means applying in 2 places.
3. Confusing to end users in portal if you have a webserver and a core server.
4. Can be confusing for lawson support to understand the scope of an issue.


There are probably many more, but I thought I would throw in my 2 cents.

A big pro for one server is performance.

Depends on your platform that you are running on.

If you are running 32 bit Lawson, I would recommend seperation of servers. One of the major reason to seperate the servers under 32 bit windows platform is OS memory management. 32 bits OS is "lacking" to handle all the third party apps required to run lawson.

If you are running 64 bit Lawson, one server do make alot of sense. The memory restrictions are no longer in place.

If you are buying a new server with alot of cores and alot of physical memory, 64 bit lawson one server configuration would be ideal for your workload that you described in my opinion. My next Lawson upgrade will be 64 bit one server configuration.