Splitting Enterprise Server

We have already split the JDE database into 2, live & dev, over 2 servers and are now looking at splitting the live JDE services and database out onto another server.

Thoughts so far are that the existing machine, IBM S70A 8-way processor, 12Gb memory, 1152Gb disk will remain the Oracle database server. We know the JDE services eat up memory & the batch jobs the processing and all with smaller disk utilisation, so we're looking at something a tad smaller then.

Are there any hints or tips from anyone for the server specs based on the different requirements of the services & database have ?

Plus any comments, good or bad, from anyones experience of this kind of split ?

Thx!

Well what we have maybe is a little different, but we have two as/400's one runs just production, it is our primary security server, runs its own services, has its own db. The secondary server runs all the rest of the pathcodes, it also has its own services, so they are seperate. But it does connect to the primary one for the security server.

We like it a lot, it gives us some flexability of taking down development functions for SP installs or backups while leaving production up and running. It also takes away from problems with performance if developers are running conversions and are hitting the DB heavy, those problems are isolated to the secondary box.

We also use a product to keep they PD pathcode (libraries) in sync with the seconary server.

Nick