Unix to Windows migration

Standard supports up to 4 CPUs.
Enterprise up to 8 CPUs.
Are you going to run WebSphere/IIS and database on the same server as well?

IIS and the database will each be on their own server.

4CPU/32GB <-- standard edition
8CPU/2TB <--- enterprise edition

Set the OS resources cap higher so you can dynamic allocate the resources when they are needed. Also, i believe the VM licenses are:

Standard Edition - 1 VM allowed
Enterprise Edition - 4 VM allowed

Thanks for the replies, I passed the information to our network staff and they will be installing the Enterprise edition. Now can you help me with sizing in the VM world. Lawson has suggested that our application server be an 8 core – 16 gb build (we will put the database and web server on its own servers). Our network people were wondering if this was overkill to start with, keeping in mind that we can always add more if needed. They tell me that we would not get the performance boost one would think if they put in an 8 core vs. 4 core (doubling the size is not going to give me twice the speed).
Given this, I’m wondering what size LSF (application) Windows 64 –bit servers others have set up. Is 8 core too much? Is 4 core too small? Please help….

We will be doing the exact same thing ..... I would like to know how your project turns out ... issues and advice, etc.

The information everyone provides in this forum is invaluable and that is why I'm asking for some help as we venture into the world of Windows VM and LSF. In other words, I'm asking for a second opinion with regards to sizing a machine for our production application server. I know the Lawson system and I have a great network group who knows virtual world, but we just want to know what others have to say from experience. Thanks. Julie

One question before I make any suggestion. What's your "current" lawson production server's specification? core/memory?

Current App Server - HP-UX Pa-RISC server 6x1ghz with 18gb ram. Our Unix sysadmin reported that on Monday the CPU usage was about 35% and memory was around 8 gb (he is working on more days to give me an average).

The numbers you listed, is the base on how much CPU/memory you would want on your VM. Scale it for future processing need also. In my opinion, the #1 rule is no one want to become slower. So make sure your VM pumps out more transaction power than your existing production server.

At 6core/35%, 8gb current memory usage, I think 8core VM with 16GB of memory is not that far off the mark. It would actually be what I would recommend if I were to do your server sizing. I would still need the peak CPU%/memory usage data before jumping into conclusion. If your existing server peak at 17gb memory, then i will need to see why it's peaking so high. Is it related to lawson or some other factor. etc etc etc

*Also factor in processing growth etc, if your company gonna hire additional 1000 employee in the coming year, you will need to take that into consideration. The higher-up won't like to hear your server can't handle the additional workload when the company is heading into expansion mode.

Are you using vmware?

Thanks for the reply Jimmy! Yes, we are using vmware. What further clouded the issue for us was a sizing document that was done some time ago that recommended a physical IBM server (Intel Xeon 2660 MHz processor with 6 cores, 24 Gb memory) for our application, web server, and database. There is also a note that states that 2 additional cores were added because of ProcessFlow (we have about 20 flows and they are either for ESS or simple flows we created). Given that and the #1 rule that we don't want to become slower, is what prompted me to ask for your opinion on sizing.