× 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.



We can't go straight to WAS 8 since it is not supported on V5R4 and the WAS applications must be stable before the OS upgrade. Otherwise I would agree.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 9/8/2011 10:33 AM, James Perkins wrote:
If you can't go to WAS 8, I would definitely go to WAS 7. WAS 6.x is based
on Java EE 1.4 which is quite awful. Also WAS 6.1 uses Java 5 which was
EOL'd almost 3 years ago.

That said, WAS 7 is based on Java EE 5 which is ageing as well. Java EE 6 is
the current standard which WAS 8 implements full Java EE 6 specification and
Java EE 7 will likely be released in about a year or so.

--
James R. Perkins


On Thu, Sep 8, 2011 at 07:06, Jim Oberholtzer<midrangel@xxxxxxxxxx> wrote:

> A client of mine is in the process of upgrading the IBM i 7 from V5R4.
>
> The use WAS (full version) extensively as well as a full copy of Zend
> Server. WAS is internal applications, Zend is external.
>
> There is a minimum of WAS 6.1.0.29 (which is already on the V5R4 system
> but not implemented) for V7 but WAS 7.0.0.7 is also available. WAS 8.x
> is determined to be too big a jump and can't be done before the upgrade
> since it is not supported on V5R4.
>
> Those of you who have done this, which server would you use? WAS 6 or
> WAS 7? Why?
>
> --
> Jim Oberholtzer
> Chief Technical Architect
> Agile Technology Architects
>
> --

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.