C H A P T E R 2 -

This chapter explains the properties you need to create and set to transition from the Sun Java System Content Delivery Server, version 2004Q1PU1 to the Sun Java System Content Delivery Server, version 2005Q4.

2.1 Setting the Configuration Properties

1. Configure the new version of the Content Delivery Server as you normally would, including setting the .cfg configuration file, and run:

2. Open and perform the following edits to the properties migration file, $CDS_HOME/cfg/migration/props_migration_2004Q1PU1_2005Q4.xml:

a. Set new-cds-home and template-home by replacing [[CDS New Home]] and [[CDS Template Home]], respectively, to the directory where the new version (2005Q4) of the Content Delivery Server is installed.

The installation of the new version contains the configuration and localization file templates of the old version of the Content Delivery Server. If your installation does not contain the templates, apply the latest patch that you can obtain from support. You must provide an absolute path.

b. Set old-cds-home by replacing [[CDS Old Home]] to the directory where the old version (2004Q1PU1) of the Content Delivery Server is installed.

c. Set all occurrences of new-name by replacing [[CDS New Deployment Name]] to the deployment name of the new version of the Content Delivery Server.

d. Set all occurrences of old-name by replacing [[CDS Old Deployment Name]] to the deployment name of the old version of the Content Delivery Server.

e. Set all occurrences of template-name by replacing [[CDS Old Distribution Name]] to cds_2004Q1PU1.

This is the distribution that contains the configuration and localization file templates for the old version of the Content Delivery Server.

3. Run the cdsi migrate props command on the $CDS_HOME/cfg/migration/props_migration_2004Q1PU1_2005Q4.xml file.

The sample properties configuration file in the following section provides an example of how to set these properties.

2.1.1 Editing the Workflow

After you set the configuration properties, you need to modify the SubmissionVerifiedWorkflow.xml file for your deployment of the Content Delivery Server. See the Sun Java System Content Delivery Server Installation Guide for information on how to edit the file to meet your deployment needs. If you choose to create your own SubmissionVerifiedWorkflow.xml file, see the Sun Java System Content Delivery Server Integration Guide.

2.2 Sample Configuration File

You can use the following sample properties configuration file to configure your Content Delivery Server properties.

CODE EXAMPLE 2-1 Sample Configuration XML File
<props new-cds-home="/home/cds_new_version" old-cds-home="/home/cds_old_version" template-home="/home/cds_new_version"> <path new-name="deployment/cds/conf" old-name="deployment/cds/conf" template-name="dist/cds_2004Q1PU1/conf/templates" action="merge"> <file new-name="ConfFile.properties" old-name="ConfFile.properties" action="merge"/> </path> <path new-name="deployment/cds/localization" old-name="deployment/cds/localization" template-name="dist/cds_2004Q1PU1/localization" action="merge"> <file new-name="NewL10nFile.properties" old-name="OldL10nFile.properties" action="merge"/> </path> </props>

CODE EXAMPLE 2-1 Sample Configuration XML File

<props

    new-cds-home="/home/cds_new_version"

    old-cds-home="/home/cds_old_version"

    template-home="/home/cds_new_version">

    <path

        new-name="deployment/cds/conf"

        old-name="deployment/cds/conf"

        template-name="dist/cds_2004Q1PU1/conf/templates"

        action="merge">

        <file

            new-name="ConfFile.properties"

            old-name="ConfFile.properties"

            action="merge"/>

    </path>

    <path

        new-name="deployment/cds/localization"

        old-name="deployment/cds/localization"

        template-name="dist/cds_2004Q1PU1/localization"

        action="merge">

        <file

            new-name="NewL10nFile.properties"

            old-name="OldL10nFile.properties"

            action="merge"/>

    </path>

</props>