1. Application Deployment Manager Guide
  2. Recommendations for Migrating Data Using Siebel ADM

Recommendations for Migrating Data Using Siebel ADM

Review the following information as recommendations of best practice when migrating data customizations using ADM.

  • Do not set up a large number of data types. Keep the number of project items low to assist with error management. If the deployment scenario contains more than ten line items, then break up the project into separate projects. This action helps improve usability.

  • Maintain strong development guidelines, especially with naming conventions. Consistent development guidelines assist in the creation of deployment filters.

  • Make sure that seed data, included as part of an installation, is in place for both the source and target environments. Do not use ADM to migrate this type of data. For example, do not migrate standard, unchanged LOV data types, which are available as part of a regular Siebel installation.

  • ADM is best suited for a high-frequency and low-volume deployment scenario. It is highly recommended to set up a deployment filter on all items. Review Siebel Enterprise Integration Manager (Siebel EIM) as a more appropriate tool for transferring large data volumes. For information about Siebel EIM, see Siebel Enterprise Integration Manager Administration Guide.

  • Maintain a compatible database code page between the source and target environments. If in doubt, then contact Global Customer Support.

  • When creating additional data areas, validate the integration object structure first before using it with the ADM framework. Use a simple workflow process in the process simulator to validate the integration object. For information about workflow processes and the process simulator, see Siebel Business Process Framework: Workflow Guide.

  • When working with files for deployment, always use a network share name in the UNC format. On Windows, do not use drive letters. Remember that file name is specified for importing from the GUI but the directory name must be specified for exporting.

  • Note that the deployment occurs in an asynchronous mode and the Server Request Broker (SRBroker) and Server Request Processor (SRProc) component parameters affect how fast the requests are processed. By default, no adjustments are necessary.

  • Securing your Siebel CRM deployment using Transport Layer Security involves deploying certificates and configuring keystores and truststores on your server computers. You must also configure your Siebel deployment (using Siebel Management Console) to be able to use these security features. Configure each server computer as needed based on how you will use it along with other servers in your deployment. Such security considerations apply to ADM as well as to other Siebel CRM features.

    For example, suppose that you want to use ADM to migrate data from a development environment (source) into another environment such as for QA or production (target). In order for ADM to be able to send requests from the source to the target, the truststore on the source must include the certificate authority (such as a commercial authority) that signed the certificate on the target. If that certificate authority is trusted, the source also trusts any valid certificate signed by that authority. See also Siebel Security Guide and Siebel Installation Guide.