|
Oracle Migration Tool On Demand Guide > Replicating Configuration Data from a Source Environment to a Target Environment >
Replicating Selective 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 a subset of 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: 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 selective configuration data from a source environment to a target environment
- Open a command line window on the computer where you have installed Oracle Migration Tool On Demand client, and navigate to the directory where you have installed it, (for example,
C:\Oracle Migration Tool On Demand).
- 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 <Type>
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.
- <Type> is the type of configuration data to be extracted from the target environment. It can be one of the following values:
- 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 CustomHTMLHeadTag
- Retrieve the required configuration data from the source environment by running one of the following commands:
migrationtool -u <UserID> -s <SourceServer> ReadAll <Type>
migrationtool -u <UserID> -s <SourceServer> Read <Type> <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.
- <Type> 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.
- 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.
- 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.
- 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.
- RelatedInformationLayout. For Oracle CRM On Demand related information configuration data.
- 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.
- WorkflowActionSet. For Oracle CRM On Demand workflow actions configuration data.
- WorkflowRuleSet. For Oracle CRM On Demand workflow rules 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 the ReadAll command 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 one ReadAll command. However, performing a Read command 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 and workflow actions) 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 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\My DynamicLayout.xml
- <FieldAuditSetUpXML> is the fully qualified path name of the field audit setup XML file, for example C:\My Files\Account.xml
- <Field ManagementXML> 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, then ten Upsert operations (one for each XML file) are required.
|
