We've successfully run struts with WAS 3.5.2:
>> Prerequisites
First of all you will need to do is have the following things at hand or
already installed.
-- JaxP (Java XML Parser)
-- WebSphere Application Server 3.5
-- WebSphere Application Server 3.5 Patch 1 & 2
-- Struts 0.5 or Higher
1. Apply the Fixes to WebSphere Application Server First before proceeding
2. Download and Install JAXP onto your workstation.
3. Have the path ready for JAXP to identify where the jar files are.
4. Download and Install Struts, Unzip the product and have the path ready
tor write down.
5. Start the WebSphere Application Server
6. Create a WebApplication from a war file following these instructions:
>> WebSphere Application Server WAR file Conversion and Installation
Here is a step by step guide. It assumes you are familiar with WebSphere..
1. Startup the Admin Server.
2. Start your Admin Console.
3. Select the "Convert War Task" menu option from the Console-->Tasks
menu.
4. You will be presented with a Wizard type window that takes you step by
step through the process.
5. Select the servlet engine you want to add the web app to.
6. Select the virtual host that is running this servlet engine.
7. Select your war file via the file dialog
8. Select the directory you want to install the war file contents to.
9. Optionally select a Web App name and root path for the Web App.
10. Click finish and the war file should be converted into WebSphere
format.
The Following JAR files will need to be added into the newly created
WebApp
-- parser.jar
-- jaxp.jar
Click on the Apply Button in WebSphere Application Server to ensure that
the changes took place.
Refresh the Administrative Console to view the changes.
>> Note: Place these jar files in the webapplications classpath inside of
WAS
Start the Application Server that you created in websphere
Open up a browser and run the following: http://localhost/<WebAppName>/
If there are any problems consult the stdout.txt file in your specified
directory that is created when problems occur.
investigate and resolve the problem
--
dIon Gillard, Multitask Consulting
Work: http://www.multitask.com.au
NetRexx: http://www.multitask.com.au/NetRexx.nsf
----- Forwarded by dIon Gillard/Multitask Consulting/AU on 04/12/2000
06:57 AM -----
Submitted by
Category
.
Public
"Ray Power" <[EMAIL PROTECTED]>
on 03/12/2000 at 10:22 PM
<[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>
RE: Struts ok with WebSphere AppServer?
-----Original Message-----
From: Lefty Burgess [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 01, 2000 11:26 PM
To: [EMAIL PROTECTED]
Subject: Re: Struts ok with WebSphere AppServer?
Craig R. McClanahan writes:
>
> I'm not familar with the details of WebSphere, but accepting WARs as a
deployment
> format is all that is all that is required. See Section 9.3 of the 2.2
spec, which
> says:
>
> The specification defines a hierarchical structure which can exist
> in an open file system, an archive file, or some other form for
deployment
> purposes. It is recommended, but not required, that servlet
containers
> support this structure as a runtime representation.
>
> As long as the container provides an environment that complies with the
> programmatic requirements of the servlet API (such as resolving
getResource() and
> getResourceAsStream() calls correctly), it does not matter what
internal
> architecture is used to represent the components of the application.
>
> Just as one example of an implication of this: it is not portable to
assume that
> you can use file I/O to talk to "files" within the web application
document root.
> The only portable mechanism is ServletContext.getResource() and
> ServletContext.getResourceAsStream() -- which is why Struts uses these
calls for
> things like reading the configuration file.
I stand corrected then. I think I'll scamper off and read the spec
more carefully.
> >
> > The whole point of a war file (and this has already appeared on the
> > list) is such that one can drop the war into any given compliant
> > container and it just work. However, one cannot simply drop a war
> > file into WebSphere and expect it to work. Utilities must be used to
> > *convert* the war file into a WebSphere application.
> >
>
> Some sort of deployment tool is required by pretty much any application
server.
> Even something simple like Tomcat has such a tool (the text editor you
use to tweak
> properties in server.xml :-).
Yes, but Tomcat does not require you to run a separate conversion
utility on a war file to convert that war file into a separate set of
files that Tomcat recognizes as a web application. This is what
WebSphere does. :)
Still, WebSphere *is* compliant then, based on your correction that
the spec only recommends the use of the war file format.
> >
> > The fact that WebSphere 3.5.2 does not *natively* support war files
> > speaks for itself in demonstrating that WebSphere is not fully
> > Servlets 2.2 compliant.
> >
> > That was my only point: that "support for WAR files" does not equal
> > fully compliant servlet container.
> >
>
> Are there particular aspects of WebSphere that cause Struts-based
applications to
> still fail, even when you properly deploy a web application using their
tools?
Heehee! That's just it. We don't know because no one has actually
tried it yet. At least, no one here has mentioned doing it, to my
knowledge.
I will be working this issue Monday, so I will definitely let everyone
know what my experience is.
> Craig McClanahan
--
Lee "Lefty" Burgess <<!>> Manipulate eternity. Power is a symphony:
Web Application Developer <<!>> elaborate, enormous, essential.
PiperStudiosInc <<!>> Dream the moment with a fiddle in summer
[EMAIL PROTECTED] <<!>> and a knife in winter.
Previous Document
Next Document
Return to View
