Press "Enter" to skip to content

WHINT DynamicConfiguration Writer



This Adapter Module is able to set the value of a Dynamic Configuration (DC) value, also known as Adapter Specific Message Attribute (ASMA). You can build the name by putting it together from

  • existing DC values or
  • by accessing the XML payload using an XPATH or
  • constants


  • Deploy the SCA/EAR file provided by Whitepaper InterfaceDesign using NWDS/JSPM/SUM/Telnet
  • Check if the deployment was successful in JNDI browser (NWA -> Troubleshooting -> Java -> JNDI Browser) It should appear under Folder WHINT with name DynamicConfigurationWriter


  • Add the Adapter Module in the Module Processor (Sender or Receiver Channel)
  • Name: WHINT/DynamicConfigurationWriter
  • Type: Local
  • Parameters (Input):
    • in.varX = xpath({XPATH on XML payload}) or dc({Key of Dynamic Configuration: NAME NAMESPACE})
    • = {true/false} (search also with xpath in attachment)
  • Parameters (Output):
    • out.dcX.key = {Key of Dynamic Configuration: NAME / NAMESPACE}
    • = {combination of in-Variables with constants/strings}
    • Substring-Values to build the target DC value (name)
      • $var1.substring(startOffset,endOffset)
      • $var2.substring(startOffset)
      • $var1.substring-after(“TEXT“)
      • $var2.substring-before(“TEXT“)


The FileName is built by concatenating the IDoc number with IDoc message type separated by “_” and with a file type “.xml”:

  • in.var1: xpath(//EDI_DC40/DOCNUM)
  • in.var2: xpath(//EDI_DC40/MESTYP)
  • in.var9: dc(FileName
  • out.dc1.key: FileName /
  • $var1+_+$var2+.xml

The screenshot example shows (as an iFlow channel configuration in NWDS) how the FileName is CHANGED by prefixing a constant “DEMO” with the content of XML element “DocumentTypeCode”.


Print Friendly, PDF & Email