Gurus - what is *minimal* JAS configuration ?? + 3 JAS Qns

[vikingsteve]

Hi everyone,

We have a new client implementing a 'standard functionality' NT Xe system in two countries. What is the minimum number of boxes we need ?? Here's what we have so far :

Development location :
Deployment Server (primary)
NT Enterprise Server (Development) + SQL Svr

Remote location :
Deployment Server (secondary)
NT Enterprise Server (production) + SQL Svr
[thin client solution]

for thin client citrix we need :
1 TSE/Citrix machine
plus one fat client to generate glbtbls.

for thin client html we need :
???

what is the minimum configuration ?
(It was suggested the JAS software can run on the enterprise server ?? our client base will be low.)




And 3 quickies :
A. On what machine are the java objects generated and how long does this take nowadays ?

B. Can you run 100% of applications via html interface?

C. What happens if the generation of java objects (in prod) crashes half way through, does this therefore render the production system out of action unless we manage a successful generation ? (or restore from backup...)


(we have to make a choice between a Citrix or Java server in case you were wondering...)


Many thanks to any helpful nudges in the right direction.

Steve Murphy FRANCE.

 

[SSAJAROFF92]

Steve :

OneWorld is very but very network - traffic - intensive.
It's better to have a centralized site and let all users access it
via thin clients (Citrix/HTML) and remote access solution (Control It,
RAdmin, PCAnyWhere).
On that central site, you may have one Deployment, an Enterprise server
for country A and another for country B, and N Citrix or JAS Servers.
I wouldn't run JAS on the Enterprise, JAS is very resource intensive
too. And it doesn't run on anything less than 2 Processors 1.5 Gb RAM box.
For example, I couldn't run more than 2 concurrent users on a
Pentium III 1 Ghz, 768 Mb RAM W2000 Box.
According to the number of users, you'll need additional UBE Servers,
Citrix or JAS servers.
You may also consider to physically separate database tier from logic
tier (two servers : one for DBMS, the other for running UBEs).
a) Java Objects are generated on a fat client and may take up to 24 hours
to be generated (of course, it depends on the client you use...)
b) Most applications run on the JAS server, but not all of them.
As a rule of thumb, the vast majority of applications that run
successfully on the Enterprise Server should run fine on the JAS, so
Applications that need to be ran locally won't succeed on the JAS.
c) If the JAS Objects generation crashes in the middle (very common
situation, by the way) you'll have to restore PD7333.F989998 and
PD7333.F989999 tables from backup.

Bonne chance mon ami! (Good luck my friend!)

Sebastian Sajaroff
Grupo ASSA
(54)-11-4510-7200
Argentine

 

[MariaG]

Hi Steve,

We have been running Xe with web/html since April. This has been on RS6000
with AIX 4.3.3 and Oracle 8.1.6. I'm unsure about the minimum config as we
have a separate web server although I have heard that this can be on the ES
although not recommended
.
In reply to your "quickies" though, hope this will help:

A. In my case, I have a high spec workstation with 1024mb memory on which
eGenerator is loaded although I haven't has the need to generate all objects
since this was installed. The process is definitely quicker on this though,
for example reports and menu's. The generation of objects seems to be
dependant upon the spec of the workstation and if "ALL" objects are
generated, then the process can allegedly be speeded up by using parallel
generation. On a workstation with only 512mb memory, using serial
generation this could take around 6hrs+. Direct object generation can also
be used but I've not attempted this so far.

B. Not all applications can be run from HTML. For example, development /
systems admin etc in not possible on an HTML client.

C. When objects are generated, the process populates 2 tables. Ours are
held in Central Objects. The new eGenerator has a Guardian process where if
errors are encountered the process will start from where it crashed. We did
have a problem where the spec of our pc (memory), wasn't high enough and we
had repeated crashes. Because we truncated the F989999 and F989998 tables
we could not use that environment until a successful generation had taken
place. Under normal circumstances we just generate what we need to (eg
reports), without truncating the tables. Where this is a requirement then
we would export them first!

Hope this helps in some small way.

Maria.



OW Xe / JAS Sp15.1 (AIX RS6000 Web/Ent Server)
Oracle 8.1.6