Bookshelf Home | Contents | Index | PDF |
Siebel Application Deployment Manager Guide > Siebel ADM Support for Additional Data Types > About Data Type Attributes for Adding New Siebel ADM Data TypesThis topic describes the data type attribute categories to consider when adding new Siebel Application Deployment Manager (ADM) data types. The following terms are used in Data Type Attributes for Adding New Siebel ADM Data Types:
Parent Data TypeName of the parent data type for hierarchical database types. Registry ParametersParameters used to provide additional information about a data type. The information is provided in a name-value pair in the registry file; for example, NOTE: The parameters are read by the code and used according to the data type's requirement. You cannot add a new parameter and expect the ADM framework to consider it, without code changes. Enterprise Profile ParametersName of parameters specified in the entprofile_enterprise_name.xml file for a particular data type. Backup MethodA backup method is used to back up data in the target environment, which is affected during the copy operation of the package. The backed up data can later be used in the restore operation to revert the changes. There are four possible values:
Deploy MethodThe method that performs the copy operation. There are four possible values:
NOTE: The way the target data is affected for database items depends on the deployment mode used during export. Deploy Validation MethodValidation performed before executing the copy operation. The following methods can be invoked:
Activate MethodThe method that makes the deployed data available to users in the target environment. There are two possible values:
NOTE: Not all data types need activation. Some data types are immediately available to the users after deployment. Activate Validation MethodValidation performed before executing the activate operation. The following methods can be invoked:
Steps Automated by Activate or Restore Activate MethodsSteps that are automatically executed with the activate or restore activate methods. Necessary steps that are not automated must be manually performed. Restore MethodThe method used to restore the target system to the same functional level as before the deployment operations were invoked. There are four possible values:
NOTE: The restore implementation is not necessarily an undo-type of mechanism, even though it restores the original data to the target system. For example, the version of versioned objects may increment in some cases. Additional actions may be required to fully restore the target system to its original state prior to deployment. Delete New Objects ParameterIf this ADM registry parameter is set to Yes during a restore operation, then all top-level objects newly created by the deployment operation are deleted from the target system. If this parameter is set to No, then the new objects are not deleted, but remain in the target system. If delete is not appropriate for a specific object type, it may be necessary to modify the objects to render it inactive. For example, you may need to mark an object as inactive to, in effect, achieve the functional state before deployment. If an object is created during deployment, and is activated after deployment, then a custom restore method must be performed to implement the additional steps needed for completely deactivating the object. If the newly created top-level objects should not or cannot be deleted during a restore operation, then the value of the parameter must be set to No, and a comment should be entered in the registry to clearly describe why. This parameter applies to database and repository only. Restore Activate MethodThe method that makes the restored data available to users in the target environment. There are two possible values:
NOTE: Not all data types need activation. Some data types are immediately available to the users after restore. Restore Activate Validation MethodThe validation method performed before executing the restore activate operation. The following methods can be invoked:
Max Units Per PackageThe maximum number of units allowed in an ADM package due to limitations with the product. The ADM Package Utility enforces the limit. Manual StepsManual steps required for deploying the data type. These steps include clicking buttons, restarting a service, clearing the cache, and so on. Additional Downtime ImpactOther impacts to system availability or downtime during deployment, in addition to those listed in Table 15. Deployment PrerequisitesPrerequisites for successful deployment of the data type. NotesSpecial considerations, limitations, and comments for the deployment of the data type. |
Siebel Application Deployment Manager Guide | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |