How to Create a Project for Staging Web Content
This topic describes how to create a project to stage Web content by using the Commerce Server Staging (CSS) Microsoft Management Console (MMC). You can create a project to stage Web content either manually or by using the New Project Wizard.
.gif "Important note") Important Note: |
|---|
Before you create a project for staging business data, review the information that is contained in How to Stage Web Content. |
You create Web content projects to replicate and update Web content to one or more endpoints.
The following table summarizes which Web content project properties are mandatory and which are optional. In addition, it indicates which properties are only applicable to specific server roles. For more information about staging options for Web content, see Web Content Staging Options.
Property |
Specification |
|---|---|
Project Name |
Mandatory. The project name must be the same on all servers in the staging topology. |
Project Type |
Mandatory. The project type must be the same on all servers in the staging topology. |
Project Directory |
Mandatory. Type the path of the new directory or click Browse and move to the directory. |
Metabase Deployment |
Leave unchecked for all Web content projects. |
Destination |
Required. This property is used to specify one of the following options:
At least one destination must be specified for Web content to be staged. |
Project filter |
Optional. Specifies which Web content files to exclude or include for staging. When it is defined, it only must be defined on the source staging server. |
IIS |
Optional. Specifies the virtual directory settings to modify the permissions that clients have on the virtual directory. When it is defined, the properties are applicable the source staging server and endpoint servers. |
Scripts |
Optional. Specifies the script path and file to be executed. Scripts are run based on the server role. Scripts must be defined on the server where they will be run.
Script optionServer role
Before any content is sent.Script is run on a source staging server or waypoint.
After all content is deployed.Script is run on a source staging server or waypoint.
Before any content is receivedScript is run on a waypoint or endpoint.
After all content is received.Script is run on a waypoint or endpoint.
|
Advanced |
Optional. Specifies how Web content is replicated.
Advanced optionServer role
Force deployment of all contentApplicable only to source staging server.
Check time stamp onlyApplicable only to source staging server.
Skip locked files on source or destinationApplicable to both source staging and endpoint servers.
Preserve content on destination when deleting from sourceApplicable to both source staging and endpoint servers.
Enable timed releaseApplicable only to an endpoint server.
|
Schedule |
Optional. Specifies the schedule to use to automate the replication and deployment of Web content.
Schedule optionServer role
Deploy automatically as content changesApplicable only to a source staging server.
Set schedule replicationApplicable only to a source staging server.
Set schedule applyApplicable only to an endpoint server. To be operable, the Enable timed release property on the Advanced tab must be enabled.
By default, the destination CSS server(s) write content to the destination folder as it comes in from the source server. You can also configure the destination server(s) to hold the content in the CSS temporary folder until they receive an Apply signal to write the content to the destination folder. You can do this by selecting the Enable timed release option of the project from the Advanced tab. You can manually issue an Apply command on the destination server(s) through the Commerce Server Staging console or command line interface. You can also schedule the Apply command to run automatically by selecting the Schedule Apply option in the New Schedule dialog box. If you want to create a replication schedule, you can use the default option Schedule Replication. |
Optional. Specifies the e-mail address where staging events are to be sent. Applies equally to all server roles. |
|
Security |
Optional. Specifies project-level authentication and users. Applies equally to all server roles. |
Note
In order to create projects, you must have permission to administer CSS or the project. You have permission if you are a member of the CSS Administrators group.
Follow these steps to create a Web content project by using the New Project Wizard or manually.
| Important Note: |
|---|
When you create the project with the New Project Wizard, the project is defined for each server in the staging topology that is defined in the project. When you create the project manually, you must create it manually on each server in the staging topology. |
To stage Web content by using the New Project Wizard
Click Start, point to Programs, point to Microsoft Commerce Server 2009 , and then click Commerce Server Staging.
In the Commerce Server Staging console, in the left pane, expand Commerce Server Staging, expand <server name>, right-click Projects, point to New, and then click Project with a Wizard.
On the Welcome to the Microsoft Commerce Server New Project Wizard page, click Next.
On the Specify a Project Name page, type a name for the staging project, and then click Next.
On the Select a Project Type page, click Deploy content from a local directory, and then click Next.
On the Specify the Project Source page, type the path of the source directory that contains the files that you want to stage or click Browse to move to the source directory, and then click Next.
On the Specify the Project Destination page, click Add.
In the Add/Edit Destination dialog box, do the following:
Use this
To do this
Endpoint server
Select this option to stage Web content to a remote server. Specify the name of the remote server, and a destination directory on the remote server. You can also enter the credentials for an authentication account on the remote server. If no account is specified, the default account will be used.
If you specify an account here, it must either belong to the CSS Operators or CSS Administrators group, or it must have been given project-level access on the destination server. For more information, see How to Add and Remove Users as Project-Level Administrators or Operators.
Route
Select this option to select a specific route for staging the Web content.
Directory
Select this option to stage the Web content to a local directory. Type the path of the destination directory or click Browse to move to the destination directory.
Click OK.
On the Specify the Project Destination page, click Next.
On the Specify the Project Virtual Directory page, click Next.
On the Create Project Schedule page, click Add.
In the New/Edit Schedule dialog box, click Once to stage the project a single time, specify the Start time, Month, Day, and Year for staging the project, and then click OK.
If you want to stage the project on a recurring basis, click Weekly on, select the day on which you want to stage the project, and then click OK.
CSS automatically sets the schedule to run as the default authentication account. If you want to change the account for running the scheduled task, use Scheduled Tasks manager to update the task.
On the Add or Remove the Project Schedule(s) page, click Next.
On the Project Summary page, review the project options that you specified to make sure that they are correct, and then click Finish.
To create a project manually to stage Web content
Click Start, point to Programs, point to Microsoft Commerce Server 2009 , and then click Commerce Server Staging.
In the Commerce Server Staging console, in the left pane, expand Commerce Server Staging, expand <server name>, right-click Projects, point to New, and then click Project.
In the New Project dialog box, type the name of your project, and then click OK.
On the Specify a Project Name page, type a name for the staging project, and then click Next.
In the Project Type dialog box, click Deploy content from a local directory, and then click Next.
Define the properties for the project that are based on the role it has in deploying content. When you are finished, click OK.
See Also
Other Resources
How to Create a Project for Staging Business Data
Changing the Properties of a Web Content Project