At a high level, you set up project containers by completing the following steps. See the following sections for detailed information on each step.
Installing Dimensions CM to the Dimensions server.
Installing Dimensions CM to each system with an Eclipse client installed to it.
Optionally, if you have previously used Dimensions CM Eclipse SCC projects and want to maintain your existing hierarchy, convert those projects to project containers. You can choose to convert them to project containers instead of upgrading them to the single Eclipse project mapping.
Select a default way of working with Eclipse projects by setting your preferences correctly.
When necessary, add Eclipse projects to a Dimensions CM project. If the Dimensions CM project does not already contain Eclipse projects, you can choose to convert the project to a project container when you add the Eclipse projects.
When adding an Eclipse project to a project container, specify a folder offset path within Dimensions. Each Eclipse project must reside in its own unique folder within the Dimensions project. This is to ensure that multiple projects, with potentially identical names, do not reside in the same folder and therefore create conflicts. By default, the location of each Eclipse project in the Dimensions project is based on the originating Eclipse project name (if the project files are located within the Eclipse workspace). However, you may need to specify a path to ensure that the path is unique, or if the project files exist outside of the Eclipse workspace.