Pre and Post-Processing Script Options

For the latest version of Commerce Server 2007 Help, see the Microsoft Web site.

For any staging project, you can specify different script and batch files to run before or after a deployment finishes. By using these scripts, you can perform custom tasks, such as exporting data or registering deployed components. The scripts you specify must reside on the server where they will run. Scripts can run on any server in the staging topology.

When you configure a project to use scripts, you provide the path name and file name of the script. This makes sure that the scripts reside on the servers where they need to be in order to run. Commerce Server Staging (CSS) will then find the script and run it according to its project schedule or when you deploy the content manually.

Note

Script files and paths entered into the Scripts tab of a project apply to the server you are administering currently. When you change the Scripts properties for the source staging server, you cannot name a script that will run on the end point server. To specify scripts to run on end points, you must change the project defined for the end point, and specify the information through the Scripts tab.

The following four options are available when you specify scripts. You can use them in any combination. The server role determines what scripts are run on that server.

Script option	Server role
Before any content is sent.	Script is run on the source staging server and waypoint(s).
After all content is sent.	Script is run on the source staging server and waypoint(s).
Before any content is received.	Script is run on waypoints and endpoints.
After all content is received.	Script is run on waypoints and endpoints.

Scripts are run as follows:

1. On the source server and waypoints:

   1. CSS runs the script specified in Before any content is sent.

   2. CSS stages the content.

   3. CSS runs the script specified in After all content is sent.

2. On the waypoints and destination servers:

   1. CSS runs the script specified in Before any content is received.

   2. CSS receives the content.

   3. CSS runs the script specified in After all content is received.

Note

CSS does not monitor the success or failure of script file execution, only the success and failure of staging projects.

See Also

Other Resources

How to Grant Permissions for Running Scripts

How to Add a Script File to a Staging Project

Changing the Script Files for a Staging Project

What are the Staging Project Options?