Page History

...

In the XML hierarchy this looks like:

• Profile
  • Operation
    
    • Copy
      • CopySource
        • CopySourceFragmentRef (one of the following)CopySourceFragmentRef
          • FTPFragmentRef
          • OR FTPSFragmentRef
          • OR etc....
          • OR ReadableAlternativeFragmentRef (Has the ref Attribute specifying the source ReadableAlternativeFragment Fragment(s)) ReadableAlternativeFragment fragments)
      • CopyTarget
        
        • CopyTargetFragmentRef (one of the following)
          • OR FTPFragmentRef
          • OR FTPSFragmentRef
          • OR etc....
          • OR WriteableAlternativeFragmentRef

The ReadableAlternativeFragmentRef and WriteableAlternativeFragmentRef elements contain attributes that reference corresponding ReadableAlternativefragment and WriteableAlternativeFragment elements in the Fragments configuration branch.

The ReadableAlternativefragment ReadableAlternativeFragment and WriteableAlternativeFragment elements then contain two or more alternative fragment elements that will be tried in turn if the first one is not able to make a connection.

In the XML hierarchy this looks like:

• Fragments
  • ProtocolFragments
  • AlternativeFragments
    • ReadableAlternativefragment
      • AltFTPFragmentRef (name = ....)
      • AltFTPFragmentRef (name = ....)
      • etc ....
    • WriteableAlternativeFragment 
      • AltFTPFragmentRef (name = ....)
      • AltFTPFragmentRef (name = ....)
      • etc....

Note that the alternative fragment elements are themselves only references to named ProtocolFragment elements.

The list above shows AltFTPFragmentRef elements - it is equally possible to specify elements with other protocols. A list of the Alt...FragmentRef elements available can be found in the parameter reference pages for ReadableAlternativefragment and WriteableAlternativeFragment elements.