Risks in migrating to ICO- there are chances that your java code will not work as expected even after successfully test within abap engine configuration

We have been asked to promote ICO usage and we heard many wonderful statements about how fast it is.

Unfortunately migration to ICO is not painless and often you will discover ICO limitation  especially in handling the Java code embedded in your mapping.

I therefore decided to share all my findings that has been already shared with SAP through proper SAP messages and in some cases fixed with patch releases.

Attachment name  and content type change (recognized as bug .Note 1852011 might solve it)

Pseudo code reported below could be used to change the content type and the name of the attachments or even only 1 of the attributes :

  1. OutputAttachments.getOutputAttachments().setAttachment(OutputAttachments.getOutputAttachments().create(<new name>,<new content type>,data);

where

Attachment could be retrieved through

InputAttachments inputAttachments = globalContainer.getInputAttachments();

……some code…

  1. inputAttachments.getAllContentIds(false);

scanning the entire vector of content IDs we could easily get the content ID of every single attachment 

Attachment attachment = inputAttachments.getAttachment(contentId);

and therefore its content and content type

  1. attachment.getContent());
  2. attachment.getContentType(),

similar code is referenced here:

http://scn.sap.com/message/14160371#14160371

http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/07/01/retaining-soap-adapter-attachment-names

Attachment name (still not recognized as bug)

The attachment name is not reflected in the SOAP attachment name,as result missing the information about name and extension. Test has been performed with Advanco SFTP adpter.

Attachment handling resulting in doubled attachment( Note 1852011 should solve it)

The attachment handling might result in doubled attachment if using below reported instruction

Code:outputAttachments.removeAttachment(contentId);

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. Anand V D

    Hi,

    We had this issue when we had created an interface on PO system using java mapping to pick a file from NFS and send it as mail attachment with same name as the input file along with one more attachment.

    The mail had the file attachment but its filename never retained with dynamic configuration. Even we tried to give a new name to the file in java mapping but it dint work. And then after a suggestion from a friend we tried the same interface on a dual stack PI using classical interface and it worked perfectly as expected. Then we concluded that using ICO we cannot rename attachments in java mapping.

    Thanks,

    Anand

    (0) 

Leave a Reply