Bookshelf Home | Contents | Index | PDF |
Siebel Application Deployment Manager Guide > Siebel ADM Supported Data Types > Siebel ADM Data Type DetailsThe Siebel Application Deployment Manager (ADM) deployment process can vary slightly or have limitations or configurations associated with it, depending on the data type selected for migration. Review the following subset of data types for further details to configure or take into account during ADM deployment and activation. You can create hierarchy for any objects you migrate using ADM. If your data type is close to a standard data type, you can create a new data type. To do this, navigate to the Application Deployment Manager screen, then the Data Type Details view. Select the existing data type, choose Copy Record, and then modify the new data type record. For example, the AssignRule data type has a child type Workload Rule. If the assignment rule does not have a workload rule, then this data type cannot be used to deploy assignment rules. You can create a new ADM data type by copying the AssignRule data type and giving it a different name. After creating the new data type, delete its child data type Workflow Rule. To do this, navigate to the Application Deployment Manager screen, then the Data Type Explorer view. In general, it is recommended not to modify the standard data type. The following ADM data types are some of those that have additional ADM details:
List of ValuesThe List of Values (LOV) data type has the following behavior when deployed using ADM: the hierarchy in the List of Values Explorer view is different from the hierarchy in the List of Values list view. The List of Values Explorer view defines relations between different LOV types. To define relations within the same LOV type, use the Parent LIC field in the List of Values list view instead. NOTE: Hierarchical LOV data for the same LOV type that is defined in the List of Values Explorer view cannot be migrated using ADM. An error is generated during data export in this case. Organizations, Divisions, and PositionsOrganizations, divisions, and positions are implemented as a hierarchy as follows: Organizations You cannot implement divisions without first implementing organizations. Similarly, you cannot implement positions without implementing organizations first and then divisions. Personalization - ActionsThe Personalization - Actions data type has the following behavior when deployed using ADM: this data type is imported together with, but before, Personalization - Events data type. Both data types require the same activation and restore activation, which are defined only for Personalization - Events. Personalization - Event DefsThe Personalization - Events Def data type has the following behavior when deployed using ADM: this data type is imported together with, but before, the Personalization - Events data type. Both data types require the same activation and restore activation, which are defined only for Personalization - Events. Personalization - RulesThe Personalization - Rules data type has the following behavior when deployed using ADM: this data type is imported together with, but before, the Personalization - Applets data type. Both data types require the same activation and restore activation, which are defined only for Personalization - Applets. Run-Time Business ServiceThe Run-Time Business Service data type has the following condition when packaging this data with ADM: the Run-Time Business Service data is only allowed in Synchronize deployment mode. SmartScriptThe SmartScript data type has the following limitations when deploying with ADM:
Validating the SmartScript Data TypeSmartScripts deployed using ADM must be valid. If you export unverified SmartScripts, the generated XML file is incorrect. For more information on SmartScripts, see Siebel SmartScript Administration Guide.
UI ThemePerform the step below to access the UI Theme data type when packaging it with ADM. To access the UI Theme data type when packaging it with ADM
WebmasterThe Webmaster data type has the following limitations when deploying with ADM:
Setting the EnableADMSupport Parameter for the Webmaster Data TypeThe Application Object Manager (AOM) parameter Set this parameter from either the Server Manager (srvrmgr) command line or the application GUI. For information on parameter administration, see Siebel System Administration Guide. To set the AOM parameter EnableADMSupport to True from the application GUI
Workflow PolicyThe Workflow Policy data type requires additional attention when activating it after an ADM deployment. Perform the following task to make sure additional configurations are satisfied. To make sure Workflow Policy data type is ready for activation
Workflow and TaskflowThe Workflow and Taskflow repository data type has the following limitations when deploying with ADM:
Workspace ProjectsThe Workspace Projects data type has the following variations to general ADM deployment behavior:
|
Siebel Application Deployment Manager Guide | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |