Adapter development: binary data and adapter specific properties?

Question

Hi,
We have succesfully developed our own SFTP adapter based on the J2SSH Maverick library (http://www.sshtools.com/showMaverick.do) and the sample file adapter that comes with XI.
There are 2 features we would like to implement as well, but lack the necessary documentation and sample code.
<b>1st Binary data</b>
We do not succeed in transporting binary data via our SFTP adapter (both text and xml go fine).  While debugging, we see that the binary data are correctly picked up, but the actual payload appearing in message monitoring is much larger.  When we write the message to a file again, the data have changed (size has e.g. increased importantly from 127180 bytes to 218198 bytes).  According to the sample adapter code,  the contenttype "application/octet-stream"  should be specified.  But the standard XI file adapter itself seems to specify "application/octet-stream".
<b>2nd Adapter specific properties (DynamicConfiguration)</b>
How can we set adapter specific properties in our own adapter code?  Where are the Java docs of the API?  Is this somewhere documented?
If you would have more information (or pointers), please post it as a response to this message.
Kind regards, Guy Crets
<b>Code snippet:</b>
XIMessageFactoryImpl mf = new XIMessageFactoryImpl();
Message msg = mf.createMessageRecord(fromParty, toParty, fromService, toService, action, actionNS);
msg.setDeliverySemantics(DeliverySemantics.ExactlyOnce);
// In case of XML documents it is not necessary to set the contentType or encoding
// But: take care that the encoding definiton in the XML document corresponds to the encoding used
if (msgText.indexOf("<?xml") != -1)
  // Check whether the payload is a XML document. If not, treat it as binary to demonstrate how
  // binary main documents work
  // First create a XML Payload                    
  XMLPayload xp = null;
  xp = msg.createXMLPayload();
  xp.setText(msgText);
  xp.setName("MainDocument");
  xp.setDescription("XI AF Sample Adapter Input: XML document as MainDocument");
  msg.setDocument(xp);
// In case of binary documents use the Payload super class methods to fill the XMLPayload object
else
  // Check whether the payload is a XML document. If not, treat it as binary to demonstrate how
  // binary main documents work
  // First create a XML Payload                    
  XMLPayload xp = null;
  xp = msg.createXMLPayload();
  //xp.setContentType("application/octet-stream");
  xp.setContentType("application/xml");
  xp.setName("MainDocument");
  xp.setDescription("XI AF Sample Adapter Input: Binary as MainDocument");
  xp.setContent(msgData);
  // Finally set the main document in the message
  msg.setDocument(xp);          
TRACE.debugT(SIGNATURE, XIAdapterCategories.CONNECT_AF, "Message object created and filled.");
ModuleData md = new ModuleData();
md.setPrincipalData(msg);

Answer 1

Hello Moorthy,
I know this part of the documentation.
So I set the indicator within the communication channel.
Now, I have to fill the dynamic configuration during my mapping. My code looks like following:
DynamicConfigurationKey keyURL =  DynamicConfigurationKey.create("http://sap.com/xi/XI/System/HTTP", <b>XXXXX</b>);
// access dynamic configuration
DynamicConfiguration conf = (DynamicConfiguration) param.get (StreamTransformationConstants.DYNAMIC_CONFIGURATION);
// set value
conf.put(keyURL, url);
So what has to be filled instead of XXXXX ?
Regards,
  Marc