Re: J Walk Server on the AS/400
--=====================_24244928==_.ALT
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Ok, so attachments don't work on this list...here it is in English
J WALK SERVER / JAVA CLIENT
OPTIMUM MINIMUM REQUIREMENTS
Client
=B7 Win NT 4.0 or Windows 2000 (the Java Client will run on both Win=
95=20
and 98, but both of these operating systems do a poor job of managing=20
resources)
=B7 Pentium III 450mhz (the higher the better)
=B7 128MB RAM
=B7 Internet Explorer 5.01 with latest JVM or Netscape 4.7 (Netscape=
=20
uses a little more memory because it is not integrated with Windows as is=
I.E.)
NT Server
=B7 Win NT 4.0 or Windows 2000 Server
=B7 Pentium III 450mhz, the higher the better
=B7 256MB RAM (The more J Walk Server instances you run, the more=20
memory we recommend. Also, the panel files and associated application files=
=20
are loaded into memory, so if your JWR is 10MB, you will need an additional=
=20
10MB)
=B7 For each 5 client connections you will need approximately 1MB of=
RAM.
=B7 Plenty of hard drive space for the J Walk Server as well as for=20
swapping.
Native AS/400 Server
=B7 V3R7 or higher, we have found that there have been performance=20
increases to HTTP server with later versions of OS/400.
=B7 J Walk will use approximately 10MB for the server application in=
=20
addition to loading the J Walk application files, JWR, JWX, JWM, etc.
=B7 For each 5 client connections you will need approximately 1MB of=
RAM.
=B7 There is a 3 to 1 ratio for green screen users to Java Clients. =
If=20
the AS/400 will support 900 green screen users, then the AS/400 will=20
support approximately 300 J Walk Java Clients. This is due to the fact that=
=20
the J Walk Native Server has to provide the Telnet connection as well as=20
all negotiations on behalf of the Client. This does not take into account=
=20
other programs running on the AS/400 that impact overhead.
Here are the variables that impact Java Client performance:
=B7 Java (Java Virtual Machine) is CPU intensive, so the higher the=20
CPU, the faster the Java Client will perform
=B7 Since Java runs in the JVM shell, it uses quite a bit of memory
=B7 The use of a lot of graphics. We are implementing caching of the=
=20
images on the local PC in J Walk 3.1C2, but the images still need to be=20
downloaded.
=B7 The speed of the connection to the J Walk Server, slower dial-ups=
=20
24K or lower, can influence performance
=B7 Running other programs, such as Lotus Notes, which is also memory=
=20
intensive, can impact Java Client performance. This will be relative to=20
the amount of total RAM on the PC.
=B7 Using our Tunneling Daemon (HTTP Tunneling, also referred to as=
the=20
SEAGULL Web Server) can impact performance.
=B7 Network bandwidth, 100 mega bit versus 10 mega bit
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
Rich Buttenhoff Phone
208)799-4181
Potlatch Corporation Fax
208)799-1687
805 Mill Road Mailto:
[email protected]
Lewiston, ID 83501-1016
http://www.potlatchcorp.com
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
Walking on water and programming from
specifications are easy, if both are frozen.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
--=====================_24244928==_.ALT
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html>
Ok, so attachments don't work on this list...here it is in English
<div align=3D"center">
<font size=3D4><u>J WALK SERVER / JAVA CLIENT
OPTIMUM MINIMUM REQUIREMENTS
</font></div>
<font face=3D"Arial, Helvetica">Client</u></font>
<dl><font face=3D"Symbol">
<dd>=B7<x-tab></x-tab></font><font=
face=3D"Arial, Helvetica">Win
NT 4.0 or Windows 2000 (the Java Client will run on both Win 95 and 98,
but both of these operating systems do a poor job of managing
resources)</font>
</dl><font=
face=3D"Symbol">=B7<x-tab></x-tab=
></font><font face=3D"Arial, Helvetica">Pentium
III 450mhz (the higher the better)
</font><font=
face=3D"Symbol">=B7<x-tab></x-tab=
></font><font face=3D"Arial, Helvetica">128MB
RAM
</font><font=
face=3D"Symbol">=B7<x-tab></x-tab=
></font><font face=3D"Arial, Helvetica">Internet
Explorer 5.01 with latest JVM or Netscape 4.7 (Netscape uses a little
more memory because it is not integrated with Windows as is I.E.)
<u>NT Server</u></font>
<dl><font face=3D"Symbol">
<dd>=B7<x-tab></x-tab></font><font=
face=3D"Arial, Helvetica">Win
NT 4.0 or Windows 2000 Server</font>
</dl><font=
face=3D"Symbol">=B7<x-tab></x-tab=
></font><font face=3D"Arial, Helvetica">Pentium
III 450mhz, the higher the better
</font><font=
face=3D"Symbol">=B7<x-tab></x-tab=
></font><font face=3D"Arial, Helvetica">256MB
RAM (The more J Walk Server instances you run, the more memory we
recommend. Also, the panel files and associated application files are
loaded into memory, so if your JWR is 10MB, you will need an additional
10MB)
</font><font=
face=3D"Symbol">=B7<x-tab></x-tab=
></font><font face=3D"Arial, Helvetica">For
each 5 client connections you will need approximately 1MB of RAM.
</font><font=
face=3D"Symbol">=B7<x-tab></x-tab=
></font><font face=3D"Arial, Helvetica">Plenty
of hard drive space for the J Walk Server as well as for swapping.
<u>Native AS/400 Server</u></font>
<dl><font face=3D"Symbol">
<dd>=B7<x-tab></x-tab></font><font=
face=3D"Arial, Helvetica">V3R7
or higher, we have found that there have been performance increases to
HTTP server with later versions of OS/400.</font>
</dl><font=
face=3D"Symbol">=B7<x-tab></x-tab=
></font><font face=3D"Arial, Helvetica">J
Walk will use approximately 10MB for the server application in addition
to loading the J Walk application files, JWR, JWX, JWM, etc.
</font><font=
face=3D"Symbol">=B7<x-tab></x-tab=
></font><font face=3D"Arial, Helvetica">For
each 5 client connections you will need approximately 1MB of RAM.
</font><font=
face=3D"Symbol">=B7<x-tab></x-tab=
></font><font face=3D"Arial, Helvetica">There
is a 3 to 1 ratio for green screen users to Java Clients. If the
AS/400 will support 900 green screen users, then the AS/400 will support
approximately 300 J Walk Java Clients. This is due to the fact that the J
Walk Native Server has to provide the Telnet connection as well as all
negotiations on behalf of the Client. This does not take into
account other programs running on the AS/400 that impact overhead.
Here are the variables that impact Java Client performance:</font>
<dl><font face=3D"Symbol">
<dd>=B7<x-tab></x-tab></font><font=
face=3D"Arial, Helvetica">Java
(Java Virtual Machine) is CPU intensive, so the higher the CPU, the
faster the Java Client will perform</font>
</dl><font=
face=3D"Symbol">=B7<x-tab></x-tab=
></font><font face=3D"Arial, Helvetica">Since
Java runs in the JVM shell, it uses quite a bit of memory
</font><font=
face=3D"Symbol">=B7<x-tab></x-tab=
></font><font face=3D"Arial, Helvetica">The
use of a lot of graphics. We are implementing caching of the images
on the local PC in J Walk 3.1C2, but the images still need to be
downloaded.
</font><font=
face=3D"Symbol">=B7<x-tab></x-tab=
></font><font face=3D"Arial, Helvetica">The
speed of the connection to the J Walk Server, slower dial-ups 24K or
lower, can influence performance
</font><font=
face=3D"Symbol">=B7<x-tab></x-tab=
></font><font face=3D"Arial, Helvetica">Running
other programs, such as Lotus Notes, which is also memory intensive, can
impact Java Client performance. This will be relative to the amount
of total RAM on the PC.
</font><font=
face=3D"Symbol">=B7<x-tab></x-tab=
></font><font face=3D"Arial, Helvetica">Using
our Tunneling Daemon (HTTP Tunneling, also referred to as the SEAGULL Web
Server) can impact performance.
</font><font=
face=3D"Symbol">=B7<x-tab></x-tab=
></font><font face=3D"Arial, Helvetica">Network
bandwidth, 100 mega bit versus 10 mega bit
</font><x-sigsep>
</x-sigsep>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
Rich
Buttenhoff=
&nbs=
p;
Phone
208)799-4181
Potlatch
Corporation =
;
Fax
208)799-1687
805 Mill Road
<a href=3D"mailto:
[email protected]"=
eudora=3D"autourl">Mailto</a>:rich.buttenhoff@potlatchcorp.<a=
href=3D"mailto:
[email protected]" eudora=3D"autourl">com
</a>Lewiston, ID
83501-1016
<a href=3D"http://www.potlatchcorp.com/"=
eudora=3D"autourl">http</a>://www.potlatchcorp.<a=
href=3D"http://www.potlatchcorp.com/" eudora=3D"autourl">com
</a>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Walking on water and programming from
specifications are easy, if both are frozen.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
</html>
--=====================_24244928==_.ALT--
