RE: WebFacing : Is this really Heaven?

Patrick, I haven't answered your questions because I'm very biased, but I
had to respond to your post, especially on performance.

PSC400 takes about half an hour to install.  Once you've done that,
converting a program takes just a few seconds.  The first time you execute
that program, it may take as long as a minute to compile the JSP (this was
for a huge screen: 37 record formats, 3000 lines of DDS).  After that,
however, screens execute with sub-second response time.  So, for you
example, it would be like this:

FIRST TIME:

1. Convert the application (10-15 seconds)
2. Compile the definitions (30 seconds)
3. Start the application first time (20-30 seconds)
4. Logon, type an option, select a record, press exit, exit, exit (5-10
seconds)

SECOND TIME:

1. Logon, type an option, select a record, press exit, exit, exit (5-10
seconds)


Where PSC400 really beats WebFacing:

1. The programs run in batch (no interactive tax)
2. The JSPs are fully customizable, to allow various look and feels
3. There is a default 5250 emulation that looks just like old green screen
(no retraining)

The only disadvantage is that PSC400 is not free.

Joe


> From: P.Goovaerts@Clipper.Be
>
> My opinion after deploying our first application which is tested
> by ourself
> so far (not by the users):
>
>
> 1) Performance
> To give an idea of our performance, here's a responsetable:
> (Embedded image moved to file: pic10956.pcx)
> The amount of time includes typing of various options and
> pressing 'enter'!
> The first execution took 8minutes and 15seconds to
> 1) start the application
> 2) logon
> 3) type an option and enter at the MenuPanel
> 4) select a record and 'enter' in the BrowsePanel
> 5) select 'exit' at the HeaderPanel
> 6) select 'Exit' at the BrowsePanel
> 7) select 'exit' at the MenuPanel to end the application.
> For an unknown reason, this first execution ended in error while quitting
> the application (select 'exit' at the MenuPanel).  Of course this
> execution
> includes the compilation and classloading and is therefore considered
> 'normal'.  The final execution (6th run) on the intranet (local, without a
> firewall) took only 1minute and 5 seconds.  The Internetconnections are
> passing a firewall.
>
> 2) My remarks:
> - only 1 of 10 displayfiles had to be changed before conversion
> - For an unknown reason, our WAS355 recompiles all JSP's
>   over and over until WAS355 is shutdown and restarted.
>       (See attached file: default_server_stderr after 1st restart 3rd
> run.log)
> - Performance using local Intranet is acceptable.
> - Performance using a BroadBand-connection is just
>   at the limit of 'acceptable' but could be better.
> - Performance using V90 (56kbps) modem is unacceptable.
> - a serious amount of (error)messages are generated
>   while running the application.  This surely takes down
>   the performance!
>       (See attached file: default_server_stdout part with
> messages menu tot
> header.log)
>
> 3) Conclusion so far:
> Great tool to create WebApps on the fly using existing 5250-applications.
> However, to use it for Internet applications, some performance issues must
> be solved!  Specially the generation of the messages in the logs must be
> checked.  On the other hand, I have to admitt that we have to check AS400
> for performance too.  Our 720 is used to run a couple of Notes-servers for
> email, WAS355 SE, development and, last but not least, about 150 users.