This file provides important information about enhancements and fixes in webMethods ebXML Module 6.0.1 Service Pack 1. For information about enhancements and fixes in previous webMethods ebXML Module releases, see the readme for those releases.
1.0 Enhancements
2.0 Included Fixes and Service Packs
5.0 Added and Removed Services and APIs
6.0 Enhancements and Fixes in Previous Release
None.
webMethods ebXML Module 6.0.1 SP1 includes the following fixes that were shipped since the last release.
1-XCSG3 (WmebXML_6-0-1_Fix16)
At Integration Server startup or restart or when the WmebXML package is reloaded, extra ebXML processing rules are created in the processing rules list for Trading Networks (and seen in the Trading Networks console). This fix addresses this issue and prevents ebXML processing rules from being duplicated.
1-W1JSL (WmebXML_6-0-1_Fix15)
When exchanging messages, the error message "Unable to construct mime message" is reported in the Transaction Analysis/Activity log. This error occurs with ebXML Module 6.0.1 installed on Integration Server 6.5 with all 13 webMethods ebXML Module fixes applied.
webMethods ebXML Module 6.0.1 supports the wm.ebxml.mimeBodyEncoding system property. If this property is not set in the config.cnf file, the default setting is set to 'binary'.
This fix corrects the wm.ip.ebxml.coder:createEnvelopeStream service to set 'binary' as a default value for the wm.ebxml.mimeBodyEncoding property.
1-UL8KD (WmebXML_6-0-1_Fix14)
When sending ebXML messages, webMethods ebXML Module 6.0.1 makes the number of attempts to send the message, as set in Trading Networks. If it fails to receive an Acknowledgement from the partner, webMethods ebXML Module 6.0.1 sends itself an ebXML Error message. When the ebXML Module receives an ebXML Error message, it incorrectly changes the User Status of the initiating document to 'SendMessage:<numberOfAttempts>'.
Additionally, webMethods ebXML Module 6.0.1 is unable to relate the generated error document to the ebXML sending message document.
This fix changes the User Status of the initiating document from 'SendMessage:<numberOfAttempts>' to 'SendMessage:Err'. It also generates the valid error message document which is related to the original message sent by the sender.
1-QN3JG (WmebXML_6-0-1_Fix13)
Error handling issue with wm.ip.ebxml.cpa services. When the wm.ip.ebxml.cpa.util:pickPackaging service is run and an error occurs, the service returns the reason as /error/errorMsg.
However, the wm.ip.ebxml.cpa:routeMessage/send/sendBizDoc service defines "errMsg=%/error/errMsg%" in EXIT steps for error handling. Therefore no reason will be returned correctly.
This fix corrects the error handling issue with wm.ip.ebxml.cpa services.
1-TFU0H (WmebXML_6-0-1_Fix12)
The XML Signature for webMethods ebXML Module does not include the C14N transform text. This fix corrects the signature.
1-TFOCI (WmebXML_6-0-1_Fix12)
webMethods ebXML Module does not send multiple payloads in the same ebXML message. This fix corrects the payload issue.
1-T9Y3L (WmebXML_6-0-1_Fix12)
When webMethods ebXML Module sends an ebXML message asynchronously and requests an unsigned ack, the partner does not like the response that is sent for the ack. This fix corrects the response.
1-T9Y0P (WmebXML_6-0-1_Fix12)
When webMethods ebXML Module sends an ebXML message and requests a Sync Ack back from the partner, webMethods ebXML Module does not receive the sync ack even though the partner says that they have sent the sync ack. This fix enables webMethods ebXML Module to correctly receive the sync ack from the partner.
1-T9XX7 (WmebXML_6-0-1_Fix12)
The http response sent by webMethods ebXML Module for asynchronous messages received is multipart/related but has no boundary and no mime parts. This fix corrects the http response for asynchronous messages received.
1-T7A9L (WmebXML_6-0-1_Fix12)
XML signature verification fails when webMethods ebXML Module receives XML signed documents from partners. This fix corrects the verification.
1-SYQMV (WmebXML_6-0-1_Fix12)
When webMethods ebXML Module sends an ebXML message using the TPA, an unsigned ack is being requested even though the value for ResponseRequest/@ackRequested is set to "none". This fix corrects the ebXML message.
1-UJOJ9 (WmebXML_6-0-1_Fix12)
This issue was created to address all issues that were found during webMethods ebXML Module 6.0.1 interoperability testing. All reported issues have been addressed in this fix.
1-TFYKV (WmebXML_6-0-1_Fix10)
The webMethods ebXML Module incorrectly considers incoming messages expired because it interprets timestamps without the 'Z' indicator (for UST/GMT) as local time.
This is not in compliance with the ebXML standard as defined in http://www.ebxml.org/specs/ebMS2.pdf. The standard states that timestamps are always in UST and the 'Z' indicator is optional.
This fix correctly handles the timezone as UST without the 'Z' indicator for incoming messages.
1-RCB9Z (WmebXML_6-0-1_Fix9)
Cannot use base64 encoding MIME message when sending papiNet over SMTP. The fix provides a way for a user to use a TPA or a system property to control the MIME encoding scheme. The details of this fix are as follows:
1. To use a TPA, this fix adds a parameter in the TPA's DataScheme:OtherParams/MimeBodyEncoding
This parameter allows a user to set the MIME body encoding scheme to one of the following values:
binary
base64
7bit
8bit
quoted-printable
uuencode
The default value is "binary".
To reduce the impact of this fix, this parameter is not supported in all routing related services.
2. To set the MIME encoding for routing related services, use the system property wm.ebxml.mimeBodyEncoding in WmebXML/config/config.cnf. This property sets the encoding scheme globally in the MIME bodies. The possible values of this property are the same as the ones in note 1 above.
Note that using the OtherParams/MimeBodyEncoding parameter in the TPA overrides the value in the wm.ebxml.mimeBodyEncoding system property.
1-OS34R (WmebXML_6-0-1_Fix8)
Cannot persist payload content part in Trading Networks (TN) transaction store. This fix corrects this issue.
1-OOKR1 (WmebXML_6-0-1_Fix6)
The wm.ip.ebxml.rules:routeMsg service does not populate the receiver's location element in the TraceHeader when HTTPS is used.
The wm.ip.ebxml.rules:routeMsg service has now been corrected to send the appropriate acknowledgement.
1-OOKRO (WmebXML_6-0-1_Fix6)
In multi-hop messaging, a connection error stops the retries of reliable delivery.
This issue has been resolved.
1-OOKSV (WmebXML_6-0-1_Fix6)
createErrorMsg Fix from ebXML 4.6 Fix 5 was not included in webMethods ebXML Module 6.0.1.
1-OGUB4 (WmebXML_6-0-1_Fix6)
Take out the option of updating existing profiles in the service, importCPA. Now you can only create new profiles from a CPA.
1-OOKR1 (WmebXML_6-0-1_Fix6)
The wm.ip.ebxml.rules:routeMsg service does not populate the receiver's location element in the TraceHeader when HTTPS is used.
The wm.ip.ebxml.rules:routeMsg service has now been corrected to send the appropriate acknowledgement.
1-OOKRO (WmebXML_6-0-1_Fix6)
In multi-hop messaging, a connection error stops the retries of reliable delivery.
This issue has been resolved.
1-OOKSV (WmebXML_6-0-1_Fix6)
createErrorMsg Fix from ebXML 4.6 Fix 5 was not included in webMethods ebXML Module 6.0.1.
1-OGUB4 (WmebXML_6-0-1_Fix6)
Take out the option of updating existing profiles in the service, importCPA. Now you can only create new profiles from a CPA.
1-N5EJU (WmebXML_6-0-1_Fix5)
Content-IDs for payloads are not unique. In this fix, a globally unique ID is generated for all Content-IDs.
1-N5EKR (WmebXML_6-0-1_Fix5)
XML signature cannot be verified if no namespace declaration is present in the Signature element. The issue is caused by a defect in Entrust's XML Signature library. This fix provides a workaround for the Entrust defect.
1-N5ELQ (WmebXML_6-0-1_Fix5)
Service wm.ip.ebxml.cpa:send crashes. This issue is caused by a different platform encoding scheme that creates a non-standard content-type string. In this fix, the Java mail API is used to create content-type string.
1-N5EIV (WmebXML_6-0-1_Fix5)
Addressable CID URI does not conform to standard. In this fix, all addressable Content-IDs are in the form of "<Content-ID>".
1-MZV2V (WmebXML_6-0-1_Fix4)
Local to UTC time is converted incorrectly, resulting in an incorrect value for TimeToLive. With this fix, the TimeToLive value is correct per the local time zone. No TimeToLive value in the TPA will not populate ebXML Header.
1-M4YTH (WmebXML_6-0-1_Fix3)
webMethods 6.0.1 ebXML routeMessage is broken on IS 6.0.1, due to a different behavior in Flow Engine in processing the path expression, "Payloads/Manifest" on IS 6.0.1 platform. Now the path expression is changed to "Payloads[0]/Manifest".
1-IWPN0 (WmebXML_6-0-1_Fix3)
Optimization of webMethods ebXML HTTP 500 handling performance.
This fix adds a new configuration property: wm.ebxml.simpleSOAPErrorProcessing to control how a SOAP 500 error is handled. This property is in the config.cnf file in the <IntegrationServer_directory>/packages/WmebXML/config directory.
- If the value of the property is set to "false", a SOAP error will be logged, the UserStatus of the related bizdoc is changed to "SendMessage:err", and an Error bizdoc is generated (which is the old behavior).
- Otherwise the SOAP error is logged and the UserStatus of the related bizdoc is changed to "SendMessage:err" only.
1-MGG4X (WmebXML_6-0-1_Fix3)
HTTP response 2xx interpreted as an error.
The webMethods ebXML Module interprets all HTTP response codes except 200 as an error. According to the HTTP and ebXML standards, all 2xx codes are success codes; other Message Service Handler (MSH) software will return 2xx codes on success.
The webMethods ebXML Module now correctly interprets the 2xx error codes as success codes.
1-MFMH5 (WmebXML_6-0-1_Fix3)
Acknowledgment from webMethods has no Acknowledgment element on AckRequested elements.
When the sender requests an acknowledgement, webMethods ebXML Module creates the acknowledgement but does not include a required Acknowedgement element. Additionally, when the sender does not request an acknowledgement, webMethods ebXML Module sends an acknowledgement anyway.
The createMsg service has now been corrected to send the appropriate acknowledgement.
1-LZKLT (WmebXML_6-0-1_Fix2)
ebXML sync ack format structure is incorrect. The http response headers are not set up correctly. This fix corrects the headers.
1-LTU79 (WmebXML_6-0-1_Fix1)
XML signature is broken after Integration Server (IS) SP1 or SP2 is installed, due to the way IS class loader behaves. This fix also contains IAIK IXSIL 1.1.0 library extracted from Entrust Java Toolkit 6.1 SP2. After you have applied the patch, you no longer need to get separate IAIK IXSIL library from IAIK.
The issues listed below have been resolved in webMethods ebXML Module 6.0.1 SP1 but were not previously released in any fixes or service packs.
1-UPPH5
The webMethods ebXML Module sample packages (WmebXMLSample) is missing .access files in the pub directory and in subsidiary directories to pub (that is, cm, cpa). That means that any authenticated user can retrieve any of the files in that directory, not just administrators. This fix adds .access file so that only users with administrator privileges can access files under the WmebXMLSample/pub folder.
None.
None.
To view information about the previous release of webMethods ebXML Module, see the previous readme on the webMethods Bookshelf.
EBXML-E&F-601SP1-20051025