JAS Server / Generator

I am currently researching the set up of an XE Web Server.
In reviewing the JDE documentation I see that they are recommending the use of 2 machines for the use of the HTML client. The JAS server and a second machine used for object generation.

Can someone give me a quick overview of how this process works?
Is is the generator only used to create objects after upgrade or modification or is it used on a daily basis.

Do any of you use the JAS server for generation?
If so does that work OK or are two machines really the way to go?

How is the generation server configured in XE, does it just require a Fat Client and the JDBC driver?

What sort of capacity does a dual processor W2K JAS server have, ie how many users can it support.

Any information you can provide will be greatly appreciated.

DCD
Xe Update 3 SP17.1_F.1
AS400 w/Central Objects
W2K Deployment Server

DCD,

basically it´s two machines. However, if your JA-Server is NT/W2K, it can
be used as generation machine. The issue here would be
performance/resources. If you have no production at night and run the
generation in off hours you may be ok.

Whenever you build a new package (full or update) you need to deploy it
to your generation machine and then run the generation for the involved
objects for them to become available for the JAVA clients. That process
runs for hours in case of generating ALL objects.

The generation machine is just a fat client with some special
configuration. All comes with JDE Software.

A two-way Pentium machine with some 2-4 Gig of memory should roughly
suport 50 (or more) connections.

Hope this helped, Gerd

Hi DCD,

Yes the generator is only used after you make changes. (after the initial generation) Whenever you build a full package or update you will need to generate those objects so they will be available to your JAS users.

Yes we have a client that does use the JAS Server to generate their objects. As well as clients that use a workstation to generate.

Yes, a fat client and the JDBC are pretty much all you need.

Hope this helps,

Robby

XESP17 on NT4/SQL7, XEU3SP18 on W2K/SQL2K, XEU3SP16.1/A73 & JAS on AS400/W2K/SQL7

Client requests are served from the JAS Server along with IIS/Http
server on the same box (what ever you want this to be, a PC, the AS400).
The JAS server fetches application specs from two key tables, F989998
and F989999, which are the serialized objects (SOs). The SOs can be
stored on a PC in SQL, on the AS400. In our situation we had our
enterprise server (AS400) also be our JAS server and we loaded Websphere
on it...Too slow, we are now testing using a Win2000 PC for the JAS and
storing the SOs in SQL or on the AS400.

modification or is it used on a daily basis.
Only used initially to create all the SOs and then when objects are
modified you have to regen them. Generator allows you to specify which
objects to generate. Not used on a daily basis.

Not here. We use one of two developer workstations (P3 with 384 Ram or
a P4 with 256 Ram).

It's good to have a high powered machine for the generator because
genning takes forever and if you are in a live environment I wouldn't
see it possible to have clients hitting the JAS server while you are
genning.

a Fat Client and the JDBC driver?
Look at the MTRs in the KG. Also Needs Websphere loaded on it.

how many users can it support.
Not sure.

gman

ENT: AS400 V4R5 OW Xe SP16.1 15+ ESUs
DEP: NT 6a SQL 7 SP3
JAS: Win2000

I am currently researching the set up of an XE Web Server.
In reviewing the JDE documentation I see that they are recommending the
use of 2 machines for the use of the HTML client. The JAS server and a
second machine used for object generation.

Can someone give me a quick overview of how this process works?
Is is the generator only used to create objects after upgrade or
modification or is it used on a daily basis.

Do any of you use the JAS server for generation?
If so does that work OK or are two machines really the way to go?

How is the generation server configured in XE, does it just require a
Fat Client and the JDBC driver?

What sort of capacity does a dual processor W2K JAS server have, ie how
many users can it support.

Any information you can provide will be greatly appreciated.

DCD
Xe Update 3 SP17.1_F.1
AS400 w/Central Objects
W2K Deployment Server

--------------------------
Visit the forum to view this thread at:
http://www.jdelist.com/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OW&Number=30726

+ - - - - - - - - - - - - - - - - - - - - - - - -+
This is the JDEList One World« / XE mailing list / forum.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found on the JDEList Forum at
http://www.JDEList.com

JDEList is not affiliated with JDEdwards«

+ - - - - - - - - - - - - - - - - - - - - - - - -+



AS400 V4R5 Coexist CO-NT Xe SP16.1
Websphere 3.5.4 on AS400 JAS SP16.1

Hi David,

We've been looking a lot at the eGenerator and recommendations for it. It
is used to generate/regenerate the Java serialized objects. I think of it
kind of like a package build for the java piece, although it's not quite
the same. Like a deployment server, you regenerate when there are changes
to the java pieces...updates, development work, etc. You can regenerate
specific applications, or you can regenerate all, (kind of like a full
package build vs an update)

Also like a package build, the generation is very processor intensive. So,
you don't want it on any machine that is being accessed a lot, (like your
webserver). There isn't anything technically preventing you from putting
it on the webserver, you just need to be aware that when you do a
generation, response time on the webserver would be awful. Same goes for
putting it on the deployment sever. It should coexist without problems,
but performance of other things will be bad when you are doing a
generation.

Our previous recommendation was to put it on a fat client. There are some
additional pieces that need ot be loaded, JDK, etc, which you can get from
the JDE minimum technical requirements. Most fat clients are 1-ways. The
numbers I've seen for 1-ways doing a full generation are 3-6 hours....a
faster processor helps a lot. Some environments, especially during the
initial implementation may be doing a lot of regenerations and want a
faster turnaround. A 2-way should process in around 2-4 hours, from the
reports I've seen. Depending on what else you have on the deployment
server, (central objects, media objects, etc.), I think that might be a
good option, but it will depend on the situation, a fat client or a
separate box might be best in other situations.

A 2-way, (relatively current processor), W2K box, (xSeries of course!),
should handle around 200 - 250 users, but it will depend on which apps are
being used, is the OW portal being used, etc. If you want to disucss
sizing in more detail, give me a call.

Best regards,

Rob Jump
Sizing Specialist
IBM/J.D. Edwards International Competency Center
303-334-1054
[email protected]
www.ibm-jdedwards.com


DCD <[email protected]>@jdelist.com on 03/15/2002 09:37:47 AM

There is a performance problem with object generation after applying SP18 and SP18.1 to the JAS Server. Object generation slows down dramatically. It took me 2 1/2 days to generate all applications. I removed the Virus software from my JAS Server and the time for object generation is back to normal.

JD Edwards is aware of this problem after applying these SPs.

Thanks,
Bill

OneWorld B733.2 SP 11.3
Win NT 4/SQL Server 7
Citrix

OneWorld Xe Update 3 SP17
Windows 2000/SQL 2000
JAS
Citrix

Hi,
In our case the e-generator (which is basically a Java applet running on an NT/Y2K machine/client that has the path codes for the environments for which you want to generate) is a development workstation that contains the latest up-to-date specs for the objects (new interactive applications, menus etc) you need to re-generate. We generate in direct mode, that is by-passing the oneworld servers we generate objects from local specs going to the serialised objects database, in our case SQL2K (one database for each path code, as part of central objects).
If your plan is to use the JAS server (runs IIS or HTTP) as a Web Server for use over the internet, then you would completely secure that server (remove any access not strictly needed thru any conceivable port etc) and therefore definitely never use this server as the e-generator. If you are using HP-UX or AS400 as your JAS platform, you will also need a separate client as your e-generator anyway. Performance of your web server will drop badly if you start using it for a full generate (can take several hours overnight till morning), definitely not recommended!
Typically you can configure 1 or several fat clients (NT, W2K) used for OW development as e-generators, make sure they have more than 250 MB RAM (500MB-1GB is recommended for a full generate) and of course the necessary jar files for the type jdbc-drivers you require (eg jt400.zip if your serialised objects would be on as400), which can be in system\bin32 drive as long as the gen.bat can find them there (your version and location of the IBM-JDK is in the gen.bat). So the machine needs a nuber of jar files se documentation), some changes to the JDE.INI and importantly the JAS.INI file which needs to be carefully configured if you use direct generation (the fastest method!), info about this is found in the JAS install guide.
After the initial full generate (which has a guardian to recover the process from an unexpected crash), you would only need to generate the new/modified objects that need to be deployed (to test or production) from time to time for the html or java clients. However after each new SP install you need to do a full generate (all objects) again..
Good luck,
Rgds,
M.A.W.


OW B7332 SP15.1 > Ent.Srv.AS400 V4R4 > CO DB2/400 > Depl.NT4 Ent.Ed. > JAS HP-UX 11 + WebSphere Std.Ed.3.5.5 > JSO SQL2K > Citrix TSE clients

Thanks for all the advice, as always there is no better source of good information than from those who have experienced the process.

Robert, thank you for your input as well I am glad to see IBM/JDE are looking at the recommendations. I was unable to find a clear description on KG of exactly how this functionality really worked.

David Dickinson
Xe Update 3 SP17.1_F.1
AS400 w/Central Objects
W2K Deployment Server

Hi,

I saw your posting regarding your JAS test with SO on AS400 and/or SQL. Have you determined which config performs better ? Is your SQL on the JAS box or elsewhere?
Will you have multiple SO's ?(assuming you have multiple JAS boxes).

Thanks.