35Replicating Configuration Data from a Source Environment to a Target Environment
Replicating Configuration Data from a Source Environment to a Target Environment
This chapter describes how to migrate all or selective 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. It contains the following topics:
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 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 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 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 WorkflowRuleSetwhere:
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 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 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 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 WorkflowRuleSetwhere:
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 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 LeadConversionMapping LeadConversionMappingXML migrationtool -u UserID -s TargetServer Upsert SalesProcess SalesProcessXML migrationtool -u UserID -s TargetServer Upsert SalesStage SalesStageXML
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.xmlActionBarCustomWebAppletXML 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.xmlActionBarLayoutXML 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.xmlAssignmentRuleGroupXML 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.xmlAssignmentRuleXML 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.xmlCascadingPicklistXML is the fully qualified path name of the cascading picklist XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\CascadingPicklist\Account.xmlConcatenatedFieldXML is the fully qualified path name of the concatenated field XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\ConcatenatedField\Account.xmlCustomHTMLHeadTagXML 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.xmlCustomizedRecordTypeXML 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.xmlCustomWebLinkXML 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.xmlCustomWebTabXML 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.xmlDetailPageCustomWebAppletXML 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.xmlDynamicLayoutXML is the fully qualified path name of the dynamic layout XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\DynamicLayout\Account.xmlEnableModificationTrackingXML 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.xmlFieldAuditSetUpXML 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.xmlFieldManagementXML is the fully qualified path name of the field management XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\FieldManagement\Account.xmlHomepageCustomWebAppletXML 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.xmlHomepageLayoutXML 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.xmlHomeTabCustomWebAppletXML 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.xmlIntegrationEventQueueXML 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 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.xmlPageLayoutFieldXML 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.xmlPageLayoutRelatedXML 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.xmlPageLayoutSectionXML 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.xmlPicklistXML 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.xmlPicklistValueGroupXML 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.xmlProcessXML is the fully qualified path name of the process administration XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\ProcessAdministration\Account.xmlRelatedInfoLayoutXML 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.xmlReportFolderXML 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.xmlRoleXML is the fully qualified path name of the role XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\Role\MyRole.xmlSalesAssessmentScriptXML 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.xmlSalesCategoryXML 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.xmlWorkflowRulesXML 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.xmlWorkflowActionSetXML 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.xmlWorkflowUsersXML 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.xmlNote: TheUpsertcommand 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.
Replicating Selective Configuration Data from a Source Environment to a Target Environment
This topic describes the commands that you run to replicate a subset of 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 selective 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 configuration data that you want to change or update on the target environment by running the following command:
migrationtool -u UserID -s TargetServer ReadAll Feature
where:
UserID is the user sign-in ID that has the appropriate privileges to run the Oracle Migration Tool On Demand client commands.
TargetServer is the URL for the Oracle CRM On Demand target server for the target environment.
Feature is the type of configuration data to be extracted from the target environment. It can be one of the following values:
AccessProfile. For Oracle CRM On Demand access profile configuration data.
ActionBarCustomWebApplet. For Oracle CRM On Demand Action bar Web applet configuration data.
ActionBarLayout. For Oracle CRM On Demand Action bar layout configuration data.
AssignmentRuleGroup. For Oracle CRM On Demand assignment rule groups.
AssignmentRules. For Oracle CRM On Demand assignment rules.
CascadingPicklist. For Oracle CRM On Demand cascading picklist configuration data.
ConcatenatedField. For Oracle CRM On Demand concatenated field configuration data.
CustomRecordType. For Oracle CRM On Demand record type configuration data.
CustomWebLink. For Oracle CRM On Demand customized Web link field configuration data.
CustomWebTab. For Oracle CRM On Demand Web tab configuration data.
DetailPageCustomWebApplet. For Oracle CRM On Demand detail page Web applet configuration data.
DynamicLayout. For Oracle CRM On Demand dynamic layout configuration data.
EnableModificationTracking. For Oracle CRM On Demand modification tracking settings.
FieldAuditSetup. For Oracle CRM On Demand field audit setup configuration data.
FieldManagement. For Oracle CRM On Demand field configuration data.
HomePageCustomWebApplet. For Oracle CRM On Demand homepage Web applet configuration data.
HomepageLayout. For Oracle CRM On Demand homepage layout configuration data.
HomeTabCustomWebApplet. For Oracle CRM On Demand Home tab Web applet configuration data.
IntegrationEventQueue. For Oracle CRM On Demand integration event queue configuration data.
-
LeadConversionMapping. For Oracle CRM On Demand lead conversion mapping configuration data.
ListAccessAndOrder. For Oracle CRM On Demand list access and order layouts.
PageLayoutField. For Oracle CRM On Demand page layout field configuration data.
PageLayoutRelatedInformation. For Oracle CRM On Demand page layout related information configuration data.
PageLayoutSection. For Oracle CRM On Demand page layout section configuration data.
Picklist. For Oracle CRM On Demand customized picklist configuration data.
PicklistValueGroup. For Oracle CRM On Demand picklist value group configuration data.
ProcessAdministration. For Oracle CRM On Demand process adminstration configuration data.
RelatedInformationLayout. For Oracle CRM On Demand related information configuration data.
ReportFolder. For Oracle CRM On Demand role associations for analytics folders.
Role. For Oracle CRM On Demand role configuration data.
SalesAssessmentTemplate. For Oracle CRM On Demand sales assessment template configuration data.
SalesCategory. For Oracle CRM On Demand field sales category configuration data.
-
SalesProcess. For Oracle CRM On Demand sales process configuration data.
-
SalesStage. For Oracle CRM On Demand sales stage configuration data.
SearchLayout. For Oracle CRM On Demand search layout configuration data.
WorkflowActionSet. For Oracle CRM On Demand workflow actions configuration data.
WorkflowRuleSet. For Oracle CRM On Demand workflow rules configuration data.
WorkflowUserSet. For Oracle CRM On Demand workflow users configuration data.
Note: You can use any third-party application of your choice to store a history of changes, for example, IBM® Rational® ClearCase®.
If you want to back up the custom HTML head tag additions from the target server, run the following command:
migrationtool -u UserID -s TargetServer ReadForValue
CustomHTMLHeadTagRetrieve the required configuration data from the source environment by running one of the following commands:
migrationtool -u UserID -s SourceServer ReadAll Featuremigrationtool -u UserID -s SourceServer Read Feature MetadataFilename
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.
Feature is the type of configuration data to be extracted from the target environment. It can be one of the following values:
AccessProfile. For Oracle CRM On Demand access profile configuration data.
ActionBarCustomWebApplet. For Oracle CRM On Demand Action bar Web applet configuration data.
ActionBarLayout. For Oracle CRM On Demand Action bar layout configuration data.
AssignmentRuleGroup. For Oracle CRM On Demand assignment rule groups.
AssignmentRules. For Oracle CRM On Demand assignment rules.
CascadingPicklist.For Oracle CRM On Demand cascading picklist configuration data.
ConcatenatedField. For Oracle CRM On Demand concatenated field configuration data.
CustomRecordType.For Oracle CRM On Demand record type configuration data.
CustomWebLink. For Oracle CRM On Demand customized Web link field configuration data.
CustomWebTab. For Oracle CRM On Demand Web tab configuration data.
DetailPageCustomWebApplet. For Oracle CRM On Demand detail page Web applet configuration data.
DynamicLayout. For Oracle CRM On Demand dynamic layout configuration data.
EnableModificationTracking. For Oracle CRM On Demand modification tracking settings.
FieldAuditSetup. For Oracle CRM On Demand field audit setup configuration data.
FieldManagement. For Oracle CRM On Demand field configuration data.
HomePageCustomWebApplet. For Oracle CRM On Demand homepage Web applet configuration data.
HomepageLayout. For Oracle CRM On Demand homepage layout configuration data.
HomeTabCustomWebApplet. For Oracle CRM On Demand Home tab Web applet configuration data.
IntegrationEventQueue. For Oracle CRM On Demand integration event queue configuration data.
-
LeadConversionMapping. For Oracle CRM On Demand lead conversion mapping configuration data.
ListAccessAndOrder. For Oracle CRM On Demand list access and order layouts.
PageLayoutField. For Oracle CRM On Demand page layout field configuration data.
PageLayoutRelatedInformation. For Oracle CRM On Demand page layout related information configuration data.
PageLayoutSection. For Oracle CRM On Demand page layout section configuration data.
Picklist. For Oracle CRM On Demand customized picklist configuration data.
PicklistValueGroup. For Oracle CRM On Demand picklist value group configuration data.
ProcessAdministration. For Oracle CRM On Demand process administration configuration data.
RelatedInformationLayout. For Oracle CRM On Demand related information configuration data.
ReportFolder. For Oracle CRM On Demand role associations for analytics folders.
Role. For Oracle CRM On Demand role configuration data.
SalesAssessmentTemplate. For Oracle CRM On Demand sales assessment template configuration data.
SalesCategory. For Oracle CRM On Demand field sales category configuration data.
-
SalesProcess. For Oracle CRM On Demand sales process configuration data.
-
SalesStage. For Oracle CRM On Demand sales stage configuration data.
SearchLayout. For Oracle CRM On Demand search layout configuration data.
WorkflowActionSet. For Oracle CRM On Demand workflow actions configuration data.
WorkflowRuleSet. For Oracle CRM On Demand workflow rules configuration data.
WorkflowUserSet. For Oracle CRM On Demand workflow users configuration data.
MetadataFilename is the name of the configuration data XML file to be retrieved, for example, for an access profile, use:
C:\Oracle Migration Tool On Demand\resources\template\AccessProfile.xml
Note: Running theReadAllcommand is a simpler way to obtain the configuration data that you require if you are planning to replicate a subset of configuration data from the source environment. For example, if you are replicating ten access profiles out of twenty, then you can run oneReadAllcommand. However, performing aReadcommand is a way of retrieving the exact configuration data that you require.If you want to extract the custom HTML head tag additions from the source server, run the following command:
migrationtool -u UserID -s SourceServer ReadForValue CustomHTMLHeadTag
Perform an Upsert operation (or an InsertOrUpdate operation, in the case of workflow rules, workflow actions, and workflow users) for the required XML file to the target environment by running the following commands, as applicable:
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 WorkflowUserSetXML migrationtool -u UserID -s TargetServer Upsert AssignmentRuleGroup AssignmentRuleGroupXML migrationtool -u UserID -s TargetServer Upsert AssignmentRule AssignmentRuleXML 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 LeadConversionMapping LeadConversionMappingXML migrationtool -u UserID -s TargetServer Upsert SalesProcess SalesProcessXML migrationtool -u UserID -s TargetServer Upsert SalesStage SalesStageXML
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.xmlActionBarCustomWebAppletXML is the fully qualified path name of the Action bar customized Web applet XML file, for example,
C:\My Files\MyActionBarCustomWebApplet.xmlActionBarLayoutXML is the fully qualified path name of the Action Bar layout XML file, for example,
C:\My Files\MyActionBarLayout.xmlAssignmentRuleGroupXML 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.xmlAssignmentRuleXML 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.xmlCascadingPicklistXML is the fully qualified path name of the cascading picklist XML file, for example,
C:\My Files\MyCascadingPicklist.xmlConcatenatedFieldXML is the fully qualified path name of the concatenated field XML file, for example,
C:\My Files\MyConcatenatedField.xmlCustomHTMLHeadTagXML is the fully qualified path name of the custom HTML head tag additions XML file, for example,
C:\My Files\CustomHTMLHeadTag.xmlCustomizedRecordTypeXML 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.xmlCustomWebLinkXML is the fully qualified path name of the custom Web link XML file, for example,
C:\My Files\MyCustomWebLink.xmlCustomWebTabXML 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 CustomWebTab.xmlDetailPageCustomWebAppletXML is the fully qualified path name of the detail page customized Web applet XML file, for example,
C:\My Files\MyDetailPageCustomWebApplet.xmlDynamicLayoutXML is the fully qualified path name of the dynamic layout XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\DynamicLayout\Account.xmlEnableModificationTrackingXML 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.xmlFieldAuditSetUpXML is the fully qualified path name of the field audit setup XML file, for example
C:\My Files\Account.xmlField ManagementXML is the fully qualified path name of the field management XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\FieldManagement\Account.xmlHomepageCustomWebAppletXML is the fully qualified path name of the homepage customized Web applet XML file, for example,
C:\My Files\MyHomePageCustomWebApplet.xmlHomepageLayoutXML is the fully qualified path name of the homepage layout XML file, for example,
C:\My Files\My HomepageLayout.xmlHomeTabCustomWebAppletXML is the fully qualified path name of the Home tab customized Web applet XML file, for example,
C:\My Files\MyHomeTabCustomWebApplet.xmlIntegrationEventQueueXML 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 list access and order layout XML file, for example
C:\Oracle Migration Tool On Demand\windows\repository\LeadConversionMapping\Account\Date of Birth.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.xmlPageLayoutFieldXML is the fully qualified path name of the page layout field information XML file for a specific record type such as Account, for example,
C:\My Files\PageLayoutFieldInformation\Account\AccountCustom.xmlPageLayoutRelatedXML is the fully qualified path name of the page layout related information XML file for a specific record type such as Account, for example,
C:\My Files\PageLayoutRelatedInformation\Account\AccountCustom.xmlPageLayoutSectionXML is the fully qualified path name of the page layout section XML file for a specific record type such as Account, for example,
C:\My Files\PageLayoutSection\Account\Account.xmlPicklistXML is the fully qualified path name of the picklist XML file, for example,
C:\Oracle Migration Tool On Demand\windows\repository\Picklist\Account.xmlPicklistValueGroupXML is the fully qualified path name of the picklist value group XML file, for example,
C:\My Files\MyPicklistValueGroup.xmlProcessXML is the fully qualified path name of the process administration XML file, for example,
C:\My Files\Account.xmlRelatedInfoLayoutXML is the fully qualified path name of the related information layout XML file, for example,
C:\My Files\MyRelatedInfoLayout.xmlReportFolderXML 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.xmlRoleXML is the fully qualified path name of the role XML file, for example,
C:\My Files\MyRole.xmlSalesAssessmentScriptXML is the fully qualified path name of the sales assessment template XML file, for example,
C:\My Files\MyAssessmentScript.xmlSalesCategoryXML is the fully qualified path name of the sales category XML file, for example
C:\My Files\1.xml-
SalesProcessXML is the fully qualified path name of the sales process XML file, for example
C:\My Files\High Potential.xml -
SalesStageXML is the fully qualified path name of the sales stage XML file, for example
C:\My Files\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.xmlWorkflowRulesXML is the fully qualified path name of the workflow rules XML file, for example,
C:\My Files\My WorkflowRules.xmlWorkflowActionSetXML is the fully qualified path name of the workflow action set XML file, for example,
C:\My Files\My WorkflowActionSet.xmlWorkflowUserSetXML is the fully qualified path name of the workflow user set XML file, for example,
C:\My Files\My WorkflowUserSet.xml
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, then ten Upsert operations (one for each XML file) are required.