1. Through Packages referencing Packages in different CM tool projects.
2. Through the sharing of Package files in the CM tool environment.
You can create a CM tool project solely for the purpose of storing reusable Packages, in which case you can choose not to check in a Model to the CM tool project. Not having a Model stored in a CM tool project means that the ModelerATFiles subfolder files typically associated with a Model are not stored in the CM tool project.
Sharing of Package files in the CM tool environment
In this scenario, you use the CM tool's file sharing facilities to share a Package in the CM tool projects that want to reuse it. If a reused Package is updated, it is automatically updated in all the CM tool projects in which it is shared. The updated information is picked up next time a user performs a get latest or check out operation on the Package in their Modeler environment.
To reuse a Package in this way, you must share a Package's files (PKF and IDF files) in the CM tool environment. You then add the shared Package to the CM tool Model through the Add Package From Another Model commands in Modeler.
The main advantage of this approach is that you can use the CM tool facilities to see which CM tool projects are making use of a reused Package.
If a Model or Package is shared in the CM tool, the following symbol is displayed to the left of the Model or Package icon in the Modeler panes: .
Example
In this example, we reuse the TCP_IP Package in the Ticketing System Model.
We start by sharing the TCP_IP Package file (PKF file) and its look up file (IDF file) with the Ticketing System project.
Initially the CM tool Model is not in our Modeler environment, so we create a replica of the Ticketing System CM tool Model. We then check out the Ticketing System Model. The Ticketing System Model needs to be checked out, because we are going to add the TCP_IP Package to it.
Notice that although the TCP_IP Package has been shared with the Ticketing System project, it is not included in the Modeler Model because it is not yet part of the Package hierarchy.
We now add the TCP_IP Package (from the Ticketing System project) to our Modeler Model. To add a Package to the Ticketing System Model, from Modeler, right-click the Ticketing System Model, point to Configuration Management, and then click Import New Packages. The dialogs that appear depend on the CM tool you are using. For Microsoft Visual SourceSafe, you select the Ticketing System project, and then select the TCP_IP file.
We now check in the Ticketing System Model and its Packages.
If a user now checks out the Ticketing System Model to Modeler, the Modeler Model will include the latest versions of the Ticket Allocation and TCP_IP Packages from the Ticketing System CM tool Model.
.
