《PC9xL1D_Mod_8_SeqGenLookups_v3》.ppt

Module 8: Sequence Generators, Lookups and Additional Workflow Tasks 8.22 This adds a great deal of power to Workflows – they can run external scripts in the Operating System. Description Command tasks are inserted in workflows and worklets to enable the Integration Service to run one or more OS commands of any nature. All commands or batch files referenced must be executable by the OS login that owns the Integration Service process. Business Purpose OS commands can be used for any operational or business unit related procedure, and can be run at any point in a workflow. Command tasks can be set to run one or more OS commands or scripts/batch files, before proceeding to the next task in the workflow. If more than one command is coded into a Command Task, the entire task can be set to fail if any one of the individual commands fails. Additionally and optionally, each individual command can be set not to run if a preceding command fails. Module 8: Sequence Generators, Lookups and Additional Workflow Tasks 8.23 The key here is the student note that gives some examples of how to use Command tasks. Examples of Command Tasks A Session task that produces an output file can be followed by a Command task that copies the file to another directory, or FTPs the file to another box location. The command syntax is the same as that which would accomplish this at the OS command prompt on the Integration Service machine. A Session task that relies on a flat file as source data can be preceded by a Command task that verifies the presence of the file, opens it and verifies control totals or record counts with some external source of information. A series of multiple concurrent or sequential Sessions can be followed by a single Command task coded to copy or move all session logs created by the workflow to a special daily backup directory. 8 Module 8: Sequence Generators, Lookups and Additional Workflow Tasks 8.24 Purpose: To introduce the lab. Steps: Describe the purpose and main