Return-Path: 
 <axis-user-return-17931-apmail-ws-axis-user-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-user-archive@ws.apache.org
Received: (qmail 32218 invoked by uid 500); 26 Aug 2003 18:34:50 -0000
Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
list-help: <mailto:axis-user-help@ws.apache.org>
list-unsubscribe: <mailto:axis-user-unsubscribe@ws.apache.org>
list-post: <mailto:axis-user@xml.apache.org>
Delivered-To: mailing list axis-user@ws.apache.org
Received: (qmail 32173 invoked from network); 26 Aug 2003 18:34:49 -0000
content-class: urn:content-classes:message
Subject: RE: SOAPMonitor
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Date: Wed, 27 Aug 2003 00:02:06 +0530
Message-ID: <CC8C22639E8BC74E9D24C23B368CDF5F019090EF@blrsnrmsg02.aditi.tech>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: SOAPMonitor
Thread-Index: AcNr+ns3pstp2Z40SeWr8DqfdTHdqwAAyxpw
From: "Harsh Raju Chamarthi" <harshrc@aditi.com>
To: <axis-user@ws.apache.org>
X-OriginalArrivalTime: 26 Aug 2003 18:32:11.0385 (UTC)
 FILETIME=[5D134690:01C36C00]
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

1.Compile your SoapMonitorApplet.java file(path normally would be: =
\webapps\axis\SoapMonitorApplet.java)
2.Make changes to ur server-config.wsdd file(manual changes):
	Here is a clipped sample server-config.wsdd that will help you!
	Add the handler element tag and service element tag for SoapMonitor!
=09


<?xml version=3D"1.0" encoding=3D"UTF-8"?>
<deployment xmlns=3D"http://xml.apache.org/axis/wsdd/" =
xmlns:java=3D"http://xml.apache.org/axis/wsdd/providers/java">
 <globalConfiguration>
	....
 </globalConfiguration>
 <handler name=3D"soapmonitor" =
type=3D"java:org.apache.axis.handlers.SOAPMonitorHandler">
  <parameter name=3D"wsdlURL" =
value=3D"/axis/SOAPMonitorService-impl.wsdl"/>
  <parameter name=3D"namespace" =
value=3D"http://tempuri.org/wsdl/2001/12/SOAPMonitorService-impl/"/>
  <parameter name=3D"serviceName" value=3D"SOAPMonitorService"/>
  <parameter name=3D"portName" value=3D"Demo"/>
 </handler>
 <handler name=3D"LocalResponder" =
type=3D"java:org.apache.axis.transport.local.LocalResponder"/>
 <service name=3D"Version" provider=3D"java:RPC">
  <parameter name=3D"allowedMethods" value=3D"getVersion"/>
  <parameter name=3D"className" value=3D"org.apache.axis.Version"/>
 </service>
 <service name=3D"SOAPMonitorService" provider=3D"java:RPC">
  <parameter name=3D"allowedMethods" value=3D"publishMessage"/>
  <parameter name=3D"className" =
value=3D"org.apache.axis.monitor.SOAPMonitorService"/>
  <parameter name=3D"scope" value=3D"Application"/>
 </service>
 <transport name=3D"local">
  <responseFlow>
   <handler type=3D"LocalResponder"/>
  </responseFlow>
 </transport>
</deployment>


3: Now that soapmonitor handler has been configured.
Make manual changes to the deploy.wsdd file of the webservice you want =
to observe(monitor).
example:
<deployment name=3D"test" xmlns=3D"http://xml.apache.org/axis/wsdd/"=20
            =
xmlns:java=3D"http://xml.apache.org/axis/wsdd/providers/java"
            xmlns:xsi=3D"http://www.w3.org/2000/10/XMLSchema-instance">
   <service name=3D"MessageService" style=3D"message">
    <parameter name=3D"className" =
value=3D"samples.message.MessageService" />
    <parameter name=3D"allowedMethods" value=3D"echoElements" /> =20
    <requestFlow>
       <handler type=3D"soapmonitor"/>
    </requestFlow>
    <responseFlow>
       <handler type=3D"soapmonitor"/>
    </responseFlow>
  </service>
</deployment>

4.deploy and open:
http://localhost:8080/axis/SOAPMonitor
to monitor;)

Hopefully this should do!
if it does not , check ur server-config.wsdd file again!
do tell me if this doesnt work.
tscus!
hrc

-----Original Message-----
From: Mark Pfeifer [mailto:pfeif4@yahoo.com]
Sent: Tuesday, August 26, 2003 8:05 PM
To: axis-user@ws.apache.org
Subject: SOAPMonitor


I know many people have posted issues and questions
about the SOAPMonitor, but I must be missing something
simple.=20

I have the applet working and have been able to get
the monitor to get the request by creating a
server-config.wsdd file with the listing below.=20

However the request does not seem to be passed along
and I get no services found issues.  I see from the
postings that the server-config file should be created
automatically, but no such luck. The one web page I
saw with instructions is for 1.0 and not 1.1.

Any ideas?=20

Thanks,
Mark


<deployment xmlns=3D"http://xml.apache.org/axis/wsdd/"
xmlns:java=3D"http://xml.apache.org/axis/wsdd/providers/java">
   =20
  <globalConfiguration>
    <requestFlow>
      <handler name=3D"soapmonitor"
type=3D"java:org.apache.axis.handlers.SOAPMonitorHandler"/>
    </requestFlow>
    <responseFlow>
      <handler name=3D"soapmonitor"
type=3D"java:org.apache.axis.handlers.SOAPMonitorHandler"/>
    </responseFlow>
</globalConfiguration>

</deployment>

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com