Previous Topic: ConceptNext Topic: New vs. Old Means to Transfer Content


How to Start Working with Content Transfer

Note: For simplicity the following recommendations refer to a deployment of two environments (such as development and production). However it can be adapted to any multi-environment deployment.

In some phase of CA Business Service Insight implementation, there is a need to put in place the deployment of several environments. Normally implementation starts with one environment that at a certain point becomes the production environment. In such a case, this is the point in time when the development environment must be built. The recommendation is to build the development based on the new production environments, so the two environments are synchronized. For more details on how to duplicate an environment, see Duplicating an Existing Environment. Once the development environment was built based on the production one, any new development is done in this environment and copied into the production environment using the content transfer interface. Following this standard process saves conflicts in the content transfer interface.

When there are already several environments in place (where the content is transferred either manually or by the old content transfer capabilities), CA recommends to first sync the environments by overwriting the development environment using the production environment content and start working with the content transfer interface from that point. If there is new content in the development environment that was not transferred yet to production, CA recommends transferring it first to the production using any selected mean and only then duplicate the production to development.