SAP Transport Release Notes - Mule 3

Upgraded library dependencies(SE-23972).

Fixed vulnerable dependencies to improve connector security.

Fixed an issue that caused metadata on an inbound IDoc to not be updated. (SE-15784)

Updated connector icons.

Updated connector icons.

Fixed many of the dependencies' security issues.

Configuring SNC in SAP connector was not working.

String JCO_MSHOST = "jco.client.mshost";
String JCO_MSSERV = "jco.client.msserv";
String JCO_R3NAME = "jco.client.r3name";
String JCO_GROUP = "jco.client.group";
String JCO_SAPROUTER = "jco.client.saprouter";

Fixed the SAP connector not sending back to SAP when a source used the request-response pattern without using the XML-to-SAP function. (SE-11761)

Outbound endpoint timeout doesn’t work - When calling an RFC that takes a long time to complete, the responseTimeout parameter was not considered, and waited for a long time, and no error or messages were triggered. This was fixed by throwing an exception when the timeout value is reached.

Outbound endpoint duplicate connection to SAP backend - If an error or timeout occurs, a second connection was triggered behind the scenes. Fixed by removing the duplicate retry call in the exception handling block.

Destination Provider reference gets lost after hot redeploy of an application (such as modifying the mule-config.xml).

Transaction ID (TID) not copied to the outbound scope - This issue occurs when making outbound calls with the Mule runtime 3.8.x EE, which introduced modifications in the transaction management implementation that affected the connector. The SAP transaction component would never initialize a transaction, resulting in a null TID when executing #[message.outboundProperties.sapTid]. The issue is now fixed and transactions are again working with Mule 3.5.0 to 3.8.x. In addition to the present patch, a workaround is also available by wrapping the SAP component in a Transactional scope.

NoSuchMethodError getDefaultEncoding() - A regression bug introduced in SAP 3.1.1 as a result of fixing an encoding issue. This exception arises only in Mule 3.5.0 EE because the method getDefaultEncoding() is not present in that version. It was introduced in 3.6.0.

IDocs containing negative numbers fail to be parsed - When sending an IDOC to SAP with a field of datatype NUMC, the conversion fails. A similar situation occurs if, for example, an unknown field is added to the IDoc. JCo can handle this content by configuring a series of parsing options but not the SAP connector. In the current version, these options are exposed through the System property mule.sap.idoc.parserOptions. Multiple options can be combined using a comma (",") separator, for example: mule.sap.idoc.parserOptions=PARSE_WITH_FIELD_VALUE_CHECKING,PARSE_IGNORE_UNKNOWN_FIELDS.

PARSE_ACCEPT_ONLY_XMLVERSION_10
PARSE_ACCEPT_ONLY_XMLVERSION_11
PARSE_ACCEPT_ONLY_XMLVERSIONS_10_TO_11
PARSE_IGNORE_INVALID_CHAR_ERRORS
PARSE_IGNORE_UNKNOWN_FIELDS
PARSE_REFUSE_UNKNOWN_XMLVERSION
PARSE_REFUSE_XMLVERSION_10
PARSE_REFUSE_XMLVERSION_11
PARSE_WITH_FIELD_VALUE_CHECKING
PARSE_WITHOUT_FIELD_DATATYPE_CHECKING

Destination Provider reference gets lost after hot redeploy of an application (that is, modifying the mule-config.xml)

When a field doesn’t have a name, SAP Connector presents a metadata for this field as ANONYMOUS.

Failure to refresh metadata - This is related to the previously fixed issue "Incomplete disposal of JCo classloader" though, this time, it affected the metadata when loading JCo libs at Mule application level (from the Global Configuration). In this version, the issue has been resolved and JCo can be used both in a shared and in a standalone environment.

DataSense cannot display metadata for extended IDocs - IDoc (and BAPI) names may contain namespaces in the form of /PACKAGE/IDOC_TYPE, PACKAGE-IDOC_TYPE, PACKAGE1-/PACKAGE2/IDOC_TYPE, etc. In previous versions of the connector, these namespaces were incorrectly escaped when building the metadata for DataSense, resulting in a truncated XML. In the present version, this issue is fixed and the XML is properly generated for any compound IDoc or BAPI name.

Wrong encoding for XML output - Until this version, if the encoding attribute was set in the endpoint but there was also a Message Transformer (that is, DataWeave) present in the flow, placed before the SAP component, explicitly overriding the encoding, the latter would be applied to the XML output. This was not the right behavior. Now, if the encoding attribute is defined in the endpoint and it is different to the System’s default, it will have precedence over any other encoding configured before.

Destination Provider reference gets lost after hot redeploy of an application (that is, modifying the mule-config.xml)

Enhanced IDoc Metadata - Additional information has been added to both DataSense/DataWeave and XML templates:

Repository Cache Invalidation - When a customer modifies the structure of an SAP Function Module or BAPI, the changes are not reflected in the payload of the call, no matter if the change has already been applied and activated in the SAP instance. Re-deploying the application that made the call to the FM or BAPI has no effect either since the repository is common and shared by all the applications running in the same Mule runtime. JCo provides a functionality to remove current FM/BAPI information from the cache. However, this feature is transparent to the user. The disposal of the cache is triggered before any outbound or inbound call is made.

Incomplete disposal of JCo classloader when sharing JCo dependencies between several applications - The second time a user performed a Test Connection, a Refresh Metadata or a Search of a Function/IDoc inside a shared JCo environment, a Destination XX could not be created: java.lang.RuntimeException: File XX.jcoDestination does not exist or Destination XX does not exist exception was thrown. This happened because the JCo destination reference wasn’t properly unregistered from the DestinationDataProvider. However, the issue it not present when installing JCo libraries in the local classpath of a Mule application.

Failure to send outbound IDoc of type ByteArrayInputStream - Previously, since version 3.0.0, when trying to transform an IDoc built from a ByteArrayInputStream, the conversion failed with an IllegalArgumentException because the payload was passed with a NULL value. Now, the issue is fixed and the transformation correctly performed.

Destination Provider reference gets lost after hot redeploy of an application (that is, modifying the mule-config.xml)

Enhanced DataSense for IDocs - For every IDoc field, additional information is displayed as part of the UI label: the data type, its length, and a description.

XML External Entities (XXE) vulnerability - By default, XML parsers are weakly configured and are therefore vulnerable to XML External Entity attacks (for example, disclosure of confidential data, denial of service, server side request forgery) when the application parses XML input. To prevent XXE, DTDs (External Entities) have been completely disabled in all the XML parsers used by the connector.

Metadata retrieval results in timeout - This is a result of additional information being displayed to enhance DataSense in version 3.0.0. The implementation has been improved and timeout is no longer being triggered. However, metadata generation takes a bit longer than in previous versions.

IDoc attributes "BEGIN" and "SEGMENT" not displayed in DataSense - Regression issue introduced in version 3.0.0. Now both DataSense UI and DataWeave correctly display these attributes, which are required to properly build the XML of a given IDoc.

Redundant XSD attribute names - To improve readability, the sap prefix has been removed from the XSD/XML template. Attributes sapOptional, sapType, sapLength and sapDescription have been renamed to optional. dataType, length and description respectively.

Parameters of type XSTRING are passed as String - XSTRING represents a byte array in ABAP. This data type was not being handled by the connector. The value was passed without any conversion. In this version, XSTRING parameters are received as a Base64 string (the user is in charge of encoding it) and converted to a byte array.

Connector hangs when application is redeployed - This occurs when deploying an application that uses an Inbound endpoint inside a Mule EE Standalone distribution. When un-deploying the app and performing a second re-deploy attempt, the Mule gets stuck and does not finish deploying it completely (the log will end at New app 'my-sap-app' instead of Started app 'my-sap-app'). As a workaround, the default value of operationTimeout has been changed from 0 (zero) -Mule would block forever until the JCo server operations to execute- to 30 (thirty) seconds. For previous versions of the connector, where the default value is 0, the workaround is to explicitly declare operationTimeout with a value greater than 0, similarly to the example below:

<sap:inbound-endpoint connector-ref="SAP" operationTimeout="5" type="idoc" ... />

Although the connector hangs when an application is redeployed, a workaround has been provided in the previous section. The underlying issue persists and will be addressed in a future release.

Destination Provider reference gets lost after hot redeploy of an application (that is, modifying the mule-config.xml)

Supports definition of SAP JCo Client Extended Properties using MEL.

Metadata generated at inbound endpoint by SAP is now organized by input and output.

Enhanced DataSense, displaying additional information:

Support for XML Version 1 was removed for Functions/BAPIs. This means that attribute xmlVersion is deprecated and templates for V1 no longer can be exported.

Connection Pool for outbound requests didn’t work when configured from the connector global configuration because it was missing the property jcoExpirationTime, needed along with jcoPeakLimit and jcoPoolCapacity to establish the connection pooling.

Destination Provider reference gets lost after hot redeploy of an application (that is, modifying the mule-config.xml)

Transaction ID (TID) has been added as a property of the Mule Message. Thus, when sending or receiving IDocs, the user will be able to call RFC-enabled Function Modules on SAP (INBOUND_IDOCS_FOR_TID and OUTBOUND_IDOCS_FOR_TID) to retrieve the IDoc number.

Java’s UTF-8 encoding had not been recognizing initial character BOM (Byte Order Marker).

Metadata retrieval in DataSense for BAPI names containing slashes ("/"), for example, "/DSD/ME_GETLIST_TR", is fixed.

Destination Provider reference gets lost after hot redeploy of an application (that is, modifying the mule-config.xml)

None

Compatibility issue with Anypoint Studio 5.2: when making a BAPI call or sending an IDoc, the SAP outbound endpoint could not parse an XML input built with a DataWeave Message Transformer.

XML version 2 parser displayed confusing ERROR messages expected when defining the record type.

The "MINIMAL" metadata mode now generates sample rows for tables.

Destination Provider reference gets lost after hot-redeploy of an application (that is, modifying the mule-config.xml)

Added demo examples to public site, available for download at SAP Connector Demos

Extended multi-tenancy support to all the connection parameters (jcoAsHost, jcoUser, jcoLang, jcoClient, jcoPasswd & jcoSysnr) so that the connections can be defined dynamically in runtime. This way, the connector can now be used in real multi-tenant scenarios within Data Gateway.

Set the correct mimeType for payload to each message created by the SAP Transport to be fully compatible with the new Data Framework.

Operation timeout cannot be configured for SAP Inbound Endpoint.

XML definition not removed from config file after deletion from Studio GUI.

NullPointerException when using Scalable Node Controller (SNC) and the password attribute is null. The SNC connection mode uses digital certificates to execute the authentication and hence no username and password are required.

Defective IDoc to XML conversion after upgrading to SAPJCo 3.0.13 and SAPidoc 3.0.12.

Destination Provider reference gets lost after hot-redeploy of an application (that is modifying the mule-config.xml)

Full-featured SAP Editor - SAP Editor includes more options to browse SAP objects (IDocs & Functions), display complete details of the selected SAP Object metadata (XML Template and/or XSD) and export the data to the desired directory. DataSense has also been improved in order to reload metadata whenever any of the following changes: SAP Object, Type (IDoc / Function), Output XMl, XML Version.

Support for IDoc Extensions - It’s now possible to generate the metadata structure for a custom IDoc.

Support for XML version 2 - It is set as the default XML version to configure a BAPI request.

Improved DataSense metadata discovery - for SAP Objects, Type (IDoc/Function), Output XML and XML Version. It also provides better coverage of failure messages.

Inbound endpoint support for qRFC doesn’t work with IDocs.

Nested BAPI structures cannot be parsed when trying to convert from XML to JCoFunction.

When parsing a JCo response with empty tables using XML version 2, an empty row is attached to them.

Failure to convert a BAPI result to XML.

Object finder doesn’t return inbound IDocs, only outbound.

XML parsers cannot process IDocs or BAPIs with slash (/) character in their name.

BAPI tables with name-less fields cannot be processed.

Inbound endpoint fails in some Mule Cluster configurations.

JCo library generates classloader leaks (only when JCo dependencies and the SAP connector lib are in the application lib directory and the latter is redeployed).

Operation timeout cannot be configured for SAP Inbound Endpoint.

Destination Provider reference gets lost after hot-redeploy of an application (such as modifying the mule-config.xml).