Last updated: July 29, 2009
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
This release of Together includes improvements in functionality, new features, and fixed bugs since Together 2008 Service Pack 1. The important changes introduced in this release are highlighted below.
This version of QVTO fully implements Operational Mappings part of MOF
Query / Views / Transformations 1.0 specification
(http://www.omg.org/spec/QVT/1.0/).
In addition to many bugfixes the following features are new to this
release:
Unlike Together 2006 R2, Together 2008 R2 does not include integrations with version control systems (StarTeam®, ClearCase) and requirement management products (CaliberRM™, RequisitePro). These integrations should be available separately from Borland. The Together 2008 R2 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.
Following are the system requirements for installing and running Borland Together 2008 R2:
| Resources | Requirements | Notes |
|---|---|---|
| Hardware | ||
| 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 in the Together.ini, .bat, .cmd, or .sh files found in the eclipse subfolder of the Together installation folder. For more information, refer to the Sun® FAQ: http://java.sun.com/docs/hotspot/PerformanceFAQ.html. |
| Disk Space | 1.3 GB | Approximately 600 MB of this space is required for temporary installation files and will be freed after the installation is finished. |
| Video | High color mode, 1024x768 | Recommended resolution: 1600x1200 |
| DVD Drive | Optional | Necessary if installing from DVD. |
| Software | ||
| Operating system | Microsoft Windows Vista, Microsoft Windows XP Pro
with Service Pack 2 Red Hat Enterprise Linux 5.2, x86-32 SUSE Linux Enterprise Server 10 SP2, x86-32 Mac OS X 10.5 |
|
| IDE Platform | Eclipse 3.5 platform | Unless you are installing to an existing Eclipse instance, the required version of Eclipse platform is automatically installed with Together. You do not have to download and install it yourself. Otherwise, at least the Eclipse SDK package of the specified version is required. |
| Java Platform | Sun® J2SE 5.0 Update 14 | Unless you are installing to an existing Eclipse instance, the required version of Java Runtime Environment is automatically installed with Together. You do not have to download and install it yourself. Otherwise please make sure that the required version of JVM is configured to run Together. Please refer Installation Instructions section for details. |
| Eclipse components and projects |
|
The required versions of Eclipse components and projects are automatically installed with Together unless you are installing to an existing Eclipse instance or use advanced install options and install from alternative update sites. In the latter case, if you experience problems with inconsistent configurations please contact the support team for assistance. |
| Web Browser | Any web browser that supports frames | Microsoft Internet Explorer 6.0 or later is recommended on Windows systems. |
| Other | ||
| SVG Viewer | Adobe SVG viewer version 3.0 or later. Follow the
link to download this viewer from Adobe web site: http://www.adobe.com/svg/viewer/install/mainframed.html. |
|
Download the Together 2008 R2 installer for your platform and then run the installer.
Note: The installer will not prevent you from choosing a folder containing another Eclipse instance as a target. But it is highly recommended that in order to install to an existing Eclipse instead of using the installer you run the target Eclipse and connect to the Borland Update Site for Eclipse 3.5 or use the Together 2008 R2 Archived Site, which is available for download. Please refer to the corresponding section below for more details.
If you want to install Together silently (this may be particularly useful for administrators with large networked systems), place the installer.properties file in the directory where your installer is located, or specify "-f" as a command line parameter for the installation binary file: -f <fullPathTo File>. An example of the installer.properties file is shown below:
#
# Destination directory to install Together
#
USER_INSTALL_DIR=/home/test/TestInst.silent
#
# Installer mode silent/console/Swing/AWT
#
INSTALLER_UI=silent
Note: If Together is installed silently, the Together uninstall will also be silent, so be careful not to run multiple uninstalls.
For installing Together to an existing Eclipse instance, use Borland Together 2008 R2 archived update site or Borland Eclipse 3.5 online update site. Both update sites leverage Eclipse p2 update features and deploy Together root files, like the executable, command line launchers, release notes, documentation in PDF format and so on.
Together executable looks for a Java Virtual Machine first in a jre
directory in the root of Eclipse and then on the search path.
To use the particular Java Virtual Machine, please specify -vm
followed by its path in Together.ini. For example:
-vm
C:\Program Files\Java\jre1.5.0_14\bin
Together command line launchers look for a java virtual machine
first in a jre directory in the root of Eclipse then use
JAVA_HOME environment variable.
You can adjust 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_14
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 3.5 and so refer org.eclipse.equinox.launcher of explicit version 1.0.200.v20090520. Newer version of Eclipse, namely its minor updates may have different version of this plugin. If you choose to install Together to the newer version than 3.5 you may need to replace all occurrences of equinox plugin version in the Together.ini and command line launchers to the actual version.
To install a patch for Together 2008 R2, perform the following steps:
1. Select Help -> Install New Software...
2. At the Work with: field select Borland Eclipse 3.5 Update Site http://altd.borland.com/update/eclipse3.5 from the list or type its URL if it is not in the list. Alternatively, if patch is distributed in the form of archived update site, use Add... and then Archive... buttons to locale archived update site with the patch, which is usually named like Together2008R2HotFixNSite.zip.
3. Expand the Together 2008 R2 HotFixes node and search for available patches. Pick the patch you need (if any), and complete the installation following the steps suggested by the Update Manager.
On some systems, the unexpected program termination may occur when antialiasing features for text and graphics are turned on. Make sure you use the latest drivers for your hardware, or try to turn antialiasing off.
EMF API provides only read access to source code elements in modeling projects.
EMF API does not provide the possibility to get parameters and return the result for Operations in UML 1.4 modeling projects.
EMF API does not provide the possibility to get the typed elements type in UML 1.4. modeling projects.
BPMN diagrams (graphical part - positions, colors) are not available through the API.
You can view but should not edit design diagram files as text files. (These files are automatically created/updated by Together and visible in the UML Explorer when the filter is off.) If edited and saved in this manner, the diagram can be lost.
BPMN simulation in step-by-step mode goes one step further than required. The problem is caused by using the standard DESMO-J library and should be fixed by a future release of Together. Note that the simulation report is calculated correctly.
(Bug 346) Navigation to source code with the Open context menu action does not work if the diagram editor is maximized.
(Bug 4688) Data Modeling, Microsoft SQL Server 2005: Secondary XML indices are not supported. The DDL parser can navigate through the construct [ USING XML INDEX xml_index_name [ FOR { VALUE | PATH | PROPERTY } ] ], but there is no support in an ERDB model.
(Bug 4451) Data modeling: The Together ER physical metamodel is a general domain model and supports only "common" DDL objects (tables, views, table columns, indexes, constraints, etc.). It is not designed to support server-specific DDL objects such as Oracle's SEQUENCE. You can design a UML 2.0 profile and support objects specific to Oracle and associations between UML 2.0 and Data Modeling projects by using hyperlinks.
Patterns with some metaclasses (for example, the TemplateSignature metaclass) cannot be applied.
(Bug 5794) If a diagram in project A is changed and there is a dependency from project B, the "ghost" read-only occurrence of this diagram in the project B will not reflect the changes until F5 is pressed to refresh its diagram editor view.
Though you can use the allInstances() OCL operation in Constraints, code generated for this operation is incorrect. Java runtime does not support the generated code and currently there is no standard way to get a collection of all instances of a given class.
Together does not support code generation for isSent/message (^,^^) operators. The corresponding error message is displayed in the "Code Generation Log" view.
OCL parser allows only infix form for mod and div standard operations. You can write 'a div b', 'c mod d', but not 'a.div(b)', 'c.mod(d)'.
Together does not support OCL constraints and code generation for UML templates.
You cannot generate Java code for QVT transformations that use profile metamodels because these metamodels do not have Java implementations. QVT transformations that use profile metamodels can be run in the 'Interpreted' mode.
The Together Modeling and DSL Toolkit features use different implementations of the OCL and QVT engines. Normally there should be no problems using these simultaneously, although the UI may contain a large amount of information. It is recommended that you turn corresponding capabilities on or off as needed (select Window -> Preferences, and then select the General node and the Capabilities node). The Together OCL and QVT engines are the primary engines to use with Together models, while the QVTO and corresponding OCL engines from Eclipse are best suited for the DSL Toolkit. Note that source artifacts may need adjustment when migrating between these engines because these engines have differences in syntax and behavior.
Moving C++ classifiers into/from other classifiers is restricted.
Template specializations are invalidated when changing the name of a specialized template.
Conditional expressions in #if directive are not supported.
Links as comments are limited to dependency links based on the commented simple field declarations of a pointer or object types.
In the generated code, links are represented as pointer type references.
Parser blueprints for custom links recognition are not supported.
There is a side effect related to the correction of unsigned modifier processing. When it appears in a method's formal parameter type, the method signature differs now from the one calculated in the English version. It may invalidate references (such as hyperlinks) to affected methods from the design part of the project created with the English-only version of Together 2006 R2 (build #4021.2).
C++ modeling projects do not function properly if the product is installed in a path containing Japanese characters. Together must be installed in a path that does not contain these characters.
(Bug 4303) Icons on diagram elements that are exported to .emf format have black background rather than transparent backgrounds. This affects generated RTF documentation where the .emf format is used for images by default. Consider switching to .GIF format for images in Preferences when generating RTF documentation.
When you create a Java Modeling project from Java projects that contain cross-project references, restart Together to make clipboard operations (Copy, Cut, and Paste) work correctly with the imported project roots.
Modeling projects cannot reference non-modeling projects: you cannot add a reference to a non-modeling project to the Model Path project property. The existing Java modeling projects that reference Java projects might work incorrectly.
You can create C++ projects referencing each other, but source code elements from referenced projects are not available in the model. You can import design elements only.
Rational Rose cannot import swimlanes from XMI. When activity diagrams with swimlane elements are exported from Together using XMI, the elements do not appear in swimlanes in Rational Rose.
If you use the XMI feature to import UML 1.4 (OMG) or UML 2.0, no design diagrams will be transferred. All the imported elements will be imported and visible in the Model Navigator. You can then include the imported elements into diagrams.
While performing XMI import to UML 1.4 or Java modeling projects, 'Replace for packages' does not work correctly. If you want the existing packages to be replaced on import, you should either delete them before the import process, or rename them and then you can delete old packages and change the names of the newly created packages after the import.
(Bug 2694): Domain Editor: Undo operation after refactoring of model element in the Domain editor is available if you switch selection to the DSL Explorer. However, this will only roll-back external references updates, so you should manually rename the element in the editor after the Undo operation. You can also use the rename refactor action in the Project Explorer instead, where the action can be undone.
(Bug 2702): Model Refactoring: Model Refactor does not support a domain’s URI mapping. So if you have ‘platform:’ URI mapping in your Domain model, move or rename operations can cause unpredictable results. It is best to clear such mappings before a move or rename operation and then restore the mappings after the operation.
(Bug 2935): Domain Editor: To avoid validation warnings during domain model resource refactoring, you should close the Domain Editor (Eclipse bug 205426). To avoid validation warnings on model element refactoring, you should close the affected Diagram Editor.
(Bug 2938): Allow main refactoring even if potential references were found in read-only resources. If Model Refactoring finds potential matches in read-only resources, you are prompted to make these resources writeable to apply the entire change. If a potential change of this type is not selected in the preview, the read-only file will not be modified.
(Bug 5753): DSL Audits and Metrics: Using QVT libraries with non-empty QVT Metamodel Mappings. Errors occurred on executing Audits and Metrics, that used QVT libraries from workspase with non-empty QVT Metamodel Mappings. In same case control for defining OCL expressions in DSL Audits and Metrics Editor can show unsubstantiated errors
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 |
Enabled |
Disabled |
|
| 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 | |
| Team | ||||
| 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 | |
| UML Modeling | Features for UML modeling. | Disabled | Disabled | |
| UML2 Diagramming | UML2 diagramming features. | Disabled | Disabled | |
| UML2 Model Development | UML2 model development features. | Disabled | Disabled |
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.
Online technical publications
The latest versions of Release Notes and product documentation are published at Together Technical Publications page
Visit Borland Technical Support at http://support.borland.com/
Visit Borland at http://www.borland.com/
