|
Product Administration Guide > Releasing Products and Other Versioned Objects >
Migrating Products Among Environments
Some businesses develop new versions of products in the same environment that they use for product that are already in production. Other businesses use separate environments for development and for production. If you use separate environments for development and production, you can migrate product data from the development to the production environment in either one of two ways:
Migrating Products Using Import and Export in Workspace Projects View
Using import and export in Workspace Projects view, you can migrate the versioned data that you can add to the Workspace Projects list, and you have the option of migrating related objects. When you export objects, a dialog box appears with these options:
- Object(s) Only. Exports only the objects in the Workspace Projects list.
- Full Structure. Exports the objects in the Workspace Projects list and related objects, such as attribute definitions and product classes. If you use this option, the related objects are imported automatically when you import the objects in the Workspace Projects list.
In either case, all the objects are exported to a single XML file. When you import this XML file, they are imported as separate objects. The data that is exported depends on the value in the Testing Date field of the Workspace Project header. If no base date is entered, it depends on the value in the Effective Start Date field. NOTE: To extend the import/export XML schema, extend integration objects under the project ISS VOD Import Export.
To migrate product data using export and import in Workspace Projects view
- In the development environment, navigate to the Administration - Product screen, then the Workspace Projects view.
- In the Workspace Projects list, in the record for workspace containing the objects you want to migrate, enter the necessary information in the fields shown in the following table.
|
|
Effective Start Date |
If no Testing Date is entered, this value is the date that the application uses to determine what versions should be exported for dependent items when the user chooses to export the full structure of the items in the Workspace Project |
Base Date |
Enter the date used as the date for dependent items for full structure export. If both Effective Starting Date and Testing Date are filled, Testing Date is used. |
Use Project |
If Use Project is checked, the workspaces of the objects in the Contents list are not exported. If Use Project is not checked, the relevant versions of those objects are exported. |
- In the Workspace Projects menu, select Export Contents.
- In the Export Versioned Object dialog box, click Object(s) Only or Full Structure.
- Save the files that are exported.
- In the target environment, navigate to the Administration - Product screen, then the Workspace Projects view.
- In the Workspace Projects list, add a new record and complete the necessary fields.
The contents will be imported into this new Workspace Project.
- In the Workspace Projects menu, select Import Contents.
- In the VOD Import dialog box, click Browse and select the file to import, and then click Import.
The imported file appears in the Workspace Projects list.
- Repeat Step 9 until you have imported all the files that you exported.
Migrating Products Using Application Deployment Manager (ADM)
Using Application Deployment Manager, you can move the objects shown in Table 40.
Table 40. Objects Moved by ADM
|
|
JointWorkspace |
Versioned Product Data, Attributes Definitions, Product Classes, Context Signals, Context Variable Maps |
ProductCatalog |
Catalog, Catalog Category, Category Products |
PriceList |
Price List, Price List Items, Pricing Adjustments |
VolumeDiscount |
VolumeDiscount, Volume Discount Items |
DynamicMatrix |
Attribute Adjustments, Attribute Adjustments Dimensions, Attribute Adjustments Domains, Attribute Adjustments Rules, Attribute Adjustments Variable Maps, |
AdjGroup |
Adjustment Group, Adjustment Dimension, Entitlement-Based Adjustment, Training-Based Adjustment, Promotion-Based Adjustment, Product-Based Adjustment, Product Eligibility Adjustment, Product Compatibility Adjustment |
DataMapObject |
Data Map Object, Data Map Components, Data Map Component Fields |
MessageType |
Message Type, Type Response, Type Response Translation, Type Translation, Payload |
ProdData |
Internal Product - Recommended Products, Compound Products, Product Validation Rules |
ProdFeature |
Product Feature |
ProdLine |
Product Line |
CostList |
Cost list, Products |
AccntPromo |
Account Promotions, Account Promotion Products |
Fund |
Funds |
Promo |
Promotions |
BundleSeq |
Siebel Pricer Bundle Sequence, Siebel Pricer Bundle Sequence Items |
BundleDiscount |
Siebel Pricer Bundle Discount, Siebel Pricer Bundle Discount |
You can use any field from the business component and operators (such as AND, OR) to construct an expression for the Deployment Filter, as follows: [<field name>]=<field value>
[<field name 1>]=<field value 1> AND/OR [field name 2]=<field value 2>...
For instance, use the following syntax for Workspace Project: [<field_name>]= <my_joint_workspace_name> AND [<field_name>]='Y'
Use the following syntax for other objects: [<field_name>]= <my_object_name>
If you want to use multiple parameters, as shown in the example above, you must string the parameters together using the AND and OR operators. For example, if you want to use the fields Full and Name as parameters, use the syntax shown in the following example: [Description]='N' AND [Full] ='Y' AND [Name]='TestADM'
In this example, the field name [Full] means to request Full Structure. For information about how to use ADM, see Going Live with Siebel Business Applications.
|
