Hardware recommendations for a new Enterprise Server and Xe


Active Member

we are evaluating the possibility of purchasing
a new Enterprise Server. Our current setup is as
follows :

Enterprise Server

IBM Netfinity 7000
4 Pentium Pro 200 MHz processors
2 GB of RAM
95 GB of disk space utilizing RAID-5 technology

Windows NT 4.0 Service Pack 6a
SQL Server 7 Service Pack 2

OneWorld B7332 Service Pack 10.1
25 Fat Clients

Primary Domain Controller
DHCP server
WINS server
Print server
File server
MacIntosh file server
MacIntosh print server
150 domain users

Deployment Server

IBM Netfinity 3000
1 Pentium III 500 Mhz processor
256 MB RAM
54 GB of disk space

Windows NT 4.0 Service Pack 6a

Central Objects

We are getting lousy performance from our Enterprise Server.
Most of the contingency is coming from the disks. Anyhow,
this machine is getting less and less stable. A few months
ago we lost the ServeRaid card and last week we lost two hard
disks. Since we are on B7332 and knowing that B9 is coming
out next summer and that we will be forced to upgrade to at
least Xe, we are thinking about buying a new server to dedicate
OneWorld to, which is a very good idea in my opinion. We are
looking for advice on hardware configurations. I have two
configurations in mind. The first setup consist of two machines.
One for SQL Server (database server) and one for OneWorld Xe
(Application Server). Is it worth setting up Terminal Services on
the apps server for just 25 clients or should I stick with all fat
clients ? Here are the configurations for the first setup :

Database server

2 Pentium III 700 MHz XEON processors
4 GB of RAM
75 GB of disk space utilizing RAID 1+0 technology

Windows 2000
SQL Server 7

Application server

2 Pentium III 700 MHz XEON processors
2 GB of RAM (4 if Terminal Services ???)
75 GB of disk space utilizing RAID 1+0 technology

Windows 2000
Terminal Services ???
OneWorld Xe

The second setup consist of one BIG machine. This machine
would hosts SQL Server AND OneWorld. It would have the
following configuration :

Database and Application Server

4 Pentium III 700 MHz XEON processors
4-8 GB of RAM
150 GB of disk space utilizing RAID 1+0 technology

Windows 2000
SQL Server 7
OneWorld Xe

Any comments, recommendations, dos and don'ts, Xe experience
and Xe watch out or you could lose your job kind of things
are all welcome. Thank you in advance for any input you can



Hi , What did you wind up buying?. We have XE in an AS400 environment but are adding a new company and want to put them on the Intell Platform. Is it possible to combine Enterprise/Deploy on the same Server? Or Sql/Deploy or any combination of these? It is a company that will have about 40 users in 6 locations so we will be using Metaframe. Thanks for any Suggestions

Barney Brown
JDEdwards Admin
DME Company
Madison Heights Mi


VIP Member
In training class, they combine both enterprise and deployment servers together into one machine. However they recommend that it should not be done. (Do as I say not as I do.)

We have our Central Objects in SQL on the deployment server. When we build client packages, it doesn't impact the users in terms of performance. (The users don't notice.)

C Ho
Intermediate Programmer/Analyst
Xe SP 15.1, update1
AS/400 V4R5 coexistant
CO on SQL 7.0 SP2 + hotfix


Well Known Member
You can combine Enterprise/Deploy - there have been a number of threads on
this in the past, but it is not recommended. Given the cost of Intel Boxes
(much cheaper than AS400) you are better getting a box for each. What do you
mean by SQL/Deploy? Do you mean make the deployment server an Database
Server as well and split the Database? Seems a bit complex for a simple

OW733.3 Xe SP 14.2
Enterprise Server - Intel NT + Oracle 8.0.6
Client - Citrix TSE + 4 NT PC's for development
Call Orchestrations From Excel – The Easy Way to Make the Orchestrator Work for You.


Re: RE: Hardware recommendations for a new Enterprise Server and Xe

1.) I think it's a great idea to separate your db and the enterprise server. Or have your db on the enterprise server, but, off-load all logic to an apps server.
2.) I've used configurations of a SQL db on the deployment server for the purpose of builds. But, another db on another box for data, ct, etc.
3.) Separating high impact tables out of the convential out-of-the-box OneWorld db also helps performance. i.e. Perhaps moving it entirely to a another physical disk.
4.) If you use your deployment server to build packages, then it would not be in your best interest to combine that with your Enterprise server. I.e. bombed package, bounce server, lose connection in your prod environment.

Dunno, just some thoughts off the top of my head.

Hope it helps,