HTML/JAS - Does anyone really use this?

I have recently installed the JAS SP20 HTML and Portal on a Intel W2K server WebSphere 3.5 with an AS/400 as the Enterprise Server. (AS/400 stores the Java objects in F989999/8). When logging onto the HTML client the first time (after reboot/IPL), it can take up to 4 minutes to load. After the menus and applications are CACHE, it works fine. Does anyone else have this issue? Do users really wait that long to load JDE? The official response from the JDE hot line is that we should not reboot our W2K Server (thus the CACHE will not be cleared). Also, the re-paging of the screens each time you click and the fact that you cannot use the IE explore BACK button seems to be an inconvenience.

Just wondering if this is a real product yet??

Hi Tom,

Have you implemented the change detailed in KG doc OTI-02-0077?

One of the things which can be done to improve things is to look at the indexes defined on the relevant tables. We're aiming to use JAS as our main interface so it matters to us a lot. We've added indexes to at least four tables so far, based on what we see in the debug logs and, particularly for building task views, that's produced a significant difference. We're now looking at pinning the task views in a keep buffer to boost it more.

I'm planning to post a heads up here when we've completed that work because it does look like it makes a significant difference.

The answer to your question is yes.
We have over 100 concurrent users on our live system served by one win2k JAS server. Performance is excellent.

How big is that win2k sever ? is it running 1,2 or ..... processors ?

I am interesting, because we are looking into the web solution and we are
in the first
step to investigate different platforms (win2k, AS400, Unix, ....).

Thank you
Mats Thunholm

---------------------------------------------------------------------------------------------------------

Mats Thunholm
Amersham Biosciences
Uppsala, Sweden
+46 18 612 0646 (w), +46 70 666 5819 (m)
[email protected]
---------------------------------------------------------------------------------------------------------



patrickjolliffe
<[email protected] To: [email protected]
fdis.com> cc:
Sent by: Subject: Re: HTML/JAS - Does anyone really use this?
owner-jdelist@j
delist.com


2002-11-04
14:29
Please respond
to jdelist






The answer to your question is yes.
We have over 100 concurrent users on our live system served by one win2k
JAS server. Performance is excellent.


OW XE, SP18.1 + one off's, AS400 V4R5
Mats Thunholm
AmershamBiosciences
Uppsala, Sweden

Based on some answers and questions, I wanted to follow up. Thanks everyone
for your input.

We are running 1 JAS Server: WebSphere 3.5 on Compaq ProLiant 3000 - dual
Intel x86 600 mhz with 2GB Memory/ 30 GB Storage - Win2K SP2. Our
enterprise Server is an AS/400 model 720. JDE XE with Service Pack 20 -
E1. (It meets minimum specs but is certainly not overpowered)

From the feedback and my own experience, this is what I think. When I
generate ALL objects, you end up with about 107,000 records of data in the
F989999 and 220,000 records in F989998. These tables hold the
serialized(JAVA) objects and are on the AS/400. WebSphere access these
tables and then CACHES the info on the INTEL box. Because there is just too
much data, it takes a long time to load the first time(you can see this in
the LOG files.. reading the F989998 file). If I pick and choose the objects
I need generated, it works fine. We have the basics, (Order Inquiry, Stock
Check, Inventory Inq, some reports). Now I only have a few thousand records
of data in the F98... tables and it works fast.

I did apply the Fix OTI-02-0077. This does speed things up but not enough.
We went from a 15 minute wait to a 4 minute wait when signing on the first
time and having ALL objects generated.

The ORACLE fokes out there don't seem to have this problem... perhaps the
all that money spent on the ORACLE database is worth it!!.....

There are several "tuning" options available in the JAS.ini file and in
WEBSPHERE, but I can't seemed to figure them out.

If anyone else is running this same configuration and has generated ALL
objects and is running fast, let us know how you do it.

Thanks

Tom



Tom Crawford

Hi,
Another tip that I have 'heard' being used is to schedule a dummy web client login right after an IPL/reboot.

Re: RE: HTML/JAS - Does anyone really use this?

Tom,

We have almost identical configuration to yours with one exception and performance is decent (15-20 sec to login- faster after that) especially after SP20. The difference is that we stored the F989998/9 tables on MS SQL residing on the JAS server machine. If you go this route you will need MS SQL JDBC drivers from Microsoft.
One performance problem we had was resolved by changing the AS400 QAQQINI file OPTIMIZATION_GOAL=*FIRSTIO.
Hope this is helpful.

Regards,

Erkut.

Hi Tom,

How many concurrent users are you running on your JAS Server ?

Best regards
Mats Thunholm

---------------------------------------------------------------------------------------------------------

Mats Thunholm
Amersham Biosciences
Uppsala, Sweden
+46 18 612 0646 (w), +46 70 666 5819 (m)
[email protected]
---------------------------------------------------------------------------------------------------------



Tom_Crawford
<Tom.Crawford@Per To: [email protected]
matex.com> cc:
Sent by: Subject: RE: HTML/JAS - Does anyone really use this?
owner-jdelist@jde
list.com


2002-11-05 21:14
Please respond to
jdelist






Based on some answers and questions, I wanted to follow up. Thanks
everyone
for your input.
We are running 1 JAS Server: WebSphere 3.5 on Compaq ProLiant 3000 - dual
Intel x86 600 mhz with 2GB Memory/ 30 GB Storage - Win2K SP2. Our
enterprise Server is an AS/400 model 720. JDE XE with Service Pack 20 -
E1. (It meets minimum specs but is certainly not overpowered)
From the feedback and my own experience, this is what I think. When I
generate ALL objects, you end up with about 107,000 records of data in the
F989999 and 220,000 records in F989998. These tables hold the
serialized(JAVA) objects and are on the AS/400. WebSphere access these
tables and then CACHES the info on the INTEL box. Because there is just
too
much data, it takes a long time to load the first time(you can see this in
the LOG files.. reading the F989998 file). If I pick and choose the
objects
I need generated, it works fine. We have the basics, (Order Inquiry, Stock
Check, Inventory Inq, some reports). Now I only have a few thousand
records
of data in the F98... tables and it works fast.
I did apply the Fix OTI-02-0077. This does speed things up but not enough.
We went from a 15 minute wait to a 4 minute wait when signing on the first
time and having ALL objects generated.
The ORACLE fokes out there don't seem to have this problem... perhaps the
all that money spent on the ORACLE database is worth it!!.....
There are several "tuning" options available in the JAS.ini file and in
WEBSPHERE, but I can't seemed to figure them out.
If anyone else is running this same configuration and has generated ALL
objects and is running fast, let us know how you do it.
Thanks
Tom
Tom Crawford
--------------------------


OW XE, SP18.1 + one off's, AS400 V4R5
Mats Thunholm
AmershamBiosciences
Uppsala, Sweden

Does anyone knows how to implement this dummy web client on AS400?
Robson
-----------------
Hi,
Another tip that I have 'heard' being used is to schedule a dummy web client login right after an IPL/reboot.

Yes, we are up on SP20_G1. The options look nifty, and we have been able to cut down a lot of the slow processing times. Our problem is that there is no comprehensive documentation out there, so the process is much akin to off-roading in a Merkur... we would like to know if others are taking the HTML e-ticket ride as well...

The machine has 4 * 700MHZ Pentium 3 processors, and 4GB memory.

Re: RE: HTML/JAS - Does anyone really use this?

Our setup is similar to yours, but our entire DB backend is SQL 2000. We do not have poor login times from HTML. We have not done anything special, other than apply the fix that has been discussed already (OTI-02-0077).