Rational Connector for SAP Solution Manager

Product Release / Trial | May 14, 2013
This is not the most recent version. We recommend Rational Connector for SAP Solution Manager . This is made available for archival purposes and may contain bugs and/or security vulnerabilities. If you do download this version, it is being provided AS IS, without warranties of any kind, including the implied warranties of merchantability and fitness for a particular purpose. We strongly advise you review the support pages for this version and update the product or take actions recommended therein. Security bulletins contain instructions for the security vulnerability addressed therein, and may require upgrading to a newer version. Link to security vulnerability blog: IBM PSIRT blog.

The downloads for this milestone are no longer available.

Rational Connector for SAP Solution Manager Release Notes

Rational Connector for SAP Solution Manager Release Notes

This release is a service release of Rational Connector for SAP Solution Manager Version 4.0.0. The release contains fixes for defects. For information about documentation, support resources, software and hardware requirements, see the Getting Started page. For information about installation upgrade steps, see the Upgrading page.

Use the queries below to see the important fixes and issues in the release. You might also want to read the Jazz Foundation 4.0.2 Release Notes, the Rational Team Concert 4.0.2 Release Notes, the Rational Requirements Composer 4.0.2 Release Notes, and the Rational Quality Manager 4.0.2 Release Notes.

Fixes in this Release

The Version release of Rational Connector for SAP Solution Manager includes non-APAR defect fixes.

-- Missing SSLEnabled="true" from server.xml The SSLEnabled="true" attribute was missing from the element defining an SSL port. The attribute is now set by default.
-- Rational Requirements Composer HTTP Client assumes the same host and port number Rational Requirements Composer delegates its authentication to the Jazz Team Server where it was assumed that the Jazz Team Server was on the same host and port number as the Rational Requirements Composer web application. Now the Jazz Team Server can be on a different host and port number from the web application.
-- Requirement artifact types are wrong when there are multiple instances of the same type For both requirement and collection types, it was assumed that there was a single instance of each of these two types. The first one was selected from a list of length 1. This is now fixed.
-- Duplicate RRC artifacts created after user deletes RRC nodes If from a Rational Requirements Composer folder, you removed individual artifacts or folders, the connector produced duplicate entries for the second+ push, because it never removed the old entries from it's database. This is now fixed.
-- TestPlan to Requirement Collection links not updated If the requirement collection to test plan link was not set correctly, or was reset, that value was not updated. This is now fixed.
-- Use project title instead of project name in RQM OSLC mapping The project title is now used instead.
-- Default ports, 80 and 443, confuse the SAP Connector server The use of default ports is now fixed.

Known problems and workarounds

For a list of the known problems and workarounds that are published as jazz.net workaround articles, view the Rational Connector for SAP Solution Manager 4.0.0 workaround articles jazz.net query.

For a list of post-release issues documented by IBM Rational Support, view the Rational Quality Manager family, SAP Connector IBM Support Portal query.