Logging of SOAP messages at server side, Axis 1.2, NO SoapMonitor / TCPMon.

Hello,
I�m looking for a way to log all SOAP communication at a Axis Server.
I want to log the messages into my logdatabase or to files at least.
I am not interrested af SOAPMonitor or TCPMonitor, those are good tools but not for my purposes.
Anyone can help me out?

Hi,
You should have a look at the Axis users guide, under "More deployment - Handlers and Chains". This part describes a LogHandler to be included in the WSDD that basically logs information about the requests and/or responses.
Also look at the class org.apache.axis.handlers.LogHandler

Similar Messages

How to send Subtopic Message From Server-Side to Client ?

I’m new at flex and i have a new question about Flex
Message Service.
How to send messages from Server-Side Java Code with
Subtopic?
For example.
I customed a Flex Message Adapter in Tomcat Server , with
this Adapter , i can send message to Client with following code .
---------------------Send message to Client------------
MessageBroker msgBroker =
MessageBroker.getMessageBroker(null);
String clientID = UUIDUtils.createUUID(false);
AsyncMessage msg = new AsyncMessage();
msg.setDestination("CustomMsgServiceDes");
msg.setClientId(clientID);
msg.setMessageId(UUIDUtils.createUUID(false));
msg.setTimestamp(System.currentTimeMillis());
msg.setBody(clientID + "this is my message from server! \n");
msgBroker.routeMessageToService(msg, null);
---------------------Send message to Client------------
But i want send a message that have Subtopic to the Client ,
How to do ?
Thank you for reply.

There's a white paper that talks about this subject -
http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=8f1eb6ea

How can i dispaly an Error Message from Server Side To form

Hi All,
How can i dispaly an Error Message from Server Side To form side .
i try several ways nothing succed.
i put the error in stack and after call the procedure from form i added
Qms$Trans_Errors.Display_Messages;
and because it is an error not informantional error the error screen displayed and enter
in infinite loop acts like flashing .
can any one help me please i use C/S Headstart6i and Designer 6i
thanks alot
radi

hi,
thanks alot lauri.
yr code work only using information message but in error message its still the same .
the error window still flash and enter in infinite loop of executeing the same triggers.
thanks again
radi

[ASK] Duplicated Error Message on server side validation

I want to use server-side validation instead of client-side validation for my input form as suggested by John Stageman, by:
1). set required=false
2). set showRequired=true
3). Ensure that the attribute is mandatory in the model layer
It seems to work, except that the error message displayed by <af:messages> is kinda weird bcause they are repeated, for example;
Attribute Attr1 in MyAM.MyView is required
Attribute Attr2 in MyAM.MyView is required
- Attribute Attr1 in MyAM.MyView is required
- Attribute Attr2 in MyAM.MyView is required
Attribute Attr1 in MyAM.MyView is required
Attribute Attr2 in MyAM.MyView is requiredand the number of reduplication seems growing each time I click the Save button.
besides, for "value required" validation, the component related error message is not displayed (the red message under the component).
Any clues?
Thanks..
@John : I decide to open it as new thread bcause it seems to be different question..

Hi, thanks for your fast response Frank,
My page has several iterator binding and I have tried to set all of their refresh options as you suggested, but the problem still remains the same T_T
Maybe somewhere, someone has put some additional manual validation, bcause it is a team project, I still dont know where to find those phantom codes..
Regards,
from island of gods

Logging inbound SOAP Message in SALT 2.0

Is there a way to log the inbound SOAP message [valid or invalid] in SALT 2.0. We have a situation where the client is sending a SOAP message that we want to be able to intercept and log. The client is reporting that the SALT gateway is reporting an invalid SOAP message, we want to be able to log this message so we can let them know what we are receiving.
Thanks

Ram--
Everywhere in XI, the acronym "LCR" is synonymous with "SLD", System Landscape Directory. It seems like it may be a term they used early on, or maybe it's the German equivalent. The LCR acronym is sprinkled throughout SAP's underlying code.
In your error message, it's complaining about the Business System entry in the SLD.
My first thought would be that either the source or target business system is not configured in the SLD, or you haven't defined the business system properly in the SOAP adapter configuration. See the "XI20 Adapter Engine" manual for instructions on how to configure the SOAP adapter.
NOTE: You may be able to configure the SLD to make this solution work on your own, but for long-term usage, you're going to want an expert to model your system landscape and configure the SLD properly.
--Dan King
Capgemini

Generating feedback messages on server-side vs client-side?

Hello,
I am maintening a client/server app (Swing client, no Web pages), basically an order processing system. The biggest part of it is to verify the conformity of orders to a set of business rules.
As usual, some of the verification can be made early on the client-side, but most of the verification work is done on the server-side. My problem is, I don't find a very satisfactory way to generate the user feedback to be displayed to the user.
If I generate them as Strings (or HTML Strings) on the server, where the rules are checked, this constrains the way these can be displayed on the client, and makes maintenance of the human-readable strings awkward and risky (e.g. localization, or restructuring the messages, like sorting them by severity vs by affected entity).
If I generate them on the client, I need a class to vehicle the diagnosis form server to client, and this class and its usage tends to become awkward in itself.
Concretely:
The initial version generated human-readable strings on the server, which assumed the messages would be displayed as strings in a JOptionPane.
Moreover, the logic evolved to distinguish between Info, Warning and Error messages, to be displayed in different colors of course, so the Strings evolved into HTML Strings, still generated on the server.
Do you think this approach is safe?
I'm afraid a simple maintenance of the strings (like, sorting the errors by severity vs by affected entity, filtering the strings,...) becomes a server-side development, which is a bit more risky (I would have to review code ownership policies, VCS and code-sharing policies,... to let less experienced staff maintain the darn error Strings).
Moreover, if the client app evolve to display the errors in complex widgets (colors in a tree/table, with tooltips), the server-side generated HTML strings would be constraining : coloring or tooltipping Tree nodes would now mean parsing the String to extract the "error level" or the "affected entity", which is quite inelegant and inflexible.
My current idea was then to use a collecting parameter to collect validation messages on the server, and traverse them on the client:
I designed a naive ErrorList class, with methods such as addInfo(String), addWarning(String), addError(Strin), and the corresponding getErrors() and hasErrors()/hasWarnings() methods. I can then generate the Strings (or whatever widget fits better, such as a table) on the client side. Moreover, I can add the client-side messages to the bag...
All nice and well, but the customer requested that the error messages be formatted such as "The profile <profile name in bold> does not allow you to order service <service name in italics>".
To format that on the client, my ErrorList class should evolve so that for a given message, I know that the error is of type ("incompatibility between profile and service", that the service is X and the prodile is Y).
That forces me to add in some API (shared by the client and server) the list of error types, and the data each error type requires.
I can evolve my ErrorList API to break up messages into a DTO giving (type, affected entity, arg1, arg2,...), but anyway the server and client have to agree on what is arg1, etc... which is a hidden coupling.
Do you use and recommend such an approach for server-to-client feedback: a collecting parameter in which the server puts the "errors", and that the client traverses to display the messages)? In particuler, isn't the coupling hard to maintain?
Thansk in advance,
J.

Presumably you are not over-engineering in that you
know that localization is a problem rather than that
in all possible worlds in might be.I appreciate your delicate questioning... I definitely have read much ruder ways to say YAGNI to a poster...
I do know that the customer will knit-pick to reword and reformat the messages. But I won't need to translate the messages to other locales. In that regard, I ackowledge my usage of the term localization is a bit liberal, but I think I should to extract the messages from the code, to be able to maintain them separately - keeping only experienced staff's hand in the server's core.
That is actually my question 1): from experience, is it worth the trouble to separate code and human-readable text, knowing that the text WILL have to be maintained?
Question 2 is about how to implement this.
In particular, the built-in MessageFormat templating engine, though originally introduced for i18n, actually suits my needs (including MessageFormat-built messages) and developing or using any other templating engine would probably be an overkill.
Given that there are two types of messages.
1. Fixed
2. Parameter driven.
In both cases you need to return an id which
identifies the message. The client has a locale
specific resource source which has a matching id.
From there a string is derived.
If the error requires parameters then the string has
formatting values in it and it s written with the
returned parameters. See java.text.MessageFormat.Yes. In some cases I don't know yet whether parameters will be displayed. I can conservatively assume the message requires a MessageFormat, and give all parameters (in my case, use rname, profile name, command id, service name, order date,...), whether thay are displayed or not in the final message.
Be warned you MUST deal with the possibility that a
id does not exist in the client, if so have a default
message that displays the id and any parameters.Good point.
"The customer name field can not be longer than 15
characters".
In the above the "15" would a parameter.Yes. The trouble is, you have to document somewhere (Sun suggests in the resource bundle file), that for error id #123456, the number of characters in in the '{0}', or in the {6}. I don't feel confident with that (this is the "coupling" part in my question 2�).
Thanks for your advices.

Error message during server side process

Bonjour,
In my application's method i call a standard r/3 function for created an order in IS-MEDIA.
In certain cases this function send an message id type 'E'.
This message causes the error: HTTP 500 - on my BSP page.
Is-it possible to avoid this ?
Best regards.

check this thread
https://forums.sdn.sap.com/click.jspa?searchID=3157097&messageID=70898

Logging SOAP messages

I need help on how to use handlers in Weblogic Workshop web services. I have the following logging handler from the bea documentation site.
Now, if I want to log my SOAP messages on the server side, do I just need to put the annotation:
* @jws:handler operation="handler.ConsoleLoggingHandler"
at the top of my JWS file? If that is the case, I don't see any messages being logged. Any help will be greatly appreciated.
Thanks.
gtata
package handler;
import java.util.Iterator;
import javax.xml.rpc.handler.MessageContext;
import javax.xml.rpc.handler.soap.SOAPMessageContext;
import javax.xml.soap.SOAPElement;
// for readability, using weblogic API instead of javax.xml.rpc.handler.GenericHandler
// See http://edocs.beasys.com/wls/docs81/webserv/interceptors.html#1060763
import weblogic.webservice.GenericHandler;
* Purpose: Log all messages to the Server console
public class ConsoleLoggingHandler extends GenericHandler
* Handles incoming web service requests and outgoing callback requests
public boolean handleRequest(MessageContext mc)
logSoapMessage(mc, "handleRequest");
return true;
* Handles outgoing web service responses and incoming callback responses
public boolean handleResponse(MessageContext mc)
this.logSoapMessage(mc, "handleResponse");
return true;
* Handles SOAP Faults that may occur during message processing
public boolean handleFault(MessageContext mc)
this.logSoapMessage(mc, "handleFault");
return true;
* Log the message to the server console using System.out
protected void logSoapMessage(MessageContext mc, String eventType)
try
System.out.println("*****************************");
System.out.println("Event: "+eventType);
System.out.println("Endpoint Method: " + getMethodName(mc));
System.out.println("Soap message is: \n " +
com.bea.wlw.runtime.jws.soap.util.SAAJUtil.SOAPPart2String(
((SOAPMessageContext)mc).getMessage() ) + "\n");
System.out.println("*****************************");
catch( Exception e )
e.printStackTrace();
* Get the method Name from a SOAP Payload.
protected String getMethodName(MessageContext mc)
String operationName = null;
try
SOAPMessageContext messageContext = (SOAPMessageContext) mc;
// assume the operation name is the first element
// after SOAP:Body element
Iterator i = messageContext.
getMessage().getSOAPPart().getEnvelope().getBody().getChildElements();
while ( i.hasNext() )
Object obj = i.next();
if(obj instanceof SOAPElement)
SOAPElement e = (SOAPElement) obj;
operationName = e.getElementName().getLocalName();
break;
catch(Exception e)
e.printStackTrace();
return operationName;
}

You can use the logging and tracing functionality to write log statements anywhere in BPEL. refer http://wiki.open-esb.java.net/Wiki.jsp?page=LoggingFromWSBPELActivityInABusinessProcess . But you should keep in mind these are not soap messages that you log. They will be abstract WSDL message instances. If you want to log specifically the soap messages you need the support in HTTP-BC.
If you turn on logging you should see the line number of BPEL where it fails. That should give you some indication. I am not 100% sure, but in the logs, we should be logging the variable which was not initialized. I can't think of any other way to find out which variable caused this exception.
-Kiran Bhumana

Logging soap messages invoked by BPEL process

Hi,
Is there any way to log the SOAP messages sent from an invoke? A receive?
Also, is there a way to capture which variable is throwing an uninitializedVariable exception?
J

You can use the logging and tracing functionality to write log statements anywhere in BPEL. refer http://wiki.open-esb.java.net/Wiki.jsp?page=LoggingFromWSBPELActivityInABusinessProcess . But you should keep in mind these are not soap messages that you log. They will be abstract WSDL message instances. If you want to log specifically the soap messages you need the support in HTTP-BC.
If you turn on logging you should see the line number of BPEL where it fails. That should give you some indication. I am not 100% sure, but in the logs, we should be logging the variable which was not initialized. I can't think of any other way to find out which variable caused this exception.
-Kiran Bhumana

How to get SOAP Message while Request in WebService.. ?

i am working on Web Logic WebService. I have created Web service and deployed into server.
But now is there any ways to get the SOAP Message while request because i want to add some headers to the my SOAP Message before it sent to the backend.
SOAPMessageContext smc=null;
SOAPMessage soapMsg = smc.getMessage();
System.out.println("SOAP MESSAGE :"+soapMsg);
But I am getting NullPointerException.
any Help ??...
ThankQ.
Ajay

Hi
In your code the NullPointerException is expected as the message context is null and not initialized before you call getMessage method on it.
You can use soap handlers (client/server side handlers) to add the headers to the message before it is sent to the server.
Soap handler has methods like below in which you can add the headers.
* Handles incoming web service requests and outgoing callback requests
public boolean handleRequest(MessageContext mc)
System.out.println("Soap message is: \n " +
((SOAPMessageContext)mc).getMessage() + "\n");
return true;
More docs at http://e-docs.bea.com/wls/docs100/webserv_adv/handlers.html
Vimala-

Server side redirect with 4.5.1 and Netscape Enterprise Server

          Is it possible to have a servlet running under WL 4.5.1 to perform a server
          side redirect ala CGI?
          Here's my config:
          web server: Netscape Enterprise Server 3.6 on solaris, with weblogic
          plugin
          servlet runner: WL 4.5.1 on different host from ES.
          Here's what I want to happen:
          1) HTTP GET from browser to enterprise server
          2) forwarded by plugin to servlet
          3) servlet logs some activity to an application log file, and sends a
          server side redirect to enterprise server
          4) Enterprise server returns the file identified by the rediect directly
          to the client.
          This is possible with enterprise server and CGI, because the ES CGI code
          checks the return stream from the CGI program for "Location: <some url>". If
          it see's that, it tries to locally resolve that URL as the client had asked
          directly for that URL. I think this would only be possible with WL if the WL
          NSAPI plug in supported a server side redirect feature. Anyone know status
          of that? Or might ES support something like this depending on the order of
          the objects in obj.conf?
          Here's what I've tried in the servlet:
          res.setHeader("Location:", location);
          res.setContentType("magnus-internal/redirect");
          res.setStatus(302);
          This just sends an HTTP tempoary new location to the client for a client
          side redirect. Client side redirect is not desirable because it doubles the
          HTTP traffic.
          Another option would be to read the file I want to redirect to from inside
          the servlet and return it from the servlet, but that is not desirable
          because I want to have ES serve the file - thats it's job, it caches, less
          network traffic (between our servers), etc.
          Server side redirect is very useful feature and not that uncommon for web
          applications, so if WL does not support it now, I will probably put in a new
          feature request.
          Thanks for your help
          Mark Johnson.


Why not just use the proxy servlet to redirect to your netscape server? That
          does it on the server side!
          -russell
          Mark Johnson wrote:
          > I belive that sendRedirect performs a client side rediret, not a server
          > side redirect.
          >
          > Guy Tal <[email protected]> wrote in message
          > news:[email protected]...
          > > public void doGet(HttpServletRequest req, HttpServletResponse res) ...
          > > ...
          > > res.sendRedirect("http://destination");
          > > ...
          > >
          > > Guy
          > >
          > > Mark Johnson <[email protected]> wrote:
          > >
          > > > Is it possible to have a servlet running under WL 4.5.1 to perform a
          > server
          > > > side redirect ala CGI?
          > >
          > > > Here's my config:
          > > > web server: Netscape Enterprise Server 3.6 on solaris, with weblogic
          > > > plugin
          > > > servlet runner: WL 4.5.1 on different host from ES.
          > >
          > > > Here's what I want to happen:
          > > > 1) HTTP GET from browser to enterprise server
          > > > 2) forwarded by plugin to servlet
          > > > 3) servlet logs some activity to an application log file, and sends
          > a
          > > > server side redirect to enterprise server
          > > > 4) Enterprise server returns the file identified by the rediect
          > directly
          > > > to the client.
          > >
          > > > This is possible with enterprise server and CGI, because the ES CGI code
          > > > checks the return stream from the CGI program for "Location: <some
          > url>". If
          > > > it see's that, it tries to locally resolve that URL as the client had
          > asked
          > > > directly for that URL. I think this would only be possible with WL if
          > the WL
          > > > NSAPI plug in supported a server side redirect feature. Anyone know
          > status
          > > > of that? Or might ES support something like this depending on the order
          > of
          > > > the objects in obj.conf?
          > >
          > > > Here's what I've tried in the servlet:
          > > > res.setHeader("Location:", location);
          > > > res.setContentType("magnus-internal/redirect");
          > > > res.setStatus(302);
          > >
          > > > This just sends an HTTP tempoary new location to the client for a client
          > > > side redirect. Client side redirect is not desirable because it doubles
          > the
          > > > HTTP traffic.
          > >
          > > > Another option would be to read the file I want to redirect to from
          > inside
          > > > the servlet and return it from the servlet, but that is not desirable
          > > > because I want to have ES serve the file - thats it's job, it caches,
          > less
          > > > network traffic (between our servers), etc.
          > >
          > > > Server side redirect is very useful feature and not that uncommon for
          > web
          > > > applications, so if WL does not support it now, I will probably put in a
          > new
          > > > feature request.
          > >
          > >
          > > > Thanks for your help
          > >
          > > > Mark Johnson.
          > >
          > >
          > >
          > >
          > >
          > >
          > >
          > >
          Russell Castagnaro
          Chief Mentor
          SyncTank Solutions
          http://www.synctank.com
          Earth is the cradle of mankind; one does not remain in the cradle forever
          -Tsiolkovsky

Logging the SOAP request/response from rules engine

Hi All,
We would like to log the soap requests and response from the rules engine.
The determinations-server.war is deployed on a weblogic server and we are not using seibel connector.
Is it possible to log the soap messages for debugging purpose.
Thanks,
Suraj

Hi All,
We would like to log the soap requests and response from the rules engine.
The determinations-server.war is deployed on a weblogic server and we are not using seibel connector.
Is it possible to log the soap messages for debugging purpose.
Thanks,
Suraj

Traping the SOAP message before making the call.

We are using the axis for Web services, it works fine,
Here is my question, before the call go out to third party services, I need to log the SOAP message into our logging system. How would I trap the message?
Thanks in advance.
-APK.

I tried to achieve that using the following:
http://e-docs.bea.com/wls/docs81/webserv/interceptors.html#1072668
But it doesn't seem to work. try it!!
-k

Need help: Using Axis, how to log all incoming and outgoing soap messages??

Hi all,
I have a big problem which probably got a simple solution:
I need to log all incoming messages, and all outgoing messages (request - response).
I do not want any other information than this. I have tested the log4j and all I get is a LOT of debug information but not the messages as the arrive/leave the system.
Please help me with this since it is a big problem for me that I cant debug my applications in the way I want...

I would preffer not to use the tcpmonitor on my server, don�t want to change ports, etc.. I want a better solution which I can choose myself when to use, and that can directly log to my log-database...
Sorry but tcpmonitor is not a solution here, even though it is a good monitor program

JWSDP1.4 Access the SOAP Message in an RPC server

hi i am new to web services... i have created RPC using JSWDP 1.4.
I used the wscompile and wsdeploy tool to create the WSDL and server side of the web service.
but because of a requirement change now i have to get the SOAP message Header and verify the client details (log who is using my service). How can i access the SOAP header??

Make a backup then edit this file,
TomcatRoot: ./shared/classes/com/tarantella/tta/webservices/client/apis/Resources.properties
Edit all locations to point to https://localhost:443

Logging of SOAP messages at server side, Axis 1.2, NO SoapMonitor / TCPMon.

Similar Messages

Maybe you are looking for