| Siebel CRM Application Deployment Manager Guide Siebel Innovation Pack 2017, Rev. B E24721-01 |
|
 Previous |
 Next |
View PDF |
| Siebel CRM Application Deployment Manager Guide Siebel Innovation Pack 2017, Rev. B E24721-01 |
|
Previous |
Next |
View PDF |
Siebel Application Deployment Manager (ADM) data types represent the customized entities that require migration to new environments. For example, an assignment rule, a List of Values, application responsibilities, or Web templates represent the type of configurations that you make in one environment that must be migrated to another environment.
Some data types are hierarchical and contain more than one object, such as where the parent object is dependent on one or more child objects. For example, the Workflow Policy data type also migrates associated child Workflow Actions.
The packaging and deployment of ADM data types are dependent on their category. Individual data types sometimes have other specific configurations, limitations, or dependencies on other ADM data types. For full details and a listing of all supported ADM data types, see Appendix A, "Siebel ADM Supported Data Types." For more information about packaging and deploying different ADM data types, see Chapter 4, "Migrating Customizations Using Siebel ADM."
This topic is part of "About Siebel ADM Data Types".
In the current release, the following general category of ADM data type is supported:
ADM Database Types. Siebel run-time customizations residing in the Siebel database, for example, a Product Line or Assignment Rule.
This topic is part of "About Siebel ADM Data Types".
Creating Application Deployment Manager (ADM) data type relationships is only necessary if certain data types must be deployed before other types. Creating this relationship makes sure that related data types are deployed as a single transaction to the target system. If any of the related data types are not applied correctly, then all related data types are not migrated to the target system.
ADM data type relationships are relationships between data types; that is, there are also relationships between different entities internally within data types. These relationships are defined within the Integration Object for a data type. For descriptions on creating or removing data type relationships, see "Creating ADM Data Type Relationships".
This topic is part of "About Siebel ADM Data Types".
An example of an ADM data type relationship is as follows: a List of Values (LOV) with a State Model configured on that LOV. Therefore, the LOV must be governed by a State Model.
To set up this relationship in ADM, add the LOV data type as a child record to the State Model data type.
When this relationship is set up, the records of the LOV (LOV Type record and LOV value records) are inserted into the database first followed by the State Model records. If there is an error in moving either the State Model or the LOV records, then both are not allowed to exist separately on the target system. If the State Model encounters a database error, then the previously inserted LOV records are removed (rolled back) so that the errors are corrected and the session can be retried.
