Getting a CM tool model the first time - creating a replica (CM tool integration)
You get a CM tool Model the first time by creating a replica of it. There are two commands for creating a replica:
• Through the From Configuration Management command - Use this command if you want to create a replica of the latest version of a model. This command is not available for IBM Rational ClearCase.
• Through the From Directory command - Use this command if you want to create a replica of a previous version of a model, or if you are working with IBM Rational ClearCase.
When you create a replica of a CM tool model, the replica contains only stubs of the Model and Packages. You can populate these stubs with the items they contain through a > > operation or a > > operation.
Creating multiple replicas of a large CM tool Model may be time consuming. As an alternative, you can export the Modeler Model, and then import the Modeler Model to the required databases.
 |
• When you create a replica, the Model and Packages in the Modeler environment are created as stubs.
• To create a replica of a CM tool Model, you require read access to the CM tool Model and its Packages, and write access to the database in which you are going to create the replica.
• If the Model exists in the database, the create replica operation will be aborted.
• After creating a replica, you can update the Modeler Model through get operations.
• 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 get a CM tool Model the first time (From Configuration Management command):
1. Start Model Explorer.
2. Right-click the database in which you want to create a replica of the CM tool Model, and select > .
3. Select the CM tool project in which the CM tool Model resides, and then click OK.
4. If a message about users being able to change the Packages in Modeler is displayed, click OK.
To get a CM tool Model the first time (From Directory command):
1. From the CM tool, get or check out the Model, its Packages and its files to a folder.
Note that stub Packages are created from only those files that can be found in the selected directory.
2. Start Model Explorer.
3. Right-click the database in which you want to create a replica of the CM tool Model, and select > .
4. Select the folder you used in Step 1, and then click OK.
5. If a message about users being able to change the Packages in Modeler is displayed, click OK.
To get a CM tool Model the first time (through Model export and import):
1. Through Model Explorer, export a Modeler Model that is linked to the CM Model you want to replicate. How?
2. Through Model Explorer, open the database in which you want to create the replica, and then import the Model you exported in Step 1. How?
3. In Modeler, open the Model you imported in Step 2.
4. Click the Packages pane, right-click the Model, select > > > , and then click Store CM Tool Paths Globally in Model.
5. Select the associated CM tool project, and then click OK.
To get a CM tool Model the first time from a directory using the command line interface:
1. In the database in which you want to create a replica, create a Modeler model. This model is overridden by the replica.
2. In a Command Prompt window run the following command from the Modeler Exe folder.
createreplica Enterprise
\\SQL\<server>@<instance>\<database>\<model>\<version>" -d -f "<folder containing exported files>"
Where:
◦ <server> specifies the name of the server on which the Database resides. The case of the name must be correct.
◦ <database> specifies the name of the Database that owns the Model that will be overridden by the replica. The case of the name must be correct.
◦ <model> specifies the name of the Model that will be overridden by the replica. The case of the name must be correct.
◦ <version> specifies the version of the Model will be overridden by the replica. If the Model has not been versioned, the version is 0.
◦ <folder containing exported files> specifies the folder that contains the exported files, from which the replica is created.
Example:
createreplica Enterprise "\\SQL\my.server\my.rep\my model\0" -d -f "c:\exported files"