Resending SOAP messages that failed

Hi All
I have a SOAP -> XI -> SOAP service.
I receive lots of messages at the same time from the sender webservice, when delivering to the receiver webservice a couple of messages will go into this webservice and some will say to be delivered, and then after a while turn to system error. Is there a way that I can get these messages to resend (or send till successful) because the error it comes back with when not getting into the receiver webservice is - soap fault: SOAP header ReliableMessaging was not understood. The messages should be fine I jsut don't think that the receiver side has a queue that can handle the load.....
Thanks
Clinton

Hi Udo
Thanks for your reply
The message that I am getting inside the AFW queue (get there with this url - http://sapxi:58000/MessagingSystem/receive/AFW/XI) and the message that i get is this -
2006-08-09 11:10:47 Success SOAP: request message entering the adapter
2006-08-09 11:10:47 Success SOAP: completed the processing
2006-08-09 11:10:49 Success The message was successfully received by the messaging system. Profile: XI URL: http://sapdxi:58200/MessagingSystem/receive/AFW/XI
2006-08-09 11:10:49 Success Using connection AFW. Trying to put the message into the receive queue.
2006-08-09 11:10:49 Success Message successfully put into the queue.
This message is inside the Message Monitor with <b>To be delivered</b> status.
Is there a way to not just let the message be put into the queue but let it send to the the webservice.
Thanks
Clinton

Similar Messages

Accepting a SOAP message that contains fault elements

Hi,
I am trying to create a webservice that will accept a valid soap messages that
contains faults. Actual functionality required is to accept a valid soap message
with or without faults. For this, I created separate methods in my java class
(one for normal flow and one that will handle fault elements) that implements
my web service. I need to manipulate the soap message for both cases. Hence, I
created separate handlers to do this task. I created two handler chains in my
web-services.xml one for handling soap messages that contains faults and one for
handling soap messages that doesn't contain faults. The web services was successfully
deployed and works fine for soap messages that doesn't contain fault. But, if
I send a soap message with faults the client (that calls my webservice) is not
even hitting my web service. It gets a HTTP
500. Can anybody help me on this ?
Thanks,
Ganesh Balachandran

Hi Ganesh,
Which version of weblogic server you are using? Can you turn on verbose in
client side? You can give a "-Dweblogic.webservice.verbose=true" to client
side JVM. We need to see what your soap message with fault looks like.
Thanks,
-Neal
"Ganesh" <[email protected]> wrote in message
news:[email protected]..
>
Hi,
I am trying to create a webservice that will accept a valid soap messagesthat
contains faults. Actual functionality required is to accept a valid soapmessage
with or without faults. For this, I created separate methods in my javaclass
(one for normal flow and one that will handle fault elements) thatimplements
my web service. I need to manipulate the soap message for both cases.Hence, I
created separate handlers to do this task. I created two handler chains inmy
web-services.xml one for handling soap messages that contains faults andone for
handling soap messages that doesn't contain faults. The web services wassuccessfully
deployed and works fine for soap messages that doesn't contain fault. But,if
I send a soap message with faults the client (that calls my webservice) isnot
even hitting my web service. It gets a HTTP
500. Can anybody help me on this ?
Thanks,
Ganesh Balachandran

Resend Message that fails in adapter engine but shows success in sxmb_moni

Hello SDN!!
We are testing sending soap requests out via SSL. We are using a BEA as a pass through server for SSL encryption only.
The scenerio is to send a message from SAP to PI 7.1 to BEA (SSL enc) to Receiving System. We successfully connect to BEA (only used as a pass-through) but the connection to Receiving System does not work. This returns an error to our adapter engine.
My question is this, Since SXMB_MONI shows the message as successful, but the adapter engine is showing an error. What is the best way for
1. Monitor the errors, (I only see where you can monitor the type of adapter only)
2. Resend the message, since it shows valid in SXMB_MONI, it won't let me resend.
Any help will be greatly appreciated and awarded
Cheers
Devlin

1. Once the message is in successful status in moni, the best way to monitor becomes RWB -> Message Monitoring.
2. For adapter engine related errors, you may resend the data manually using the resend option in the Message Monitoring. Otherwise, for automatic retry of messages, you may change the default settings.
Regards,
Prateek

GWcheck errors for messages that failed to archive

There are numerous errors in the GWCheck logs for messages failed to
archive for one user. The cause is usually insufficient disk space in the
archive path. I moved his archive folder to a place with more disk space
sometime last year. It seems that the messages that were unable to archive
at the time are lost in limbo. They are no longer in the user's inbox and
are not in the archive. I spoke with the user and he stated that the
messages are no longer important.
The errors in gwcheck look like this:
Error 83- Item failed to archive
- Subject: Fwd: Dayton VA emergency renovation
- From: John Hall
- Date: Nov 6, 2009 - 1:47 pm
- First archive attempt date: Jul 25, 2011
- Number of archive attempts: 1
- Error number on last Archive attempt: 0x8204
9938 ITEM_RECORD check
Error 83- Item failed to archive
- Subject: Fwd: Building 700 Elevator and Building 701 Demoliton Facade/
Canopy Work
- From: John Hall
- Date: Jan 6, 2010 - 1:29 pm
- First archive attempt date: Jul 25, 2011
- Number of archive attempts: 1
- Error number on last Archive attempt: 0x8204
10585 ITEM_RECORD check
....ETC...
I found TID 7009495 that states the following:
Resolution
WARNING: THE FOLLOWING RESOLUTION WILL DELETE MAIL
GroupWise POA code level minimum must be 7.0.4 or 8.0.2HP2.
Run the following options on one or more users before running it against
an entire post office.
1) Run a standard expire reduce that covers the dates of these items and
verify that they are not purged (because of the outstanding archive
failure)
2) Add the IGNOREARCHIVEFAILURE option on the MISC tab of GWCheck and run
the same expire reduce again.
3) The new option should allow the items to be purged.
Additional Information
The most common reasons that the GroupWise items failed to auto-archive is
either because the archive disk filled up or there was a disruption in
communication to a remote archive store.
....QUESTION...
Will this only "delete" the failed to archive messages or will it affect
any messages for that user during those dates? I don't want to
accidentally delete any messages that need to be kept. I just want to
clear the messages that have failed.
Sorry for the long message. Thank you for your help.

In article <MQfOs.2116$[email protected]>, RSharp wrote:
> Error 83- Item failed to archive
> - Subject: Fwd: Dayton VA emergency renovation
> - From: John Hall
> - Date: Nov 6, 2009 - 1:47 pm
> - First archive attempt date: Jul 25, 2011
> - Number of archive attempts: 1
> - Error number on last Archive attempt: 0x8204
> 9938 ITEM_RECORD check
> Error 83- Item failed to archive
> - Subject: Fwd: Building 700 Elevator and Building 701 Demoliton Facade/
> Canopy Work
> - From: John Hall
> - Date: Jan 6, 2010 - 1:29 pm
> - First archive attempt date: Jul 25, 2011
> - Number of archive attempts: 1
> - Error number on last Archive attempt: 0x8204
> 10585 ITEM_RECORD check
>
That looks like they are from the GWCheck done July 25th, 2011. Are the
same messages still showing up in current contents check?
Do you run a regular purge only expire reduce? If not, run one soon, and
check those logs for any instance of errors purging. An expire of old
trashbin is also a worthwhile expire reduce job to run as part of this.
I'm assuming by your concern that these users have messages and such from
that time frame and earlier that they want to keep, hence making that TID
sound very suspicious for your purpose. If that assumption is invalid,
then that TID should be just fine for you, just be careful of your # of
days you pick.
GWAVA's Retain has hit similar issues and therefor has the tools built in,
but then this is a tool that archives without removing mail from the
primary storage. One client of mine still deletes mail over 999 days from
GroupWise itself just to retain efficient operations, relying on Retain
for anything older. That link supplied for next steps if my assumption
was correct.
http://support2.gwava.com/kb/?View=entry&EntryID=379
Andy Konecny
Knowledge Partner (voluntary SysOp)
KonecnyConsulting.ca in Toronto
Andy's Profile: http://forums.novell.com/member.php?userid=75037

Best practice for messages that fails

Hi all,
In a scenario, for e.g. proxy -> XI -> WS
For e.g. if the Webservice service is down, we would have a message failure in XI.
What is the best practice in business scenario to handle such situations?
Appreciate any comments,

Hi,
In your initial question you didn't mentioned about Synchronous Scenario
You are right, if it is Synchronous Service message won't be persistent by default, although you can explicitly set the option to save sync messages also but it's not best practice.
As it is synchronous process the requestor will get response back and in any case(success or failure) , in case of any failure you can send the alert to the support person by configuring Alert in XI and the message need to be resend from the requestor system once the service is up.
Support person will fix the issue and will inform the requestor to send the message again.
*Reward points if answers your question.*
Thanks
Amit

Mail on Lion does not save messages that fail to send

When I am not connected to the web if I am composing a message and hit send button Mail does not save the message, and just tells me that It could not be sent and discards it. This is really annoying. I am using 10.7.4. Anybody else experiencing it? Any way around it?
For example, if I am on a plane, and I want to compose my messages to be sent later, this will not do it.. I never had this issue on Snow Leopard.
Thanks

Thanks. This is helpful.. However, do you agree that this is bug? Because, if I accidentally hit "send" in the full screen view, it just discards everything I wrote, it seems like. This was not the case in Snow Leopard. It would just save it in Outbox. When it is not in full screen mode, it still seems to put in in Outbox. I think my solution is to avoid this full screen view. It sounded a good idea, but changing bevavior just becuase I am in full screen, I cannot get it.

Using PI 7.0 to handle moving a PDF document into a SOAP Message & sending

Here is our situation. We have the business writing all invoices for a day out of SAP to disk formatted as a PDF document; meaning, if the file is FTP'd from the disk of SAP to an NT server inside our firewall it is recognised as a PDF by Windows and Adobe.
After we read the PDF, I need to add it as the payload to a SOAP message that will be sent to the web service of a partner out side our firewall. They will extract the PDF from the SOAP Message and print the invoices... stuff the envelopes ... and post them.
I have been trying to use the file adapter to "pick up" the PDF and the SOAP adapter to send... Obviously, it is not working and I need some assistance. I am new to XI, so any advice will be greatly appreciated.
Thanks,
Rich

1.If the partner webservice supports SOAP attachments then you can send the required attachments from FileAdapter by selecting "Additional Files" check box in the File Sender channel.
Check this link: [http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm|http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm]
2.Else if this not the case i.e., you want to send PDF file stream as part of payload then you need to convert the PDF file stream to BASE64 format then map to one of the field of Webservice structure and then post using SOAP Adapter.
Remember the webservice field length should be enough to carry the BASE64 string otherwise the target application will fail to process the data or it will process data by truncating. Also there should be extra funtionality in target webservice for converting BASE64 format to binary format(PDF file).
But in general the webservices will support attachements. So you can go ahead with Case1.
Thanks,
- Gujjeti.

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

Soap Message in webservice

Hello All,
I have a SOAP request as below shich is sent from a client proxy(consumer proxy) in SAP.
POST /blw/annehmen/2/0/ws/sendeWholesaleMeldung
HTTP/1.1..Content-Type: text/xml;
charset=utf-8..Content-Length:23711..accept-language: en..sap-language: E..soapaction: ""..accept: text/xml..
sap-srt_id: 20090804/162628/v1.00_final_6.40/4A71719D8F44393BE10000000AAF5D7F..
user-agent: SAP Web Application Server (1.0;700)..
host: 10.13.21.619:12000..accept-encoding: gzip....
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
<soap-env:Header>
     <soap-env:Body>
          <n0:sendeWholesaleMeldungRequest xmlns:n0="http://wholesale.de/portal/blw/v2"
                        xmlns:prx="urn:sap.com:proxy:DWT::700:2008/01/11">
               <n0:Meldung>
                    <n0:Meldungsnummer>Str 313</n0:Meldungsnummer>
                    <n0:Geschaeftsfallart>string 314</n0:Geschaeftsfallart>
                    >
               </n0:Meldung>
          </n0:sendeWholesaleMeldungRequest>
     </soap-env:Body>
</soap-env:Envelope>
I want to send the type of the complex type Meldung like
<n0:Meldung xsi:type="swm:MeldungENTMType">
in the SOAP message that i sent.
Can anyone please let me know how this could be achieved.

No cross posting
Read the "Rules of Engagement"
Regards
Juan

How to send a signed SOAP message with additional HTTP Header fields

Our Partner's integration requirements are that we send them asynchronous SOAP messages, that are digitally signed, and whose HTTP headers contains 5 or 6 additional header fields, of which 3 or 4 will need to be dynamically set during the message mapping. I believe we can use the HTTP adapter for adding new fields to the HTTP header, but don't believe it supports signing. I believe that the SOAP adapter supports signing, but I'm not clear on how to use it to add fields to the HTTP header. What is the most straight-forward way to achieve both the signing of the message and the addition of the HTTP header values?
Thanks,
Kurt

>>>What is the most straight-forward way to achieve both the signing of the message and the addition of the HTTP header values?
Use Java mapping for both.
1) Signing the message
You can digitally sign the soap message using many standard api like WSS4j? or refer Java XML signature API which comes in Jdk1.6.
Refer these links
WSS4J - http://ws.apache.org/wss4j/axis.html
Java XML signature : http://java.sun.com/developer/technicalArticles/xml/dig_signature_api/
2) >>whose HTTP headers contains 5 or 6 additional header fields, of which 3 or 4 will need to be dynamically set during the message mapping
Use Dynamic configuration API to set the additional header fields during message mapping.

Can't Verify a SOAP message

I have a problem in verifying a SOAP message that I have created my self, after signing the message and then convert it to string, I try to verify it, but it returns false each time, but when I use the Document after siging it without converting it to a string , it works, I really need some one to tell me why is it doing this here is the code for both cases
- Converting Document to String before verifying sugnature
signature.sign(dsc);
TransformerFactory tf = TransformerFactory.newInstance();
Transformer trans = tf.newTransformer();
StringWriter signedXMl = new StringWriter();
trans.transform(new DOMSource(docElement), new StreamResult(signedXMl));
String tempstr = signedXMl.toString();
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
dbf.setNamespaceAware(true);
NodeList nl = null;
DocumentBuilder builder = dbf.newDocumentBuilder();
Document doc = builder.parse(new InputSource(new StringReader(inXML)));
nl = doc.getElementsByTagNameNS(XMLSignature.XMLNS, "Signature");
if (nl.getLength() == 0)
                    System.out.println("In main: ERROR - Cannot find Signature element");
validateElement(nl.item(0),kp);---------------------------------------------------------------------------------------------
- Using the same Document element used in Signing for verification
signature.sign(dsc);
NodeList nl = doc.getElementsByTagNameNS(XMLSignature.XMLNS, "Signature");
validateElement(nl.item(0),kp);----------------------------------------------
both use validateElement function
private static void validateElement(Node signElement,KeyPair kp) {
                 DOMValidateContext valContext = new DOMValidateContext(kp.getPublic(), signElement);
          String providerName = System.getProperty("jsr105Provider","org.jcp.xml.dsig.internal.dom.XMLDSigRI");
          XMLSignatureFactory factory = null;
          XMLSignature signature = null;
          try
               factory = XMLSignatureFactory.getInstance("DOM",(Provider) Class.forName(providerName).newInstance());
               signature = factory.unmarshalXMLSignature(valContext);
               boolean coreValidity = signature.validate(valContext);
               String kiki = null;
               boolean sv = signature.getSignatureValue().validate(valContext);
               //System.out.println("signature validation status: " sv);
               Iterator i = signature.getSignedInfo().getReferences().iterator();
               for (int j=0; i.hasNext(); j++)
                    boolean refValid = ((Reference) i.next()).validate(valContext);
                    String koko = null;
          } catch (Exception e)
               String koko = null;
I really apreciate any input, I don't know what to do

There is no such system as Windows 7 Vista SP2. Either you have Windows 7 or Windows Vista. If your system is Vista, then sending video messages is not available. This feature is only present on Windows 7 and higher systems.

Sending a copy of each SOAP message arriving on the ESB to archive

I am trying to enable the ESB to serve as my "message copy collector" to achieve non-repudiation. My idea is that each SOAP message that enters the ESB will be copied, and a copy sent to an archive. Will this require some sort of service (attached to the bus) to which all service components attached to the bus will have to address a copy of their messages?

The message archiving feature of ALSB is not "strictly" designed to be used as a non-repudiation mechanism. The message persisted by ALSB may be slightly different than the message received on the wire.
There are other solutions available with ALSB to do non-repudiation.
If you simply want to store messages you can look at the report action:
http://edocs/alsb/docs26/operations/reporting.html
Gregory

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

The embedded oc4j in JDeveloper returned a wrong data from the SOAP message

Greetings,
I made a webservice in .NET to send simply the current time of the server. then, I developed another client in JDeveloper to receive the time.
and the object declared in j2ee as Calendar object.
everythings went fine, but what I have noticed when I print the Calendar object, the time came plus 3 hours later as the .NET time.
FYI, I had checked the soap message that was received by embedded OC4J ,it was correct time, but the problem when you print it. and both .NET and Jdeveloper in the same machine
example:
<?xml version = '1.0' encoding = 'utf-8'?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body>
<HelloWorldResponse xmlns="http://tempuri.org/">
<HelloWorldResult>2008-10-14T10:40:21.12</HelloWorldResult>
</HelloWorldResponse>
</soap:Body>
</soap:Envelope>
when I printed the data, I got 2008-10-14T13:40:21.12
so, does anyone have an idea about what is going on ??
thanks in advance.

ANY HELP :(

Resending SOAP messages that failed

Similar Messages

Maybe you are looking for