Configuring virtual path maps

To define a path map in Rational XDE, start the Pathmap Editor from the Windows Start menu by clicking Start > Programs > Rational XDE [version information] > Rational XDE Tools > Rational Rose Pathmap Editor. Each teammember should establish a path map. When associating a Rational RequisitePro project to a model or package, you can set the path map in the dialog box if you have already created a path map for that project.

In the following example, the RequisitePro project is stored in one location, but the users have mapped different drive letters to that location. Likewise each user assigns a different drive letter to reference the location of the XDE model. The virtual path map names are the same for both users; however, the location of the XDE model that they reference may be different.

User A

$XDEModel=Z:\Shared Location\XDE Models

$RequisiteProProject=Q:\Shared Location\RequisitePro

User B

$XDEModel=J:\XDE Models

$RequisiteProProject=Y:\RequisitePro

Virtual path maps and ClearCase Unified Change Management (UCM)

Teams that use ClearCase Unified Change Management (UCM) can improve
their multi-user compatibility by establishing a path map for both RequisitePro
projects and XDE models. Consider following this guideline if your team uses
the Rational RequisitePro-XDE Integration, and also meet any of the
following criteria:

• The drive letter mapping for the location of the RequisitePro project is mapped
  differently for each member of the team, and members use UNC naming convention to locate
  the RequisitePro project.
• The location of the XDE model is different for each team member; such as,
  when using Rational ClearCase UCM.
• Team members must invoke the integration from both their Rational ClearCase
  UCM development view and integration view.

Note   If you are a Rational ClearCase UCM user, you typically do not need to invoke the Rational RequisitePro-XDE integration when working in the integration view. However, if you must invoke the integration from your integration view, then you will need to manually update your path map to accurately reflect the location of the model you want to work with in your integration view.