You are here:

Step 2 — Processing Commands (Optional)

Note: This Step does not apply to Queue Process Events.

You can use DTS parameters to enter the name of a program (.vbs, .vbe, .js, .jse, .wsf, .wsh, .com, and .bat), VBScript , or batch file (Command) to run before or after the job executes.

To specify processing commands

Do one of the following to locate the pre and post programs:
- Locate the pre and post programs in or under the Collaboration folder. The Integration Process (IP) refers to the filename, not the path, but prefixes the file name with the subfolder name if necessary.
- Locate the pre and post programs somewhere other than the Collaboration folder. This allows you to share files across multiple Collaborations. You must specify the path to the file in the Integration Server Application Path setting in the Console. The IP refers only to the filename, not the path.
  If you are using pre and post scripts, locate the script files in or under the Collaboration folder. The IP refers to either the filename with no path, or the filename relative to the Collaboration (the subfolder name only). Do not specify wscript.exe as the command. Instead, use the script filename on the command line, instead of on the parameter line.
  Note: You must type the name of the program or script without the path. If you type an invalid filename or include a path, no error occurs until you run the process.
  
  The Collaboration path does not display when you return to the Console after browsing. This is expected behavior and no action is necessary.
In the Parameters fields, enter any parameters necessary to run the application defined in the pre job and post job Command fields.
Proceed to Step 3, Properties Process.