Configuring a Scriptor Component

The script run by a Scriptor component can be stored internally, as part of the .pcf file, or externally, in a separate file that is called by the component when it runs.

You can write a general-purpose script that can behave differently depending on the parameters that are passed to it. Save the script itself in a file, and then configure the Scriptor component to pass the parameters.

Note

The Microsoft Transaction Server (MTS) context is not available to a Scriptor component or to any components called by a Scriptor (that is, context.SetComplete() and context.SetAbort() are not available to scripts hosted by Scriptor).

To configure a Scriptor component
  1. In the Pipeline Editor, open the pipeline.
  2. Do one of the following, depending on which version of the Pipeline Editor you are using:
  3. For Scripting Engine, select the language in which the script is written.
  4. For Source, do one of the following:
  5. To pass parameters to the script, type the parameters in the Config box.

    Parameters must be in the form name=value.

  6. In the Win32-based Pipeline Editor, click OK. In the ASP-based Pipeline Editor, click Update.
To convert a Scriptor between external and internal in the Win32-based Pipeline Editor
  1. In the Win32-based Pipeline Editor, open the pipeline.
  2. Right-click the Scriptor component you want to configure, click Properties on the shortcut menu, and then click the Scriptor tab.
  3. For Source, do one of the following:
  4. Click OK.

Related Topics


© 1997-1998 Microsoft Corporation. All rights reserved.