IBM Support

Rational Application Developer for WebSphere Software, Version 7.5 releases: new features and enhancements

Product Documentation


Abstract

The IBM Rational Application Developer 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



For information on deprecated, removed or stabilized product features, see: http://www.ibm.com/support/docview.wss?uid=swg27013438

Table of contents:

Version 7.5.5.5 - Interim Fix 1
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


Interim Fix 1 for version 7.5.5.5
Download Interim Fix 1 for version 7.5.5.5


This release of Rational Application Developer for WebSphere Software contains the following enhancements:




Eclipse patches and fixes
The following additional Eclipse 3.4.2.8 patches and fixes are included in this release:
Eclipse Equinox Bugzilla fixes:
259241, 295744, 290189, 318277, 272087, 329204, 337226, 378979

Eclipse Help Bugzilla fixes: 258974, 103301, 294502, 294390, 306825, 320547, 320548, 319344, 317055, 271049, 254575, 326092, 329204, 329582, 375751

Eclipse JDT Bugzilla fixes: 261198, 256942, 285124, 291716, 124646, 293443, 288211, 296343, 303663, 316447, 277574, 334397, 335861, 342463, 341128, 351103, 355571, 305172, 3644503

Eclipse RCP Bugzilla fixes: 266538, 269158, 273850, 247069, 285804, 270316, 268789, 250782, 142593, 283283, 295744, 259241, 129514, 300174, 264194, 305991, 290189, 305070, 309269, 318277, 323219, 239477, 325474, 329335, 337226, 117746, 326578, 348928, 239477, 8976, 378979

Eclipse RSE Bugzilla fixes: 283744, 281355, 281357, 284176, 284421, 284937, 283606, 283748, 283841, 286812, 268364, 286815, 289389, 287305, 283157, 291612, 299433, 300264, 300005, 295923, 299700, 302490, 302492, 302727, 286122, 315987, 316798, 309802, 309802, 332120, 338665, 350395, 280453, 338665, 280453, 334129, 350395, 381884



IBM WebSphere Application Server test environment updates

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


Rational Application Developer for WebSphere Software Build Utility update

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

Version 7.5.5.5
Download Version 7.5.5.5


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



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:


IBM WebSphere Application Server test environment updates

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



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

Version 7.5.5.4
Download Version 7.5.5.4


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




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




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


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



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

IBM WebSphere Application Server test environment updates

The following IBM WebSphere Application Server Test Environment updates are available: JSF tools
  • New message added to tell users that the JSFTrace is enabled at run time.

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.

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
Version 7.5.5.3
Download Version 7.5.5.3


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





Eclipse platform updates
The following additonal Eclipse 3.4.2 patches and fixes are included in this release:


IBM WebSphere Application Server test environment updates

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

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.

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.

Version 7.5.5.2
Download Version 7.5.5.2


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





Eclipse platform updates





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



IBM WebSphere Application Server test environment updates

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



Java EE Connector (J2C) tools


Test and profiling tools
  • It is no longer necessary for you to set up environment variables when profiling web application on a local WeSphere 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.

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.
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.
Version 7.5.5.1
Download Version 7.5.5.1


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




Eclipse platform updates




Additional supported Web browser versions
Beginning with version 7.5.5.1, the following additional Web browser versions are supported:
  • Mozilla Firefox 3.6



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



IBM WebSphere Application Server test environment updates

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

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.

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.

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.
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.
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.
Version 7.5.5
Download Version 7.5.5


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




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


Eclipse platform updates

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



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



IBM WebSphere Application Server test environment updates

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

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.


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.


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

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

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.
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.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:
    1. A SAML project facet is available to enable or prevent publishing to WebSphere Application Server.
    2. The Policy Set Attachment Wizard can consume SAML tokens, and generate binding configuration files
    3. The new SAML General Bindings are supported. (SAML Bearer and Holder of Key)
    4. A SAML sample is available.
  • Editors have been created for the following WebSphere policy set binding configuration files:
    1. WSSecurity
    2. JMSTransport
    3. SSLTransport
    4. HTTPTransport
    5. WSReliableMessaging
    Using these editors, you can create and edit valid binding configuration files for both the client and service.
    You can also create, attach and edit custom binding configuration files for the service provider side by using these editors.

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.

Version 7.5.4
Download Version 7.5.4


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




Additional supported operating system version
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



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



Eclipse platform updates

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




IBM Runtime Environment updates

IBM Runtime Environment for Java 2 (JRE) is updated to the following versions for Windows and Linux operating systems:
  • IBM 32-bit Runtime Environment for Windows, Java 2 Technology Edition, Version 6.0 service release 5 plus interim fix
  • IBM 32-bit Runtime Environment for Linux, Java 2 Technology Edition, Version 6.0 service release 5 plus interim fix



IBM WebSphere Application Server test environment updates

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


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.


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.


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.


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

IBM 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


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.

SIP Tools


The SIP (Session Initiation Protocol) 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.
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.
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.

Version 7.5.3
Download Version 7.5.3


This release of Rational Application Developer 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:



IBM Runtime Environment updates

The IBM Java™ Runtime Environment (JRE) is updated to the following versions for Windows® and Linux operating systems:
  • IBM 32-bit Runtime Environment for Windows, Java 2 Technology Edition, Version 6.0 service release 5
  • IBM 32-bit Runtime Environment for Linux, Java 2 Technology Edition, Version 6.0 service release 5



IBM WebSphere Application Server test environment updates

The following IBM WebSphere Application Server 6.1 Test Environment updates are available:

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.

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:
    • 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


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.
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 Application Developer for WebSphere Software contains new features and enhancements in the following areas:



Eclipse platform updates

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 also 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


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


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


Updates to IBM Runtime Environment
The IBM Java™ Runtime Environment (JRE) is updated to the following versions for Windows® and Linux operating systems:
  • IBM 32-bit Runtime Environment for Windows, Java 2 Technology Edition, Version 6.0 service release 4
  • IBM 32-bit Runtime Environment for Linux, Java 2 Technology Edition, Version 6.0 service release 4


New installable feature: Service Component Architecture Development Tools
This 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.

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.

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.


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".

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.

Version 7.5.1
Download Version 7.5.1


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



Updates to IBM Runtime Environment
The IBM Java™ Runtime Environment (JRE) is updated to the following versions for Windows and Linux operating systems:
  • IBM 32-bit Runtime Environment for Windows, Java 2 Technology Edition, Version 6.0 service release 3
  • IBM 32-bit Runtime Environment for Linux, Java 2 Technology Edition, Version 6.0 service release 3



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


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 in Rational Application Developer. Each new function is activated by selecting its corresponding option in the SQLJ preferences. You can access the new SQLJ preference by selecting Window > Preferences, 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.


      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.



      Domain modeling (graphical code editing)
      • Domain modeling 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 name and location of new static method sequence diagram.
        • You can now specify the name and location of the 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.



      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.


      Version 7.5
      Download Version 7.5
      Read about major advances in product features and technology since our last release in the following areas:



      EJB 3.0 development tools

      Enterprise JavaBeans™ (EJB) 3.0

      EJB 3.0 is a new standard for developing and testing enterprise beans that conform on the server side to the distributed component architecture defined in the Sun Microsystems Enterprise JavaBeans™ (EJB) 3.0 specification. Although the tools still support applications developed using the EJB 2.1 specification, the EJB 3.0 development model helps you to develop beans more simply than in the 2.1 standard.

      EJB 3.0 requirementsEarlier version of EJB requirements
        • Annotated bean class
        • Annotated business interface
        • Remote or local interface
        • Bean class for business logic that is required to implement:
            • Javax.ejb.SessionBean, Javax.ejb.EntityBean or Javax.ejb.MessageDrivenBean
            • Remote or local interface
            • Home interface
        • Explicit use of tools for code generation
        • Configuration of services in deployment descriptor
        • Vendor-specific files

      EJB 3.0 reduces the development complexity of previous versions of Enterprise JavaBeans in the following ways:

      • Annotations: You can use annotations in your Java™ source code to provide information that was previously contained in XML deployment descriptors.
      • Java objects: You can create entity beans from plain old Java objects (POJOs) using Java Persistence API (JPA).

      EJB tools

      From the Java EE perspective in the workbench, you can access a number of tools that help you in the creation of EJB enterprise applications.

      • Annotations view: You can use the Annotations view to create, modify, and delete the annotations you use in your Java classes. This view provides default values where possible, and indicates which attributes are required.
      • Content Assist: In the Java editor, Content Assist provides coding options for you to insert into your code while you create your classes.
      • As-you-type validation: The tools check your code while you type it, indicating where problems or errors occur.
      • Quick Fixes: This tool helps you add the necessary dependencies and attributes for annotations that you insert into your Java™ code.
      • Refactoring: In your EJB 3.0 session bean class that specifies its business interface using annotations or a deployment descriptor, you can use refactoring to expose a business method in the interface. The following types of refactoring are supported:
      • Add a new business method to the bean, when the bean does not implement the business interface.
      • Rename a business method in the bean, when the bean does not implement the business interface.
      • Rename dependency injections in the bean.

      EJB 3.0 modeling

      You can use Unified Modeling Language (UML) class diagrams to model, or visually represent annotations and develop artifacts of EJB 3.0 applications in a single, tightly integrated development environment.

      You can use class diagrams to model and analyze an existing EJB 3.0 application to identify its annotations, and classes, and to create a representation of the application in another form. You can use class diagrams to abstract the structural information for the application from code to a new form at a higher abstraction level. You can also modify the target application or develop and generate new applications.

      From class diagrams, you can visually develop and edit the following EJB 3.0 enterprise beans:

      • Entity beans
      • Message-driven beans
      • Stateless and stateful session beans

      Getting started with EJB 3.0 development

      For more information on developing EJB 3.0 enterprise beans, refer to the Help (Help > Help Contents) and the Counter EJB 3.0 sample in the Samples Gallery (Help > Samples Gallery).

      For more information on the WebSphere Application Server with Feature Pack for EJB 3.0, refer to WebSphere Application Server V6.1 Feature Pack for EJB 3.0 documentation.




      Java Platform, Enterprise Edition 5 development tools

      Supported specifications

      The following specifications are now supported by the tools for Java™ Enterprise Edition 5:

      • Web services:
      • JSR-224: JAX-WS 2.0, JAXB 2.0, SAAJ 1.3
      • JSR 181 Web services Metadata - Annotated Java classes for easy definition of Web services
      • Web applications:
      • Servlet 2.5 (JSR 154)
      • JSP 2.1 (JSR 245)
      • JSTL (JSR 52)
      • JSF 1.2
      • Enterprise applications:
      • EJB 3.0
      • JPA (JSR 220)
      • JCA 1.5 (JSR 112)
      • Management:
      • J2EE Application Deployment (JSR 88)
      • J2EE Management (JSR 77) Manage Web/Enterprise Applications on Java EE 5 Servers

      Java EE 5 projects

      You can create and edit Java EE 5 applications that you can publish to application servers that support Java EE 5, including Apache Tomcat 6 and Geronimo 2.

      For information on Enterprise JavaBean™ (EJB) 3.0 support for the IBM® WebSphere® Application Server 6.1 EJB 3.0 feature pack, refer to the topic "Limitations in developing EJB 3.0 modules for the EJB 3.0 Feature Pack" in the Help (Help > Help Contents).

      Easier publishing of dependencies

      You can add entries on the Java build path to the published structure of J2EE module projects through the J2EE Module Dependencies properties page.

      More flexible validation

      The validation framework now supports content types, so that additional file names added to content types on the Content Type preference page are also validated by their respective validators.

      Java EE 5 models

      Java EE 5 models include:

      • XML translator framework: The Translator model allows the EMF models to be updated during the editing of XML documents.
      • Java EE 5 annotations: Annotations are metatdata that can be embedded in the Java classes that they describe. Annotations do the following:
      • Replace the need for deployment descriptors (in most cases)
      • Remove the need for marker interfaces (like java.rmi.Remote)
      • Allow application settings to be visible in the component that they affect

      Java EE 5 tools

      Java EE 5 tools include:

      • Annotations view: You can use the Annotations view to create, modify, delete, and the annotations you use in your Java classes. This view provides default values where possible, and indicates which attributes are required.
      • Content Assist: In the Java editor, Content Assist provides coding options for you to insert into your code while you create your classes.
      • As-you-type validation: The tools check your code while you type it, indicating where problems or errors occur.
      • Quick Fixes: This tool helps you add the necessary dependencies and attributes for annotations that you insert into your Java™ code.
      • Refactoring: The following types of refactoring are supported:
      • Add a new method to the class.
      • Rename a method in the class.
      • Rename dependency injections in the class.

      Content assistance and validation

      Content assistance and validation are available, while you type, for both Java source and annotations. Additionally Quick Fixes can help you correct errors, and the tools automatically update the associated metadata when you refactor code.




      JPA development tools

      Java Persistence API (JPA)

      Java™ Persistence API (JPA) is a new standard for data persistence in Web and distributed business applications. This standard replaces container-managed persistence (CMP) beans in the Java 2 Platform, Enterprise Edition (J2EE).

      Defining and editing object-relational mappings for EJB 3.0 JPA entities

      With extensible frameworks and tools, you can perform many tasks that are associated with accessing data for a multi-tier enterprise application:

      • Create a new JPA project.
      • Manage and work with the persistence.xml and orm.xml files
      • Synchronize classes in the persistence.xml file.
      • Make Java classes can be made into several persistent types: entity, embeddable, mapped, and mapped superclass.
      • Specify additional tables.
      • Specify entity inheritance.
      • Validate mappings and reporting problems.
      • Modify persistent project properties.

      Top-down and Bottom-up Mappings

      With the JPA tools, you can generate JPA entities from existing database tables (bottom-up mapping) or database tables from existing JPA entities (top-down mapping).

      Java Messaging Service (JMS) binding support

      Java Messaging Service (JMS) bindings can be used as a transport in addition to the Enterprise Information Server (EIS) bindings. You can use J2C properties editor to add and edit JMS bindings from the Service Component Architecture (SCA) component editor.

      Creating different types of mappings

      With the JPA tools, you can create the following types of mappings for JPA entities:

      • Basic
      • Embedded
      • Embedded ID
      • ID
      • Many-to-many
      • Many-to-one
      • One-to-many
      • One-to-one
      • Transient
      • Version

      Simplification of mapping

      In order to minimize the complexity of mapping between JPA entities and tables, you can use wizards to create and automate initial mappings. You can also receive programming assistance from the tools through dynamic problem identification.

      Ease of Refactoring

      When you rename or move a class that is related to JPA, you can use a wizard to refactor all references to these classes in persistence.xml and orm.xml files.

      Integration of the JPA Details view and the Annotations view

      You can work with JPA properties in either the JPA Details view or the Annotations view, so that you don’t need to keep both views open at once. For clarity, the Annotations view distinguishes between implied and specified annotation attributes.

      Adding JPA Support to a plain Java project

      Using Quick Fixes, that are available in the Java editor, you can easily add JPA support to a plain Java project. When you type a JPA annotation into a plain old Java object (POJO) in a plain Java project, the resulting compilation errors have Quick Fixes for adding the required JPA facet and an appropriate runtime environment (if available) to your project.




      Web application development tools

      JPA consumption

      Using Web tools, you can access relational data using the Java™ Persistence API (JPA), and then generate JSF user interface components to display, create, update, and delete data.

      Using the JPA consumption wizard, you can configure JPA entity beans as well as the manager bean facade in order to:

      • Perform queries
      • Filter results
      • Order results
      • Find, create, update, or delete a records
      • Manage multiple tables using relationships

      You can generate and configure a JPA manager bean facade. This facade provides an interface for business logic and shields client code from database schema details.

      You can configure deployment information, such as JPA persistence unit settings and data source definition, to be used when publishing a Web application on IBM® WebSphere® Application Server.

      Web 2.0 development support

      This product provides support for developing Web 2.0 applications, based on technologies available in the WebSphere Application Server Feature Pack for Web 2.0. In particular, Web 2.0 development support includes:

      • Server-side technologies: Server-side technologies enable back-end components to provide or consume Web 2.0 services and connectivity. The Java libraries for these technologies can be configured easily in dynamic Web projects for development as well as deployment to the WebSphere Application Server. These technologies include feeds syndication and publication, Web remoting, publish/subscribe Web messaging and JSON data serialization and de-serialization.
      • Web Remoting via RCP Adapter: Developed by IBM, this technology allows server-side POJOs to be easily exposed for access via HTTP. It makes them readily accessible to AJAX clients. Using Web tools, RPC services can be easily created, tested, and consumed in AJAX clients.
      • IBM Dojo toolkit: The IBM Dojo toolkit contains the open source Dojo Toolkit, as well as IBM extensions for advanced user interface and service consumption. Dojo development support includes content assist in JavaScript™ and HTML, a palette drawer for Dijit (including dojox.Grid), and automatic project setup.
      • AJAX proxy: AJAX proxy allows an AJAX client to access services provided by end-points from a different Web domain. Using the tools in this product, you can easily setup an AJAX proxy and configure it to access external services.

      Web services consumption improvements

      You can use Web tools to discover SOAP-based Web services. You can also generate Java client proxies for JAX-WS or JAX-RPC services using either the IBM WebSphere Application Server or Axis Web services runtime environment.

      Using a set of visual tools, JAX-WS and JAX-RPC Web services can be consumed easily via Java client proxies on a Web page using JSF user interface components.

      JavaServer Faces support

      The tools offer these changes to JSF support:

      • A JSF configuration (faces-config.xml) editor
      • Content assist is now available when you create a JSF EL expression in a JavaServer Page (JSP) file.
      • Support for creating JSF 1.2 applications.
      • Using JSF tools, you can create a custom JSF component library.
      • JSF tools support third party JSF component libraries. You can now define the required resource, the palette, how tag attributes will be handled and the design time visualization for a JSF component library.
      • JSF tools support the creation of customized Faces data templates for page generation.

      Web Site Navigation

      You can now create multiple pages from selected nodes. You can also zoom in and out of Web Site Navigation to enlarge or shrink the view of the site structure.

      Page Designer

      You can edit pages in the Source and Design or Preview views simultaneously using split horizontal or vertical panes. You can also absolutely position all elements on the Design page by dragging and dropping to the desired location. You can set attribute values for multiple selected elements at the same time.

      Struts

      Struts tools offers support for Struts framework 1.2.9 and 1.3.5, including support for the new taglib attributes that were added in Struts 1.2 and 1.3.




      Web services development tools

      Web service standards

      The Web services tools support a set of Web services standards that result in interoperable and reliable Web service applications:

      • Java™ API for XML Web Services (JAX-WS 2.1): JAX-WS simplifies application development through a standard, annotation-based model to develop Web service applications and clients. A common set of binding rules for XML and Java objects make it easy to incorporate XML data and processing functions in Java applications; and a further set of enhancements help you send binary attachments, such as images or files, with the Web services request in an optimal way.
      • Java Architecture for XML Binding (JAXB 2.1): JAXB is a Java technology that provides an easy and convenient way to map Java classes and XML schema for simplified development of Web services. JAXB leverages the flexibility of platform-neutral XML data in Java applications to bind XML schema to Java applications without requiring extensive knowledge of XML programming.
      • Web Services Metadata 2.0 (JSR-181) and A Metadata Facility for the Java Programming Language (JSR-175): Both JAX-WS and JSR-181 introduce a JSR-175 style annotations programming model which aims to make it easier for users to create and modify a Web service. The annotations embed metadata in the compiled .class file of Web service implementations and service endpoint interfaces which can be processed at runtime much like deployment descriptors.
      • SOAP 1.2: SOAP 1.2 provides a more specific definition of the SOAP processing model, which removes many of the ambiguities that sometimes led to interoperability problems in the absence of the Web Services-Interoperability (WS-I) profiles.
      • SOAP Message Transmission Optimization Mechanism (MTOM): SOAP MTOM provides vendor interoperable attachment support for sending binary attachments, including images or files, with your Web services request across vendors.
      • Implementing Enterprise Web Services (JSR-109 v1.2): Defines the Web Services for Java EE (WSEE) architecture. This is a service architecture that leverages the Java EE component architecture to provide a client and server programming model which is portable and interoperable across application servers and provides a scalable secure environment. Through this, EJB-based JAX-WS Web services can be deployed and common deployment descriptors can be used to describe both JAX-RPC and JAX-WS Web services and clients.

      You can send messages asynchronously, so that your messages can communicate reliably even if one of the parties is temporarily offline, busy, or not available. You can send messages securely and rest assured that your messages are not vulnerable to attack. You can be confident that your communication is reliable and reaches its destination and is compatible with other vendors.

      New server support added

      JAX-WS Web services can be deployed to WebSphere Application Server v7.0. Additionally you can install, start and test a Web service or Web service client targeted to a server stub if you specify an existing server in the Web Service wizard. This existing server could be a remote server or a server that is compatible with that stub server runtime.

      Portable JAX-WS Web service clients

      JAX-WS makes physical WSDL documents optional in deployed clients. Although this simplifies the deployment of a Web service client, it also introduces some potential run time issues. Portable clients minimize run time issues that could result from moving your client code from one system to another.

      Create Web services from a POJO

      Bottom-up Web services can be created from a POJO (Plain Old Java Object) residing in a Java project.

      You can also Web service enable a Java bean using Quickfixes. Add an @WebService annotation to a Java bean in a Java project and use the provided quickfix to convert the project into a Web service enabled project, for example a dynamic Web project or an EJB project when @Stateless is also present.

      Web service policy sets to control quality of service

      The Web service tools support the capabilities of IBM® WebSphere® Application Server V6.1 Feature Pack for Web services and WebSphere Application Server v7.0 to facilitate sending Web services messages asynchronously, reliably, and securely, permitting interoperability with other vendors and supporting the Java API for XML Web Services (JAX-WS) 2.1 programming model. Simplified management using Web service profiles makes it easy to configure and reuse configurations, so that you can introduce new Web service profiles seamlessly in the future. These configurations are captured in a grouping called policy sets, in which you select and associate different qualities of service with an application. Policy sets can be imported and exported using the Import and Export wizards.

      You can configure policy sets to allow only those capabilities within a given WS-Interoperability (WS-I) profile, thereby limiting configurable portions to those that work across vendors. WS-I is an open industry organization chartered to promote Web service interoperability across platforms, operating systems, and programming languages. Validation and conformance can be set for WS-I BP 1.2 and 2.0, as well as BSP 1.0. WS-I and quality of service preferences can now be found in a single Service Policies preferences page. The workspace Service Policies setting can also be overridden on the project level using the project properties page.

      Added support for General bindings for policy sets

      The Web service tools include pre-configured bindings that you can use to test Qualities of service. They can be imported using the Import wizard.

      Support for WS-Policy sharing between Web Services providers and Web services client using WSDL embedded policy information

      Web services providers can share information about policy sets using in a Web service with clients. Web services providers can specify if the information is available in the WSDL or if clients need to use WS-Metadata Exchange to get the information. Clients can be configured to use any policy sets that are available from a provider, or they can choose to add more capabilities by adding client specific Qualities of service.

      Kerberos security tokens supported for JAX-WS and JAX-RPC Web services

      For Web services deployed to WebSphere Application Server v7.0, the Kerberos security token can be used. For JAX-RPC Web services it can be configured through the Web service security wizards, and for JAX-WS Web services it is part of the Web Services Security policy type.

      Services view in Java EE perspective Enterprise Explorer

      The previous JAX-WS and JSR-109 nodes in the Enterprise Explorer have been consolidated into the Services view which will allow you to quickly find and work with all the available services in a workspace. Similar information on Services is available under each of the projects in the Enterprise Explorer.

      Improvements to Web service annotations autocompletion and quick fixes

      The workbench supports automatic completion of Web service annotations even when the classes are not on the system classpath. You can insert the Web service annotations @WebService and @WebMethod, in the Java editor, as a template with appropriate values.

      Web service annotations support the use of quick fixes. When a JAX-WS annotation is unresolved, quick fixes can help you to enable JAX-WS project support.

      Schema library improvements

      You can use the JAXB related tools to automatically refactor the generated Java code in projects for a set of complex and interdependent XSD files. Refactoring occurs as a part of the generation process. You can also group the generated code into the projects that you select.

      Validation improvements

      Client side policy set bindings support validation. WSDL validation can now track IBM® WebSphere® Application Server requirements. For example WSDL validation can warn you of relative namespaces or unusual URI patterns and unsupported wire formats based on IBM WebSphere Application Server requirements.

      Simplified Ant task based Web service creation

      When creating Web services and clients using Ant tasks, the scripts are now located in a standard location and can be easily run without copying the scripts or modifying them based on workspace location and product install directories. You can also select the Web services runtime and Web service type when importing Ant files into the workspace. This enables yo to use an Ant file template best matched with the runtime and scenario you want to run.

      Support for sample JSP creation

      You can now generate Web services sample JSP files using a stub server. Also, when using the context menu to generate sample JSP files, you can select the server type and server instance on which to run the sample JSP files.




      XML development tools

      XML Web Services


      New XML, XSD, WSDL, and XSL validation preferences

      In addition to controlling the build or manual enablement for a validator, you can now specify additional options. For example, you can specify which files or folders the validator must validate or exclude. By excluding folders that contain static and stable content, you can improve the overall build performance.

      Dependencies revalidation

      The XML, XSD, and WSDL validators provide dependency revalidation. For example, if an XML schema is edited and saved, the XML document, that is constrained by the XML schema, is revalidated. Dependencies revalidation function is also available for XML schema and WSDL documents, that have dependencies through imports and include statements.

      Additional XML validation preferences

      The XML file preferences page includes settings to control:

      • Validation of document with XInclude directives.
      • Configuration of the severity of Grammar constraint errors.

      Opening XML schema and WSDL documents located outside the workspace

      You can now use the XML schema and WSDL editor to open XML schema and WSDL documents located outside the workspace. This feature is applicable to files located on the local file system, as well as remote files, for example XML schema or WSDL documents located on a Web server. Local files can be opened by using File > Open file. Remote documents referenced by import and include statements can be opened from the graphical view or outline view of the editor.

      Improved XML Schema visualization

      The XML schema editor provides a new enhanced type-oriented view of an XML schema. By using the new type expansion functionality, you can show or hide parent types, complex types, or simple types by clicking controls located at the top or right side of a figure.

      Zoom level control and zoom overview

      You can now control the zoom level used to render the Graphical View of the XML schema and WSDL editors. Use the toolbar control to zoom in or zoom out.

      In the XML schema editor, you can also use the new thumbnail overview to scroll the graphical view. You can access this new feature by selecting it in the toolbar of the outline view.

      Support for editing and validating WSDL bindings extensions for SOAP 1.2

      You can now choose to select SOAP 1.2 as the default protocol when you use the WSDL editing wizards. The source view in the WSDL editor also provides content assist for SOAP 1.2 bindings extensions. The WS-I profile service policy controls the selection of the default binding protocol in the New WSDL wizard. The WSDL validator provides validation for SOAP 1.2 binding extensions.

      Improved generation of XML schema from an XML instance

      You now have better control over the representation of XML schema types when generating an XML schema from an XML instance document. In the wizard, you can specify either anonymous or global types for both simple and complex types.

      XML Catalog import/export wizard

      The new XML catalog Import/Export wizard replaces the old XML catalog import/export dialog.




      Portal development tools

      JSR 286: Portlet Specification 2.0

      The portlet tools now support developing, testing, and debugging portlets based on the JSR 286 specification.

      This includes additional capabilities like filters, events, and public render parameters.

      IBM® WebSphere® Portal V6.1 support

      IBM WebSphere Portal V6.1 support includes the WebSphere Portal V6.1 target runtime.

      Web 2.0 support with WebSphere Portal V6.1

      Web 2.0 support includes:

      • Client side programming model support
      • Semantic tagging support
      • Enhancement to Portal themes
      • Ajax proxy support
      • Person tagging support

      Static page aggregation support for WebSphere Portal V6.1

      This feature supports the use of static HTML layouts in Portal pages. You can now create generic HTML pages as static Portal pages using any HTML authoring tool.




      Assembly and deployment tools for WebSphere Application Server

      WebSphere Application Server



      Specification level support

      The workbench now includes support for IBM® WebSphere® Application Server v7.0 and WebSphere Application Server v6.1 with Feature Pack for Web Services, Web 2.0, and EJB 3.0.

      The following table summarizes the specification levels that each server supports.

      WebSphere Application Server release level
      Specification Level
      EAR
      EJB
      Web
      Application Client
      v6.0
        • 1.2
        • 1.3
        • 1.4
        • 1.1
        • 2.0
        • 2.1
        • 2.2
        • 2.3
        • 2.4
        • 1.2
        • 1.3
        • 1.4
      v6.1
      v6.1 with the Feature Pack for Web services
      v6.1 with the Feature Pack for Web 2.0
      v6.1 with the Feature Pack for Web services and the Feature Pack for Web 2.0
      v6.1 with the Feature Pack for EJB 3.0
        • 1.2
        • 1.3
        • 1.4
        • 5.0
      The server does not fully support the Java EE 5 specification level. It supports an EAR 5.0 application containing EJB 3.0 modules with Web or Application Client modules at the J2EE 1.4 (or earlier) specification-level.
        • 1.1
        • 2.0
        • 2.1
        • 3.0
      In an EJB 3.0 module, CMP 2.1, 2.0 or 1.1 is not supported.
        • 2.2
        • 2.3
        • 2.4
      Java EE 5 specification-level is not supported. In other words, Web 2.5 is not supported.
        • 1.2
        • 1.3
        • 1.4
      In other words, Application Client 5.0 is not supported.
      v6.1 with the Feature Pack for EJB 3.0 and the Feature Pack for Web 2.0
      v7.0
        • 1.2
        • 1.3
        • 1.4
        • 5.0
        • 1.1
        • 2.0
        • 2.1
        • 3.0
        • 2.2
        • 2.3
        • 2.4
        • 2.5
        • 1.2
        • 1.3
        • 1.4
        • 5.0

      The workbench no longer supports tools for WebSphere Application Server v5.1 or WebSphere Application Server Network Deployment environment. However, using WebSphere Application Server Network Deployment, you can continue to run the profile management tool from the workbench to create and augment profiles.

      WebSphere Application Server v6.1 with Feature Pack for EJB 3.0

      When publishing an application to a WebSphere Application Server v6.1 with EJB 3.0 Feature Pack, Java™ Enterprise Edition (Java EE) 5 support is available for both Enterprise archive (EAR) and Enterprise JavaBeans™ (EJB) modules; however, container-managed persistence (CMP) beans at 2.1, 2.0, or 1.1, are not supported in an EJB 3.0 module. In addition, the Web module must remain at Web 2.4, 2.3, or 2.2 specification-level and the application client module must remain at Java 2 Platform Enterprise Edition (J2EE) 1.4, 1.3, or 1.2 specification level.

      Although, the WebSphere Application Server v6.1 with the Feature Pack for EJB 3.0 does not support Servlet 2.5 Web archive (WAR) files and Java EE 5 application client modules, the application server does support annotated injections for Servlet 2.4 WAR files and J2EE 1.4 application clients as a common annotations extension.

      WebSphere Application Server with Feature Pack for Web 2.0

      The WebSphere Application Server with Feature Pack for Web 2.0 can be installed on top of any of the following WebSphere Application Server release:

      • WebSphere Application Server v6.1
      • WebSphere Application Server v6.1 with Feature Pack for Web Services
      • WebSphere Application Server v6.1 with Feature Pack for EJB 3.0
      Although the WebSphere Application Server with Feature Pack for Web 2.0 can be installed on top of WebSphere Application Server v6.0.2, the IBM Rational Software Delivery Platform currently does not support this runtime configuration.

      New WebSphere Application Server tools

      • A new option to automatically determine connection settings is available under the Server connection type and administrative ports section of both the New Server wizard and the server editor. When you use this option, the workbench, automatically selects which available connection type to use.
      • A new test connection link is available under the server connection type and administrative ports section of both the New Sever wizard and the server editor. Use this link to test the connection between the server and the workbench to determine if there are any connection problems. When a connection fails, messages display with possible explanations and solutions.
      • A new connection type, InterProcess Connector (IPC), is available for WebSphere Application Server v7.0. It offers a more stable and robust connection between the workbench and a local WebSphere Application Server v7.0.
      • A new Workspace Migration dialog appears when opening a workspace that contains projects targeting a server runtime that is not defined in the workspace. Use this dialog to replace undefined server runtimes with runtimes already defined in the workspace. This helps resolve errors such as: Unbound classpath container and Target runtime WebSphere Application Server vX.X is not defined.
      • The Table and Data Source Creator wizard now supports creating tables and data sources for testing Java Persistence API (JPA) beans on a WebSphere Application Server:
      • When you right-click a server in the Servers view, there is a new Properties option in the pop-up menu. Use the Properties pages to find general information about the server, such as the name of the server, server type, vendor, and the location of its metadata. You can also use the Properties pages to monitor data sent to the server ports. For WebSphere Application Servers, you can also use the Properties pages to view the log files, profile name, and directory.
      • When you use the Installation Manager to install the integrated test environments for WebSphere Application Server, you can create profiles during the installation or create the profiles in the workbench after installation. This flexibility assists a server administrator when installing the application server for an enterprise..

      EJB deployment tool
      EJB deployment code specification-level differences

      For the EJB 3.0 specification-level you no longer need to generate the EJB deployment code. The server runtime automatically generates the required deployment code. You can continue to generate EJB deployment code for the EJB 1.1, 2.0, and 2.1 specification-levels using the Prepare for Deployment option in the workbench or the command-line tool, ejbdeploy.

      Database systems support

      Support for the following database systems has been added when generating EJB deployment code for WebSphere Application Server v6.1 with Fix Pack 11 (v6.1.0.11) and later:

      • IBM® DB2® Universal Database™ v9.1 for Linux™, UNIX™, and Windows®
      • DB2 Universal Database for z/OS®, v9

      This option includes the generated data model that has all the new catalog features of DB2 Universal Database for z/OS v9 specified in the new function mode. It enables the option to work with the generated data model available in the workbench.

      Jython tools


      WebSphere Application Server v7.0 adds wsadmin objects to Jython script libraries

      The WebSphere Application Server v7.0 adds numerous WebSphere Administrative (wsadmin) objects to the Jython scripting libraries, in addition to the standard five wsadmin objects: AdminControl, AdminConfig, AdminApp, AdminTask, and Help.

      In the Jython preferences (Window > Preferences > Jython), select Enable content assist for WebSphere Application Server v7.0 script libraries. The additional wsadmin objects are available when using content assist (Ctrl+Space) in the Jython editor.

      Restriction: The additional wsadmin objects are supported for Jython scripts running on a WebSphere Application Server v7.0.




      J2C development tools

      Support for WebSphere Adapters

      WebSphere® Adapters are new J2C-compliant adapters that use the Enterprise Metadata Discovery (EMD) framework. Through EMD, the J2C tools can query the Enterprise Information Systems (EIS) for information. The EIS that can be accessed through the new WebSphere Adapters include:

      • SAP
      • Siebel
      • PeopleSoft
      • J.D. Edwards EnterpriseOne
      • Oracle

      With the new support for WebSphere Adapters you can create a full J2C Java bean and associated data binding classes by connecting to the EIS, querying the data types and functions available, and then creating the data binding classes from this information.

      With the J2C wizard you can select the adapter that you want to use to connect to the EIS.

      With the new Service Discovery wizard page, you can perform live queries of EIS databases. Once you connect to the remote EIS, you can perform data operations, such as:

      • Create
      • Update
      • Delete
      • Retrieve
      • Retrieve all
      • Apply changes
      • Exists

      [{"Product":{"code":"SSRTLW","label":"Rational Application Developer for WebSphere Software"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"General Information","Platform":[{"code":"PF033","label":"Windows"},{"code":"PF016","label":"Linux"}],"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","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

      Document Information

      Modified date:
      17 June 2018

      UID

      swg27014208

      Page Feedback