Integrations (PTC products, 3rd party products and code) > 3rd party product integrations (CM, DOORS, Rose, Simulink and XML) > Configuration management tool integration > Commands > Models Neighborhood commands > Create replica from configuration management command (CM tool integration)
  
Create replica from configuration management command (CM tool integration)
This command gets a Model and its Package hierarchy from your CM tool. The Model and Packages are created in the Modeler environment as stubs that are under configuration control. The Model is created in the database you right-clicked in Model Explorer. You use the (Create Replica) From Configuration Management command the first time you work with a CM tool Model.
After creating a replica of a CM tool model, you have stub Model and Packages. You can populate these stubs with the items they contain through a Tools > Configuration Management > Get Latest operation.
This command appears on the context menu when you right-click a database in Model Explorer.
To create a replica of a CM tool Model you require:
in the CM tool, read access to the Model and its Packages. Packages can be either checked in or checked out.
In Modeler, write access to the database in which the replica is going to be created. If the Model exists in the database, the create replica operation will be aborted.
* 
This command is not available when integrated with IBM Rational ClearCase (users of ClearCase must use the From Directory command) or when the CM tool integration is disabled. You can enable and disable the CM tool integration through the Enable Configuration Management Integration check box for the General entry on the Tool Options dialog.
Creating multiple replicas of a large CM tool Model may be time consuming. As an alternative, you can export the Model, and then import the Model to the required repositories.
If problems occur while creating a replica, delete all PKF, MDF and IDF files from your Windows Temp folder, and then repeat the create replica operation.
After creating a replica, Modeler attempts to find the associated CM tool file for the Model and each Package. If the path of an associated CM tool file is different from the path recorded in the Model, Modeler stores the path locally on your computer. If Modeler cannot find an associated CM tool file and you want to return that Package to configuration control, you must do so manually. For more information see, Reconnecting Modeler packages to configuration control (CM tool integration)
To use this command you require a Modeler license and a CM Integration license.