Initialize Target Sites

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 asset management server is already running.

  1. 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.

  2. Access the ATG Business Control Center and log in as a user with access rights to the Admin Console.

  3. In the Home page, expand the ATG Content Administration option in the Operations list, and click Admin Console.

  4. Click Configuration.

  5. Click Make Changes Live.

  6. Select Flag Agents Only or Do a Full Deployment as appropriate (see Site Initialization Options), and click Make Changes Live.

  7. 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.

If you need to restart an initialized target site application, you must also restart the asset management 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:

  1. Drop the existing (clustered) primary key.

  2. 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.

Adding agents to an initialized target

After you initialize a target, you can add a deployment agent to that site as follows:

  1. Configure the deployment agent as described earlier (see Configure Target Site Deployment Agents).

  2. Return to the target site’s Configuration page and click Make Changes Live.

  3. Perform the steps associated with one of the following conditions:

    If the new agent is responsible for...

    Perform these steps:

    File assets (ConfigFileSystem or WWWFileSystem)

    1. Choose Do a Full Deployment

    2. Click Make Changes Live

    File assets whose file directories are on a sharable network resource used by other agents in the Content Administration cluster

    1. Open the Component Browser page in Dynamo Administration and navigate to /atg/epub/DeploymentServer

    2. Scroll to the target site. In the Force Snapshot ID field, enter the Current Installed Agent Snapshot value.

    3. Click Init.

    Repository assets

    1. Open the Component Browser page in Dynamo Administration and navigate to /atg/epub/DeploymentServer

    2. Scroll to the target site. In the Force Snapshot ID field, enter the Current Installed Agent Snapshot value.

 
loading table of contents...