Content staging configuration

Configuration of the Content staging module consists of two parts: the source and target server configuration.

Microsoft WSE Configuration

To enable Content staging, you first need to open the bin folder under your web project and rename the Microsoft.Web.Services3.dll.rename file to Microsoft.Web.Services3.dll. This needs to be done on both the source and the target server.

Source (Staging) Server Configuration

Source configuration is required for the staging (testing) server. You need to enable content staging using the following parameters in Site Manager -> Settings -> Content staging section.

•	Log content changes - if enabled, synchronization tasks are automatically generated when content (documents) is modified

•	Log data changes - if enabled, synchronization tasks are automatically generated when custom tables data are modified

•	Log object changes - if enabled, synchronization tasks are automatically generated when an object is modified

•	Log staging changes - if enabled, synchronization tasks are created for changes made by synchronization from another server to this server; see Bi-directional staging for more details

•	Log export tasks - if enabled, synchronization tasks are logged when an object is deleted (incremental update support)

Then you need to specify the target server(s). Go to CMSDesk –> Tools –> Content staging -> Servers. This is where you can manage the list of target servers.

Every site can use different target servers for content staging. You can even synchronize the content between the source and target server between different sites in the same web site instance (in the same database).

To add a new server, click New server (), enter the server properties and save them:

•	Server display name - server display name displayed to the users in the administration interface

•	Server code name - server name used in web site code

•	Server URL - staging service URL that points to the content staging web service of the target server; the web service page is located at ~/CMSPages/syncserver.asmx, so the URL should look like this: http://www.targetserver.com/CMSPages/syncserver.asmx

•	Enabled - if checked, the target server is enabled, it means that the tasks are automatically generated for the server and the synchronization is enabled for this server; you can temporarily disable the server by unchecking the box in case of server maintenance or any other case

•	Server authentication - server authentication settings; you should set the same parameters that are configured for your target server (described below); the default user name is admin and the default password is pass

Please note

Tasks are logged only for created and enabled servers. If there is no server created or if no server is running, no tasks are logged.

Target (Production) Server Configuration

On the target server, the staging service is disabled by default. For it to work, you need to perform staging configuration in Site Manager -> Settings -> Content staging.

•	Enable staging service - if checked, the staging service is enabled for the given site;

•

Staging service authentication - staging service authentication type; you can choose from the following options, while it's recommended that you choose USERNAME authentication to configure the staging first, test the synchronization and then you can optionally configure the site for X509 certificates

•	USERNAME – username/password authentication (fast, recommended for the data without high security requirements)

•	X509 – X509 certificate authentication (more secure, slower, requires certificates)

•	Staging service username and password - username and password for the USERNAME authentication

•	Server key ID and Client key ID - certificate keys for the X509 authentication, the certificates need to be stored within Local computer – Personal certificate store

Page url: http://devnet.kentico.com/docs/devguide/index.html?content_staging_configuration.htm