parallel

You can specify parallel to run all the activities "simultaneously" and independently of one another. However, truly simultaneous execution (for example, as in the case of time slicing) is not implemented.

The parallel activity is terminated when all the child activities have terminated. If one child activity outputs an error then child activities that are still running are cancelled.

The results of any given child activity are not visible in the other child activities.

The transfer of context objects to the parent context is not planned at present. Consequently, context objects which arise during the parallel activity are discarded.

A listDirectory as a direct child element of a parallel activity therefore does not return a usable event list (see section “listDirectory”).

parallel refers to the parallel processing of activities by openFT-Script. The maximum number of file transfers that actually run in parallel is determined by the openFT connection limit and process limit (see the manual "openFT (Unix and Windows systems) - Command Interface", fmodo command). To save resources, openFT-Script restricts the number of requests in the request queue in order to ensure that this connection limit is not exceeded. In the case of parallel, the requests can be processed in any order.

Synchronous activities such as deleteScript are also not necessarily all started at the same time within the framework of a parallel activity. Instead, the maximum number is limited (250 by default but can be modified using the ftmodsuo command), so that not too many threads have to be established.

The openFT connection limit and process limit operating parameters Control whether requests in the request queue are processed simultaneously or sequentially and consequently influence the actual level of parallel execution as well as the performance and resource consumption of your openFT-Script request.

Format

 <parallel>
   comment?
   context?
   Activity+
 </parallel>

Example

 <?xml version="1.0" encoding="UTF-8"?>
 <ftscript version="1">
   <parallel>
     <transferFile>
       <fromLocalFile name=
          "W:/openFT/ftscript/Test/data/large/text.txt" data="char"/>
       <toRemoteFile name="text.txt">
         <partner name="UnixP_1">
           <transferAdmission>
             <ftacAdmission ftacAdmission="FTACADM1"/>
           </transferAdmission>
         </partner>
         <directory name="frg_eis_13"/>
       </toRemoteFile>
     </transferFile>
     <transferFile>
       <fromLocalFile name=
          "W:/openFT/ftscript/Test/data/large/bin.mp3" data="bin"/>  
       <toRemoteFile name="bin.mp3">
         <partner name="WindowsP_1">
           <transferAdmission>
             <ftacAdmission ftacAdmission="FTACADM2"/>
           </transferAdmission>
         </partner>
         <directory name="frg_eis_13"/>
       </toRemoteFile>
     </transferFile>
   </parallel>
 </ftscript>

The files text.txt and bin.mp3 are delivered "simultaneously".

In fact, the file transfer requests are sent to openFT "simultaneously". If enough capacity is free then these requests are executed simultaneously.