Bookshelf Home | Contents | Index | PDF     

Oracle Migration Tool On Demand Guide > Replicating Configuration Data from a Source Environment to a Target Environment >

Replicating All Configuration Data from a Source Environment to a Target Environment

This topic describes the Oracle Migration Tool On Demand client commands that you run to replicate all the configuration data from a source environment to a target environment of Oracle CRM On Demand.

CAUTION:  Most components of Oracle CRM On Demand cannot revert to their original states by using the backup copies of the configuration data. For example, after a new access profile is inserted into the target environment, it cannot be removed by using the backup copy (that is, access profiles in Oracle CRM On Demand cannot be deleted). A backup copy of the configuration data provides a reference of the target environment before applying new configuration data.

NOTE:  In the following examples, the Oracle Migration Tool On Demand client requests your Oracle CRM On Demand password, which can be redirected (using the pipe command) to the client program from standard input; that is, from a file, from the command line, or from another program.

To replicate all configuration data from a source environment to a target environment

  1. Open a command line window on the computer where you have installed the Oracle Migration Tool On Demand client, and navigate to the directory where you have installed it, for example:

    C:\Oracle Migration Tool On Demand

  2. Back up the existing configuration data in the target environment by running the following commands:

    migrationtool -u <UserID> -s <TargetServer> ReadAll AccessProfile

    migrationtool -u <UserID> -s <TargetServer> ReadAll ActionBarCustomWebApplet

    migrationtool -u <UserID> -s <TargetServer> ReadAll ActionBarLayout

    migrationtool -u <UserID> -s <TargetServer> ReadAll CascadingPicklist

    migrationtool -u <UserID> -s <TargetServer> ReadAll ConcatenatedField

    migrationtool -u <UserID> -s <TargetServer> ReadForValue CustomHTMLHeadTag

    migrationtool -u <UserID> -s <TargetServer> ReadAll CustomRecordType

    migrationtool -u <UserID> -s <TargetServer> ReadAll CustomWebLink

    migrationtool -u <UserID> -s <TargetServer> ReadAll CustomWebTab

    migrationtool -u <UserID> -s <TargetServer> ReadAll DetailPageCustomWebApplet

    migrationtool -u <UserID> -s <TargetServer> ReadAll DynamicLayout

    migrationtool -u <UserID> -s <TargetServer> ReadAll FieldAuditSetUp

    migrationtool -u <UserID> -s <TargetServer> ReadAll FieldManagement

    migrationtool -u <UserID> -s <TargetServer> ReadAll HomePageCustomWebApplet

    migrationtool -u <UserID> -s <TargetServer> ReadAll HomepageLayout

    migrationtool -u <UserID> -s <TargetServer> ReadAll HomeTabCustomWebApplet

    migrationtool -u <UserID> -s <TargetServer> ReadAll PageLayoutField

    migrationtool -u <UserID> -s <TargetServer> ReadAll PageLayoutRelatedInformation

    migrationtool -u <UserID> -s <TargetServer> ReadAll PageLayoutSection

    migrationtool -u <UserID> -s <TargetServer> ReadAll Picklist

    migrationtool -u <UserID> -s <TargetServer> ReadAll PicklistValueGroup

    migrationtool -u <UserID> -s <TargetServer> ReadAll RelatedInformationLayout

    migrationtool -u <UserID> -s <TargetServer> ReadAll Role

    migrationtool -u <UserID> -s <TargetServer> ReadAll SalesAssessmentTemplate

    migrationtool -u <UserID> -s <TargetServer> ReadAll SalesCategory

    migrationtool -u <UserID> -s <TargetServer> ReadAll WorkflowRuleSet

    where:

    • <UserID> is the customer administration user's sign-in ID for the Oracle CRM On Demand target environment where the extraction occurs.
    • <TargetServer> is the URL for the Oracle CRM On Demand target server for the target environment.

      In addition, back up all workflow action sets for each of the object names and trigger events that exist on the target server:

    migrationtool -u <UserID> -s <TargetServer> ReadForRuleSet WorkflowActionSet
    <RecordType> <TriggerEvent> [<ParentRecordType>]

    For more details on extracting workflow action sets, see Extracting a Workflow Action or a Workflow Action Set.

  3. Retrieve all configuration data from the source environment by running the following commands:

    migrationtool -u <UserID> -s <SourceServer> ReadAll AccessProfile

    migrationtool -u <UserID> -s <SourceServer> ReadAll ActionBarCustomWebApplet

    migrationtool -u <UserID> -s <SourceServer> ReadAll ActionBarLayout

    migrationtool -u <UserID> -s <SourceServer> ReadAll CascadingPicklist

    migrationtool -u <UserID> -s <SourceServer> ReadAll ConcatenatedField

    migrationtool -u <UserID> -s <SourceServer> ReadForValue CustomHTMLHeadTag

    migrationtool -u <UserID> -s <SourceServer> ReadAll CustomRecordType

    migrationtool -u <UserID> -s <SourceServer> ReadAll CustomWebLink

    migrationtool -u <UserID> -s <SourceServer> ReadAll CustomWebTab

    migrationtool -u <UserID> -s <SourceServer> ReadAll DetailPageCustomWebApplet

    migrationtool -u <UserID> -s <SourceServer> ReadAll DynamicLayout

    migrationtool -u <UserID> -s <SourceServer> ReadAll FieldAuditSetUp

    migrationtool -u <UserID> -s <SourceServer> ReadAll FieldManagement

    migrationtool -u <UserID> -s <SourceServer> ReadAll HomePageCustomWebApplet

    migrationtool -u <UserID> -s <SourceServer> ReadAll HomepageLayout

    migrationtool -u <UserID> -s <SourceServer> ReadAll HomeTabCustomWebApplet

    migrationtool -u <UserID> -s <SourceServer> ReadAll PageLayoutField

    migrationtool -u <UserID> -s <SourceServer> ReadAll PageLayoutRelatedInformation

    migrationtool -u <UserID> -s <SourceServer> ReadAll PageLayoutSection

    migrationtool -u <UserID> -s <SourceServer> ReadAll Picklist

    migrationtool -u <UserID> -s <SourceServer> ReadAll PicklistValueGroup

    migrationtool -u <UserID> -s <SourceServer> ReadAll RelatedInformationLayout

    migrationtool -u <UserID> -s <SourceServer> ReadAll Role

    migrationtool -u <UserID> -s <SourceServer> ReadAll SalesAssessmentTemplate

    migrationtool -u <UserID> -s <SourceServer> ReadAll SalesCategory

    migrationtool -u <UserID> -s <SourceServer> ReadAll WorkflowRuleSet

    where:

    • <UserID> is the customer administration user's sign-in ID for the Oracle CRM On Demand source environment where the extraction occurs.
    • <SourceServer> is the URL for the Oracle CRM On Demand source server for the source environment.

      In addition, extract all workflow action sets for each of the object names and trigger events that exist on the source server:

    migrationtool -u <UserID> -s <SourceServer> ReadForRuleSet WorkflowActionSet
    <RecordType> <TriggerEvent> [<ParentRecordType>]

    For more details on extracting workflow action sets, see Extracting a Workflow Action or a Workflow Action Set.

  4. Perform an Upsert operation (or an InsertOrUpdate operation, in the case of workflow rules and workflow actions) for each XML file to the target environment by running the following commands:

    migrationtool -u <UserID> -s <TargetServer> Upsert CustomRecordType <CustomizedRecordTypeXML>

    migrationtool -u <UserID> -s <TargetServer> Upsert CustomWebTab <CustomWebTabXML>

    migrationtool -u <UserID> -s <TargetServer> Upsert FieldManagement <FieldManagementXML>

    migrationtool -u <UserID> -s <TargetServer> Upsert Picklist <PicklistXML>

    migrationtool -u <UserID> -s <TargetServer> Upsert CascadingPicklist <CascadingPicklistXML>

    migrationtool -u <UserID> -s <TargetServer> Upsert PicklistValueGroup <PicklistValueGroupXML>

    migrationtool -u <UserID> -s <TargetServer> Upsert CustomWebLink <CustomWebLinkXML>

    migrationtool -u <UserID> -s <TargetServer> Upsert ConcatenatedField <ConcatenatedFieldXML>

    migrationtool -u <UserID> -s <TargetServer> Upsert ActionBarCustomWebApplet <ActionBarCustomWebAppletXML>

    migrationtool -u <UserID> -s <TargetServer> Upsert DetailPageCustomWebApplet <DetailPageCustomWebAppletXML>

    migrationtool -u <UserID> -s <TargetServer> Upsert HomepageCustomWebApplet <HomepageCustomWebAppletXML>

    migrationtool -u <UserID> -s <TargetServer> Upsert HomeTabCustomWebApplet <HomeTabCustomWebAppletXML>

    migrationtool -u <UserID> -s <TargetServer> Upsert SalesAssessmentTemplate <SalesAssessmentScriptXML>

    migrationtool -u <UserID> -s <TargetServer> Upsert HomepageLayout <HomepageLayoutXML>

    migrationtool -u <UserID> -s <TargetServer> Upsert ActionBarLayout <ActionBarLayoutXML>

    migrationtool -u <UserID> -s <TargetServer> Upsert RelatedInformationLayout <RelatedInfoLayoutXML>

    migrationtool -u <UserID> -s <TargetServer> Upsert AccessProfile <AccessProfileXML>

    migrationtool -u <UserID> -s <TargetServer> Upsert PageLayoutField <PageLayoutFieldXML>

    migrationtool -u <UserID> -s <TargetServer> Upsert PageLayoutRelatedInformation <PageLayoutRelatedXML>

    migrationtool -u <UserID> -s <TargetServer> Upsert PageLayoutSection <PageLayoutSectionXML>

    migrationtool -u <UserID> -s <TargetServer> Upsert DynamicLayout <DynamicLayoutXML>

    migrationtool -u <UserID> -s <TargetServer> Upsert Role <RoleXML>

    migrationtool -u <UserID> -s <TargetServer> InsertOrUpdate WorkflowRules <WorkflowRulesXML>

    migrationtool -u <UserID> -s <TargetServer> InsertOrUpdate WorkflowActionSet <WorkflowActionSetXML>

    migrationtool -u <UserID> -s <TargetServer> Upsert CustomHTMLHeadTag <CustomHTMLHeadTagXML>

    migrationtool -u <UserID> -s <TargetServer> Upsert FieldAuditSetUp <FieldAuditSetUpXML>

    migrationtool -u <UserID> -s <TargetServer> Upsert SalesCategory <SalesCategoryXML>

    where:

    • <UserID> is the customer administration user's sign-in ID for the Oracle CRM On Demand environment where the Upsert operation occurs.
    • <TargetServer> is the URL for the Oracle CRM On Demand target server for the target environment.
    • <AccessProfileXML> is the fully qualified path name of the access profile XML file, for example, C:\Oracle Migration Tool on Demand\repository\AccessProfile\MyCustomProfile.xml
    • <ActionBarCustomWebAppletXML> is the fully qualified path name of the Action bar customized Web applet XML file, for example, C:\My Files\MyActionBarCustomWebApplet.xml
    • <ActionBarLayoutXML> is the fully qualified path name of the Action Bar layout XML file, for example, C:\My Files\MyActionBarLayout.xml
    • <CascadingPicklistXML> is the fully qualified path name of the cascading picklist XML file, for example, C:\My Files\MyCascadingPicklist.xml
    • <ConcatenatedFieldXML> is the fully qualified path name of the concatenated field XML file, for example, C:\My Files\MyConcatenatedField.xml
    • <CustomHTMLHeadTagXML> is the fully qualified path name of the custom HTML head tag additions XML file, for example, C:\My Files\CustomHTMLHeadTag.xml
    • <CustomizedRecordTypeXML> is the fully qualified path name of the customized record type XML file, for example, C:\Oracle Migration Tool on Demand\repository\CustomRecordType\My CustomRecordType.xml
    • <CustomWebLinkXML> is the fully qualified path name of the custom Web link XML file, for example, C:\My Files\MyCustomWebLink.xml
    • <CustomWebTabXML> is the fully qualified path name of the custom Web tab XML file, for example, C:\Oracle Migration Tool on Demand\repository\CustomWebTab\My CustomWwebTab.xml
    • <DetailPageCustomWebAppletXML> is the fully qualified path name of the Detail page customized Web applet XML file, for example, C:\My Files\MyDetailPageCustomWebApplet.xml
    • <DynamicLayoutXML> is the fully qualified path name of the dynamic layout XML file, for example, C:\Oracle Migration Tool on Demand\repository\DynamicLayout\MyDynamicLayout.xml
    • <FieldAuditSetUpXML> is the fully qualified path name of the field audit setup XML file, for example C:\My Files\Account.xml
    • <FieldManagementXML> is the fully qualified path name of the field management XML file, for example, C:\Oracle Migration Tool on Demand\repository\FieldManagement\MyFieldManagement.xml
    • <HomepageCustomWebAppletXML> is the fully qualified path name of the Homepage customized Web applet XML file, for example, C:\My Files\MyHomePageCustomWebApplet.xml
    • <HomepageLayoutXML> is the fully qualified path name of the homepage layout XML file, for example, C:\My Files\My HomepageLayout.xml
    • <HomeTabCustomWebAppletXML> is the fully qualified path name of the Home tab customized Web applet XML file, for example, C:\My Files\MyHomeTabCustomWebApplet.xml
    • <PageLayoutFieldXML> is the fully qualified path name of the page layout field information XML file for a specific object such as Account, for example, C:\My Files\PageLayoutFieldInformation\Account.xml
    • <PageLayoutRelatedXML> is the fully qualified path name of the page layout related information XML file for a specific object such as Account, for example, C:\My Files\PageLayoutRelatedInformation\Account.xml
    • <PageLayoutSectionXML> is the fully qualified path name of the page layout section XML file for a specific object such as Account, for example, C:\My Files\PageLayoutSection\Account.xml
    • <PicklistXML> is the fully qualified path name of the picklist XML file, for example, C:\Oracle Migration Tool on Demand\repository\Picklist\MyPicklist.xml
    • <PicklistValueGroupXML> is the fully qualified path name of the picklist value group XML file, for example, C:\My Files\MyPicklistValueGroup.xml
    • <RelatedInfoLayoutXML> is the fully qualified path name of the related information layout XML file, for example, C:\My Files\MyRelatedInfoLayout.xml
    • <RoleXML> is the fully qualified path name of the role XML file, for example, C:\My Files\MyRole.xml
    • <SalesAssessmentScriptXML> is the fully qualified path name of the sales assessment template XML file, for example, C:\My Files\MyAssessmentScript.xml
    • <SalesCategoryXML> is the fully qualified path name of the sales category XML file, for example C:\My Files\1.xml
    • <WorkflowRulesXML> is the fully qualified path name of the workflow rules XML file, for example, C:\My Files\My WorkflowRules.xml
    • <WorkflowActionSetXML> is the fully qualified path name of the workflow action set XML file, for example, C:\My Files\My WorkflowActionSet.xml

      NOTE:  The Upsert command must be run for each XML file that is retrieved from the source environment. For example, if ten access profile XML files are retrieved from the source environment, then ten Upsert operations (one for each XML file) are required.

    
Oracle Migration Tool On Demand Guide, Release 32 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. Legal Notices.