Hi, 

> From: [EMAIL PROTECTED]
>
> Can anyone direct me to a reference on how to install Axis on 
> BEA WebLogic?

I just did this with axis-beta-3 on BEA WebLogix 6.1 SP2.  There is 
one big issue with this particular version:  When deploying a web 
application, the BEA server "validates" (for whatever reason) the 
MANIFESTs that it finds in any jar-file, and this fails for two
that are shipped with axis: 

  commons-logging.jar     and
  log4j-1.2.4.jar

I think this bug appeared in 6.1 SP2 and is fixed in 6.1 SP3, but 
I'm not sure.  No infos about 7.0 yet.

Threre are two workarounds for this problem:

  - Move the appropriate jars into some other directory and include
    them into the servers CLASSPATH.  This works, since the BEA server
    only investiages MANIFESTs of jars that it find in WebApplications
    (aka: WEB-INF/lib), this is not done for other jars.

  - Unpack the approrpiate jars, remove the META-INF directories and
    repack them with the -M option of the jar tool (probably using a
    different name).  Then put them into axis/webapps/axis/WEB-INF/lib
    and remove the "offending" jars.

After that you should be able to deploy axis as every other web 
application:

  a) Put the axis directory from axis/webapps into the "applications" 
     directory of your server and restart the server.

  b) Open the Server Console and select "web applications", then "axis",
     then the "Targets" tab.

  c) Add the appropriate server (I did all this in "examples", so there
     was the "exampleServer" available.

  d) Now http://localhost:7001/axis/happyaxis.jsp should work.

  e) To make the "Administer Axis" link work, you have to add a 
     servlet-mapping to the deployment descriptor (web.xml) of 
     axis:
       servlet-name:   AdminServlet
       url-pattern:    /servlet/AdminServlet
     (Don't do this with the BEA console, this screwed up my setup 
     several times.  Do it manually: stop the server, edit the web.xml,
     restart the server.)

Deploying axis as war file did not work yet, since it tries to access
the file "null/server-config.wsdd".  I think this needs some more tuning ;-)

Hope this helped a little bit

Regards

  Jonas

--
    Jonas Rathert

    PLATINION GmbH
    A Company of the Boston Consulting Group

    Im Mediapark 5, 50670 Cologne/Germany
    Tel.    +49 221. 58 95 83 04
    Fax     +49 221. 589 20 51
    mailto:[EMAIL PROTECTED]
    http://www.platinion.de/

Reply via email to