(Build ID: 154668)

MagicDraw Reader edition is made for reading and previewing UML models created with MagicDraw and is free of charge. It is extremely useful when you want to share your ideas expressed in UML with partners, colleagues, or clients, who do not have their copy of MagicDraw. This edition is also equipped with printing and the image export capabilities.

* Sometimes when running the program the OutOfMemory error occurs. The cause of an OutOfMemoryError is that you simply haven't got enough memory available for the workings of the application.
Parameters JAVA_ARGS can be updated in <MagicDraw installation directory>/bin/mduml.properties in the line JAVA_ARGS=-Xmx800M
NOTE: The java maximum heap should be set to less than the available physical RAM on the machine, that is the RAM minus the amount of memory taken by any other processes that will run concurrently. Otherwise your JVM process will likely swap and that will slow down the application.

Operating system: Any Java SE 6 or later compatible virtual machine, i.e., Windows 95/98/NT/2000/XP/Vista/ 7/ 8, Linux, Mac OS X (most testing procedures and debugging were performed on those operating systems).

HTML browser: Any. Preferred Firefox or Internet Explorer and Safari for Mac OS X.

Java Virtual Machine:

• Oracle Java SE 7 Update 21 is recommended for Windows, Linux, Mac OS X Lion, and Mac OS X Mountain Lion.
• Oracle Java SE 6 Update 45 is recommended for Mac OS X Leopard and Mac OS X Snow Leopard.

You can find the up-to date JVM list at:
http://www.nomagic.com/support/jvm-list.html

If you use an operating system other than Windows, Unix, or Mac OS X, we recommend to run MagicDraw Reader from the no-install package (see section "Using no-install package").

Using installer

1. Download the installer MD_Reader_<version number>_win.exe

2. Double-click the installer. 

Unix

1. Download MD_Reader_<version number>_unix.sh.
2. Double-click the installer. 

• JVM installed.
• The execute permission on install files.

Mac OS X

1. Download MD_Reader_<version number>_mac.dmg.
2. Go to the Applications folder and create a new folder named for example MagicDraw Reader <version number>. We suggest to create different folders for different MagicDraw Reader versions in order to do not overwrite previous MagicDraw Reader versions. After installing a new version to the specially created folder you will be able to import a previous MagicDraw Reader version configuration.
3. Double-click the installer.
4. Drag the MagicDraw Reader folder to the Applications/MagicDraw Reader <version number> folder or some other folder.

IMPORTANT! Be sure you have JVM installed. Be aware, that Mac OS X Lion and Mac OS X Mountain Lion do not include a Java runtime by default. It must be installed separately.

Using no-install package

Download the no-install package to run MagicDraw Reader on any operating system.

Windows 95/ 98/ NT/ 2000/ XP/ Vista/ 7/ 8

1. Download MD_Reader_<version number>_no_install.zip.
2. Extract the file.
3. Go to the bin directory and run mduml.exe to start MagicDraw

1. Download MD_Reader_<version number>_no_install.zip.
2. Extract the file.
3. Go to the bin directory and run mduml to start MagicDraw.

1. Download MD_Reader_<version number>_no_install.zip.
2. Extract the file.
3. Go to the root directory and run MagicDraw UML Reader.app to start MagicDraw Reader.

Changing Java version

In the mduml.properties file, which is located in <MagicDraw installation directory>/bin, add the value for the following parameter:

JAVA_HOME=<path to new JRE>

NOTE: Integrated MagicDraw runs on the JVM specified by the IDE. In order to change JVM, you need to modify startup properties for the IDE, MagicDraw integrates with. If you are running MagicDraw integrated with IDE, read the appropriate readme.html for the specific integration, which can be found in <MagicDraw installation directory>\integrations\<IDE directory>.

Changing the location for configuration files storage

If MagicDraw is running, you can open the configuration files folder directly from the application. Do the following:

1. On the main menu, click Help > About MagicDraw.
2. Open the Environment tab.
3. Click the Configuration Files hyperlink.

• <MagicDraw installation directory>
• Other directory

1. Open the mduml.properties file, which is located in <MagicDraw installation directory>/bin.
2. Change the parameter value from

   -DLOCALCONFIG=true

   to

   -DLOCALCONFIG=false

3. On Windows OS, add the additional parameter

   -DWINCONFIG=false

   IMPORTANT: It is important to add the DWINCONFIG parameter on Window OS, otherwise the configuration files will not be stored at MagicDraw installation directory.

Do either:

1. Go to the folder, where the configuration files are stored (for the exact location, see the preceding table).
2. Create a new file named magicdrawredirect.
3. In the file, type the absolute path to the folder, wherein MagicDraw configuration files will be saved, e.g., C:/<directory name>.

1. Open the mduml.properties file, which is located in <MagicDraw installation directory>/bin.
2. Change the parameter value:
   

   -Dlocalconfig.location=<absolute path to a chosen location>

   NOTE: If you have defined to store files in the MagicDraw installation directory (see section "To store configuration files in MagicDraw application installation directory"), files will not be stored in the defined location.

Redirecting output info to the console

The MagicDraw output information by default goes into the md.log file. If there is a need, you can redirect the output to the console.

NOTE: If you cannot find the md.log file, see section "md.log file location".

On all operating systems

In the mduml.properties file, which is located in <MagicDraw installation directory>/bin, add the value for the following parameter:

APP_ARGS =-verbose

OutOfMemory problem

Sometimes when running the program the OutOfMemory error occurs.

Windows, Linux OS, Mac OS X

If you are running the Sun's JVM, set the following java properties in your mduml.properties file to avoid the above problem:
in the line JAVA_ARGS=-Xmx600M, change the number of the heap size '600' to the maximal heap size in megabytes.

For example, the java heap size would be:
JAVA_ARGS=-Xmx800M
This sets the java heap size to 800 megabytes.

NOTE: Integrated MagicDraw runs on the JVM, specified by the IDE. If you are running MagicDraw, integrated with the IDE, you will need to modify startup properties for the appropriate IDE.

OutOfMemory PermGen space problem

If you get the exception "java.lang.OutOfMemoryError: PermGen space", please check, if PermSize is specified in the configuration file.

Windows, Linux OS, Mac OS X (not applicable for IBM JVM)

If PermSize is specified in the mduml.properties file and the same problem still appears, MaxPermSize should be increased. PermSize is a part of heap size, so MaxPermSize should always be smaller than the heap size specified with the Xmx parameter.

For example:
JAVA_ARGS=-Xmx800M -XX\:PermSize\=40M -XX\:MaxPermSize\=200M

NOTE: Integrated MagicDraw runs on the JVM, specified by the IDE. If you are running MagicDraw, integrated with the IDE, you will need to modify startup properties for the appropriate IDE.

StackOverflow problem

Sometimes when running the program, StackOverflowError occurs.

Windows, Linux OS, Mac OS X

If you are running the Sun's, IBM JVM, set the following java properties in your mduml.properties file to avoid the above problem:
to the line JAVA_ARGS=-Xmx600M, append the string -Xss<stack size>.

For example:
JAVA_ARGS=-Xmx600M -Xss2M

This sets the java stack size to 2 megabytes.

NOTE: Integrated MagicDraw runs on the JVM, specified by the IDE. If you are running MagicDraw, integrated with the IDE, you will need to modify startup properties for the appropriate IDE.

Computer freezes or reboots while exiting MagicDraw or repaint problems occur

This may happen because of JDK SDK and the Windows direct draw incompatibility. We would suggest you to turn off the direct draw for the MagicDraw application.
In the <MagicDraw installation directory>/bin/mduml.properties file to the line'JAVA_ARGS=' append the additional part
-Dsun.java2d.noddraw.

NOTE: Integrated MagicDraw runs on the JVM, specified by the IDE. If you are running MagicDraw, integrated with the IDE, you will need to modify startup properties for the appropriate IDE.

After the install, MagicDraw cannot be launched or it just appears on the screen and vanishes

Try the following solution:

1. Start MagicDraw with the system property no.printer.lookup=true.
2. In the <MagicDraw installation directory>/bin/mduml.properties file to the line'JAVA_ARGS=' append the additional part
   -Dno.printer.lookup=true. 

NOTE: Integrated MagicDraw runs on the JVM, specified by the IDE. If you are running MagicDraw, integrated with the IDE, you will need to modify startup properties for the appropriate IDE.

MagicDraw installer is not started or MagicDraw is not started on Linux OS

The MagicDraw installer may not be started or MagicDraw itself may not be started, because of changes in the default system Java. In this case when starting the installer or MagicDraw, no GUI appears or when starting from the command line the following message is displayed:
Configuring the installer for this system's environment... No Java virtual machine could be found from your PATH environment variable. You must install a VM prior to running this program.
We would suggest the following solution:

• Change your default system Java to recommended.
• After some Ubuntu update, the Ubuntu Java overrides the default Sun Java and the default system Java becomes Ubuntu Java. To start the MagicDraw installer, Ubuntu-restricted-extras should be installed. For more information about installing the Ubuntu-restricted-extras, see the Ubuntu website: https://help.ubuntu.com/community/RestrictedFormats.

1. On the main menu, click Help > About MagicDraw.
2. Open the Environment tab.
3. Click the Log File hyperlink.

If for some reasons MagicDraw cannot be started, look for the md.log file in configuration files directory. For more information about configuration files location, see the "Changing the location for configuration files storage" section.

Frequently Asked Questions and Forum