This file provides important information about enhancements and fixes in webMethods RosettaNet Module 6.0.1 Service Pack 2. For information about enhancements and fixes in previous webMethods RosettaNet Module releases, see the readme for those releases.
1.0 Fixes and Service Packs Included in This Release
2.0 Enhancements
3.0 Resolved Issues
5.0 Added and Removed Services and APIs
6.0 Enhancements and Fixes in Previous Release
webMethods RosettaNet Module 6.0.1 Service Pack 2 includes the following fixes and service packs that were shipped since the last release.
- RN_6-0-1_Fix29
- RN_6-0-1_Fix31
- RN_6-0-1_Fix32
- RN_6-0-1_Fix33
- RN_6-0-1_Fix35
- RN_6-0-1_SP1
- RN_6-0-1_SP1_Fix1
- RN_6-0-1_SP1_Fix2
- RN_6-0-1_SP1_Fix3
- RN_6-0-1_SP1_Fix4
- RN_6-0-1_SP1_Fix5
- RN_6-0-1_SP1_Fix6
- RN_6-0-1_SP1_Fix7
For detailed information on these fixes and service packs for webMethods RosettaNet Module, see the Knowledge Base on the webMethods Advantage Web site.
webMethods RosettaNet Module 6.0.1 SP2 includes no new enhancements.
The issues listed below have been addressed in this release.
RosettaNet Module ignores the settings for the Delivery Maximum Retries parameter and the Wait Between Retries parameter when both parameters are set to 0.
1-Z2XDN (RN_6-0-1_Fix31)
The RosettaNet Module receive service (wm.ip.rn:receive) results in an HTTP response status of 400.
1-12GH1T (RN_6-0-1_Fix32)
Process Instance Identifier not retrieved correctly by the RosettaNet Module when the focal role contains a "-" character.
1-149JOK (RN_6-0-1_Fix33)
RosettaNet Object (RNO) Attachment header is missing the Content Disposition field when viewing the header through Trading Networks.
1-15LAMW (RN_6-0-1_Fix35)
In webMethods RosettaNet Module, when defining a partner profile in Trading Networks, if the 'Port' field is left blank the delivery of the document fails.
RN_6-0-1_SP1
webMethods RosettaNet Module 6.0.1 Service Pack 1 includes fixes from RN_6-0-1_Fix1 to RN_6-0-1_Fix27.
1-11M0EI (RN_6-0-1_SP1_Fix1)
The receive service incorrectly assumes that the HTTP header names are case sensitive.
1-11MUHI (RN_6-0-1_SP1_Fix2)
Unable to export TN data from TN Console after applying RosettaNet 6.0.1 SP1.
1-13DSTW (RN_6-0-1_SP1_Fix3)
In the webMethods RosettaNet Module 6.0.1, the Pip3A4PurchaseOrderConfirmation document once received by the customer causes a process failure.
1-111U22 (RN_6-0-1_SP1_Fix4)
RosettaNet Module throws errors on start up.
1-13DSTW (RN_6-0-1_SP1_Fix4)
The Pip3A4PurchaseOrderConfirmation document once received by the customer causes a process failure.
1-11MUHI (RN_6-0-1_SP1_Fix4)
Unable to export TN data from TN Console after applying RosettaNet 6.0.1 SP1.
1-11M0EI (RN_6-0-1_SP1_Fix4)
The receive service incorrectly assumes that the HTTP header names are case sensitive.
1-137NRO (RN_6-0-1_SP1_Fix5)
The Message Tracking ID in the Delivery Header of the messages is not uniquely generated by RNIF 2.0 transport.
1-WAVLR (RN_6-0-1_SP1_Fix5)
In webMethods RosettaNet Module, when you click on the RNIF 2.0 certification logo in the Rosettanet About page, a javascript error is displayed.
1-15DFR5 (RN_6-0-1_SP1_Fix5)
In webMethods RosettaNet Module, if BizDocuments are sent to a custom receive service instead of a RN receive service, the contentInfo and protocolInfo are not being populated in the pipeline for RNIF 2.0 framework.
1-156CG0 (RN_6-0-1_SP1_Fix5)
In webMethods RosettaNet Module, the wm.ip.cm.handlers: processUnhandledDocument service when invoked throws an incorrect exception.
1-156CGW (RN_6-0-1_SP1_Fix5)
In webMethods RosettaNet Module, when processing an unhandled document the flow service throws an exception.
1-XZ51E (RN_6-0-1_SP1_Fix6)
In webMethods RosettaNet Module, after applying RN_6-0-1_Fix1, sending NOF fails by throwing an error "No matching conversation script".
1-135IDV (RN_6-0-1_SP1_Fix6)
In webMethods RosettaNet Module, the flow service "wm.ip.profile:getPreferredProtocol" refers to Alternate Protocol as the default protocol, which is incorrect.
1-17IVZK (RN_6-0-1_SP1_Fix7)
In webMethods RosettaNet Module, the condition where when the same document is received more than once for the same conversation ID is not being checked.
1-1IC38J (RN_6-0-1_SP1_Fix7)
When receiving documents for RNIF 2.0 transport, webMethods RosettaNet Module throws the error "Invalid x-RN-Version".
None.
None.
To view information about the previous release of webMethods RosettaNet Module, see the previous readme on the webMethods Bookshelf.
ESTDRN-E&F-601SP2-20070412