(Build ID: 173316)

Cameo Enterprise Architecture™ software includes UPDM, SysML, BPMN, SoaML, TOGAF, Zachman Framework, and UML for building integrated enterprise architectures meeting DoDAF and MODAF requirements. The product supports all DoDAF 1.5, DoDAF 2.0, and MODAF 1.2 viewpoints and views dependent on the selected user environment. Each user environment provides architecture framework specific concepts, artifacts, new project templates, samples, and architecture framework specific usability features. A user environment can be changed any time by fully converting model to meet requirements of the selected architecture framework.

Users of Cameo Enterprise Architecture Architect and Enterprise editions can use the information engineering notation for conceptual, logical, and physical data modeling.

* Sometimes when running the application, the OutOfMemory error occurs. This means that your computer has not enough memory for working with the application. Ways of solving the problem are described in section OutOfMemory problem.

Operating system: Any Java 7 or later compatible operating system, i.e., Windows XP/ Vista/ 7/ 8, Linux, Mac OS X (most testing procedures and debugging have been performed on these operating systems).

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

Java Virtual Machine:

• Oracle Java SE 7 Update 55 is recommended for Windows and Linux.
• Oracle Java SE 7 Update 25 is recommended for Mac OS X Lion, Mac OS X Mountain Lion, and Mac OS X Mavericks.

http://www.nomagic.com/support/jvm-list.html

First, obtain the Cameo Enterprise Architecture installation files. You can download the latest version from the Cameo Enterprise Architecture homepage http://www.nomagic.com/products/cameo-enterprise-architecture.html

If you are going to install Cameo Enterprise Architecture on Unix, MAC OS, or other operating system that is not Windows OS, then JVM must be installed on your computer. For more information about the recommended Java version, see 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 Cameo Enterprise Architecture from the no-install package (see section Using no-install package).

Using the installer

1. Ensure that your computer meets the system requirements for running the application.

2. Download either:

• Cameo_Enterprise_Architecture_<version number>_win.exe for 32-bit Windows
• Cameo_Enterprise_Architecture_<version number>_win64.exe for 64-bit Windows

3. Double-click the installer.

4. In case the User Account Control dialog appears asking your permission for the installer to make changes in your computer, click Yes.

5. Follow the on-screen instructions to install Cameo Enterprise Architecture.

NOTES:

• For more information about the recommended Java, see http://www.nomagic.com/support/jvm-list.html

• For more information on how to change the Java version, see Changing Java version.

• For more information about memory allocation, see section "Memomy allocation" in MagicDraw UserManual.pdf.

Unix

1. Download Cameo_Enterprise_Architecture_<version number>_unix.sh.

2. Double-click the installer.
   IMPORTANT!  Be sure you have:

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

Mac OS X

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

1. Download Cameo_Enterprise_Architecture_<version number>_mac.dmg.

2. Open the Applications folder and create a new folder named, for example, Cameo Enterprise Architecture <version number>.
   NOTE: We suggest creating a new folder for each Cameo Enterprise Architecture version in order to not overwrite earlier Cameo Enterprise Architecture versions. After installing a new version in the newly created folder you will be able to import the configurations from an earlier Cameo Enterprise Architecture version.

3. Double-click the installer.
   

4. Drag the Cameo Enterprise Architecture folder to the Applications/Cameo Enterprise Architecture <version number> or some other folder.

Using no-install package

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

1. Download Cameo_Enterprise_Architecture_<version number>_no_install.zip.

2. Extract the file.

3. Open the bin directory and run cameoea.exe to start Cameo Enterprise Architecture.

Unix

1. Download Cameo_Enterprise_Architecture_<version number>_no_install.zip.

2. Extract the file.

3. Open the bin directory and run cameoea to start Cameo Enterprise Architecture.
   IMPORTANT! Be sure you have installed JVM.

Mac OS X

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

1. Download Cameo_Enterprise_Architecture_<version number>_no_install.zip.

2. Extract the file.

3. Open the root directory and double-click Cameo Enterprise Architecture <version number>.app to start Cameo Enterprise Architecture.

To use the Cameo Enterprise Architecture's release that contains no Java Virtual Machine (JVM), you should have the JVM installed on your computer. JVM is an application that provides the interpretation of the bytecode Java class files. Different operating systems may have different JVM implementations, thus some bugs may be specific to the operating system or JVM.

Cameo Enterprise Architecture is a stable environment, if it is configured properly and if the stable JVM is used. USE RECOMMENDED JVM TO AVOID MANY PROBLEMS. All recommendations are written below. As Cameo Enterprise Architecture is a Java application, most of the stability and performance depends on the JVM implementation. Refer to the JVM specification and problem descriptions, if you have problems on the specific OS.

JDK 1.1.x, 1.2.x, 1.3.x, 1.4.x, and 1.5.x is not supported.

To review your system and JVM information (in case you have already installed Cameo Enterprise Architecture) on the main menu click Help > About Cameo Enterprise Architecture and then in the opened dialog click the Environment tab. JDK version can also be encountered from the command-line prompt by typing the command:

java -version

Attention for non-Windows users!
You have to start the application setup from the command-line prompt. Your system should have Java Virtual Machine (JVM) installed BEFORE running the Cameo Enterprise Architecture installer (preferred versions are mentioned above).

You can download the newest demo version of Cameo Enterprise Architecture from
http://www.nomagic.com/products/cameo-enterprise-architecture.html

Changing Java version

In the cameoea.properties file, which is located in <Cameo Enterprise Architecture installation directory>\bin, add the value for the following parameter:

JAVA_HOME=<path to new JRE>

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

Changing the location for configuration files storage

If Cameo Enterprise Architecture is running, you can open this folder directly from the application. Do the following:

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

• <Cameo Enterprise Architecture installation directory>
• Common Application Data location (on Windows OS)
• Other directory

1. Open the cameoea.properties file, which is located in <Cameo Enterprise Architecture installation directory>\bin.
2. Change the parameter value from

   -DLOCALCONFIG=true

   to

   -DLOCALCONFIG=false

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

1. Open the cameoea.properties file, which is located in <Cameo Enterprise Architecture installation directory>/bin.
2. Change the parameter value from

   -DLOCALCONFIG=true

   to

   -DLOCALCONFIG=false

NOTE: The Common Application Data location is the following:
• On Windows NT4 - C:\WINNT\Profiles\All Users\Application Data
• On Windows 2000/XP - C:\Documents and Settings\All Users\Application Data
• On Windows Vista/7/8 - C:\ProgramData

Do either:

1. Open the folder, wherein the configuration files are stored (for the exact location, see the preceding table).
2. Create a new file named cameoearedirect.
3. In the file, type the absolute path to the folder, wherein Cameo Enterprise Architecture configuration files will be saved, e.g., C:\<directory name>.

1. Open the cameoea.properties file, which is located in <Cameo Enterprise Architecture 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 Cameo Enterprise Architecture installation directory (see section To store configuration files in Cameo Enterprise Architecture application installation directory), files will not be stored in the defined location.

Redirecting output info to console

Cameo Enterprise Architecture output information by default goes into the cea.log file. If there is a need, you can redirect the output to console.

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

On all operating systems

In the cameoea.properties file (or the cameoea64.properties file on 64-bit Windows), which is located in <Cameo Enterprise Architecture installation directory>\bin, add the value for the following parameter:

APP_ARGS =-verbose

Web page

To download the demo of this version and to get contact information or purchase details, please go to http://www.nomagic.com/products/cameo-enterprise-architecture.html

New features

What edition do I need?

For information on Cameo Enterprise Architecture editions, go to http://www.nomagic.com/products/cameo-enterprise-architecture.html and click the Editions tab.

Forum

Discuss and get answers about No Magic products in No Magic Community Forum. With respect to the growing interest in No Magic products, we have expanded the capabilities that had been provided by our newsgroups and have moved the content to the online forum. You are welcome to post your comments and questions here.

Knowledgebase and new issue registration

• Knowledge base and new issues registration - http://www.nomagic.com/support.html
• Issues, suggestions, and requests about new features can be submitted directly from Cameo Enterprise Architecture application - Help > Report an Issue.
  
• sales@nomagic.com - questions regarding academic and site discounts, delivery, customer profile, invoices and related issues.
  
• contact@nomagic.com - email for other contacts.
  

We are awaiting your comments and suggestions. More than a half of the features of the current version added because our demo version users have requested them. Do not miss the chance to see your desired features in the future versions!

Documentation

Find out useful information about working with Cameo Enterprise Architecture in the following types of documentation:

• Manuals, user guides, and tutorials stored in <Cameo Enterprise Architecture installation directory>\manual

- For the generic information about using the application, see MagicDraw UserManual.pdf.
- For the specific information about building integrated enterprise architectures that meet DoDAF, MODAF, and NAF requirements, see Cameo EA UserGuide.pdf.

• Cameo Enterprise Architecture Help

OutOfMemory problem

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.

If during your work the out of memory Error dialog box appears, change the java heap size and/or the MaxPermSize directly in this dialog box (change the option that is labeled with red color).

• The maximum theoretical heap limit for the 32-bit JVM is 4G. Due to various additional constraints such as available swap, kernel address space usage, memory fragmentation, and VM overhead, in practice the limit can be much lower. On 32-bit Windows systems the maximum heap size will range from 1.1G to 1.3G. On 32-bit Solaris kernels the address space is limited to 2G. On 64-bit operating systems running the 32-bit VM, the max heap size can be higher, approaching 4G on many Solaris systems (Java HotSpot VM FAQ).
• On 64-bit VMs, you have 64 bits of addressability to work with resulting in a maximum Java heap size limited only by the amount of physical memory and swap space your system provides (Java HotSpot VM FAQ).

If the out of memory Error dialog box does not appear or increasing the heap size does not help examine the full error message. In the exception message, further information is supplied after java.lang.OutOfMemoryError. Here are some common examples of what that additional information may be, what it may mean, and what to do about it:

• Java heap space
  This indicates that an object could not be allocated in the heap. The issue may be just a configuration problem. You could get this error, for example, if the maximum heap size specified by the –Xmx command line option (or selected by default) is insufficient for the application and needs to be increased.
• PermGen space
  This indicates that the permanent generation is full. If an application loads a large number of classes, then the permanent generation may need to be increased. You can do so by specifying the command line option –XX:MaxPermSize=n, where n specifies the size.
• unable to create new native thread
  This indicates that OS cannot allocate memory for the new thread. This formula gives a decent estimate for the number of threads you can create:

  (MaxProcessMemory – JVMMemory – ReservedOsMemory) / (ThreadStackSize) = Number of threads
  JVMMemory=Perm Size + Heap Size.
  

  In this case you need to decrease the java maximum heap size or/and decrease the stack size for threads. You can do so by specifying the command line option -Xss.
• requested <size> bytes
  The Java HotSpot VM cannot expand its heap size if memory is completely allocated and no swap space is available. This can occur, for example, when several applications are running simultaneously. If you see this symptom, consider increasing the available swap space by allocating more of your disk for virtual memory and/or by limiting the number of applications you run simultaneously. You may also be able to avoid this problem by setting the command-line flags -Xmx and -Xms to the same value to prevent the VM from trying to expand the heap. Note that simply increasing the value of -Xmx will not help when no swap space is available (Java HotSpot VM FAQ).

You can change the java maximum heap size (-Xmx), permanent generation maximum size (-XX:MaxPermSize), thread stack size (-Xss) in your <Cameo Enterprise Architecture installation directory>/bin/cameoea.properties file, in the line:
JAVA_ARGS=-Xmx800M -XX\:PermSize\=40M -XX\:MaxPermSize\=150M -Xss512K

NOTE: Integrated Cameo Enterprise Architecture runs on JVM that is specified by the IDE. If you are running Cameo Enterprise Architecture integrated with IDE you will need to modify startup properties for the appropriate IDE.

Application pause time problem

If you are having problems with pause times in your application, try to change the default garbage collector.

• If you have a single-processor client machine, it is suggested to use the Concurrent Mark-Sweep (CMS) Collector in Incremental mode. When trying incremental mode, it is recommended the following as an initial set of command line options: -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:+CMSIncrementalPacing -XX:CMSIncrementalDutyCycleMin=0 -XX:CMSIncrementalDutyCycle=10
• If you have a multiprocessor machine (especially with four or more processors), try one of the parallel garbage collection algorithms - Concurrent Mark-Sweep (CMS) Collector or Parallel Compacting Collector. The parallel compacting collector is used specifying the command line option -XX:+UseParallelOldGC, CMS collector is used, specifying the command line option -XX:+UseConcMarkSweepGC.

StackOverflow problem

Sometimes when running the program, the StackOverflowError occurs.

If you are running the Sun's, IBM JVM, set the following java properties in your <Cameo Enterprise Architecture installation directory>/bin/cameoea.properties file to avoid the above problem:
to the line JAVA_ARGS=-Xmx800M, append the string -Xss<stack size>.
For example:
JAVA_ARGS=-Xmx800M -Xss2M
This sets java stack size to 2 megabytes.

NOTE: Integrated Cameo Enterprise Architecture runs on JVM that is specified by the IDE. If you are running Cameo Enterprise Architecture integrated with IDE you will need to modify startup properties for the appropriate IDE.

Computer freezes or reboots while exiting Cameo Enterprise Architecture or repaint problems occur

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

NOTE: Integrated Cameo Enterprise Architecture runs on JVM that is specified by the IDE. If you are running Cameo Enterprise Architecture integrated with IDE you will need to modify startup properties for the appropriate IDE.

Java Virtual Machine could not be started

Open the <Cameo Enterprise Architecture installation directory>/bin/cameoea.properties file for editing and comment the lines defining default memory settings. These lines should look like this:

# DEFAULT_MEMORY_SETTINGS_64=-Xmx2400M -XX\:PermSize\=60M -XX\:MaxPermSize\=200M -Xss1024K
# DEFAULT_MEMORY_SETTINGS_32=-Xmx800M -XX\:PermSize\=40M -XX\:MaxPermSize\=150M -Xss640K

After the install, Cameo Enterprise Architecture cannot be launched or it just appears on the screen and vanishes

Please try one of the following solutions:

• Start Cameo Enterprise Architecture with system property no.printer.lookup=true.
  In the <Cameo Enterprise Architecture installation directory>/bin/cameoea.properties file to the line'JAVA_ARGS=' append additional part
  -Dno.printer.lookup=true.
  
• The problem may be related with printer driver. The description of this problem is published in the Java Bug Database (http://java.sun.com/). Bug ID is 4988827. Try to change the default printer driver on your Windows OS and load again. For example, the HP LaserJet 4000N PCL5e should be compatible, while HP LaserJet Series 4000 PCL6, HP LaserJet Series 4000 Postscript, Savin 2535 PCL6, HP LaserJet Series 5000 Postscript, HP Deskjet 560C, Acrobat PDFWriter are not.

Cameo Enterprise Architecture is not started on Windows Vista

Cameo Enterprise Architecture installer is not started or Cameo Enterprise Architecture is not started on Linux OS

Cameo Enterprise Architecture installer may not be started or Cameo Enterprise Architecture itself may not be started, because of changes in default system Java. In this case when starting installer or Cameo Enterprise Architecture, no GUI appears or when starting from 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 default Sun Java and default system Java becomes Ubuntu Java. To start the Cameo Enterprise Architecture 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.
  

Sometimes Cameo Enterprise Architecture becomes unpredictable

1. Open the <Configuration files directory>\.cameoea\<version number> and delete all cache folders. For more information about configuration files location, see section Changing the location for configuration files storage.
2. Restart Cameo Enterprise Architecture.
   

cea.log file location

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

If for some reasons Cameo Enterprise Architecture cannot be started, look for the cea.log file in configuration files directory. For more information about configuration files location, see section Changing the location for configuration files storage.

Frequently Asked Questions

Example files

After you have installed Cameo Enterprise Architecture, you can open an example of a diagram. These files are in the samples directory.

DEMO version of Cameo Enterprise Architecture allows for saving a project with 20 classes, 25 actions, 25 use cases, 25 states, 25 lifelines, 25 instance specifications, 25 nodes, and 25 components, although it can read and print projects of any size.

The DEMO version expiration date is limited. The exact expiration date is provided in the email containing demo license key.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/) and JIDE Software (http://www.jidesoft.com).