After you configure and start the IBM® Rational® Software Architect Design Manager
Import Engine,
you must create an import definition on the Design Management Server that
specifies all the model content to import to the server.
Before you begin
Important: Before you import a model, you must
create and define a configuration space. A configuration space is
a group of configurations (a unique set of versions). Each design
management project area is associated with a configuration space;
multiple project areas can be related to the same configuration space
and can share configurations.
About this task
You can define the model content to place on the
Design Management Server in
two ways:
- Import an entire workspace: This mode uses
an installed version of Eclipse to access the workspace. With this
option, you can perform an exact one-to-one mapping or import of the
local workspace; every model in the workspace is placed on the model
server. This option places all content on the model server quickly.
- Import individual projects: This mode uses
the file system and does not require an Eclipse installation unless
you want to use Ant scripts. With this option, you can customize and
define individual projects to place on the model server. Using this
option, you can pull projects from different Eclipse workspaces; you
can also pull specific projects from the same Eclipse workspace, rather
than all content, when you use the first option.
Important: After an import definition
is created, you cannot change the mode until the import definition
is deleted. To delete an import definition, on the Import Definition
page, click Delete Import Definition and Data.
Note: To
access the Import Definition page, click the
Import menu
at the top of the screen, and click
Import Definition.
Procedure
- To create an import definition by specifying an Eclipse
workspace path, go to https://fully_qualified_hostname:9443/dm/web,
and click Import > Import Definition;
then, select a project area that has already been defined.
- On the Import Definition page, click an import option,
and complete the substeps for the option:
- Import an entire workspace
- In the Import Engine Name field, enter the same import
engine ID that you created when you configured the import engine: DM_Import_Def.
- Click Test to ensure the import engine
started and that the connection is valid.
- (Optional) In the Ant Script Path field, enter the location
of the Ant script.
- In the Eclipse Workspace Path field, enter the path to
your local Eclipse workspace folder that contains the model content
to import to the Design Management Server.
The Eclipse workspace path should point to a local computer (not to
the Design Management Server)
that contains the Rational Software Architect models;
this computer must also have the import engine installed, configured,
and running. When you provide this file path, you are configuring
the import engine to go to a specific workspace and put all the model
contents into a project on the Design Management Server.
- (Optional) In the Path Maps section, specify
the path map variables that you use in your workspace. Remember, the Design Management Server has
no file system, so the value of a path map must be relative to the
workspace path.
- Import individual projects from one
or more Eclipse workspaces. This mode uses the file system and does
not require an Eclipse installation unless you want to use Ant scripts.
- In the Import Engine field, enter the same import engine
ID that you created when you configured the import engine: DM_Import_Def.
- Click Test to ensure the import engine
started and that the connection is valid.
- (Optional) In the Ant Script Path field, enter the location
of the Ant script.
- Under Projects, enter the paths to the individual projects
in Eclipse workspaces on the computer that contains the model content
to import. To add a project, in the Projects section, click Add.
- Enter the names of the projects to import.
- (Optional) In the Path Maps section, specify
the pathmap variables that you use in your workspace. The server has
no file system, so the value of a path map must be relative to the
workspace path.
- (Optional) In the Advanced section, specify
the number of minutes for the import engine to wait before the engine
stops trying to transfer model content.
- (Optional) In the Schedule section, click Automatically
request an import using this schedule and specify how
often the import engine checks for model updates. You can also schedule
a snapshot after the import process so that you have a view of the
project at a specific point in time.
- To retain all the import definition updates, click Save.