Splitting large XDE models before import

You can split large XDE models into multiple models to reduce memory consumption during the XDE model import process. This topic provides an example of how to split up a large XDE model before you import it.

Before you split a large XDE model into smaller models, try to increase the Java™ Virtual Machine (JVM) heap size to solve any memory consumption issues.

When you split your model, make sure to divide the model in a logical manner; consider taking your high-level organizational packages and breaking them out as separate models. Also, you may want to take model elements that have underlying subunits such as packages and subsystems and create separate XDE models from them. When you divide a large XDE model into smaller models, make sure the resulting models do not contain circular dependencies and try to keep the inter-model dependencies to a minimum.

As shown in the following diagram, assume you have a large XDE model named A that you have split into models A and A1 through A8. Notice that there are no circular dependencies among the resulting set of models.

An XDE model diagram that displays an XDE model named A and shows how you can split it into multiple models.

After you split your XDE model into multiple models, you should try to import the main model (model A) to see if it can be successfully imported. Model A is much smaller because a majority of the model content has been moved into separate models (models A1 to A8). Even though model A still requires the dependent models to go through the import process, there is a better chance of success because the load is split into smaller models. If you still receive the Internal error window indicating an out-of-memory problem, or if one or more diagrams did not successfully import, select a smaller model or smaller set of models to import.

For example, you might consider trying to import model A2 and its referenced models (models A4 through A8) because model A, A1, and A3 are not part of the dependency closure. If this approach still does not work, try a smaller set such as model A6, and so on.

Once you successfully import a smaller set of models such as A6, the next time you try to import a model that uses the models in the smaller A6 set, the Rational® XDE Model Import wizard marks the models as Already imported. The Rational XDE Model Import wizard reuses the A6 model set, which increases the chance for a successful import because memory is not needed to import the A6 set of models.

Related concepts
XDE model migration
Rational XDE model upgrade process
Terms of use | Feedback
(C) Copyright IBM Corporation 2004, 2005. All Rights Reserved.