text: In this example, you can see that we defined a transform that is named MyTXFRM_EXE, which 
  calls the transform command**txfrm.exe**, which is defined in the <CmdLineExe> tag. 
  
  The <TransformName> is used as the viewer name when it calls the ODWEK Retrieve APIs. 
  From this configuration, ODWEK knows that the transform requires RECORDLENGTH, 
  CARRIAGECONTROL, CODEPAGE, and OUTPUTFILE information from Content Manager OnDemand, 
  and can set it on the**cmdline**by using the options that are specified in each related XML tag. 
  
  Also, the**txfrm.exe**requires additional information to be passed on the**cmdline**. The**-r**that 
  is specified in the <Cmdlineparm> tag has no meaning to Content Manager OnDemand, so it is 
  passed through and set on the**cmdline**call to the**txfrm.exe**. 
  
  In the custom Java code, the call to retrieve the data from ODWEK includes the <Transform 
  Name> that is specified in the XML and looks like the following line: 
  
  "byte[] transformedDocument = ODHit.retrieve("MyTXFRM_EXE"); 
  
  From this example definition, ODWEK calls the specified transform with the following**cmdline**
  executable file. Details for the items within “< >” are provided by ODWEK from the Content 
  Manager OnDemand data definitions: 
  
  "c:/opt/txfrm.exe -lm <*record len*> -x <*carriage control*> -a <*codepage*> -o <*output*
  *file name*> -r PDF" 