IBM Rational Rhapsody version 7.5 readme | IBM Corporation |
© Copyright IBM Corporation 1998, 2009.
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 IBM Rational Rhapsody 7.5.
It is divided into the following sections:
New code visualization workflow
Rational Rhapsody 7.5 provides a new code development workflow for C and C++ that promotes a “code centric” approach where the code is the primary source of information and the model reflects the code with no regeneration of code. This makes it easier for teams to make changes to their code and visualize the code for documentation and better understanding of the architecture and behavior. There are two modes: code visualization and code update. With code visualization you are able to evolve the external code in parallel with its visualization in the model. This workflow is designed for the user who wants to work in the code only but also wants documentation. The model, including diagrams, updates continuously to reflect the changes in the code but no code generation is performed. Code update also updates the model with changes in the code but the user can also edit the model and generate code with minimal intervention in the code. For example, indentation of the code is preserved after generation. Code update is designed for the user who primarily works in code but also wants the flexibility to modify the model. A new set of settings for code centric development enables these capabilities which are automatically added for the active component after reverse engineering code.
Animation of legacy code
The ability to add animation to legacy code is improved for visual debugging of existing code for early defect identification and visualization of design behavior. You are able to take existing code and add animation with minimal intervention in the code. After completing animation you can regenerate code without the animation instrumentation in the code.
Sequence diagram based animation
Rational Rhapsody 7.5 adds the ability to specify the scope of animation based on a sequence diagram to quickly limit the scope of animation to the design elements of current interest. This is helpful after importing existing code by simplifying the operation of limiting animation to a subset of the code. The operation is performed by choosing Animate from the right click context menu of a sequence diagram.
Flowchart Creation from code
Originally released in the Telelogic Rhapsody 7.4.0.1 release, Rational Rhapsody 7.5 improves the visualization of operation bodies for C and C++ as flowcharts, helping to assist you in gaining a better understanding of code behavior. Examples of the constructs recognized in the Rational Rhapsody design environment are if-then-else, switch, while loops, do while loops, for loops plus nesting of these constructs. To help visualize the code behavior when reverse engineering code, you can specify that flowcharts for operations are visualized.
Integration with Microsoft Visual Studio
Rational Rhapsody 7.5 provides a tighter integration with Microsoft Visual Studio 2008 simplifying and automating the integration between the two. A Rational Rhapsody toolbar is added into Visual Studio enabling you to navigate to the Rational Rhapsody model directly from the code in Visual Studio. You can now create a Visual Studio project that is connected to the Rational Rhapsody configuration and the integration updates include paths and define symbols directly into the Visual Studio project. The code in Visual Studio and Rational Rhapsody model remain synchronized with one another through dynamic model code associativity. For example, you are able to change the name of a class within Visual Studio and that operation is recognized within the Rational Rhapsody model. If files are added in Rational Rhapsody then they appear in Visual Studio. Existing Visual Studio projects can be exported to Rational Rhapsody and brought into the Rational Rhapsody model through reverse engineering.
Makefile guided reverse engineering
Developers and engineers know that a makefile provides a listing of the required source code and important settings such as defines and include paths that are essential in building the code. To assist in aiding this style of workflow, Telelogic Rhapsody 7.4.0.1 added the ability to parse the makefile for C and C++ code and imports settings discovered in the makefile. In addition, the Rational Rhapsody model-driven development (MDD) environment brings the discovered settings into the modeling environment, helping to make the reverse engineering set-up and subsequent building of Rational Rhapsody-generated code easier.
Roundtripping of language types
It is now possible to roundtrip types specified by C++ code inside classes to keep changes in the code synchronized with the model.
Refactor/Rename within user code
Rational Rhapsody now supports refactoring through renaming of model elements with the added ability to auto-replace all chosen user code references by selecting the Refactor->Rename option from the context menu. Code references in operation bodies, action on entry, action on exit, reaction in state, overridden properties and configuration initialization are replaceable. This improves the consistency between the model element and the code references and helps to manage changes easier.
Requirements generated into code
During code generation for C, C++, and Java, Rational Rhapsody can now generate comments into the code containing the requirement information for the element to provide traceability from requirements to implementation. Control of generation of the requirements is performed with the “Include Requirements as Comments in Code” setting of the code generation configuration or by adding the $Requirements keyword to the DescriptionTemplate property of the element that you want requirements information generated. The requirement comments template is specified in the language specific property <language>_CG::Requirement::DescriptionTemplate, for example, CPP_CG::Requirement::DescriptionTemplate.
Optimization of timeout code
The performance and size of timeout code for C++ code generation is improved by reducing the number of pointers in the timeout code. (Available in Telelogic Rhapsody 7.4.0.1 release)
Generate directory for specific package
It is now possible for you to control generation of a directory for each specific package instead of for all packages in the component for C, C++ and Java providing you with more control over code generation.
Improved C++ templates generation
The generation of C++ template is improved in Rational Rhapsody 7.5 by generating only .h files to optimize the generated code, supporting execution of ports on template classes to help more complex designs, and providing an enhanced user interface to select a template parameter value to help improve usability.
Specifying classes as C++ structs
C++ code generation is improved to allow generation of a C++ class as a “struct”, helping to benefit your development process with more flexible code generation. (Available starting in Telelogic Rhapsody 7.4.0.1)
Ada development improvements
Ada developers are offered behavioral and multi interface ports, enabling you to build Ada designs that leverage these constructs. The IBM Rational Rhapsody environment helps with this by assisting you with the ability to create links between ports with the correct interfaces. To achieve this, multiple contracts use Ada 2005, and Ravenscar active classes are now supported. In addition improvements are made in the reverse engineering of Ada code to better leverage existing design developed for Ada.
Rhapsody RulesComposer Improvements
The Rational Rhapsody Developer RulesComposer Add On™ adds ATL integration (open source transformation engine) provided by Eclipse plug-ins. Additionally, a debugger is added helping you when you need to set breakpoints and stepping through rules templates to assist in debugging the rules surrounding your development project. (Available starting Telelogic Rhapsody 7.4.0.1)
Improved support for resource constrained targets
Rational Rhapsody 7.5 improves the MicroC profile and MicroC framework (MXF), for targeting resource constrained targets such as micro controllers by not allocating dynamic memory, minimizing image footprint and providing configuration settings for customization. The MicroC profile and MXF helps you achieve this with:
Static compile time initialization for data structures
Segmented memory support with the ability to locate parts in ROM
Optimized code for direct flow ports and direct relations optimizes initialization and amount code generated for these constructs
Initialization of user attributes per instance
Static initialization with File and Singleton & OXF support
Segmented memory capability with “pragma” definition plus access macros
Target monitoring for constrained target
Embedded targets often may be resource constrained and it is difficult to allocate resources for debugging the application on the target. Rational Rhapsody 7.5 helps to improve debugging on targets with the addition of target monitoring for resource constrained targets when using the MicroC framework. You are able to monitor classes or instances using sequence diagrams to visualize the behavior of the running executable. Communication for RS-232 and TCP/IP is supported but it is possible to customize for other implementations.
Optimized port implementation
The MicroC profile provides new stereotypes for ports without contract that optimize the implementation of ports code for more efficient code. The new stereotypes are InEventPort and OutEventPort. To send an event using these stereotyped ports use the macro RiCGEN_EV_PORT(PORT,EVENT). This new implementation may also allocate the data related to the ports to be in a const memory segment to further improve performance using the property C_CG::Configuration::EnableSegmentedMemory.
Network Ports
An icon for network ports is available on the architecture diagram. inNetworkPort and outNetworkPort types make it easier to bind a data-element on a flow-port to an external bus or other I/O signal.
Enhanced Rational Statemate Blocks
The interface with Rational Statemate is improved to allow sending and receiving of Rational Rhapsody events to the Statemate block. An event received by a Statemate block triggers the corresponding Statemate event according to the binding specified. A Statemate event generated inside the Statemate block is translated into a Rhapsody event which is sent to the object connected to the Statemate blocks ports. This feature is supported with Rational Statemate 4.6 and is available for C code as part of the Rational Rhapsody Interfaces Add-on.
Support for AUTOSAR 3.1 (available Telelogic Rhapsody 7.4.0.1)
Rational Rhapsody adds a profile that helps support your AUTOSAR version 3.1 projects, in addition to AUTOSAR 2.1.2 projects. This new profile helps you benefit from the new features found in AUTOSAR 3.1, including new kinds of component types and the splitting and merging of data elements using delegation connectors.
Activity Diagrams improvements
Rhapsody 7.5 improves activity diagrams to model more elements and improve the overall usability of the activity diagram editor helping you to model behavior using activity diagrams. The improvements include
Activity Final from Termination State
Decision Node from Condition Connector
Merge node from Junction Connector
Multicast of ports and flowports
Rational Rhapsody 7.5 now provides the ability to multicast events and data from a single port or flowport to multiple ports or flowports making it easier to model, generate and execute the broadcasting of events and data.
Tabular Statecharts
The ability to view a statechart as a table is provided to enable you to represent state behavior that may be too complicated as a diagram in a tabular form. The tabular view can make it easier to identify missing elements. You are able to edit the statechart to add and delete transitions and events. It is possible to switch between diagram and tabular view of the statechart.
Tables and Matrix improvements
Rational Rhapsody 7.5 provides many improvements to tables and matrices to make it easier to convey model information in a tabular format and modify information directly within tables and matrices:
UPDM profile
The UPDM (Unified profile for DoDAF and MODAF) provides a single modeling standard that supports both the USA Department of Defense Architecture Framework (DoDAF) and the UK Ministry of Defence Architecture Framework (MODAF). With the release of Rational Rhapsody 7.5 support is provided for both “levels” of compliance for UPDM. Level 0, based on UML and level 1 based around SysML. The Rational Rhapsody UPDM support provides:
The UPDM support is available in the IBM® Rational® Rhapsody® for DoDAF, MODAF, and UPDM Add On
Support for importing all definitions for IBM Rational System Architect
Companies developing DoDAF products can now transition to lower levels of systems engineering by migrating information from Rational System Architect in DoDAF to DoDAF artifacts in Rational Rhapsody to avoid consistency errors between DoDAF operational and systems views, even across company boundaries.
Process automation for IBM Rational Harmony
Improvements to the Rational Harmony wizards are added that address issues with the current features and adds new capabilities that further help to automate and accelerate the development process: New features include:
MARTE Profile
Rational Rhapsody 7.5 adds a profile for the support of the OMG Modeling and Analysis of Real-Time Embedded Systems (MARTE) profile enabling teams to model concepts of real time systems through stereotypes to annotate models for support by analysis tools. Software engineers can model real time embedded aspects such as concurrency, allocations, time, etc. Annotations for schedulabilty analysis can provide you the ability to predict if the design will meet timing constraints and validate temporal correctness. Annotations for performance analysis enable you to predict if a system with no deterministic behavior can provide adequate performance, usually defined by statistical measures. It is also possible to model hardware and software resources to perform trade off analysis between implementing in hardware or software. The MARTE profile replaces the Schedulability, Performance and Time (SPT) profile.
Save model as Rational Rhapsody 7.4
Starting with Rational Rhapsody 7.5 it is possible to save a model in a previous version of Rational Rhapsody making it easier to migrate to a new version and exchange information among team members that have not upgraded. If differences occur between the new and older release elements the newer release elements are replaced with older versions. Rational Rhapsody 7.5 can save a model for Rhapsody 7.4.
Apply profile support
Profiles provide a powerful means to customize your modeling environment. Rational Rhapsody 7.5 allows you to control whether to apply a profile globally or to specific packages or components enabling the usage of multiple profiles in one model for maximum flexibility.
Improved tag value support
Rational Rhapsody 7.5 provides the ability to type tags by stereotypes and meta-classes in addition to Boolean, string, integer, user defined datatype and terms providing the ability to model more complex designs. In addition, it is now possible to specify a list of values for tags with a multiplicity greater than one enabling more complex information to be modeled.
Support for class variants in C++ (Classes) and C (Files)
For companies modeling a family of products or a product line, variation points provide a means to differentiate different products within the model. Each product can be generated later by selecting which variant to implement for each variation point.
Additional features added within Eclipse integration
The Rational Rhapsody integration with Eclipse included with Rational Rhapsody Developer and Rational Rhapsody Architect for Software is improved with the addition of the following features for the Eclipse integration:
Improved editing multiple elements
Often it is desired to change the features of multiple elements at the same time. It is now possible to open the features dialog for editing multiple elements at once for attributes, types, dependencies, packages, classes and operations. You should select multiple items of the same metaclass to enable this feature, for example several attributes. If multiple metaclasses are selected a generic features dialog is opened where the stereotype can be changed.
Improved Unified Context Menu
Rational Rhapsody 7.5 organizes the context menus to make it easier to find desired operations in the browser or diagrams. The operations are organized as open, new, edit, navigation, element specific, configuration management, actions, context specific, and helpers/add-ons. The new operation is better organized to reduce the size of the menu and group similar operations together.
New Diagram Drawing Toolbar
Rational Rhapsody 7.5 provides a new drawing toolbar that includes the diagram tools, common operations and free shapes. The new toolbar supports floating, docking and a label/non label mode. The mode, state and position of the toolbar is kept and restored on application launch.
Gradient graphics and toolbars
The graphics and toolbars are improved with gradient background for a better look and feel. This is the default mode and is enabled or disabled from the View menu.
Full screen mode
You are now able to enter full screen mode for diagrams that shows only a working area, corresponding diagram toolbar and browser providing more screen area for diagram drawing. The application toolbars are hidden and application menus are in auto-hide mode at the top of the window. This mode is activated from the View menu or with “alt+shift+enter” keys.
Improved Favorite organization
Navigating to information quickly is important and the favorites window is improved to provide the ability to add and remove folders to organize favorites for faster access. In addition it is possible to add a favorite simply by dragging it and dropping it in to the favorites window. The favorites information is saved per user per project in the rpw file for the project.
Improved deletion of references across units
Project teams working together on a model often may work on elements checked out in writeable units but with references in other units in a read only state. If this element is deleted then a situation arises where unresolved elements are created in the read only units. Rational Rhapsody 7.5 helps prevent this situation by displaying a dialog with a list of the read only units containing the references to the deleted element and you have the option to check out those units to avoid creating unresolved elements.
Highlighting elements in active component scope
Rational Rhapsody provides the ability to create multiple components each with a scope specifying the model elements part of that component. In Rational Rhapsody 7.5, the model elements that are in scope for the active component are shown in bold providing you with a visual indication of whether the model element is in scope to avoid performing operations that would only be available for model elements in scope. The property HighlightElementsInActiveComponentScope under General::Model is used to enable this feature.
Zooming with ctrl+scroll across all diagrams
It is possible now to zoom in or out of a diagram by holding the control key while moving the mouse wheel. . If an element is selected on the diagram then the zoom operation is performed relative to the selected item.
Populate existing diagrams
Rational Rhapsody 7.5 provides the populate diagram operation to an existing diagram to add more elements to the diagram and automatically create relations to it making it easier to visualize the design. This capability also works when populating diagrams with reverse engineering to update diagrams created through reverse engineering with updated information from the code.
Improved helper organization
User defined helpers can now be organized in a hierarchical fashion under the Tools and context menu to better organize and reduce the size of those menus.
Improved batch support
The Rational Rhapsody command line adds support for the COM API for enhanced nightly builds using user-defined helpers and plug-ins. In addition batch generation for users targeting Ada development is now possible.
Flowport support during testing
It is now possible to use, send and receive flow messages in tests cases providing the ability to create test cases with modeling more complex behavior.
CppUnit and JUnit Test Integration
Users can now leverage cppUnit or JUnit test cases as external test cases and execute them through Rational Rhapsody TestConductor to improve the reliability of their applications.
Support for Micro C models
Users of the Rational Rhapsody’s Micro C framework can now leverage Rational Rhapsody TestConductor to automate the testing and validation of their designs.
Offline testing for resource constrained targets
Rational Rhapsody TestConductor provides support for testing applications executing on an embedded target without the need of a connection to the target using black box tests enabling testing of resource constrained targets. The results of the testing are obtained through a dump from a debugger. This is available for C and C++ and is limited to statechart, flowchart and code test cases.
Hierarchical model coverage computation
It is now possible to compute coverage for parts of the system under test (SUT) and also test components providing better control of the testing results.
User-defined test case execution order
The order of execution of test cases can be controlled via the browser providing the user with more control and flexibility for testing.
Statechart test cases
It is now possible to define test cases using statecharts providing another mechanism to create test cases for more flexibility.
Full lifecycle traceability from requirements to test cases
Rational Rhapsody TestConductor improves the integration of testing with Rational DOORS with the ability to link test case with requirements using Rational Rhapsody Gateway to easily exchange information with Rational DOORS and help ensure that all requirements are being adequately tested. Combined with the ability to generate requirements into code, it is possible for traceability from requirements to design, implementation and test.
Triggered testing helpers
It is now possible to create customizable helper functions that are triggered when Rational Rhapsody TestConductor performs certain operations, such as creating a test architecture. The helper functions use that API and allow you to perform customizable operations for better control and further automation of your testing process.
Hidden test case execution
Test execution is improved by providing the ability to optionally hide the test execution window to maintain focus on the Rhapsody window.
Bidirectional Rational DOORS synchronization
Rational Rhapsody Gateway Add-on integration with Rational DOORS is improved with a synchronization operation between Rhapsody and DOORS that synchronizes the high level requirements in DOORS and Rhapsody. This allows changes to be made in either DOORS or Rhapsody and update the data appropriately. The synchronization uses Rhapsody’s differencing and merging capability to manage the changes automatically. After initial set up of the export operations, using the synchronize operation creates a workflow with that minimizes the interaction required with the Rhapsody Gateway providing a virtually seamless integration between Rhapsody and DOORS.
Rational DOORS Type Builder Wizard
A new wizard is provided in the Rational Rhapsody Gateway project editor that enables customization of DOORS XML types based on existing and recommended analysis features applied on attributes from DOORS objects making it easier import types from Rational DOORS.
Hierarchy Type
A new hierarchical type of analysis is available for Rational DOORS for better handling of Rational DOORS modules that captures the entire DOORS object hierarchy for modules that do not allow clear identification of sections and requirements.
Navigate to Element in DOORS
Navigation is provided to go from the Rational Rhapsody model element in the Rational Rhapsody Gateway directly to the exported Rational DOORS module containing the model elements.
Improved Rational DOORS export
Exporting Rational Rhapsody elements to Rational DOORS is made easier with an improved tabbed dialog with common features readily available, the ability to specify the server directly in the export dialog, more control over the specific types and ordering of exported elements.
Usability improvements
The Rational Rhapsody Gateway Add-on is updated with new features to improve the user workflow:
Improved interface to Rational ClearCase through SCC mode
Teams using Rational ClearCase via SCC mode from Rational Rhapsody can now take advantage of repository restructuring capabilities of Rational Rhapsody previously only available in batch mode. Users can now leverage the SCC mode capabilities of visual indicators of the state of a configuration management unit and perform UCM operations plus repository restructuring all from the single SCC workflow with Rational ClearCase.
Graphical merge for all diagrams
Rational Rhapsody 7.5 completes support for the graphical merging of all diagrams with the addition of static diagram support including object model, use case, structure, collaboration and panel graphics improving team collaboration and change management.
State based configuration management operations
When using SCC mode for configuration management it is possible to obtain the state of the configuration management unit which provides information on further actions that can be performed on the unit. Rational Rhapsody uses this information to decide if an operation should take place to prevent errors during configuration management operations. When a unit is checked in, do not perform the check-in operation if the unit is not checked out. When a unit is added to archive, do not perform the add-to-archive operation if the unit is already controlled by configuration management. When the undo checkout operation is performed on a unit, do not continue if the unit is not checked out.
Fetch reference units across projects
Rational Rhapsody adds the ability in SCC mode to fetch the current version of a reference unit from configuration management when using multiple projects within Rational Rhapsody.
Improved Jazz based IBM Rational Team Concert integration
Leveraging the power of Jazz and Eclipse, the Rational Rhapsody integration with Rational Team Concert (RTC) enables users to perform their configuration management through Team Concert enabling them to automatically notify each other of model updates as they occur. Rational Rhapsody 7.5 improves with workflow with Rational Team concert enabling teams to more effectively leverage the real time collaboration abilities provided with Rational Team Concert when doing their modeling work. Rhapsody’s powerful model differencing and merging capability is automatically triggered by Rational Team Concert to incorporate the changes into the model to manage changes better. Team Concert Integration is supported using the Rhapsody Eclipse Platform Integration.
Telelogic Synergy 7.0 Interface
Rational Rhapsody leverages the upgrade of the SCC interface of Telelogic Synergy 7.0 to support task related operations (e.g. create task, complete task) in addition to standard configuration management operations (e.g. check in, check out) (available in Telelogic Rhapsody 7.4.0.1 release).
Documentation generation improvements
The generation of documentation using Rational Rhapsody ReporterPLUS is improved with the additional support for panel diagrams and the ability to change the image format in the generated report to provide more control over the generated documentation.
Rose Import: Merge Code and Model (Available version Rhapsody 7.4.0.1)
Projects that are using IBM® Rational® Rose® and then developing software based on the model are now aided by new capabilities that can help you unify the model and code originating from Rose in the Rational Rhapsody environment. The Rose importer enriches this process by adding the ability to import code after importing the Rose Model; you can then bring this imported code into the model, helping you merge the model data and code. The operations in the code are parsed and the bodies are merged into the model elements that correspond to the code.
Import Japanese names from Rational Rose
The Rational Rose import is improved to import Japanese names as labels into Rational Rhapsody.
Rational Rose properties import
The Rational Rose import is improved to include properties from Rational Rose improving the transition of information.
Incremental XMI import
A new workflow is provided that enables updated XMI data to be merged with the current projects. The XMI file can be imported into a new Rational Rhapsody project. Differencing and merging can then be performed to identify the changes between imports and manage model updates.
Improved XMI support (available in Telelogic Rhapsody 7.4.0.1)
The Rational Rhapsody XMI component (available as a feature in the Rational Rhapsody Interfaces Add On™ solution) adds support for importing and exporting double byte characters, helping you exchange model information for languages (such as Japanese) that use double byte characters. The XMI Add-on is now available as a plug-in to the Rhapsody environment, which can help you improve performance by integrating it with the model to improve performance. Also, support for components is added to help you exchange more model information.
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.
Property Help in Japanese
To view the Property Help in Japanese in the features dialog, add the following item to the [General] section of the rhapsody.ini file.
PropertyHelpLanguage="JA"
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.
Using Rational Rhapsody with Rational Synergy
In the Team Collaboration Guide, in the chapter on using Rational Rhapsody with Rational Synergy, there are instructions for importing the Rhapsody type definition file. These instructions include a link for downloading this xml file from the IBM Web site. This file is no longer available for download. Rather, it is included as part of the Rhapsody installation. It can be found in the directory [Rhapsody installation directory]\Share\cm\Synergy.
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
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.
When opening activity diagrams created with versions of Rhapsody prior to 7.5, Rhapsody will replace certain elements with the new corresponding elements introduced in 7.5, with the following exceptions:
Junction Connectors are not converted to Merge Nodes.
Transitions are not converted to ObjectFlows or ControlFlows.
Adaptors
Rhapsody 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.4", 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.4 (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
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.
When using the Rhapsody Eclipse Platform Integration, you cannot generate AUTOSAR XML.
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.
Code-centric Settings
When using the Code-centric Settings with Eclipse platform integration, if you want to reverse engineer a project, you must use the “Import Sources to Rhapsody” option rather than the “Export to Rhapsody” option.
When using the Code-centric Settings in RiC, models must be file-based and not class-based.
Configuration Management
After "updating" from CVS repository, units are reported as unresolved even though they are in the correct location in the file system. To correct this problem, select the unresolved unit in the Rational Rhapsody browser and select "Load with descendants" from the pop-up menu.
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
Helper Menu Customization
This feature is not available in Eclipse platform integration.
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).
MicroC Profile
"Executable" classes cannot be used as Parts with multiplicity greater than 1.
Rhapsody's S-Function feature cannot be used with the MicroC profile.
When using the MicroC 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 MicroC profile. By default, "Advanced" mode is used.
DMCA (Dynamic Model-Code Associativity) cannot be used with this profile.
The port multicast feature cannot be used with the MicroC profile.
Panel Diagrams
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.
There are currently no methods for adding an ObjectFlow or a ControlFlow to an activity diagram.
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.
SA Import
The UI does not provide any way to select an import map. As a workaround, the xml file can be edited manually.
Save as 7.4 Model
When saving a model as a 7.4 model, not all activity diagrams elements are saved correctly. When opening the model in 7.4, Rhapsody may display a message about unresolved stereotypes.
After you save a model as a 7.4 model, any CGCompatibilityPre75 profiles should be manually removed from the model when you open it in Rhapsody 7.4.
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.
Static Inheritance
In RiC, when using static inheritance with name mangling, the code generated for the derived class may not compile. Suggested workarounds: Manually define a dependency from the derived class to the base class or manually override the problematic operations.
When using static inheritance in RiC++, if you roundtrip changes made to the derived class, the static inheritance relation disappears.
When using static inheritance with a base class that has ports, there are situations where Rhapsody mistakenly identifies a port as a multicast port, and the generated code will not compile. If you do not use multicast ports in your model, you can work around this limitation by disabling multicast support (set the value of the property SupportMulticast to Never).
Synergy Integration
After creating a task from within Rhapsody, the task list is not automatically refreshed. To have the task list updated, click the Refresh button.
System Designer
In Rhapsody System Designer, Cygwin and Microsoft are the only targets supported.
Tabular Statechart
When editing tabular statecharts, you cannot add new triggered operations or new states.
Variants
Currently, variation points should only be defined on classes and files (not on objects).
Visual Studio 2008 Support
For the OseSfk environment, Rhapsody does not support use of the Visual Studio 2008 compiler.
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 TestConductor
Domain-specific Profiles
Such as DoDAF and MoDAF
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
Eclipse Workflow Integration
Workflow integration with Eclipse 3.4 is not supported on Red Hat 5.0.
Fixed-point variables
This feature is not included in the Linux version.
Generate Support Request
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 Eclipse Platform Integration
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 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 SP1
Windows XP (SP1/SP2/SP3)
CPU
Pentium 4, 3.0 GHz
Disk Space
~750 MB (full installation)
RAM
512 MB
The following software is required to run Rhapsody:
License management software
FlexNet 11.5
Network protocol
For design-level debugging with animation, Rational Rhapsody requires TCP/IP and an IPX/SPX-compatible network protocol.
RiJ (for compiling and running code)
IBM Java 1.5
or
Version 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.
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 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 support.
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 support.
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 support.
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 support.
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 and C++
RTX™ (VenturCom®)
5.5 - Rhapsody in C++
For the latest version, contact support.
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 support.
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 sales representative or Customer Support with specific inquiries.
Eclipse
3.4 (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 support.
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 Frameworks and Operating Systems Reference 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)
4.3.2 (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.
IBM® Rational® DOORS®
Rhapsody DOORS Interface supports: 8.3, 9.2
Rhapsody Gateway supports: 8.3, 9.2
IBM® Rational® SDL Suite
6.2
IBM® Rational® Statemate®
4.3
IBM® Rational® Synergy
7.0
IBM® Rational® System Architect®
11.2
IBM® Rational® Tau
4.2
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
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
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 6.6
VxWorks PENTIUM_RTP_gnu - VxWorks 6.5, VxWorks 6.6
VxWorks PENTIUMdiab - VxWorks 6.5, VxWorks 6.6
VxWorks PENTIUMgnu - VxWorks 6.5, VxWorks 6.6
VxWorks PPC32_RTP_diab - VxWorks 6.5, VxWorks 6.6
VxWorks PPC32_RTP_gnu - VxWorks 6.5, VxWorks 6.6
VxWorks PPC32diab - VxWorks 6.5, VxWorks 6.6
VxWorks PPC32gnu - VxWorks 6.5, VxWorks 6.6
VxWorks PPC403 - VxWorks 5.5
VxWorks PPC403diab - VxWorks 6.5, VxWorks 6.6
VxWorks PPC403gnu - VxWorks 6.5, VxWorks 6.6
VxWorks PPC603 - VxWorks 5.5
VxWorks PPC603diab - VxWorks 6.5, VxWorks 6.6
VxWorks PPC603gnu - VxWorks 6.5, VxWorks 6.6
VxWorks PPC604 - VxWorks 5.5
VxWorks PPC604diab - VxWorks 6.5, VxWorks 6.6
VxWorks PPC604gnu - VxWorks 6.5, VxWorks 6.6
VxWorks PPC860 - VxWorks 5.5
VxWorks SIMNT - VxWorks 5.5
VxWorks SIMNTdiab - VxWorks 6.5, VxWorks 6.6
VxWorks SIMNTgnu - VxWorks 6.5, VxWorks 6.6
VxWorks SIMPENTIUM_RTP_diab - VxWorks 6.5, VxWorks 6.6
VxWorks SIMPENTIUM_RTP_gnu - VxWorks 6.5, VxWorks 6.6
Use this URL for Rhapsody support.
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, and ibm.com 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.