I made a few changes and posted to struts-users as well. Can someone test
and/or provide feedback...
Thanks,
Bob
----
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-example
.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-example
/
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:\xerces\xe
rces.jar
-Dweblogic.class.path=c:\weblogic\lib\weblogic510sp8.jar;C:\weblogic\license
;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
