Axway B2Bi 2.6 Release Notes

Document version: January 2020

Important: B2Bi 2.6 Patch 1 is mandatory

Before starting B2Bi 2.6 for the first time, you must install B2Bi 2.6 Patch 1.

If you upgrade to B2Bi 2.6 and start the product before applying Patch 1, you may lose the AS4 certificate agreements defined in your system.

If you upgrade to B2Bi 2.6 and create some AS4 certificate agreements before applying Patch 1, these new agreements are added to the agreements created with your old B2Bi version when you apply B2Bi 2.6 Patch 1.

If any duplicate AS4 Certificate agreements are present in the UI after the upgrade to B2Bi 2.6 Patch 1, you should delete them manually.

Product versions

The following products are installed with the B2Bi 2.6 installers:

Axway product Contents Version

B2Bi Server

B2Bi Server

2.6
 B2Bi Client B2Bi Client 2.6
Mapping Services 3.6 SP1

Standards Libraries:

  • Core EDI
  • Extended B2Bi
  • Financial

 

1.10.0

1.9.0

3.8.0

Integration Services 2.6
B2Bi Integration Engine Client tools 2.6

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

Axway product Version
PassPort 4.6.0
Sentinel 4.2.0
Transfer CFT 3.3.2

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

New features and enhancements

Multi-Cluster

Create an installation architecture with two or more Processing Clusters to increase message throughput and service availability.

Usage metering for AMPLIFY subscriptions

Support for tracking and reporting product usage for subscription customers.

Platform support

Install and run B2Bi on Windows Server 2019 and SUSE Linux Enterprise Server 15.

Database support

Use Oracle 18c as the B2Bi product database.

Java runtime update

B2Bi 2.6 is now delivered with and runs on Azul Zulu 11 for B2Bi Server and Azul Zulu 8 for B2Bi Client.

MQ9

The product can connect and transfer messages to and from IBM MQ version 9.

SAP ALE certification

B2Bi 2.6 has been certified for integration with SAP NetWeaver, using SAP ERP 6.0 and SAP Java Connector 3.0. The certification expires in November 2022.

SAP S/4HANA certification

B2Bi 2.6 has been certified for integration with SAP S/4HANA, using SAP S/4HANA 1709 and SAP Java Connector 3.0. The certification expires in November 2022.

Sequencing for HTTP, OFTP2, RosettaNet

Deliver messages in the same order as they are received on HTTP application pickup, OFTP2 or RosettaNet 2.0 trading pickups.

Debug log per exchange point (OFTP2)

Enable debug logging per individual exchange points (OFTP2).

Long running transactions

Improve the management of long running transactions.

REST API improvements

Enhanced message processing and search operations; new configuration operations:

  • Improved message search
  • Message payload retrieval
  • Message reprocess and resubmit
  • Community and Partner attributes management
  • Metadata Profile attributes management
  • Exchange Point testing

Silent file upgrade

Upgrading between B2Bi versions using silent files has been validated and documented.

Integrator Gateway Connector

B2Bi can now send and receive messages via Axway Gateway. This functionality is only supported for the overall process of migration from Integrator / XIB. Axway Gateway configuration must eventually be migrated to native B2Bi mode.

AS4 Agreements

B2Bi now has support for AS4 Agreements in ENTSOG.

CSOS e222 form updates

The CSOS e222 form has been updated to include Shipped Quantity, Shipped Date and Supplier Street address.

CRLs are required by default

Starting with this release, CRLs are required by default. Upgrades to B2Bi 2.6 are not impacted, as the previous system configuration is preserved.

CoreEDI 1.9.0

Added support for X12 7060.

Financial Standards Libraries 3.7.0

Added support for:

  • SWIFT FIN 2019
  • SEPA SCT 2019
  • SEPA Direct Debit 2019
  • SEPA e-Mandate 2019

Deprecated and removed capabilities

Deprecated capabilities

The following capabilities are deprecated with B2Bi 2.6 and will no longer be supported from B2Bi 2.7 (April 2020) onwards:

  • Symantec Storage Foundation / Veritas Cluster File System
  • PassPortAM support
  • Centralized Access Management can be achieved with external IdP / SAML support in B2Bi, which will be completed to all client tools by B2Bi 2.7.

Removed support for operating systems

The following operating systems are no longer supported:

  • AIX – any version (no more support for AIX as platform)
  • Microsoft Windows Server 2012
  • SUSE Linux Enterprise Server 11

Removed support for databases

The following databases are no longer supported:

  • Microsoft SQL Server 2012
  • Oracle 11g

Fixed issues

Issue and resolution Internal ID Case ID

[DOC] Changes in partner delivery don't trigger peer cloning consistently

Documentation was updated.

BTOBIEXEC-24599 01104579

[DOC] Resetting the sequence on Interchange when the sequence is reset on Integrator

Documentation was updated.

BTOBIEXEC-24203 01044300

[DOC] B2Bi documentation Integrate with Sentinel

Documentation was updated.

BTOBIEXEC-24173 01095437

[RestAPI] retry value of Application deliveries restricted

Issue:

Trying to POST or PUT an application delivery with value of retries more than 100 returns the error : "Retries must be between 0 and 100." In the UI the retry value must be between 0 and 2147483647.

Resolution:

The REST API is aligned with the UI now, so the value of retries can be between 0 and 2147483647.

BTOBIEXEC-24038 01098908

OFTPv2 non signed receipts request command format issue with third party

Issue:

The SHA-256 encryption algorithm is used starting with B2Bi 2.4. When this algorithm is used in newer B2Bis, the SFID command is generated with SFIDCIPH code 03 or 04 - which are rejected as unknown by the partners using older B2Bis.

Resolution:

For making the trading with older partners possible at least when they set no security, the default value for SFIDCIPH when no security is requested for messages and receipts is now 00.

The field in SFID command specifying that no security is set for messages is SFIDSEC=00, the field specifying that no security is set for receipt is SFIDSIGN=N.

Note that the same field SFIDCIPH is used for security of messages and receipts, meaning that the messages and receipt should have the same cipher set for signature if both are set as secure.

When no security is requested for receipt and encryption only is requested for message, SHA-256 is still used as a default, generating SFIDCIPH code 03 or 04.

BTOBIEXEC-23965 01090954

OFTPv2:Secure authentication doesnt seem to work in B2bi

Issue:

Messages sent using the OFTPv2 protocol that use secure authentication to third party partners fail due to invalid AURPRSP command.

Resolution:

Messages sent using the OFTPv2 protocol that use secure authentication are processed successfully by the third party partners.

BTOBIEXEC-23929 01097253

[DOC] reference to B2BiUpdater.bat should be removed

Documentation was updated.

BTOBIEXEC-23927 01080269

OFTPv2 non signed receipts request command format issue with third party

Issue:

The SHA-256 encryption algorithm is used starting with B2Bi 2.4. When this algorithm is used in newer B2Bis, the SFID command is generated with SFIDCIPH code 03 or 04 - which are rejected as unknown by the partners using older B2Bis.

Resolution:

For making the trading with older partners possible at least when they set no security, the default value for SFIDCIPH when no security is requested for messages and receipts is now 00.

The field in SFID command specifying that no security is set for messages is SFIDSEC=00, the field specifying that no security is set for receipt is SFIDSIGN=N.

Note that the same field SFIDCIPH is used for security of messages and receipts, meaning that the messages and receipt should have the same cipher set for signature if both are set as secure.

When no security is requested for receipt and encryption only is requested for message, SHA-256 is still used as a default, generating SFIDCIPH code 03 or 04.

BTOBIEXEC-23737 01090954

Messages being created by the enveloper with ISA/GS but no payload

When the same CIP EDI enveloper stage was used with override attributes or as a dynamic MBC and different sets of separators, or when Outbound agreements were used to envlop EDI messages with different sets of separators, a race condition could cause the documents or transaction sets in the envelope to disappear. Fixed. In case the problem reappears for a different reason, X12 will log a lot more information.

The B2BI_AUX client for the unique id server waited for server replies in the wrong MBC context when used by more than one MBC or more than one MBC instance in the same processing engine. Fixed. This could cause the EDI separators of an MBC instance to be modified by another one. B2BI_AUX is used by default by the B2BI EDI envelopers. This bug was introduced in B2Bi 2.2.1 for farm servers, and in 2.3.0 for everybody.

BTOBIEXEC-23686 01089033, 01089010

Control Numbers roll over at smaller # of digits.

The B2Bi Unique Id task now writes unique files atomically and with truncation, to avoid corruption issues.

The B2Bi Unique Id task will no longer truncate leading zeroes when it receives a request for the current value of unique ids.

BTOBIEXEC-23557 01088594

[DOC] Install guide update for Windows

Documentation was updated.

BTOBIEXEC-23536 01081301

B2Bi TLS use of weak RC4 cipher on port 8865

Issue:

Detected vulnerability on port 8865 with RC4 ciphers.

Resolution:

The weak ciphers RSA_RC4_128_MD5 and RSA_RC4_128_SHA are disabled.

BTOBIEXEC-23500 01071347

Detected an vulnerability with port 8865 'TLS/SSL Server Supports DES and IDEA Cipher Suites'.

Issue:

Detected vulnerability on port 8865 'TLS/SSL Server Supports DES and IDEA Cipher Suites'.

Resolution:

The weak ciphers RSA_DES_192_CBC3_SHA and RSA_IDEA_128_SHA are disabled.

BTOBIEXEC-23499 01073939

Detected an vulnerability with port 8865 'TLS/SSL Birthday attacks on 64-bit block ciphers (SWEET32)'.

Issue:

Detected vulnerability on port 8865 'TLS/SSL Birthday attacks on 64-bit block ciphers (SWEET32)'.

Resolution:

Disabled weak cipher.

BTOBIEXEC-23498 01073938

Cannot see disabled partners - no indication

Updated REST API documentation.

BTOBIEXEC-23494 01088365

XSS /ui/partycfg/local/AuthorizedParties

Issue:

A Cross Site Scripting issue was reported when the URL of authorized trading partners of a community (https://localhost:6443/ui/partycfg/local/AuthorizedParties?partyId=26501) was modified to contain something like "&movepage=1&message.stats.timespan=whs%3C/script%3E%3cbody/onload=prompt()%3e".

Resolution:

The parameters that can be given in the authorized parties page are checked and if their values are not of the requested types, a bad request page will be shown and an error will be logged.

BTOBIEXEC-23188 01069160

[DOC] Insert in the DB lock messages in HME3 queues

Issue:

Not all database parameters were documented.

Resolution:

Extended the documentation to include the "validation query" parameter.

BTOBIEXEC-23169 01078958

Always padding Flat file filed

If the environment variable CORE_MAP_STRING_JUSTIFICATION_NONE_ERROR is defined, customString output fields with justification set to None will give an error if the value set is below the minimum or above the maximum length.

BTOBIEXEC-23163 01068628

SFTP embedded server fails with username containing @

Removed the encoding for user name in case of SFTP embedded server.

BTOBIEXEC-23035 01079631

SSH key no longer working after installation of 2.3.1 Sp3 P3

Issue:

Some SSH keys were not loaded successfully due to the fact that the Bouncy Castle "BC" security provider was replaced in Patch 3 with the "BCFIPS" provider, compatible with FIPS mode. The UI did not display the key and both test from UI and SFTP authentication failed when using that key.

Resolution:

The SSH keys are displayed correctly in UI and the SFTP authentication is now functional.

BTOBIEXEC-22940 01076980

Problems with cloning trading partners option in peer networking

Issue:

When navigating back and forth in Trading partners to clone wizard, in the list of partners to clone, the partners are displayed as selected even though the selection was cleared.

Resolution:

Corrected the issue, now when navigating through the list of partners to clone all selections/deselections are kept for every page of the list.

BTOBIEXEC-22706 01074231

Duplicate cycle links when reprocess message

Issue:

Reprocessing a message generates the same multiple lines in Sentinel's Cycle Link table.

Resolution:

Reprocessing a message generates 2 lines in Sentinel's CycleLink table. For reprocessed messages sent to CFT (using the CFT tracking object in Sentinel) the lines are different, making the connection lines for the CycleGraph (B2Bi initial- B2Bi reprocess - CFT).

Limitation: For non-CFT reprocessed messages the 2 lines are the same in the CycleLink table.

BTOBIEXEC-22695 01057189

queue_commit_history.s4 execution fails

Issue:

Sometimes, calling queue_commit_history.x4 fails.

Resolution:

1) A performance fix in a routine called each time Integrator creates an internal TCP/IP connection.

2) Many performance fixes in the component that notifies all HME tasks in Integrator of configuration changes, for a customer that had thousands of HME tasks.

BTOBIEXEC-22687 01073024

Certificates expiration alert not generated in case of Trusted SSL root certificate

Issue:

When the certificates from the trusted root certificates tabs of a community are expired or about to expire, no alerts are shown in UI or sent through email.

Resolution:

When the certificates from the trusted root certificates tabs of a community are expired or about to expire, the corresponding alerts are shown in UI and sent through email.

BTOBIEXEC-22647 01061459

Apache Commons FileUpload Remote Code Execution Vulnerability

Issue:

If 2.4.0 SP1 is installed, commons-fileupload-1.3.1.jar is still present within the installation folders.

Resolution:

commons-fileupload-1.3.1.jar was removed from the installation.

BTOBIEXEC-22625 01064328

B2BI_FILER.DataIODelete failed to decrease link count on filer file

Issue:

If the "exclude non-existing files from the archiver file list" checkbox is checked, and "write warnings about non-existing files to the trace log" is unchecked, the archiver outputs filer errors. This feature worked on all versions of Integrator but it never worked on B2Bi.

Resolution:

No errors in trace when the "exclude non-existing files from the archiver file list" checkbox is checked, and "write warnings about non-existing files to the trace log" is unchecked.

BTOBIEXEC-22619 01072639, 01102945, 01067657

Finish context entries remain active : RN XPM Triggering

When Integrator could not retry sending a file (e.g. somebody deleted the filer file) the log entry remained active and nothing was sent to the error activity of the send activity. Fixed.

BTOBIEXEC-22618 01062888

Messages stuck in Scheduled Production

Issue:

The Reject processMessages tool is blocked after the first reject message.

Resolution:

The reject process is optimized to not load each MessageState into memory.

BTOBIEXEC-22494 01042210

Errors in control node log when starting B2Bi

Issue:

When starting the B2Bi from command line with option -T, errors regarding application pickups are present in the control node log. The error message is the following format : 'yyyy-mm-dd hh:mm:ss,mmm- ERROR [Cluster Thread xx] (MessageExecutionWrapper) - There was an error while executing message id <MsgId> from node <NodeName> b2bx.server.B2BXException: No connection to Integrator. Could not check Application status for application of name: <B2BiExchangePoint> of type: <Type>.

Resolution:

B2Bi starts without errors in the control node. The issue was caused by a validation method which has one of the many conditions checking if a B2BiExchangePoint is complete by calling Integrator before it starts. Reordering the conditions in the validation method fixed this issue.

BTOBIEXEC-22487 01071877

Cross Site Scripting - ByDeliveryExchange

Issue:

Vulnerability when setting a wrong id for the receiverDeliveryExchangeId

Resolution:

Vulnerability resolved when setting a wrong id for receiverDeliveryExchangeId

BTOBIEXEC-22434 01069153

Cross Site Scripting - TransportModify

Issue:

A Cross Site Scripting issue was reported when the URL of trading pickups of a community page(https://localhost:6443/ui/partycfg/local/TransportModify?bizId=1563543948379.4060@item-ax31384_cn&partyId=47001&transportId=45008) was modified to contain something like "whs"-alert``-"".

Resolution:

The parameters that can be given in the trading pickups page are checked and if their values are not of the requested types, a bad request page will be shown and an error will be logged.

BTOBIEXEC-22433 01069141

WebDav delivery not working

Issue:

When using a WebDAV partner delivery with Apache Server, a 412 error and a 400 error are returned and the file is not delivered.

Resolution:

When using a WebDAV partner delivery with Apache Server the file is successfully delivered.

BTOBIEXEC-22375 01068910

[RosettaNet] Setting the encryption certificate in collaboration setting does not use it to send RN receipt and default certificate configured in the Partner setup.

Issue:

The "Specify the partner's encryption certificate to use" setting from the community to partner specific collaboration settings page was not applied to receipt/signal messages.

Resolution:

The certificate selected on the "Specify the partner's encryption certificate to use" setting from the community to partner specific collaboration settings page is now applied for the receipt/signal messages.

BTOBIEXEC-22374 01071283

RosettaNet - MIME Encoding Options

Issue:

The "quoted-printable" MIME Encoding was not available in the collaboration settings for RosettaNet in B2Bi.

Resolution:

The "quoted-printable" MIME Encoding can now be selected in the collaboration settings for RosettaNet.

BTOBIEXEC-22367 01071221

FTP embedded server slowness

Issue:

FTP protocol command of RETR seemed to hang the embedded SFTP control connection due to an slow query executed on the database with a large number of rows in the messages table.

Resolution:

The query was optimized to run fast.

BTOBIEXEC-22359 01065387

Unable to delete certificates - still

Issue:

A certificate may not be deletable if it is part of a larger trust chain because of improper verification of the certificate's ancestors and their own descendants.

Resolution:

Fixed certificate pre-delete verification in order to apply only on direct descendants - a certificate having descendants is not allowed to be deleted unless all of it's descendants are deleted first.

BTOBIEXEC-22343 01069035

View payload option does not work correctly with Specific role [where all permission selected except 'Administrator. Users with this role have unlimited permissions, regardless whether other permissions are selected.']

Issue:

View payload option does not work as expected with specific role (where all permissions are selected except 'Administrator. Users with this role have unlimited permissions, regardless whether other permissions are selected.') generating the error message "Payload formatting or access error".

Resolution:

The view payload option is now working correctly with specific role (with all permissions selected except 'Administrator').

Also the combined error message "Payload formatting or access error" has been split into separate messages "Payload formatting error" and "Access denied" respectively, depending on the case.

BTOBIEXEC-22283 01059074

SAML Integration with Oracle IDP- Global Logout Error on Redirect Page

Issue:

The logout parameters sent from B2Bi to Oracle Access Management (SAML server) were incorrect.

Resolution:

The logout parameters are now in correct format and the logout action executes successfully.

BTOBIEXEC-22177 01042871

Multiple concurrent threads attempted to access a single broker

Issue:

Messages are stuck in "In process" state with the error "Multiple concurrent threads attempted to access a single broker. [...]".

Resolution:

All messages are processed successfully.

BTOBIEXEC-22151 01038581

Connecting with B2Bi System Manager (tsclient) will cause Errors with full dev path displayed in Trace: "Unknown client option: --"

Removed full path from b2bi_toolbox trace messages.

BTOBIEXEC-22134 01064158

[DOC] JMC Developer Guide - code example to be improved

Documentation was updated.

BTOBIEXEC-22131 01065091

[DOC] - M3 / MOVEX support

Documentation was updated.

BTOBIEXEC-22127 01066326

XSS /ui/partycfg/integration/ServerModify

Issue:

A Cross Site Scripting issue was reported by Customer Security software. When the URL on an application PeSIT embedded server with TLS is modified and contains "isIntegration=whs%22-alert``-%22" an empty box appears when going to the "trusted certificates" tab and clicking on the "expiration date".

Resolution:

A security filter was defined for this route and for the parameter "isIntegration". If the value of the "isIntegration" is not boolean as expected, a bad request error (400) will be thrown in the UI, and an error will be logged: "A boolean value was expected for parameter: isIntegration, but got: <theValueOf>".

BTOBIEXEC-22062 01054039

XSS: /ui/partycfg/integration/TransportModify

Issue:

A Cross Site Scripting issue was reported by Customer Security software. When the URL on a pickup exchange point using an embedded server is modified and contains "isIntegration=whs%22-alert``-%22" an empty box appears when clicking on the embedded server link.

Resolution:

A security filter was defined for this route and for the parameter "isIntegration". If the value of the "isIntegration" is not boolean as expected, a bad request error (400) will be thrown in the UI, and an error will be logged: "A boolean value was expected for parameter: isIntegration, but got: <theValueOf>".

BTOBIEXEC-22061 01054040

"PrintCharString: write failed. errno 4 : Interrupted system call"

"Interrupted system call" errors could occur in .so (DML) maps on Unix platforms. Fixed.

BTOBIEXEC-22034 01064231

MessageLog: Mark as manually corrected creation date

Since jLogger was introduced, the Message Log GUI updates to log entries incorrectly updated the display. Fixed.

BTOBIEXEC-22029 01064165

Re-add CTR ciphers to FIPS

Issue:

In B2Bi 2.3.1 in FIPS mode the CTR ciphers for SFTP transfers were no longer available with the update of the Maverick jars.

Resolution:

The CTR ciphers are now available by providing an alternative security provider for them with BCFIPS.

BTOBIEXEC-22027 01039393, 01001389, 01003215, 01034425

Impossible to update MetadataProfile output

Issue:

When having a map with multiple different outputs, an output could not be modified.

Resolution:

PUT /metadataprofile/outputs modifies an output, as expected.

BTOBIEXEC-22005 01052581

Reopened - B2Bi can't classify EDIFACT document on UNH 009 0057

Issue:

Edifact inbound agreement classification could not be done based on the UNH 009 0057 field.

Resolution:

The field UNH 009 0057 was added in the "Identification" section of the inbound agreement. This will allow filtering of the messages based on the UNH 009 0057.

BTOBIEXEC-22001 01058113

deployment : inconsistency between Mapping Services and Interchange when the version of the deployment package already exists

Issue:

When deploying a package from Mapping Services, the error message "container is already installed" is displayed in CN log when the version of the deployment package already exists, but the result is successful in Mapping Services output console (due to an internal mishandling of packages ids).

The container deployment is incorrectly rejected instead of being overwritten.

Resolution:

When re-deploying a package from Mapping Services (with the same version), the deployment is being now handled successfully.

BTOBIEXEC-21958 01033419

B2BI Integrator : GetParameter method in module "PGM" still supported on B2Bi 2.3.1 ?

Issue:

B2BIDOC_ attributes were not accesible from Amtrix maps.

Resolution:

The behavior of B2Bi 1.5.0, which is also described in the documentation of all B2Bi versions, is restored.

BTOBIEXEC-21955 01015709

Some HME tasks not starting and cannot be started

Issue:

Some HME tasks of Integrator were not starting.

Resolution:

Fixed a security issue related to EDIFACT and X12 files.

BTOBIEXEC-21954 01060507

ebXMl issues CPA builder: To Role not found

Issue:

On the EbXml with the StartBod payload, the sent messages were rejected because ToRole Name could not be found in the payload

Resolution:

The code was modified in this case, to not validate the mandatory existence of ToRole Name field.

BTOBIEXEC-21917 01060748

Duplicate cycle links when resending file from B2B to CFT via Pesit

Issue:

When sending a file from B2Bi to CFT through PeSIT, 2 identical lines (beside the ID) are generated in Sentinel's CycleLink table. When re-sending the file, the lines duplicate, having 4 lines of identical information.

Resolution:

Only one line is generated in Sentinel's CycleLink table when sending a file. When the file is re-sent, B2Bi does not send any CycleLink information.

BTOBIEXEC-21906 00997909

[DOC] Sample JMCs are missing

Documentation was updated.

BTOBIEXEC-21893 01062156

Duplicate element id used in ebXML message

Issue:

While building ebXML soap messages, the B2Bi system may generate duplicate ID for the XML elements that could cause errors on remote system during document processing.

Resolution:

The ID generation function was changed to eliminate the possibility to generate a duplicate ID for the XML elements while building ebXML soap messages.

BTOBIEXEC-21857 00979860

Error when deploying a Datamapper map : STORECONTAINER: Unexpected number of containers, can't handle more then 100000number of containers (see mantis 146657)

Issue :

The Datamapper simulation did not work with maps containing more than 10000 containers.

Resolution:

The Datamapper Builder now allows more than 100000 containers. UNIT_HANDLE_OFFSET errors are therefore replaced by a warning about available memory.

Fixed c4edi compile error about missing data tree handle variables with certain maps in "Store mapped data only" mode.

When running Datamapper Simulation "Store mapped data only" must be set, otherwise the map generator runs out of memory.

BTOBIEXEC-21779 01049315

Delete the ioverflow file when cleaning the timer

Issue:

"r4edi b2bi_clean.x4 -i" does not remove $B2BI_SHARED_DATA/timer/singleton/ioverflow file.

Resolution:

Now "r4edi b2bi_clean.x4 -i" command removes ioverflow file.

BTOBIEXEC-21766 01020456

Web UI users can't update their details

Issue:

Non-admin users could not update their details from 'My profile' link.

Resolution:

Non-admin users can now update their details from 'My profile' link.

BTOBIEXEC-21761 01050844

jQueueJournalFiles increasing on B2Bi Test

Issue:

The number of JQueue Journal Files was increasing on the B2Bi environment.

Resolution:

Fixed a race condition during jQueue compaction that could prevent subsequent compactions.

When the "DataStorage$StorageWriter.doWriteOnce - Message too big for default queue file size, this will decrease performance" message appears in trace or jqueue log, jqueue compaction may hang causing unlimited disk space utilization. Fixed.

A FileAllocator exception occurred sometimes due to a race condition. Fixed.

BTOBIEXEC-21760 01056172

jQueue startup timeout tuning

The new environment variable CONFIGURE_CORE_SERVICES_START_TIMEOUT can be used during B2Bi configure to allow slower startup of JQueue. The value is in seconds.

It can be put in $CORE_ROOT/config/environment.dat to make it permanent.

BTOBIEXEC-21759 01053290

HME3 tasks stop on COP_StringToString

Issue:

When dml repo files which store dml variables definitions are corrupted then the runtime will no longer crash without indication.

Resolution:

Instead error message will be displayed in trace and message processing will be marked with error in Message Log.

BTOBIEXEC-21752 01053582

Unable to delete Messaging ID

Issue:

MessagingID could not be deleted.

Resolution:

MessagingID can now be deleted.

BTOBIEXEC-21738 01060027

Standard functions like 'getYear, getDate,getMinute returns Null when input date value suffixed with 'Z'

Issue:

Standard functions like 'getYear, getDate,getMinute' returns Null when input date value is suffixed with 'Z'

Resolution:

Now standard functions - getYear, getDate, getMinute - extract the right values from input date suffixed with 'Z'

BTOBIEXEC-21660 01044120

Stopping Integrator server takes too long

Issue:

Stopping Integrator server takes too long.

Resolution:

Performance fixes for stopping hundreds of procengines, when CPU for the second level starter process would go to 100%.

BTOBIEXEC-21658 01051238

SFTP trading pickup is cloning all partners when Update a user under 'Accounts owned by partners"

Issue:

Peer Networking, "Accounts owned by partners" in the SFTP Trading pickup Directories: when modifying an account owned by a partner, the auto-cloning for all partners is triggered.

Resolution:

"Accounts owned by partners" in the SFTP Trading pickup Directories: when modifying accounts owned by a partner, only the auto-cloning for the owing partner is triggered.

BTOBIEXEC-21654 01048360

Import of dataset from XIB is getting array index out of bounds error and "search failed" error

Fixed "search failed" errors in Integration Services by escaping special characters.

BTOBIEXEC-21653 01058867

B2Bi can't classify EDIFACT document on UNH 009 0057

Issue:

Edifact inbound agreement classification could not be done based on the UNH 009 0057 field.

Resolution:

The field UNH 009 0057 was added in the "Identification" section of the inbound agreement. This will allow filtering of the messages based on the UNH 009 0057.

BTOBIEXEC-21645 01058113

IDOC parsing issue (ALE pickup) - fix failed BTOBIEXEC-18278

Issue:

For IDOCs received from SAP Server, when adding "EDI_DC40" in the IDOC information fields an error was generated.

Resolution:

Modified the parser to look for separators in the beginning of lines and ignore the rest of "EDI_DC40" occurrences in the idoc.

BTOBIEXEC-21644 01041859

SQL Server: SFTP partner delivery embedded - Downloading events are missing

Issue:

When a No packaging SFTP embedded partner delivery is created and messages are delivered to it, if a user connects with an external client to get his files, the Downloading, Downloaded and Deleted events are not published to te_events.log.

Resolution:

The events Downloading, Downloaded and Deleted are published to te_events.log for a No packaging SFTP embedded partner delivery, when a user connects with an external client to get his files.

BTOBIEXEC-21631 01042697

Transport alerts cause UI error

Issue:

For the items in the "Alerts" menu section, the "right-click -> open in a new tab" option is no longer working as expected, different browsers behaving differently (option is disabled, is not present at all in the right-click menu, or opens a new tab with the title "about:blank#blocked").

Furthermore, in the "Alerts" page (after clicking "More alerts"), some browsers will display the error message "Invalid request! Received a GET instead of POST." when "right-click -> open in a new tab" on an alert item in the list.

Resolution:

The "right-click -> open in a new tab" option is now functional and opens the alert item in a new tab as expected from the "Alerts" menu and the "Alerts" page.

BTOBIEXEC-21602 01039243

Rest API retrieves only the first sftp user defined in application pickup

Issue:

Before the fix, no query returned all the SFTP users defined for an application pickup. It was noticed that it was the same behavior for FTP users defined for an application pickup.

Resolution:

New queries for listing all the SFTP and FTP users (including their subdirectories) defined for application pickups were implemented.

BTOBIEXEC-21577 01051870

Wrong file makes HME task crash

Issue:

A memory corruption appeared when dealing with many errors that exceeded a total of 10000 characters.

Resolution:

Fixed the memory corruption.

BTOBIEXEC-21574 01047214

RNIF 1.1 Optimistic Locking

Issue:

Optimistic locking errors may occur when RNIF 1.1 messages requests and responses are processed on different cluster nodes.

Resolution:

Processing of RNIF 1.1 messages on different cluster nodes should no longer fail with optimistic locking errors.

BTOBIEXEC-21572 01037771

Message attribute definition with criteria not updated correctly

Issue:

Deleting the message attribute condition from the "Message handler" feature will always delete the last criteria and not the selected one.

Resolution:

The deleted message attribute condition is now the selected one.

BTOBIEXEC-21562 01048624

Valuable information for hackers is send in AS4 error response message

Issue:

When using curl to post a faulty message to an AS4 exchange point, the error response contains information about the used libraries (com.ctc.wstx.exc.WstxUnexpectedCharException).

Resolution:

When using curl to post a faulty message to an AS4 exchange point, the error response does not contain information about the used libraries.

BTOBIEXEC-21561 01056137

Unable to connect to B2Bi server from Mapping services if Passport AM is enabled//Backport BTOBIEXEC-5826 correction over B2bi 2.2.1 SP2

Issue:

Deploying maps with Client and Passport enabled fails with a NPE in the cn log.

Resolution:

Deploying maps with Client and Passport enabled succeeds.

BTOBIEXEC-21558 01035357

B2Bi Integration Services : Problems with CIP-deploy after 2.3.1 upgrade

If the connection between the Integration Server GUI and the configuration server broke, the Integration Server GUI went into an infinite loop and flooded the trace. Fixed. This bug has always existed.

Under certain conditions, the "B2Bi Config Server for Integration Services" task could be started on more than one node, leading to data corruption. Fixed. This bug has always existed.

When deploying CIP integrations to a B2Bi installation that already had many services, components, application pickups or application deliveries, the performance degraded significantly. Fixed. This bug was introduced in B2Bi 2.2.1. This fix might cause rest calls to timeout in Integration Services, in which case the timeout must be increased in View->Options.

When deploying some CIP projects, particuarly those migrated from a different version of Integration Services and originally from XIB 2.1.1, every save of a project would create more unsaved changes, requiring the user to restart Integration Services. Fixed.

BTOBIEXEC-21556 01037837

No Event sent to Sentinel B2bi_system tracked object

Issue:

Killed user tasks and FORCE STOP errors were not reported to Sentinel.

Resolution:

Killed user tasks and FORCE STOP errors are reported to Sentinel.

BTOBIEXEC-21549 01019008

Non significant digits are included for the control of reals

Issue:

The real decimal (p,s) for XML is more precise than for other standards. The non-significant digits are taken into account when doing validations, and because of this the facets check fails.

Resolution:

Non-significant digits contained in decimal or scale part will not be considered when doing the length validation for XML.

For example, for a real defined as (4,2), valid values should be: 22.22, 000022.22, 22,220000, 000022,22000000, -22,6900, while invalid values should be 22,222, 222,34.

BTOBIEXEC-21524 01032802

Double messages received from MQ Transfer Adapter

When multiple retrieve methods were used with the same MQ TA, some messages were not committed; also, sometimes received messages were committed when they were not yet written to the XIB internal queue. Fixed.

BTOBIEXEC-21523 01035028

Delivery criteria broken after system restore

Issue:

A delivery settings criteria condition of type Compare with "From equals {partner}" or "From not equals {partner}" exported with system export is not properly imported into a new, empty environment, resulting a broken {partner} reference in the imported condition.

This also affects the community import, not only system import.

Resolution:

The system import and community import now handles correctly the condition of a delivery settings criteria of type Compare, having {partner} reference properly set.

BTOBIEXEC-21514 01023926

SSO not working through B2Bi Load Balancer URL with diffeent outside port

Issue:

Using an Load Balacer/Reverse Proxy/DNS URL between the client and the SSO SAML login page published on the standard 6643 port is not working properly. The client is redirected to the standard B2Bi login page instead of the SSO server login page.

Resolution:

A new system property variable named "sso.forwarded.port" is now available that can be used to configure the port used by the Load Balacer/Reverse Proxy/DNS URL on the public interface. Also the administrator of the Load Balacer/Reverse Proxy can set the "X-Forwarded-Proto"/"Forwarded" header and the B2Bi will accept connections on SSO SAML server as long as the LB public interface uses the standard port=443.

BTOBIEXEC-21481 01043885, 01041327

READ/PIPE READ: end of file / SCAN: end of file on input file

A log entry with a very long description would crash the HME. This bug was introduced in B2Bi 2.3.0. Fixed.

BTOBIEXEC-21460 01049292

Integrator restarts while loading resources for new component of type document

Issue:

When having hundreds of maps and a lot of configuration and trying to add a new component, it stays on loading please wait,

but it never load it and restarts Integrator.

Resolution:

Changed the volume of data sent to list document components with dropbox, now it sends only the component names without the full list of component parameters.

These parameters are sent only when certain document or detector is chosen.

BTOBIEXEC-21399 00994734

Cannot add payload message to SOAP Body due to payload parsing failure

Issue:

Interchange requests data from WebServices and until now the length of the transmitted message was the number of characters instead of the number of bytes, resulting in inconsistencies when dealing with special characters that occupy more than one byte.

Resolution:

Sent the number of bytes instead of the number of characters to Interchange.

BTOBIEXEC-21248 01035304

The system ran out of space because the jQueueJournal directory suddenly had a large size (hundred of GB)

  1. Fixed an error in the output of /references REST API for jQueue. This is a debug API.
  2. The following environment variables can now be used to tune jQueueJournal compaction:
  3. CORE_CS_MIN_FILES_FOR_COMPACTION=compaction is never triggered if disk space usage of the jQueueJournal is lower than this number multiplied by 100 MB
  4. CORE_CS_COMPACTION_USAGE_LIMIT=percentage, between 0 and 100; if the percentage of space in jQueueJournal which is actually used by queue entries is below this limit compaction is triggered
  5. CORE_CS_MAX_FILES_FOR_COMPACTION=compaction is more frequently triggered if disk space usage of the jQueueJournal is higher than this number multiplied by 100 MB.
  6. Fixed some race conditions in jQueue, related to compaction.
  7. When journal file is deleted during compaction the jqueue state become invalid, the compaction remained unfinished and journal files started to accumulate. The issue was fixed.
  8. Increased default logging in jqueue.log files to have more information about jqueue internal state over time. It includes details about journal files, compaction and memory. Even more details are included in logs with level INFO when environment variable EXTRA_DBG_ON_NEW is present.
BTOBIEXEC-21130 01046634

DML addTrace("DEBUG", "test") is logged (as INFO) when the debug is not set in the Service

Issue:

addTrace was throwing traces even if the Component was not set in debug in the Service.

Resolution:

Changed the condition for adding traces. DEBUG traces are now logged only if the Component is set in debug in the Service.

BTOBIEXEC-21084 01043796

Vulnerability scan for b2bi 2.4.0: TLS 1.0 enabled

Issue:

TLS 1.0 is in the default list of enabled protocols.

Resolution:

TLS 1.0 and TLS1.1 are not in the default list of enabled protocols anymore.

BTOBIEXEC-21081 01047222

Warnings sent in cn / te logs when whenever the mapProxyDeployer tool is executed

Issue:

When mapProxyDeployer tool is executed some warnings are shown in _cn.log and _te.log

Resolution:

When mapProxyDeployer tool is executed the warnings in _cn.log and _te.log are shown only in debug mode.

BTOBIEXEC-21003 01045927

SSH Server CBC Mode Ciphers Enabled

Issue:

By default the SSH servers defined in B2Bi used a small number of weak encryption ciphers. Also the user was able to select using the UI interface these weak ciphers using the "Override SSH ciphers" option.

Resolution:

By default the weak encryption ciphers are disabled and the user can select these ciphers only after he manually add them into the ssh.unsecured.ciphers system property.

BTOBIEXEC-20974 01043879

SSH Weak MAC Algorithms Enabled

Issue:

By default the SSH servers defined in B2bi used a small number of weak HMAC algorithms. Also the user was able to select using the UI interface these weak algorithms using the "Override HMAC algorithms" option.

Resolution:

By default the weak HMAC algorithms are disabled and the user can select these algorithms only after he manually add them into the ssh.unsecured.hmacAlgorithms system property.

BTOBIEXEC-20973 01043879

XXE vulnerability in Axway B2Bi for 2.3.1 SP3

Issue:

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.

Resolution:

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.

BTOBIEXEC-20942 01041637

Issue when deploying a CIP : "Cannot find receive activity with id=17188"

Projects created in B2Bi 2.1.0 that contained migration objects (i.e. the projects were originally imported from Integrator standalone) could not be imported correctly in later versions (all migration objects were lost instead of being converted to the new format for migration objects). Fixed. This requires importing again the project from B2Bi 2.1.0 to a fixed B2Bi 2.3.1.

BTOBIEXEC-20897 01038435

Size limit reached in netty : io.netty.handler.codec.TooLongFrameException: Adjusted frame length exceeds 1073741824: 1333586743

If MBC_HIERCHMSGENV.HoldSession and ReleaseSession were used in a hold, release, hold sequence in an MBC, especially with a pause between release and second hold, an HME session slot was leaked. This bug has always existed and would eventually hang the HME. Fixed.

If DATAIO.Delete were moved to the end of ProcessMessage_x in the huge splitter example MBC, IOSET SWITCH errors would occur in the HME under load. This is a bug in the huge splitter because this unzip splitter should be flexible enough to be used as a starting point for completely different sorts of splitters. Fixed.

BTOBIEXEC-20887 01037838

No reprocess event sent to Sentinel for inbound standard messages

Issue:

Reprocess of an inbound standard message would not generate a "Reprocess" event in Sentinel.

Resolution:

When the message is reprocessed, the "Reprocess" event is sent to Sentinel.

BTOBIEXEC-20874 01030110

SFTP trading pickup is cloning all partners when delete a user under 'Accounts owned by partners"

Issue:

Peer Networking sends clone messages for all Trading Partners who have SFTP partner delivery exchange when deleting user in the "Accounts owned by partners" in the SFTP Trading pickup.

Resolution:

Changes were done and now only one peer-message will be sent per changed partner when deleting an account owned by a partner.

BTOBIEXEC-20872 01038609

Scheduler not honored after node restart - polling continued after end time

Issue:

When a schedule on a trading pickup (with the option to not delete the files after pick up) was in place and the cluster manager in a cluster was restarted, the schedule did not stop when it should have.

Resolution:

When a schedule on a trading pickup (with the option to not delete the files after pick up) is in place and the cluster manager in a cluster is restarted, the schedule stops when it has to.

BTOBIEXEC-20844 01010515

Message lost due to optimistic locking

Issue:

The message received using the Pesit protocol was not dispatched if the same file was retransmitted by the remote system while the original message was still in processing.

Resolution:

A new variable named "pesit.checkMessageAlreadyProcessing" is now available in the tuning.properties file that will activate the verification that the same message was not received before and is still in processing. The default value for this variable will be "false" which means that the verification will not be made.

BTOBIEXEC-20823 01023915

Failing RNIF 1.1 message causes thread to get stuck

Issue:

When a specific RN message was being processed, the TE worker thread doing that could end up stuck until a restart of the TE node.

Resolution:

Processing of RN message should no longer block TE worker threads.

BTOBIEXEC-20814 01040815

Error packaging Message: writeTo caught Exception

Issue:

The ApplicationXmlDch.writeTo method throws a NullPointerException under concurentiality conditions.

Resolution:

Synchronized the objects that can be accessed by the concurrent threads.

BTOBIEXEC-20809 00959334

Report on Heatwave : Error GETHANDLEBYDISTNAME in Datamapper when use @ and LastOccurrence

Mixing LASTOCCURRENCE with index expressions in Datamapper never worked. Fixed.

BTOBIEXEC-20621 01021462

Report on Granite: HME3 task stops

Fix for a crash of DML maps in hme_xx functions.

BTOBIEXEC-20494 01022291

Real Number Mapping Issue

Issue:

Numeric data with implied decimal defined as Nn, contain n digits to the right of the implied decimal. Leading zeroes are suppressed unless needed to satisfy the length of the element.

In our case, the received value from input FlatFile T211 field "009" (0.09) was incorrectly transformed to 9. It should have been transformed to 09. (aar 7030 417 fields G15\T2 e11_0462 is defined as N2 in the standard).

Resolution:

The input T211 value "0009" will be transformed to 09 in the output aar 7030 417 fields G15\T2 e11_0462).

I have also tested some other values:

input T211 => value to be mapped => output G15\T2 e11_0462

0900 => 9.00 => 900

9000 => 90.00 => 9000

0090 => 0.9 => 90

0000 => NULL => NULL (This remains unchanged, the fix does not affect this mapping).

This change affects all maps to EDI that contain fields with Data type: "numeric[len], s".

BTOBIEXEC-20439 01023198

Custom message attribute issue added in lower case in packaged outbound message

Issue:

Custom attributes on the header of an outbound message has lower case and it should start with uppercase first letters "X-Cyclone-Metadata" as in the documentation.

Resolution:

I have made the changes and the attribute is shown as in the documentation - "X-Cyclone-Metadata".

BTOBIEXEC-20434 01033097

[DOC] Query about Interchange SSO Login (SAML)

Updated documentation for 2.6.

BTOBIEXEC-20405 01034583

Procengine terminated when the XML header is invalid (contains doubled double quotes)

Issue:

Doubled double quotes in XML header caused terminating procengine.

Resolution:

Fix resolve this issue, though XML is not processed due to invalid syntax.

So added error message for traces and logs about invalid XML prolog.

BTOBIEXEC-20252 01019203

RNIF 1.1 NullPointerException when receiving a ReceiptAcknowledgementException

Issue:

Parsing the RosettaNet 1.1 incoming receipt acknowledgement exceptions from the partners failed with NullPointerException .

Resolution:

The RosettaNet 1.1 incoming receipt acknowledgement exceptions from the partners are parsed successfully.

BTOBIEXEC-20180 01025261

"java.lang.StringIndexOutOfBoundsException: String index out of range: 5818" when sending an IDOC containing EDI_DC40 in a free text field

Issue:

When an IDOC segment contained the string "EDI_DC40" an error was thrown.

Resolution:

Following revision e35eec65, the IDOCs are sent in block and the SAP Server manages to manages to differentiate between "EDI_DC40" as a delimiter and "EDI_DC40" as a text field.

BTOBIEXEC-20125 01003140, 01002775

Change in behavior: CSOS Quantity Received of 0

Issue:

Users were not able to set the "Quantity Received" value to 0 in the E222 form for CSOS 850 orders after receiving the CSOS 855.

Resolution:

Users are now able to set the "Quantity Received" value to 0 in the E222 form for CSOS 850 orders after receiving the CSOS 855 only after a comment is added in the Notes field.

BTOBIEXEC-20103 01027004

Error reading key store file to get private key for certificate randomly

Issue:

When receiving multiple messages from multiple partners, B2Bi uses the partners keys stored in cache to decrypt the messages. If there are more keys than the "keystores.cache.max.entries" property some messages are failed because B2Bi can't find the key in cache.

Resolution:

If B2Bi cannot find the partner's key, it refreshes the cache and then tries to get the key.

As this is a capacity issue, the fix does not solve the issue but improves the behavior.

BTOBIEXEC-19884 01013209

TBLElts-0 max size check

TLV engine fixed.

BTOBIEXEC-19840 01025533

PE TA HTTP OB Task(procengine(ta_http)):Connection id <1> has status null

Fixed more race conditions in the HTTP connector HTTP client socket read events handler. These could be triggered by a small Transfer Timeout and/or a large HTTP TA send queue.

The errors could look like this:

FATAL :(procengine(ta_http)):Connection id <something> has status null

FATAL :(procengine(ta_http)):Illegal connection id <something> called by function HTTPCONNECTION.GETREQUESTPENDING

ERROR :(procengine(transadaptenv)):the MBC 'HTTP Transfer Adapter' threw an exception 'HTTPCONNECTION', error 503 in statement 'HTTPCLIENT.SOCKETREADEVENT_CLIENT'

BTOBIEXEC-19796 01006287

The cluster manager thread blocked caused system hanged on B2Bi login page and transfers failed

Issue:

In "tools/partyInfo.sh" Linux script, OPTIONS variable is not set properly which may cause nodes to connect to the cluster as a TE nodes instead of TOOL nodes.

Resolution:

Fix "tools/partyInfo.sh" Linux script in order to have the node name and node type set correctly.

BTOBIEXEC-19791 01017690

[Documentation] $CORE_DATA/log housekeeping (broadcast-auditdeploy.log and broadcast-audit.log)

Documentation was updated.

BTOBIEXEC-19781 00980593

Importing partner profile with wrong SSH key breaks consecutive imports of SSH key in profiles

Issue:

In the process of import, when was thrown an exception, the temporary file with the keys for SFTP users, remain in the temporary folder, and the process continued.

Resolution:

When the exception was thrown at the extracting and validation keys for the SFTP users, the process of import was stopped, and the temporary file is deleted.

BTOBIEXEC-19779 00996239

Unable to deploy certain maps to B2Bi

DML Mapper repository module fixed to support files greater than 2GB.

BTOBIEXEC-19760 01020994

B2Bi not able to control max number of physical connections for Pesit

Issue:

The Pesit Application Deliveries connection would be closed after a period of time where there was no message received from the partner.

Resolution:

You can now use a tuning property, "pesit.forceConnectionToStayOpen", to force the PeSIT connection to remain open for a certain period of time even if there is no message received from the partner. The tuning property must be set to "true". The connection will stay open until the OS closes it. The setting for transfer timeout - caller mode (seconds) should be similar to OS connection timeout.

BTOBIEXEC-19721 01009460

ALE connectivity issue in a cluster environment

When starting/stopping the tasks on multiple nodes, if the tasks were in the end not started on some nodes, the receive TGs or receive TAs could believe each other were stopped on all nodes. Fixed. Workaround before the fix was to manually restart affected Inbound TA and TG tasks.

BTOBIEXEC-19701 01008205

Interrupted events to Sentinel is missing some values

Issue:

The information about the exchange point for the messages sent to Sentinel related to interrupted events was missing.

Resolution:

The messages transmitted to Sentinel related to interrupted events contains the information about the exchange point.

BTOBIEXEC-19642 00998215

Updating ExchangePoints via API only possible if user password is known

Issue:

Using RestAPI to GET a SFTP partner delivery retrieves the server username and a "*" character for the password. Using the JSON object in a PUT operation would change the server's password to "*" making impossible to correctly update the retrieved server configuration when the password is unknown. This behavior is the same for all servers that have user/pass authentication.

Resolution:

When a PUT operation is executed, if the password for the updated server is "*" the old password will be used.

BTOBIEXEC-19633 01012541

Creating user on second node in CSOS cluster causes unexpected error

Issue:

When adding a new user on a second node of a CSOS Interchange (or B2Bi) cluster, an unexpected error is thrown. The user gets partially created, the email and role are missing.

Resolution:

Updated the CSOS user-related code to act as a singleton in a cluster environment.

BTOBIEXEC-19620 01010516

Message Builder "FORMAT" function & round-up issue

On all versions of Windows and with Visual C++ compilers ranging from Visual Studio 6.0 (released in 1998) to Visual Studio 2017 using the universal CRT in Windows 10 Creators Edition, printf-like functions printed incorrectly rounded floating point numbers (sometimes 0.xxx5 was rounded upwards, sometimes downwards).

Even correct implementations such as the Linux glibc (which uses GMP behind the scenes) might cause issues due to the inherent precision loss of binary floating point representations of decimal numbers.

Introduced a new reserved variable in the Message Builder language, $__NumericFlags__, that, when set to $__OverrideOsRounding__, should fix float-to-integer conversions and also switch the FORMAT() implementation for the %f, %g and %e format specifiers from the operating system one to an improved one (see $CORE_ROOT/readme/lucent_license.txt for the name of the author of the code). The new routines implement bankers' rounding (round-to-even) with a tolerance to binary floating-point representation loss of precision of three decimals (if the binary error is so large that the most significant three decimals to be lost through rounding are affected, the rounding will be in error).

These flags are defined in "4ediflags.s4h". They are not used for compile-time constant folding (i.e. integer variables assigned floating point constants in the original or the post-optimization code, or calls to FORMAT() which can be computed at compile time) unless the environment variable C4EDI_OPTIONS contains -t OverrideFormatFloatRounding.

The new reserved variable is specific to the .x4 program in which it is set. Other Message Builder programs will have different values of the variable and therefore be unaffected.

Added the c4edi language options -t DoNotFoldConstFormatFunc and -t OverrideFormatFloatRounding. The first of these stops the compiler from optimizing a FORMAT() call to a constant - but is ineffective if FORMAT() is called in a the constant initializer of a variable. The second one enables the new FORMAT() implementation for FLOAT variables, both during compilation of an .x4 file (including for constant initializers) and at runtime, again only for that .x4 file.

As usual, all c4edi options are also settable through the environment variable C4EDI_OPTIONS.

BTOBIEXEC-19502 00890300

Hang issue in Integrator "B2Bi TA B2BXGI OB Task"

Repeating "Unexpected disconnect made by GI" errors in Trace Viewer caused Integrator to stop sending messages to Interchange, or to send them extremely slowly (one attempt every 5 seconds, 12 messages per minute that is). Connections are reconnected more aggresively now, fixing this issue.

Tentative fix for the following issue: sometimes Integrator stops sending messages to Interchange (no message in transaction for the "B2Bi TA B2BXGI OB Task" queue in Queue Monitor, though this task is started). This was only observed at two customers without debug enabled, not in Axway and not reproduced again by the customers, thus the cause is still uncertain. Possible workaround (if the fix does not work) is to restart the task.

BTOBIEXEC-19498 01015028

FSL - [SWI - 28008]: Invalid Block 1

Issue:

There was no error message when customer used a bdoc without opening tags.

Resolution:

Added an error message.

BTOBIEXEC-19478 01041569, 01011472

While checking message through message log shows error 'DATAIO.OPENINPUT: failed to open file' in trace

Filer files could not be accessed on Windows from automatically restored archives. Fixed.

This bug (in the automatic restore feature) has always existed.

Old archives will not be fixed by this (but they can be fixed by manually creating symbolic links).

BTOBIEXEC-19467 01011016

Dataconversion in mapping cannot handle valid utf-8 triple byte

When converting to all ISO8859 encodings, Unicode dashes of various length, breaking and non-breaking, are now converted to an ASCII hyphen-minus instead of an error. This change does not otherwise affect the existing hyphen-minus and soft hyphen characters. This fallback to hyphen-minus is recommended in the Unicode standard. The conversion will consider this a distortion.

BTOBIEXEC-19439 00995550

RCA : Crash of integrator Trace task

Fixed three race conditions that could cause the trace server to crash. These were very rare conditions, and two of them were introduced in the year 2013.

Another race condition in the trace server could cause it to report fewer entries for a Trace Viewer search limited to the past. The search had to have returned more than 1000 entries (or 10000 entries for trace server versions from before the year 2013). Fixed. This is a very old non-crash bug, but after the -e feature was added and enabled by default in 2013 this old bug caused the two above-mentioned crash bugs.

Improved the functioning of the trace server -e option, the old behaviour still hung for one second. The -e option is enabled even if not present in the command line, and it helps to avoid unresponsiveness when huge searches are done in the Trace Viewer.

Long running searches in the trace server could return a few duplicate and out-of-order messages. Fixed. This bug was introduced in 2013 with the -e option.

BTOBIEXEC-19399 00998348

HME task crash when archive is running

The DML function GetInputMessage would crash the processing engine if the filer file was deleted. Fixed, now an error is returned.

The filer has been improved to isolate badly behaving custom MBCs from well-behaving ones with regard to filer errors. To benefit from this fix, the following procedure is necessary, otherwise the isolation will not be enabled:

  1. After installing the fix, go to the CoreTasks tab in Composer, and create a new filer task with a new directory.
  2. Assign the new filer task to all other CoreTasks which have a Filer Task Reference and, also, all CommAdapters from the neighboring "Communication" tab, replacing the old filer task.
  3. The old filer task and its directory may only be deleted a couple of months after the new filer has been sent to server.

Data will not be lost, as the tasks will still connect to the old filer for old data.

BTOBIEXEC-19396 00987100

FTP Transfer Adapter issue

On Windows, even if BSOCKET_SOCKET_COUNT was set to a large value, a single FTP service task could handle no more than about 30 FTP connections at the same time without random hangs. Fixed. This bug has always existed.

BTOBIEXEC-19395 00992983

procmbc_cscconverter does not work as expected, Our Windows charset convertors never implemented "allow distortion"

Improved distortion and fallback character support in the "windows" character set encodings; it should now match the support in the ISO8859 encodings.

BTOBIEXEC-19327 01011468

Application Delivery looks invalid in Web Browser (UI)

Issue:

The Application Delivery UI display is corrupt in some cases if an error condition is encountered on one of the Application Delivery items.

Resolution:

The Application Delivery UI is now rendering properly, displaying the "alert" icon if an error condition is encountered on one of the Application Delivery items.

BTOBIEXEC-19306 01014185

Deployment preformance issues

Improved the re-deployment time of maps from Mapping Services by optimizing some write operations.

BTOBIEXEC-19195 01012042

IDOC Enhancements are not displayed by the SAP Server importer

Issue:

Customer created an extended idoc ZDELVRY07EXT that couldn't be imported from SAP Server (it was not displayed by the importer tool).

Resolution:

The extended idocs can now be imported.

Note: They will appear in the idoc list with the prefix "EXT_". Ex: EXT_"ZDELVRY07EXT".

BTOBIEXEC-19052 01002199

Failed to write stage Classifier when deploying a copied project

The fix_xib module is again available. It contains tools to fix XIB 2.1.1 datasets being imported into CIP.

BTOBIEXEC-18959 01005290

The attribute 'B2BXGIReceive_B2BiRootCoreId' does not exist in sample MBC

$CORE_SOLUTIONS/example/procmbc_b2bi_exampletrigger.s4 did not work correctly if Sentinel was enabled (the errors stated that the attribute B2BXGIReceive_B2BiRootCoreId was not set). Fixed.

BTOBIEXEC-18068 00999232

Edigas detector concurrent access issues

Issue:

The Edigas needs to be updated with new modifications.

Resolution:

Updated the Edigas standard code for B2Bi.

BTOBIEXEC-15399 00952735

Standards Library

Description Internal ID Case ID

Error "Unknown TAG" when parsing an MT202COV message

Field 121 was updated for all 271 bdocs with the new pattern xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx and length of 36 characters.

STAN-3545 01074222

Transformation CFONB160 CFONB320 SCT

Issue:

The comparison was done only if $Sum/100 is strictly greater to 0.0 . As a consequence, any CFONB input values between 0 and 9 were failing.

Resolution:

Modified comparison of variable $Sum/100 to be greater or equal to 0.0 . This allows also input CFONB values between 0 and 9 to be valid.

STAN-3498 01070591

Unix / Windows Input File Format

Issue:

Only Windows delimiter was present in Mapping Services, so any Unix file must have Unix delimiter (LF).

Resolution:

Added an alternative delimiter (LF) in Mapping Services, in order to allow both types of files (windows and unix) without prior delimiter modifications.

STAN-3499 01071427

Mapping Services

Description Internal ID Case ID

IDOC Enhancements are not displayed by the SAP Server importer

Issue:

Customer created an extended idoc ZDELVRY07EXT that couldn't be imported from SAP Server (it was not displayed by the importer tool).

Resolution:

The extended idocs can now be imported.

Note: They will appear in the idoc list with the prefix "EXT_". Ex: EXT_"ZDELVRY07EXT".

 

BTOBIEXEC-19052 01002199

Known issues and limitations

Issue or limitation

Internal ID

(Case ID)

[FIPS] The DHE ciphers are missing from the TLS cipher list when ssl.unsecured.ciphers is true

The ciphers TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 and TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 are missing from the TLS cipher list when B2Bi Server Heatwave is in FIPS mode and the property ssl.unsecured.ciphers is set to "true".

BTOBIEXEC-24686

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.5, which affects AS2 transfers.

BTOBIEXEC-19896

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-15830

Datamapper simulation HEADERS file

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

BTOBIEXEC-16835

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

When trying to revert from an upgraded B2Bi 2.4.0 to B2Bi 2.3.1, 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: /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 in a new B2Bi 2.3.1 installation.

BTOBIEXEC-19326

Trying to connect to an SFTP server with 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 such as "sftp~!@#$%^&()_+-={}[];'.," .

BTOBIEXEC-17126

FIPS-compliant implementations and PassPort

FIPS-compliant implementations of B2Bi Server 2.6 cannot be used with PassPort.

BTOBIEXEC-23920

UniqueIdTool.x4: Using the UniqueIdFilePath parameter

In a Multi-Cluster environment the file does not physically exist. It is a grouping of unique ids maintained just to preserve backward compatibility.

The path must contain <B2BI_SHARED_DATA>/uniqueserver/singleton/. The system connects to the server, the group with the file name (excluding the folder) is used and unique ids are stored only in Apache Ignite Server. The file name is used only as a grouping of unique ids and the folder is used only for backward compatibility (the folder is actually discarded).

For example, in a Multi-Cluster environment, the following command displays all the unique sequences that are part of the group file1.unq:

r4edi UniqueIdTool.x4 $B2BI_SHARED_DATA /uniqueserver/singleton/file1.unq

BTOBIEXEC-24259

Restoring and reverting are not supported for B2Bi Server 2.6

When installing B2Bi Server 2.6, you cannot restore or revert to the previous version. You can only uninstall B2Bi Server 2.6 and re-install the previous version.

BTOBIEXEC-24085

Start failure for B2Bi clusters on Linux with NFS

B2Bi clusters on Linux with NFS may take more time than expected to start correctly or may restart several times before successfully starting. To troubleshoot this issue, it is recommended to turn off the read lease function on the NFS server:

  1. Important: Stop B2Bi before you perform this procedure.
  2. As root, execute the command:
  3. echo 0 > /proc/sys/fs/leases-enable
  4. Restart the NFS daemon:
  5. /etc/init.d/nfs restart
  6. After you complete the previous steps, unmount and re-mount from the NFS clients.

The B2Bi Administrator Guide has been updated accordingly. See the Troubleshoot unexpected trading engine restarts section.

BTOBIEXEC-21402

Verify status of resent messages in case of trading engine failure

For Linux installations: If the trading engine fails while processing a batch of messages that were resent via the REST API, you should verify in Message Tracker if all the IDs from the REST API response were processed or not.

 
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 Metadata Browser chapter in the B2Bi Operations Guide.
  •  
    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 backend, 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.
    • Currently, the B2Bi WSDL wizard 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.
  •  
    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 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 an 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.
  •  
    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.
  •  
    PassPort integration issue with integration engine tools
  • When configuring 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.
  •  
  • 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 (for example, from 2.3.1 to 2.4.0, from 2.3.1 SP1 to 2.4.0).
  • Initial configurations are kept but the 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 database connection has been updated to ensure that the table and field names in the statement follow the exact names of those in the database.
  • Note   MySQL is case-sensitive.
  •  
    B2Bi in FIPS mode not available with PassPort integration
  • FIPS-compliant implementations of B2Bi Server 2.6 cannot be used with PassPort.
  •  

    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.6:

    • 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

    B2Bi is accompanied by a complete set of documentation, covering all aspects of using the product. To find documentation for this product version, go to http://docs.axway.com. Additional documentation may be available at Axway Support at https://support.axway.com.

    For step-by-step instructions on how to configure and how to convert various inbound and outbound files from one format to another, see the B2Bi Getting Started Guide.

    The following reference documents are available at http://docs.axway.com:

    • Supported Platforms - Lists the different operating systems, databases, browsers, and thick client platforms supported by each Axway product.
    • Interoperability Matrix - Provides product version and interoperability information for Axway products.

    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 © 2019 . All rights reserved

     

    Related Links