× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Is there a similar link for 4.0?

I have this little brochure entitled "WebSphere for IBM eserver iSeries
Installation Checklist", subtitled "IBM WebSphere Version 4.0".  However
the links in this pretty printed brochure do not work.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin


Subject: Smooth WAS Install!
From: "John Taylor" <john.taylor@xxxxxxxxxxxxxxx>
Date: Sat, 9 Jun 2001 18:09:34 -0600

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

The last time I had WAS on the machine was at version 2.0, and after
hearing
about the various horror stories with this application, I was expecting
the
worst when I began installing version 3.5.3 this afternoon. Thankfully,
the
process went without a hitch. Here are the basic steps that I followed:

1) install latest group PTF's for everything except WAS.
2) install WAS 3.5
3) install WAS group PTF - brings it up to 3.5.3.
4) install Admin console on W2K with SP2.
5) install Admin console fixpack to bring it up to 3.5.3.
6) set max# jobs for SQL server to *Nomax.
7) verified QEJB user's authority to CRTLIB (*use).
8) configure HTTP server for WAS & restart it.
9) start QEJBSBS & Admin console
10) start default_server application
11) Ran Hello World! servlet to verify installation.

There were several potential "gotchas" that could have made things much
more
painful, but I was fortunate enough to find the following webpage, which
has
a great section on installing WAS. It takes you through the process step
by
step, in an easy to follow manner. Kudo's to whoever is responsible for
this
great documentation:

http://www-1.ibm.com/servers/eserver/iseries/software/websphere/wsappserver/
docs/as400v35std/docs/indexiic.html

The next thing that surprised me was the performance of the software. It
wasn't nearly as bad as I'd expected it to be, based upon what I'd heard.
My
hardware consists of the following:

AS/400
--------
9406-170 w/2385 CPU  (460 CPW)
1GB RAM
32GB non-raid  DASD (4 x 6713)
V4R5M0

Workstation
-------------
Intel PIII 933Mhz
384MB Ram
W2K w/SP2

Here are the initial startup times:

- start of QEJBSBS - 5 minutes
- start Admin console - 25 seconds
- start WAS default server - 60 seconds

Here's how long it takes to shut things down (with just a simple servlet):

- end default server - 4 seconds
- end QEJBSBS (using *CNTRLD 600) - 9 seconds

Here are the subsequent startup times:

- start of QEJBSBS - 1 minute, 6 seconds
- start Admin console - 20 seconds
- start WAS default server - 25 seconds

Overall, I'm quite pleased. It's too early to say what performance is
going
to be like with a real web-app instead of a simple hello-world servlet,
but
the initial numbers are encouraging.


John Taylor
Canada




+---
| This is the WEB400 Mailing List!
| To submit a new message, send your mail to WEB400@midrange.com.
| To subscribe to this list send email to WEB400-SUB@midrange.com.
| To unsubscribe from this list send email to WEB400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.