Issue with SOAP attachment boundary

Hi All,
We are building an application which retrieves documents from server and passed it to client side as Soap + MTOM attachments.
We are using IBM webspere and webservices at the server end. And Java Webservices (JAX-WS) at the client end.
We are facing a different issue where the client side JAX-WS is not able to identify the images properly, since it is not able to recognize the noundary some times.
Is there any fix for this issue

I have i fact never seen this before.
On with tools release are you working and wich CI/component are you trying to call.
Also can you verify if the CI is valide, by opening it in Application Designer.
If validate, can you try to test the CI in Application Desiger and invoke the Find method.
If above test fial, fix the CI and regenerate the CI Service.
If both tests run fine, try to delete the WSDL and CI Service and Provide CI Service again.

Similar Messages

"Content is not allowed in prolog" with SOAP Attachment

I'm writing an application using SAAJ that sends a soap message to a servlet which responds with some information, including HTML which the client application will display. The HTML has to go into a SOAP attachment so the tags won't get confused with XML.
I had the whole thing working with plain text sending within a normal node, and I only switched a few lines to make that text an attachment with HTML instead, but now I'm getting the exception "Content is not allowed in prolog" on the Client side when it tries to create the envelope from the SOAPMessage.
Code for building answering SOAPMessage with attachment (Servlet to Client)
 public static SOAPMessage buildXML(Message newMessage){
 SOAPMessage msg = null;
 try {
 MessageFactory msgFactory = MessageFactory.newInstance();
 msg = msgFactory.createMessage();
 // Create an envelope in the message
 SOAPEnvelope envelope = msg.getSOAPPart().getEnvelope();
 msg.setProperty(SOAPMessage.WRITE_XML_DECLARATION, "true");
 msg.setProperty(SOAPMessage.CHARACTER_SET_ENCODING, "UTF-8");
 //Get hold of the the body
 SOAPBody body = envelope.getBody();
 SOAPElement soap_message = body.addChildElement("MESSAGE");
 if (newMessage.message_type != null){
 SOAPElement soap_message_type = soap_message.addChildElement("MESSAGETYPE");
 soap_message_type.addTextNode(newMessage.message_type);
 if (newMessage.questionID != 0){
 SOAPElement soap_questionID = soap_message.addChildElement("QUESTIONID");
 soap_questionID.addTextNode("" + newMessage.questionID);
 if (newMessage.username != null){
 SOAPElement soap_username = soap_message.addChildElement("USERNAME");
 soap_username.addTextNode(newMessage.username);
 if (newMessage.password != null){
 SOAPElement soap_password = soap_message.addChildElement("PASSWORD");
 soap_password.addTextNode(newMessage.password);
 if (newMessage.message_text != null){
 AttachmentPart soap_message_text = msg.createAttachmentPart("<html><body>" + newMessage.message_text + "</body></html>", "text/html");
 soap_message_text.setContentId("MESSAGETEXT");
 msg.addAttachmentPart(soap_message_text);
 //SOAPElement soap_message_text = soap_message.addChildElement("MESSAGETEXT");
 //soap_message_text.addTextNode(newMessage.message_text);
 if (newMessage.sampleString != null){
 SOAPElement soap_password = soap_message.addChildElement("SAMPLESTRING");
 soap_password.addTextNode(newMessage.sampleString);
 SOAPElement tmpEl;
 for (int i=0; i<newMessage.numArrayUsed; i++){
 tmpEl = soap_message.addChildElement("SAMPLEINT");
 tmpEl.addTextNode("" + newMessage.sampleInt);
 msg.saveChanges();
 } catch (Exception e) {
 e.printStackTrace();
 return msg;
You can see in the area where it adds MESSAGETEXT there are two clients commented out which work. The three lines above it are what changed to make it an attachment instead.
Code in Client for recieving reply from Servlet
SOAPMessage reply = connection.call(soap_msg, endpoint);
System.out.println("\nReceived reply from: " + endpoint);
reply.writeTo(System.out);
System.out.println("");
reply_msg = ProcessXML.parse(reply);This is the console output:
Edit: These forums seem to be inserting an extra > before the <?xml version="1.0" encoding="UTF-8"?> line, but it doesn't exist in the code I'm pasting
Received reply from: http://localhost:8080/kuj/CaseStudyServlet
------=_Part_2_371807.1137465625031
Content-Type: text/xml; charset=UTF-8
<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/><SOAP-ENV:Body><MESSAGE><MESSAGETYPE>deliverquestion</MESSAGETYPE><QUESTIONID>1</QUESTIONID><USERNAME>zac</USERNAME></MESSAGE></SOAP-ENV:Body></SOAP-ENV:Envelope>
------=_Part_2_371807.1137465625031
Content-Type: text/html
Content-Id: MESSAGETEXT
<html><body>This is an Array sort Question. You will be given 10 random integers and you must sort and return them in the order of greatest to least.</body></html>
------=_Part_2_371807.1137465625031--
ERROR: 'Content is not allowed in prolog.'
17-Jan-2006 02:40:25 com.sun.xml.messaging.saaj.soap.EnvelopeFactory createEnvelope
SEVERE: SAAJ0511: Unable to create envelope from given source
com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to create envelope from given source:
 at com.sun.xml.messaging.saaj.soap.EnvelopeFactory.createEnvelope(EnvelopeFactory.java:111)
 at com.sun.xml.messaging.saaj.soap.ver1_1.SOAPPart1_1Impl.createEnvelopeFromSource(SOAPPart1_1Impl.java:39)
 at com.sun.xml.messaging.saaj.soap.SOAPPartImpl.getEnvelope(SOAPPartImpl.java:98)
 at com.zacwittedesign.xml.ProcessXML.realParse(ProcessXML.java:32)
 at com.zacwittedesign.xml.ProcessXML.parse(ProcessXML.java:26)
(snip)And this is the beginning of the code for extracting the info from the SOAPMessage on the Client side:
private static Message realParse(SOAPMessage msg){
 Message newMessage = new Message();
 try {
 SOAPEnvelope envelope = msg.getSOAPPart().getEnvelope();
 SOAPBody body = envelope.getBody();
(snip)It dies on SOAPEnvelope envelope = msg.getSOAPPart().getEnvelope();
Does anyone know what I'm doing wrong?

I suppose I should also include the bit where the Servlet actually SENDs the resulting SOAPMessage
SOAPMessage msg = ProcessXML.buildXML(outMessage);
// try to send it
try {
 response.setContentType("text/xml");
 msg.writeTo(response.getOutputStream());

Issue with Excel Attachement in BI 7.0

Hi,
I have developed a custom report to send an e-mail with excel attachment in BI 7.0. When we are trying to open the excel sheet attachment in the e-mail. I am getting a message warning message stating that 'This file is not in a recognizable format'. but if we click on ok button then everything looks fine i.e the data is displaying as expected.
I have developed the same reports in SAP R/3 and SRM but I don't see any issues over there.
Can any one help me on this issue.
Thanks in advance,
Venkat Bomma

When the selection screen pops up choose the KEY only function on the TOOLS on the top right corner of the screen. Then you will be able to enter the values manually.
Hope this helps.

Problem with SOAP Attachment in MM7

Hi, I'm developing with Bea Weblogic 7 sp2 a MM7 server. My problem is when I add an attachment to SOAP message, Weblogic can't receive the message and say something as "The ID referenced by .... is unknow" but the href attribute in SOAP Message has the same value as the Content-ID of the attachment.
The attachment is multipart/mixed. Please, I need help.
I add here an old post from other user about this problem.
Hi
I need some help for a problem I have with bea 7.0 sp1 web services.
I'm trying to develop a SOAP Message Handler to intercept a SOAP Messages.It seems
work properly for simple soap requests.
But I need to send attachements so my request is like:
POST /mm7/mm7Service HTTP/1.0
Content-Type: multipart/related; type="text/xml"; start="<2ED4C017A7C250C35409DE82D1A8E6B1>";
boundary="----=_Part_18_90248.1076664111251"
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: Axis/1.1
Host: xxx.xxx.xxx.xxx
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: "http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2?operation=Deliver"
Content-Length: 5177
------=_Part_18_90248.1076664111251
Content-Type: text/xml; charset=UTF-8
Content-Transfer-Encoding: binary
Content-Id: <2ED4C017A7C250C35409DE82D1A8E6B1>
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header>
<ns1:TransactionID soapenv:mustUnderstand="0" xsi:type="xsd:string" xmlns:ns1="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2">E8D97EC0A80A712B5CF3C7E5A56AF121</ns1:TransactionID>
</soapenv:Header>
<soapenv:Body>
<DeliverReq xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2">
<MM7Version>5.3.0</MM7Version>
<LinkedID>fa571b8e93C0A809513c33d383069dfb</LinkedID>
<Sender>
<RFC2822Address displayOnly="false">[email protected]</RFC2822Address>
</Sender>
<Recipients>
<To>
<Number displayOnly="false">+123454678</Number>
</To>
<Cc>
<RFC2822Address displayOnly="false">[email protected]</RFC2822Address>
</Cc>
<Bcc>
<RFC2822Address displayOnly="false">[email protected]</RFC2822Address>
</Bcc>
</Recipients>
<Priority>High</Priority>
<Content href="cid:74935BFBD687B557CE9C25A591FEE0DA" allowAdaptations="true"/>
</DeliverReq>
</soapenv:Body>
</soapenv:Envelope>
------=_Part_18_90248.1076664111251
Content-Type: multipart/mixed;
boundary="----=_Part_17_2373292.1076664111231"
Content-Transfer-Encoding: binary
Content-Id: <74935BFBD687B557CE9C25A591FEE0DA>
------=_Part_17_2373292.1076664111231
I implemented a simple Handler with a system.out in
public boolean handleRequest(MessageContext mc)
method
But weblogic never gets there. It gives me this error instead:
javax.xml.soap.SOAPException: failed to receive message:
at weblogic.webservice.core.DefaultWebService.invoke(DefaultWebService.java:227)
This seems related to this line
<Content href="cid:74935BFBD687B557CE9C25A591FEE0DA" allowAdaptations="true"/>
If I remove it, it can reach the handleRequest() method.
Unfortunately I need the Content parameter....
Does weblogic support href attributes in soap ?
many thanks to whatever help
(I already lost 3 days on that problem.....)
alan
Thanks.

Hello,
Problem 1)
In a previous question about this in SDN, someone (sorry, can't remember who) answered:
"Have you or the user logged into the SAP GUI before? If not, have them login in. Our problems occured
with new users that never logged into the SAP gui and so the user profile was never loaded with the ini
file."
Please try that.
Problem 2)
Are you sure it's running with the same variant in the background?
What if you try every 5 minutes instead - maybe a minute is too short and it gets mixed up.
You could also try copying RSWUWFML2 to ZRSWUWFML2, inserting an infinite loop and then attaching to it in order to debug it in the background.
regards
Rick Bakker
Hanabi Technology

Issues with SOAP output from our adapter.

Hi,
I have a supplier who is building a SOAP processor. To do this I streamed the output to them and they reviewed it. A number of things were pointed out and I wanted to know if there was a way for me to resolve them. The message is below. I am not a MIME/SOAP guru but they think the output does not follow W3C standards.
1) The Content-Type in MIME header should be multipart/related; type="text/xml"; since attachments are included.
2)The entire actual MIME message is 7 bit encoded. We are expecting to see that the SOAP message is 7 bit encoded and each attachment is base64 encoded.
3) The SOAP message is missing xml header <?xml version="1.0" encoding="UTF-8"?> in the actual MIME message.
Any thoughts are apprieciated
Message-ID: <11922341.1155159668324.JavaMail.webmethods@exshaw>
MIME-Version: 1.0
Content-Type: text/xml; charset=utf-8
content-transfer-encoding: 7bit
--SAP_c4faf651-27ef-11db-a170-0014c258bd93_END: --SAP_c4faf651-27ef-11db-a170-0014c258bd93_END
Content-ID: <[email protected]>
Content-Disposition: attachment;filename="[email protected]"
- Hide quoted text -
Content-Description: SOAP
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Header><sap:ReliableMessaging xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'><sap:QualityOfService>ExactlyOnceInOrder</sap:QualityOfService><sap:QueueId>ORD2000000625</sap:QueueId></sap:ReliableMessaging><sap:Diagnostic xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'><sap:TraceLevel>Information</sap:TraceLevel><sap:Logging>Off</sap:Logging></sap:Diagnostic><sap:HopList xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'><sap:Hop timeStamp='2006-08-09T21:25:59Z' wasRead='false'><sap:Engine type='BS'>EP_QAS_SRM_QSR_100</sap:Engine><sap:Adapter namespace='http://sap.com/xi/XI/System'>XI</sap:Adapter><sap:MessageId>7eb44f25-ecc2-844e-9188-b79f8a9ab640</sap:MessageId><sap:Info>3.0</sap:Info></sap:Hop><sap:Hop timeStamp='2006-08-09T21:25:59Z' wasRead='false'><sap:Engine type='IS'>is.00.bp1houap494</sap:Engine><sap:Adapter namespace='http://sap.com/xi!
/XI/System'>XI</sap:Adapter><sap:MessageId>6dd9983c-e326-8744-bf40-ace9767a88c0</sap:MessageId><sap:Branch><sap:MessageId>6dd9983c-e326-8744-bf40-ace9767a88c0</sap:MessageId><sap:Service>Digital_Oilfield</sap:Service></sap:Branch><sap:Branch><sap:MessageId>0e3736f7-9f64-6e47-973f-632caf0d8ed6</sap:MessageId><sap:Party agency='' scheme=''>Channelinx_Party</sap:Party><sap:Service>PIPP32_10_Seller</sap:Service></sap:Branch><sap:Info>3.0</sap:Info></sap:Hop><sap:Hop timeStamp='2006-08-09T21:26:00Z' wasRead='false'><sap:Engine type='AE'>af.qxi.bp1houap494</sap:Engine><sap:Adapter namespace='http://sap.com/xi/XI/System'>XIRA</sap:Adapter><sap:MessageId>6dd9983c-e326-8744-bf40-ace9767a88c0</sap:MessageId></sap:Hop></sap:HopList><sap:Main xmlns:sap='http://sap.com/xi/XI/Message/30' versionMajor='3' versionMinor='0' SOAP:mustUnderstand='1'><sap:MessageClass>ApplicationMessage</sap:MessageClass><sap:ProcessingMode>asynchronous</sap:ProcessingMode><sap:MessageId>6dd9983c-e326-8744-bf4!
0-ace9767a88c0</sap:MessageId><sap:TimeSent>2006-08-09T21:25:59Z</sap:
TimeSent><sap:Sender><sap:Party agency='http://sap.com/xi/XI' scheme='XIParty'></sap:Party><sap:Service>EP_QAS_SRM_QSR_100</sap:Service></sap:Sender><sap:Receiver><sap:Party agency='http://sap.com/xi/XI' scheme='XIParty'></sap:Party><sap:Service>Digital_Oilfield</sap:Service></sap:Receiver><sap:Interface namespace='http://sap.com/xi/SRM/SupplierEnablement/Global'>PurchaseOrderChangeRequest_In</sap:Interface></sap:Main></SOAP:Header><SOAP:Body><ns0:PurchaseOrderChangeRequest xmlns:ns0='http://sap.com/xi/SAPGlobal/Global'><MessageHeader><ID schemeID='0102'>20000006250000000220060809212559</ID><CreationDateTime>2006-08-09T21:25:59Z</CreationDateTime><SenderParty><InternalID schemeID='PartnerID' schemeAgencyID='EP_QAS_SRM_QSR_100'>055034086</InternalID></SenderParty><RecipientParty><InternalID schemeID='PartnerID' schemeAgencyID='EP_QAS_SRM_QSR_100'>80025171</InternalID></RecipientParty></MessageHeader><PurchaseOrder><ID schemeAgencySchemeAgencyID='ZZZ' schemeAgencyID='EP_QAS_SR!
M_QSR_100'>2000000625</ID><BuyerPostingDateTime>2006-08-01T12:00:00Z</BuyerPostingDateTime><BuyerLastChangeDateTime>2006-08-01T18:36:40Z</BuyerLastChangeDateTime><Note>KALIS3 01.08.2006 20:13</Note><ItemListCompleteTransmissionIndicator>true</ItemListCompleteTransmissionIndicator><BuyerParty><BuyerID>108</BuyerID></BuyerParty><SellerParty><BuyerID>80025171</BuyerID></SellerParty><ProductRecipientParty><BuyerID>7249</BuyerID><Address><OrganisationFormattedName>MD-HM</OrganisationFormattedName><OrganisationFormattedName>Mad Dog Operations</OrganisationFormattedName><PersonName><FormattedName>Sankar Kaliaperumal</FormattedName><LegalName>Sankar Kaliaperumal</LegalName><GivenName>Sankar</GivenName><PreferredGivenName>Sankar</PreferredGivenName><Family><FamilyName>Kaliaperumal</FamilyName><PrimaryIndicator>true</PrimaryIndicator></Family><Affix><AffixName>Mr</AffixName><AffixCode>FormOfAddress</AffixCode></Affix></PersonName><PhysicalAddress><CountryCode>US</CountryCode><RegionC!
ode listID='TX'/><StreetPostalCode>77079</StreetPostalCode><CityName>H
ouston</CityName><StreetName>501 Westlake Park Dr</StreetName></PhysicalAddress><Communication><CorrespondenceLanguageCode>en</CorrespondenceLanguageCode><Email><Address>[email protected]</Address><AddressDefaultIndicator>true</AddressDefaultIndicator><AddressUsageDenialIndicator>false</AddressUsageDenialIndicator></Email></Communication></Address></ProductRecipientParty><BillToParty><BuyerID>108</BuyerID><Address><OrganisationFormattedName>BP Root</OrganisationFormattedName><OrganisationFormattedName>BP Enterprise</OrganisationFormattedName><PhysicalAddress><CountryCode>US</CountryCode><RegionCode listID='TX'/><StreetPostalCode>77079</StreetPostalCode><CityName>Houston</CityName><StreetName>501 Westlake Park Dr</StreetName></PhysicalAddress><Communication><Telephone><Number><SubscriberID>1-281-366-5000</SubscriberID></Number><NumberDefaultIndicator>true</NumberDefaultIndicator><NumberUsageDenialIndicator>false</NumberUsageDenialIndicator></Telephone><Facsimi!
le><Number><SubscriberID>1-281-366-5000</SubscriberID></Number><NumberDefaultIndicator>true</NumberDefaultIndicator><NumberUsageDenialIndicator>false</NumberUsageDenialIndicator></Facsimile><Email><Address>[email protected]</Address><AddressDefaultIndicator>true</AddressDefaultIndicator><AddressUsageDenialIndicator>false</AddressUsageDenialIndicator></Email></Communication></Address></BillToParty><ShipToLocation><BuyerID>5667</BuyerID><Address><OrganisationFormattedName>BP Root</OrganisationFormattedName><OrganisationFormattedName>BP Enterprise</OrganisationFormattedName><PhysicalAddress><CountryCode>US</CountryCode><RegionCode listID='TX'/><StreetPostalCode>77079</StreetPostalCode><CityName>Houston</CityName><StreetName>501 Westlake Park Dr</StreetName></PhysicalAddress><Communication><Telephone><Number><SubscriberID>1-281-366-5000</SubscriberID></Number><NumberDefaultIndicator>true</NumberDefaultIndicator><NumberUsageDenialIndicator>false</NumberUsageDenialIndicator></Teleph!
one><Facsimile><Number><SubscriberID>1-281-366-5000</SubscriberID></Nu
mber><NumberDefaultIndicator>true</NumberDefaultIndicator><NumberUsageDenialIndicator>false</NumberUsageDenialIndicator></Facsimile><Email><Address>[email protected]</Address><AddressDefaultIndicator>true</AddressDefaultIndicator><AddressUsageDenialIndicator>false</AddressUsageDenialIndicator></Email></Communication></Address></ShipToLocation><CashDiscountTerms><MaximumCashDiscount><DaysValue>10</DaysValue><Percent>0.5</Percent></MaximumCashDiscount><NormalCashDiscount><DaysValue>30</DaysValue><Percent>0.0</Percent></NormalCashDiscount></CashDiscountTerms><FollowUpPurchaseOrderConfirmation><RequirementCode>04</RequirementCode></FollowUpPurchaseOrderConfirmation><FollowUpDespatchedDeliveryNotification><RequirementCode>04</RequirementCode></FollowUpDespatchedDeliveryNotification><FollowUpServiceAcknowledgementRequest><RequirementCode>02</RequirementCode></FollowUpServiceAcknowledgementRequest><FollowUpInvoiceRequest><RequirementCode>01</RequirementCode><EvaluatedReceiptSettlement!
Indicator>false</EvaluatedReceiptSettlementIndicator></FollowUpInvoiceRequest><Item><ID>1</ID><ActionCode>02</ActionCode><UnplannedItemPermissionCode>01</UnplannedItemPermissionCode><Product><TypeCode>1</TypeCode><Note>Chris Test</Note></Product><ProductCategory><BuyerID>83101603</BuyerID></ProductCategory><Price><NetUnitPrice><Amount currencyCode='USD'>10.0</Amount><BaseQuantity unitCode='EA'>1.0</BaseQuantity></NetUnitPrice></Price><Attachment id='1 .QAVendorID's.txt' filename='QAVendorID's.txt'>chris test</Attachment><ScheduleLine><ID>1</ID><DeliveryPeriod><StartDateTime>2006-08-01T14:00:0002:00</StartDateTime><EndDateTime>2006-08-01T14:00:0002:00</EndDateTime></DeliveryPeriod><Quantity unitCode='EA'>1.0</Quantity></ScheduleLine></Item></PurchaseOrder></ns0:PurchaseOrderChangeRequest></SOAP:Body></SOAP:Envelope>
--SAP_c4faf651-27ef-11db-a170-0014c258bd93_END
content-id: [email protected]
content-type: text/plain
80150395- Farmington
80150396-Houston
80025171- Tulsa
80025173- Tulsa
80236936- Dallas
SAP_c4faf651-27ef-11db-a170-0014c258bd93_END
Thanks,
chris

Amy,
Would agree with Stacy. Have someone on BASIS team check SOST transaction on day where you had email go out, and the customer indicated they got no PDF. You could at least validate that the message leaving your SAP system had a PDF attached to it by looking in SOST. You could then definitely say that the issue is on the receiving side.
If the transmission in SOST is void of PDF, then you would be back to reviewing your output type and the config behind it (including programs).
Hope this helps. Revert back if not.
Thanks,
Jay

Issue with soap response

Hi,
Below my SOAP request message..
<?xml version="1.0"?>
<soapenv:Envelope xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2003/03/addressing/" xmlns:xsd="http://www.w3.org/2001/XMLSchema/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance/">
<soapenv:Header xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<wsse:Security soap:mustUnderstand="1" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:UsernameToken>
<wsse:Username>xxxxx</wsse:Username>
<wsse:Password>xxxxx</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</soapenv:Header>
<soapenv:Body xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:Find__CompIntfc__IDS_RQST_PSR_INQ_CI xmlns="http://xmlns.ing.com/Enterprise/Tools/schemas/EDS_FIND_FLT.V1" xmlns:ns2="http://xmlns.ing.com/Enterprise/Tools/schemas/EDS_FIND_REQ.V1" xmlns:ns3="http://xmlns.ing.com/Enterprise/Tools/schemas/EDS_FIND_RSP.V1" xmlns:ns4="http://xmlns.ing.com/Enterprise/Tools/schemas/EDS_GET_FLT.V1" xmlns:ns5="http://xmlns.ing.com/Enterprise/Tools/schemas/EDS_GET_REQ.V1" xmlns:ns6="http://xmlns.ing.com/Enterprise/Tools/schemas/EDS_GET_RSP.V1">
<ns2:ING_SUSPS_CNTL_NBR>999999999</ns2:ING_SUSPS_CNTL_NBR>
<ns2:IDS_SITE_ID>HFD</ns2:IDS_SITE_ID>
</ns2:Find__CompIntfc__IDS_RQST_PSR_INQ_CI>
</soapenv:Body>
</soapenv:Envelope>
I am getting the below response message... The issue is with namespace in the response (ns2success). I do not know why there is a success word in the namespace which is causing invalid XML message.
<?xml version="1.0"?>
<soapenv:Envelope xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<ns2:Find__CompIntfc__IDS_RQST_PSR_INQ_CIResponse xmlns:ns2Success="http://xmlns.ing.com/Enterprise/Tools/schemas/EDS_FIND_RSP.V1"/>
</soapenv:Body>
</soapenv:Envelope>

I have i fact never seen this before.
On with tools release are you working and wich CI/component are you trying to call.
Also can you verify if the CI is valide, by opening it in Application Designer.
If validate, can you try to test the CI in Application Desiger and invoke the Find method.
If above test fial, fix the CI and regenerate the CI Service.
If both tests run fine, try to delete the WSDL and CI Service and Provide CI Service again.

Pages5.1+Mavericks = issues with margins, attaching, transport, pictures, printing, more.

Got Mac Mini with Mountain Lion ; the GOALS for this computer:
Writing for publication, filling out forms, sending data, photo editing and adjustments, artwork, tasks, email, online consulting, volunteer advocacy, research, etc.
Was beginning to get the hang of things, with some difficulties;but was not finding what I needed.
Unknowingly took bad advice: updated to Mavericks.
Everything FUBAR'd.
Straightened some things out; at least can access email, get online, do a few things--still can't do meaningful work on it.
Mini = very expensive Entertainment Box; NOT my priority.
I Thought: download programs that can do work.
Got Pages 5.1. It fails to work right:
Margins refuse to adjust.
Pictures pasted into Pages document, very hard to adjust on page or get type to wrap around picture, adjust sizing, etc.--time wasting, unable to adjust as wanted on pages--settled for what it would do at all.
Page Setup is hardly relevant to actually setting up a Page.
Won't attach to Email.
Won't allow reading it anywhere but on the computer it was made.
Won't allow saving Pages nor Text documents using ANY other extensions.
Saving is a contorted mouse-hunt; there's no "save-as".
For one typed page, a box told me there was HTML in the thing, and that it couldn't deal with it, even though there wasn't.
Pages document Won't save properly to a Pendrive for transport: it reads OK on the MAc, but on the PC, only 1st page visible, the rest unitelligible, pixelated, when moved to a PC.
I thought to transport the Pages document to the PC to copy/paste it into a Owrd Document--THAT failed, too.
Trying to print this Pages document turned into a nightmare: 1st page almost printed, ensuing pages resembled NOTHING I'd saved; a 10-page Pages document turned into many more pages of garbled mess.
I haven't had time to try other features; just making a pretty basic Pages document has been a wicked time-waster.
There doesn't seem to be ANY work-around.
I Thought: copy/paste the content of the Pages document, into a Text document: THAT FAILED.
Copy/Pasting one page at a time for this maneuver, also failed:
Pictures [.jpg] turn fuzzy and HUGE, and refuse adjustment in any way I can find.
Pictures refuse to adjust Easily, whether Pages or Text--couldn't make pictures in Text adjust at all.
Very UNimpressed with the picture editing on this Mac, to date.
Having terrible time doing ANYthing to adjust .jpg's in any document--forget putting photos in emails.
"Help" has been fairly useless; tutorials instruct to do things the programs won't do, or has no suggestion.
Pages is Useless, if it only allows making a basic document that's ONLY visible or minimally usable on the unit it got made on.
Feartures hark back to antique MS Word, like having to go up to Edit in order to copy/paste [as in this message], instead of being able to use Mouse to copy/paste directly in document, for instance.
This computer refuses to allow printing via ethernet or hardwire; Mini sees there's a printer, but can't print, thinks it's not on, or some unknown blockage.
Uninstalled printer, tried to reinstall, Mini refuses to allow reinstall; can't auto-find printer, refuses manual entry of information.
This Mac nearly choked/crashed after updated to Mavericks, in many ways.
MAYBE all this is really yet more Mavericks issues? ?
I paid dearly to get a computer that SHOULD have been Stably ready to roll; instead, it's caused about 3+ months worth of time-wasting.
This fails as a reliable, stable WORK unit.
Getting vetted, stable software should be easy, but it isn't.
ALL the problems APPEAR to be software issues.
This isn't just a Learning Curve, this is diabolical Sudoku gone horribly wrong!
Microsoft historically, repeatedly, rushed unstable, incomaptible software to users before de-bugging/de-glitching, or issues incomplete licenses to ancillary programs making htem disfunctional: it's what I've hated MOST about PC's.
IMHO, the contract that conjoined Mac with Microsoft seems to have caused Macs to take on the worst of PC habits.
This MacMess is turning my brain to mush! Where do I send a BILL to Apple for premature onset of Dementia / Stressed-Brain injuries + Time Lost, related to bad computer software?!
At this rate, I'll never finish a book for publication anywhere, and must fall back on hand-writing forms and reports.

Thanks Peter--it is what I thought [return to Mountain Lion].
Chi
PS: Contracts between Microsoft and Apple can be Googled; numerous things come up; could start here:
http://www.roughlydrafted.com/RD/RDM.Tech.Q1.07/592FE887-5CA1-4F30-BD62-407362B5 33B9.html
It continued, with variations, later dates.
Using "conjoined" was perhaps, not exactly the correct term. But that contract changed how Macs operated; dependability has, IMHO [and others], declined, while PC's have gained some bits of dependability.
Macs subsequently started using other processors, instead of Apple hardware--[not knowing how that might change things].
There's been more of Apple rushing software to users prematurely; always a badly played Microsoft trick, for instance.
It has some hints that MS and Apple are becoming more homogenous; that would be sad. It will take longer than this, to accomplish; but this kind of contracts between industry giants, often portend that sort of merge at later date, done in a step-wise manner. These kinds of things can take years longer than this; meanwhile, users deal with bad products.

Issue with SOAP receiver

Hi,
I'm using PI 7.0, SP13 and I'm sending a message to a MS webservice, using BURP as a proxy in between to avoid NTLM authorisation issues.
The problem is that it's perfecly possible to send a message using soapUI, but sending the exact same message ends up in an error:
"SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 400 Bad Request"
I already configured the MessageTransformBean by setting the ContentType to text/xml; charset=utf-8. Here are the settings of my communication channel:
Target URL: http://<correct URL on local network>
User authentication: false
Certificate authentication: false
Proxy: BURP proxy and BURP port
Proxy user authentication: false
Secutiry profile: false
Do not use SOAP envelope: false
Keep headers: false
Keep attachments: false
Use encoded headers: false
Use query string: false
SOAP action: <correct SOAP action>
I also played with the parameters "Do not use SOAP envelope", "Keep headers" and "Keep attachments", without any success. The only difference that I can think of is that soapUI runs on Windows, and the PI system runs on Linux.
Ideas, anyone?

@Baskar Gopal: I didn't generate a WSDL: I'm using the SOAP receiver to post a message to an existing webservice.
@sdnuser: the endpoint URL is 100% correct. I also added the MessageTransformBean like I stated before.
@Chirumamilla Sukarna: HTTP adapter doesn't work because I need the SOAP envelope.
The payload is in both cases (soapUI and PI) the same. Here's the part that's different:
soapUI (working part):
POST /DynamicsNAV/WS/Rendon%20Voorburg/Codeunit/Webservice HTTP/1.0
Accept-Encoding: gzip,deflate
Content-Type: text/xml;charset=UTF-8
SOAPAction: "urn:microsoft-dynamics-schemas/codeunit/Webservice:ContractorOrderInSync"
User-Agent: Jakarta Commons-HttpClient/3.1
Host: 192.168.1.8:7049
Proxy-Connection: Keep-Alive
Content-Length: 4292
Connection: Keep-Alive
SAP PI (not working part):
POST /DynamicsNAV/WS/Rendon%20Voorburg/Codeunit/Webservice HTTP/1.0
Accept: /
Host: 192.168.1.8:7049
User-Agent: SAP-Messaging-com.sap.aii.messaging/1.0505
Authorization: Basic aGFhZ3dvbmVuQGJpbTpRYnFyRU84IQ==
content-id: <soap-C89FD74E68782E13E1000000C0A8E010 @ sap.com>
Content-Type: text/xml;charset=UTF-8
Content-Length: 4292
SOAPACTION: "urn:microsoft-dynamics-schemas/codeunit/Webservice:ContractorOrderInSync"
Connection: Keep-Alive
I know the content type looks correct here, but the SOAP adapter gives an error about this nevertheless.

Issue with SOAP.jar in Oracle Apps 11i

Hi,
We have developed OAF page in R11i to call BPEL services, it works fine with following settings
1. Place soap.jar on server from JDeveloper
2. Set class path to point soap.jar in jserv.properties file
In our instance one saop.jar already exists in server and path for this file in specified in in jserv.properties, our functionality works fine if we place our soap.jar path in jserv.properties before standard soap.jar file. If we ask our DBA to specify our path before standard soap.jar then our DBA has doubt that it may clash with other XML services.
Please let me know if there is any Metalink doc id available for this issue or any SR has been raised for the same, please help it is urgent.
Regards,
Reetesh Sharma

Any update on this??
Edited by: Reetesh Sharma on 08-Jul-2010 04:38

Critical Issue:-- Convert SOAP Attachment into SOAP Body

hi,
 My requirment is
FTP----> SOAP synchronous.
In this one at SOAP receiver side SOAP request is an attachment file and response also I m getting as an attachment.
My problem is that I need to convert this SOAP response (attachment) in SOAP body so that I can map it with FTP datatype.
I used PayLoadSwapBean module but i m unable to convert this attachment into SOAP Body.
I just followed this blog
The specified item was not found.
May be i m not using this module in a proper mannner.
Can anybody explan it step by step.
Is there anyother solution for my problem..
<It is against the rules of Engagement to post a question with the catch of awarding points. Please refrain from the same.>
Thanks
Jaideep Jain
Edited by: Bhavesh Kantilal on Dec 3, 2008 10:26 AM

hi stefan,
I m getting this error after using PayloadSwapBean.
com.sap.aii.af.ra.ms.api.DeliveryException: Object not found in lookup of payloadSwapBean
I m mentioning here the value of parameter name and value for this module:--
parameter name parameter value
swap.keyName payload-name
swap.keyValue MainAttachment
Can u suggest where i went wrong.....
Thanks
Jaideep
Edited by: Jaideep Baid on Dec 5, 2008 9:27 AM

Issue with reading attachment in sender mail adapter

Hi, I am working on Email to file scenario, where I have to connect to exchange server and take the attachment of the email (xml file) and save it on to PI server. I have configured sender mail communication channel with following details:
Protocol: POP3
Message protocol: XIPAYLOAD
Mail attributes: keep attachments
Module:
1 localejbs/AF_Modules/PayloadSwapBean Local Enterprise Bean 1
2 localejbs/sap.com/com.sap.aii.adapter.mail.app/XIMailAdapterBean Local Enterprise Bean mail
1 swap.keyName Content-Description
1 swap.keyName Content-Description
1 swap.keyValue attachment,filename="MailAttachment-1.xml"
1 swap.keyValue MailAttachment-1
Also, configured receiver file adapter.
Since I donu2019t have to read mail content , I havenu2019t created any design components in ESR. I have just refrred to dummy namespace, interface (both sender and receiver). in receiver determination, interface determination, sender agreement and receiver agreements.
It was working fine, not sure what changes happened. Now I could see the attachment payload in message monitor.
Under Inbound message->payloads->
MailMessage ( text/xml;charset=utf-8 )
MailAttachment-1 ( text/xml;name="****************")
But the fille that is getting created doesnu2019t have the contents of the attachment (xml file) . It has some other information, shown below:
Directory: ******
Name: ********.xml
 =NextPart_002_01CB2C5B.B033B325#
content-type:text/plain;charset="us-ascii"#
content-length:30#
content-transfer-encoding:quoted-printable#
<<**********.xml>>=20#
 =NextPart_002_01CB2C5B.B033B325#
content-type:text/html;charset="us-ascii"#
content-length:#
content-transfer-encoding:quoted-printable#
 =NextPart_002_01CB2C5B.B033B325 #
Can you please let me know what is going wrong here.

using following parameters in module resolved my problem:
MOdule name Type Module Key
AF_Modules/PayloadSwapBean Local Enterprise Bean transform sap.com/com.sap.aii.adapter.mail.app/XIMailAdapterBean Local Enterprise Bean mail
Module Key Parameter Name Parameter value
transform swap.keyName Payload-Name
transform swap.keyName MailAttachment-1

Mail adapter issue with mail attachment

Hi all,
I have a scenario mail to file and i have a problem.
Is it possible, in a sender adapter mail to use the option keep attachment and mail package at the same time ?
So,is it possible to use the module payloadswapbean and XMLanonymizer in a sender adapter mail in order to suppress a namespace from the attachment in it ?
Is the option mail package useful if i am using payloadswapbean module ?
from what i see, It seems that the XMLanonymizer doesn't work for sender mail adapter with attachment. I've tested the configuration on a sender adapter file and works fine.
Anyone already tested it ?
Thanks,
Jean-Philippe
Edited by: Jean-Philippe PAIN on Feb 9, 2010 5:29 PM

Hi Stefen,
Thanks for the answers.
The question is, whether the payloadswapbean is useful at all in a sender mail scenario.
I don't understand this one ! Isn't mandatory in sender adapter mail scenario if you want to read your mail attachment ?
Yes. If you configure the payloadswapbean correct, the XMLanonymizer works on the attachment.
It is not easy to set the payloadswapbean in a correct way. IPost your parameters here, when it does not work for you.
Ok. Maybe my configuration is wrong, please tell.
Processing sequence :
localejbs/AF_Modules/PayloadSwapBean => 0
localejbs/AF_Modules/XMLAnonymizerBean => 1
sap.com/com.sap.aii.adapter.mail.app/XIMailAdapterBean =>mail
module configuration :
swap.keyName =>Content-Disposition
swap.keyName => Content-Description
swap.keyValue=>MailAttachment-1
swap.keyValue=>attachment;filename="MailAttachment-1.xml"
anonymizer.acceptNamespaces =>http://namespace ''
anonymizer.quote => ''
I am on PI 7.1 version and when i am looking in the monitoring(sxmb_moni), it doesn't seems working.
Thanks,
Jean-Philippe
Edited by: Jean-Philippe PAIN on Feb 10, 2010 10:36 AM

Issue with SOAP receiver AXIS adapter

Hi All,
We have a scenario SOAP -- > PI -- > SOAP (axis) using SOAP 1.2 version synchnrous scenario. Using Webservice navigator am trying to trigger a message to PI .
Message has reached to PI box and failing in the receiver SOAP(axis) channel as :
Delivering to channel: Receive_SOAP_BulkFeedback 18.08.2014 10:33:24 Information MP: processing local module localejbs/AF_Adapters/axis/AFAdapterBean 18.08.2014 10:33:24 Error
MP: processing local module localejbs/AF_Adapters/axis/AFAdapterBean
MP: processing local module localejbs/AF_Adapters/axis/AFAdapterBean 18.08.2014 10:33:24 Error MP: exception caught with cause javax.ejb.EJBException: ASJ.ejb.005043 (Failed in component: sap.com/com.sap.aii.axis.app, BC-XI-CON-SOP) Exception raised from invocation of public com.sap.aii.af.lib.mp.module.ModuleData com.sap.aii.adapter.axis.modules.AFAdapterBean.process(com.sap.aii.af.lib.mp.module.ModuleContext,com.sap.aii.af.lib.mp.module.ModuleData) throws com.sap.aii.af.lib.mp.module.ModuleException method on bean instance com.sap.aii.adapter.axis.modules.AFAdapterBean@6bbad627 for bean sap.com/com.sap.aii.axis.app*xml|com.sap.aii.adapter.axis.ejb.jar*xml|AFAdapterBean in application sap.com/com.sap.aii.axis.app.; nested exception is: java.lang.NullPointerException: while trying to invoke the method com.sap.aii.af.lib.mp.module.SModule.process(com.sap.aii.af.lib.mp.module.ModuleContext, com.sap.aii.af.lib.mp.module.ModuleData) of an object loaded from field com.sap.aii.adapter.axis.modules.AFAdapterBean.core of an object
Please help and suggest.

Hi Raja,
The end system is closing the communication. Try to reset your PI ICM instance. Also check if your PI system is affected by this note 1675953 - SSL Client Authentication failed with PI SOAP Axis Adapter
Regards.

Huge Issues with PDF Attachements in Emails

I am using my Q10 as my business device and most of the time I love it, it brought me back to BBRY. But one thing is really causing me headaches and problems I thought were left in the past since a couple of years.
I receive and send a lot of Emails and I rely a lot on this way of communication. But with the Q10, I always have to carry my old iPhone 5 with me, because the Q10 can´t open roughly 50% of all the PDF attachments on Emails. I just found a PDF Viewer which can open those files, but its a hustle which I don´t understand, because its actually the first phone which I owned in the past years which has such an issue in such an essential feature.
For example, one of my employee´s just send me a handwritten checklist as a PDF document via Email and when I try to open the file, the viewer, which is started out of the Email-Programm, says (in german) that an error occured while opening the file. The Acrobat Reader gives the same error-message. qPDF Viewer is able to open the file without an issue at all. Also the iPhone 5, iPad and every Email programm that I tried has no problem to open the file.
My employee used the built-in scan-to-PDF-functionality of one of our HP Officejet 8600 Pro printers in the office to create the file. It was not changed after the scan-process.
I bet that the issue is known, but if I can help, I will provide as much information as you need (incl. sample-files of course), but this problem needs to be fixed immediately. I can´t think of a serious business device which has problems showing several PDF-files, this is something every Smartphone can do since the 8800 or even before that, and without any problems! Not to mention all the toyish Android Smartphones and iPhones on the market. This is a key feature for many many many companies, just imangine you´re in a hurry and you need to decide upon a changed offer, but you´re not able to open the file on your phone? You´ll need to carry an extra device for that, thats not good.

Hey -jo-,
Welcome to the BlackBerry® Support Community Forums.
Currently the BlackBerry Q10 smartphone supports PDF files with true PDF text, rather than scanning images into the PDF. Alternatively, if the sender has the option they can try sending the file as a text file(.txt).
Let me know if you have any other questions.
Thanks.
-HB
Come follow your BlackBerry Technical Team on twitter! @BlackBerryHelp
Be sure to click Kudos! for those who have helped you.Click Solution? for posts that have solved your issue(s)!

Mapping issues with soap sender adapter

Scenario SOAP->XI-> file.
I have configured a sender soap adapter.
When the soap message is sent to XI from third party system using the 'DOC' , SXMB_MONI shows the following format
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:m="http://localhost">
<SOAP-ENV:Body>
 <m:MyOperation>
 <m:a>123</m:a>
 <m:b>abc</m:b> </m:MyOperation>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
But I get a mapping exception..
While the soap message generated through XMLSPY, is processed successfully. The main difference that I can see between the two soap request, "The namespace M: is getting attached to the failed soap request". I have highlighted the difference. How should I handle this?
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>
<SOAP-ENV:Body>
 <m:MyOperation xmlns:m="http://localhost">
 <a>123</a>
 abc
 </m:MyOperation>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Hi,
Are you using XSL mapping for the Same ? If so try to add the NameSpace in the Header. like <xmlns:....Name Space Name/>
Otherwise avoid the Namespace from your message. That can be done while creating the Message Type.
Hope this helps..
Regards,
Moorthy

Issue with SOAP attachment boundary

Similar Messages

Maybe you are looking for