Final WAS Install document

Sun, 13 May 2001 18:43:04 -0700

This is the final revision of the WAS install document, based on feedback from this group. Let me know if you have any further comments.
--
Dan Miser

WebSphere Application Server 3.5 Configuration

Server: Windows 2000 Server with WebSphere 3.5.3 Advanced

Configuring WAS 3.5
  1. Open struts.jar with WinZip. Extract the three DTD's (struts-config_1_0.dtd, web-app_2_2.dtd and web-app_2_3.dtd) into c:\websphere\appserver\classes, making sure you use folder names (so the files extract to classes/org/apache/struts/resources). Now WebSphere can find the DTD files with it's class loader, and there is no problem with using the SYSTEM identifier for the DTD. These files will be available to all webapps that WAS hosts with no additional effort.
  2. For each individual webapp, you will need to put your XML files in servlets/WEB-INF or add c:\websphere\appserver\hosts\default_host\<webapp>\web to the classpath. This is due to a bug in WAS, namely the class loader is not handling getResourceXXX calls properly.
  3. For each individual webapp, you will need to copy the 1.0.1 version of jaxp.jar and parser.jar to the servlets directory. You can find the correct version here
Deploying struts-example
  1. Start up the adminserver.
  2. Start up Admin Console.
  3. Use the Convert War file task to convert the struts-example.war from the struts-b1 distrib as-is.
  4. Convert to the default_server, default servlet engine and standard install directory (c:\websphere\appserver\hosts\default_host).
  5. Modify your classpath for struts-example by adding c:\websphere\appserver\hosts\default_host\struts-example\web. Be sure to restart your webapp.

    Alternatively: Create a WEB-INF directory in the servlets dir and copy struts-config.xml, database.xml AND web.xml into it (Keep WEB-INF with all the TLD's under web - both WEB-INF directories must be present).

  6. Copy jaxp 1.0.1's (NOT 1.1.1's) jaxp.jar and parser.jar to the servlets directory of the strut-example webapp.
  7. Click on struts-example in the Admin Console under Default Server/Default Servlet Engine and click the advanced tab on the right hand side of the screen.
  8. Down where it says Default Error Page, enter /ErrorReporter and then click Apply.
  9. Start the Default Server via the Admin Console. You should see a whole bunch of ActionServlet messages in the default_host_stdout.log file with no exceptions.
  10. Via a browser access the app using http://localhost/struts-example/index.jsp.
  11. If it returns "Application not Available" then go back to the Admin Console, right-click on struts-example and select Restart WebApp.
  12. Once it reports success, go back to the URL above and try again - it should work flawlessly.

Original by: Chris Assenza and dIon Gillard
Modifications by: Dan Miser and Stephen Schaub

Reply via email to