You can use custom Ant scripts to pull the latest versions of model data onto the file system of the computer from which the Design Management Server retrieves data. In the web UI, you can use the Import Definition page to specify where the Design Management Server retrieves the model data by using the Eclipse workspace path or the workspace path and project directories. These paths must point to the file system of the same computer on which the import engine is installed and configured.
| Design Management Server field | Description |
|---|---|
Ant Script Path Location: In the web UI, on the Import Definition page |
This path points to the location of the Ant script. The location must be on the same file system as the computer on which the import engine is installed. For example, an Ant script might perform a task such as using specific credentials to log into the source control management (SCM) server, locate the projects in the workspace, and retrieve the latest data. You can also write Ant scripts to perform other tasks; however, at this time, Ant is not required for anything other than pulling model data from the SCM system. Note: You can write an Ant script that does not require
knowledge of workspaces. When you add an Ant script path to the import
definition, the Ant script runs as the first step in the import process.
|
Eclipse Installation Directory Location: In the Import Engine Configuration window |
This field must point to an Eclipse installation that can interpret the Ant script in the import definition. If you did not provide an Ant script, leave the value of this field as the default value, which points to the installation location of the import engine. Although the import engine is not a true Eclipse installation, but is a rich client platform, it can manage the import process when an Ant script is not required. |