You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@xml.apache.org by "Braginsky, Leo" <lb...@akamai.com> on 2001/01/25 20:07:22 UTC
RE: Running samples with WebLogic 5.1
Hi all
Below are my observations of my recent ordeal of deploying Apache SOAP 2.0
with WebLogic 5.1 server. I hope these notes will help those who embark on
this tortuous path to avoid the pain and frustration I had to go through in
the past 3 days.
1) The jar files, soap.jar and xerces.jar have to be present in both
CLASSPATH and WEBLOGIC_CLASSPATH.
2) The directory where the sample code resides must also be added to both
classpaths
3) The rpcrouter servlet must be registered in weblogic.properties in this
fashion:
weblogic.httpd.register.soap/servlet/rpcrouter=org.apache.soap.server.http.R
PCRouterServlet
weblogic.httpd.initArgs.soap/servlet/rpcrouter=ServicesStore=DeployedService
s.ds
4) The service must be deployed. One way to deploy it is my using the admin
GUI tool, following the instructions that come with Apache SOAP 2.0 package
and also, http://www-106.ibm.com/developerworks/library/ws-peer2/?dwzone=ws
<http://www-106.ibm.com/developerworks/library/ws-peer2/?dwzone=ws> .
Another was is to edit an XML file, called deploymentdescriptor.xml (they
can be found in each sample directory) and deploy it by doing this:
java org.apache.soap.server.ServiceManagerClient
http://hostname:port/soap/servlet/rpcrouter
<http://hostname:port/soap/servlet/rpcrouter> deploy foo.xml
Ones this is done, the service deployment info is written out to a file
called DeployedServices.ds, which lives in d:\weblogic root.
5) THe debug tool is great. Below is an excerpt of a message sent to me by
Peter Go who was helping me to get myself set up
C:\>java org.apache.soap.util.net.TcpTunnelGui
Usage: java TcpTunnelGui listenport tunnelhost tunnelport
where: <listenport> is a brand new port (not being used)
<tunnelhost> e.g. localhost
<tunnelport> is the port that your webserver is defined on
Let's say your client talks to your server via http://localhost:7501
<http://localhost:7501> , that
is, it sends commands thru port 7501. tcptunnel wants to come between you
and the server, so he can echo the traffic to you. So you need to pick a
<listenport> for tcptunnel (e.g. 7507), and change your client to talk thru
it by instead going to http://localhost:7507 <http://localhost:7507> .
tcptunnel will route HTTP
traffic to port 7501. Your server responds to 7507 (tcptunnel) who then
routes it back to your client. It's really cool. So in this case, run
tcptunnel as:
java org.apache.soap.util.net.TcpTunnelGui 7507 localhost 7501
- leo