Remerciez-le!

Remerciez @Admin pour avoir partagé cet document gratuitement, de la manière la plus simple, en partageant sur les réseaux sociaux.

Salesforce migration guide

Force com Migration Tool Guide Version Winter ? salesforcedocs Last updated November C ? Copyright ?? salesforce com inc All rights reserved Salesforce is a registered trademark of salesforce com inc as are other names and marks Other marks appearing herein may be trademarks of their respective owners CCONTENTS Chapter Force com Migration Tool Overview Chapter Installing the Force com Migration Tool Prerequisites for Using the Force com Migration Tool Installing the Force com Migration Tool Chapter Using the Force com Migration Tool Entering Salesforce Connection Information Constructing a Project Manifest Specifying Named Components Specifying all Components of a Type Specifying Standard Objects Getting Information About Metadata Types Describing Metadata Types Listing Components for a Metadata Type Creating Retrieve Targets Retrieving Unpackaged Components Retrieving Managed or Unmanaged Packages Retrieving Components in Bulk Retrieving Metadata from a Salesforce Organization Editing Metadata Deleting Files from an Organization Deploying Changes to a Salesforce Organization Deploying Components Deploying Code Running Tests in a Deployment Checking the Status of a Task Chapter Common Migration Issues Glossary Index C CCHAPTER Force com Migration Tool Overview The Force com Migration Tool is a Java Ant-based command-line utility for moving metadata between a local directory and a Salesforce organization The Force com Migration Tool is especially useful in the following scenarios ? Development projects where you need to populate a test environment with large amounts of setup changes ?? Making these changes using a Web interface could take a long time ? Multistage release processes ?? A typical development process requires iterative building testing and staging before releasing to a production environment Scripted retrieval and deployment of components can make this process much more e ?cient ? Repetitive deployment using the same parameters ?? You can retrieve all the metadata in your organization make changes and deploy a subset of components If you need to repeat this process it's as simple as calling the same deployment target again ? When migrating from stage to production is done by IT ?? Anyone that prefers deploying in a scripting environment will ?nd the Force com Migration Tool a familiar process Understanding Metadata API Metadata API contains a set of objects that manage setup and customization information metadata for your organizations and the SOAP calls that manipulate those objects With Metadata API you can ? Work with setup con ?guration as XML metadata ?les ? Migrate con ?guration changes between organizations ? Create your own tools for managing organization and application metadata Though you could write your own client applications for using Metadata API SOAP calls Salesforce provides the Force com Migration Tool to retrieve and deploy Apex and metadata Understanding Package and Directory Structure Metadata API functions in a package-centric manner Components may be in one or more packages or in no package at all Packages may be local created in your Salesforce organization or installed from Force com AppExchange Whenever the Force com Migration Tool retrieves a set of components that set will be limited to what ? s