After you configure target sites, you must initialize the target sites for use with the DeploymentServer.
Note: If you use an MS SQL database, review the next section, Initializing Targets on MS SQL with Clustered Primary Keys, before starting the procedure below.
This procedure assumes the ATG Content Administration server is already running.
Start an application on each target server that includes the appropriate agents. For information on starting agents, see Running Deployment Agents earlier in this chapter.
Access the ATG Business Control Center and log in as a user with access rights to the Admin Console.
In the Home page, expand the ATG Content Administration option in the Operations list, and click Admin Console.
Click Configuration.
Click Make Changes Live.
Select Flag Agents Only or Do a Full Deployment as appropriate.
Caution: If any projects are currently checked in when you initialize the target, and you select the Flag Agents Only option, all those projects are deployed immediately on initialization, including any marked as Deploy Later. This behavior occurs because the Flag Agents Only option deploys all data from the main versioning branch. If you have any projects scheduled for later deployment, therefore, and deploying those projects immediately is undesirable, perform a full deployment instead. The behavior does not occur with the full deployment option.
Display the Overview page, and review the information that appears for the target sites you initialized.
You can also confirm target initialization by viewing the service information for the atg/epub/DeploymentServer component via the Component Browser in the ATG Dynamo Server Admin interface.
Note: Deployment targets and their agents are reinitialized with repository data every time you restart the ATG Content Administration server application.
If you need to restart an initialized target site application, you must also restart the Content Administration server applications that deploy to it.
Initializing Targets on MS SQL with Clustered Primary Keys
If your ATG Content Administration environment uses an MS SQL Server database that employs clustered primary keys for repository tables, locking errors might occur when you initialize your targets:
Warning /atg/deployment/DeploymentManager Transaction (Process ID 164) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
To avoid these errors, configure your database so it does not use clustered primary keys. (Note that MS SQL uses clustered primary keys by default.) As a temporary alternative, set the following property values in the /atg/deployment/DeploymentManager component:
phaseCompletePollingInterval=30000 maxThreads=5 transactionBatchSize=5
If the errors still occur, try the following settings:
phaseCompletePollingInterval=60000 maxThreads=1 transactionBatchSize=1
To configure an MS SQL table so it does not use a clustered primary key, complete the following steps:
Drop the existing (clustered) primary key.
Add the NONCLUSTERED keyword to the primary key creation statement. For example:
ALTER TABLE MY_TABLE ADD CONSTRAINT MY_PK PRIMARY KEY NONCLUSTERED (ID);
Refer to the MS SQL documentation for detailed information.
