Bookshelf Home | Contents | Index | PDF |
Siebel Application Deployment Manager Guide > Configuring and Administering the Siebel ADM Framework > About Siebel ADM Configurations for New Data Types > Configuring Integration Objects for ADM DeploymentThis topic is part of About Siebel ADM Configurations for New Data Types. Many Application Deployment Manager (ADM) data types have hierarchical structures of different objects that consist of parent-child relationships. In some cases, you might want to control how these hierarchies are deployed by removing the child entities from ADM deployments. For example, the responsibility data type also migrates users as well as responsibilities, because responsibilities are associated with users and these users would need to be included with the responsibility. However, in this example, you might not want to migrate users between environments, because this migration deploys development users to a production environment. To deploy only parent records of hierarchical relationships, you must disable the child integration component of the respective data type integration object. Perform the following procedure to configure this behavior. Intermediate-level knowledge of the Siebel EAI architecture and integration is a prerequisite before performing these tasks. For more information on Siebel EAI, see Overview: Siebel Enterprise Application Integration. For more information on using the synchronization wizard and configuring integration objects, see Integration Platform Technologies: Siebel Enterprise Application Integration. To configure an integration object for ADM deployment
|
Siebel Application Deployment Manager Guide | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |