SOAP adapter looses attachment name

We have a very annoying problem regarding the SOAP adapter. PI "looses" the attachment names when we send from one to the other PI system with the SOAP adapter. E.g. source attachment name is "invoice.pdf", on the target side it is "attachment-1". It seems to be a general shortcoming/bug of the SOAP adapter. I do not know if it gets lost in the SOAP receiver channel or later in the sender channel of the other party.
Is there any way to get around this, so that the partner receives the correct attachment name ? Some configuration in the SOAP channels ? One solution is to pass a name in the content-type (I think that will be preserved), but that I consider only as workaround.
We have that problem on PI 7.0 and even on PI 7.1
Regards,
Christian Sy

Hello,
The following note may help with this issue
1255507 Attachments not being sent to the receiver
Also you could check:
1522630 XI runtime: Payload ignored due to parsing error
1501345 XI runtime: Manifest <attachment-name> is initial
Regards,
Sarah

Similar Messages

SOAPFault from Integration Server because of attachment name

Hello everyone,
I'm currently building the attachment function into our adapter for IBM Lotus Notes and SAP XI.
In the Sender part, the adapter must add the attachment from Lotus Notes to the XI Message as a payload.
The following source code show how to do this:
/Create a payload from a XI Message/
Payload attachment = xiMessage.createPayLoad();
/Set the attachment name with the file name of the Notes attachment/
/I have problem with this method/
attachment.setName(notesAttachment.getFileName());
/Set the content (byte array) of the attachment/
attachment.setContent(notesAttachment.getBytesContents());
This works well unless no special file name like ("Ättachment") is entered in the method Payload.setName().
Errors will be shown in the Audit Log:
1. SOAPFault received from Integration Server. ErrorCode/Category: XIProtocol/SAP_CODEPAGE_CONVERSION_ERROR; Params: ; AdditionalText: ; ApplicationFaultMessage: ; ErrorStack: Error when converting the code page for character set UTF-8 (code page 4110): Cannot convert character sets for one or more characters.
2. Transmitting the message to endpoint http://kit-was:8000/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during creation of multipart mime object.
and in the Logviewer:
1. enrichMessageData(): Error during retrieving the end-to-end-monitoring information
Thrown:com.sap.aii.rwb.endtoendmonitoring.util.Sxmb_Get_Pmi_Info_Fault_Exception: at sun.reflect.GeneratedConstructorAccessor553.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
But in the "Message content --> SOAP Document", the attachment name can be showed correctly:
- <sap:Payload xlink:type="simple" xlink:href="cid:[email protected]">
<sap:Name>Ättachment</sap:Name>
<sap:Description>üüüäää</sap:Description>
<sap:Type>ApplicationAttachment</sap:Type>
</sap:Payload>
I've no idea, what should I do. Apparently I did every correctly, but why SAP Integration Server didn't work?
The ABAP stack of the XI server should also support Unicode. Our XI server is 04 SP 19.
Please give me some help.
with regards
Xiang

Hi Stefan,
thanks for your reply.
The problem is that String is unicode in Java. The method from SAP is
void setName(java.lang.String name) .
In Java it is only necessary to define charset when create a string based on a bytes array.
String(byte[] bytes, String charsetName)
Constructs a new String by decoding the specified array of bytes using the specified charset.
I got the file name from Lotus Notes as a String and just gave it to the SAP method. Then the Integration Server gave an error message about the name.
Regards
Xiang

Sender mail adapter - attachment name

Hi there
We have configured a sender email adapter to receive text/csv attachments and save them to a file system. What we are having a problem with is reading the attachment name. So we are using Dynamis Configuration to create the file name using the subject line - Which is not ideal. Ideally we would like to use the same name as the origianl attachment but haven't found any way of doing that. We even tried using Content-type in the Variable Header (XHeaderName1) suing variable transport binding but it doesn't show up in the Dynamic Config part of the SOAP message.
Is there any way of reading the name of the file attachment? We are on PI release 7.0.
Any help would be appreciated.
Cheers
Salil

Hi Vitor
There are 2 scenarios that I can think of -
1. You are saving the email attachment as a file. In that case use step 3 in the earlier reply to get the attachment name and save the file witht that name.
2. You are sending the XML straight to a receiver using HTTP, IDOC, JDBC etc. in which case you would need the attachment name much earlier that step 3. For that I guess you would have to write another adapter module on the sender mail adapter(at Position 3 where position1 = payloadswap bean, 2 = custom module to get the attachment name) and add an xml tag to your incoming message. These adapter modules are really powerful and are like user exits in ABAP. In that case you would have to change the Data Type in the Integration repository to reflect that extra tag. Here is some code from a module we wrote to totally change the structure of the xml coming in. The key thing to remember is this module is that you can read the whole message byte by byte. There might be smarter ways of doing it (like using the SAP XML parser factory class) but since I'm not a Java programmer I stuck to the basics. Here's the code( you could also look at the example given in sap help where they remove (or add I'm not sure) CR(carriage return) from CRLF (CR Line feed).
Created on Aug 8, 2007
To change the template for this generated file go to
Window>Preferences>Java>Code Generation>Code and Comments
package jdbcPackage;
import javax.ejb.CreateException;
import javax.ejb.SessionBean;
import javax.ejb.SessionContext;
import com.sap.aii.af.mp.module.*;
import com.sap.aii.af.ra.ms.api.*;
@author Salil.Mehta Soltius NZ Ltd
To change the template for this generated type comment go to
Window>Preferences>Java>Code Generation>Code and Comments
public class jdbcClass implements SessionBean, Module {
 private SessionContext myContext;
 public void ejbRemove() {
 public void ejbActivate() {
 public void ejbPassivate() {
 public void setSessionContext(SessionContext context) {
 myContext = context;
 public void ejbCreate() throws CreateException {
 public ModuleData process(
 ModuleContext moduleContext,
 ModuleData inputModuleData)
 throws ModuleException {
 // put your code here
 try {
 Message msg = (Message) inputModuleData.getPrincipalData();
 XMLPayload payload = msg.getDocument();
 String payEnc = payload.getEncoding();
 byte[] payByte = payload.getContent();
 byte[] payByteOut = new byte[payByte.length];
 byte[] payByteTemp = new byte[payByte.length];
 int i;
 int j;
 int actualCount = 0;
 char xmlTagFound = ' ';
 char endXmlTagFound = ' ';
 char tagFound = ' ';
 System.arraycopy(payByte, 0, payByteTemp, 0, payByte.length);
 // Step 1 - Conversions
 // convert "< to <" and "> to >"
 // convert " to "
 // This will remove any carriage returns and line feeds
 // and the <XML* and </XML* tags plus the <row> and </row> tags
 for (i = 0; i < payByte.length; i++) {
 // convert < to < and > to >
 if (payByteTemp == '&') {
 if (payByteTemp[i + 1] == 'l') {
 if (payByteTemp[i + 2] == 't') {
 if (payByteTemp[i + 3] == ';') {
 payByteTemp = '<';
 payByteTemp[i + 1] = '\n';
 payByteTemp[i + 2] = '\n';
 payByteTemp[i + 3] = '\n';
 if (payByteTemp == '&') {
 if (payByteTemp[i + 1] == 'g') {
 if (payByteTemp[i + 2] == 't') {
 if (payByteTemp[i + 3] == ';') {
 payByteTemp = '>';
 payByteTemp[i + 1] = '\n';
 payByteTemp[i + 2] = '\n';
 payByteTemp[i + 3] = '\n';
 if (payByteTemp == '&') {
 if (payByteTemp[i + 1] == 'q') {
 if (payByteTemp[i + 2] == 'u') {
 if (payByteTemp[i + 3] == 'o') {
 if (payByteTemp[i + 4] == 't') {
 if (payByteTemp[i + 5] == ';') {
 payByteTemp = '"';
 payByteTemp[i + 1] = '\n';
 payByteTemp[i + 2] = '\n';
 payByteTemp[i + 3] = '\n';
 payByteTemp[i + 4] = '\n';
 payByteTemp[i + 5] = '\n';
 // This will take in the initial xml declaration from the Byte array
 // And we also don't want the stuff after the xml declaration till
 // we reach the first <row> tag
 if (xmlTagFound == ' ') {
 if (payByteTemp == '>') {
 xmlTagFound = 'X';
 payByteOut[actualCount++] = payByteTemp;
 if (xmlTagFound == 'X') {
 payByteOut[actualCount++] = '\r';
 continue;
 if (xmlTagFound == 'X') {
 if (payByteTemp == '<') {
 if (payByteTemp[i + 1] == 'r') {
 if (payByteTemp[i + 2] == 'o') {
 if (payByteTemp[i + 3] == 'w') {
 if (payByteTemp[i + 4] == '>') {
 xmlTagFound = 'Y';
 } else {
 continue;
 } else {
 continue;
 } else {
 continue;
 } else {
 continue;
 } else {
 continue;
 // Carriage return and line feed
 if ((payByteTemp == '\r') || (payByteTemp == '\n')) {
 continue;
 // <XML_*> tag
 if (payByteTemp == '<') {
 if (payByteTemp[i + 1] == 'X') {
 if (payByteTemp[i + 2] == 'M') {
 if (payByteTemp[i + 3] == 'L') {
 tagFound = 'X';
 endXmlTagFound = ' ';
 continue;
 // </XML_*> tag
 if (payByteTemp == '<') {
 if (payByteTemp[i + 1] == '/') {
 if (payByteTemp[i + 2] == 'X') {
 if (payByteTemp[i + 3] == 'M') {
 if (payByteTemp[i + 4] == 'L') {
 tagFound = 'X';
 endXmlTagFound = 'X';
 continue;
 // <row> tag
 if (payByteTemp == '<') {
 if (payByteTemp[i + 1] == 'r') {
 if (payByteTemp[i + 2] == 'o') {
 if (payByteTemp[i + 3] == 'w') {
 if (payByteTemp[i + 4] == '>') {
 tagFound = 'X';
 continue;
 // </row> tag
 if (payByteTemp == '<') {
 if (payByteTemp[i + 1] == '/') {
 if (payByteTemp[i + 2] == 'r') {
 if (payByteTemp[i + 3] == 'o') {
 if (payByteTemp[i + 4] == 'w') {
 if (payByteTemp[i + 5] == '>') {
 tagFound = 'X';
 continue;
 if ((payByteTemp == '>') && (tagFound == 'X')) {
 tagFound = ' ';
 continue;
 if (tagFound == ' ') {
 if (endXmlTagFound == 'X') {
 continue;
 payByteOut[actualCount++] = payByteTemp;
 byte[] payByteExp = new byte[actualCount];
 System.arraycopy(payByteOut, 0, payByteExp, 0, actualCount);
 payload.setContent(payByteExp);
 msg.setDocument(payload);
 inputModuleData.setPrincipalData(msg);
 } catch (Exception e) {
 ModuleException me = new ModuleException(e);
 throw me;
 return inputModuleData;

Axis SOAP Adapter - Setting MIME headers for attachements (Handlers?)

Hello,
I need to know if/how it is possible to set the individual MIME headers of the parts making up a multipart/related SOAP message using only standard Axis Handlers e.g. "com.sap.aii.axis.xi.XI30DynamicConfigurationHandler" (as described in the Axis FAQ in Note 1039369).
I know I can insert transport headers using "com.sap.aii.axis.xi.XI30DynamicConfigurationHandler", but I can't see a way of setting a MIME header for, say, the first part (i.e. the SOAP part) or the second part (e.g. an attachement). Is this possible without writing your own Axis handler? The Axis FAQ, in "Advanced usage question 31" implies that you can set MIME Headers but only shows an example of setting the transport header.
I am using the SOAP Adapter to send a message comprising and XML message (in the SOAP body) and a PDF document (as an attachement). The external company this is being sent to requires that we have specific values for the "Content-Id" MIME header in each part of the multipart/related document. This is why I need to understand if we can do this without writing our own Axis Handler.
Incidentally, I have tried to write a custom Axis Handler but couldn't get PI to find it after deployment. I did this by inserting my JAR file in the "com.sap.aii.adapter.lib.sda" (as per Notes 1039369 / 1138877) and then using JSPM. After deployment, though, when I tried to start the SOAP Adapter I got the following error in the RWB: "failed to initialize: org.apache.axis.ConfigurationException: java.lang.ClassNotFoundException: com.hp.gerryaxis.GerryAxis..." (my class was called "GerryAxis" and I placed this in package "com.hp.gerryaxis"). I'm not an experienced Java programmer (my background is in ABAP), so if anyone can suggest whey I'm getting this error, I'd be very grateful (for example, could my choice of package be causing the problem?).
Thanks for your help.

I went ahead and wrote a simple bespoke Axis Handler. By invoking this from the standard "HandlerBean" in the module processor of my communication channel, I was able to overwrite and set new MIME headers in the Attachment Parts of my SOAP Message. I was also able to change the contents of the SOAP Envelope; for example, I found I could easily delete the SOAP Header. However, I've encountered a problem when I try and update the MIME headers of the SOAP Part i.e. the Part of the multipart/related message containing the SOAP Envelope.
Does anyone know why I can't seem to change the MIME headers of the SOAP Part?
The Axis API calls I used were as follows:
(1) To update the MIME headers of attachements in my SOAP message:
(a) Message = MessageContext.getCurrentMessage()
(b) Iterator = Message.getAttachments()
(c) AttachmentPart = Iterator.getNext()
(d) AttachmentPart.setMimeHeader(name, value)
This works.
(2) To update the MIME headers of the SOAP (root) Part:
(a) Message = MessageContext.getCurrentMessage()
(b) SOAPPart = Message.getSOAPPart()
(c) SOAPPart.setMimeHeader(name, value)
This DOESN'Twork - the MIME headers of the SOAP Part never change.
(3) To update the SOAP Envelope (delete the SOAP Header):
(a) Message = MessageContext.getCurrentMessage()
(b) SOAPPart = Message.getSOAPPart()
(c) SOAPEnvelope = SOAPPart.getEnvelope()
(d) SOAPHeader = SOAPEnvelope.getHeader()
(e) SOAPHeader.removeContents()
This works.
I just don't understand why the call to SOAPPart.setMimeHeader() doens't work when I try and insert new MIME headers to the SOAP Part (e.g. "Content-Name") or when I try and change existing MIME headers there (e.g. "Content-ID"). I don't get any errors.
The code of my handler is:
@(#)GerryAxis.java
Set MIME headers in the SOAP and specified attachment part of a message
package com.hp.handlers;
import org.apache.axis.handlers.BasicHandler;
import org.apache.axis.AxisFault;
import org.apache.axis.attachments.AttachmentPart;
import org.apache.axis.Message;
import org.apache.axis.MessageContext;
import java.util.Iterator;
import javax.xml.soap.SOAPMessage;
import javax.xml.soap.SOAPEnvelope;
import javax.xml.soap.SOAPHeader;
import javax.xml.rpc.handler.soap.SOAPMessageContext;
The <code>GerryAxis</code> handler class sets MIME headers.

This handler accepts the following parameters:
<ul>
<li>name: Name of header
<li>value: Value for header
<li>attachment: Attachment number
</ul>
public class GerryAxis extends BasicHandler {
/* (non-Javadoc)
@see org.apache.axis.Handler#invoke(org.apache.axis.MessageContext)
public void invoke(MessageContext msgContext) throws AxisFault {
 int i=0;
 boolean found = false;
 AttachmentPart ap = null;
 javax.xml.soap.SOAPPart sp = null;
 StringBuffer debug = new StringBuffer();
 try {
 // The MIME header change is controlled from the parameters "name", "value", "attachment" which are
 // set in the module processor as parameters.
 String name = (String)getOption("name");
 String value = (String)getOption("value");
 String attachment = (String)getOption("attachment");
 Message msg = msgContext.getCurrentMessage();
 // Get the SOAP Part (the part holding the SOAP Envelope
 sp = msg.getSOAPPart();
 if (sp == null)
 debug.append("getSOAPPart returned <null> / ");
 // Set a MIME header in the SOAP Part - THIS DOES NOT WORK - WHY?
 sp.setMimeHeader(name,value);
 // Remove the SOAP Header for the Envelope - this works fine
 SOAPEnvelope se = sp.getEnvelope();
 SOAPHeader sh = se.getHeader();
 sh.removeContents();
 // For debugging - writes some debuggin information to a "DEBUG" MIME header in the first Attachement Part
 debug.append("name = " + name +" / ");
 debug.append("value = " + value +" / ");
 debug.append("attachment = " + attachment + " / ");
 debug.append("getMimeHeader for SOAPPart returned " + sp.getMimeHeader(name)[0] + " / ");
 debug.append("getContentId for SOAPPart returned " + sp.getContentId() + " / ");
 // Update the specified attachement's MIME header - this works fine
 Iterator it = msg.getAttachments();
 while (it.hasNext()) {
 i++;
 ap = (AttachmentPart) it.next();
 if (i == new Integer(attachment).intValue()) {
 found = true;
 break;
 if (found) {
 ap.removeMimeHeader(name);
 ap.setMimeHeader("DEBUG",debug.toString());
 ap.setMimeHeader(name,value);
 msg.saveChanges();
 catch (Exception e) {
 throw AxisFault.makeFault(e);
Thanks
Edited by: Gerry Deighan on Oct 3, 2010 10:27 PM

Modify the SOAP attachment name

hi,
I have a Service with Party, which sends messages in SOAP format to XI.
When the SOAP message sent to XI contains a '&' character in its attachment name, the message gets failed to processed through XI.
I believe this happens since '&' character is a wildcard character in XML hence XI expects a escape character sequence following it and cannot parse through the '&' character. Also as per the IR tests executed for the SOAP message, when the '&' is replaced with its escape sequence the message is processed through successfully.
Is it possible to replace the '&' character with its escape sequence in the SOAP attachment name before it is processed by the XI Integration Engine. That is at the adapter level?
regards,
Diptee
Edited by: diptee s on Oct 26, 2010 4:47 PM

hi,
i have created the Java Mapping .
in the pdf document How Tou2026Work with Character Encodings in Process Integration from SAP, for the Escape sequences it is said that for adding Escape sequences to the unescaped characters, add the Java mapping before the required mapping.
however, i am not able to test the interface in the IR even after adding the new Java mapping.
please suggest.
regards,
Diptee

Email attachment name in sender mail adapter to the receiver file adapter

HI ,
Ths is regarding email to file scenario. I am trying to create file (in rceiver file adapter) with the same name as the email attachment that i read from mail sender adapter. I want ro use adapter module for this. I could find from blogs that there is module - GetAttachmentName - available that i can use for this in sender mail adapter.
Can you please let me know what whetehr i neeed to mention any module key and parameters for this.
I assume , i need to do following steps :Please confirm.
1. i can use this module - after payload swap module and before standard mail adapter module in sender mail adapter
2. select ASMA option in advanced tab in sender mail adapter
3. In receiver file adapter select ASMA option in advanced tab in sender mail adapter
4. Also select file name option in ASMA in sender mail adapter
Thanks,
Vamsi

Hi Vamsi,
your scenario is also described here: Re: sender mail adapter - attachment name
If you use the Module getAttachmentName, which is described here,
http://wiki.sdn.sap.com/wiki/display/XI/AdapterModulePI7.0GetAttachmentName
your scenario should work as you described it.
You just need to make sure that the Attachment Name that you read in the first place, is mapped to the Filename Attribute of the
Fileadapter (http://sap.com/xi/XI/System/File/FileName).
regards,
Daniel

Need to get the Mail attachment name as it is to the receiver file adapter

I am doing a Mail to File scenario. I need to get the attachment from the mail and store it on the file server. I am using the PayloadSwap bean in the sender mail adapter. My requirement is to carry forward the attachement name as it is to the receiver file adapter side and store the file with the same name.
Did any one try doing this? I was looking at developing an adapter module but got struck as I could not find whether the attachement name is stored in the XI payload after it has got swapped using the swap bean.
Any help would be appreciated.
VJ

Oops pressed the send key. Take two.
This is becoming a damn nightmare. When I run the adapter I am getting ModuleExceptions. Can you pass your eyes over these Java config settings to see what I am doing wrong. Using NWDS CE 7.1 with PI 7.1 both at SP07. All the imports were taken from PI 7.1 after SP07 was applied. The build id of NWDS is
SAP NetWeaver Developer Studio
SAP NetWeaver 7.1 Composition Environment SP07 PAT0001
Build id: 200901152336
APPLICATION.XML
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN"
"http://java.sun.com/dtd/application_1_3.dtd">
<application>
<display-name>MailPOP_EAR</display-name>
<description>EAR description</description>
<module>
<ejb>MailPOP_EJB.jar</ejb>
</module>
</application>
APPLICATION-J2EE-ENGINE.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application-j2ee-engine SYSTEM "application-j2ee-engine.dtd">
<application-j2ee-engine>
<reference reference-type="hard">
<reference-target provider-name="sap.com" target-type="service">engine.security.facade</reference-target>
</reference>
<reference reference-type="hard">
<reference-target provider-name="sap.com" target-type="library">engine.j2ee14.facade</reference-target>
</reference>
<reference reference-type="hard">
<reference-target provider-name="sap.com" target-type="service">com.sap.aii.af.svc.facade</reference-target>
</reference>
<reference reference-type="hard">
<reference-target provider-name="sap.com" target-type="interface">com.sap.aii.af.ifc.facade</reference-target>
</reference>
<reference reference-type="hard">
<reference-target provider-name="sap.com" target-type="library">com.sap.aii.af.lib.facade</reference-target>
</reference>
<reference reference-type="hard">
<reference-target provider-name="sap.com" target-type="library">com.sap.base.technology.facade</reference-target>
</reference>
<fail-over-enable mode="disable" />
</application-j2ee-engine>
EJB-J2EE-ENGINE.XML
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-j2ee-engine SYSTEM "ejb-j2ee-engine.dtd">
<ejb-j2ee-engine>
<enterprise-beans>
<enterprise-bean>
<ejb-name>GetMailAttachment</ejb-name>
<jndi-name>GetMailAttachment</jndi-name>
<session-props/>
</enterprise-bean>
</enterprise-beans>
</ejb-j2ee-engine>
EJB-JAR.XML
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans
2.0//EN"
"http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<description>EJB JAR description</description>
<display-name>EJB JAR</display-name>
<enterprise-beans>
<session>
<ejb-name>GetMailAttachment</ejb-name>
<home>com.sap.aii.af.lib.mp.module.ModuleHome</home>
<remote>com.sap.aii.af.lib.mp.module.ModuleRemote</remote>
<local-home>com.sap.aii.af.lib.mp.module.ModuleLocalHome</local-home>
<local>com.sap.aii.af.lib.mp.module.ModuleLocal</local>
<ejb-class>sample.GetMailAttachment</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
</ejb-jar>
SENDER MAIL ADAPTER modules
1 AF_Modules/PayloadSwapBean Local EB 1
2 GetMailAttachment Local EB 2
3 sap.com/com.sap.aii.adapter.mail.app/XIMailAdapterBean Local EB 3
1 swap.keyName payload-name
1 swap.keyValue MailAttachment-1
RECEIVER FILE MODULES
1 localejbs/AF_Modules/DynamicConfigurationBean Local Enterprise Bean 1
2 localejbs/CallSapAdapter Local Enterprise Bean 2
1 key.0 write http://sap.com/xi/XI/System/File FileName
1 value.0 message.interface
VARIABLE FILENAME SUBST WITH ASMA TURNED ON
fName message:interface_name
JAVA SOURCE
package sample;
import javax.ejb.CreateException;
import javax.ejb.SessionBean;
import javax.ejb.SessionContext;
import com.sap.aii.af.lib.mp.module.Module;
import com.sap.aii.af.lib.mp.module.ModuleContext;
import com.sap.aii.af.lib.mp.module.ModuleData;
import com.sap.aii.af.lib.mp.module.ModuleException;
import com.sap.engine.interfaces.messaging.api.Message;
import com.sap.engine.interfaces.messaging.api.MessagePropertyKey;
import com.sap.engine.interfaces.messaging.api.TextPayload;
import com.sap.engine.interfaces.messaging.api.XMLPayload;
import com.sap.aii.af.service.cpa.Channel;
@ejbHome <{com.sap.aii.af.lib.mp.module.ModuleHome}>
@ejbLocal <{com.sap.aii.af.lib.mp.module.ModuleLocal}>
@ejbLocalHome <{com.sap.aii.af.lib.mp.module.ModuleLocalHome}>
@ejbRemote <{com.sap.aii.af.lib.mp.module.ModuleRemote}>
@stateless
<code>GetMailAttachment</code>
@SuppressWarnings("unused")
public class GetMailAttachment implements SessionBean, Module {
 private static final long serialVersionUID = 7612238514043673502L;
 private SessionContext myContext;
 private MessagePropertyKey myFileName;
 public void ejbRemove() {
 public void ejbActivate() {
 public void ejbPassivate() {
 public void setSessionContext(SessionContext context) {
 myContext = context;
@throws CreateException
 public void ejbCreate() throws CreateException {
 public void getMessageProperty(MessagePropertyKey FileName) {
 myFileName = FileName;
@param moduleContext
 Contains data of the module processor that might be important
 for the module implementation such as current channel ID
@param inputModuleData
 Contains the input XI message as principal data plus eventual
 set supplemental data
@return ModuleData Contains the (changed) output XI message. Might be the
 response message if the module is the last in the chain.
@exception ModuleException
 Describes the cause of the exception and indicates whether
 an retry is sensible or not.
 @SuppressWarnings("deprecation")
 public ModuleData process(ModuleContext moduleContext,
 ModuleData inputModuleData) throws ModuleException {
 try {
 Message msg = (Message) inputModuleData.getPrincipalData();
 TextPayload payload = msg.getDocument();
 String contentType = payload.getContentType();
 // Content Type could be something like
 // text/plain;charset="UTF-8";name="file.txt"
 contentType = contentType.replaceAll("\"", "");
 int i = contentType.lastIndexOf("=") + 1;
 String fileName = contentType.substring(i);
 msg.setMessageProperty(myFileName, fileName);
 inputModuleData.setPrincipalData(msg);
 } catch (Exception e) {
 return inputModuleData;
JAVA ERRORS
2009-02-04 11:41:14 Information Mail: calling the module processor for channel LMK_Common_Mail_Sender
2009-02-04 11:41:14 Information Swap: swapping by payload-name ? MailAttachment-1
2009-02-04 11:41:14 Information Swap: successfully swapped
2009-02-04 11:41:14 Information Mail: message leaving the adapter (call)
2009-02-04 11:41:14 Information The application tries to send an XI message asynchronously using connection AFW.
2009-02-04 11:41:14 Information Backward validation is enabled
2009-02-04 11:41:14 Error Unable to validate the message with message ID 8702df71-f254-11dd-9b9b-001a64a73518
2009-02-04 11:41:14 Error Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Content is not allowed in prolog.
2009-02-04 11:41:14 Error Mail: error occured: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Content is not allowed in prolog.
2009-02-04 11:41:14 Error Mail: error occured: com.sap.aii.af.lib.mp.module.ModuleException

Dynamic attachment name in receiver mail adapter

Hi all,
i am doing a receiver mail scenario (PI 7.1). my requirement is like this :
Receiver file need to be send in receiver mail attachment and attachment name should be dynamic
format for the attachment name should be like this
R+value from a particular field in payload +Timestamp
for example my file name should be like this R001_510815021009062532.xml
which is R+ 001_510815 + 021009062532 + .xml
can anybody suggest me how to go for this requirement? is ther any UDF or should i go for adapter module developement?
Thanks
sandeep sharma
Edited by: sandeep sharma on Oct 13, 2009 8:55 AM

Hi K Fatima,
I read your solution.I have a similar requiement but I need to send the entire output payload as an attachment,so I am using XSLT to send the payload as an attachment.
I am creating the file name through dynamic configuration in XSLT but the name of attachment is not as required but its any random generated name:
*code used:*
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:map="java:java.util.Map"
xmlns:dyn="java:com.sap.aii.mapping.api.DynamicConfiguration"
xmlns:key="java:com.sap.aii.mapping.api.DynamicConfigurationKey">
<xsl:output method="xml" version="1.0" encoding="UTF-8" />
<xsl:output indent="yes" />
<xsl:param name="inputparam"/>

<xsl:template match="*">
<ns:Mail xmlns:ns="http://sap.com/xi/XI/Mail/30">
<xsl:variable name="new-value" select="Shipment/InternalShipmentNum"/>
<Subject>Mail</Subject>
<From>xyz</From>
<To>abc</To>
<xsl:variable name="dynamic-conf"
 select="map:get($inputparam, 'DynamicConfiguration')" />
 <xsl:variable name="dynamic-key"
 select="key:create('http://sap.com/xi/XI/System/File', 'Directory')" />
 <xsl:variable name="dynamic-value"
 select="dyn:get($dynamic-conf, $dynamic-key)" />
 <xsl:variable name="new-value"
 select="concat($dynamic-value, 'subfolder\')" />
 <xsl:variable name="dummy"
 select="dyn:put($dynamic-conf, $dynamic-key, $new-value)" />

<Content_Type>application/xml</Content_Type>
<!Content Description>
<Content_Disposition>attachment;filename "<xsl:copy-of select="$new-value"/>"</Content_Disposition>

<Content_Description><xsl:copy-of select="$new-value"/></Content_Description>
<Content>
<xsl:copy-of select=".">
<xsl:apply-templates/>
</xsl:copy-of>
</Content>
</ns:Mail>
</xsl:template>
</xsl:stylesheet>
Please suggest ! I need the value in "Shipment/InternalShipmentNum" as name of attachment.
Thanks in advance!
Indu Khurana

Setting interface name dynamically from client for SOAP Adapter...

Hi,
does anyone have experience in setting the sender interface name in the HTTP-SOAP request dynamically? I have followed the instructions in "How To Use the XI 3.0 SOAP Adapter" on page 17 (see also SAP Note 856597) which say:
"If you select Use Encoded Headers and Use Query String,
[...]The sender SOAP adapter creates the XI message header according to the
information provided in the query string. [...] In the sender SOAP adapter, you can use only some of the parameters, but the first
parameter must always be the version. For example, you send from the Web service client to the following URL: http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet?channel=<party>:<service>:<channel>&version=3.0&Interface=http%3A
%2F%2Fsap.com%2Ftest%5ETest
This will overwrite the default interface and namespace of the sender channel."
This is exactly what I need! However, what I actually get as a response following this description is a SOAP:Fault with a java.lang.StringIndexOutOfBoundsException: String index out of range: -1.
Has anyone got this to work properly?
Thanks in advance.

Thank you for your input. I am using the following format for the call (with "x" standing for one letter each):
http://xix.xxx.xx.xxx:5xx00/XISOAPAdapter/MessageServlet?channel=:xx_xxx_xxx_xxxx:xx_xxx_x_SOAP_S&version=3.0&Interface=http%3A%2F%2Fxxxxxxxx.xx%2Fxxxxxx%2Fxxxxxxxxxxxxxxxxxxxxxxxx%5Exxxxxxxxxxxxxxxxxxxxxx
Anything wrong with that? With unchecked "Use Encoded Headers" and "Use Query String" it works fine (default interface) but as soon as I set these flags I get the SOAP-Fault response.
We are on XI 3.0 SPS18.

Setting dynamic attachment name in mail adapter

Hi experts,
I have a mail adapter that send e-mails from ECC to several address.
I have configured dynamically the FROM and TO field using the code showed below in message mapping:
public String SetMailParameters(String Mail_address_to, Container container){
//write your code here
String valueFrom = "my_address";
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key1 = DynamicConfigurationKey.create( "http://sap.com/xi/XI/System/Mail", "THeaderFROM");
DynamicConfigurationKey key2 = DynamicConfigurationKey.create( "http://sap.com/xi/XI/System/Mail", "THeaderTO");
conf.put(key1, valueFrom);
conf.put(key2, Mail_address_to);
return "";
In communication channel I have checked ASMA and variable transport binding (using XHeaderName1 and 2), mail package is not checked.
It works fine!
My question is:
I need to dynamically configure also the Attachment name: is it possible?
I've tried adding the code below:
DynamicConfigurationKey key3 = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
conf.put(key3,Attachment_name);
and also
Transform.ContentDisposition attachment;filename=<FileName>
in Message TransformBean in communication channel, but it doesn't work!!!
Any idea?
Thanks
Fabio Boni

Hi,
thanks a lot!!
ASMA and variable transport binding must be checked or not?
it raise an error in runtime workbench message monitoring:
2010-09-02 17:41:15 Success Mail: calling the adpter for processing
2010-09-02 17:41:15 Error Mail: call failed; com.sap.aii.messaging.util.XMLScanException: expecting end tag: Mail, but found {'}Content_Disposition at state 1
2010-09-02 17:41:15 Success Mail: sending a delivery error ack ...
2010-09-02 17:41:15 Success Mail: sent a delivery error ack
2010-09-02 17:41:15 Error Mail: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: com.sap.aii.messaging.util.XMLScanException: expecting end tag: Mail, but found {'}Content_Disposition at state 1
2010-09-02 17:41:15 Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: com.sap.aii.messaging.util.XMLScanException: expecting end tag: Mail, but found {}Content_Disposition at state 1
2010-09-02 17:41:15 Error Exception caught by adapter framework: com.sap.aii.messaging.util.XMLScanException: expecting end tag: Mail, but found {}Content_Disposition at state 1
2010-09-02 17:41:15 Error Delivery of the message to the application using connection Mail_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: com.sap.aii.messaging.util.XMLScanException: expecting end tag: Mail, but found {}Content_Disposition at state 1.
This is my message in message monitoring:
<?xml version="1.0" encoding="UTF-8" ?>
- <ns1:Mail xmlns:ns1="http://sap.com/xi/XI/Mail/30">
<Content_Disposition>"attachment; filename="MyFileName.txt"</Content_Disposition>
<Content>ZLF;0001000079;Dealer Motors UK</Content>
</ns1:Mail>
In message mapping with target message mail package I've linked Content_Disposition with the constant
"attachment; filename="MyFileName.txt"
If I cancel this relation the mail arrives correctly.
One other thing: when I took mail.xsd from SAP the fields Content_Disposition and Content_Description weren't in, so I added them manually in XSD.
thanks
Edited by: Fabio Boni on Sep 2, 2010 5:42 PM
Edited by: Fabio Boni on Sep 2, 2010 6:06 PM

Change Queue Name in Sender Soap Adapter (or make it dynamic)

Hello SDN!!!!
We have a scenario where we want to make a message EOIO and I have set the Queue Name in the Sender Soap Adapter and this works great. BUT it is needed to have a more specific queue name (based on order numbers not interface name) So with this being said, Is there any way to change the queue name or append to it from the Soap Sender Adapter. I see it is possible to write a Module Bean, but the Message object returned from the ModuleContext is a scaled down version of the normal message object. Any help would be greatly appreciated
Cheers
Devlin

Is this the only way to change the queue name for Soap Sender? I don't think it is possible for them to do this, as their urls are static when calling us

Sender SOAP Adapter: zipped Payload or zipped Attachement possible?

Hi,
I've a SOAP --> PI --> Proxy Scenario. As the payload of the message can become quite huge (around 10MB), I'd like to zip the message.
From the documentation it's not clear for me if the Sender SOAP Adapter can be enhanced with the standard PayloadZipBean:
"You cannot add your own modules to this adapter" --> so is it possible to use modules provided by SAP?
If it's not possible: is there another way to send the message zipped via SOAP, e.g. as a additional attachement to the SOAP message, and to unzip the attachement / use the content of it as message payload for mapping?
Please note: usage of SOAP is a must for that scenario.
Best regards
Holger

> File size is a question due to limited network speed between sender and PI. If I can reduce the data package to be transferred, it'd be a big help. Therefore I'd like to zip the message.
In this case it would be sufficient to use Content-Encoding gzip.
This is part of the HTTP protocol and will be unzipped automatically by the HTTP framework, so you need not do anything special in SOAP adapter.
See http://tools.ietf.org/html/rfc2616#section-14.11
Check if your SOAP client is able to use that.
Regards
Stefan
Edited by: Stefan Grube on Mar 31, 2009 2:11 PM

How to send original filename as the attachment name through mail adapter?

Hi,
I have a File to Mail scenario where the file is picked up from a folder in R/3 system and is sent as an attachment through mail. The requirement is to send the file unconverted and with the same file name.
When tried without creating any ESR objects, it was sending the file with the name Untitled.xml.
Since the filename has to be picked dynamically, I am not able to configure it through module parameters also (where we can set it through Content_Disposition)
I tried configuring it as mentioned in the following link: [http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=138084630]
But still it is going as Untitled.xml with the whole mail package as the content of the attachment.
Any pointers to solve this issue will be of great help.
Thanks
Justin

there is no standard way so you will have to write module beans.
in other way:
XI Mail Adapter: An approach for sending emails with attachment with help of Java mapping - XI Mail Adapter: An approach for sending emails with attachment with help of Java mapping
Dynamic name in the mail attachment - pseudo "variable substitution" :
XI: Dynamic name in the mail attachment - pseudo "variable substitution"
Dynamic attachment name in receiver mail adapter

Change attachment name using mail adapter

Hi All,
I have a problem changing the attachment name in my scenario. I use Mail scenario to send a pdf Attachment from R/3 to email address. Everything working fine except the attachment name that becoming untitled.pdf and untitled.txt.
Communication Channel setting :
message protocol : xipayload
transport protocol : smtp
checked use mail package
checked keep attachment
I have use MessageTransformBean in my receiver adapter, but no luck. It was produce an error.
anyone have an idea to solve my problem?
thx,
Robby

Hi,
You need to go to the Module tab of the Mail adapter receiver communcation channel and give the parameter as Transform.contentDisposition and its value as attachment ( since you needed the output to be sent as an attachment) and give the name of the attachment as you required.
Please see the help page : [http://help.sap.com/saphelp_nw04/helpdata/en/57/0b2c4142aef623e10000000a155106/frameset.htm] for more details and more options of the parameters.
Regards,
Kalpana.

Problem: Original Attachment Name from SOAP Sender changes to attachment-1

Hi everybody,
we have a scenario where a SOAP sender receives a xml message describing several documents. Each document has a mime type and a file name, size, md5 checksums etc as attributes.
The documents are send as attachments with the same Web service in SWA(SOAP with attachment style).
The web service calls an ABAP proxy provider class in a R/3 backend.
The ABAP proxy class will save the attached documents for further processing and must use the original document names.
At the soap communication channel monitoring(Java Stack) we still see the original attachment names in the message content tab.
At the Integration Server(sxmb_moni) the attachment name changes to attachment-1, attachment-2 and so on.
Using the method
IF_AI_ATTACHMENT ->GET_DOCUMENT_NAME
in the provider ABAP proxy class returns the name attachment-1.
We can see that there is a mapping of the new attachment-1 name to the old, original name in the manifest section of this message on the Integration server.
Is there a way to access the manifest section at a provider ABAP proxy class? Or otherwise a PI configuration setting to preserve the original attachment names.
Thanks a lot,
Heiko
=> PI 7.1 SP9

Hi Stefan,
(I was hoping you would find that thread ...)
I see a good reason why the attachment names are changed as the PI message protocol sends the main document as an attachment as well. So no problem with that because the information of the mapping old to new names still exists in the manifest part and is visible at the sxmb_moni.
We see a manifest part like this (Sorry cant post the whole xml doc as the formatting for longer messages isn't working in the forum)
<SAP:Payload xlink:href="cid:4cc43edd-839f-423f-b7c6-7e44294d663a_sig.p7m">
<SAP:Name>attachment-1</SAP:Name>
<SAP:Description>attachment</SAP:Description>
<SAP:Type>ApplicationAttachment</SAP:Type>
</SAP:Payload>
The (red) cid entry is the original file name. This manifest is from the sxmb_moni in the r/3 backend. So all the information is there.. The question is how to retrieve this information .. Any idea?
Best Regards,
Heiko Bergmann

SOAP adapter looses attachment name

Similar Messages

Maybe you are looking for