To use the Test Server deployment, you must create a sufficiently sized pool of 'test' web application instances to support the expected amount of concurrent in-context preview activity.
IMPORTANT: This pool must be large enough to prevent a bottleneck in the content production process, as contributors would be forced to wait for a test server to become available before being able to conduct their preview activities.
2. Obtaining a Test Server for Deployment
Once the test server pool has been created, you can complete the following process in either the user sandbox or review sandbox. The process is the same for both.
From the user sandbox, open the More Actions menu and click the Deploy icon.
Choose a test server to use (only one test server can be allocated to a sandbox at a time) and click OK. This allocates the test server to the current sandbox and deploy the contents of the sandbox. The Monitor Deployment window opens. This window shows the progress of each deployment currently executing in the server.
Note: An AJAX callback is used to poll the server for progress. The frequency of this polling request can be set in the web-client-config-wcm.xml configuration file.
Once the deployment completes the state is updated as shown below. When a URL has been configured, this displays under the Deployment Successful message to allow instant previewing of the deployed site. If an error occurs, the reason for the error is shown under the Deployment Failed message.
You can close the window at any time during the deployment. However, you cannot return to the window (this will be rectified in a future release). To monitor progress if the Monitor Deployment window is closed, open the snapshot list in the staging area and monitor the status column, an IN PROGRESS message will be shown if one or more deployment processes are executing.
If there are no unallocated test servers available the window will show the following message: