Rational Software Architect for WebSphere Software Version 7.5 Releases: New Features and Enhancements

Product documentation


Abstract

The IBM Rational Software Architect for WebSphere Software Version 7.5.x releases contain cumulative fixes, enhancements, and new features, meaning that they include all new features or enhancements, as well as additional fixes to Eclipse, from earlier releases.

Content

The following is a summary of enhancements made available in the version 7.5.5.4 release.

Table of contents:


Version 7.5.5.5
Version 7.5.5.4
Version 7.5.5.3
Version 7.5.5.2
Version 7.5.5.1
Version 7.5.5
Version 7.5.4
Version 7.5.3
Version 7.5.2
Version 7.5.1
Version 7.5


Version 7.5.5.5
Download Version 7.5.5.5


This release of Rational Software Architect for WebSphere Software contains new features and enhancements in the following areas:
  • Updates to supported web browsers
  • Additional Eclipse patches and fixes
  • IBM WebSphere Application Server test environment updates
  • Rational Application Developer for WebSphere Software build utility update




  • Updates to supported web browsers
    Beginning with version 7.5.5.5, the following additional web browser versions are supported:
    • Mozilla Firefox 5.0, 6.0, and 7.0

    Back to top



    Additional Eclipse patches and fixes
    The following additional Eclipse 3.4.2.8 patches and fixes are included in this release:
    Back to top



    IBM WebSphere Application Server test environment updates

    The following IBM WebSphere Application Server Test Environment updates are available:
    Back to top



    Rational Application Developer for WebSphere Software build utility update

    Rational Application Developer for WebSphere Software build utility, v7.5.5.5 is available. For more information, see: http://www.ibm.com/support/docview.wss?uid=swg24031226

    Back to top

    Version 7.5.5.4
    Download Version 7.5.5.4


    This release of Rational Software Architect for WebSphere Software contains new features and enhancements in the following areas:
    • Updates to supported operating systems
    • IBM Runtime Environment for Java Technology updates
    • Updates to supported web browsers
    • Additional Eclipse patches and fixes
    • IBM WebSphere Application Server test environment updates
    • JSF tools
    • Web development tools
    • Web services




    • Updates to supported operating systems
      Beginning with version 7.5.5.4, the following additional operating system versions are supported:
      • Microsoft Windows 7 Service Pack 1
      • Microsoft Windows Server 2008 Release 2 Service Pack 1
      • Red Hat Enterprise Linux 5 Update 6
      • Red Hat Enterprise Linux 4 Update 9
      • SUSE Linux Enterprise Server 10 Service Pack 4
      • SUSE Linux Enterprise Desktop 10 Service Pack 4

      Back to top



      IBM Runtime Environment for Java Technology updates
      IBM Runtime Environment for Java Technology is updated to the following versions:
      • IBM 32-bit Runtime Environment for Windows, Java Technology Edition, Version 1.6 Service Release 9 plus Fix Pack 001 and interim fix
      • IBM 32-bit Runtime Environment for Linux, Java Technology Edition, Version 1.6 Service Release 9 plus Fix Pack 001 and interim fix

      Back to top



      Updates to supported web browsers
      Beginning with version 7.5.5.4, the following additional web browser version is supported:
      • Mozilla Firefox 4.0
      • Microsoft Internet Explorer 9

      Back to top



      Additional Eclipse patches and fixes
      The following additonal Eclipse 3.4.2 patches and fixes are included in this release:
      Back to top



      IBM WebSphere Application Server test environment updates
      The following IBM WebSphere Application Server Test Environment updates are available:
      Back to top



      JSF tools
      New message added to tell users that the JSFTrace is enabled at run time.

      Back to top



      Web development tools
      • To reduce the disk space used to install the product, now only the latest version of the Communications Enabled Applications Feature Pack is included in the product. Other versions of the Feature Pack can by used by importing them from disk into the workspace.
      • Firebug has been upgraded to v1.7.
      • IBM Mashup Center support has been upgraded to version v3.0.0.1.

      Back to top



      Web services
      Handling of multiple schema versions when generating web services and clients:
      When generating web services and clients, all code is generated into one project and main source folder even if the source WSDL is different, and the dependent XML schema files have different versions.

      Back to top

      Version 7.5.5.3
      Download Version 7.5.5.3


      This release of Rational Software Architect for WebSphere Software contains new features and enhancements in the following areas:


      Additional Eclipse patches and fixes
      The following additonal Eclipse 3.4.2 patches and fixes are included in this release:
      Back to top



      IBM WebSphere Application Server test environment updates
      The following IBM WebSphere Application Server Test Environment updates are available:
      Back to top



      Portal tools
      • IBM JSF Portlet bridge support for JSR 286 Portlet porjects based on JSF 1.2.
        IBM Portlet bridge now supports JSR 286 JSF Portlet projects. Palette options and tooling support for JSR 286 features for JSF Portlet projects, such as eventing and resource serving, have been added.

      Back to top



      UML-to-XSD and UML-to-WSDL transformations
      You can now specify whether the UML-to-WSDL and UML-to-XSD transformations generate output by using customized output information, such as namespace and resource location information, that you provide in the transformation configuration: On the Output Options page of a transformation configuration, select the Customize the output according to the entries in the following table check box. When you run the transformation, it uses the information in the corresponding table to generate output. By default, this option is selected.

      If you disable this option, the transformation ignores the information in the table and uses only the information in the source model to generate output. Although the information in the table is refreshed, the transformation ignores it.

      Back to top



      Web development tools
      • Tooling updates to support the following changes:
        • IBM WebSphere Application Server Feature Pack for Web 2.0: updated to v1.0.1.1.
        • IBM WebSphere Application Server V7 Feature Pack for Communications Enabled Applications (CEA) CEA: updated to v1.0.0.7.
        • JavaScript FireBug debugger: updated to v1.6.
        • Lotus iWidget support: updated to specification level 2.1.
      • Performance was improved in the Link Indexer.

      Back to top

      Version 7.5.5.2
      Download Version 7.5.5.2


      This release of Rational Software Architect for WebSphere Software contains new features and enhancements in the following areas:


      Eclipse platform updates
      The following additional Eclipse 3.4.2 patches and fixes are included in this release:
      Back to top



      IBM Runtime Environment for Java Technology updates
      IBM Runtime Environment for Java Technology is updated to the following versions for Windows and Linux operating systems:
      • IBM 32-bit Runtime Environment for Windows, Java Technology Edition, Version 1.6 service release 8
      • IBM 32-bit Runtime Environment for Linux, Java Technology Edition, Version 1.6 service release 8

      Back to top



      IBM WebSphere Application Server test environment updates
      The following IBM WebSphere Application Server Test Environment updates are available:
      Back to top



      Java EE Connector (J2C) tools
      • IMS TM Resource Adapter updates from version 10.32 to 10.40.
      • WebSphere Adapters have been updated to the following versions:
        • V7.0.0.1
          • JD Edwards Enterprise One 7.0.0.1
          • Oracle 7.0.0.1
          • PeopleSoft Enterpise 7.0.0.1
          • SAP Software 7.0.0.1
          • SAP Software with transaction support 7.0.0.1
          • Siebel Business Applications 7.0.0.1
        • V6.2.0.x
          • JD Edwards Enterprise One 6.2.0.3
          • Oracle 6.2.0.4
          • PeopleSoft Enterpise 6.2.0.3
          • SAP Software 6.2.0.4
          • SAP Software with transaction support 6.2.0.4
          • Siebel Business Applications 6.2.0.4. 
      Back to top



      Service modeling - SoaML profile & tools
      In earlier releases, the SoaML 1.0 specification was supported only at a draft level. Now the final SoaML 1.0 specification is supported. Models that use the SoaML profile from earlier versions of the product are automatically migrated to the new profile version when they are opened.

      Back to top



      Test and profiling tools
      • It is no longer necessary for you to set up environment variables when profiling web application on a local WebSphere Application Server v6.x server running on "pre-JRE 1.5" JVM if you have write access to the "<WAS_ROOT>\java\jre\bin" folder.

      Back to top



      Web development tools
      • JPA tooling has been redesigned to provide more intuitive configuration of manager beans and JEE entity beans.
      • FireBug has been upgraded to version 1.5.4.
      • Communications Enabled Applications (CEA) support have been upgraded to support the WebSphere Application Server Feature Pack for CEA Fix Pack 1.0.0.5.
      • You can now use JPA resource injection in any web application. (This is advanced functionality in which you put the beans in a plain JPA project and then use them from a JSF application.) Previously, you could not "Use resource injection" if the project was an EJB project or if the project was not a JSF project.

      Back to top



      Web services tools
      The generated client proxies for IBM WebSphere JAX-RPC and JAX-WS Web service runtimes now have a control method called useJNDIOnly(boolean). When this method is invoked with a value of true, the proxy will attempt to perform a JNDI lookup for the service reference and stop if it fails. Otherwise, the Web service client will use an unmanaged invocation mechanism. For JAX-RPC, this is through the Locator class. For JAX-WS, it is through the generated Service class.

      Back to top

      Version 7.5.5.1
      Download Version 7.5.5.1


      This release of Rational Software Architect for WebSphere Software contains new features and enhancements in the following areas:


      Additional Eclipse patches and fixes
      The following additional Eclipse 3.4.2 patches and fixes are included in this release:
      Back to top



      Updates to supported Web browsers
      Beginning with version 7.5.5.1, the following additional Web browser version is supported:
      • Mozilla Firefox 3.6

      Back to top



      IBM Runtime Environment for Java Technology updates
      IBM Runtime Environment for Java Technology is updated to the following versions for Windows and Linux operating systems:
      • IBM 32-bit Runtime Environment for Windows, Java Technology Edition, Version 1.6 service release 7 plus interim fix 001
      • IBM 32-bit Runtime Environment for Linux, Java Technology Edition, Version 1.6 service release 7

      Back to top



      IBM WebSphere Application Server test environment updates
      The following IBM WebSphere Application Server Test Environment updates are now available:
      Back to top



      Application build
      A new ANT task for preparing for deployment is available. By using this new ANT task, you can have a common build process for local developing and deploying to testing or production systems. This ANT task to is equivalent to the WebSphere Application Server task WsDeploy.

      Back to top



      Debug tools
      The XSLT debugger now supports debugging XSLT 2.0 in addition to XSLT 1.0. For this new support, new views and actions in the XSLT debugger are available and a new XSLT 2.0 debug engine (developed on top of the XLTXE-J2 processor) is included.

      Back to top



      Portal tools
      The value of context-param com.ibm.faces.portlet.USE_RENDER_PARAMETERS added to the web.xml is changed from "true" to "false" to reduce extensive use of session in the portlet bridge and allow the bridge to use session to pass the JSF artifacts between action and render requests, resulting in reduction of session size as compared to the usage of render parameter.

      Back to top



      Rational Rose model import
      You can now save the the subunit conversion options in a file which has .xml as the file name extension on the Subunit Conversion page of the Rational Rose Model Importer wizard.

      When you need to import the same sets of subunits (with count in order of hundreds or thousands) multiple times with the same conversion pattern, you can use this feature to load and reapply the .xml file for subsequent imports.

      Back to top



      UML-to-XSD and UML-to-WSDL transformations
      XSD polymorphism and substitution groups are now supported by an extension to the UML-to-XSD and UML-to-WSDL transformations. When the transformation runs with this extension enabled, the transformation generates global elements that support XSD polymorphism and substitution groups.

      To enable this extension, create or open a transformation configuration file for a UML-to-XSD or UML-to-WSDL transformation, and in the transformation configuration editor, on the Extensions page, select the check box for the Support for XSD polymorphism and substitution groups extension.

      Back to top



      UML Profile-based Integrated Architecture (UPIA) (IAM2)
      The UML Profile-based Integrated Architecture (UPIA) feature has been upgraded to further support DoDAF 2.0 and to improve usability. For detailed information, see the Rational support document, "Changes to the IBM Rational UML Profile-based Integrated Architecture (UPIA) feature in V7.5.5.1," at http://www.ibm.com/support/docview.wss?uid=swg27017935.

      Back to top



      Web development tools
      • Support for the WebSphere Web 2.0 Feature Pack v1.0.1 which includes a Dojo version update to 1.4.
      • Lotus iWidget Test Client update to support version 2.0.0.1 of the Lotus iWidgets container.
      • Descriptions for all Dojo widgets and properties.
      • Update of the Firebug JavaScript debugger to 1.5.2.

      Back to top



      Web services tools
      • Updates to the WebSphere Web 2.0 feature pack include a JAX-RS (RESTful Web Services) runtime. This runtime is available in WebSphere Application Server versions 6.1.0.29 and 7.0.0.9.
      • When developing JAX-RS applications that target the WebSphere JAX-RS runtime, a JAX-RS library is now predefined when adding the JAX-RS facet to a Dynamic Web Project.
      • Applications that use the predefined JAX-RS libraries can automatically pick up the latest JAX-RS runtime when the server is updated by using the Shared library support.
      • When creating new Dynamic Web projects, a new project configuration named IBM JAX-RS Configuration is available.

      Back to top

      Version 7.5.5
      Download Version 7.5.5


      This release of Rational Software Architect for WebSphere Software contains new features and enhancements in the following areas:


      Eclipse platform updates
      The following Eclipse 3.4.2 patches and fixes are included in this release:
      Back to top



      Updates to supported operating systems
      Beginning with version 7.5.5, the following additional operating system versions are supported:
      • Microsoft Windows Server 2008 Release 2
      • Microsoft Windows 7

      Back to top



      IBM Runtime Environment for Java Technology updates
      IBM Runtime Environment for Java Technology is updated to the following versions for Windows and Linux operating systems:
      • IBM 32-bit Runtime Environment for Windows, Java Technology Edition, Version 1.6 service release 6 plus interim fix
      • IBM 32-bit Runtime Environment for Linux, Java Technology Edition, Version 1.6 service release 6 plus interim fix

      Back to top



      Service modeling with SoaML
      The creating SoaML capability from UML activity is now supported from the tool palette.

      Back to top



      UML-to-WSDL transformation
      The UML-to-WSDL transformation now supports SOAP 1.2. On the WSDL Options page, in a transformation configuration file, you can specify which version of SOAP binding (version 1.1 or 1.2) the transformation uses for the SOAP interfaces in the source model.

      Back to top



      Java-to-Service-Model transformation
      The Java-to-Service-Model transformation now generates a part in the provider component of the generated service model. The type and name of this part correspond to the component that the transformation generates from the Java implementation class.

      Back to top



      Session-Bean-to-Service-Model transformation
      The Session-Bean-to-Service-Model transformation now generates the following items in a service model:
      • A component whose name corresponds to the remote interface of the session bean in the source model.
      • In the provider component, a part and the corresponding connectors. The type and name of the part correspond to the component that the transformation generates from the remote interface for the session bean.

      Back to top



      UML modeler
      • New preference to set the search scope options for models, new option when setting the search scope to exclude non-imported UML libraries.
      • The following new functions have been introduced to sequence diagrams:
        • Asynchronous messages can be created without a Behavior Execution Specification.
        • Behavior Execution Specification for asynchronous message can be deleted.

      Back to top



      Rational Asset Manager integration
      The publish asset wizard can now handle custom attribute fields.

      Back to top



      Rational Requirements Composer integration transformation
      The Rational Requirements Composer integration transformation now supports archives from Rational Requirements Composer Version 2.0, or later.
      To import archives from Rational Requirements Composer Version 2.0, or later, you must use Rational Software Architect for WebSphere Software Version 7.5.5 with Interim Fix 002, or later. For more information, see http://www.ibm.com/support/docview.wss?uid=swg21415580.

      Back to top



      UML Profile tooling
      • By default, when you re-generate tooling code, files such as plugin.xml, plugin.properties, and the template model are overwritten. However, you can now specify preferences that determine whether these key files are overwritten. In addition, these preferences also allow you to create backup copies of these files. For details on how to specify the new preferences, see the profile tooling online help.
      • It is now possible to specify an image and indent status for property tabs generated as part of profile tooling. For details on using images in profile tooling, see the profile tooling online help.

      Back to top



      Rational Rose model import
      You can use the new Map Rose User Types page of the Rational Rose Import wizard to map user-defined types of a Rational Rose model to a new custom model library, or map user-defined types to existing model libraries, and set this configuration for subsequent imports.
      There is also an option in the same page to import Rational Rose user-defined types as primitive or class types. Previously this option was only available through application parameters in the eclipse.ini file.

      Back to top



      IBM WebSphere Application Server Test Environment updates
      The following IBM WebSphere Application Server Test Environment updates are available:
      Back to top



      Java EE Connector (J2C) tools
      • WebSphere Adapter changes:
        The following new Websphere Adapter versions have been added:
        • SAP Software V7000_F01
        • PeopleSoft Enterprise V7000_IF01
        • Siebel Business Applications V7001_IF01
        • JD Edwards Enterprise One V7000
        • Oracle E-Business Suite V7000
        These Websphere Adapters have been updated to the following versions:
        • IMS TM Resource Adapter V10.3.2
        • Oracle E-Business Suite V6203
        • PeopleSoft Enterprise V6202
        • SAP Software V6204
        • Siebel Business ApplicationsV6203
        The following Websphere Adapters have been removed:
        • JD Edwards Enterprise One V6102_IF01
        • Oracle E-Business Suite V6103_IF01
        • PeopleSoft Enterprisae V6103_IF01
        • SAP Software V6104_IF01
        • Siebel Business Applications V6104_IF01
      • The J2C Service migration wizard includes a new Resource Adapter Selection Page. If you migrate WebSphere Software Application Developer Integration Edition (v.5.1) WSDL services to J2C beans, you can use the Resource Adapter Selection Page to choose the resource adapter type and version, as well as the target server version.
        The command-line J2C WSDL Migration tool now also provides similar support.
      • A new suffix option is added to the command-line J2C WSDL migration and the J2C Service Migration wizard. By using this option, you can modify the migrated J2C bean implementation name (that usually ends with "Proxy") to "Impl" or other values.

      Back to top



      Java EE tools
      • The JavaEE project preferences page has been enhanced.
      • You can now specify an output folder.
      • A new validator named "Project Structure Validator" has been added. The new validator flags Java EE projects that do not adhere to a single-root structure. The validator is enabled for both automatic and manual builds and contains a severity level preference option.

      Back to top



      Portal tools
      Tooling support is now available for creating and publishing iWidgets on WebSphere Portal v6.1.5.

      Back to top



      Server tools
      The performance of publishing all applications in a single Add/Remove module action has been improved.

      Back to top



      SCA tools
      • Enhanced editors, wizards, validators and other tools to support several new capabilities of the WebSphere Application Server v7 Feature Pack for SCA Version 1.0.1 are available:
        • With the graphical composite editor, you can enable your components to integrate loosely with JMS applications by configuring the new JMS binding on your component services and references.
        • You can configure components to interact directly with Web 2.0-style applications using ATOM feeds or JSON-RPC. Also, you can configure SCA components to inject SCA properties and references into your JavaScript code. The tools can generate HTML or JavaScript skeletons to help you get started.
        • You can use Java EE Enterprise Applications (EARs) with or without SCA extensions as the implementations of SCA components, enabling you to assemble entire EARs along with other kinds of business implementation assets into heterogeneous SCA service assemblies.
        • You can use existing Spring applications as implementations of SCA components. Similar to the Java EE support, this enables you to assemble Spring application assets along with other kinds of business assets into heterogeneous SCA service assemblies.
        • The tools now include support for SDO (Service Data Objects) as an alternative to JAXB (Java Architecture for XML Binding) for components must process dynamic or weakly-typed business data. The tools generate Java skeletons with your choice of SDO or JAXB data bindings.
        • New samples and tutorials are included to help you learn about and experiment with the new capabilities.
      • The SCA tools continue to support development for the WebSphere Application Server, version 7 Feature Pack for SCA Version 1.0.0. When you develop and when you publish applications, the tools verify that the SCA assembly model features that you are using are supported by the version of the Feature Pack for SCA that you are targeting.
      • There are usability enhancements to the user interface of the SCA tools:
        • The Refresh from Implementation and Regenerate Implementation actions are now available when the editor has changes that have not been saved (if you run these actions you are prompted to save your changes before continuing). In earlier version, these actions were not available if the composite editor contained changes that were not saved.
        • You can now add SCA support to a Java project by using a single quick fix instead of two fixes.
        • The SCA validator can now detect additional warning and error conditions in SCA assemblies, including the new bindings and implementations supported by the WebSphere Application Server SCA Feature Pack Version 1.0.1.
        • The tools provide more control over the namespace and workspace file names of your composite by making it easier to organize composites and avoid name collisions.

      Back to top



      Web Development Tools
      You can now add Communication Enabled Application (CEA) Widgets version 1.0.0.1 or 1.0.0.0, and existing project can be changed to either version.
      Back to top



      Web services tools
      • You can now enable support for JAX-WS 2.1.6 and later through a new Service Policy option under WebSphere Programming Models > JAX-WS.
        If you enable this support, you will get warnings for methods in a Java class that will be implicitly exposed as a result of the new specification. A quickfix is available to hide these methods and preserve the Web service interface from prior JAX-WS standards.
      • RESTful Web services are now supported using the JAX-RS specification:
        You can download a Java-based JAX-RS 1.0 implementation and configure Dynamic Web projects to use it. Validators,  annotations processors and quickfixes provide assistance with configuring the run time and using the programming model.
        You can also use WebSphere's shared library option to centralize the management of their JAX-RS implementations.
      • SAML (Security Assertion Markup Language) support:
        • A SAML project facet is available to enable or prevent publishing to WebSphere Application Server.
        • The Policy Set Attachment Wizard can consume SAML tokens, and generate binding configuration files.
        • The new SAML General Bindings are supported. (SAML Bearer and Holder of Key)
        • A SAML sample is available.
      • Editors have been created for the following WebSphere policy set binding configuration files:
        • WSSecurity
        • JMSTransport
        • SSLTransport
        • HTTPTransport
        • WSReliableMessaging
        Using these editors, you can create and edit valid binding configuration files for both the client and services.
        You can also create, attach and edit custom binding configuration files for the service provider by using these editors.

      Back to top



      XML Tools
      • You can now compile and integrate XSL 1.0 and 2.0 stylesheet documents into Java projects. This new functionality automatically handles classpath and runtime configurations. Also, a new option is available to incorporate a Java utility class is offered so that you can integrate compiled stylesheets.
      • The Expression Builder tool in the XSL Editor now supports as-you-type evaluation for XPath 1.0 and 2.0.
      • The XSL Editor now supports grammars for XSL versions 1.0 and 2.0. Content assist has been enhanced to incorporate better prefix handling, customized icons and detailed descriptions for all XSL element suggestions. Version sensitive file decorations are now available for XSL documents.
      • You can now run XSLT 2.0 transformations.
      • Content assist for XPath 2.0 and XSLT 2.0 functions in the XSL editor and XPath Expression Builder is now available.
      • The XSLT validator now supports both XSLT 1.0 and XSLT 2.0, and provides build, manual and as-you-type validation. The validator helps you ensure that your XSLT documents are correct according to the XSLT 1.0 or 2.0 specifications.
      • XSL templates are now available that can be added to new XSL files from the New XSL wizard. The templates can also be inserted into XSL files through the content-assist feature in the XSL editor.
        You can modify the XSL templates through XML preferences page (Window > Preferences > XML > XSL> Editor > Templates).
      • A new XSLT 2.0 sample is available that demonstrates the XSLT 2.0 transformation using context menu and Java code.

      Back to top

      Version 7.5.4
      Download Version 7.5.4


      This release of Rational Software Architect for WebSphere Software contains new features and enhancements in the following areas:
      • Eclipse platform updates
      • Updates to supported operating systems
      • Updates to supported Web browsers
      • IBM Runtime Environment for Java Technology updates
      • IBM WebSphere Application Server test environment updates
      • Service modeling with SoaML
      • Service profile migration
      • BPMN modeling
      • BPMN-to-service-model transformation
      • UML-to-SOA transformations
      • XSD and WSDL transformations
      • XSD profiling
      • Deployment planning and automation
      • IBM Rational Modeling for Communications Applications (new installable priced feature)
      • SIP code development tools
      • UML Profile-based Integrated Architecture (UPIA) (IAM2)
      • 3GL domain modeling
      • EJB 3.0-to-UML and JPA-to-UML transformations
      • Java domain modeling
      • Java EE Connector (J2C) Tools
      • Java EE tools
      • Java transformations
      • Patterns and transformations
      • Profile tooling generator
      • Rational RequisitePro integration
      • Rational Rose model import
      • Rational System Architect integration
      • Rational Team Concert Client integration
      • Traceability
      • UML model analysis and metrics
      • UML modeler
      • UML compare and merge
      • Web Development Tools
      • Web publishing
      • XML Tools




      • Eclipse platform updates
        The following Eclipse 3.4.2 patches and fixes are included in this release:
        Back to top



        Updates to supported operating systems
        Beginning with version 7.5.4, the following additional operating system versions are supported:
        • Microsoft® Windows® XP Service Pack 3
        • Microsoft Windows Vista Service Pack 2
        • Microsoft Windows Server 2008
        • Red Hat Enterprise Linux® 5 Update 4
        • Red Hat Enterprise Linux 4 Update 8

        Back to top



        Updates to supported Web browsers
        Beginning with version 7.5.4, the following additional Web browser versions are supported:
        • Mozilla Firefox 3.5.2
        • Microsoft Internet Explorer 8

        Back to top



        IBM Runtime Environment for Java Technolgy updates
        IBM Runtime Environment for Java Technology is updated to the following versions for Windows and Linux operating systems:
        • IBM 32-bit Runtime Environment for Windows, Java Technology Edition, Version 1.6 service release 5 plus interim fix
        • IBM 32-bit Runtime Environment for Linux, Java Technology Edition, Version 1.6 service release 5 plus interim fix

        Back to top



        IBM WebSphere Application Server test environment updates
        The following IBM WebSphere Application Server Test Environment updates are available:
        Back to top



        Service modeling with SoaML
        • In this release, comprehensive support is added to service modeling based on the forthcoming new Service Oriented Architecture Modeling Language (SoaML) standard from OMG :
          • The new services modeling tools and related enhancements reflect SOA development process best practices documented by RUP SOMA 2.9 to guide you to success with business-driven, robust, scalable SOA development.
            A new Services Design Model template can automatically create the recommended model and package structure and includes reusable building blocks that let you build robust service designs more quickly.
          • The services modeling tools are integrated with the new Business Process Modeling Notation (BPMN) 2.0-based business process modeling tools. This includes automatic creation of traceability links from service model elements back to the business process model elements from which they were derived. This enables you to have better change governance and do more accurate impact analysis on SOA projects.
            For example, given a high-level BPMN 2.0 business process model, an IT architect doing up front candidate service identification can select an appropriate business process model element and easily create a corresponding service model capability (representing a candidate service) in a service model (including a traceability link). These Capabilities can then be refined and refactored as needed, becoming input into subsequent process steps, such as service identification.
          • The services modeling editor and related tools focus heavily on usability and keeping simple things simple. This enables even those who are new to UML and SOA to successfully and effectively build detailed services models as part of an overall SOA process. However, the expressiveness of full UML is also always available.
          • When editing a Services Model, the UML editor provides context menu and palette drawer items specifically tailored to be convenient and useful for services modeling.
            • Various "accelerators" provide quick ways to perform common multi-step operations in a single step.
            • A Service tab added to the Properties view is selection-sensitive and lets you view and modify those properties of selected elements that are of most interest to services modelers.
          • You can migrate existing services models that are based on the (now-deprecated) Software Services profile to the new standard SoaML profile from OMG.
          • Samples and a tutorial help you get up to speed by using the new Services Modeling and related tools.
        • A new transformation named BPMN-to-Service-Model is available for generating service models based on the information in Business Process Modeling Notation (BPMN) models.
        • UML-to-SOA transformations (WSDL/XSD, BPEL, and SCDL) have been updated to work with SoaML.
        • A new UML-to-SOA transformation is provided: UML-to-Open SCA.

        Back to top



        Service profile migration
        A new tool to migrate from the Software Services Profile to the SoaML profile is provided. The new Migrate to SoaML Profile menu will pop up when the model contains "Software Services" profile. The tool applies SoaML profile stereotypes when it finds matching SoftwareServices profile stereotypes on UML elements in the model.

        Back to top



        BPMN modeling
        • New support for the creation and management of semantic models and diagrams based on Business Process Modeling Notation (BPMN) version 2.0.
        • Integrated with UML modeling:
          • Link and navigate to BPMN elements from UML elements (by creating URL links using Add UML > URL Link and Navigate >To URL Link pop-up menus)
          • Use the Service Modeling (SoaML) tool palette to complete the following tasks:
            • Create SoaML <<Capability>>Classes from existing BPMN elements (also works with UML Activities as the source elements).
            • Create SoaML <<ServiceInterface>Interface/Class from existing BPMN element.

        Back to top



        BPMN-to-service-model transformation
        A new transformation named BPMN-to-Service-Model is available for generating service models based on the information in Business Process Modeling Notation (BPMN) models.
        In the New Transformation Configuration wizard, you can select this transformation from the Service Oriented Architecture Transformations folder.

        Back to top



        UML-to-SOA transformations
        • A new UML-to-SCA transformation is available. In the New Transformation Configuration wizard, you can select this transformation from the Service Oriented Architecture Transformations folder.
        • Previously included UML-to-SOA transformations (WSDL/XSD, BPEL, and SCDL) have been updated to work with SoaML.

        Back to top



        XSD and WSDL transformations
        • WSDL transformations have been enhanced with a new capability to model the binding per Port/Interface. You can specify the SOAP header for each operation using a new property page.
        • Enhanced to transform UML Datatypes and Signals to complex types from the XSD and WSDL transformations.
        • Enhanced the XSD-to-UML transformation to become a reverse transformation to the UML-XSD transformation.
        • Enhanced the "Auxiliary sources and target" tab to easily discover the XSD source files' auxiliary files when you click the Discover Auxiliary Sources button.
        • Enhanced the UML-to-XSD transformation to become an inverse transformation to the XSD-UML transformation enabling round-trip transformation scenarios.

        Back to top



        XSD profiling
        This feature provides a new palette for the profile, providing tools to easily generate the modeling artifacts used by the UML-to-XSD transformation. The palette appears on Class diagrams and free form diagrams. You can enable this palette by enabling the diagram capability "XSD Transformation Profile" in the properties view of the root model node.

        Back to top



        Deployment planning and automation
        • New support for Model Driven Deployment, with which you can create workflows from topologies and publish those workflows to Rational Build Forge. You can import existing scripts and automation definitions, such as Build Forge Libraries, and use advanced pattern matching and deployment intelligence to apply those automation definitions to topologies and create automation workflows.
        • New support to design reusable "automation signatures" from existing Build Forge libraries, including the reflection of required parameters for the libraries, and the ability to design semantic Topology "patterns" used in the creation of organized automation workflows.
        • New support for Tivoli Application Dependency Discovery Manager v7.1 SP1. You can search, explore, and import information from the TADDM Configuration Management Database (CMDB) into a Topology model. Initial support is also available for Computer Systems, Operating Systems, Network, Storage, and Installed Software domains.
        • New support for customizing the appearance of links in Topology diagrams, including removing links from diagrams, manually choosing a path for links on the diagram, rendering links over link intersection points with “hopping”, adjusting the smoothness of the line, and customizing the color of the line.
        • New technology domains for the Topology editor including support for the IBM Z-series platform, "Connectivity as a Service" messaging abstractions, IBM MQ® Series messaging platform, and the Java Messaging Service (JMS).
        • New tab on Topology Status View guides you through the preparation of Topologies for automated deployment.
        • Better personalization support for diagram behaviors such as the presentation action bars, pop-up link handles, and selection fading within Topology diagrams.
        • A new welcome window to introduce the Topology editor and guide you through their first steps.
        • Improved Dependency Link creation dialog box to make link creation easier for new users, including enhanced button labels, and easier to understand preferences.
        • You can use the new Non-visualized Units action to identify orphan model units and either add them to a new or existing diagram, or remove them from the model.
        • Enhanced Topology Status view makes it easier for you to view, understand, and act on status messages provided by the validator.
        • Enhancements to performance for large topology models in the diagram editor and in the Project Explorer view.

        Back to top



        IBM Rational Modeling for Communications Applications (new installable priced feature)
        Important: A feature-specific license is required to activate these capabilities.
        By using this new installable feature, you can adopt key industry standards, frameworks, and protocols, and complete the following tasks:
        • Create visual models of Next Generation Network (NGN) converged services applications.
        • Design call flows and generate Session Initiation Protocol (SIP) Servlet-based applications.
        • Reverse-engineer call flows from actual network traffic.
        • Generate SIP test cases for IBM Rational Performance Tester.
        • Model and generate Telecom Web Services based on the Parlay X specification.
        • Jump-start your use of TeleManagement Forum's (TM Forum) Next Generation Operations Support Systems and Software (NGOSS) architectures in UML by using the provided sample model.

        Back to top



        SIP code development tools
        The SIP (Session Initiation Protocol) code development tools have been extended to support the JSR 289/SIP 1.1 Servlets specification, and include the following new features and enhancements:
        • Project creation wizard to support the creation of SIP 1.1 projects
        • Servlet creation wizard to support the creation of SIP 1.1 Servlets according to the JSR 289/SIP 1.1 Servlets specifications.
        • New Deployment Descriptor Editor support for SIP 1.1
        • Import and export of SAR (SIP archive) files for SIP 1.1 projects.

        Back to top



        UML Profile-based Integrated Architecture (UPIA) (IAM2)
        The UML Profile-based Integrated Architecture (UPIA) feature has been upgraded to support DoDAF 2.0 and to improve usability. In addition, the UPIA explore tools on the diagram palette now support custom queries for populating diagrams. For detailed information, see the Rational support document, "Changes to the IBM Rational UML Profile-based Integrated Architecture (UPIA) feature in V7.5.4," at http://www.ibm.com/support/docview.wss?rs=3539&amp;uid=swg27016194.

        Back to top



        3GL Domain modeling
        New pop-up menus are now available from the Package or Project Explorer view and in domain modeling class diagrams. You can now delete domain modeling elements from both a class diagram and the project or from only the diagram.

        Back to top



        EJB 3.0-to-UML and JPA-to-UML transformations
        In EJB 3.0-to-UML and JPA-to-UML transformations, a new option is available for using deployment descriptor files (orm.xml) to generate corresponding JPA stereotypes in the target UML elements.
        When you create a transformation configuration for these transformations, on the Main page of the transformation configuration editor, select the Use a deployment descriptor to generate UML elements check box.

        Back to top



        Java domain modeling
        • A new option is added to the Java domain modeling Preferences page and you can now decide to show or hide annotation compartments of Java classifiers in domain modeling class diagrams.
        • A pop-up editor is now available for Java classifiers in domain modeling class diagrams. When you select a Java class or interface in a class diagram, a code editor pops up for you to edit the Java code.
        • Relationships between UML model elements and domain modeling elements are now supported.
          You can also show relationships between elements from different domains, for example, between WSDL and Java elements in a domain modeling class diagram.
        • A new Preferences option is added for you to filter elements in static method sequence diagrams.
        • The Java domain modeling capabilities are enhanced for you to complete the following tasks:
          • Visualize projects and show project dependencies based on Java class path.
          • Visualize package dependencies.
          • Visualize package and project contents in a new or open diagram from the Project and Package Explorer view.
          • Visualize the contents of a Java project, package, and classifier in a new class diagram by using the pop-up menu from a open class diagram.
        • When you right-click a Java classifier in a class diagram and then click Navigate > Navigate to source, the Java editor opens just below the diagram.

        Back to top



        Java EE Connector (J2C) Tools
        • The following Websphere Adapters are updated from v6.2.0.2 to v6.2.0.2_IF01:
          • Adapter for SAP Software
          • Adapter for Siebel Business Applications
          • Adapter for Oracle E-Business Suite
          • Adapter for JD Edwards EnterpriseOne
        • The following WebSphere Adapter is updated from v6.2.0.1 to v6.2.0.1_IF01:
          • Adapter for PeopleSoft Enterprise
        • This refresh also contains the SAP BAPI Monitor fix which is required to run the inbound adapter monitor application for WebSphere Business Event and WebSphere Business Monitor.

        Back to top



        Java EE Tools
        Using the MANIFEST.MF editor and annotation exclusion tool, you can indicate files that you want to exclude from annotation scanning.

        Back to top



        Java transformations
        • A transformation configuration option is now available to generate associations automatically when you run a Java-to-UML-transformation. The transformation generates one directed association for each Java field. To be consistent with existing transformations, by default, this option is not enabled. To select this option, on the Main page of the transformation configuration editor, select the Generate a UML association for each Java field check box.
        • For UML-to-Java transformations, an option to link all generated Java code elements to the corresponding UML model elements is now available. This feature is useful when code is added to the generated Java code and the UML model, but there is no link between the added code in these models.
          When you create or edit a UML-to-Java transformation configuration, to link the generated Java code elements to the corresponding UML elements, in the transformation configuration editor, click Link Java to UML.
        • Several Java interfaces are now available to provide more flexibility for authoring Java transformation extensions.
        • Authors of Java transformation extensions can access or override the following interfaces in the transformation context:
          • com.ibm.xtools.transform.java.common.util.IRootCertifier: Use this interface to redefine the root element of a Java transformation.
          • com.ibm.xtools.transform.uml2.java5.util.ICompilationUnitSerializer: Use this interface to customize how elements are written out.
          • com.ibm.xtools.transform.uml2.java5.util.IMergeUtility: Use this interface to customize how elements are merged.
          • com.ibm.xtools.transform.uml2.java5.util.IUML2JavaAPI: This interface provides functions for creating new compilation units, type references, and for setting the body of a Java method to a string. Transformation extension authors should not override this interface.
          • com.ibm.xtools.transform.java.uml.util.IJavaUMLAPI: This interface provides functions for adding filters to the Java-to-UML transformation merge utility. Transformation extension authors should not override this interface.

        Back to top



        Pattern and transformation APIs and authoring tools
        • Public API for transformation configurations has been expanded: You can now create and validate transformation configurations by using new methods in the utility class named com.ibm.xtools.transform.core.config.TransformConfigUtil. The new method for creating a transformation configuration requires an IFile parameter that represents the workspace file for the transformation configuration.
          The methods in this class that create transformation configurations no longer validate the transformation configurations automatically; you must use the validateConfiguration method to do so.
        • Transformations can now update the progress bar that the progress dialog box shows when a transformation runs. To do this, you can add the new rule named com.ibm.xtools.transform.core.UpdateProgressMonitorRule to the transformation source code. This feature provides you with more accurate information about how much work the transformation must complete.
        • The transformation configuration editor has been converted to a form-based editor that supports both form-based and non-form-based pages. The editor now displays non-form-based pages on a white background to provide a consistent look with the form-based pages.
          Transformation authors can now contribute form-based pages by using a new class named com.ibm.xtools.transform.ui.AbstractTransformConfigFormPage in the public API.
        • You can now specify the location of log files that are used for debugging transformations.
          To configure this preference, complete the following steps:
          1. Click Window > Preferences.
          2. In the Preferences window, expand Modeling; then click Transformations.
          3. In the Location of debug logs field, specify a folder on the file system.
          Each time a transformation runs, a log file is generated in the location that the preference specifies.
          To open a log file, in the transformation configuration editor, click the corresponding icon that is located in the shared header of the transformation configuration editor.
        • When debugging a transformation, transformation authors can now view the sorted contents of a transformation context. A logical structure has been provided for transformation contexts:
          • The context is now shown as a flat, alphabetical list of property identifiers and values, instead of using the structure of a HashMap.
          • When you debug a transformation, in the Variables view, click Show Logical Structure. When you expand a variable that represents a transformation context, the context is displayed by using the logical structure.
        • Authors of transformations or transformation extensions can determine whether a property is available for use by the current transformation configuration by using methods from a new utility class named com.ibm.xtools.transform.core.extension.TransformExtensionUtil. The property is available if it is defined by the transformation or by an extension that is enabled in the transformation configuration.

        Back to top



        Profile tooling generator
        When you execute the Generate Tooling Code command, you are now presented with a number of dialog boxes, asking if you want to overwrite each of the following files: plugin.xml, plugin.properties, and the template model. The purpose of the warnings is to inform you that these files are about to be overwritten, in case you manually modified these files and want to maintain their customization. There is an issue with accidentally overwriting the plugin.properties files. For more information, see http://www.ibm.com/support/docview.wss?uid=swg21403692.

        Back to top



        Rational RequisitePro integration
        • The process for opening a Rational RequisitePro® project has been improved to optimize the loading speed of projects, including complex package structured projects.
        • The Rational RequisitePro linking performance has also been improved to reduce the time to link and unlink requirements and domain elements

        Back to top



        Rational Rose model import
        • To avoid model validation error IRJA0232E, you can select the Add create keyword to the trigger for the transitions originating from Start State option in the Rational Rose Model Import wizard preferences page. This option adds a create keyword for the trigger that is linked with the transitions originating from the initial node.
        • To avoid model validation error IRJA0131W, the Rational Rose Model Import adds events to the triggers to the imported model based on the following rules:
          • Events in Rose with name equals to When are converted to a Change Event. The parameter of the events is copied to the associated opaque expression.
          • Events in Rose with name equals to After or At are converted to a time event. The parameter of the events is copied to the associated time expression.
          • Any event other than When, After, or At cannot be termed as any specific event. In this case, you can select the option from the Convert unmapped State Machine Transition Events to menu in the Rose Model Import wizard preference page and convert the event.
        • The Rose Model Import wizard now supports the pathmap-based profiles for the custom properties in the imported Rose model. The enhancement covers the following changes:
          • To import Rose custom property set or custom stereotype as profile, you can now use any pathmap variable defined in the preferences page (Window > Preferences > Model > Path Maps).
          • You can also reference available pathmap-based profile. The Rose Model Import wizard allows mapping of Rose custom property set or the Rose stereotype to the compatible deployed profile using pathmap.
        • The Browse for Profile dialog box has been enhanced so you can navigate to the deployed profile and reference the profile through pathmap.

        Back to top



        Rational System Architect integration
        The Rational System Architect import and export wizards have been enhanced to support both the predefined system architect multiplicity names (as before) and the general UML multiplicity format "N..M", such as "1..5". These import and export wizards are available only on Windows systems.

        Back to top



        Rational Team Concert Client integration
        Beginning with version 7.5.4, the product is updated to support the following versions of Rational Team Concert Client:
        • Rational Team Concert Client 2.0.0.1
        • Rational Team Concert Client 1.0.1.1 iFix001
        The product continues to package Rational Team Concert Client 1.0.1.1 iFix001 as an installable feature.

        Back to top



        Traceability
        Traceability now supports tracing to Rational Team Concert work items and Rational Requirements Composer requirement specifications through a new type known as a URL link. A client can create a URL link via the product UI (pop-up menus and the tool palette) much like a URL. In traceability, URL links are treated as specifications. URLs are treated as suppliers in traceability queries and analysis rules.

        Back to top



        UML model analysis and metrics
        • There are several new UML model metrics in the Coupling category:
          • Abstractness: Use this metric to calculate the ratio of abstract and interface classes to the total number of classes in a package and its subpackages.
          • Afferent coupling: Use this metric to count the number of classifiers that a classifier references; that is, the afferent coupling. This metric examines the following outgoing relationships: inheritance, dependency, attributes type, and operation return and parameters type. The parent nodes show the average of the results for the child nodes.
          • Efferent coupling: Use this metric to count the number of classifiers that reference a classifier; that is, the efferent coupling. This metric examines the following incoming relationships: inheritance, dependency, attributes type, and operation return and parameters type. The parent nodes show the average of the results for the child nodes.
          • Instability: Use this metric to calculate the ratio of efferent coupling to the total coupling (afferent plus efferent). Greater the package dependencies, more instable the package is, that is more likely it is to change when one of its dependencies change.
          • Normal distance: Use this metric to calculate the normalized distance to the main sequence. The main sequence is where abstractness and instability are balanced. This means that a totally concrete package should have a few dependents while a totally abstract package should have many, or incoming dependencies should be proportional to the abstractness of the package. The parent nodes show the average between its own result and the child nodes results.
        • Several changes had been made to the UML model metrics in the Sizing category:
          • The rolling-up of all the rules starting by Number has been changed to sum instead of average.
          • All the rules have been duplicated into a new set starting by Average where the rolling-up is now average.
        • There is a new rule in the Completeness category:
          • Orphaned Elements: Use this rule to identify elements without relationships to other elements. Elements that are flagged as orphaned might be good candidates to delete from the model.
        • There is a new Coupling review category with two rules:
          • Cross-Model Dependency: Use this rule to identify the classifiers in a logical model that reference classifiers in a different logical model (model or package).
          • Cross-Package Dependency: Use this rule to identify the classifiers in a package that reference classifiers in a different package. Select No in the Include Sub Packages section to exclude subpackage dependencies from being flagged.

        Back to top



        UML modeler
        • URL and URL links can now have a display name. If set, display names are used by default throughout the product UI (the Project Explorer view and diagrams). If not set, the URL expression is used instead, as in prior product versions.
          As part of this feature, URLs and URL link properties, like their display name, can now be edited on the Properties view on the General page. In addition, URL and URL links have icons which can be edited from the Properties view.
        • URLs and URL links can now be linked to individual elements in a workspace.
          You can browse the workspace and create or edit URL and URL links to individual elements in the workspace, including model elements through a new Select Element dialog box launched from either the Create URL/URL link dialog box or the URL/URL link properties view. URL and URL links referencing model elements are non-semantic references.
        • Added tooling for detecting and resolving cases where duplicate GUIDs are found in the same logical model. A validation constraint checks for duplicate GUIDs for logical content in a given selection, and a new action has been added to the Modeling context menu that can allow the user to resolve the conflict through a dialog box launched from this action.
        • It is now possible to obtain modeling references to multiple modeling elements. Previously, you could only obtain modeling references to single modeling elements, for example by right-clicking on a single element and choosing Modeling references from the pop-up menu. The new functionality allows you to select multiple elements and obtain references to them.
        • Attributes from stereotypes can now be show or hidden on the diagram elements.
          In addition to controlling the visibility of these stereotype attributes per instance shape, the user can also set the default visibility behavior through modeling preferences.
        • When adding a Stereotyped class in a class diagram, you can use the pop up list to select from applicable stereotypes that are now in alphabetic order. In addition, you can also sort the Stereotype and Profile columns in the Apply Stereotype dialog box. By default, elements in this dialog box are sorted by the Stereotype column.
        • The visualization of return messages on sequences diagrams has been improved: they can now clearly be identified as dotted on display and on print.
        • You can now attach documentation in rich text to UML diagrams just as how they would attach documentation to other modeling elements.
        • You can now visualize Java binary classes that are related UML modeling elements, using the Show Related Elements functionality.Now you can localize your UML models by using an automated and simplified process.
        • The process of localizing UML models can now be done in three simplified steps:
          1. Localization export functionality exports localizable strings from a model into a .properties file.
          2. Translators translate the .properties file into another language.
          3. Localization import functionality imports the translated .properties file back into the model to be localized.
        • The XML Metadata Interchange (XMI) import feature has been enhanced to better support real-world XMI serializations of UML 2.1 models produced by other tools. It is more forgiving of nonstandard XMI extensions created through the export capabilities of other products. For example, it better handles models exported by Sparx Systems Enterprise Architect, No Magic MagicDraw, and IBM Rational Rhapsody®, including models with nested and external profiles. Problem reporting and robustness is improved when dealing with unrecognized or malformed content.


        Back to top



        UML compare and merge
        • A new conflict detection strategy for Opaque elements like Opaque Expressions, Opaque Behaviors, and Opaque Actions is introduced for Opaque elements with the same signature. This support is also extended to add deltas of classes, interfaces, class operations, and class attributes. In addition, merge as text for opaque element's body is also introduced.
        • Text sub merge compare viewer is added in the bottom half of the Compare editor for opaque elements with language body conflicts that can be toggled from Visualization of Structural changes pane, and provides enhanced sub merge usability such as swapping left and right text panes and committing or discarding sub merge results by using the new buttons added to the Text sub merge compare viewer.

        Back to top



        Web Development Tools
        • New installable feature: Communication Enabled Application (CEA)
        This feature provides a set of tools for developing communications enabled applications based on the WebSphere Application Server Feature Pack for CEA.The tools include a facet that installs the CEA widget library into your Web project, palette drag and drop support for CEA widgets into the Web page editor, and content assist and validation in the Web page source editor.
        • New feature: iWidget
        This feature provides tools for developing iWidget applications. The tools include a facet that installs the iWidget library into your Web project, an iWidget creation wizard that assists you with creating a new iWidget based on templates provided, an iWidget editor that includes validation function, and a Universal iWidget Test Client that assists you with testing the iWidget, the markup, and the event handlers.

        Back to top



        Web publishing
        • You can now specify the navigation style of the published model by using the documented ANT task com.ibm.xtools.publish.CLModelPublish. Previously, the default navigation style was of type Javadoc, but you can now publish models by using Interactive Tree layout with the ANT task.
        • Web published models now show the multiplicity of operation parameters. Previously, if an operation had parameters with a defined multiplicity, there would be no way to show these in web published models.
        • URL display names are now published in URL hyperlinks when publishing a model containing URLs with display names and the Create Links option selected. If no display name is set, the URL expression itself is hyperlinked. If the Create Links option is cleared, only the non-hyperlinked URL expression is published instead.
        • The new type URL link is now published in Modeling Web Publish output. They are published under the same table as URLs and their display names are published in hyperlinks if they contain display names and the Create Links option is enabled. If neither a display name is set or Create Links option is enabled, the URL expression of the URL link is published.

        Back to top



        XML Tools
        The XML to XSD generator wizard can now produce schema documents using complex type definitions with simple content. The wizard now also provides an option to persist the generation settings and automatically apply them in future invocations.

        Back to top

        Version 7.5.3
        Download Version 7.5.3


        This release of Rational Software Architect for WebSphere Software contains new features and enhancements in the following areas:


        Eclipse platform updates
        The following Eclipse 3.4.2 patches and fixes are included in this release:
        Back to top



        IBM Runtime Environment for Java Technology updates
        IBM Runtime Environment for Java Technology is updated to the following versions for Windows ® and Linux operating systems:
        • IBM 32-bit Runtime Environment for Windows, Java Technology Edition, Version 1.6 service release 5
        • IBM 32-bit Runtime Environment for Linux, Java Technology Edition, Version 1.6 service release 5

        Back to top



        IBM WebSphere Application Server test environment updates
        The following IBM WebSphere Application Server 6.1 Test Environment updates are available:
        Back to top



        Application Build
        You can export an SCA archive from the command line using the new Ant Task scaArchiveExport. The Ant task performs the same operation as the Export SCA artifact wizard.

        Back to top



        Java EE Connector (J2C) Tools
        • The following IBM WebSphere Adapters have have been updated to version 6.2.0.2:
          • IBM WebSphere Adapter for JD Edwards EnterpriseOne
          • IBM WebSphere Adapter for JDBC
          • IBM WebSphere Adapter for SAP
          • IBM WebSphere Adapter for Siebel
          • IBM WebSphere Adapter for Oracle
          For information about supported software for IBM WebSphere Adapters, see the following Web address: http://www-01.ibm.com/support/docview.wss?rs=695&uid=swg27006249
        • ECIResource Adapter is updated from version 7.1.0.2 to 7.1.0.3.
        • The J2C Bean wizard now gives you a warning message if the EJB3 feature pack for WebSphere Application Server 7.0 is not installed. (The EJB3 feature pack is required for the inbound adpater-monitor - WebSphere Business Event and WebSphere Businss Monitor - support.)
        • J2C tools provide WebSphere Business Event (WBE) V6.2.0.1 support. You can generate an inbound WebSphere adapter-WBE application using the J2C bean wizard.
          The application generates a Common Base Event (CBE) that is consumed by WebSphere Business Event product.

          A new menu option appears when you right-click on the generated inbound session bean (WBE enabled): click Source > Generate Event Mapping.

          This option generates two files -EventBOTypeMapping.xml and EventBOTypeMapping.xsd - in the same location as the schema files.

          The EventBOTypeMapping.xml file contains information about the eventName and the schemas to be consumed by the WebSphere Business Event Design Data, which in turn is used in the WBE Project.

          This integrated solution of the three products enables users to monitor inbound events from an Enterprise Information System such as SAP and PeopleSoft via JMS Topics.

          The following IBM WebSphere adapters included in version 7.5.3 support the Websphere Business Event:ns:
          • IBM webSphere Adapter for JD Edwards EnterpriseOne V6.2.0.2
          • IBM Websphere Adapter for PeopleSoft V6.2.0.1
          • IBM Websphere Adapter for SAP V6.2.0.2
          • IBM Websphere Adapter for Siebel V6.2.0.2
          • IBM Websphere Adapter for Oracle V6.2.0.2

        Back to top



        Java transformations
        The following enhancements have been made to Java transformations:
        • Several profile changes have been made to assist in modeling for UML-to-Java and Java-to-UML transformations:
          • If The <<JavaWildcard>> stereotype may now be applied to a UML class allowing a wildcard to be the type of either a typed element of multiplicity or for a typed element with a <<JavaCollection>> stereotype.
          • The current <<JavaCollection>> stereotype has been deprecated, and a replacement added with the same name that allows the key type property used in Map collection to be a UML type instead of a string. This would allow a <<JavaWildcard>> UML class to be the keytype of a Map.
          • A new stereotype <<JavaRedirect>> has been added that can be applied to any UML type. It has a single property called "redirect" that will redirect to any other UML type. The UML to Java transformation will generate all references to the <<JavaRedirect>> as the redirected type instead. This allows for any type to be specified as a UML template parameter, for the purposes of Java code generation.
        • A new extension has been added to UML-to-Java transformation that can be enabled in a UML-to-Java transformation configuration. This extension generates the names of all getters and setters by using the get/set<field name first letter uppercase> string, rather than following the Java naming conventions. This can result in a difference for getters and setters of boolean fields.


        Back to top



        Patterns and transformations
        The following enhancements have been made to transformation configuration:
        • For transformation configuration inheritance there is a new API for getting and setting values in the inheriting transformation configurations. Y
        • You can now write pages that display in the transformation configuration editor or wizard and support inheritance.

        Back to top



        Struts tools
        A new Workspace preference is available that, when enabled, displays a dialog box to warn you when your workspace contains a Struts 1.1 or 1.0.2 project.. To enable this preference, click Window > Preferences > Struts and then select Warn about Struts 1.1 security vulnerabilities.

        Note: Regardless of whether you enable this new preference, if your workspace contains a Struts 1.0.2 or 1.1 project, a warning marker will display on the project in the Enterprise Explorer view and the Problems view.

        Back to top



        UML-to-XSD and XSD-to-UML transformations
        UML-to-XSD and XSD-to-UML transformations have been enhanced to support the generation of restrictions for complex types.
        • A change has been made to the behavior of the UML-to-XSD transformation with respect to the handling of generalization relationships between two complex type classes:
          • If a generalization relationship has no stereotype, it is transformed to an XSD "extension".
          • If a generalization relationship has "restriction" stereotype, it is transformed to an XSD "restriction".
        • The XSD-to-UML transformation generates the "restriction" stereotype when processing a restriction relationship, but does not generate any stereotype when processing an extension relationship.

        Back to top



        XML Web Services Tools
        When generating Java SDO code from XML schema documents, you can now choose the compiler compliance level. By default, the compliance level is set the same as the level of the target project for the generated code. To change the compliance level, click Advanced in the XML Schema to Java SDO wizard to reveal the compiler settings.



        Version 7.5.2
        Download Version 7.5.2


        This release of Rational Software Architect for WebSphere Software contains new features and enhancements in the following areas:



        Additional Eclipse patches and fixes
        In this release, Eclipse platform is updated to Eclipse 3.4.2. For more information, see the Eclipse 3.4.2 Project Release Notes.
        The following Eclipse 3.4.2 patches and fixes are included in this release:
        • Eclipse platform: Bugzilla fix 266538
        • Graphical Modeling Framework (GMF): Bugzilla fixes 243187, 266004, 266025
        • Test and Performance Tools Platform (TPTP) Project: Bugzilla fixes 135710, 244203, 262975, 265987
        • Equinox Project: Bugzilla fixes 265340, 267141, 267518
        • Patch for Java Development Kit (JDK): Bugzilla fix 263094
        • BIRT Chart Runtime and Report Runtime Environments: Bugzilla fix 266914

        Back to top



        Updates to supported operating systems
        Beginning with version 7.5.2, the following additional operating system version is supported:
        • Red Hat Enterprise Linux® 5 Update 3

        Back to top



        Updates to supported Web browsers
        Beginning with version 7.5.2, the following additional Web browser version is supported:
        • Mozilla Firefox 3.0 with updates

        Back to top



        IBM Runtime Environment for Java Technology updates
        IBM Runtime Environment for Java Technology is updated to the following versions for Windows ® and Linux operating systems:
        • IBM 32-bit Runtime Environment for Windows, Java Technology Edition, Version 1.6 service release 4
        • IBM 32-bit Runtime Environment for Linux, Java Technology Edition, Version 1.6 service release 4

        Back to top



        New installable feature: Java client application editor
        The feature provides tools for building and testing graphical user interface Java client applications by using the SWT, AWT, or Swing UI libraries.

        Back to top



        New installable feature: Service Component Architecture Development Tools
        The feature provides a concise set of tools for developing Service Component Architecture service components implemented with annotated Java, for graphically wiring components together to form new composite services, for associating protocol bindings and quality of service intents to Service Component Architecture components, and for packaging Service Component Architecture assets and deploying them to the WebSphere Application Server.

        Back to top



        Rational Requirements Composer integration
        Now links attached to Rational Requirements Composer elements are transformed to UML comments with a Link stereotype applied. The Link stereotype adds two attributes: title, an optional alternative link title, and relation, an optional relationship type of the given link. Information from Rational Requirements Composer is preserved in these attributes.

        Each BPMN Collaboration participant is transformed into UML as follows:
        • A UML collaboration role attribute is created per participant.
        • A UML interface is created per BPMN process and participant pair. This interface will be the type of the respective role in UML collaboration.
        • Each such interface will contain a UML operation per BPMN task on the respective BPMN process.
        • Each such UML operation will have in or out parameters, if respective BPMN task was connected to or from a data association leading to a Data Object

        In this release for each Data Object, the transformation will create a class, and place it into the Common Classifiers folder under the root model. This class will be used to type the input and output pins created on connected activity nodes, as well as UML operation parameters for the interface which represents the UML activity.

        A new Navigate to Requirements Composer pop-up menu is available in the Project Explorer view for the UML elements transformed from composer artifacts, such as actors, use cases, and BPMN artifacts. This action opens the Rational Requirements Composer client and displays the original artifact.

        Back to top



        Rational Team Concert client integration
        It is now possible to create Rational Team Concert work items from modeling markers. The work item descriptions are initially populated with information pertaining to the selected markers. The descriptions also include hyper links to the modeling elements in the workspace to support easy navigability. In addition, it is possible to drag and drop modeling elements from the Project Explorer view into the work item description to create additional hyper links.

        This functionality is enabled by default when the Rational Team Concert Client feature is installed by IBM Installation Manager. You can create work items from the pop-up menu of a modeling reminder in the Tasks view or a modeling validation error or warning in the Problems view.

        Back to top



        Rational Rose model import
        • The Rational Rose® Model import model sharing feature is enhanced to support the following capabilities:
          • Nested Rose subunits whose parent subunit is imported as new model, can now be shared with existing models.
          • Rose subunits can now be shared with models from multiple modeling projects.
          • The Rose Model Import wizard now automatically finds out and marks the subunits that can be shared during import. If you do not want to share any of the shared subunits, you can change to desired conversion choices.
          • When a subunit is shared with existing models/packages, all the nested subunits are disabled as that is implicitly taken care of by the mapped shared model for the top level subunit.
        • The Rational Rose Model import subunits conversion feature is enhanced to support the following capabilities:
          • Rose subunits can be imported as top level root package.
          • Rose subunits can be shared with existing top root level package from multiple modeling projects. .

        Back to top



        Transformation core
        Transformation configurations can now inherit values of properties from each other. If multiple transformation configurations share the value of a specific property, you can set the value in the parent transformation configuration, and the updated value propagates automatically to the child transformation configurations.

        Back to top



        UML-to-EJB and UML-to-JPA transformations
        Now the UML-to-EJB and UML-to-JPA transformations have the option to generate the JPA annotations in the deployment descriptor (orm.xml and persistence.xml files) or in the Java code as before.

        Back to top



        UML Profile-based Integrated Architecture (UPIA)
        The UML Profile-based Integrated Architecture (UPIA) (IAM2) feature has been upgraded to improve usability. In addition to some minor profile and tooling changes, all of the UPIA constraints were examined and updated with descriptive messages.

        Back to top



        UML modeler: activity diagram
        The expansion region and expansion node elements are now supported in activity diagrams. The Expansion Region creation tool is found in the Structured Activity Node palette stack in the Actions palette while the Expansion Node tool is in the Object Node stack in the Activity palette.

        Back to top



        Java EE tools
        • In the Enterprise Explorer view, you can now choose to display Java EE projects grouped together by project type.
        • Simple validation support for Java EE 5.0 has been added for EAR, EJB, Web and Application Client projects.
        To validate the project, right-click and select Validate.  Also, the validators run automatically if the Build Automatically workspace preference ( Window > Preferences > General > Workspace) is turned on.

        Back to top



        Portal tools
        From the product workbench, you can now start or publish to installations of IBM WebSphere Portal servers that have profile names other than the default name of "wp_profile".

        Back to top



        Ant tasks
        Ant tasks related to workspace preferences are improved to support Eclipse preference files (epf).
        • A workspacePreferenceExport task is added to export preference files in an Eclipse preference file format.
        • The workspacePreferenceFile task can read an Eclipse preference file.
        • The workspacePreferenceGet and workspacePreferenceSet tasks can get or set preferences in a format compatible with the Eclipse preference files.

        Back to top




        Version 7.5.1
        Download Version 7.5.1


        This release of Rational Software Architect for WebSphere Software contains new features and enhancements in the following areas:



        IBM Runtime Environment for Java Technology updates
        IBM Runtime Environment for Java Technology is updated to the following versions for Windows ® and Linux ® operating systems:
        • IBM 32-bit Runtime Environment for Windows, Java Technology Edition, Version 1.6 service release 3
        • IBM 32-bit Runtime Environment for Linux, Java Technology Edition, Version 1.6 service release 3
        Back to top



        Additional Eclipse patches and fixes
        The following Eclipse 3.4.1 patches and fixes are included in this release:

        Back to top



        New splash screen
        A progress bar was added to the common splash screen that displays when an Eclipse 3.4 based product is being started.

        Back to top



        IBM Telelogic System Architect integration
        You can import a subset of the diagrams and content from UML models developed in IBM Telelogic ® System Architect into a UML model in the Rational modeling products, such as Rational Software Architect for WebSphere Software. Typically such models would be expressions of software architecture best-practice patterns that have been articulated as part of the Enterprise Architecture definition that resides in Telelogic System Architect. After the model is imported to the Rational modeling products, you can use such a model as the basis for designing a specific software solution that adheres to the best practice.

        Back to top



        Rational Requirements Composer integration
        You can import use case and process sketch diagrams that were used to capture business requirements in Rational Requirements Composer, and use the rich UML modeling capabilities to elaborate them into solution designs that fulfill the business requirements. Linkages between the Composer sketches and Rational RequisitePro ® requirements records are propagated to the UML modeling tool.

        Back to top



        Deployment architecture tools
        • You can now substitute a custom image in place of the default appearance of a unit in topology diagrams. You can select images from a set of predefined stock images or from your workspace or file system.
        • The properties of topology elements such as units and capabilities may be selected and displayed directly on the containing unit in a topology diagram. Users may select a set of available properties, which are then rendered on the figure in the diagram. Changes to the model properties will automatically update the information that is displayed on the unit.
        • Topology units now have a form-based editor to make it easier to consume and edit information about a single unit in the topology. The editor is filtered automatically in order to show the most important details of the topology. The form-based editor supports easy to read layouts for capability and requirement elements which show any attributes that are set or declared as parameters.
        • The Relationship Explorer allows you to browse the relationships of a topology element to other topology elements. For example, if you select a unit, the Relationship Explorer shows you the units that link to that unit, the units to which that unit links, the diagrams that display that unit, and so on. The Relationship Explorer is available as a stand-alone view or embedded in the new form-based unit editor, and in both cases, it shows the relationships throughout the entire workspace.
        • The new Inventory Planning Report for topologies supports high level planning sessions with commonly used information about servers, operating systems, and installed software in a topology.
        • The new Architecture Review Report for topologies supports detailed review processes for subject matter experts to focus on the relevant important details for their domains.
        • Improved Rational Asset Manager integration, including the ability to seamlessly integrate asset bindings or topology templates into the active topology editor by searching for assets and dragging them onto a topology editor canvas, as well as extensible frameworks to generate asset searches using topology units as the search input.
        • The new Storage domain model supports common types like Storage Volumes (disks), Disk Partitions, Storage Pools, and Storage Subsystems as well as improved support for mapping File systems onto Storage hardware.
        • The new Networking domain model supports common types like IPSubnet, LAN, VLAN, Gateway, Router, Firewall, Load Balancer, and Wireless Access Point.
        • The WebSphere Application Server domain is enhanced to support WebSphere Portal Server deployments.

        Back to top



        Rational Asset Manager integration
        You can now share plug-in assets using Rational Asset Manager. Plug-ins require special handling when treated as reusable assets; they must first be installed into your local workbench before you use them. Examples of typical plug-in assets would be patterns, transformations, and tooling plug-ins for custom UML profiles. With the introduction of this new integration feature, you can not only publish plug-in assets to Rational Asset Manager and use Rational Asset Manager to govern search them, but also you can search and discover assets that you want to use and have them installed in your workbench environment.

        Back to top



        Rational Asset Manager Client
        Categorization and tagging of assets is now supported in the asset publishing dialog. The new Categories tab lists all the possible subcategories than can be assigned to an asset. Note that some categories can be restricted to particular asset communities by the server. You can use the Tags tab to insert or remove tags set for the asset.

        Back to top



        WebSphere Business Modeler integration
        • WebSphere Business Modeler integration now supports models created with version 6.2 of WebSphere Business Modeler.
        • WebSphere Business Modeler integration now supports adding the implementation type of the local tasks in WebSphere Business Modeler models such as Dynamic Assembler and Human task in the form of keywords in the associated UML elements CallOperationActions/CallBehaviorActions.
        • WebSphere Business Modeler integration now supports generating CallOperationAction actions when the local human task is associated with a role in the WebSphere Business Modeler model.

        Back to top



        InfoSphere Data Architect integration
        IBM InfoSphere Data Architect is the new name for Rational Data Architect. This product includes a feature to transform a Logical Data Model into a UML class model. This complements the transformation that is packaged with the Rational UML modeling products that creates a Logical Data Model based on a UML class model. By integrating InfoSphere Data Architect with the product, you can transform a UML class model into a logical data model as supported by InfoSphere Data Architect.

        Back to top



        Transformation core
        • In a transformation configuration, you can specify that the transformation should use the workspace as either the source or target. You can configure this option on the Source and Target page of the New Transformation Configuration wizard and the transformation configuration editor.
        • The transformation debug log now contains time stamps that indicate when each transformation element runs.

        Back to top



        Transformations
        • XSD-to-UML transformation
          The transformation now generates anonymous enumerations for XSD global elements or attributes with a simple type that has an enumeration.
        • UML-to-XSD transformation
          A new sample, UML-to-XSD transformation extension, was added to the product information center. This sample demonstrates how to extend the UML-to-XSD transformation to perform post-processing operations on the generated XML Schema Definition (XSD) files before saving them.
        • UML-to-Java transformation
          • You can specify that the UML-to-Java transformation automatically adds Java project dependencies for UML references that map to Java projects other than the target project: In the transformation configuration editor, on the Java-to-UML Associations page, specify a Java-to-UML associations file; on the UML to Java options page, select the Generate Java project dependencies check box.
          • The getters and setters that the UML-to-Java transformation generate use Java development tools (JDT) naming conventions. This changes the getter names for Boolean fields if the appropriate JDT setting is enabled.
          • Support was added for Java generic bindings, Java template argument extensions, and Java wildcards. For example, transforming the following Java code from and to UML is now supported:
            Class1<X extends String & IMyString> {}
            Class2 extends Class1<MyString> {
            public Class1<MyString> myfield;
            public Class1<? extends MyString> myfield;
            public Class1<? super MyString> myfield;
            }
        • UML-to-SOA transformation
          • The UML-to-SOA transformation now generates the following components:
            • Dynamic Assembler implementation type SCDL components
            • Human task implementation type SCDL components
          • When the UML-to-SOA transformation generates output in the workspace, it creates WebSphere Integration Developer library projects that have unique names. If a WebSphere Integration Developer library project with the specified name already exists in the workspace, the transformation merges or overwrites this project, depending on the value of the merge option in the transformation configuration. If the transformation creates a library project that has a name other than what is specified in the UML source model, the transformation adds a warning message to the error log.
          • If you have uncommitted changes when you run the UML-to-XSD, UML-to-WSDL, or UML-to-SOA transformations, you will receive a prompt to save the appropriate files. If you confirm the save operation, the transformation continues to run. If you cancel the save operation, the transformation stops running and adds an error to the log file.
        • UML-to-JPA and UML-to-EJB 3.0 transformations
          • The UML-to-JPA and UML-to-EJB 3.0 transformations now contain the following functionality:
            • Wizards to reverse engineer database tables from either a live connection or ddl, and create corresponding UML elements with the correct stereotype and properties
            • Capability of the transformation to add different constraints to validate the correct values of the table/column names and primary keys
            • Enhanced property pages and wizard pages for the entities and properties inside the entities. These pages simplify how to apply and configure stereotypes, and provide content assistant functionality in the available table/column names
          • The UML-to-JPA and UML-to-EJB 3.0 transformations support the following items:
            • Reverse transformation of Entity relationships
            • Transformation and reverse transformation of join table and join column
            • Enhanced property pages for the association to facilitate the configuration of join column and join table
          • The EJB 3.0/JPA Palette now supports the following relationships:
            • Entity
            • Inheritance
            • Interceptors
            • Realization.
        Back to top



        UML modeler
        • Support for an active language has now been added.
          To modify the active language default settings, complete the following steps:
          1. Click Window > Preferences.
          2. In the Preferences window, expand Modeling and click Active Language.

          In addition, you can add multiple languages to a constraint from the Properties view.
        • You can change the line width for connectors in the diagram editor.
          To change connector line width, in the diagram editor, right-click a connector; then click Format > Line Width and select the appropriate size.

          To change the line width from the Properties view, select the connector, open the Appearance tab and click the Line Width button.
        • An Open All Sub-Fragments option was added to the pop-up menu of fragments in the Project Explorer view.
          To open all sub-fragments, in the Project Explorer view, right-click a fragment that contains other fragments and click Open All Sub-Fragments.
        • Public API was added for Redefinition support (com.ibm.xtools.uml.redefinition).
        • A preference was added to control expanding the message to the length of the message to display the full method signature's text.
          To modify this preference, complete the following steps:
          1. Click Window > Preferences.
          2. In the Preferences window, expand Modeling and UML Diagrams; then click Sequence and Communication.
          3. Select Set initial message label width to distance between source and target lifelines.
        • You can now upgrade a model and all the fragments that it owns to the latest version of the product at the same time, instead of individually.
          Upgrading a model and its owned fragments at the same time saves time and memory resources because the model and fragments do not have to go through the silent migration process each time that you load the model.

          To upgrade a model and its owned fragments at the same time, complete the following steps:
          1. Open the model to upgrade and ensure that you have both read and write access to all the owned fragments.
          2. After the model fully loads, in the Model Editor view, click the Details tab.
          3. Under Model Operations, click Upgrade. The Upgrade Model window opens and warns that the product might appear unresponsive for an unknown length of time, and that you should not interrupt the process until the migration is complete.
          4. To upgrade the model and its related fragments, click Yes.
        • In communication diagrams, you can choose from a list of operations when you assign operations to messages. This is consistent with sequence diagram behavior.
        • A preference was added to specify whether colors of stereotype images are preserved.
          To modify this preference, complete the following steps:
          1. Click Window > Preferences.
          2. In the Preferences window, expand Modeling and Appearance; then click Shapes and select Retain original colors of stereotype images.
        • Event management has been improved:
          • A validation rule has been developed to find unreferenced events in models. This rule initially only examines in-memory models. To search all models in the workspace, open the Quick Fix dialog box from a problem corresponding to this rule. You will then be given the option to search for all unreferenced events for all models in the workspace. You can also use the Quick Fix dialog box to delete the unreferenced Events.
          • The Refactor or Delete operation for collaboration elements, interaction elements, and other sequence diagram elements now verifies if events will become unreferenced after a Delete operation. Events which will become unreferenced are listed in the Preview page of the Refactor wizard. You can clear the check boxes corresponding to the events you want to keep. Also, the Refactor or Delete action can now be started from the sequence diagram in addition to the Project Explorer view.
          • You can now reuse events. The Properties view for message elements now contains a new section that lists associated events for the selected message. From this section, you can select applicable events for the message.
          • Refactor and Move operations are now supported for collaboration and interaction elements.
        • When you add a state to an object node typed by a classifier, you can now select only valid states.
        • The operations property tab contains a column that displays the owner of the operation.
          You can use this column to determine which operations are local and which are inherited.
        • Show Related Elements, Show/Hide Relationships, and topic diagrams now support link relationships.
        • Memory optimizations have been implemented to assist with loading and validating larger models.
          To take advantage of these optimizations, you can add one or both of these parameters to the eclipse.ini configuration file:
          • Dcom.ibm.xtools.trimResourceIdToEObjectMap=1
            Adding this parameter will only populate the entries of the map on demand (i.e. when something is requested from the map). It assumes no clients are requesting the map directly.
          • Dcom.ibm.xtools.modeler.disableAdapterMapsDuringFragmentLoad=1
            Adding this parameter will free up the adapter maps before loading, then repopulate them after the loading is complete. This results in more available memory during the load and validation.
        • The Format > Snap Back command is now supported on state machine diagrams.
          This command "snaps" the name back to the diagram element that it is associated with.
        • The Navigate > Show in > Project Explorer command from the diagram editor now takes context into account.
          This command now locates the corresponding element under the nearest imported element in scope, using the diagram as the context.
        • State invariant elements are now supported in sequence diagrams.
          To add a state invariant, in the Sequence Palette, click State Invariant and then click an existing lifeline in the sequence diagram.

        Back to top



        Graphical code editing
        • Graphical code editing core
          • You can now rename class diagram files in the Project Explorer view.
          • You can now customize the palettes based on the project and the class diagram, such as one diagram with Java and JPA palettes and a different diagram with Java and Web Services palettes.
          • You can now specify the name and location of a new static method sequence diagram.
          • You can now specify the name and location of a new class diagram file when you visualize Java artifacts in a new class diagram.
          • You can now create a new diagram by right-clicking the Diagrams folder in the Project Explorer view.
        • JAX Web service modeling
          • Java EE 5 provides a robust platform on which you can build and deploy Web services. You can build Web services with either regular Java classes (POJO) or EJB 3.0 stateless session beans.
          • A new JAX Web service modeling (graphical editing) capability supports creating JAX Web service from a class diagram. It also supports promoting any POJO method to JAX Web services.
          • Java 5 annotations will be shown in a different compartment, namely the Annotation Compartment, along with the attribute and operation compartments. There is a property section in the property page for the annotation. You can add or update an annotation from the property page.

        Back to top


        Data Tools
        • Data Web Services replaces DADX (WORF)
          DADX (or WORF) is replaced by Data Web Services (DWS). DWS is the next-generation solution to significantly ease the development, deployment, and management of Web services-based access to DB2 and IDS database servers. With DWS, you can take DML statements (such as Select, Insert, Update, Delete, XQuery) and stored procedure calls, and generate Web services from them without writing any code. DWS provides a complete Web service interface, including support for SOAP and REST-styled bindings.
          The generated Web services are packaged in the form of a ready-to-deploy Web application, which you can then deploy to supported application servers.
        • SQLJ Enhancements
          Five new functions have been added to SQLJ support. Each new function is activated by selecting its corresponding option in the SQLJ preferences. You can access the new SQLJ preference by selecting Window > Preference, and then in the Preferences window clicking Data > SQLJ Applications. There is no change in SQLJ processing from earlier releases if the default value for these new preferences is used.

          For EJB projects, specifying the folder to use for SQLJ generation

          In earlier releases, the SQLJ preference for the SQLJ Java source folder was not used for EJB projects. All generated SQLJ files were stored in the EJB generation folder. In this release, you can control the location of the generated SQLJ files by using the new EJB projects, folder for SQLJ generation preferences.

          Use EJB generation folder
          If selected, all generated SQLJ files are stored in the EJB generation folder. This is the default option, and is the behavior in earlier releases.

          Use SQLJ Java source folder
          If selected, all generated SQLJ files are stored in the SQLJ Java source folder that is defined for that project.

          When the preference is changed, the setting is propagated to all open EJB projects in the workspace. If needed, the generated SQLJ files are moved to the folder that is associated with the selected option.

          Validating SQLJ syntax when files are saved in SQLJ editor

          In earlier releases, errors in SQLJ clauses in an SQLJ file were detected only when the file was translated during a build. In this release, you can select the For EJB projects, folder for SQLJ generation checkbox to specify that if building automatically is not enabled in the workspace, you can validate SQLJ syntax when you save a file in the SQLJ editor.

          If you select this preference, when you save a file in the SQLJ editor, SQLJ translation occurs and any errors are reported in the Problems view. All of the results from the translation, except for the error messages, are discarded.

          Specifying default SQLJ project properties at a workspace level

          In earlier releases, you could specify SQLJ project properties only at a project level. If you wanted to use a non-default setting, you had to update the setting in each project. Now you can specify default values for SQLJ project properties at a workspace level through new SQLJ preferences.

          The default settings of the new preferences are the same as the default settings for the project properties in earlier releases.

          You can override the default settings at a project level through the project properties. You can access the SQLJ properties of a project through the Properties command on the project pop-up menu. In the Properties window, click SQLJ Applications.

          To change the project properties, select the Enable project specific settings check box and then specify the SQLJ properties for the project.

          Specifying whether to update SQLJ profiles during translation

          In earlier releases, when SQLJ files were translated, the associated SQLJ profiles were updated as part of the translation process. The updated SQLJ profiles wrote over any changes that might have been made to the SQLJ profiles as the result of a customization. In that case, you needed to customize and bind the SQLJ profiles again. With a new preference, you can control whether SQLJ profiles are updated during translation.

          You can override the default preference setting at a project level through the project properties. You can access the SQLJ properties of a project through the Properties command on the project pop-up menu. In the Properties window, click SQLJ Applications.

          If the Update SQLJ profiles during translation check box is selected, processing is the same as in earlier releases. That is, any time an SQLJ file is translated, its associated SQLJ profiles are updated as part of the translation process. If the check box is cleared, the SQLJ profiles are not be updated as part of the translation process and any customization is preserved.

          If SQLJ profiles are not updated and an SQLJ file changes after its associated SQLJ profiles are created, the contents of the SQLJ profiles might be out of sync with their associated SQLJ file. The tooling cannot detect whether the files are out of sync. If you change an SQLJ file, you can resynchronize the SQLJ files by selecting the new Resynchronize SQLJ on Next Build command on the pop-up menu of an SQLJ file.

          After you select this command, the SQLJ file is included in the next build for the project and the SQLJ profile is updated as part of the translation process, regardless of the state of the Update SQLJ profiles during translation check box.

          Specifying whether to mark folders in the SQLJ Java source folder as derived

          Different tools can use the derived property for various purposes. For example, some library systems use the derived property to determine whether to add the resource to the library. In earlier releases, you could automatically have the SQLJ profiles marked as derived, but there was no way to specify that you wanted the folders that represent the package for these resources to automatically be marked as derived. With the new Set top folders in the SQLJ Java source folder as derived preference, you can control whether to mark the top folders in the SQLJ Java source folder as derived.

          If the Set top folders in the SQLJ Java source folder as derived check box is not selected, which is its default state, the top folders in the SQLJ Java source folder are not marked as derived. If the check box is selected, all of the top folders that are contained in the SQLJ Java source folder for a project are marked as derived. If a folder is marked as derived, all of the contents of the folder also are considered derived.

          Only folders contained in the SQLJ Java source folder are marked as derived. If the SQLJ files are not generated into the SQLJ Java source folder, folders that contain the generated SQLJ files are not marked as derived, because there also might be non-SQLJ files in those folders. For example, the SQLJ files could be generated into the EJB generation folder or into the same folder as the SQLJ file.


        Back to top



        Updates to Web Services Tools
        • The Web Services wizard now creates modules that matches with the JEE levels of the user-supplied EAR files.
        • The Create Router Modules pop-up menu now creates JAX-WS or JAX-RPC JMS Listener message-driven beans based on the type of JMS Web services that EJB module contains. A JAX-WS router module is generated if there is at least one JAX-WS Web services. Otherwise, a JAX-RPC router module is generated.

        Back to top



        Portal tools
        A new target runtime named "WebSphere Portal v6.1 Server on WAS7" is introduced to support the instances where WebSphere Portal v6.1.x (for example, Portal v6.1.0.1) is installed over WebSphere Application Server, v7.0.
        The pre-existing runtime named "WebSphere Portal v6.1 Server" should be interpreted as meaning WebSphere Portal v6.1.x installed on WebSphere Application Server v6.1 (which is the default server for WebSphere Portal server v6.1 installations).

        The new target runtime will be reflected at following dialog boxes or wizards:
        • Server runtime creation dialog in the workbench preferences.
        • Portlet project creation wizard to support the new runtime.
        • Portal project creation wizard to support the new runtime.
        • New server creation wizard to allow creation of portal server instance for server related use cases of portlet and portal projects.

        IBM Faces portlet-type is removed from the portlet-type options in the portlet project creation wizard for the WebSphere Portal v6.1 Server on WAS7 target runtime because it is not supported for this new portal server runtime.

        Back to top



        User assistance
        • A tutorial, Create a BIRT report design for a UML model, was added to the documentation. The tutorial shows how to use the Business Intelligence and Reporting Tools (BIRT) to design a report for UML models. The tutorial provides information about creating data sources and data sets to supply report content, and about using the BIRT user interface to format reports. Also read new articles on IBM developerWorks® on topics related to using BIRT to report against UML models and RequisitePro requirements.

        Back to top

        Version 7.5
        Download Version 7.5


        This release of Rational Software Architect contains new features and enhancements in the following areas:


        Deployment architecture tools
        The deployment architecture tools simplify application deployment. You can model your application and target infrastructure in the same terms. The topology editor ensures that the infrastructure meets the requirements of the application.
      • Creating and editing topologies
        You can use the deployment architecture tools to create and edit topologies and diagrams, which can describe applications and infrastructure. You can create topologies either as a representation of existing systems or in terms of the abilities of the infrastructure and requirements of the application.

        In the topology editor, you create units representing the components of your application and the available infrastructure, including the requirements, constraints, and capabilities of each resource. The tools validate your plan for deployment and guide you in configuring the application and host environment.
      • UML integration
        Topologies and UML models can interact with each other. If you have modeled your application in UML, you can import the UML elements into a topology. The topology editor is aware of connections between the UML elements and creates communication requirements to match.

        You can apply diagrams, such as sequence diagrams, to a topology to further constrain the links between units. You can also drag units from a topology into a UML model.
      • Layers of abstraction
        The topology editor includes units to represent specific operating systems, servers, and databases, as well as generic units to represent any type of operating system, server, or database. In this way, you can begin modeling at a conceptual level and move to a more specific description of the deployment instance.
      • Integration with workbench artifacts
        When you're ready to plan the deployment of a specific application, you can import application components such as EARs files, DDL files, and database connections into the topology. The deployment architecture tools examine the workbench artifact and create a matching topology unit that includes many of the attributes of the artifact.
      • Error correction
        The deployment modeling tools warn you of conflicts, unsatisfied requirements, or other potential deployment problems, simplifying the deployment process. In many cases, the topology editor can suggest and implement fixes for deployment problems.
      • Reporting
        The deployment architecture tools include report templates that use the Business Intelligence and Reporting Tools (BIRT). You can generate reports in a variety of formats from a standard template, or you can design your own report.

        Back to top


        Extensibility and pattern-based engineering
      • Model-to-model transformation authoring
        The mapping metamodel was extended to include a new mapping type: custom submap. This new mapping type enables you to invoke another transformation from within the code that is associated with a custom mapping.

        You can now change the path to referenced source or target files when a transformation is created.

        Transformation source code can be generated in a customized transformation framework. The model-to-model transformation framework was improved to support transform outputs other than existing model files. Transformation authors can set default workspace and project-specific code generation properties.
      • Model-to-text transformation authoring
        Markers on replaceable text are now more visible. They have clearly worded descriptions, and can be easily distinguished from other markers in the Problem view. In the Package Explorer and the Project Explorer views, markers, and any containing folders, are decorated with an icon that indicates the presence of replaceable text. In the JET authoring editor, actions are decorated with an icon if the corresponding templates contain markers.

        You can integrate JET with model-to-model or profile tooling using the new "UML Interface to a JET transformation wizard, which steps you through the generation of a “front-end” model-to-model transformation. You can automatically generate an EMF project, model, and Java code, generate a UML profile project, or create a model-to-model project in which the appropriate input and output metamodels are configured and the corresponding JET invocation code generated.
      • Patterns
        The design pattern content library now uses the specialized pattern framework, which handles read-only models better by ensuring that only elements in the pattern instance model of interest receive writes. Traceability support and keyword functionality for roles is now built-in to the specialized framework.

        UML profile support at authoring and application time now supports profile enumerations to be used as pattern parameters. This means that you can bind a type in a custom pattern to a type in a custom stereotype.
      • UML profiles and profiles tooling
        You can visualize stereotypes, profiles, stereotype applications, and profile applications in modeling diagrams. You can also query these types of elements in diagrams by using the Explore palette.

        The Tooling Model profile was updated to include elements that enable you to model custom properties view contributions and templates were added to support the generation of the Properties view code.

        You can now repair or remove broken profile applications from the Model Editor. In particular, the Remove button is now enabled for unresolved profiles and the Repair button is added for unresolved profiles.
      • Query
        The topic diagram wizard was updated to enable you to create new query files from registered query types. You can create custom queries as topic artifacts and preview the results in the Topic diagram.

        A new “Queries” virtual folder was added to the Project Explorer view to display all of the .tpx files as query objects that you can drag and drop on to a diagram.

        Back to top


        Model-based analytics and compliance
      • Rational Asset Manager integration
        You can integrate the Rational modeling products and deployment architecture tools with Rational Asset Manager to publish, search, and import modeling artifacts and to publish reusable topology assets.

        When models are published using Rational Asset Manager, the references are relative to the Web server.
      • Traceability analysis
        You can create dependency and traceability relationships between model elements, or their contained Operations, attributes, or parameters, directly in the Project Explorer view, without having to create diagrams.

        A Relations tab was added to the Properties view, which displays a list of all the relationships That an element is involved in. You can create, delete, or navigate to these relationships from the Properties view.
      • Model reporting
        • Improved the EMF/UML ODA datasource and dataset dialog boxes by enhancing the performance (on-demand browsing of models), the layout (resizable sections), and usability (browser contents based on model type, context sensitive xpath proposals, more xpath APIs, better xpath syntax checking.)
        • Added support for parameterized dataset for EMF/UML ODA driver. You can define parameters for a dataset, used in the xpath expressions of row and column mapping and then bound to values at runtime.
        • Removed the report generation functionality from the Report Explorer view and added a new Report Configuration Wizard. You can use the wizard to create multiple configurations with specifying report templates, source instance models, report parameters, and optional model transformations.
      • Printing
        The Print Preview functionality now takes the Scaling and Fit to page settings into account. You can change the scale factor and print to a page from the Print Preview dialog box.

        Back to top


        UML usability and model management
      • Top-level packages
        The most commonly used root element for reusable model constructs is a simple package. To support this convention, you can now define top-level UML packages as the root element, rather than Models. You can import or merge them into any number of logical models.

        You can convert a root package into a model and a model into a root package by using the Refactor popup menu in the Project Explorer view.
      • Expand in place
        The Project Explorer view and Select Element dialog box now display the imported elements for element imports and package imports. This permits you to view a collection of UML models in a hierarchical view. You can browse and work with these imported elements (including models and packages) in the importing model. You can also browse shared resources.
      • Refactoring
        When refactoring, you are now identify the resources that will be affected by pressing the Preview button. You are can also deselect closed resources to prevent them from being updated (for example, if you only have read only access to those files).
      • Expanding closed models and fragments from the Project Explorer view
        You can open closed models and fragments by expanding them in Project Explorer view. This will open the model, allowing you to browse the model elements without opening the model's main diagram or Model Editor.
      • Modeling working sets
        You can use modeling working sets to reduce the modeling content in the Project Explorer view. You specify the working sets that you want to use when you create a new model or a new profile. You can also add new or existing models to modeling working set.
      • Content filtering viewpoints
        As with the palettes and popup menus, action bars and connector flyouts reflect the capabilities that you have enabled. The Viewpoint preferences page has been updated to include Content Filter options that enable you to select the set of filters that match the viewpoint. When you change the viewpoint in the workbench, all elements in the Project Explorer view that are not included in the selected filter set are not displayed.
      • Automatic reporting and repair of unresolved references
        A new broken references dialog replaces the missing resources dialog. You can choose to repair, mark problems, or ignore the broken references. Some unresolved references shown in the Problems view can be corrected by using the Quickfix menu item.
      • Group/ungroup support
        Modeling elements can be grouped together and operations such as cut, copy, move, and delete can be performed on them.
      • Preferences
        The preferences have been rearranged in more logical groups. In addition, several new preferences have been added to control the display of compartments and titles, name and roles, multiplicity, and class shapes on use-case diagrams.

        Back to top


        UML modeling
      • Freeform diagrams
        You can now use arrowheads to show connections between the geometric shapes, and you can choose the style of line to use.
      • Activity diagrams
        Flow creation has been simplified. The Flow tool, which replaces the Control Flow and Object Flow, automatically creates the correct flow type. In addition, flow re-orienting between object nodes, control nodes and actions is now supported by automatically completing the context, such as adding pins, or morphing object flows and control flows where required. (You may re-enable the previous two flow tools by enabling the UML Activity 4 capability under UML Element Building Blocks from the General, Capabilities preference page and clicking the Advanced button.)

        To reduce the complexity of the diagram, you can hide pins on actions inside activity diagrams. You can connect flows to existing hidden pins and toggle whether pins should be hidden or shown on individual activity diagrams.all Behavior Actions and Call Operation Action names can now be kept in sync with the referenced Behavior or Operation. This will work automatically when the Call Action has a blank name. If the Call Action's name is not blank, it is reported in the Problems view.
      • Sequence diagrams
        You can now copy and paste sequence diagram elements within and between sequence diagrams, and copy and paste interactions within the Project Explorer view. The paste operation is now context aware and will reuse existing lifelines and elements when possible.

        You can refactor sections of a sequence diagram into a new sequence diagram, and the new sequence diagram can be referenced through an InteractionUse.

        Non-integer types are supported for guard conditions. Support has also been added to specify Boolean expressions in the guard condition of a loop combined fragment and to specify opaque expressions for minimum integer and maximum integer in the guard condition of a loop combined fragment.

        Message argument values can be specified using the Properties view for a message. You can add and delete argument values, change the argument type, change the argument value, reorder existing argument values, and populate argument values for all message arguments.

        Back to top


        Compare and merge
      • For a large model with many fragments, full context (logical model) merging can take a significant amount of time. Sparse model merge speeds this up significantly, as only those fragments that actually changed are loaded, along with their parent containers up to the root of the logical model. However, there are side-effects, particularly the appearance of broken references where fragments are missing. This does not affect the merge result.

        The new Text view allows you to see the full contents of multi-line text fields.

        The top level model object can be converted to UML package. Thus, we provided the ability of comparing and merging objects of these two Meta model classes.

        In activity diagrams, a control flow can be converted to an object flow and vice versa. You can compare and merge objects of these two Meta model classes.

        You can use the "-modelAlignment" option in an existing "logdeltas" command line for comparing model files with different root model ids. The logdeltas command line is used to compare two model files and output the differences in XML format. You can open and review the XML log file by using the Model Delta annotation viewer.

        You can select the base and the contributor when comparing two models. This option is on the Preference page, under General > Compare/Patch > Modeling Compare/Merge > EMF Compare/Merge.

        You can set the visibility of panes in the Combine Model dialog box to persist automatically. This option is on the Preference page, under General > Compare/Patch > Modeling Compare/Merge > Combine Models Merge.

        You can integrate the Rational modeling products with Rational Team Concert.

        Back to top


        Code-based modeling
      • Java modeling
        Several enhancements were made to sequence diagrams to support Java code modeling. You can “drill-down” selected method calls on a static method sequence diagram, create static method sequence diagrams for multiple Java methods via single UI action, or copy an interaction from the saved .dnx static method sequence diagram and paste it onto a sequence diagram in a UML model. You can also refactor method signatures.

        You can select a visualized Java element and navigate to the corresponding element in the Project Explorer view.
        Extension support allows JPA/EJB 3.0 modeling tools to reuse and extend existing Java modeling functionality.
      • JPA/EJB 3.0 modeling
        The existing Java modeling capability was extended to support the new domain modeling capability. Tools were added to the palette to support the creation of Beans (JPA Entity, JPA Entity from table, Session Bean, and Message Driven Bean), relationships between JPA Entity beans, inheritance between JPA Entity beans, and EJB reference relationships.

        Visualization of JPA/EJB 3.0 Java artifacts includes diagrammatic rendering of annotations in a new compartment.

        You can specify common EJB annotations including Security, Interceptors, and Transaction management type/attribute.

        Back to top


        Packaged transformations
      • Transformation core
        Authors of transformation extensions can now contribute pages to the transformation wizard and editor. New extensions can also participate in validation.

        You can now enable or disable transformation extensions on a per transformation configuration basis. A new Extensions page has been added to the transformation configuration wizard; it displays the available forward and reverse transformations, making you aware of the extensions and allow you to choose when to use them.

        When an error or a warning occurs while a transformation is running, an entry is made in the error log. An error reporting tool has been added to the transformation framework that opens a dialog box in which the errors and warnings are displayed. Errors and warnings that are associated with a transformation configuration can become stale. You can run validation to refresh the messages.

        Users are adopting the Design Contract Management Protocols, DCMPs (formally known as theories of operations). Three of the five DCMPs are applicable for transformations: conceptual, mixed and reconciled. They are included in the new transformation configuration wizard and the transformation configuration editor, allowing you to choose which DCMP you want to use.

        The transformation mapping utility now uses a workspace path to refer to the mapping model, rather than a file system path. When you use a transformation configuration from an earlier release, it will automatically be converted to a workspace path.
        Collections and Maps are supported transformation property values.
      • SOA transformations
        The new XSD-to-UML transformation maps multiple source files to multiple target models and supports most XSD element combinations. The transformation output is consumable by the UML-to-XSD transformation.

        There are two new service modeling transformations: Java-to-Service-Model transformation and Session-Bean-to-Service-Model transformation. The generated service models can by consumed by the UML-to-SOA transformation.

        A new "cross-domain" merge view provides a visual mapping of UML source with generated domain elements (XSD, WSDL, SCDL, and BPEL.) Deltas are displayed in target elements that are associated with the UML source.

        The UML-to-BPEL transformation provides support for human task generation.

        The UML-to-XSD and UML-to-WSDL transformation configurations include new a Output Options page where you can specify a target namespace, resource locations, and artifact names.
      • Java transformations
        Basic support was added for Java generic types.

        Delta filter settings are preserved when fusing transformation results into existing models; however, you can reset them to the default settings by using a menu item.

        You can specify finer-grained source for Java-to-UML transformations, including Java projects, source folders, packages, classes, interfaces, and enumerations.

        The UML-to-Java transformation supports XSD Data Type library types.

        Java-to-UML associations link the Java elements to UML elements and enable the proper generation of relationships between UML models during a Java-to-UML transformation.
      • JPA/EJB 3.0 transformations
        Four new transformations are supported: UML-to-JPA, UML-to-EJB 3.0, JPA-to-UML, and EJB 3.0-to-UML. These are extensions of UML-to-Java and Java-to-UML transformations.

        There are two new profiles: JPA transformation profile and EJB 3.0 transformation profile.

        The UML-to-JPA transformation generates JPA annotations for Entity classes. It supports reapply by using new JMerge rules to handle the merging of annotations. This transformation also supports replacement of UML elements and the generation of traceability links.

        The JPA-to-UML transformation supports fusing of the target model.

        The UML-to-EJB 3.0 transformation generates EJB 3.0 artifacts: Session Beans, JMS and non-JMS Message Driven Beans, and external elements (Datasource, Topics, and Queues.) This transformation transforms sequence diagrams to initial implementation of operations. It supports reapply by using new JMerge rules to handle merging of annotations. This transformation also supports replacement of UML elements and the generation of traceability links.

        The EJB 3.0-to-UML transformation supports fusing of the target model.

        Back to top

      • Rate this page:

        (0 users)Average rating

        Add comments

        Document information


        More support for:

        Rational Software Architect for WebSphere Software
        General Information

        Software version:

        7.5, 7.5.1, 7.5.2, 7.5.3, 7.5.4, 7.5.5, 7.5.5.1, 7.5.5.2, 7.5.5.3, 7.5.5.4, 7.5.5.5

        Operating system(s):

        Linux, Windows

        Reference #:

        7014043

        Modified date:

        2011-11-03

        Translate my page

        Machine Translation

        Content navigation