× 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're going through this now (most applications are converted, there are
two left). There is a migration document in the 5.1 documentation that
goes through the steps at a very high level.

One thing that it doesn't touch on is that you need to make sure that
you're on the Apache Based HTTP sever before you can use the WebSphere
5.1 plug-in. If you haven't already migrated, don't bother with the
Migration Wizard (you can search the archives both here and at
http://www.ignite400.org for why I'm telling you this). Instead, pick up
a copy of "Professional Apache 2.0" and do the migration yourself. Also,
make sure that you have the latest group PTF for WebSphere installed to
make sure that everything is up to date. You'll also need to have JDK
1.4 and 5722AC3 installed (put both of those on before installing the
group PTF's).

Connection pools and session managers are accessed differently in the
two releases. The connection pool difference is minor (don't pass any
parameters in on the call to get the InitialContext). The applications I
was responsible for converting didn't use sessions so I don't know
what's involved there.

You'll need to make sure that the application uses the J2EE directory
structure and that your web.xml specifies version 2.3 of the webapp DTD.
You'll also need to add resource references to the connection pools
you're using (this goes in the web.xml) or you application will not be
able to look up a connection pool.

Also, I highly recommend that you avoid the GUI that's built into the
HTTP Server admin GUI. It's incredibly easy to clobber this GUI (if you
use it and it gets messed up, the archives at http://www.ignite400.org
has a posting by me that explains how to fix it). Use the console
application instead (besides the fact that it will not clobber itself,
it also performs much better), you will need to use the HTTP Server
Admin GUI to start the console application but that's the extent of the
use I recommend. You will need to do more steps with the console
application than in the HTTP Server Admin GUI to get things done but the
documentation talks about how to do this. Also, the new console is not
an application that you need to download, it's all browser based.

Matt

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of bruce@xxxxxxxxxx
Sent: Monday, June 27, 2005 10:46 AM
To: web400@xxxxxxxxxxxx
Subject: [WEB400] 3.5 Application to 5.1

We have an Websphere Application that was created using version 3.5. Is
there a redbook or other articles that can help me in converting the
application from WAS 3.5  to 5.1.

 

Thanks

 

Hoss 


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.