Anyone Out There...

choysiulung

Member
After a long history with World software, my company is on the track of implementing Xe. We are a global manufacturing company with approx 40 plant sites scattered evenly through all four continents.

Our goal is to implement OW Xe on a single instance of SQL2000 on an NT platform with clients accessing the software via citrix. We discarded the AS400 because we could not justify the cost of a server capable of running 35 concurrent UBEs.

We are in CRP phase of our implementation and have applied Update #1 and SP15.1 to Xe. I am writing to see if there are other implementations of this size on a single SQL Server instance.

Last but not least

Any comments are welcome.

JH
CNC, W2K Advance Server, SQL2000 Enterprise Edition, CO on Enterprise Server, Citrix
 

SSAJAROFF

Reputable Poster
John :

I've got about 20 different customers running on NT/W2K/SQL, some of them
use Citrix and others
don't.
How many users are you going to have? 200? 600?
A few advices would be :
a) I would not use a single box for such situation. It's not scalable.
b) Think on separating Database servers from UBE Servers : a box running
UBEs, another one
running SQL Server, both communicated across a fiber ring. It's a highly
scalable solution,
its only drawbacks are its network bandwidth requirements and $$$ cost.
c) Think on physical separation of Production and Developing environments,
for example a
server for DV, PY and JD databases; and another server for PD databases. A
server for
DV, PY and JD processing UBEs, and other for PD UBEs.
d) Evaluate the possibility of clustering and/or replication to ensure your
data availability.
e) UBE server clustering could be an interesting idea too.
f) Keep CO away from the Enterprise, packages read specs from there. Put CO
on the Deployment.
g) Put Data files and Transaction Logs files on different physical disks.
h) Have you been thinking on your backup and disaster recovery strategy?
i) If you plan to install across several time zones, be sure to define all
your servers
with the same time. For example, UT (former GMT, Greenwich time) time.
j) I do realize that a) to g) are expensive ideas, but remember that
JDE/W2K/SQL2K
is not an AS/400. It's not a high reliability - high availability A7.3 host
environment,
it's a distributed processing schema where Murphy's Laws often apply.

Yours,

Sebastian Sajaroff
ssajaroff@grupoassa.com
B7321 to Xe, NT/W2K/SQL/JAS/Citrix/Interop
MSCE,MCDBA,MCP+I,Citrix Admin



B7321 to Xe, NT/W2K/SQL
JAS, Interoperability
MCDBA,MCP+I,MCSE,Citrix Admin
ssajaroff@grupoassa.com
Grupo ASSA - Application Software SA
 

choysiulung

Member
Re: RE: Anyone Out There...

THanks for the reply. It is interesting that you are recommending placing the CO on the deployment server instead of the enterprise server. Can you expound on your reasoning for it? On all your other points, we are on the path of doing exactly as you are recommending.

Lastly, any ideas on 3rd party monitoring tools besides SAW.

Thanks a bunch.

jh
 

SSAJAROFF

Reputable Poster
RE: RE: Anyone Out There...

John :

Remember that packages UBEs have to read 2.5 Gb of specs tables to create a
full package,
and that client packages run 100% on the Deployment (server packages run 50%
on the
Deployment, 50% on the Enterprise).
If you put C.O. on the Deployment, the package spec reading process will not
affect the
Business Data and Control Tables databases performance, and you will reduce
network
traffic because specs will be located on the Deployment itself.

Sebastian Sajaroff



B7321 to Xe, NT/W2K/SQL
JAS, Interoperability
MCDBA,MCP+I,MCSE,Citrix Admin
ssajaroff@grupoassa.com
Grupo ASSA - Application Software SA
 

hotm6654

Well Known Member
Ah yesssss, the Enterprise server Catch 22.......



I just wonder how many OW installs there are out there that couldn't =
manage to justify the premium price for the AS/400. Somehow they manage =
to justify the added expenses of a fission solution (multiple, =
clustered, enterprise servers; redundant enterprise servers; application =
servers; batch UBE servers; redundant terminal servers; additional =
Citrix, SQL2000, and NT Server licenses; added NT administrator =
overhead, added OneWorld administrator overhead).




----- Original Message -----=20
From: "Sajaroff Sebasti=E1n" <SSAJAROFF@grupoassa.com>
To: <jdelist@jdelist.com>
Cc: <jdelistml@jdelist.com>
Sent: Monday, June 11, 2001 6:50 AM
Subject: RE: Anyone Out There...


them
running
highly
cost.
environments,
databases. A
your
Put CO
disks.
strategy?
all
host
of
plant
NT
the
running
and
of
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=3D&Board=3DOW&N=
umber=3D1



JD Nowell
OW: B7332
ES: AS400 V4R4 CO: DB2/400 SP: 11.2
Users: 250 TSE Users: 100
 
Top