Before you begin to import Rational® XDE™ Java™ code models, you should complete the
steps in this topic to prepare for migration.
Prerequisite: Review the XDE Model Import
wizard online help. For details, see the Importing Rational XDE models online help topic.
In addition, you can experiment with the XDE Java code model import process by testing
the process with the models that you intend to migrate. After you experiment
with the import process, you can make educated decisions about how to manipulate XDE Java code
models to make the import process easier.
Before you import an XDE Java code
model:
- Install the Rational UML modeling product on the same computer
where you create and maintain code models in XDE for Java. This configuration ensures that the Java
Code Model Import wizard has access to all of the XDE registry settings
and other related information such as the factory-built JDK reference models
that are embedded in the XDE installation path. Also, reference models might reside
on a shared network location; make sure you have access to these models.
- Verify that all the XDE models that are required to complete
a model closure are present in the XDE workspace. A model closure represents
a set of models in which all cross-model references resolve; that is, there
are no missing models and no broken references. In XDE for Java, a closure might contain one or more Java code
models and zero or more non-code models (content models). Each Java code
model also references one or more factory-built JDK reference models and quite
possibly other “reference models” that you defined. In most cases, you migrate
all the projects in the workspace.
- Determine the encoding scheme for the project that you are importing.
In most cases, the project encoding is correct and you can select the Default option
in the XDE Java Project Import wizard; however, some
files in a model might use an encoding scheme that is different from the native
one so that parts of the model can interchange with parts of models from another
team. While XDE and
the Rational modeling
products enable you to specify different encoding for individual files in
a project, you cannot specify individual files in the XDE Java Project import wizard. You must import
the entire project using the same project encoding scheme. For more information
about file encoding, see the Text file encoding and Changing
the encoding used to show the source online help topics in XDE for Java.
- Ensure that all XDE content models and Java code models do not contain cross-model
references that resolve to Web models, EJB models, and J2EE Deployment models;
you cannot import these types of XDE models. The Rational UML modeling products support
Web and J2EE development differently, based on the use of Web-specific and
J2EE-specific modeling languages that make no use of UML.
- Synchronize the Java code models (the model and related
code) in XDE and
verify that the project builds correctly without any errors, warnings, or
informational messages. If the code does not build correctly or the model
does not validate cleanly in XDE, the migration might not succeed.
- Ensure that all XDE models are of XDE model version 7.1 or later.
- Import the closure of XDE models (.mdx files) using the XDE
Model Import wizard.
- Back up the imported XDE models (now .emx models) in a recoverable
location.