Axway B2Bi 2.4.0 Release Notes

Document version: November 15, 2018

Product version requirements

B2Bi 2.4.0 operates with the following product versions:

Axway product Version
B2Bi Client 2.4.0
Mapping Services 3.4.0

 

The following Standards Libraries are included in B2Bi 2.4.0:

Standards Library Version
Core EDI 1.7.0
Extended B2B 1.6.0
Financial 3.5.0

 

Implementations with other Axway products require the following versions for compatibility with B2Bi 2.4.0:

Axway product Version
PassPort 4.6.0
Sentinel 4.2.0
Transfer CFT 3.2.4

To obtain the latest service pack for the Axway product versions, refer to support.axway.com.

New features and enhancements

Audit of payload access

Regardless of the tool used to access a payload, there will be an entry in the audit log for Message Tracker or the Trace log for Message Log and Document Tracker. This entry contains information about Date/Time, Username and the type of access (View or Edit).

Session Management for the System Manager UI

System Manager UI sessions will now time out and terminate if they are not active. The time is the same as for the Web UI session timeout.

HTTP/S is now default for UI access

After installation, HTTP/S is now the default option for UI access and fully supported for TS Client. It is still possible to change back to plain HTTP for the UI. A self-signed certificate is included with the initial installation, but should be replaced with a CA-issued certificate.

Agreement updates for AS4 ENTSOG

B2Bi now supports ENTSOG AS4 Agreement updates. See https://www.entsog.eu/public/uploads/files/publications/INT%20Network%20Code/2016/INT1049-170109_ENTSOG%20AS4%20Agreements%20and%20Agreement%20Updates_Rev_1.pdf for further information about ENTSOG Agreement updates. This will require a patch available on December 10, 2018.

Separation of recent X12 standards for Axway B2Bi Client and Axway B2Bi Server

Due to changes in the X12 licensing model, we can only distribute the X12 libraries (006050 and newer) to customers who are members of X12. Axway supports the development of any-any data integration patterns, which includes X12 and offers solutions such as the Axway B2Bi product containing X12 intellectual property. Axway and X12 have reached an agreement that allows Axway customers to continue using the X12 materials within the EDI tools for a discounted subscription fee. Through this initiative, Axway customers with an active X12 subscription can use and reference their X12 libraries through the Axway software. Axway customers must obtain a subscription through X12's online store for an annual fee of $180 to continue to utilize the X12 data within the software. Please note that this user license is only needed for the usage of the X12 006050 (introduced in 2013) and newer versions. If Axway customers already have a license from X12, there is no need for a separate user license. Your membership status can be verified by contacting licensing@x12.org.

UI Node name can now be customized

Each node on an installation can now display a customized name. This can be achieved using the ui_customization.properties file.

Ability to configure multicluster instances

This release introduces the multicluster installation option in restricted availability.

New node type for B2Bi Interchange / ACF

A new node type, Synchronization Agent, has been added in Axway B2Bi Interchange to ensure synchronization between the various clusters in a multicluster configuration. Unlike all other node types, this node type is not visible in the UI.

B2Bi node included in multicluster configuration

Axway B2Bi administrators are now able to install or configure a Axway B2Bi node within the multicluster configuration.

TLS 1.2 for PeSIT and OFTPv2

The support for TLS 1.2 is extended to PeSIT and OFTP. All transports in B2Bi now support TLS1.2.

SHA256 support for OFTPv2

The SHA256 message digest algorithm is now available for OFTPv2.

SHA256 and AES 128/256 for ebXML

The SHA256 and AES 128/256 algorithms are now available for ebXML.

Support RSASSA-PSS signing and RSAES-OAEP for AS2

Additional signing and encryption algorithms for AS2 to support current regulations.

CoreEDI 1.7.0

Added support for:

  • X12 7050
  • Edifact D17B
  • Edifact D18A

ExtendedB2Bi 1.6.0

Added support for AAR 7050.

Financial 3.5.0

Added support for:

  • SEPA 2018 Instant Payment and SEPA 2018 SCT
  • SWIFT FIN 2018

Additional REST APIs

Additional REST APIs for Collaboration settings, Delivery Exchanges and testing of Exchange points are now available.

New port for Map as a Service API

Map as a Service API is moved to the Trading Engine API, and is exposed as a new resource. The old accessing location is no longer available. The port is now the same as for all other REST APIs.

Stop user tasks in Integration Engine

Optionally, it is now possible to stop a User Task in the Integration Engine without stopping the message processing for the rest of the system. This behavior is activated by setting the messaging.keepprocessing.taskuserdown system property to True.

SE Linux

It is now possible to install B2Bi on Security Enhanced Linux.

AWS support

Axway B2Bi is tested on Amazon Cloud, using Linux SUSE and Oracle Database.

Support the in-place upgrade option for B2Bi Client

The B2Bi Client can be installed using the upgrade option in the B2Bi installer. It is no longer required to uninstall the B2Bi Client for an upgrade. B2Bi Client configuration is kept after upgrade.

Fixed problems

Case ID Internal ID Description
01008385 BTOBIEXEC-18809

[Security Vulnerability] Broken Access Control - Folder Names by change id in URL

Before the fix:

Using the RenameFolder URL, an attacker with a WebTrader user can change the number of the ID variable and then view the name of the folder associated with the ID not belonging to them.

After the fix:

If the ID of the folder is changed in the URL and the WebTrader isn't the owner of the folder, B2Bi will not display the folder name associated with the ID, and the WebTrader will be asked to select one of his folders, if exists.

01002199 BTOBIEXEC-18746

org.xml.sax.SAXParseException when importing an Idoc from file

Before the fix:

Client had an unusual Idoc that had the first hierarchy level higher than 1 and importing it was impossible.

After the fix:

Made that kind of import possible.

01006689 BTOBIEXEC-18645

Table messages RoutingIDtype too short for AS4

Before the fix:

Processing of AS4 messages could fail if the routing IDs of the involved parties were greater than 50 characters. The Messages table had a restriction of 50 for a column that had to keep the routing ID of the sender and receiver. Inserts into the database for such messages failed.

After the fix:

Processing of AS4 messages should be successful for any valid routing ID. The limit of the routing ID was not changed - it can still have at most 70 characters. The corresponding column from Messages was increased to 70 to match it.

01007056 BTOBIEXEC-18643

Unable to enable, disable webtrader user when logged in as webtrader manager

Before the fix:

WebTrader managers could not enable or disable a WebTrader user. This was only possible for admin users.

After the fix:

WebTrader managers can now enable and disable WebTrader users.

00989198, 00978984, 00981988 BTOBIEXEC-18642

Issue to view the payload in E222 Form

Before the fix:

On CSOS environment, "View sent payload" in the "Message processing details" tab is not displayed correctly, and it shows an error. This behavior applies to received payloads.

After the fix:

Now in both tabs, "Document summary" and "Message processing details", the payload is correctly displayed, formatted as e222 form.

01007023 BTOBIEXEC-18641

message attributes with a space character can be created but cannot be removed

Before the fix:

If a message attribute contained a space, it could not be deleted.

After the fix:

Message attributes with space in them can be deleted, but can no longer be created.

00991016 BTOBIEXEC-18640

logger restore not working

B2Bi creates a lot of connections between cluster nodes and between its processes on the same node. On Windows, especially on versions older than Windows 10 and Windows 2016 server, this can cause exhaustion of the local dynamic port range, with errors such as "address already in use" or "no buffer space available" (if the first of these two errors occurs, make sure that it occurred while connecting rather than listening for connections, as it could also happen when a port from the pool of Integrator ports was stolen by another application).

To solve this problem, it is required to add more static IP addresses to the network adapter (obtain them first from the local network administrator, and then add them on the TCP/IP version 4 advanced properties in the Ethernet adapter properties in "Network and Sharing Center"). In addition, the same addresses should be added to the environment variable CORE_REBIND_OUTGOING, separated by commas, e.g.

CORE_REBIND_OUTGOING=10.133.1.1, 10.133.1.2, 10.133.1.3, 10.133.1.4, 10.133.1.5, 10.133.1.6, 10.133.1.7, 10.133.1.8, 10.133.1.9,

after which B2Bi should be restarted.

Do not add special addresses such as 127.0.0.1 in the list, either for the Ethernet properties or for the environment variable.

DNS may continue to point only to the original IP address.

It may also be necessary to increase the value of the environment variable BSOCKET_SOCKET_COUNT.

On Windows, when the PROCESS.WAIT Message Builder subroutine was used on an array of more than 63 processes and a non-zero timeout, the wrong process was returned. If there were more than 4032 processes, memory corruption occurred. Fixed. This bug has always existed, but B2Bi code never calls this subroutine in this manner, and user-written MBCs normally use a different subroutine for waiting for processes.

Made the number of online logger restore tasks, of GUI tasks and of porter pool ports configurable using the B2Bi Configure program.

01007858, 01006542 BTOBIEXEC-18627

issues when extending the port range allocation

The number of porter pool ports was limited to 1200, limiting the number of Processing Engines; now the limit is larger, toward 4000 ports.

00998319 BTOBIEXEC-18581

[AS4]Continuation of defect BTOBIEXEC-18189 related to Content-ID

Before the fix:

The Content id, CipherReference URI, Reference URI, and PartInfo in AS4 message have a special character not in hex-encoded; because of this, the message got rejected by the partner with a negative response.

After the fix:

Updated the code which generates the Content id, CipherReference URI, Reference URI, and PartInfo. The generated ID will not contain known special characters.

00958478 BTOBIEXEC-18578

Issues while adding new message attribute on Axway Interchange

Before the fix:

Internet Explorer 11 has the engine Mozilla but does not work like other browsers when using this engine. As a result, this modification blocks the flux of adding a message attribute into the page that refreshes the list of conditions for using the attribute.

After the fix:

Internet Explorer 11 was correctly identified into the JavaScript code, and the list of conditions is refreshed without any problem.

00951910 BTOBIEXEC-18295

Custom Transaction set control number generator not working

The percentage forms of X12 control number generators now support negative width (do not pad with zeroes) like the dollar forms.

00985441 BTOBIEXEC-18291

MAP_STAGE_OUTPUT_NAME to be set in the maincode (to handle multiple outputs)

Before the fix:

Processing fails if the MAP_STAGE_OUTPUT_NAME attribute is not set when having a datamapper map with multiple outputs in B2Bi.

After the fix:

By delivering a main code template (B2BiMultipleOutputs.mc) and using it in MappingServices, template which sets the MAP_STAGE_OUTPUT_NAME attribute, the processing of maps with multiple outputs ends with success.

00980273 BTOBIEXEC-18219

random result when mapping a Date And Time field (B2Bi 2.3.0 SP1 + P9)

Fixed an inconsistency in the fraction digit field of the date format structure.

Before the fix:

When mapping a Date And Time field that contained fractions, the outputs were random.

After the fix:

The outputs are consistent.

00996807 BTOBIEXEC-18218

"Z" (date pattern) added in output even if it is not present in input

Before the fix:

The "Z" was added even if it was not present in input:

2009-01-28T17:07:29 -> 2009-01-28T17:07:29Z

After the fix:

"Z" is not present in output:

2009-01-28T17:07:29 -> 2009-01-28T17:07:29

00999163 BTOBIEXEC-18128

To Routing ID is not set on the transfer as per upload directory name with the fix provided on Case 00970181 using "./" in destination path

Before the fix:

By default, in B2Bi, file paths containing "./" are not allowed. To allow paths which contain "./", the "ssh.disallowEmbedded" parameter should be set to false. When uploading using the command line on SFTP Embedded Server on Application Pickup, using "./", the selected message attributes that should apply via "Message attribute directory mapping" are not correctly applied.

After the fix:

The issue was corrected for SFTP Embedded Server on Application Pickup, and applies only if the "ssh.disallowEmbedded" tuning property is set to false.

00988918 BTOBIEXEC-18085

Database issue during B2bi 2.3.1 upgrade

Before the fix:

The upgrade from Interchange 5.10 to B2Bi 2.3.1 failed during system startup due to problems regarding database update for the InstalledUpgrades table.

After the fix:

The table is correctly updated, and the startup process continues to the next step.

00998319 BTOBIEXEC-18076

[AS4] GRTgaz partner Natgas send Negative acknowledgment for AS4 outbound message as content id has special character not in hex-encoded

Before the fix:

The content id, CipherReference URI, Reference URI and PartInfo in AS4 message have a special character not in hex-encoded; because of this, the message got rejected by the partner with a negative response.

After the fix:

Updated the code which generates the content id, CipherReference URI, Reference URI and PartInfo. Now, the content id will not contain known special characters. CipherReference URI, Reference URI, and PartInfo are now URL encoded.

00980273 BTOBIEXEC-18020

"Z" (Zulu time zone) is removed from the date

Before the fix:

When mapping date to date, the "Z" is removed

2009-01-28T17:07:29Z -> 2009-01-28T17:07:29

using the YYYY-MM-DDThh:mm:ss.3zzzzzz pattern.

After the fix:

"Z" is present in date

2009-01-28T17:07:29Z -> 2009-01-28T17:07:29Z and

added Z to the existing pattern:

YYYY-MM-DDThh:mm:ss.3Zzzzzzz

00995339, 00991141 BTOBIEXEC-18009

XML profile import changesEmbedded server DMZ port values

Before the fix:

XML profile import containing references to an embedded server changed the DMZ port values.

After the fix:

The DMZ port values remain constant during XML import for the existing embedded servers. However, the port is changed if a new server is imported, and the port is already in use.

00967727 BTOBIEXEC-17865

Urgent - B2Bi 2.3.1 TsClient Issue

Before the fix:

It was possible that multiple nodes of the cluster tried to update the REST configuration file from the shared folder at the same time, causing issues because of missing configuration tags.

After the fix:

The nodes of the cluster update the REST configuration file one at a time. There is now a locking mechanism that prevents multiple nodes from updating the file at the same time.

00970886 BTOBIEXEC-17757

"shared file system not responding" warnings in trace from time to time followed by crash

Improved RAW module and cfgserver error reporting on Windows.

00974299 BTOBIEXEC-17754

unexpected behavior of comparison operator / what's the result of length(null)?

Changed the behavior of the "length" function.

Before the fix:

length(NULL) returned NULL, causing problems when comparing the result with an integer.

After the fix:

length(NULL) returns 0.

00981750 BTOBIEXEC-17753

unexpected behavior of index function

Changed the behavior of the "index" function when searching for a non-empty substring in an empty string.

Before the fix:

index("", substring) returned NULL.

After the fix:

index("", substring) returns 0.

00967590 BTOBIEXEC-17752

FTP retrieves same file twice

When the Transfer Gateway was restarted without also restarting the associated retrieve Transfer Adapters, a retrieve method taking much time to run could be started again, in parallel with the existing instance. This happened with more probability when the Transfer Adapter had several Processing Engines. Fixed, now the same retrieve method will never run in parallel to itself.

00973862 BTOBIEXEC-17751

System down after there were no space left and the application crashed

After running out of disk space, encountering some other disk error, process kill or power failure, the logger task could, under certain circumstances, fail to write the highest log id correctly; after resolution of the underlying problem and restart of the logger task, errors about an inconsistent logger database would subsequently make the logger task unusable. The workaround was to use logger_raisehighestlogid.s4 to manually raise the highest logid to a sufficient level (higher than that attained during the incident and not written to disk) before starting to process messages. Fixed, now the highest log id will no longer be recorded incorrectly during such an incident. This bug has always existed.

When the logger ran out of disk space, the Transfer Gateway did not terminate, possibly losing messages. Fixed. This bug has always existed.

00986056 BTOBIEXEC-17750

Serious datamapper problems with patch CORE_211_04-01-01_SOL28

Patch CORE_211_04-01-01 introduced a bug in Datamapper maps, XML files with nil elements could cause the parent element to lose its end tag. Fixed. Maps do not need to be recompiled.

00988618 BTOBIEXEC-17749

XPM Adapter crashes with fatal warning

Some customers have custom alerter clients that delete alerts. The TG, TA or HME tasks could not start while they were running and alerts were being generated. Fixed. The Trace Viewer error mentioned ALERTER.ReadAlert and "unknown alert id".

00994410 BTOBIEXEC-17747

InitiatingPartner in RNIF responses wrong

Before the fix:

For RosettaNet 1.1 message exchange implementation, the initiating partner value from the response service header was different from the initiating partner value from the request service header, which was not compliant with the standard.

After the fix:

The initiating partner value remains constant over the life of the message exchange process.

00994907 BTOBIEXEC-17738

[Vuln-68 - Critical] Stored XSS on /ui/partycfg/FilterPickupsForGroup?groupId=

Before the fix:

A Stored Cross-Site Scripting (XSS) attack vulnerability was possible by adding a new "Pickup group" with JavaScript code as group name and navigating in the "Manage pickup group assignments" page.

After the fix:

The vulnerability is now eliminated by sanitizing the input before adding the data into the database and before the pickup group name is rendered by the UI server.

00998512, 00993120 BTOBIEXEC-17711

PeSIT transfers file name limited to 80 characters

When sending a file with a name longer than 80 characters from B2Bi to CFT, the filename is no longer truncated.

00993940 BTOBIEXEC-17688

Trust root certificate via API

Before the fix:

When a certificate was imported through REST API operations v1/communities/security/{id}/certificate/public/import or v1/tradingPartners/security/{id}/certificate/import, the certificate was not imported as trusted root, even if the correct parameters were given.

After the fix:

When a certificate is imported through REST API operations v1/communities/security/{id}/certificate/public/import or v1/tradingPartners/security/{id}/certificate/import, it is imported as trusted root, the behavior being the same as in the UI.

00974101 BTOBIEXEC-17675

PESIT TLS App Delivery certificate

Before the fix:

If the same certificate was shared by different servers (application deliveries, trading pickups...) for TLS communication, and the user deleted it from one server, the certificate was actually deleted from system KeyStore, making the remaining servers using that certificate unusable.

After the fix:

The system checks if the certificate is used by other servers or communities before removing it from the certificate KeyStore.

00983979 BTOBIEXEC-17659

XXE vulnerability in Axway B2Bi

Before the fix:

When having external entities, these were interpreted and their contents shown. If external entities were added in the headers of a message, the contents could be seen in message tracker.

After the fix:

When having external entities, these are not interpreted anymore. Also, a tuning property was added (xml.allowExternalEntities), which has the value secured (false) by default, and can be changed if the interpretation of external entities is needed. If it is left with the default value, and an external entity is added in the header of the message, an error is shown in message tracker.

00988981 BTOBIEXEC-17654

Ftp exchange point not visible on Two FTP embedded server

Before the fix:

NullPointerExceptions would occur whenever any type of ExchangePoint didn't have a BusinessProtocol associated with it.

After the fix:

The code will now check for a BusinessProtocol before attempting to retrieve information from the BusinessProtocol.

00992213 BTOBIEXEC-17650

[CRPEX] Vulnerability XercesImpl-2.9.1.jar (2.9.0 too)

Before the fix:

The vulnerable xercesImpl library could cause a denial of service attack.

After the fix:

The vulnerable library was replaced with another version that is safe, and the denial of service should no longer be possible.

00968818 BTOBIEXEC-17645

An issue connecting B2Bi 2.3.1 SQL db over TLS

Before the fix:

It was not possible to establish a secure connection from B2Bi to an MS SQL Server.

After the fix:

It is possible to establish a secure connection from B2Bi to an MS SQL Server.

In order to establish the secure connection, in conf/datastoreconfig.xml, under the mssql entry, where the connection url is, the ;encrypt=true;trustServerCertificate=true parameters must be used. So, it should look like:

<ConnectionURL>jdbc:sqlserver://{Host}:{Port}; databaseName={DatabaseName}; SelectMethod=Cursor; sendStringParametersAsUnicode=false; socketTimeout=600; encrypt=true; trustServerCertificate=true</ConnectionURL>

To test the database connection, the dbConfig tool has to be used, because, when running the installer, the information that the connection should be secure or not is not available yet.

00979082 BTOBIEXEC-17538

[CONFIRMED] Using RESEND option files going to default delivery queue instead of correct queue

Before the fix:

Using the RESEND option, the files are going to the default delivery queue instead of the correct queue (chosen by the matched criteria).

After the fix:

Using the RESEND option, the files are going to the correct queue (chosen by the matched criteria).

00991819 BTOBIEXEC-17531

Oracle 12.2 support documentation

Added extra verbiage in the Installation Guide for Oracle databases. Now it states "12c Release 1 and Release 2 (12.1, 12.2)".

00987984 BTOBIEXEC-17506

Unable to initiate handshake:javax.net.ssl.SSLHandshakeException

Before the fix:

When a remote host was connecting to the Interchange server on an OFTP TLS connection, and closed the connection before the handshake was complete (for example, when a load balancer was sending the heartbeat ping), the system logged an error (Unable to initiate handshake:javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake) and its corresponding stacktrace.

After the fix:

The system detects if the connection is valid (a secure session can be established) before the handshake phase begins and logs a warning ("Unable to create a valid SSL session") just to make sure that the system administrator doesn't miss potential real connection attempts that fail due to network problems.

00970181 BTOBIEXEC-17504

File dropping with "./" prefix is failing with Permission denied

Before the fix:

By default, in B2Bi, file paths containing "./" are not allowed. To allow paths which contain "./", the "ssh.disallowEmbedded" parameter should be set to false. By setting this tuning property, a SFTP Embedded Server will accept "./" when "Allow files to be uploaded to any subdirectory" is checked, but will throw a "Permission denied" error if "Do not allow files to be uploaded to subdirectories unless a message attribute is configured for the subdirectory level" is checked. The tuning property does not address full paths starting with "./"; this kind of paths are not allowed in B2Bi.

After the fix:

The behavior was extended to allow in-path "./" when "Do not allow files to be uploaded to subdirectories unless a message attribute is configured for the subdirectory level" is checked, using the same "ssh.disallowEmbedded" tuning property, which should be set to false.

00985515 BTOBIEXEC-17412

Issue to view the payload in E222 Form

Before the fix:

On CSOS environment, "View sent payload" at "Document summary" tab, the e222 form is displayed correctly, but in the "Message processing details" tab it is not displayed correctly, and it shows an error. This behavior applies to received payloads.

After the fix:

The behavior for displaying the received payload formatted as e222 form was corrected in CSOS environment. Now in both tabs, "Document summary" and "Message processing details", the payload is correctly displayed, formatted as e222 form.

00982002, 00983805 BTOBIEXEC-17368

Database Server Failover using Microsoft SQL Server Mirroring

Before the fix:

Unable to use database failover feature using MS SQL Server.

After the fix:

B2Bi is now using the driver provided by Microsoft, which includes the failover functionality.

00970181 BTOBIEXEC-17366

File dropping with "./" prefix is failing with Permission denied

Before the fix:

By default, in B2Bi, file paths containing "./" are not allowed. To allow paths which contain "./", the "ssh.disallowEmbedded" parameter should be set to false. By setting this tuning property, a SFTP Embedded Server will accept "./" when "Allow files to be uploaded to any subdirectory" is checked, but will throw a "Permission denied" error if "Do not allow files to be uploaded to subdirectories unless a message attribute is configured for the subdirectory level" is checked. The tuning property does not address full paths starting with "./"; this kind of paths are not allowed in B2Bi.

After the fix:

The behavior was extended to allow in-path "./" when "Do not allow files to be uploaded to subdirectories unless a message attribute is configured for the subdirectory level" is checked, using the same "ssh.disallowEmbedded" tuning property, which should be set to false.

00987826 BTOBIEXEC-17345

B2Bi 2.3.1 CSOS DEA REG search does not filter search

Before the fix:

The CSOS users that are not admins have access to the shared filters for DEA and CSOS numbers, but these filters are always empty.

After the fix:

The shared filters load correct data for non-admin users.

00981456 BTOBIEXEC-17343

Problem with Function replaceIfNullOrAbsent or convertToD

Fixed a memory corruption in the EXE_replaceIfNullOrAbsent_D_DD function.

Before the fix:

Running an expression like the following:

addTrace("INFO", "***SIM4**" & replaceIfNullOrAbsent( in:Leaf3, convertToD( "01/01/1980","DD/MM/CCYY" ) ))

would return a corrupted result.

After the fix:

Running the above expression returns the correct result.

00976534 BTOBIEXEC-17322

After upgrade to 2.3.1, XIB version still reads 4.4.0 instead of 4.5.0

If 2.3.2 is applied as upgrade over 2.3.1, the XIB version will be modified from 4.5.0 to 4.7.0.

The problem has been resolved by updating IntegratorVersion from integrator.properties, which is used by the message builder code to update the XIB version.

00963109 BTOBIEXEC-17321

Metadata Browser - SAP login does not accept more than 8 characters for the password

Increased the password field maximum length from 8 to 40 characters.

Before the fix:

Passwords larger than 8 characters didn't work.

After the fix:

Passwords larger than 8 characters are accepted.

00973063 BTOBIEXEC-17319

Files getting stuck in Queue Monitor

Before the fix:

A random socket issue could cause HME to hang waiting for JLogger.

After the fix:

The HME task does not hang anymore.

00979054 BTOBIEXEC-17318

[CONFIRMED] non-admin user DEA number search filter not working

Before the fix:

The CSOS users that are not admins have access to the shared filters for DEA and CSOS numbers, but these filters are always empty.

After the fix:

The shared filters load correct data for non-admin users.

00985211 BTOBIEXEC-17315

processing details tab: cannot see the data in e222 from

Before the fix:

On CSOS environment, "View sent payload" at "Document summary" tab, the e222 form is displayed correctly, but in the "Message processing details" tab it is not displayed correctly, and it shows an error. This behavior applies to received payloads, and it also applies to 855EDI.xsl formatting.

After the fix:

The behavior for displaying the received payload formatted as e222 form and 855EDI was corrected in CSOS environment. Now in both tabs, "Document summary" and "Message processing details", the payload is correctly displayed, formatted as e222 form or 855EDI. In order for the formatting to work properly, "Backup files that go through this transport" should be checked.

00981987 BTOBIEXEC-17304

[CONFIRMED][RN]Query about what should be the value of "Known Initiating Partner" in 3A4 response message under service header? Is it the DUNS of the TP initiating the 3A4 request or the 3A4 Confirmation?

Before the fix:

In case of a RosettaNet response, the KnownInitiatingPartner/GlobalBusinessIdentifier field from Service Header does not contain the routing ID of the partner that generated the request.

After the fix:

The KnownInitiatingPartner/GlobalBusinessIdentifier field from Service Header now contains the routing ID of the partner that generated the request.

00976409 BTOBIEXEC-17284

GWI: Filtering by Protocol on Tracker

Before the fix:

In B2Bi Message Tracker, there was no possibility to filter messages by a specific Production Url or to display it in the columns of the list of messages.

After the fix:

The Production Url column can be displayed in Message Tracker, and, using the Production Url text box, messages can be filtered by the delivery.

00984097 BTOBIEXEC-17231

[CONFIRMED] Event Sent to Sentinel Does Not Have the Message Type for only traded messages

Before the fix:

In Sentinel Monitoring interface, the MessageType field reported by B2Bi was populated by the Trading engine (Interchange) and the Processing Engine (Integrator) with different values, which could have been confusing for the final user.

After the fix:

A new interface field, named TradingEngineMessageType, was introduced, which will be populated by the Trading engine (Interchange), and the MessageType field will be populated by the Processing Engine (Integrator).

00982687 BTOBIEXEC-17230

Maps are not synced with after B2Bi upgrade from 2.2.1 to 2.3.1

Before the fix:

When running the mapProxyDeployer tool, the command FORCE_SYNC with parameters -update and -ignoreDate, the parameter -ignoreDate is not considered.

After the fix:

Changes were done in the mapProxyDeployer tool to take into consideration the parameter -ignoreDate, in the command: USER <YourUser> PASS <YourPassword> FORCE_SYNC -update -ignoreDate.

00982106 BTOBIEXEC-17229

Wrong format wsa:MessageID is sent from B2Bi to Webservice request

Before the fix:

The wsa:MessageID from the SOAP envelope was formatted like "urn:uuid:EDE9A716636134CBE6152718015030".

After the fix:

The wsa:MessageID from the SOAP envelope is formatted like "uuid:bc1c0eea-2581-45da-85c8-8599b632b8a0".

00984497 BTOBIEXEC-17214

Unable to delete unused messaging ID

Before the fix:

Unused messaging ID could not be deleted until another messaging ID was set as default.

After the fix:

The messaging ID can be deleted if it is not in use, and does not matter if it is default or not.

00975678 BTOBIEXEC-17188

After upgrading to B2BI, Manage partners option is slow when set users.defaultNumberOfSearchResultsPerPage to 100 in SystemProperties page

Before the fix:

Increasing value for the "ui.paging.maxItemsPerPage" property in the System Properties page could lead to a slow load for the "Manage Partners" page if the installation has a big number of partners. This problem is triggered by the fact that checking the todo list for every partner in the list takes a lot of time and resources.

After the fix:

A new variable named "ui.party.checkIsCompleteInList" was added in the System Properties page to help the user disable the todo check for the partners on paged lists and tables in the UI.

00979373 BTOBIEXEC-17183

Exchange point enabling and disabling takes long time

Before the fix:

A slow startup could be encountered for a B2Bi cluster that had in the configuration many partner deliveries (in the order of thousands), and all of them using just a few embedded servers. This was due to the high number of internal cluster messages needed to distribute the exchanges between running TE nodes. Each startup of a TE needed a re-balance to equally distribute the exchanges between nodes.

After the fix:

The B2Bi startup distribution logic was updated and optimized in order to limit the internal traffic and reuse cached data related to the exchange points that must be re-balanced.

00975148 BTOBIEXEC-17170

WebTrader UserID no longer part of Sentinel Reporting

Before the fix:

B2Bi_Message tracked object is not capturing UserID for WebTrader users making submissions and send to Sentinel. This attribute was present in GI 5.10.1 XFBtransfer tracked object.

After the fix:

B2Bi_Message tracked object now contains UserId for WebTrader users, and is included in Sentinel. The new tracked object must be deployed in Sentinel.

00979782 BTOBIEXEC-17169

WebTrader Sentinel Consumed event missing RoutingIDs

Before the fix:

On Interchange 5.10.1, the XFBtransfer tracked object used to capture SenderRoutingID and ReceiverRoutingID in all events for WebTrader users making submissions to Interchange. Those attributes are now missing for the "CONSUMED" event of the B2Bi_message tracked object for B2Bi 2.3.1.

After the fix:

Added SenderRoutingID and ReceiverRoutingID also for the "CONSUMED" event for WebTrader users making submissions to Interchange.

00954186 BTOBIEXEC-17078

MS SQL Server cannot be established from MCTester.exe using sqljdbc4-2-0 driver

Before the fix:

When running a map with MappingServices which connect to a MS SQL Server using sqljdbc4.2 driver, the JAVA_HOME environment variable set before starting MappingServices is used by the Microsoft driver.

After the fix:

JAVA_HOME is programatically set to Java delivered with MappingServices before sqljdbc driver to use it.

00980046 BTOBIEXEC-17068

[CONFIRMED]Update to PGP key does not trigger auto-clone

Before the fix:

The PGP certificates associated to peer community or peer partners that used the auto-clone feature were not replicated on add or remove actions.

After the fix:

The replication of the PGP certificates is working correctly for peer community or peer partners that use the auto-clone feature on both add and remove actions.

00969868 BTOBIEXEC-17067

Custom Message Attribute in Delivery Criteria do not wrap

Before the fix:

The delivery criteria is showed into single line, and if the criteria is formed from massive amount of attributes, the page lengthens on the right.

After the fix:

The delivery criteria is fitted on multiple rows, and the width of column does not exceed 400 pixels.

00981344 BTOBIEXEC-17062

parsing error on a date field when using DML version 2.1 (works fine when using 1.5 or 2.0)

Before the fix:

An error was generated when parsing a valid date field using the DML version 2.1 and worked fine for DML 2.0 and DML 1.5.

After the fix:

Parsing works for DML 2.1 also.

00981124 BTOBIEXEC-17056

Java Deserialization Vulnerability detected over port 8842

mdimporter task is no longer created at installation time.

00981371 BTOBIEXEC-17049

[DOC] B2Bi 2.3.1 SenderRoutingID/ReceiverRoutingID values in B2Bi_Message (in Sentinel) is different as compare to Interchange 5.10.1 SP13

Documentation was updated.

00980273 BTOBIEXEC-17029

"Z" (Zulu time zone) is removed from the date

Before the fix:

Mapping date to date, the "Z" is removed

2009-01-28T17:07:29Z -> 2009-01-28T17:07:29

using the YYYY-MM-DDThh:mm:ss.3zzzzzz pattern.

After the fix:

"Z" is present in date

2009-01-28T17:07:29Z -> 2009-01-28T17:07:29Z and

added Z to the existing pattern:

YYYY-MM-DDThh:mm:ss.3Zzzzzzz

00964877 BTOBIEXEC-17018

Non-admin gets UI error when openeing details page of failed PGP message

Before the fix:

When trying to see a failed message as an user with restricted search to a selected community permissions, in the UI, the message could not be seen in message tracker and an error occurred.

After the fix:

When trying to see a failed message as an user with restricted search to a selected community permissions, the message can be seen in message tracker.

00980123 BTOBIEXEC-16989

[CONFIRMED] SFTP Embedded Server Trading pickup with SFTP user's modification does not clone or other peer node

Before the fix:

When the password or public key of a SFTP or FTP (only the password) user (on an application pickup or trading pickup) were changed, the updates weren't sent to the peer nodes.

After the fix:

When the password or public key of a SFTP or FTP (only the password) user (on an application pickup or trading pickup) are changed, the updates are sent to the peer nodes.

00970886 BTOBIEXEC-16988

"shared file system not responding" warnings in trace from time to time followed by crash

The B2BI_TASK_PING_TIMEOUT environment variable can now be used to increase the timeout when pinging filer, logger, table, timer or kernel server tasks. The default remains 10 seconds.

00976231 BTOBIEXEC-16984

[CONFIRMED] B2Bi_message Filesize attribute value issue

Fixed the issue with the message size not correctly reported in Sentinel after being modified by the inline processor.

00977178 BTOBIEXEC-16930

API csos/approvePendingOrder: Unable to select certificate

Before the fix:

When approving an order through REST API, it was not possible to choose a certificate to sign with; the first certificate with a matching DEA number was taken.

After the fix:

When approving an order through REST API, the ID of the certificate which will be used to sign the order is given as a parameter of the operation.

00979767 BTOBIEXEC-16927

Security Assessment - Minor -Finding #4 Query parameter in SSL request

Before the fix:

It was observed that the application reveals the sensitive information such as "username" as a query parameter in SSL and Non-SSL request. Information exposure through query strings in URL is when sensitive data is passed to parameters in the URL. Some affected URLs:

https://yourhost.com/ui/core/users/UserModify?userId=032456

https://yourhost.com/ui/partycfg/b2bi/ApplicationConnectionModify?id=1411501

After the fix:

The request to URLs: "/UserModify" and "/ApplicationConnectionModify" where changed to POST, the sensitive information is no longer revel.

00978664 BTOBIEXEC-16900

Manage Users Page - Issue with search For User Names or UserIDs using Uppercase Aplhabets

Before the fix:

There were inconsistencies in searches when lowercase or uppercase characters in usernames were used.

After the fix:

This was resolved.

00969568 BTOBIEXEC-16894

After upgrade from B2Bi 2.3.0 SP1 to B2B 2.3.1 SP1, Rosettanet message (2way pip: 3A4) is failing

Before the fix:

When a RosettaNet 2 message is received with a "thisDocumentGenerationDateTime" element that contains a customized date format, the message is rejected with the error:

Error packaging message

com.cyclonecommerce.rosettanet.protocol.RosettaNetException: RosettaNet 2 way Pip request message with coreId: .... doesn't contain a proper value for the "thisDocumentGenerationDateTime" field.

After the fix:

Any message that has the "thisDocumentGenerationDateTime" element defined and whose value is not blank will be accepted.

00976285 BTOBIEXEC-16891

IDOC structure imported does not match the standard (ORDERS05)

Idoc Segment cardinality was not imported correctly from SAP server. Fixed.

00964076 BTOBIEXEC-16872

Datamapper Simulator XML-ADF closes TAG twice

In a Datamapper map whose output was an XSD ADF, the root container (the one with xmlAttr) was sometimes output with both /> and </ end specifications. Fixed.

00977164 BTOBIEXEC-16840

NullPointerException in ExchangePointDistributorProcessor

Before the fix:

A NullPointerException could be thrown and could cause a TE node, in cluster mode, to not listen to embedded servers. A complete restart of all nodes was the only way to recover.

After the fix:

An extra check was added to avoid the NullPointerException, which was causing the issue.

00970886 BTOBIEXEC-16837

"shared file system not responding" warnings in trace from time to time followed by crash

Added extra error information on Windows for FILE DELETE and UNIQUE extension.

00971428 BTOBIEXEC-16834

File dropping with "./" prefix is failing with Permission denied to SFTP embedded server

Before the fix:

In B2Bi, file paths containing "./" are not allowed. When a file path containing "./" is used, a "Permission denied" error will be thrown.

After the fix:

By default, in B2Bi, file paths containing "./" are not allowed. For supporting "./" in file paths, we added a new tuning property, "ssh.disallowEmbedded". To allow paths which contain "./", the "ssh.disallowEmbedded" parameter should be set to false; in other words, the "ssh.disallowEmbedded = false" line should be added in "<InstalationDir>/Interchange/conf/tuning.properties". The tuning property does not address full paths starting with "./"; this kind of paths are not allowed in B2Bi.

00963881 BTOBIEXEC-16818

Status Still "In Process" although EDI file created

Before the fix:

Having a large number of documents enveloped together led to a NullPointerException, and the message returned from processing was displayed as "In Process" in Message Tracker.

After the fix:

There are no errors during processing when a large number of documents are enveloped together, and the message is delivered successfully. There still is a warning regarding the truncation of a metadata attribute, as it is done for all metadata attributes exceeding 4000 characters, but this does not affect trading in any way.

00968540 BTOBIEXEC-16817

[AS4][GRTGAZ][PROD]- Files failing with error "packageMessage caught Exception: Error during encryption" with XML file as payload having specific collaboration setting

Before the fix:

Using AES-GCM as encryption algorithm for AS4 would generate an error, and the file could not be sent to the partner.

After the fix:

AES-GCM can be used as encryption algorithm for AS4.

00964851 BTOBIEXEC-16812

wrong keytype field in authorized_keys prevents subsequent keys from authenticating.

Before the fix:

The authorized_keys file format specifies that, for an SSH Protocol version 2 key, the entry requires a minimum of 2 fields, the key type (algorithm) and the base64-encoded key. For example, if there is a dss key, and the key type shows as 'ssh-rsa', the authentication will fail. All keys listed after the bad key in the file are not considered.

After the fix:

If in the authorized_keys file there is a key which has a wrong algorithm, for example, the key is dss and the type is ssh-rsa, then B2Bi will check if there are other keys in the authorized_keys file. If there are other keys, it will try to authenticate with them, otherwise, an error will be thrown.

00971355 BTOBIEXEC-16802

SFTP dual authentication does not work with B2Bi2.3.1 when Axway Secure Transport works as SFTP server

Before the fix:

By default, in B2Bi, for SFTP dual authentication keyboard-interactive is preferred over password. This led to problems in dual authentication (not working) when the server supports keyboard-interactive authentication.

After the fix:

Changed the preferred keyboard-interactive over password to false; now by default password will be preferred. SFTP dual authentication works as expected.

00976274 BTOBIEXEC-16765

random result when mapping a Date And Time field

Fixed an inconsistency in the fraction digit field of the date format structure.

Before the fix:

When mapping a Date And Time field, the outputs were random.

After the fix:

The outputs are consistent.

00975453 BTOBIEXEC-16752

[CONFIRMED] CSRF possible on certain urls

Before the fix:

After logged into the application, all of the links can be accessed from outside of the browser and can run without a problem.

After the fix:

On accessing the links outside of the browser, the associated code cannot be run, and it returns a pop-up error.

00975299 BTOBIEXEC-16694

Cannot search for manually corrected entries in B2Bi Message Log

Before the fix:

The "Manually Corrected Messages" entry is missing from "Message Log", "Search>New" dialog box.

After the fix:

The "Manually Corrected Messages" entry is present on "Message Log", "Search>New" dialog box.

00974954 BTOBIEXEC-16687

error handling improvement : DATAIO.COPY: filer file xxxx/f184_131858761 does not exist

MBC_HIERCHMSGENV.GetData exceptions were incorrectly suppressed. Fixed.

Made DATAIO.Copy errors coming from the HME more detailed.

00963956 BTOBIEXEC-16659

Archiver fails when using UNC path

If hard links are not supported by the shared drive, automatic restore of archives fails with errors such as "DIR_CREATE: failed to create directory "\": Permission denied". Fixed. Also improved the error message.

00968096 BTOBIEXEC-16606

Fails to compile Datamapper map with error ERROR: different version strings in PRAGMA VERSION directives for module "ccp"

Updated B2bi core to latest ccp.

00973579 BTOBIEXEC-16604

root certificates in community imported as p7b have no link

Before the fix:

The friendly name of the root certificate cannot be imported (remained null).

After the fix:

The friendly name will be completed with the value from Subject Common name of Root Certificate.

00973660 BTOBIEXEC-16603

User profile case sensitivity issue

Before the fix:

The "Related Task" on User Profile section is missing if the logged user is written ADMIN, while real name user is admin (logging into UI is case-insensitive).

After the fix:

The Related Task is accessible regardless of the logged user.

00972971 BTOBIEXEC-16577

Document Class: Binary instead of XML when encoding is specified UTF-16

Before the fix:

The files with a DOCTYPE element were not recognized as XML (Document class).

After the fix:

The files with a DOCTYPE element can be recognized as XML by setting a tuning parameter that allows this type of files.

00955980 BTOBIEXEC-16538

"saving changes" on an exchange point where no changes were made triggers autocloning of partners

Before the fix:

The "Save" button on the UI page "Modify Trading Pickup" will clone all partners on peer networking; in any case, the configuration is changed or not.

After the fix:

The "Save" button on the UI page "Modify Trading Pickup" won't clone partners on peer networking, without changes made in configuration of pickup.

00964379 BTOBIEXEC-16537

sftp Application pickup, moving to page 2 on directory tab gets an error

Fixed the defect for SFTP, FTP and HTTP application pickups.

00962970 BTOBIEXEC-16516

B2B with Passport : how to change the default domain in UI

Before the fix:

In B2Bi, the default domain for PassPort is Synchrony, and cannot be changed to other default domain, so a user always has to choose from the domain list.

After the fix:

Added a tuning property, "passport.defaultDomain". By using it, the user can choose a default domain other than Synchrony. For example, if in tuning.properties the "passport.defaultDomain = B2Bi" line is set, then the first domain in the list will be B2Bi. The value of "passport.defaultDomain" needs to be set to one valid domain name from PassPort.

00972113 BTOBIEXEC-16494

Unable to view e222 payload for CSOS messages consumed by API

Before the fix:

If an order was uploaded via REST API v1/csos/upload when trying to see it with stylesheet formatting from "Message processing details", "Origination" section, an error was shown.

After the fix:

If an order is uploaded via REST API v1/csos/upload, when trying to see it with stylesheet formatting form "Message processing details", "Origination" section, the order is displayed with stylesheet formatting.

00971121 BTOBIEXEC-16480

No Payload View for messages received via AS2 and delivered via PeSIT

Before the fix:

The "View Payload" link did not appear for messages received via AS2 trading pickup in limited mode and delivered to a PeSIT delivery.

After the fix:

The "View Payload" link appears for the case described above.

00968134 BTOBIEXEC-16440

Error importing SFTP public key as "Error creating authorized_keys list. com.axway.dmznode.ssh.SshKeyException: Invalid record found in the user input file. keyType field must be ssh-rsa or ssh-dss"

Before the fix:

When importing a SFTP public key in SSH2 format to a SFTP account in B2Bi, it converts the key to valid OpenSSH format but it introduces a leading line break into the authorized_keys file due to which the keys cannot be viewed through UI. An error is thrown: "Error creating authorized_keys list. com.axway.dmznode.ssh.SshKeyException: Invalid record found in the user input file. keyType field must be ssh-rsa or ssh-dss".

After the fix:

Added logic in the method which creates the UI list to skip leading line breaks which can sometimes occur in the authorized_keys file, and now the keys are correctly displayed in UI.

00968058 BTOBIEXEC-16361

Not able load SFTP user key, getting error "Invalid record found in the user input file. split record length must be 2 or 3 but was 5"

Before the fix:

When adding a public key file for a transport user, SFTP user, if the file contains keys which have comments, then the following error will appear: "Error creating authorized_keys list. com.axway.dmznode.ssh.SshKeyException: Invalid record found in the user input file. split record length must be 2 or 3 but was 5".

After the fix:

When adding a public key file for a transport user, SFTP user, the keys are correctly displayed, even when the public key file contains keys with comments.

00971693 BTOBIEXEC-16305

memory corruption in map execution

The output date size was too large, resulting in printing too many characters from memory in case of long date patterns.

00971477 BTOBIEXEC-16282

AddTrace output in DataProcessing.log is not line breaked

Before the fix:

When using the addTrace function in a DML map for adding an INFO log which contains "\n", only the first line will appear as INFO in the trace log. All the other lines will appear as UNKNOWN logs. Also, when the last character is "\n", there will be an extra empty UNKNOWN trace.

After the fix:

Each new line in the DML mapping log will appear as a trace with same gravity as in the DML mapping. No empty log appears after "\n".

The DML mapping log will be split into lines using strtok. Each line will be traced as a separate log by the HME.

00971419 BTOBIEXEC-16275

Rest API for adding sftp user under 'Account owned by partner' tab of trading pickup.

Before the fix:

It was not possible to add FTP and SSH users owned by partners on trading pickups.

After the fix:

It is possible to add FTP and SSH users owned by partners on trading pickups. The owning partner is specified by an optional query parameter, partyId. If the parameter is not provided, the user is owned by the community that owns the exchange point.

00968832 BTOBIEXEC-16186

Pluggable transport encypted passwords causes upgrade to fail (again)

Before the fix:

Upgrading from 2.3.1 with pluggable transports that had passwords to be encrypted, if null values were added in Oracle database, those values will be "- ", and B2Bi would try to decrypt them and generate a fatal error that would fail the upgrade.

After the fix:

B2Bi checks for null values specific to Oracle DB and doesn't try to modify them.

00968372 BTOBIEXEC-16173

AS4 error; The signature or decryption was invalid

Before the fix:

A decryption error was displayed for certain payloads with values in the Content-Disposition header received over AS4.

After the fix:

The encryption/decryption mechanism for AS4 works as expected.

00889460 BTOBIEXEC-16109

Classification activity can't be enabled: duplicate value

If two configuration objects are created with the same name and parent by two different users, the GUI error message received by one user did not include the name of the other user, making it difficult to debug with a large userbase. Fixed.

00946438 BTOBIEXEC-16108

warning in trace viewer "the log entry is too big"

Parse steps with INHOUSE Business Documents as input could log a log entry that was too big for the logger to handle. Fixed. This bug has always existed.

00959464 BTOBIEXEC-16107

HME crashes with messages getting stuck in the queue

Fixed a filer leak in the EXE_getInputMessage_V_ function.

00968629 BTOBIEXEC-16101

get /application/exchange/{id}/sftpSubDirectory not returning all directories

Before the fix:

When trying to get all the subdirectories of all the users for an application pickup through REST API, for SFTP or FTP (with embedded server), the operations returned only one subdirectory, the first user's first subdirectory.

After the fix:

When trying to get all the subdirectories of all the users for an application pickup through REST API, for SFTP or FTP (with embedded server), two new operations were added that return all the existing subdirectories.

00951724 BTOBIEXEC-16079

errors when registring MBCs

If the "B2Bi Config Server for Integration Services" task was not yet started when the "B2Bi Auto Registration Server" task was started, the latter task entered an invalid state, and could no longer register MBCs for Integration Services, until this latter task was manually restarted. The error message was "missing mandatory field 'ParentFolderId'". Fixed.

In cluster mode, the MBC registration could fail to register MBCs in Integration Services. The error was "duplicate value". Fixed.

00947070 BTOBIEXEC-16059

Automation on Queue Monitor with statistics_queue.x4

Since patch CORE_211_03-14-28 or CORE_211_03-41-11 (or CORE_211_03-50-01), the number of queues was reduced to save disk space. This caused an "array out of bounds" error in the statistics_queue.x4 command line tool when run on a TA task. Fixed.

Also fixed another "array out of bounds" error, which occurred when a queue task was not started.

00953894 BTOBIEXEC-16058

HTTP task timeout

If an HTTP Transfer Adapter task was used for both server and client connections, and the total number of connections (server+client) exceeded the configured maximum, and these connections were of both server and client type, the task no longer read from the send message queue, and it was necessary to restart the TA. Fixed.

00931654 BTOBIEXEC-16055

Archiving is very slow

Some configuration operations were always slow. Also, logger archiving was very slow every time the logger was misused in some way, such as processing many EDIFACT or X12 messages with identical "unique" identifiers such as UNH_0062, setting thousands of parents references for the same logger entry, etc.

Fixed. To activate the fix for existing runtime logger tasks, they must reindex after applying the first patch or service pack containing the fix; this can be done by stopping the logger tasks - which will stop all processing tasks - then deleting their "dirty" file from their directories, and then restarting the logger tasks; the reindexing can be monitored from Trace Viewer.

00906113 BTOBIEXEC-16050

Message Log search error

The updates for the search expressions introduced in tool_msglog version 1.5.53 (any CORE_211_03-36-xx, CORE_211_03-39-xx, CORE_211_03-41-xx, or CORE_211_03-50-xx patch) did not work correctly when an AND logical operator was present (e.g., when both Integration and Activity were checked in the Integrations and Activities log entry search). The symptom was a "parse error" when running the search, and the workaround was to re-edit the search every time the Message Log was opened. Fixed.

Also, the update was not done for the third and subsequent search tabs, if present.

00936023 BTOBIEXEC-16049

Size of ACxml.cfg (MetaData Browser) / Work concepts

Even when the environment variable CORE_GUI_SLOWCON was set to "dontwaitreply", the Metadata Browser was very slow on long distance connections (transatlantic, transpacific tsclient.exe connections) if the left side tree contained a thousand or more items. Fixed.

00841592 BTOBIEXEC-16046

[Integrator child] round function is removing - sign for values between -1 and 0

Added the negative sign for values between -1 and 0 in the truncateOrRound function.

00940707, 00940115 BTOBIEXEC-16044

Integrator 3.7.3 and EDIFACT v4

Changed the repetition separator of EDIFACT v4 Business Documents according to the one given in the map. It will only be displayed in the UNA segment of the output EDIFACT document.

Also changed the other UNA separators if the ones in the map are different from the default ones.

00967881 BTOBIEXEC-16040

[CONFIRMED] B2Bi allows invalid ssh public keys to be added

Before the fix:

The SSH public keys did not check at import to validate them as valid keys.

After the fix:

Invalid SSH public keys will not be accepted at import.

00968213 BTOBIEXEC-16035

update tool_perfmon to fix issue with statistics_queue.x4

Fixed "array index out of bounds" errors for tasks without queues. Error message added.

00967120 BTOBIEXEC-16023

[DOC] Modify tool Filerutil.x4 to filerutil_fromet.x4 in documentation

Changed the name of the util file to the correct name.

00956236 BTOBIEXEC-16022

complete cycle graph not generated when rerouting from one cft to another.

Before the fix:

In B2Bi, when receiving messages from a partner over PeSIT (Transfer CFT), and then rerouting to another partner over PeSIT (Transfer CFT), in Sentinel the "End To End" cycle graph is incomplete.

After the fix:

A condition was added in B2Bi that applies to messages from a partner over PeSIT, which are then rerouted to another partner over PeSIT. When the condition applies, B2Bi will send necessary information to Sentinel for generating complete "End To End" cycle graph.

00960520 BTOBIEXEC-16020

[AS4] GRTgaz partner Natgas send Negative acknowledgment for AS4 outbound message as content id has special character not in hex-encoded

Before the fix:

The content ID in AS4 messages has a special character not in hex-encoded; because of this, the message got rejected by the partner with a negative response.

After the fix:

Updated the code which generates the content id, now it will not contain known special characters.

00957875 BTOBIEXEC-16019

OFTP - Sharing partners missing after Importing partner profiles

Before the fix:

Missing sharing partners from OFTP Partner Delivery when importing system profile; only the first sharing partner is kept.

After the fix:

When importing system profile, all sharing partners from OFTP Partner Delivery are imported.

00939886 BTOBIEXEC-16017

EDI file crashes B2Bi - Java heap space error 1/2

Before the fix:

Reporting processing events in Message Tracker for an X12 Interchange with several thousand messages failed with network and timeout errors.

After the fix:

The processing events are reported successfully. Now there is also a configurable limit for the number of processing events reported in Message Tracker for each message. The limit is per event severity, and has a default value of 20. It can be configured with the b2bi.integrator.processingEvents.limit system property, and takes effect in Integrator/B2Bi Core after restarting the server.

00934548, 00962922, 00934208 BTOBIEXEC-16016

reflected XSS scripting vulnerability

Fixed XSS vulnerability.

00876833 BTOBIEXEC-16015

EBXML - Message Attributes defined in the Application Delivery are missing from the filepath (in the mmd file)

Before the fix:

When an ebXML transfer is done from a partner to a community, to an application delivery file system with message metadata, message attributes set in the related application delivery are missing in the MMD file, in the location of the payload. The payload is delivered correctly, but the link to the payload in the MMD file is not correct.

After the fix:

When an ebXML transfer is done from a partner to a community, to an application delivery file system with message metadata, message attributes set in the related application delivery are included in the MMD file, in the location of the payload and the link to the payload is correct.

00961515 BTOBIEXEC-16013

Exchange URL is not sent correctly by B2bi if SFTP embedded server user defined in Partner delivery exchange

Before the fix:

ExchangeURL would not be correctly populated for certain messages.

After the fix:

ExchangeURL will now be correctly populated.

00958306 BTOBIEXEC-15995

Inclusion file filtering fails with Directory Attribute Mapping via SFTP

Before the fix:

When having Directory Mapping and an inclusion file filtering enabled, it did not consume the file from the directory that matched the given pattern.

After the fix:

When having Directory Mapping and an inclusion file filtering enabled, it consumes the file from a directory that matches the given pattern.

00994502 BTOBIEXEC-15974

[OFTPv2] overriding the Routing Id in the Metadata profile has no effect

Before the fix:

The values for the sender RoutingID (From ID) and the receiver RoutingID (To ID) of the messages transmitted using OFTP and processed by the Integrator (Processing Engine) are replaced during transmission with the corresponding RoutingIDs that exist on the binary collaboration for the partners/communities involved.

After the fix:

The values of the sender RoutingID (From ID) and the receiver RoutingID (To ID) for the messages transmitted using the OFTP and processed by the Integrator keep their value during transmission.

00931358 BTOBIEXEC-15933

Error while Web service packaging as "Error packaging Message org.apache.axiom.om.OMException: Error while writing to the OutputStream"

Before the fix:

When B2Bi processes a message received/sent through Web services, it would randomly encounter an OMException because of a Stream still in use, which is closed by the garbage collector.

After the fix:

The GC will not close a Stream in use.

00926970 BTOBIEXEC-15866

submitMessage API call intermittently returns SoapFault: ConcurrentModificationException

Before the fix:

Submitting messages using the API (Global embedded web services API server) occasionally, the sender could receive a SoapFault response indicating that a java.util.ConcurrentModificationException occurred.

After the fix:

No more ConcurrentModificationException is thrown.

00961912 BTOBIEXEC-15863

sftp directories are case sensitive after upgrade to 2.3.1

Before the fix:

SFTP user names and directories passed by an external SFTP client would no longer be handled with case sensitivity disabled by the B2Bi embedded SFTP server. This could lead to errors during login, directory traversal, file uploads or downloads.

After the fix:

The Maverick implementation used by the B2Bi embedded servers was customized to re-disable the case-sensitive behavior. This applies to both user names and directories. For example, external SFTP clients can now log in using either <MyUser> or <myuser> as the user name, or navigate to a specific subdirectory using either <MyInbox> or <myinbox>.

00954985, 00953069, 00952803 BTOBIEXEC-15837

B2Bi to CFT PeSIT SSL performance issue

Before the fix:

When transferring from B2Bi to PeSIT (Transfer CFT) with TLS, as inbound, PeSITt being an application delivery, the connections/ sessions are not being reused, which caused a performance issue, a low transfer rate. When transferring from B2Bi to PeSIT, as outbound, PeSIT being a partner delivery, the connections/ sessions are reused.

After the fix:

Added support for reusing the connections/sessions when transferring from B2Bi to PeSIT on inbound flow; this was made by extending the existing implementation.

00954017 BTOBIEXEC-15740

SAP-ALE Login fails after Import entire System Profile

Exported and imported System Profile can be used for SAP-ALE.

00955843 BTOBIEXEC-15590

queue monitor's clean queue option while tasks are not stopped

Before the fix:

All the queue entries that are not in processing can be deleted (clean action from queue monitor) when the corresponding task is started.

After the fix:

Clean action from queue monitor will work if the corresponding task is not started.

00838894 BTOBIEXEC-15479

Blocked FailoverCoordinator threads leads to build-up of "Scheduled Production" messages

Before the fix:

The number of messages waiting in Production Queue can't be controlled and limited.

After the fix:

Using the following tuning parameters, the number of messages that wait in Production Queue can be limited (activating System Throttle):

"maxMessagesInProductionQueue" - maximum number of queued messages up to the trading pickups are active (when this value is exceeded, system throttle is activated)

"minMessagesInProductionQueue" - minimum number of queued messages up to the trading pickups are inactive (when this value is lower than the one set in the property, system throttle is deactivated)

00948368 BTOBIEXEC-15139

File Name of Downloaded payload in Document summary tab from Message Tracker is different in Interchange 5.10.1 and B2bi 2.3.1

Before the fix:

On B2Bi 2.3.1, in the web interface on the "Message details" page, when "View received payload" was clicked and then "Download" was clicked, then the downloaded file had the coreID formatted file name.

After the fix:

The downloaded file keeps its original name.

00949176 BTOBIEXEC-15095

Query about Custom Tablespaces for DB2

Before the fix:

There was no procedure for enabling tablespaces in DB2 and no code in B2Bi that could install the B2Bi database in those tablespaces.

After the fix:

The procedure is now documented for custom tablespaces for DB2, and B2Bi manages installing in those tablespaces.

00947350 BTOBIEXEC-14930

E-Mail Subject encoding/decoding

Before the fix:

When receiving emails with "Subject" encoded using base64 and the original string contains underscore chars, at decoding they are replaced with space chars. This happens when using the Migration EMAIL Connector.

After the fix:

When decoding email's headers encoded using base64, the underscore ("_") is not replaced with space (" ").

00946270 BTOBIEXEC-14919

Invalid encoding: redundant leading 0s after upgrade to b2bi 2.3.1 from GI 5.10.1.0.15

Updated bundled jre version to 1.8.0_162.

00929399 BTOBIEXEC-13740

Secure Renegotiation (Client-initiated)

Before the fix:

The TLS embedded servers are vulnerable to CVE-2011-1473 or TLS Renegotiation and Denial of Service Attacks.

After the fix:

The jvmArguments.xml file contains a new property, "jdk.tls.rejectClientInitiatedRenegotiation", set to "true", which disables the client-initiated renegotiation. Any attempt to initiate the renegotiation from the client side will result in the connection being closed by the server.

00851137 BTOBIEXEC-13730

procmbc_example module readme file missing

Added readme file for procmbc_examples module.

00996361 BTOBIEXEC-19325

[DOC] Documentation missing a privilege

Documentation was updated.

Standards Library

Case ID Internal ID Description
00971129 STAN-2722

Missing optional fields in the TRADACOM DELIVR Business Document

Several optional missing fields were added, according to the latest version for TRADACOMS standard.

00952763 STAN-2723

Wrong date pattern of the CrtDtTm field (SEPA_pain_001_001_03.bdoc)

Before the fix:

When using certain date time patterns in the PSR_Generation project, the system will display errors during processing.

After the fix:

Date time pattern changed to accept multiple date time formats.

Mapping Services

Case ID Internal ID Description
00973397 MS-1207

IDOC ORDERS05 structure imported does not match the standard : E2CUCFG003 should be optional

IDOC Segment (e.g. E2EDKA1003) cardinality was not imported correctly from SAP server.

After the fix:

Cardinality is correct: 0-99.

00983225 MS-1194

"Invalid input" when sharing project to GIT

Before the fix:

The resources shared to GIT couldn't be opened.

After the fix:

All resources are opened without pointing errors.

Known issues and limitations

Case  ID Internal ID Description
  BTOBIEXEC-19896

Java-related performance issue

Following a new security change made in Java to prevent password-guessing attacks, a performance degradation issue has been reported on B2Bi 2.4.0, which affects AS2 transfers.

01010501 BTOBIEXEC-19165

Error parsing as DN string: Hex literals of form #hh... not supported with As4

Messages received through AS4 which have Hex Encoding for a custom OID set on the certificate fail in B2Bi.

01001389, 01003215 BTOBIEXEC-19160

Re-add CTR ciphers to FIPS

When upgrading from B2BI 2.3.0, the CTR ciphers are no longer available for SFTP transfers.

BTOBIEXEC-15830

Integrator tasks terminate unexpectedly when trading a file that generates many processing warnings

When trading a file that generates thousands of processing warnings, some Integrator tasks may terminate unexpectedly because of an out-of-memory error and do not recover. The message remains active in Message Log.

BTOBIEXEC-19191

Transfers over No Packaging HTTP/S fail to be received when the filename contains spaces or special characters

Files which contain spaces or special characters in the name will fail when being transmitted over No Packaging HTTP/S.

00978863 BTOBIEXEC-16890

Changing the number of CPU does not modify the number of PEs for the HMEs

After changing the number of CPUs in an upgrade or through the Configure wizard, the number of PEs for each HME must be configured manually from System Profile Manager.

Downgrading the number of CPUs is currently not supported. Any attempt to change the number of CPUs to a lower value than the initial one will cause failures during the startup process of the Deployment Server.

BTOBIEXEC-19215

PORTER.ALLOCATEPORT: failed to write to persistent memory file when simulating map on localhost

Sometimes, when simulating a Datamapper map on localhost using the Datamapper Simulator Server, the following error occurs:

r4edi(porter):porter.s4:2632:FILE MOVE: failed to rename "client_install_location\data\porter\porter.mem.wrk" to "client_install_location\data\porter\porter.mem" r4edi(DMSimulation):dmb_simrunner.s4:244:PORTER.ALLOCATEPORT: failed to write to persistent memory file r4edi(DMSimulation):dmb_simrunner.s4:247:failed to allocate new port from porter

Workaround: To solve this issue, manually remove porter.mem and porter.mem.wrk files.

BTOBIEXEC-19189

Not able to run any message from Edifact D18AV4 in Datamapper

When trying to run in Datamapper any message (e.g. GOVCBR) from Edifact D18A4, an error is received during deployment. According to the error given in the console, the system is not able to load "install_localtion\Integrator\datamapper\edi\D18A_V4\version.dat".

BTOBIEXEC-16835

Datamapper simulation HEADERS file

When trying to run in Datamapper a X12 7050 message (e.g. 475) which contains segment R9, element 0001, the message gets rejected because an enumeration value is expected (present in HEADERS files (UNOA/UNOB)).

BTOBIEXEC-19304

UI connection is lost after importing as partner a community from AIX

When a partner profile exported from a B2Bi installation running on an AIX environment is imported into a non-AIX environment, if the HTTPS UI connection does not have specific ciphers selected, the UI HTTPS connection will not be accessible until after a restart. As a workaround, before importing the partner profile from an AIX environment, select one or more specific cipher suites to be used for the UI HTTPS connection.

BTOBIEXEC-18259

In SWIFT FIN 2018, the messages that contain a String Z field with values more than 65 characters and without "/" are not rejected

When trying to process a SWIFT FIN 2018 message (e.g. 700), if a field of type String Z (e.g. 45A) contains two or more lines with more than 65 characters without any CRLF/, the message is processed, although it should be rejected, because the total length exceeds the maximum limit for a single line (65).When the first two lines have more than 65 characters, only then the message gets rejected.

BTOBIEXEC-19326

When reverting back from 2.4.0 to 2.3.1 an X12 error is thrown in the console

When trying to revert from an upgraded 2.4.0 B2Bi to 2.3.1 B2Bi, the following error is thrown in the console:

In action "Configure X12 based on license selection [Run script]" (screen "Installation"), property "Script": java.nio.file.NoSuchFileException: <install_location>/Integrator/solutions/config/b2bx/repos/x12.ver.free

Workaround: To downgrade an installation from 2.4.0 to 2.3.1, use the 2.3.1 backed up database and shared folder, and use them in a new B2Bi 2.3.1 installation.

BTOBIEXEC-17126

Trying to connect to an SFTP server having a user containing special characters returns errors

Trying to connect to an SFTP server using an external client returns errors when the user contains special characters like "sftp~!@#$%^&()_+-={}[];'.,".

BTOBIEXEC-19351

X12 dates shorter than expected are not replaced by default date

When the X12 date segment is shorter than expected in the input file, the output value is padded instead of set to the default value 18000101.

Miscellaneous issues

The following issues do not correspond with a case or internal ID:

  • B2Bi Client in place upgrade limitations
  • In order to allow the upgraded B2Bi Client to be downgraded, a backup of the Integration Services workspace must be done prior to upgrade. When downgrading, the backed up workspace must be used. To identify the workspace location, run B2Bi Client Configure and back up the folder specified in the "Enter path to workspace" option.
  • SAP Metadata Browser plugin not supported
  • Issue: B2Bi supports the transfer of IDocs to and from SAP using ALE. However, the use of the B2Bi Metadata Browser to directly view SAP IDOC reports is no longer supported.
  • Workaround: To view SAP IDOC reports, export the reports from the SAP system and use them in the Metadata Browser to create ADF files. For details about creating and viewing ADF files, see the B2Bi Operator Guide / Metadata Browser chapter.
  • Failover and sequential delivery
  • The ability to deliver messages in sequence in the case of a failover is not always guaranteed.
  • API Connector and Datamapper ADF Metadata Browser plugins not supported
  • The Metadata Browser plugins for the API Connector and Datamapper ADF should not be used. They will be removed in a future release.
  • PassPort integration issue with integration engine tools
  • When you configure the integration engine with PassPort access management, the B2Bi integration engine client tools lose the ability to distinguish between different levels of user privileges (view/modify/execute). Access to individual tools can either be granted or not granted.
  • Web Services provider mode configuration using Mapping Services RouteTo block
  • When a Web Services provider flow with attachments is configured that uses a Mapping Services map with a RouteTo block, B2Bi copies the inbound request attachment attributes onto the output response. This results in the inbound attachments being forwarded back to the originator of the Web Service request.
  • Web Services provider mode HTTP connection fails to close
  • Issue: When you configure Web Services provider mode for one-way communication with faults returned to client, on the Web Service trading pickup you must normally select the "Synchronous response generated in backend" option in order to enable sending the fault file to the requesting service consumer. However, if the incoming request message does not trigger a fault and is correctly delivered to the back end, the HTTP connection is kept open until timeout on the client side.
  • Workaround: For a one-way Web Service provider configuration, do not select the "Synchronous response generated in backend" option. This prevents the provider from sending a fault message, but allows the connection to close normally after receiving the client request message.
  • General Web Services limitations
    • B2Bi 2.x supports Web Services on the trading (partner side), but not on the application side.
    • By default, WS-Addressing must be used in provider mode. To disable the need for WS-addressing, refer to the alternate axis2NoWSAddressing.xml file in your WS pickup configuration.
    • The B2Bi WSDL wizard currently only supports the generation of WSDL definitions. These definitions cannot be edited afterwards. To change the WS interface, you must either regenerate a new WSDL using the wizard, or edit the WSDL manually.
  • Web Services provider flow: "check input attributes" and "check output attributes" not persisted on B2Bi server
  • Issue: In Mapping Services, when you create an enumeration in a BusinessDoc leaf (in the Attributes/Enumeration tab), and then use the BusinessDoc in a Flow in which the "check input attributes" and "check output attributes" options are selected, these options are not persisted when you deploy the map to a B2Bi server.
  • Resolution: You must manually select the "check input attributes" and "check output attributes" options in the B2Bi user interface (Service/Service details/Component details).
  • RHEL 6 requirement for X.400 support
  • By default, the Red Hat Enterprise Linux 6 x86_64 operating system installs without installing a 32-bit library (/lib/ld-linux.so.2) needed by the trading engine X.400 subsystem. To enable B2Bi with X.400 installed on RHEL 6, install the glibc.i686 package from the RHEL installation media.
  • Secure Relay installation on AIX platforms
  • For installations on AIX platforms, both B2Bi Server and Secure Relay must use the same operating system.
  • SAN file system hotfix requirement
  • Issue: Two SAN 6.2 cluster nodes show different contents of a file on CFS share.
  • Workaround: In order to run B2Bi on SAN 6.2, you must obtain the VxFS 6.2.0.003 HotFix from Symantec Support and apply the HotFix to each Veritas cluster node.
  • Swagger API client: Swagger user can continue to execute operations after logout
  • When using Chrome and Firefox browsers, after logging out of a Swagger session, a user can call operations as though they had not logged out. This problem occurs because these browsers remember, and automatically provide, the login credentials. Credentials are cleared from memory when the browser window is closed.
  • Swagger API client: Swagger user cannot log in using the login method
  • Issue: The REST login method asks for the authorization header, which is a single string composed of a hash of the username and password. However, in most cases, users only know their username and their password.
  • Workaround: The user can call directly the desired operation. This triggers the login, causing the browser to display a user-friendly prompt for the username and password.
  • With ebXML intermediary (SMTP), message cannot be delivered to external SMTP server
  • When setting up an ebXML intermediary (SMTP), an embedded SMTP server must be used for the receiver. If the external SMTP server is used, the trading to the receiver fails.
  • FTPS outbound transfer fails when Secure Relay Routing Agent runs on AIX
  • Issue: For B2Bi installations with Secure Relay, when the Secure Relay Routing Agent (RA) runs on an AIX machine, FTPS outbound transfers fail when any of the following cipher suites are used as overrides on the partner delivery:
    • SSL_RSA_WITH_DES_CBC_SHA
    • SSL_DHE_RSA_WITH_DES_CBC_SHA
  • Workaround: Select an alternate cipher suite on the partner delivery.
  • Sequential delivery: Trading engine blocks sequential delivery when message-handling timeout threshold is engaged
  • For messages that are consumed on exchange pickups with sequential delivery activated, when the message handling timeout threshold for the pickup is reached, the trading engine begins a resend/retry cycle on the sequenced message that blocks the entire sequence until the production of the message is resolved.
  • Mapping Services known limitations for CDA(Health Care Format) XML schema:
    • The "xsi:type" attribute should display only in elements with the type derived from an abstract type.
    • Simulation of 1-to-1 mapping is not possible due to the number of mapped elements/complexity, but it works fine if it is deployed on the server.
  • Mapping Services - SAP connection not kept after using upgrade option to install 3.4.0.
  • This version can be applied by upgrading a B2Bi Client installation (e.g. from 2.3.1 to 2.4.0, from 2.3.1 SP1 to 2.4.0). Initial configurations are kept, but SAP connection has to be manually set. The "sapjco3.dll" file should be manually added in the MappingServices/plugins/com.axway.ms.dml.sap.bundle_3.3.0.6 folder.
  • Mapping Services recommendations
    • If an error occurs when deploying a project, perform a clean for the specific project and redeploy. This reviews your project and ensures that all dependencies are valid. To perform a clean, from the Mapping Services toolbar, select "Project -> Clean..."
    • For Database Maps, after importing a project, it is critical that the reconnection to a database is performed, to verify that the correct business document structure corresponds with the database tables. For MySql Database Maps, the SQL statement must also be reviewed after the update of the database connection to ensure that the tables and field names in the statement follow the exact names of those in the database. Note: MySql is case-sensitive.

Documentation

This section describes documentation enhancements and related documentation.

Documentation enhancements

The following documents have been updated to take into account new product features and enhancements for B2Bi 2.4.0:

  • B2Bi Installation Guide
  • B2Bi Administrator Guide
  • B2Bi Interchange Upgrade Guide
  • B2Bi Operations Guide
  • B2Bi Security Guide
  • B2Bi Trading Engine Developer Guide
  • B2Bi Capacity Planning Guide
  • B2Bi online help

Support services

The Global Support team provides worldwide 24 x 7 support for customers with active support agreements.
Email support@axway.com or visit Axway Support at https://support.axway.com.

Copyright © 2018 . All rights reserved

 

Related Links