Product Documentation
Abstract
Fix packs for IBM Rational Application Developer for WebSphere Software are cumulative, meaning that they include all new features or enhancements (as well as fixes to APARs) from earlier fix packs. The following is a summary of enhancements made available in the version 7.0.0.x fix packs, with the most recent fix pack at the top.
Content
Table of contents:
Version 7.0.0.10 | |
Version 7.0.0.9 | |
Version 7.0.0.8 | |
Version 7.0.0.7 | |
Version 7.0.0.6 | |
Version 7.0.0.5 | |
Version 7.0.0.4 | |
Version 7.0.0.3 | |
Version 7.0.0.2 | |
Version 7.0.0.1 | |
Download Version 7.0.0.10 |
This release of Rational Application Developer for WebSphere Software contains new features and enhancements in the following areas:
- Eclipse platform updates
- Supported operating system updates
- IBM Runtime Environment for Java 2 updates
Eclipse platform updates
The following Eclipse 3.2.2 patch is included in this release:
- Eclipse Java™ development tools (JDT): Bugzilla fix 138184
Back to top
Supported operating system updates
The following additional operating system versions are supported beginning with the version 7.0.0.10 fix pack:
- Red Hat Enterprise Linux Workstation Version 5.0 Update 4
- Red Hat Desktop Version 5.0 Update 4 (running in 32-bit mode)
Back to top
IBM Runtime Environment for Java 2 updates
The IBM Runtime Environment, Java 2 Technology Edition is updated to the following versions for Windows and Linux operating systems:
- IBM 32-bit Runtime Environment for Windows, Java 2 Technology Edition, Version 5.0 service release 10
- IBM 32-bit Runtime Environment for Linux, Java 2 Technology Edition, Version 5.0 service release 10
Back to top
Download Version 7.0.0.9 |
This release of Rational Application Developer for WebSphere Software contains new features and enhancements in the following areas:
- Eclipse platform updates
- Supported operating system updates
- IBM Runtime Environment for Java 2 updates
- New Web browser support
Eclipse platform updates
The following Eclipse 3.2.2 patches and fixes are included in this release:
- Java Visual Editor: Bugzilla fix 216275
- Test and Performance Tools Platform (TPTP) Project: Bugzilla fix 263982
Back to top
Supported operating system updates
The following additional operating system versions are supported beginning with the version 7.0.0.9 fix pack:
- Microsoft Windows Vista with Service Pack 2
- Red Hat Enterprise Linux® Workstation Version 4.0 Update 8
- Red Hat Desktop Version 4.0 Update 8 (running in 32-bit mode)
- Red Hat Enterprise Linux Workstation Version 5.0 Update 3
- Red Hat Desktop Version 5.0 Update 3 (running in 32-bit mode)
Back to top
IBM Runtime Environment for Java 2 updates
The IBM Runtime Environment, Java 2 Technology Edition is updated to the following versions for Windows® and Linux operating systems:
- IBM 32-bit Runtime Environment for Windows, Java 2 Technology Edition, Version 5.0 service release 9
- IBM 32-bit Runtime Environment for Linux, Java 2 Technology Edition, Version 5.0 service release 9
Back to top
New Web browser support
The following Web browsers are supported beginning with the version 7.0.0.9 fix pack:
- Microsoft Internet Explorer 8
- Mozilla Firefox 3.5
Download Version 7.0.0.8 |
This release of Rational Application Developer for WebSphere Software contains new features and enhancements in the following areas:
- Updates to supported operating systems
- Updates to IBM Runtime Environment
- Additional Eclipse patches and fixes
- J2C Tools
- Data Tools
- Source Editor
- Debugger
- Struts Tools
Updates to supported operating systems
The following additional operating system versions are supported beginning with the version 7.0.0.8 fix pack:
- Red Hat Enterprise Linux® Workstation Version 4.0 Update 7
- Red Hat Desktop Version 4.0 Update 7 (running in 32-bit mode)
Updates to IBM Runtime Environment
The IBM Runtime Environment is updated to the following versions for Windows® and Linux operating systems:
- IBM 32-bit Runtime Environment for Windows, Java™ 2 Technology Edition, Version 5.0 service release 8a plus patches IZ29767, IZ30684, IZ31214 and IZ31213
- IBM 32-bit Runtime Environment for Linux, Java 2 Technology Edition, Version 5.0 service release 8a plus patches IZ29767, IZ30684, IZ31214 and IZ31213
Additional Eclipse patches and fixes
The following Eclipse 3.2.2 patches and fixes are included in this release:Web Tools Platform R1.5.5 Patch P20081023211315-20081023211315
- XSD Patch (Bugzilla 200848)
- Platform Patch (Bugzilla 242544)
- Platform Patch (Bugzilla 156951)
- TPTP Patch (Bugzilla 231691)
J2C Tools
Updates to IMS TM Resource Adapters
The following new IMS™ TM Resource Adapters are included in this fix pack:
- IMS TM Resource Adapter Version 9.1.0.2.5.a. For more information about this version see: http://www.ibm.com/software/data/ims/ims/components/1conjav124.html
- IMS TM Resource Adapter Version 10.2.1. For more information about this version see: http://www.ibm.com/software/data/ims/ims/components/1conjav125.html
Note: If you run IMS applications on IBM WebSphere Application Server, then you should download the IBM TM Resource Adapters from https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=imscjd
Data Tools
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.
Source Editor
You can now configure the problem severity of missing tags as reported by the HTML Validator. To configure the problem severity preference, use the new HTML Validation preference page (Preferences > Web and XML > HTML Files > HTML Validation). Preference changes are applied to the entire workspace.
Tip: By default, missing start tags are reported as Errors and missing end tags as Warnings.
If you change the HTML Validation preferences, then you are prompted to run a full validation of the workspace for the new settings to take effect.
Debugger
Debugging of tag libraries is now supported. You can add breakpoints to tag libraries. Also, you can step through the tag libraries and inspect variables after being suspended at a breakpoint in the tag library.
Struts Tools
The Web application development tools now supports the following Struts versions in addition to Struts 1.1:
- Struts 1.2.9
- Struts 1.3.8
To add Struts 1.2.9 or 1.3.8 support to an existing project, that is not Struts-enabled, right-click your Web project and select Properties > Project Facets.
Struts 1.2.9 and 1.3.8 are now supported by the following tools:
- Web Diagram Editor
- Struts Configuration File Editor
- Struts-related wizards
- Page Designer, including the Palette, Page Data, and Properties views
- Project Explorer
- Struts configuration file validation
- Links validation
Download Version 7.0.0.7 |
This release of Rational Application Developer for WebSphere Software contains new features and enhancements in the following areas:
- Updates to supported operating systems
- Updates to IBM Runtime Environment
- Additional Eclipse patches and fixes
- J2C Tools
- JSF Widget Library
- Portal Tools
- Web RAD Development Tools
- Web services
Updates to supported operating systems
The following additional operating system versions are supported beginning with the version 7.0.0.7 fix pack:
- Microsoft® Windows® XP Professional Edition, Service Pack 3
Updates to IBM Runtime Environment
The IBM Runtime Environment is updated to the following versions for Windows and Linux® operating systems:
- IBM 32-bit Runtime Environment for Windows, Java™ 2 Technology Edition, Version 5.0 service release 6b + IZ15865 interim fix
- IBM 32-bit Runtime Environment for Linux, Java 2 Technology Edition, Version 5.0 service release 6b + IZ15865 interim fix
Additional Eclipse patches and fixes
The following Eclipse patches and fixes are included in this releaseWeb Tools Platform R1.5.5 Patch P20080602124433
J2C Tools
- Updates to IMS TM Resource Adapters
- IMS TM Resource Adapter Version 10.2.0. For more information about this version see: http://www.ibm.com/software/data/ims/ims/components/1conjav125.html
- It contains a new convID field in the interactionspec
- It supports IMS conversational flow
- It supports development of MSF-based applications. (Running MSF-based applications is not supported.). Note that language support for this capability is available in English only.
The following new IMS™ TM Resource Adapters are included in this fix pack:
- Here are some additional details about this adapter:
Note: If you run IMS applications on IBM WebSphere Application Server, then you should download the IBM TM Resource Adapters from https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=imscjd
JSF Widget Library
The JSF Widget Library (JWL) supports the Safari 3.1 browser running on the Mac OS X operating system.
Portal Tools
The following portlet projects and portlet types are supported for creation and publishing on IBM WebSphere Portal Server v6.1:
- Portlet projects
- IBM
- JSR 168
- Portlet types
- Faces
- Basic
- Struts
- Empty
Note: Portal projects are not supported for WebSphere Portal Server v6.1.
Web RAD Development Tools
On the property page of the JDBC Connections project wizard, you can now add JDBC connections with automatic runtime deployment for the following additional database versions: Web services
- A new "Generate portable client" option is added to the Web services client wizard for JAX-WS runtime. When you select this option, the client packages the WSDL file in the client module, and the generated client code references the WSDL file in the client module. This allows you to run the client module on different computers, and you can deploy it to a remote server.
- A new "Preserve Web Services metadata" option is added to the WSDL2Java tab of the WebSphere JAX-RPC Code Generation preference page for Web Services (Window > Preferences > Web Services > WebSphere > JAX-RPC Code Generation > WSDL2Java).
If you enable this option, then when you run any Web Services wizards, your current JAX-RPC Web services metadata is stored in a .backup folder in the selected project.
Note: To use your backed-up configuration, you must manually copy and paste the handler and security configurations from the backed-up files in the .backup folder into the newly generated Web services deployment descriptor files.
Download Version 7.0.0.6 |
This release of Rational Application Developer for WebSphere Software contains new features and enhancements in the following areas:
Platform, operating system, and utility software enhancements:
- Microsoft® Windows® Vista Service Pack 1
- IBM Installation Manager, Version 1.1.1
J2C Tools
- Updates to IMS TM Resource Adapters
- (updated) IMS TM Resource Adapter Version 9.1.0.1.5.b For more information about this version see: http://www.ibm.com/software/data/ims/ims/components/1conjav124.html
- (updated) IMS TM Resource Adapter Version 9.1.0.2.5.a For more information about this version see: http://www.ibm.com/software/data/ims/ims/components/1conjav124b.html
- (new) IMS TM Resource Adapter Version 10.1.1 For more information about this version see: http://www.ibm.com/software/data/ims/ims/components/1conjav125.html
- Updates to CICS ECIResource Adapters
- CICS ECIResource Adapter V5.1.0.3
- CICS ECIResource Adapter V6.0.2.2
- CICS ECIResource Adapter V7.0.1.1
http://www.ibm.com/support/docview.wss?uid=swg24008817
- Improvements to data binding file generation
Web services
- Web services can be created from Java beans in Java projects
XML Tools
- New "Remove Unused Imports" action
Download Version 7.0.0.5 |
This release of Rational Application Developer for WebSphere Software contains new features and enhancements in the following areas:
- Platform, operating system, and utility software enhancements:
- Microsoft® Windows® XP Professional x64 Edition (running in 32-bit mode on AMD and Intel® processors)
- IBM Installation Manager, Version 1.1.0.1
Download Version 7.0.0.4 |
This release of Rational Application Developer for WebSphere Software contains contains new features and enhancements in the following areas::
- Rational RequisitePro Integration
- J2EE Connector (J2C) tools: J2C migration
- User assistance: new AJAX portlet sample
Rational RequisitePro integration
Note: The documentation for the following new features is not included in the online Help.
- The new Requirement Editor view
The 7.0.0.4 release includes a new Requirement Editor view. In this view, you can edit the name, description, attributes, and traceability for a requirement. You can also add optional HTML tags to format the description.
If you add HTML tags to the description, the formatted text is displayed on the Preview page and in the Requirement Text view. The HTML tags are visible in Attribute Matrix views, on the Description page, and in the Requirement Properties window in Rational RequisitePro®. Do not use HTML tags to format the description of requirements that are located in Microsoft® Word documents.
To view and modify a requirement:
1. In the Requirement Explorer view, double-click a requirement.
2. In the Requirement Editor view, on the Overview page, view or modify the text for the requirement in the Description field. Optionally, you can add HTML tags and click Preview to view them as formatted text.
3. In the Details section, specify attribute values.
4. Click the Traceability tab to view and modify traceability to and from other requirements.
5. On the toolbar, click Save.
- The new Requirement Text view
The 7.0.0.4 release includes a new Requirement Text view. Click a requirement in any requirement view to display the name and description of a requirement in the Requirement Text view. Requirements that use HTML tags are displayed as formatted text in this view. Text in this view is read-only; use the Requirement Editor view to modify the name or description. Click the Pin Text View icon in this view or click requirements in other views to continue to display the current requirement text. - Links to WebSphere Business Modeling
Links between Rational RequisitePro requirements and WebSphere Business Modeling elements are now displayed in the UML domain.
J2EE Connector (J2C) tools: J2C migration
The behavior for the J2C migration feature has changed:
Old behavior: When using the J2C Migration wizard, if your workspace does not already contain a corresponding connector project, then a corresponding connector project is imported and the target server for the project is set to WebSphere Application Server, Version 6.1. Otherwise, the corresponding connector project already in your workspace is used for J2C migration.
New behavior: When using the J2C Migration wizard, if your workspace does not already contain a corresponding connector project, then a corresponding connector project is imported and the target server for the project is set to WebSphere Application Server, Version 5.1. Otherwise, if your workspace already contains the corresponding connector project:
- If the target server for the connector project is WebSphere Application Server, Version 5.1, then it will be used for J2C migration.
- If the corresponding connector project in your workspace is does not have its target server set to WebSphere Application Server, Version 5.1, then a new connector project is created that has its target server set to WebSphere Application Server, Version 5.1 and is named following the convention <old name>_51, where <old name> is the name of the connector project already in your workspace.
User assistance: new AJAX portlet sample
A new portlet showcasing the AJAX (Asynchronous JavaScript™ and XML) technology has been added to the portlet technology samples in the Samples Gallery.
Download Version 7.0.0.3 |
This release of Rational Application Developer contains the following new features and enhancements:
- Platform, operating system, and software integration support enhancements:
- Red Hat Enterprise Linux® 4 Update 5
- Citrix Presentation Server 4.0.
Note: - The server must run on an operating system that is supported by Rational Application Developer.
- You must use a floating license for sharing license keys with multiple users. The use of an authorized user license is not supported.
- IBM Installation Manager, Version 1.0.0.4 includes the enhancement to allow updates to be rolled back. For information, see the version 1.0.0.4 readme file at http://download.boulder.ibm.com/ibmdl/pub/software/rationalsdp/v7/im/1004/docs/readme/readme.html.
- IBM WebSphere Application Server, Version 6.0.2 Fix Pack 15
- IBM WebSphere Application Server, Version 6.1 Fix Pack 9
- IBM WebSphere Application Server, Version 6.1 Feature Pack for Web Services
- Eclipse Modeling Framework (EMF) 2.2.3. For information, visit the Eclipse Modeling Framework home page at http://www.eclipse.org/modeling/emf/downloads/?project=emf.
- New installable features:
Note:
New installable product features are not displayed and cannot be added while running the Update Packages wizard in Installation Manager. To view and add new installable product features, run the Modify Packages wizard in Installation Manager after you have installed the fix pack.
- Web services feature pack Provides features for assembling and deploying reliable, asynchronous, secure, and interoperable Java® Web services for application components. The Web services feature pack is designed for IBM WebSphere Application Server, version 6.1, extended with the WebSphere Application Server feature pack for Web services. This feature supports the development of Web services from annotated Java or from Web Services Description Language (WSDL) using any XML Schema.
- IBM WebSphere Application Server, version 6.1 Feature Pack for Web services Upgrades IBM WebSphereApplication Server, version 6.1 to version 6.1.0.9 and installs the runtime required to support the Feature Pack for Web Services.
The WebSphere Application Server V6.1 Feature Pack for Web Services extends the capabilities of WebSphere Application Server V6.1 to enable Web services messages to be sent asynchronously, reliably, and securely, focusing on interoperability with other vendors and to provide support for the Java API for XML Web Services (JAX-WS) 2.0 programming model.
The Feature Pack for Web Services introduces a set of Web services standards that support interoperable and reliable Web services applications. You can send messages asynchronously, which means 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 your messages are not vulnerable to attack. You can be confident that your communication is reliable and reaches its destination while interoperating with other vendors.
JAX-WS simplifies application development through a standard, annotation-based model to develop Web services 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.
Simplified management using Web services profiles makes it easy to configure and reuse configurations, so you can introduce new Web Services profiles seamlessly in the future. These configurations are captured in a grouping called Policy Sets which allows you to select and associate different qualities of service with an application. You can configure policy sets to allow only those capabilities within a given WS-Interoperability (WS-I) profile, thereby limiting and ensuring that the only configurable portions are those that are desired. WS-I is an open industry organization chartered to promote Web Services interoperability across platforms, operating systems and programming languages.
The Feature Pack for Web Services includes support for:
- New Web services standards, including:
- Web Services Reliable Messaging (WS-RM)
- Web Services Addressing (WS-Addressing)
- SOAP Message Transmission Optimization Mechanism (MTOM)
- New standards-based programming model support:
- Java API for XML Web Services (JAX-WS 2.0)
- Java Architecture for XML Binding (JAXB 2.0)
- SOAP 1.2
- SOAP with Attachments API for Java (SAAJ 1.3)
- EJB domain modeling enhancements: Enterprise JavaBeans (EJB) domain modeling was enhanced by adding property views for these items:
- EJB beans
- CMP fields of entity beans
- EJB interfaces
- EJB Java archive (JAR) files
- WSDL domain modeling enhancements: The WSDL domain modeling has been enhanced to support:
- Creating a binding to a port type in a different WSDL file
- Assigning messages from one WSDL file to an operation in a different WSDL file
- Importing WSDL/XSD files
- Importing existing local and remote XSD schemas
Download Version 7.0.0.2 |
This release of Rational Application Developer for WebSphere Software contains the following new features and enhancements:
Platform, operating system, and browser support enhancements:
Eclipse 3.2.2 (for compatibility with previous releases and known issues, see the Eclipse 3.2.2 Project Release Notes).
Mozilla Firefox 2.0.
IBM Runtime Environment for Windows®, Java™ 2 Technology Edition, Version 5.0 service release 4.
IBM Runtime Environment for Linux®, Java 2 Technology Edition, Version 5.0 service release 4.
Microsoft® Internet Explorer 7.0.
Microsoft Windows Vista Business, Vista Enterprise, and Vista Ultimate (for information about installing Rational Application Developer for WebSphere Software, Version 7.0.0.2 on Windows Vista.
WebSphere Portal Server, Version 6.0.1 is compatible as a target runtime. (The user interface will continue to display WebSphere Portal v6.0 as the type of runtime.)
Transformation authoring:
Pathmap URI support: The resource selection windows in the Transformation Mapping editor and the Auxiliary Model page of the Transformation Configuration editor now enable you to specify a URI that is a pathmap; for example "pathmap://UML_LIBRARIES/UMLPrimitiveTypes.library.uml".
Registered UML profile browsing: You can browse and select registered UML profiles from the resource selection windows in the Transformation Mapping editor.
Automatic import of referenced models: Referenced models are now automatically imported when submaps that reference elements or features in them are created by using the "New" submap feature.
Automatic resolution of simple cross-model references: Previously, if a deferred reference could not be resolved because there was no corresponding object created for it, then the transformation failed and an error message was displayed. Now, the product checks for the following conditions and, if both conditions are met, then the original object (for example, an integer) is used to resolve the reference:
The reference is to an object in a different model from the main source that is being transformed.
If the type of the original reference is compatible with the new reference in the transformed model.
Disabling creation of mapping models in non mapping projects: The New Transformation Mapping wizard displays an error message and disables the Finish button if you attempt to create a mapping model in a non mapping project, which is a project without the proper project nature.
J2EE Connector (J2C) tools, updates, and enhancements for IMS™ TM resource adapters:
Alternate Client ID: The alternate client ID enhancement allows Java client applications to retrieve messages from any asynchronous output queue (OTMA Tpipe) by specifying an alternate client ID on shareable persistent socket connections. Prior to this enhancement, a client could retrieve asynchronous messages from a Tpipe in two ways. The first approach was to use dedicated persistent socket connections. However, the use of dedicated persistent sockets could cause duplicate client ID problems in a Sysplex distributor environment. The second approach was to use shareable persistent socket connections. This approach was too limiting because the original interaction that led to the generation of asynchronous output and the retrieval of that asynchronous output would have to occur on the same socket (usually within the same application). With this enhancement, both of these limitations are eliminated.
SSL Null Encryption: The SSL null encryption enhancement allows you to specify "ENULL" encryption for a connection factory. This enables you to use the authentication capability provided for an SSL socket connection without incurring the overhead of encrypting each message that flows over that connection. Prior to this enhancement, you could only specify that the connections created by a connection factory use either "STRONG" or "WEAK" encryption, which meant that strong or weak data encryption would be used on the connections. You will find this new feature useful when you want to prevent access to a server by internal users with malicious intent, but you are not concerned about encrypting the data that flows to and from that server because the data flow takes place behind your firewall.
For more information on these new features, see the IMS TM Resource Adapter User's Guide and Reference, available from the IBM Information Management Software for z/OS® Solutions Information Center.
WSDL domain modeling enhancements:
Creation of XML Schema Definition (XSD) elements within a Web Service Definition Language (WSDL) file, including XSD simple and complex types
Editing of XSD elements, such as changing XSD types and adding XSD elements to existing XSD complex types
Download Version 7.0.0.1 |
This release of Rational Application Developer for WebSphere Software does not contain new features and enhancements.
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg27012391