Replicating All Configuration Data from a Source Environment to a Target Environment
This topic describes the commands that you run to replicate all the configuration data from a source environment to a target environment of Oracle CRM On Demand using the command-line interface of the Oracle Migration Tool On Demand client.
To replicate all configuration data from a source environment to a target environment
Start the command-line interface of the Oracle Migration Tool On Demand client, as described in Starting the Oracle Migration Tool On Demand Client Command-Line Interface.
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 AssignmentRule migrationtool -u UserID -s TargetServer ReadAll AssignmentRuleGroup migrationtool -u UserID -s TargetServer ReadAll CascadingPicklist migrationtool -u UserID -s TargetServer ReadAll ClientSideExtension 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 EnableModificationTracking 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 IntegrationEventQueue migrationtool -u UserID -s TargetServer ReadAll LeadConversionMapping migrationtool -u UserID -s TargetServer ReadAll List migrationtool -u UserID -s TargetServer ReadAll ListAccessAndOrder 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 ProcessAdministration migrationtool -u UserID -s TargetServer ReadAll ProcessAdministrationTransitionState migrationtool -u UserID -s TargetServer ReadAll RelatedInformationLayout migrationtool -u UserID -s TargetServer ReadAll ReportFolder 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 SalesProcess migrationtool -u UserID -s TargetServer ReadAll SalesStage migrationtool -u UserID -s TargetServer ReadAll SearchLayout 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 record types 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.
In addition, back up all workflow user sets that exist on the target server:
migrationtool -u UserID -s TargetServer ReadForRuleSet WorkflowUserSet Analytics ScheduledEvent
For more details on extracting workflow user sets, see Extracting Workflow User Sets.
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 AssignmentRule migrationtool -u UserID -s SourceServer ReadAll AssignmentRuleGroup migrationtool -u UserID -s SourceServer ReadAll CascadingPicklist migrationtool -u UserID -s SourceServer ReadAll ClientSideExtension 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 EnableModificationTracking 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 IntegrationEventQueue migrationtool -u UserID -s SourceServer ReadAll LeadConversionMapping migrationtool -u UserID -s SourceServer ReadAll List migrationtool -u UserID -s SourceServer ReadAll ListAccessAndOrder 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 ProcessAdministration migrationtool -u UserID -s SourceServer ReadAll ProcessAdministrationTransitionState migrationtool -u UserID -s SourceServer ReadAll RelatedInformationLayout migrationtool -u UserID -s SourceServer ReadAll ReportFolder 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 SalesProcess migrationtool -u UserID -s SourceServer ReadAll SalesStage migrationtool -u UserID -s SourceServer ReadAll SearchLayout 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 record types 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.
In addition, extract all workflow user sets that exist on the source server:
migrationtool -u UserID -s SourceServer ReadForRuleSet WorkflowUserSet Analytics ScheduledEvent
For more details on extracting workflow user sets, see Extracting Workflow User Sets.
Perform an Upsert operation (or an InsertOrUpdate operation, in the case of workflow rules, workflow actions, and workflow users) 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 SearchLayout SearchLayoutXML migrationtool -u UserID -s TargetServer Upsert Role RoleXML migrationtool -u UserID -s TargetServer Upsert IntegrationEventQueue IntegrationEventQueueXML migrationtool -u UserID -s TargetServer InsertOrUpdate WorkflowRules WorkflowRulesXML migrationtool -u UserID -s TargetServer InsertOrUpdate WorkflowActionSet WorkflowActionSetXML migrationtool -u UserID -s TargetServer InsertOrUpdate WorkflowUserSet WorkflowUsersXML migrationtool -u UserID -s TargetServer Upsert AssignmentRuleGroup AssignmentRuleGroupXML migrationtool -u UserID -s TargetServer Upsert AssignmentRule AssignmentRuleXML migrationtool -u UserID -s TargetServer Upsert List ListXML migrationtool -u UserID -s TargetServer Upsert ListAccessAndOrder ListAccessAndOrderXML migrationtool -u UserID -s TargetServer Upsert ReportFolder ReportFolderXML migrationtool -u UserID -s TargetServer Upsert CustomHTMLHeadTag CustomHTMLHeadTagXML migrationtool -u UserID -s TargetServer Upsert FieldAuditSetUp FieldAuditSetUpXML migrationtool -u UserID -s TargetServer Upsert SalesCategory SalesCategoryXML migrationtool -u UserID -s TargetServer Upsert EnableModificationTracking EnableModificationTrackingXML migrationtool -u UserID -s TargetServer Upsert ProcessAdministration ProcessXML migrationtool -u UserID -s TargetServer Upsert ProcessAdministrationTransitionState TransitionStateXML migrationtool -u UserID -s TargetServer Upsert LeadConversionMapping LeadConversionMappingXML migrationtool -u UserID -s TargetServer Upsert SalesProcess SalesProcessXML migrationtool -u UserID -s TargetServer Upsert SalesStage SalesStageXML migrationtool -u UserID -s TargetServer Upsert ClientSideExtension ClientSideExtensionXML
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\windows\repository\AccessProfile\MyCustomProfile.xml
ActionBarCustomWebAppletXML is the fully qualified path name of the Action bar customized Web applet XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\ActionBarCustomWebApplet\MyActionBarCustomWebApplet.xml
ActionBarLayoutXML is the fully qualified path name of the Action Bar layout XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\ActionBarLayout\MyActionBarLayout.xml
AssignmentRuleGroupXML is the fully qualified path name of the assignment rule group XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\AssignmentRuleGroup\Account\My AssignmentRuleGroup.xml
AssignmentRuleXML is the fully qualified path name of the assignment rule XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\AssignmentRule\Account\My AssignmentRuleGroup\My AssignmentRule1.xml
CascadingPicklistXML is the fully qualified path name of the cascading picklist XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\CascadingPicklist\Account.xml
-
ClientSideExtensionXML is the fully qualified path name of the concatenated field XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\ClientSideExtension\logo.xml
ConcatenatedFieldXML is the fully qualified path name of the concatenated field XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\ConcatenatedField\Account.xml
CustomHTMLHeadTagXML is the fully qualified path name of the custom HTML head tag additions XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\CustomHTMLHeadTag\CustomHTMLHeadTag.xml
CustomizedRecordTypeXML is the fully qualified path name of the customized record type XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\CustomRecordType\My CustomRecordType.xml
CustomWebLinkXML is the fully qualified path name of the custom Web link XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\CustomWebLink\Account.xml
CustomWebTabXML is the fully qualified path name of the custom Web tab XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\CustomWebTab\My CustomWwebTab.xml
DetailPageCustomWebAppletXML is the fully qualified path name of the detail page customized Web applet XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\DetailPageCustomWebApplet\Account\MyDetailPageCustomWebApplet.xml
DynamicLayoutXML is the fully qualified path name of the dynamic layout XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\DynamicLayout\Account.xml
EnableModificationTrackingXML is the fully qualified path name of the modification tracking settings XML file, for example
C:\Oracle Migration Tool On Demand\windows\repository\EnableModificationTracking\Account.xml
FieldAuditSetUpXML is the fully qualified path name of the field audit setup XML file, for example
C:\Oracle Migration Tool On Demand\windows\repository\FieldAuditSetUp\Account.xml
FieldManagementXML is the fully qualified path name of the field management XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\FieldManagement\Account.xml
HomepageCustomWebAppletXML is the fully qualified path name of the homepage customized Web applet XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\HomePageCustomWebApplet\Account\MyHomePageCustomWebApplet.xml
HomepageLayoutXML is the fully qualified path name of the homepage layout XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\HomepageLayout\Account\My HomepageLayout.xml
HomeTabCustomWebAppletXML is the fully qualified path name of the Home tab customized Web applet XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\HomeTabCustomWebApplet\MyHomeTabCustomWebApplet.xml
IntegrationEventQueueXML is the fully qualified path name of the integration event queue XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\IntegrationEventQueue\MyIntegrationEventQueue.xml
-
LeadConversionMappingXML is the fully qualified path name of the lead conversion mapping XML file, for examle,
C:\Oracle Migration Tool On Demand\windows\repository\LeadConversionMapping\Date of Birth.xml
-
ListXML is the fully qualified path name of the list XML file, for example
C:\Oracle Migration Tool On Demand\windows\repository\ListAccessAndOrder\Account\AllList.xml
ListAccessAndOrderXML is the fully qualified path name of the list access and order layout XML file, for example
C:\Oracle Migration Tool On Demand\windows\repository\ListAccessAndOrder\Account\ExpertRole.xml
PageLayoutFieldXML is the fully qualified path name of a page layout field information XML file for a specific record type such as Account, for example,
C:\Oracle Migration Tool On Demand\windows\repository\PageLayoutField\Account\AccountCustom.xml
PageLayoutRelatedXML is the fully qualified path name of a page layout related information XML file for a specific record type such as Account, for example,
C:\Oracle Migration Tool On Demand\windows\repository\PageLayoutRelatedInformation\Account\AccountCustom.xml
PageLayoutSectionXML is the fully qualified path name of a page layout section XML file for a specific record type such as Account, for example,
C:\Oracle Migration Tool On Demand\windows\repository\PageLayoutSection\Account\AccountCustom.xml
PicklistXML is the fully qualified path name of the picklist XML file for a specific record type such as Account, for example,
C:\Oracle Migration Tool On Demand\windows\repository\Picklist\Account.xml
PicklistValueGroupXML is the fully qualified path name of the picklist value group XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\PickValueGroup\MyPicklistValueGroup.xml
ProcessXML is the fully qualified path name of the process administration XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\ProcessAdministration\Account.xml
RelatedInfoLayoutXML is the fully qualified path name of the related information layout XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\RelatedInformationLayout\Contact\ContactAccountChildList\MyRelatedInfoLayout.xml
ReportFolderXML is the fully qualified path name of the XML file containing the role associations for an analytics folder, for example,
C:\Oracle Migration Tool On Demand\windows\repository\ReportFolder\MyFolder.xml
RoleXML is the fully qualified path name of the role XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\Role\MyRole.xml
SalesAssessmentScriptXML is the fully qualified path name of the sales assessment template XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\SalesAssessmentTemplate\Account Survey\MyAssessmentScript.xml
SalesCategoryXML is the fully qualified path name of the sales category XML file, for example
C:\Oracle Migration Tool On Demand\windows\repository\SalesCategory\1.xml
-
SalesProcessXML is the fully qualified path name of the sales process XML file, for examle,
C:\Oracle Migration Tool On Demand\windows\repository\SalesProcess\High Potential.xml
-
SalesStageXML is the fully qualified path name of the sales stage XML file, for examle,
C:\Oracle Migration Tool On Demand\windows\repository\SalesStage\[High Potential]\Short List.xml
SearchLayoutXML is the fully qualified path name of the search layout XML file, for example
C:\Oracle Migration Tool On Demand\windows\repository\SearchLayout\Account\MyAccountSearchLayout.xml
-
TransitionStateXML is the fully qualified path name of the process administration XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\ProcessAdministrationTransitionsState\Activity\Assigned.xml
WorkflowRulesXML is the fully qualified path name of the workflow rules XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\WorkflowRuleSet\Activity\WriteRecordNew.xml
WorkflowActionSetXML is the fully qualified path name of the workflow action set XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\WorkflowActionSet\Task email.xml
WorkflowUsersXML is the fully qualified path name of the workflow user set XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\WorkflowUserSet\ScheduledEvent1.xml
Note: TheUpsert
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.