Borland® Together® 12.6 Release Notes

Last updated: November 28, 2013

This file contains important information that may not appear in the online Help. Please read this file in its entirety.

What's New and Fixed in This Release

System Requirements/Prerequisites

Installation Instructions


Known Issues and Limitations

Together Capabilities

Finding Out More

Getting assistance

What's New and Fixed in This Release

This release of Together includes improvements in functionality and fixed bugs since Together 12.5. The important changes introduced in this release are highlighted below.

Selective Loading

When working with large projects, memory consumption can become an issue. To avoid running into such issues, selective loading is now available in Together 12.6:

  1. Select Preferences -> Modeling -> Selective Loading.
  2. Use the Add Packages and Remove buttons to select the packages that you want to work with. Only these packages will be loaded into memory.
  3. Click Apply to confirm your selection.

Note: Uncheck the Load package-selection below only checkbox to load the complete project, as in previous versions.

Modeling C++ Projects


Back to top


Since version Together 2007 integrations with version control systems (StarTeam®) and requirement management products (CaliberRM™, RequisitePro) are not part of the Together product anymore. These integrations should be available separately from Borland. The Together 12.6 help still includes information about these integrations. However, newer versions of integrations may have some changes in functionality, so it is recommended that you check the release notes that are provided with each integration package.

Back to top

System Requirements/Prerequisites

Following are the system requirements for installing and running Borland Together 12.6:

Resources Requirements Notes
CPU Intel® Pentium® 4 1GHz (or compatible) Intel® Pentium® 4 2.8 GHz or more recommended
Memory 1 GB minimum 2 GB is recommended. For optimal performance when working with large-scale projects, you might need to adjust the JVM heap setting in the Together.ini, .bat, .cmd, or .sh files found in the eclipse subfolder of the Together installation folder.
Disk Space up to 700 MB May be less if some of the needed Eclipse components are already installed.
Video High color mode, 1024x768 Recommended resolution: 1600x1200
DVD Drive Optional Necessary if installing from DVD.
Operating system Microsoft Windows Vista, Microsoft Windows XP Pro with Service Pack 3, Microsoft Windows 7 (32/64 bit), Microsoft Windows 8
Red Hat Enterprise Linux 5, x86-32/64, Red Hat Enterprise Linux 6, x86-32/64


IDE Platform Eclipse 4.3.1 platform  
Java Platform Sun® J2SE 5.0 Update 22, J2SE 6.0 update 45 (latest update is recommended). JVM should already be installed prior installing Together. Please make sure that the required version of JVM is configured to run Eclipse where Together is going to be installed. Please refer Installation Instructions section for details.
Eclipse components and projects
  • Eclipse 4.3.1
  • GEF SDK 3.9.1
  • EMF SDK 2.9.1 (EMF + XSD)
  • EMF Transaction SDK 1.7.0
  • MDT OCL SDK 4.1.1
  • MDT UML2 SDK 4.1.1
  • GMF SDK 3.0.1
  • M2M QVTOML SDK 3.3.0
  • Birt 4.3.1 + DTP 1.11.1 + WTP WST 3.5.1
  • CDT SDK 8.2.1
Eclipse SDK should be already installed prior to installing Together. Please refer Installation Instructions section for details.
Web Browser Any web browser that supports frames Microsoft Internet Explorer 6.0 or later is recommended on Windows systems.
SVG Viewer Adobe SVG viewer version 3.0 or later. Follow the link to download this viewer from Adobe web site:

Back to top

Installation Instructions

Together 12.6 can be installed to an existing instance of Eclipse SDK version 4.3.1 from the online or archived update site. Therefore Eclipse SDK as well as Java Virtual Machine needed to run it should be already installed prior to installing Together. If you have both installed please omit the following two subsections and jump right to the subsection Installing Together.

Installing Java Virtual Machine

If you already have an instance of Eclipse 4.3.1 installed you must have the JVM needed to run it installed as well. You may want to verify that the recommended version of JVM is used by Eclipse at the configurations details: once Eclipse is running invoke Help -> About from the main menu, then press Installation Details button, switch to Configuration page and look for java.home, java.version lines.

Together shares the requirements of Eclipse; namely it needs Java 5 update 22, or Java 6 update 45. Note that later updates of Java 6 contain the important fixes, so the latest available Java 6 update is recommended.

If the appropriate JVM version is not installed, please download the latest one from the Java Archive Downloads - Java SE 6 at the Oracle web site. If you need Java 5, you may download JRE 5 update 22 from the Archive area.

Installing Eclipse SDK

If there is no any instance of Eclipse 4.3.1 on your system, please visit Eclipse 4.3.1 downloads page at the Eclipse web site and download the package. The installation is as simple as unpacking the archive to the folder of your choice.

If you would like to add Together to an existing Eclipse installation, note that Together needs Eclipse SDK. Thus please make sure your Eclipse contains the Eclipse SDK feature.

If it is not the case perform the following steps prior installing Together:

If it appears you have several JVMs installed, note that it is possible to enforce Eclipse to use a particular Java Machine. It is necessary to add -vm <path to JVM> parameter in eclipse.ini files, for example:
Original file:


File with changes:
C:\Program Files\Java\jre1.5.0_22\bin
Important: Make sure you preserve the line breaks.

Without these parameters Eclipse will first try to look for a Java machine in the ./jre subfolder of its home folder. If there is not one it will use the JVM installed in your system. In the later case, to check what version of JVM going to be used you may run the console at the Eclipse home folder and execute the command:

java -version

Installing Together

For installing Together in an existing Eclipse instance, use Borland Together 12.6 archived update site or Borland Eclipse 4.3.1 online update site.

Installing Micro Focus License Manager

Since Together 12.5 the licensing system has changed. Now you need to install Micro Focus License Manager.

On Windows systems Together will ask you to install License Manager when you try to use Together functionality first time after installation (for example when you create your first project). You should choose Yes and follow the instructions of the Micro Focus License Manager installer. Also you can run the installer manually from your Together folder. lmsetupx86.msi for 32 bit systems and lmsetupx64.msi for 64 bit.

On Linux systems you need to run the installer script manually. Execute script in Terminal as root.

Adjusting parameters in Together.ini and command line launchers

If you have several JVMs installed and need Together to use a particular one, you may want to edit Together.ini file. Please refer to the instructions and the example provided above in the section Installing Eclipse SDK for the eclipse.ini file. Perform similar operations for Together.ini in order to add -vm <path to JVM> parameter Without this parameter Together looks for a Java Virtual Machine first in a ./jre directory in the root of Eclipse and then on the search path.

Together command line launchers look for a java virtual machine first in a ./jre directory in the root of Eclipse, and then use the JAVA_HOME environment variable. You can adjust the JAVA_HOME environment variable in your system settings or edit command line launcher files specifying the path to the location where the required JVM is installed. For example at gendoc.cmd:
REM Unless you have a JRE installed in the Eclipse home, please define JAVA_HOME ...
set JAVA_HOME=C:\Program Files\Java\jre1.5.0_22

Note: Please refer the System Requirements section for the information about the required JVM version.

Together.ini and command line launchers are preconfigured to work with Eclipse version 4.3.1 and so refer to Equinox launcher (org.eclipse.equinox.launcher) and launcher library of explicit versions 1.3.0.v20130327 and 1.1.200.v20130807 respectively. Other versions of Eclipse may have a different version of this plugin. If you choose to install Together in an Eclipse version other than 4.3.1 you may need to replace all occurrences of the Equinox plugin version in the Together.ini and command line launchers with the actual version.

Back to top


Once you installed Micro Focus License Manager and you have your authorization code please do the following:

Existing customers with active support contracts please contact Support Line to request your new license keys. License keys from previous versions are not suitable for Together 12.6.

Back to top

Known Issues and Limitations

New issues may be identified and/or resolved after release. Please check the latest version of the Together Release Notes at Together Technical Publications page for changes to the known issues below.

Modeling and Diagrams

Together OCL and QVT

C++/IDL Modeling Projects

Documentation Generation and Printing

Import Together Project Wizard

Referenced Projects

XMI Import/Export

DSL Development



Back to top

Together Capabilities

The default capabilities are different for classic Together Modeling and the DSL Toolkit. Select Window -> Preferences, then select the General node and the Capabilities node. You can click the Advanced button to enable/disable capabilities at a more granular level.

The following table lists the Together capabilities that are enabled and disabled for classic Together Modeling and the DSL Toolkit:

Capability group Advanced Capability item Description Classic Together Modeling default DSL Toolkit default
DSL Development   Features related to domain-specific language and model-driven development. Disabled Enabled
  Diagram Definition Diagram definition capabilities for domain models. Disabled Enabled
  Domain Modeling Capabilities associated with modeling a domain-specific model. Disabled Enabled
  DSL Project General features for working with DSL Projects. Disabled Enabled
Model to Model Transformations   Features for model-to-model transformations. Disabled Enabled
  Operational Mapping Language (QVT) Operational mapping language (QVT) features. Disabled Enabled
  Operational QVT Debugging Operational QVT debugging features. Disabled Enabled
Model to Text Transformation   Features for model-to-text transformations. Disabled Enabled
  Template Authoring Template authoring features. Disabled Enabled
  Template Exploring Template exploring features. Disabled Enabled
  Template Exploring (Legacy) Legacy template exploring. Disabled Disabled
Model Workflow   Features for model workflow. Disabled Enabled
  Workflow Definition Workflow definition features. Disabled Enabled
  Workflow Execution Workflow execution features. Disabled Enabled
Modeling   Modeling Capabilities. Enabled Disabled
  Business Process Modeling Business Process Modeling. Enabled Disabled
  C++ Modeling C++ Modeling. Enabled Disabled
  Data Modeling Data Modeling. Enabled Disabled
  Documentation Documentation generation. Enabled Disabled

Enhanced Rich Text Editor
Enhanced Rich Text Editor
  IDL Modeling IDL Modeling. Enabled Disabled
  Java Modeling Java Modeling. Enabled Disabled
  Manage element persistence Ability to manage element persistence state, make it stand-alone or packaged along with other elements in containing package. Disabled Disabled
  MDL and MDX Imports MDL and MDX Imports. Enabled Disabled
  Model QA Model Quality Assurance. Enabled Disabled
  Modeling profiles Profiles. Enabled Disabled
  Patterns Patterns Definition and Registry, Patterns Recognition. Enabled Disabled
  Source code QA Source code Quality Assurance. Enabled Disabled
  Together Project Import Import project from one of the previous versions of Together. Enabled Disabled
  Together QVT QVT implementation initially appeared at Together 2006, primary engine to work with Together models. Enabled Disabled
  UML 1.4 UML 1.4 Modeling. Enabled Disabled
  UML 2.0 UML 2.0 Modeling. Enabled Disabled
  XMI Import/Export XMI Import/Export. Enabled Disabled
  XSL XSL transformations. Enabled Disabled
Modeling Tools   Features for modeling tools. Disabled Enabled
  Hyperlinks and Requirement Traces (Early Access) Hyperlinks and requirement traces features (early access). Disabled Disabled
  Model Refactoring (Early Access) Model refactoring features (early access). Disabled Enabled
Reporting   Features for reporting. Disabled Enabled
  Model Reporting Model reporting features. Disabled Enabled
  CVS Support for Modeling CVS Actions for Model Navigator and Diagram Editors. Adds several variants of Edit/Unedit actions to the Team menu for model elements. When work with CVS in watch/edit mode and autocheckout turned off, those actions simplify taking required resources behind the selected model element for editing. Disabled Disabled

Back to top

Finding Out More

Online Help

Together provides online help through your Eclipse help browser. Select Help Contents on the Help menu. When the help browser opens, click Borland® Together® Modeling Guide, Borland® Together® DSL Toolkit Guide, Borland® Together® UML 2.1 Guide, or another online help section.

Together site

Please visit Together site Together

Back to top

Getting Assistance

Visit Micro Focus SupportLine at,

Visit Borland at

Back to top


Copyright © 2013 Micro Focus IP Development Limited. All Rights Reserved. Portions Copyright © 1998-2010 Borland Software Corporation (a Micro Focus company).
BORLAND, the Borland logo, and Borland product names are trademarks or registered trademarks of Borland Software Corporation or its subsidiaries or affiliated companies in the United States, United Kingdom, and other countries. All other marks are the property of their respective owners.