Rhapsody version 7.4 readme | IBM Corporation |
© Copyright IBM Corporation 1998,2008.
U.S. Government Users Restricted Rights - Use, duplication, or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
This file contains last-minute product information and updates to Rhapsody 7.4.
It is divided into the following sections:
The Telelogic® Rhapsody Architect™ package is enhanced with the addition of generation and reverse engineering of code enabling software developers to leverage existing code, visualize and generate code for the architecture and structure of the design, and then create documentation synchronized with the design implementation. Rhapsody Architect is able to produce C, C++ or Java code from the model, enabling you to rapidly move from design to implementation. Architect models can be exchanged with Rhapsody Developer™ enabling teams to leverage the animation, test and full behavioral code generation provided with Rhapsody Developer from the same model. Rhapsody Architect is currently available on Microsoft® Windows®.
Telelogic Rhapsody® 7.4 adds the integration of Telelogic Rhapsody TestConductor™ and IBM® Rational® Test RealTime™, enabling software developers to validate and verify their designs in a single environment. This integrated solution allows users to simultaneously perform both model level validation and code level verification, using the same functional test cases for both. Whenever defects are detected, users can easily identify the root cause of the problem by navigating from the defect report back into the model. This allows designers to extend Model Driven Testing to also include code based testing. By testing early and often throughout the design cycle, developers identify both functional and structural defects early in the development process when they are most cost effective to correct. This integration enables the application of Rational Test RealTime structural analysis such as coverage analysis, memory profiling and performance profiling during test case execution with TestConductor. The integration is available for Telelogic Rhapsody in C™ and Telelogic Rhapsody in C++™.
The model coverage reports generated from TestConductor during testing are enhanced to include hyperlinks to the model element for easy navigation to the model element covered or still uncovered during testing.
Leveraging the power of Jazz and Eclipse, Rhapsody 7.4 enables teams to collaborate in real time using the integration with Rational Team Concert (RTC). Users can perform their configuration management through Team Concert enabling them to automatically notify each other of model updates as they occur. Rhapsody’s powerful model differencing and merging capability is automatically triggered to incorporate the changes into the model. Team Concert Integration is supported using the Rhapsody Eclipse Platform Integration.
A user with restrictions on using C++ templates can now develop a Rhapsody application without templates in the generated code or Rhapsody Object Execution Framework (OXF). This enables a user to take advantage of services the Rhapsody Object Execution Framework (OXF) provides for creating multi- threaded reactive applications, event processing for behavioral execution, managing memory, inter-object event communication, operating system abstraction and container support within the Rhapsody model all without using templates.
The Telelogic System Architect® Interface is upgraded to add import of System Architect DoDAF information that is mapped directly to Rhapsody DoDAF elements, in addition to SysML which is currently supported. Moreover, support for import of all artifacts in Telelogic System Architect is supported if the map file supports it.
The Rhapsody 7.4 XMI import is enhanced to handle the proprietary data that is contained in the XMI exported from No Magic, Inc.’s MagicDraw® and Sparx Systems Enterprise Architect tools, enabling users of those products to easily migrate to Rhapsody.
The animation for Telelogic Rhapsody Developer in Ada™ is improved to support ObjectAda and Integrity. In addition, interfaces and timeout animation is now supported, enabling you to discover design errors early in development when they are easiest and least costly to fix.
The Telelogic Rhapsody XMI Toolkit™ and the Telelogic Rhapsody Gateway Add On™ are now available as part of the Rhapsody Eclipse Platform Integration enabling Eclipse users to leverage model interchange between tools using XMI and easily integrate information from requirements capture and Requirements Management tools with the Rhapsody model directly from Eclipse.
The Telelogic Rhapsody 7.4 release adds support for integrations with the following versions of Telelogic products Telelogic DOORS® 9.1, Telelogic SDL Suite™ 6.2, Telelogic Tau® 4.2 and System Architect 11.2. Support is dropped for DOORS 8.2, DOORS 9.0, SDL Suite 6.1, Tau 3.1 and Tau 4.1.
Rhapsody 7.4 now is supported as a host and target platform for RedHat Linux 5.0. Support for RedHat Linux 3.0 is dropped in this release.
Telelogic Rhapsody 7.4 now supports the IBM Java environment enabling users to leverage this version of Java.
Rhapsody 7.4 adds support for MontaVista Linux 5.0 as a target environment. Support for MontaVista Linux 3.0 is dropped.
Additional information regarding the features added to Rhapsody in Ada in this release can be found in the document RiA_ Changes.pdf.
Net-centric Operations Support (Generate/Import WSDL)
If you plan to use Rhapsody's support for net-centric operations, you can find a detailed example in the directory [Rhapsody installation directory]\Samples\SystemSamples\NetCentric.
This directory also contains a small tutorial that demonstrates how this feature can be used.
Rhapsody Plugins
If you plan to write plugins for Rhapsody, a detailed example can be found in the directory [Rhapsody installation directory]\Samples\ExtensibilitySamples\Simple Plug-in.
This directory also contains a document that provides basic instructions for developing plugins for Rhapsody.
For a list of the defects corrected in this release, see the Fixed Defect List, which is available at the support site.
For detailed information on upgrading versions of Rhapsody, see the Upgrade Guide.
64-bit Framework Support
If you want to build applications for 64-bit targets, you must first rebuild the Rhapsody framework libraries. If you are running Rhapsody on a 64-bit host system, then if you rebuild the libraries using the menu option Code > Build Framework, the Rhapsody libraries will be rebuilt such that you will be able to build applications for 64-bit targets. However, if you are running Rhapsody on a 32-bit host system, you will have to rebuild the Rhapsody libraries manually.
The Webify feature will not work with 64-bit applications, out-of-the-box. If you plan to use Webify with 64-bit applications, contact Support in order to receive a version of the WebServices library complied for 64-bit platforms.
Rhapsody's 64-bit support is limited to 64-bit Linux and 64-bit Windows.
Note that Rhapsody can be run on 64-bit systems, but it is still a 32-bit application.
Activity Diagrams
Activity diagrams for packages - can't rename a transition.
You can have multiple activity diagrams or multiple statecharts for a class, but you cannot have both an activity diagram and a statechart for a single class.
As of Rhapsody 7.1.1, activity diagram inheritance is no longer supported.
Adaptors
Rhapsody now supports VxWorks 6.6. If you are using VxWorks 6.5, you should make the following property changes for the appropriate VxWorks6 environment:
- InvokeMake - change 6.6 to 6.5 in property value
- BuildFrameworkCommand - change 6.6 to 6.5 in property value
- IDEInterfaceDLL - value should be changed to $OMROOT/DLLs/Workbench26DebuggerIDE.dll
- GetConnectedRuntimeLibraries - value of the property should be changed to $(OMROOT)/LangCpp/lib/vxWebComponents$(CPU)$(TOOL)$(LIB_EXT), $(OMROOT)/lib/vx65WebServices$(CPU)$(TOOL)$(LIB_EXT)
If you plan to work with VxWorks Workbench, you must manually install the relevant plugin (found under [Rhapsody installation directory]\Eclipse\plugins). In previous versions of Rhapsody, this was done automatically during the Rhapsody installation.
To avoid possible compilation errors when using the GNAT 3.15, Integrity4, Multi3.5, Nucleus, or OseSfk adaptors, install Rhapsody in a directory that does not contain spaces.
Note that the Rhapsody installation automatically adds a directory called "Rhapsody 7.3", i.e., a directory containing a space, under the installation directory you have selected. To prevent the installation from adding this directory, install Rhapsody to a directory whose name begins with the string "Rhapsody", for example, C:\aa\bb\cc\Rhapsody7.3 (not case-sensitive).
Users that work with Solaris 2.9 GNU must rebuild the framework libraries.
If your model uses the QNXNeutrinoMomentics environment, and you are running Rhapsody on Windows Vista, you should install the patch "patch-630SP3-0522-vista.zip".
Animation
When using animation in Rhapsody in C, you cannot invoke an operation that contains an "out" argument.
AutomotiveC Profile
The profile does not support the use of rapid ports.
The profile does not support the use of reactive interfaces.
Rhapsody's S-Function feature cannot be used with the AutomotiveC profile.
When using the AutomotiveC profile, you can't send events across address spaces.
Code cannot be generated for a single class, file, package, or configuration. To generate correct code, you must select Code > Regenerate > [active configuration].
The "respect" mode of roundtripping/code generation cannot be used with the AutomotiveC profile. By default, "Advanced" mode is used.
DMCA (Dynamic Model-Code Associativity) cannot be used with this profile.
In OSEK21 configurations, an Active class can only have a single instance.
AUTOSAR
Due to tool limitation, it is recommended that you work in a bottom-up fashion. For example, a ComponenPrototype should be defined only after the AtomicSoftwareComponentType on which it is based has been defined. The type of the prototype must be specified immediately after defining the prototype.
Import/Export from/to AUTOSAR XML format does not work on Windows Vista.
After generating code with Rhapsody's customizable CG feature (C_CG::Configuration::CodeGeneratorTool = Customizable), you can't import AUTOSAR XML until you close and reopen Rhapsody.
Build Framework
The "Build Framework" menu item in the Code menu works only for Linux, Cygwin, and Microsoft environments. For all other environments, the menu item is grayed-out.
Build Window
Errors and warnings may be displayed as info messages.
The ability to jump from an error message to the relevant code location has only been tested with English-language versions of compilers. If you encounter problems with this feature when using compilers that display errors in languages other than English, try modifying the values of the properties ParseErrorMessage, ParseSeverityError, and ParseSeverityWarning.
Build with Dependencies
When you use the Build ...with Dependencies option, Rhapsody does not allow you to perform any action until the build is completed.
C Ports and Interfaces
Ports with multiplicity greater than 1 are not yet supported.
Callback API
Callback events will not appear in the list of "helper triggers" in the Rhapsody Helpers dialog (Tools > Customize, from main menu).
CM - Batch Mode
Batch mode CM may not work correctly if there are spaces in the model path.
Code Generation (Integrity)
In Rhapsody in C, for the Integrity and Integrity5 environments, the file Integrity5.ld is not copied from ..\Share\MakeTmpl to the output folder automatically. This file should be copied manually.
Code Respect
When code is generated after roundtripping, there may be some differences compared to the original code.
Auto-generated #includes, such as <oxf/oxf.h>, cannot be removed.
Addition/ordering of friend dependencies is not supported.
Roundtripping ignores changes to language types in classes (deletion, modification, reordering). The relevant code is always generated at the beginning of the class.
If #ifdef conditionals have been brought into the model via reverse engineering:
- Roundtripping cannot handle changes within the #ifdef blocks.
- Roundtripping cannot handle changes made to the #define directives that define the conditions for the #ifdef blocks.
In such cases, if you have to make changes to the #ifdef-related code, you must make the changes in the model and then regenerate the code.
Configuration Management State Awareness
In general, the CM status display is refreshed only when the user initiates a refresh. So, for example, the CM status display is not refreshed when the user sets a different project to be the active project.
Cygwin Adaptor
If you are using Cygwin and encounter problems compiling Rhapsody models, try rebuilding the framework libraries for Cygwin. This can now be done by selecting "Build Framework" from the Code menu.
Eclipse - Refactoring
The following limitations apply to Rhapsody's ability to roundtrip changes made to code using the refactoring options offered by Eclipse:
- If you rename a class (or class member) in Eclipse and use the option of updating references to the class (or member) inside comments, changes will also be made to the Rhapsody-generated annotations, and this will lead to roundtripping problems.
- If you use Eclipse's option to make indentation and formatting changes, only the formatting changes made inside operation bodies will be picked up by Rhapsody.
- Roundtripping does not support the creation of new packages. So if you add a new directory to a project and add classes to the directory, these classes will not be roundtripped into the model.
- In Java code, Rhapsody will not pick up changes made to the order of members within a class.
- In Java code, Rhapsody will not pick up changes made to the order of import statements.
Eclipse CDT Debugger Integration
It is known that the Eclipse debugger may appear to be sluggish.
If you disable the Eclipse debugger's default launch setting option "Stop on startup at main", it will break the animation synchronization between Rhapsody and Eclipse debugger (due to Eclipse bug).
Eclipse Platform Integration
Rhapsody does not support Eclipse's Window > New Window and Window > New Editor options.
In order to prevent compilation errors stemming from a bug in Cygwin's make.exe (version 3.81), Rhapsody includes a property called CG::Cygwin::ConvertToCygwinPathInIDE which is set to True by default. This converts standard Windows paths to paths that Cygwin can handle. The downside of this workaround is that certain navigation features in the Eclipse GUI, such as jumping to included files, will not work properly. If you wish to use these navigation features and are not concerned about compilation errors, you can set the value of the property ConvertToCygwinPathInIDE to False.
When you use the File > Switch Workspace option in Eclipse, you may receive an error message with regard to your Rhapsody license. To prevent this problem, it is recommended that you switch workspaces by manually closing and reopening Eclipse and then selecting the new workspace.
When you use the File > Switch Workspace option in Eclipse, you may receive a message indicating that the animation port is still open. To prevent this problem, it is recommended that you switch workspaces by manually closing and reopening Eclipse and then selecting the new workspace.
Eclipse Project Import
Only managed C/C++ projects are imported into Rhapsody.
If user wants to use animation or trace instrumentation with imported models, they must update- the Rhapsody-generated main function manually.
Build process will still be Eclipse's responsibility: Not all Eclipse project build settings are imported into the Rhapsody Eclipse configuration. In order to perform the build with the original build settings, the "Build in IDE" option (in Rhapsody Eclipse configuration) is selected by default.
Events as Types
If you use an event as the type for a global variable, compilation errors will result.
Flowcharts with Code Generation
In previous versions of Rhapsody, you could add a flowchart anywhere you could add an activity diagram. Now, you can only add a flowchart at the operation level.
Graphics - General
If you are using Windows XP SP2, installing the following update from Microsoft can help prevent system resource leaks when performing graphic-intensive operations in Rhapsody, such as generating reports for large models - Update for Windows XP (KB319740):
http://www.microsoft.com/downloads/details.aspx?FamilyId=9B5EDFC8-A4BB-4080-9063-6518166E2DAB&displaylang=en&displaylang=en
Installation - Rhapsody in Ada
If you have selected the GNAT VxWorks compiler during installation, Rhapsody will display an error message that it cannot find GNATVx.
Installation on Citrix Server
The single-file .msi installation may fail when installing on Citrix servers. Microsoft has provided a hotfix to solve this problem for Windows Server 2003, and also provides a workaround for this problem. All of the details can be found at http://support.microsoft.com/kb/925336
Alternatively, you can install Rhapsody from the DVD, which contains a multiple-file msi-based installation.
Installation on Vista
To ensure proper registration of Rhapsody's COM interface, Rhapsody must be installed under the Administrator account. A simple way to do this is to right-click the Command Prompt item in the Start menu, and select "Run as administrator" from the context menu. Then, just change to the directory containing the .msi file and run it.
On Vista, the license path is stored in the registry under HKEY_CURRENT_USER\FlexLm (and not under HKEY_LOCAL_MACHINE as on Windows XP).
Panel Diagrams
This feature is not available when using Rhapsody within Eclipse.
If you use panel diagrams with the FunctionalC profile, the various controls can only be used to monitor data. You cannot use them to input data.
ReporterPLUS
ReporterPLUS is supported on Microsoft® Office 2000 and 2002. It cannot be used with Word 97 or 98.
Rhapsody API
This feature is not available in Rhapsody Architect.
Rhapsody Gateway™
Gateway cannot be used with Rhapsody Architect.
In certain situations, if you try to delete or replace a DOORS project in Gateway's Edit Project dialog, a message will be displayed indicating that the file is locked by another user. If you encounter this message, close and reopen Gateway and then open the Edit Project dialog again.
If your project is based on the one of the AUTOSAR profiles, you will not see Gateway appear as an option in the context menu for the project. To overcome this problem, open the rhapsody.ini file and locate the settings for Gateway in the [Helpers] section. Modify the applicableTo setting so that it includes the following: AUTOSAR_20, AUTOSAR_21.
Rhapsody in Ada
The new Ada95 framework (NewFWK95) cannot be used to generate code for the following environments: INTEGRITY5 and OBJECTADA. To change the framework used, change the value of the property Component::Ada_CG::UseAdaFramework to either FWK95 or FWK83.
The Build tab of the output window does not work with Ada compilers. In RiA, all messages will be presented via the Log tab.
Rhapsody in Java
Roundtripping/Reverse Engineering are not supported for static import of individual class members.
There is no support for Java annotations in roundtripping.
Java code generated by Rhapsody will not include annotations that have been applied to the following types of elements: constructors, destructors, association ends.
If you use the Edit > Format option in Eclipse, then roundtripping of changes to Java code may not work correctly. This is due to spaces being added to the annotations used by Rhapsody. To prevent such problems, define a formatting profile where the "Tab policy" is set to "spaces only", and the "Enable comment formatting" option is not selected.
SDL Integration
This feature is not available in Rhapsody in C.
The code generation scope can contain only one SDLBlock.
SDL Signal arguments will not contain "call by reference" arguments (char*, etc.)
Sequence Diagrams
In animated sequence diagrams in Rhapsody in C, return values are not displayed for triggered operations.
Simulink Integration
On VxWorks, there is not support for Simulink integration if the Simulink-generated files are located in a path that contains spaces.
Only primitive Simulink types can be used as the input to / output from S-functions created in Rhapsody.
Statemate Integration
A Statemate model can only be represented once in a Rhapsody model, i.e., there can only be one Statemate block representing the model. You can, however, have a number of Statemate blocks representing a number of different Statemate models.
System Designer
In Rhapsody System Designer, Cygwin and Microsoft are the only targets supported.
Webify in RiJ
When using the Webify feature in Rhapsody in Java, you cannot customize the web interface.
The features listed below are not available when using the Rhapsody Eclipse Platform Integration Plug-In. In addition, some other Rhapsody features may not be available when using this plugin.
Add-ons
Such as Gateway, TestConductor, and XMI Import/Export
Domain-specific Profiles
Such as DoDAF, MoDAF, and SysML
The following limitations apply only to the Linux version of Rhapsody
Back and Forward Navigation Buttons
This feature does not work in the Linux version.
Code Generation
Modifying the <lang>_CG::<environment>::PathDelimiter property to backslash is not supported on Linux systems because the operating system does not recognize paths that contain backslashes instead of forward slashes.
COM Development
This feature is not included in the Linux version.
Configuration Management / SCC
This feature is not included in the Linux version.
CORBA Development
This feature is not included in the Linux version.
Customizable Code Generation
This feature is not included in the Linux version.
Customizable Static Checks
This feature is not included in the Linux version.
DOORS Interface
The following features are not available in the Linux version of Rhapsody:
- Export diagram graphics from Rhapsody to DOORS
- Navigate from DOORS to Rhapsody
Fixed-point variables
This feature is not included in the Linux version.
Graphic Editor
On Linux systems, the Alt key does not work for the “Move/Stretch without contained” command. The possible workarounds are as follows:
- Use Edit > Move/Stretch without contained.
- Left-click the element you want to move or scale, but do not move the mouse. Press the Alt key, then move the mouse.
Helper Applications
This feature is not included in the Linux version.
Import from Rose
This feature is not included in the Linux version.
Internal Reporting Tool (Report on model)
If you use Report on Model with the property General::Graphics::ExportedDiagramScale set to "UsePrintLayout", then you must set the property General::Graphics::RotateDiagramOnExport to "No".
Miscellaneous
If you work with the Exceed X-server (which is not officially supported by
Rhapsody), a small, floating toolbar appears when invoking Rhapsody. You
must close this toolbar (using the x button) to be able to work with the Rhapsody menus.
It is not possible to invoke console applications without a GUI, such as vi, from Rhapsody helpers, or to use them as external editors. A workaround is to call xterm -e in the beginning of the command.
Populate Diagram
The Preferred Layout Style options are disabled in the Populate Diagram dialog box. Rhapsody automatically uses the default style.
Print Diagrams
The header and footer text, as well as graphics, may be clipped if they are placed on the top and bottom page break lines. To overcome the problem with the graphics:
- Set your diagram to “view page breaks” and try to avoid placing shapes and
lines on the page boundaries.
- Print using FitToOnePage and avoid placing graphics at the very top of the
page.
ReporterPLUS
On Linux, ReporterPLUS cannot generate Powerpoint and Word reports.
On Linux, ReporterPLUS does not include a table of contents in RTF reports that are generated.
If you get an error when generating a report from ReporterPLUS while Rhapsody is not running, it is recommended that you run and exit Rhapsody, and try generating the report again.
On Red Hat 5.0, reports generated with ReporterPLUS may not always be opened automatically after they have been generated. In such cases, you will have to open the report manually.
Rhapsody API
The Callback API is not included in the Linux version.
Rhapsody ATG
This feature is not included in the Linux version.
Rhapsody Gateway™
On Linux, the diagram preview feature is not available. When you select a diagram, the preview window will not be opened.
Rhapsody in Ada
This feature is not included in the Linux version.
Rhapsody Plugins
This feature is not included in the Linux version.
Rhapsody TestConductor
Installation of TestConductor on Linux requires uudecode.
RTOSes
Only the following operating systems are supported in the Linux version:
MontaVista 5.0
Linux Red Hat® (Enterprise Linux®) 4.0
Linux Red Hat® (Enterprise Linux®) 5.0
Integrity 5.0.7 MultiNativeLinux X86 4.2.3
Rules Composer and Player
This feature is not included in the Linux version.
Running Applications Instrumented for Tracing
When you run an application instrumented for tracing, you must press Enter twice after each command. However, if you run the same application from the command prompt, you can simply press Enter once.
Simulink Integration
This feature is not included in the Linux version.
Split Diagrams During Export
This feature is not included in the Linux version.
Statemate Integration
This feature is not included in the Linux version.
Systems Designer and Systems Architect
These editions are not available for Linux.
TLB Importer
This feature is not included in the Linux version.
VBA
This feature is not included in the Linux version.
Welcome Screen
On certain versions of Linux, the home page may contain only the New Project and Open Project links.
XMI Import/Export
Export to 1.3 format does not work on Linux.
This version of Rhapsody runs on the following host platforms:
Citrix 4.0 (hosted on Windows Server 2003)
Red Hat Enterprise Linux 4.0, 5.0
Windows Vista
Windows XP (SP1/SP2)
CPU
Pentium II, 800MHz
Disk Space
~750 MB (full installation)
RAM
256 MB minimum, 512 MB recommended
The following software is required to run Rhapsody:
License management software
FlexNet 11.4
Network protocol
All versions of Rhapsody require TCP/IP and an IPX/SPX-compatible network
protocol. Rhapsody uses the TCP/IP protocol for design-level debugging. See
Solution 325 in the Customer Solution Center for more information.
RiJ (for compiling and running code)
IBM Java 1.5
or
Version 1.4.2 or 1.5 of the Java 2 Platform, Standard Edition Software
Development Kit (J2SE™ SDK), formerly known as the Java Development
Kit (JDK), or Java SE 6.
Version 1.5 or Java SE 6 are required to use the following features:
- Eclipse integration
- Java version of the Rhapsody API
- XMI import/export
- AUTOSAR import/export
Software needed if CORBA support is required (RiC++)
An ORB
An IDL compiler
CORBA header files
CORBA libraries
Rhapsody support for different real-time operating systems (RTOSes) is generic and can be customized to most existing systems.
The supported Rhapsody capabilities, platforms, and third-party product integrations have undergone formal testing. Although not explicitly listed or formally tested, other integrations are available. Contact your Telelogic sales representative or Customer Support with specific inquiries.
Rhapsody provides pre-customized support for the RTOSes shown below. Pre-customized support in Rhapsody means that a set of preconfigured code generation properties are provided for the environment:
- Precompiled versions of the relevant framework libraries are provided.
- The precompiled framework libraries have been fully tested.
RTOS support is available only in the Developer package. The Designer package includes makefiles for building the framework on Windows only.
INTEGRITY® (Green Hills)
4.0.8 - Windows version of Rhapsody - C, C++, Ada
5.0.4 - Windows version of Rhapsody - C, C++, Ada
5.0.7 - Linux version of Rhapsody - C and C++ only
For the latest version, contact ssmdsupport@telelogic.com.
The Release version of Integrity was not tested. You can modify the framework and application build files for use in Release mode.
Itron (MicroItron)
4.0 - Rhapsody in C++
For the latest version, contact ssmdsupport@telelogic.com.
Linux® (MontaVista®)
Professional Edition 5.0 - Rhapsody in C and C++ - only available in Linux version of Rhapsody
LynxOS® (LynuxWorks™)
4.0 - Rhapsody in C++
For the latest version, contact ssmdsupport@telelogic.com.
Nucleus® (Mentor Graphics®)
1.13.7 - Rhapsody in C and C++
ObjectAda® (Aonix®)
V7.2 (Raven™/PowerPC) - Ada
OSE Delta (Enea)
4.5 - Rhapsody in C++
Phar Lap Embedded ToolSuite
(ETS™) (VenturCom®)
Rhapsody in C++
For the latest version, contact ssmdsupport@telelogic.com.
QNX® Neutrino® (QNX)
Neutrino 6.3.2 (QNX Momentics 6.3.0 Service Pack 3) - Rhapsody in C++
Red Hat® (Enterprise Linux®)
4.0, 5.0 - Rhapsody in C++
RTX™ (VenturCom®)
5.5 - Rhapsody in C++
For the latest version, contact ssmdsupport@telelogic.com.
Solaris™ (Sun™)
2.8, 2.9 - Rhapsody in C and C++
Note that Solaris targets are not supported by Rhapsody in Ada.
ThreadX® (Express Logic)
Rhapsody in C and C++
For the latest version, contact ssmdsupport@telelogic.com.
VxWorks® (WindRiver®)
5.5, 6.5, 6.6 - Rhapsody in C and C++
Windows® Embedded CE (Microsoft®)
6.0 - Rhapsody in C++
Rhapsody support for different integrated development environments (IDEs) is generic and can be customized to most existing environments.
The supported Rhapsody capabilities, platforms, and third-party product integrations have undergone formal testing. Although not explicitly listed or formally tested, other integrations are available. Contact your Telelogic sales representative or Customer Support with specific inquiries.
Eclipse
3.3 (with CDT 4.0, JDT 1.0.0)
MULTI® (Green Hills)
3.5 - Windows version of Rhapsody - C++ and Ada only
4.0.5 - Windows version of Rhapsody - C, C++ and Ada
4.2.3 - Linux version of Rhapsody - C and C++ only
For the latest version, contact ssmdsupport@telelogic.com.
Tornado® (Wind River)
2.2 (VxWorks 5.5) - C, C++
Workbench (Wind River)
2.6 (VxWorks 6.5), 3.0 (VxWorks 6.6) - C, C++
Note: In terms of integration with Rhapsody, for Workbench 2.6, only workflow integration is supported (not the Eclipse Platform Integration feature).
When using compiler versions other than the ones listed in the following table, you must recompile the OXF libraries. See the RTOS Adapter Guide for details.
Cygwin
2.427 - C, C++
Diab Data
4.3f (Nucleus) - Rhapsody in C++ and C
5.0.3 (OSE Delta) - Rhapsody in C++
Forte
6.1
Rhapsody in C++ and J on Solaris
To properly build an application with the Sun Forte 6.1 compiler, the following patches must be installed with the compiler: 107355-05, 107357-09, 107311-10, 107295-01, and 107289-05.
gcc
2.95.3 (Solaris)
2.95.3 (QNX Neutrino) - Rhapsody in C++ on Windows
2.9.6 (Tornado 2.2)
3.4.3 (Red Hat EL4)
3.4.4 (Cygwin) - Rhapsody in C++ and J
GNAT
gnatwin-3.15p - Rhapsody in Ada
Java 2 SDK
1.4.2, 1.5, or Java SE 6
Rhapsody in Ada and J
To use the Eclipse integration features, version 1.5 or higher is required.
MULTI 2000
MultiWin32 => Windows target + Multi 3.5 Standard (ANSI/ISO) C++ compiler
INTEGRITY => INTEGRITY 4.0 target + INTEGRITY 4.0 Standard (ANSI/ISO) C++ cross-compiler (running on Windows and generating binaries for INTEGRITY)
- Rhapsody in C++
AdaMULTI 2000 for native x86
- Rhapsody in Ada
ObjectAda (Aonix)
7.22 - Rhapsody in Ada only
Visual C++ Studio (Microsoft)
6.0 SP-3
Visual Studio .NET (Microsoft)
Visual Studio .NET 2005
The Microsoft Visual Studio .NET compiler is supported; however, .NET features are not supported.
DOORS®
Rhapsody DOORS Interface supports: 8.3, 9.1
Rhapsody Gateway supports: 8.3, 9.1
SDL Suite™
6.2
Statemate®
4.3
Synergy™
6.5 SP2
System Architect
11.2
Tau®
4.2
Internet Explorer (Microsoft)
5.5 or higher
MATLAB, Simulink (The MathWorks)
Matlab 7.1 with Simulink 6.3, Matlab 7.3 with Simulink 6.5, or Matlab 7.5 with Simulink 7.0, with Real-Time Workshop® Embedded Coder component.
Microsoft® Office
ReporterPLUS is supported on Microsoft® Office 2000 and 2002.
Mozilla
1.4.3 - supported in Linux version of Rhapsody only
PVCS Dimensions™ (Serena)
9.1 - supported in Windows version of Rhapsody only
Rational Rose (IBM®)
Rose® 2003 - Rhapsody in C++ and Rhapsody in J
Rational® ClearCase® (IBM®)
4.2
ClearCase patch number p4.0-5 is required on Solaris 2.8.
6.0
7.0
Tao
1.4
Teamcenter Systems Engineering (UGS)
7.1
Visual Basic®/VBA (Microsoft)
6.3
Webify Toolkit is supported for the following environments:
Integrity mbx800
Integrity5 mbx800, rpx-cllf
Integrity5ESTL mbx800, rpx-cllf
IntegrityESTL mbx800
Linux Red Hat x86
Microsoft Windows
Microsoft Windows CE 4.2 x86
MultiWin32
Nucleus PowerPC
QNX Arm
QNX Mips
QNX PowerPC
QNX Windows
QNX x86
Sun Solaris
VxWorks PENTIUM - VxWorks 5.5
VxWorks PENTIUM_RTP_diab - VxWorks 6.5
VxWorks PENTIUM_RTP_gnu - VxWorks 6.5
VxWorks PENTIUMdiab - VxWorks 6.5
VxWorks PENTIUMgnu - VxWorks 6.5
VxWorks PPC32_RTP_diab - VxWorks 6.5
VxWorks PPC32_RTP_gnu - VxWorks 6.5
VxWorks PPC32diab - VxWorks 6.5
VxWorks PPC32gnu - VxWorks 6.5
VxWorks PPC403 - VxWorks 5.5
VxWorks PPC403diab - VxWorks 6.5
VxWorks PPC403gnu - VxWorks 6.5
VxWorks PPC603 - VxWorks 5.5
VxWorks PPC603diab - VxWorks 6.5
VxWorks PPC603gnu - VxWorks 6.5
VxWorks PPC604 - VxWorks 5.5
VxWorks PPC604diab - VxWorks 6.5
VxWorks PPC604gnu - VxWorks 6.5
VxWorks PPC860 - VxWorks 5.5
VxWorks SIMNT - VxWorks 5.5
VxWorks SIMNTdiab - VxWorks 6.5
VxWorks SIMNTgnu - VxWorks 6.5
VxWorks SIMPENTIUM_RTP_diab - VxWorks 6.5
VxWorks SIMPENTIUM_RTP_gnu - VxWorks 6.5
Support and information for Telelogic products is currently being transitioned from the Telelogic Support site to the IBM Rational Software Support site. During this transition phase, your product support location depends on your customer history.
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send written license inquiries to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send written inquiries to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, JapanThe following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions. Therefore, this statement may not apply to you.This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:
Intellectual Property Dept. for Rational Software
IBM Corporation
1 Rogers Street
Cambridge, Massachusetts 02142
U.S.A.Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.
The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.
Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.
If you are viewing this information softcopy, the photographs and color illustrations may not appear.
Trademarks
IBM, the IBM logo, ibm.com, Telelogic, Telelogic Synergy, and Telelogic Change are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. These and other IBM trademarked terms are marked on their first occurrence in this information with the appropriate symbol (® or ™), indicating US registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at www.ibm.com/legal/copytrade.html.
Adobe, the Adobe logo, PostScript and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
Java and all Java-based trademarks and logos are registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Other company, product or service names mentioned may be trademarks or service marks of others.