Re: Struts installation notes - WebLogic 5.1

[Ted Husted <ne...@husted.com>]

** WEBLOGIC USERS ***

We're adding a installation page to the Struts documentation package.
If any can playtest Robert's notes, or has any other additional
comments, please let us know as soon as possible. 

This is an important way you can contribute to the Struts project. We
appreciate everyone's help!

*********** REPLY SEPARATOR  ***********

On 1/31/2001 at 10:50 AM rhayden@rdg.boehringer-ingelheim.com wrote:

>I have put together the following install notes for WebLogic 5.1 based
on my
>experience over the past few weeks. Any comments or suggestions? I am
>particularly disturbed by the fact that I can't get WL to deploy
unzipped
>web applications without including app-specific classes in the WL
classpath!
>Does anyone have another approach to this? Another problem I can't
seem to
>get around- Deployment of wars requires manually extracting the
resource
>file(s). Perhaps there is a way to get WL to find all files in the war
(and
>not just *.class)?
>
>BTW- the builds for the past few nights have a problem with the lowsrc
>property in class ImgTag (Thanks Carl for pointing out that problem
with the
>case in that method).
>
>
>-Bob
>
>~~~~~~~~~~~~~~
>
>WEBLOGIC 5.1 (service pack 8)
>
>(1) Obtain and install the Xerces XML parser (do not use the Sun
reference
>implementation). Put xerces.jar in your WebLogic system path.
>
>(2) Obtain and unpack the Struts binary distribution (this procedure
assumes
>it was extracted to C:\jakarta-struts).
>
>(3) Add an entry to weblogic.properties for each of the Struts web
>applications that you would like to configure. For example, to make
the
>struts-example application available, add the following line to
>weblogic.properties:
>
>weblogic.httpd.webApp.strutsexample=c:/jakarta-struts/webapps/struts-ex
ample
>.war
>
>(4) You do not need to include struts.jar or any of the application
specific
>classes in the WebLogic classpath, since this will be done
automatically
>(unless deploying an unpacked web archive- see below).
>
>(5) Start WebLogic server and point your web browser to the struts
>application. For example, to connect to the example application added
in
>step 3:
>
>http://localhost:7001/strutsexample
>
>* This example application depends on the Struts specific resource
file
>ApplicationResources.properties to be present on the classpath.
However,
>WebLogic only extracts *.class files from the archive so this file
will not
>be found, resulting in an error the first time it is needed- something
>similar to: javax.servlet.ServletException: runtime failure in custom
tag
>'message'. Steps 6 & 7 will need to be performed for this application,
and
>any other that relies on ApplicationResources.properties.
>
>(6)  Extract ApplicationResources.properties from the *.war file, and
>manually copy it to the respective package in the _tmp_war_ directory
>WebLogic created for this application. Again referring to the
struts-example
>application, this would be:
>
>c:\jakarta-struts\webapps\WEB-INF\_tmp_war_strutsexample
>
>(7) Restart WebLogic. You will now be able to run the application:
>
>http://localhost:7001/strutsexample
>
>
>* The above steps should be followed for applications deployed as
*.war
>files. For unpacked web applications, configuration involves adding
both
>struts.jar and /WEB-INF/classes to the WebLogic classpath. For this
reason,
>I would suggest deploying applications as war files to WebLogic.
However,
>the same example application can be successfully deployed in extracted
>format by modifying weblogic.properties (assuming the war was
extracted to
>directory webapps/struts-example):
>
>weblogic.httpd.webApp.strutsexample=c:/jakarta-struts/webapps/struts-ex
ample
>/
>
>And starting WebLogic with the updated WebLogic classpath. For
example:
>
>c:\jdk1.3\bin\java -ms16m -mx64m -classpath
>c:\weblogic\lib\weblogic510sp8boot.jar;C:\weblogic\classes\boot;c:\xerc
es\xe
>rces.jar
>-Dweblogic.class.path=c:\weblogic\lib\weblogic510sp8.jar;C:\weblogic\li
cense
>;C:\weblogic\classes;C:\weblogic\myserver\serverclasses;C:\weblogic\lib
\webl
>ogicaux.jar;C:\jakarta-struts\lib\struts.jar;C:\jakarta-struts\webapps\
strut
>s-example\WEB-INF\classes -Dweblogic.system.home=c:\weblogic
>-Djava.security.manager
-Djava.security.policy=c:\weblogic\weblogic.policy
>weblogic.Server



-- Ted Husted, Husted dot Com, Fairport NY USA.
-- Custom Software ~ Technical Services.
-- Tel 716 425-0252; Fax 716 223-2506.
-- http://www.husted.com/about/struts/

Re[2]: Struts installation notes - WebLogic 5.1

[Matthias Kerkhoff <ma...@BESToffers.de>]

>> ** WEBLOGIC USERS ***
>>
>> We're adding a installation page to the Struts documentation package.
>> If any can playtest Robert's notes, or has any other additional
>> comments, please let us know as soon as possible.

I would like to add the following points:

- Servlet and JSP-Reloading should be turned off.
  (First, you pay a performance penalty. Depending on the number of JSPs,
   the number of requests and the configured checking interval, the server
   will slow down.
   Second, with JSP- and Servlet reloading, one opens the door for various
   weblogic classloader problems, that are difficult to diagnose, difficult
   to handle and often lead to lost HTTP-sessions.)

- Set the name of the sessionid to JSESSIONID, if cookies are used for
  session tracking and to jsessionid, if sessions are URL-based.
  (There are additional problems related to URL-based sessions, caused from
   BEA's way to encode the session id (J2EE-incompatible) as query-param.
   Especially <bean:include> will not work with URL-based sessions yet.
   However, using the correct session name solves at least some problems.)

- Configure the JSP-Servlet registration in weblogic.properties for
  maximum J2EE-compliance and/or for maximum performance.

  The JSP-Servlet supports some initialization parameters that can be
  customized to get best performance, maximum compliance or (as shown
  below) easier debugging:

  weblogic.httpd.initArgs.*.jsp=\
       pageCheckSeconds=-1,\
        setEmptyStrings=false,\
         compileCommand=./_jspCompiler_.cmd,\
             workingDir=/weblogic/myserver/tmp_classfiles,\
          keepgenerated=true,\
                  debug=true,\
                verbose=true
                
  In the above example, the batch file (_jspCompiler_.cmd) invokes jikes
  which results dramatically reduced startup times (jikes is about three
  times faster than javac.) The batchfile contains only a single line:

  @jikes -g -nowarn %*

  The next cinfiguration could be used when all tests have been done and
  speed is the major concern ...
  
  weblogic.httpd.initArgs.*.jsp=\
       pageCheckSeconds=-1,\
        setEmptyStrings=false,\
         compileCommand=./_jspCompiler_.cmd,\
             workingDir=/weblogic/myserver/tmp_classfiles,\
          keepgenerated=false,\
                  debug=false,\
                verbose=false

  ... together with ...

   @jikes -O -nowarn %*

   Weblogic supports similar settings through <context-params> in web.xml,
   (Please read the latest documentation at the BEA website for details.)

-- 
Matthias                        (mailto:make@BESToffers.de)

Re: Struts installation notes - WebLogic 5.1

[Wong Kok Wai <wo...@pacific.net.sg>]

The only correction needed is point one where JAXP can be used. All other
points are what I would state too.

Ted Husted wrote:

> ** WEBLOGIC USERS ***
>
> We're adding a installation page to the Struts documentation package.
> If any can playtest Robert's notes, or has any other additional
> comments, please let us know as soon as possible.
>
> This is an important way you can contribute to the Struts project. We
> appreciate everyone's help!
>