Unpackaged-Components that live natively in your organization, such as standard objects, go in the unpackagedpackage. Whenever the Migration Tool retrieves a set of components, that set is limited to what’s in a single package or what’s in no package at all. Packages can be local (created in your Salesforce org) or installed from AppExchange. Components can be in one or more packages, or in no package. Metadata API functions in a package-centric manner. Or you can pull down changes to your Developer Edition org every day. Scheduling batch deployments-You can schedule a deployment for midnight to not disrupt users.When migrating from stage to production is done by IT-Anyone that prefers deploying in a scripting environment will find the Migration Tool a familiar process.If you need to repeat this process, it’s as simple as calling the same deployment target again. Repetitive deployment using the same parameters-You can retrieve all the metadata in your organization, make changes, and deploy a subset of components.Scripted retrieval and deployment of components can make this process much more efficient. Multistage release processes-A typical development process requires iterative building, testing, and staging before releasing to a production environment. Development projects for which you need to populate a test environment with a lot of setup changes-Making these changes using a web interface can take a long time.The Migration Tool is especially useful in the following scenarios. The Migration Tool is a Java/Ant-based command-line utility for moving metadata between a local directory and a Salesforce org.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |