File Reusability in Plug-in Activities

The file reusability scenarios for stream and file handling are listed here.

  • When the FileToStream activity is used in a process, the file used in the FileToStream activity can be reused only when it is successfully processed by the following activities. If these activities throw an exception while using the input stream created from the FileToStream activity, the stream is closed to ensure that the file can be reused.
    • GetFragment
    • XMLSplitter
    • XMLValidation
    • TransformXML
  • When a large XML file name is directly used as input source with the following activities, the file can be reused when these activities complete successfully or if they throw an error.
    • GetFragment
    • XMLSplitter
    • XMLValidation
    • TransformXML
  • If the FileToStream activity is used in a process followed by any TIBCO ActiveMatrix BusinessWorks activity (non-Large XML activities) and an exception is thrown, the file used with the FileToStream activity is released when the CloseStream activity is used.
  • When FragmentCriteriaException is thrown, the GetFragment activity can still iterate through the fragment by skipping the excessSplitElement given out in the FragmentCriteriaException. To allow this functionality, the file name and input stream handles are not reused if you do not iterate back to the GetFragment activity on error handling. In this case, the file handle is released when the job ends.