How to move selection of job definitions from an older version of Control-M/Enterprise Manager to a newer one

Version 1
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Control-M/Enterprise Manager


    COMPONENT:

    Control-M/Enterprise Manager


    APPLIES TO:

    Control-M/Enterprise Manager



    QUESTION:

    How can one move a selected set of job definitions, rather than the entire database (DB) at once, from an older major version of Control-M/Enterprise Manager to a newer one?


    ANSWER:

    The only supported method for converting job definitions from an older version to a newer one is to perform the "Elevate" step on a Control-M/Server entry in the Control-M Configuration Manager(CCM), moving the entire component from one version to a newer one, as part of the migration upgrade process, which is designed for upgrading an entire server at once.

    The best way to transfer a limited set of job definitions from a source Control-M environment of an older major version to a destination Control-M environment of a newer major version is to follow these basic steps: 

    For version 9.0.19.200 and below:

    1. Set up a Control-M staging environment of the same version as the destination environment.
    2. Use the upgrade migration toolkit from the staging environment to perform a full upgrade migration from the source Control-M environment to the staging environment. Make sure to include the "Elevate" step on the staging Control-M/Server, since this is the step that converts the job definitions from the source version to the target version.
    3. Export the desired job definitions from the staging environment, either by loading them into a workspace and exporting as XML or by using an EM utility such as "emdef exportdefjob".
    4. Copy the exported job definitions from the staging environment to the destination environment.
    5. Import the exported job definitions into the destination environment, either by opening a workspace and selecting the "Import" function or by using an EM utility such as "emdef defjob". This method of import should match the method you used to perform the export.

    For version 9.0.20, the migration toolkit only supports migrating data between Control-M environments on the same version.  These are steps for moving job definitions from an older version to 9.0.20:

    1.  Install a staging environment that is at the same version as the source environment.
    2.  Use the migration toolkit to migrate the data from the source environment to the staging environment.
    3.  Perform an in-place upgrade to version 9.0.20.
    4.  At this point, you can use now export job definitions from the 9.0.20 staging environment.  You can export the jobs from a workspace in the Planning domain or use utilities such as "emdef exportdefjob".
    5.  Copy the exported job definitions to the environment that you want to import the jobs into.
    6.  Import the exported job definitions into the destination environment, either by opening a workspace and selecting the "Import" function or by using an EM utility such as "emdef defjob". This method of import should match the method you used to perform the export.


    Article Number:

    000220226


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles