Axway B2Bi 2.6 SP1 Release Notes

Document version: August 2020

Important: New packaging method for Service Packs

B2Bi 2.6 SP1 is now delivered as a self-contained package (.sh / .exe) that can either be installed as a standalone product or be used for upgrade from B2Bi 2.6. Before upgrading, make sure to back up your entire system (existing installation folders, shared folders, database contents). See the B2Bi installation guide.

Downgrading to 2.6 is not supported from the installer. If you try to uninstall a service pack, the whole B2Bi product is uninstalled.

Important: B2Bi 2.6 SP1 Patch 2 is mandatory

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

Product versions

The following products are installed with the B2Bi 2.6 SP1 installers:

Axway product Contents Version

B2Bi Server

B2Bi Server

2.6 SP1
 B2Bi Client B2Bi Client 2.6 SP1
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 SP1
B2Bi Integration Engine Client tools 2.6 SP1

 

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

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 improvements

Patch a Multi-Cluster system without processing downtime. Use individual DMZ nodes for each processing cluster.

Platform support

Install and run B2Bi on Red Hat Enterprise Linux 8 and CentOS 8.

Database support

Oracle 19c is now supported.

Support for TLS 1.3 for selected protocols

The first phase of TLS 1.3 support focuses on the UI and REST API HTTPS connections, as well as on HTTPS No Packaging and AS2.

Extended external Identity Provider support

Users managed by an external Identity Provider can now authenticate to Mapping Services and B2Bi System Manager.

Consolidate configuration on shared folder

More of the B2Bi configuration is now stored in the shared folder, thus simplifying upgrades.

Sentinel Tracked Object in Mapping Services

Import and use the Sentinel Tracked Object definitions from native Sentinel server XML representation into the Mapping Services workspace.

REST API improvements

New configuration objects available in the REST API:

  • Message Handler - Message attributes
  • Message Handler - Message processing actions
  • Partner categories
  • Roles management

X12 Improvements

B2Bi now includes the HIPAA 5010 standard messages.

The X12 repetition character and composite elements syntax rules are now supported.

Miscellaneous

Allow for 4096 key length in FIPS mode.

Financial Standards Libraries 3.8.0

  • Added support for IBANSTRUCTURE_V2 FULL and DELTA format for reference data files.
  • Added support for SWIFT MX 2020 format (Payment Clearing and Settlement).
  • Added support for the following CBPR+ format messages: camt.052.001.08, camt.053.001.08, camt.054.001.08, camt.060.001.05, camt.057.001.06, pacs.002.001.10, pacs.004.001.09, pacs.008.001.08, and pacs.009.001.08.
  • Added support for Oracle 18c and 19c for Reference Data integration.
  • Added support for the following ISO 20022 messages: camt.052.001.08, camt.053.001.08, camt.054.001.08, camt.057.001.06, camt.026.001.08, camt.029.001.10, camt.056.001.09, camt.087.001.07, pacs.002.001.11, pacs.003.001.08, pacs.004.001.10, pacs.008.001.09, pacs.009.001.09, and pacs.010.001.04.

Extended B2Bi 1.9.0

  • Added support for HIPAA 5010 standard.
  • Updated the EDIGAS standard messages to the 5-1-5 codelist.
  • Updated MARSIT and ACKNOW Edigas messages to the 5-1-5 codelist (STAN-751 -00878240).

Deprecated and removed capabilities

Deprecated capabilities

The following capabilities are deprecated with B2Bi 2.6 SP1:

  • SSLv2Hello and SSLv3 support
  • Staged HTTP servlet support
Note   Support for these capabilities will be discontinued no earlier than the next 9 months.

The following capabilities are deprecated with B2Bi 2.6:

  • Symantec Storage Foundation / Veritas Cluster File System
  • PassPortAM support
  • Centralized Access Management can be achieved with external IdP / SAML support in B2Bi.

Removed support for Integrator tools

The following Integrator tools are no longer supported:

  • servermode
  • optimizeServer
  • ExecuteServerCommand
  • deployment

Fixed issues

This service pack provides the following corrections and enhancements:

Issue and resolution Internal ID Case ID

Failed to parse received EMAIL message: token not found in content-type

Issue:

The standard Delphi Internet protocol library (Indy) sends the Content-type header with a spurious semicolon at the end, violating RFC2045.

Resolution:

Made the EMAIL Integrator connector more tolerant, because there are companies still using Delphi in 2020 and trading with Axway customers.

BTOBIEXEC-27665 01153576

B2Bi 2.4.0 to 2.6 upgrade fails on the Upgrading configuration for Integrator Core step

The start timeout of b2bi_startup.x4 during B2Bi upgrade was increased from 30 seconds to 240 seconds. This and other installation timeouts are now tunable through the
CORE_INSTALLER_TIMEOUTS environment variable.

BTOBIEXEC-27630 01123926

[CSOS] EDI 850/855 not linked when 855 is created from split

Issue:

When multiple CSOS 855 files are received in one message which passes through EDI Splitter, the related 850 orders were not updated because of a missing message state.

Resolution:

When multiple CSOS 855 files are received in one message which passes through EDI Splitter, the correct message states are created, and the CSOS 850 orders are correctly linked and updated.

BTOBIEXEC-27623 01140472

[DOC] Install guide error

Issue:

Documentation was describing wrong location folders for Integrator log and trace directories.

Resolution:

Documentation was updated.

BTOBIEXEC-27621 01153308

Bad Request error when clicking "Next" on the Trading partners page of a community

Issue:

Clicking Next on the Trading partners page of a community returns a Bad Request error.

Resolution:

Fixed.

BTOBIEXEC-27612 01153111

[DOC] Linux packages required for installation

Issue:

Documentation was lacking details about the Linux packages required at installation time.

Resolution:

Documentation was updated.

BTOBIEXEC-27533 01151445

MO_HttpSend.s4 when using HTTPLIB: tasks completely freeze on big messages, and determine severe service interruption

Issue:

When using HTTPLIB, tasks completely freeze on big messages, and determine severe service interruption.

Resolution:

HTTPLIB.ClientDialog leaked a filer file in case of error during the sending phase of a larger (>16KB) transfer.

MBCs that use HTTPLIB and are not recompiled will not benefit from the fix.

BTOBIEXEC-27503 01151025

Customer needs to decide in Integrator (in our CIP) between inline and normal attachments. Currently the attribute B2BXGIReceive_packagingLocation contains the value Attachment for both types.

Issue:

There was no way to differentiate between regular Email attachments and inline attachments. Both such messages generated by B2Bi had the packagingLocation attribute with the Attachment value.

Resolution:

B2Bi messages generated from Email inline attachments will now contain the packagingLocation attribute with the
InlineAttachment value. Regular email attachments will still have the Attachment value.

BTOBIEXEC-27499 01148404

Password required for public/private keypair auth users

Issue:

When creating a trading pickup over an embedded SFTP server which requires SFTP client to authenticate using a public/private key pair and adding such user with username and public key, accessing Transport Users (SFTP) will display "User needs a SFTP password policy". Furthermore, selecting an user and trying to save changes will display "Invalid user password".

Resolution:

In this scenario, when the server requires the SFTP client to authenticate using a public/private key pair, no password or password policy should be required.

BTOBIEXEC-27473 01149903

Resetting the sequence on Interchange when the sequence is reset on Integrator

Issue:

The B2Bi administrator should have the possibility to reset the sequence numbers in Interchange without running a whole purge.

Resolution:

The messagePurgeTool script has been modified by adding a new parameter, called resetSequences, that deletes the information managed by the sequence coordinator in Interchange.

BTOBIEXEC-27472 01044300

Can't select "Deliver to application" on CIP with more than 10 outputs

Issue:

In a CIP flow with more than 10 outputs, we can only select an application delivery for the first 10 outputs. The drop-down list is disabled for the remaining outputs.

Resolution:

We can select an application delivery for all the outputs in a CIP flow with more than 10 outputs.

BTOBIEXEC-27421 01149714

Issue while executing mapProxyDeployer commands

Issue:

A non-admin user could not run the mapProxyDeployer tool.

Resolution:

If the user has the necessary rights, they can run the mapProxyDeployer tool.

BTOBIEXEC-27377 01148416

Issue with partner inbound Webservices responses

Issue:

With a B2Bi license that does not support message processing and integration, a synchronous WebService response was scheduled to be sent to Integrator.

Resolution:

Two additional checks were added:

1. If the license does not support message processing and integration, the
NODE_SEND_TO_B2BI_CONNECTOR node is not created.

2. If the license does not support message processing and integration and the
NODE_SEND_TO_B2BI_CONNECTOR node already exists, the doAction() in this node will treat all messages in Interchange mode.

BTOBIEXEC-27351 01144386

[DOC] B2Bi Cluster A/A : Failover and expected behavior

Issue:

Documentation was lacking information about ports to be open in a cluster.

Resolution:

Documentation was updated to include information on the ports required to configure network communication in an active / active setup.

BTOBIEXEC-27312 01141744

How to trigger a metadata profile when a message is received by XFB Gateway

Issue:

No migration option was shown in metadata profile criteria.

Resolution:

Added migration options in metadata profile criteria when XFB Gateway is enabled.

BTOBIEXEC-27309 01140268

Replacing PeSIT embedded server corrupts PeSIT application delivery client authentication certificate

Issue:

Exporting the private key of a TLS client certificate for an application delivery resulted in a 0 kb file. This issue was first observed for PeSIT clients, and then for HTTPS clients.

Resolution:

The private keys of TLS certificates are exported correctly after adding the integration PSE as an option from where to retrieve the private key.

BTOBIEXEC-27245 01146101

Agreement configuration changed when using peer networking

Issue:

For two peer nodes that have a community, a partner and an agreement using a specific routing ID of the partner as sender or responder, the agreement sender (or responder) identifier is changed to ALL in the mirror node when the partner is modified in one node, even if the change does not involve the routing ID.

Resolution:

An extra check was added to change the identifier to ALL only if the routing ID of the partner is changed, and the old routing ID was deleted and cannot be found.

BTOBIEXEC-27236 01137489

String or binary data would be truncated

Issue:

Some messages are reported as failed in Message Tracker and Message Log, but the receiving partner has confirmed that they have actually received the messages. The problem occurred when the advanced search information related to the messages delivered to multiple endpoints was saved in the database, and was caused by the undersized column length and some database transaction errors.

Resolution:

The column type was changed to accommodate the information size, and the database transaction errors were solved.

BTOBIEXEC-27201 01119961

Application Delivery custom directory not working

Issue:

Adding SFTP user directories containing the colon character (:) could corrupt the delivery URL in UI, and also resulted in failed transfers to that delivery.

Resolution:

SFTP user directories containing the colon character (:) can now be defined in UI without corrupting the URL, and trading will also work.

BTOBIEXEC-27198 01138916

Issue when updating migration pickups

Issue:

Changes made to migration pickups from the UI (for example, XFB.Gateway) are not properly sent to Integrator. Especially when editing the pickup's name, the Integrator ends up with two pickups: the existing pickup with the old name, and a new pickup with the new name, respectively.

Resolution:

Changes made to migration pickups from the UI are now properly sent to Integrator, and editing the pickup's name is reflected correctly in Integrator.

BTOBIEXEC-27157 01143683

"0" should not be in the drop-down list for "Test indicator" (Inbound EDIFACT agreement)

Issue:

When creating an inbound EDIFACT agreement, in the Inbound tab, there is a setting called Test indicator. Depending on the EDIFACT version used in the agreement, it contains different values (0-1 or 0-1-2-3-4...). According to the standard, "0" is not a valid value for Test indicator. Therefore, the availability of "0" in the drop-down list is confusing.

Resolution:

The 0 Production option in the Test indicator drop-down list was renamed to Production.

BTOBIEXEC-27138 01119217

[RestAPI] SSH key in SFTP application delivery

Issue:

When creating an SFTP application delivery that connects to an external SFTP server using the public/private key pair authentication, there is no option or way to add the private key with the REST API.

Resolution:

When creating an SFTP application delivery that connects to an external SFTP server using the public/private key pair authentication, the private key can be added in the body of the request.

BTOBIEXEC-27134

01142512

01143138

AK4 Segment issue for Outbound 997

Issue:

Acknowledgement segment AK4 was not present in the output.

Resolution:

Selecting the option to return detailed acknowledgements on the inbound agreement returns the correct content in the AK4 segment.

BTOBIEXEC-27110 01141446

Inclusion file filtering still fails with Directory Attribute Mapping via SFTP

Issue:

When having Directory Mapping and an inclusion file filtering enabled, the file is not consumed from the directory that matches the given pattern.

Resolution:

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

BTOBIEXEC-26959 01135459

A2A perfomance issue (InHouse parser)

Multiple performance improvements were brought to the areas of mapping, character set conversion, and general HME processing.

One of the biggest improvements was made to DML A2A maps, and can be enabled by setting both the CORE_TINY_INSTANCES and
CORE_TINY_INSTANCES_FASTER environment variables to any value.

BTOBIEXEC-26935 01139487

Gateway HTTP Interface documentation

Issue:

The new feature Axway XFB Gateway HTTP Interface and the associated configuration page are not covered in the documentation.

Resolution:

Documentation was updated to include information on the Axway XFB Gateway HTTP Interface option and the associated configuration page.

BTOBIEXEC-26911 01107269

logger_raisehighestlogid.x4: error bumping the current log id number: operation not allowed in external allocation mode

Issue:

The logger_raisehighestlogid.x4 tool does not work.

Resolution:

An extra parameter, CORE_LOGGERQUEUE, was added. To raise the logger ID, you must configure the logger_raisehighestlogid.x4 tool to connect to the queue server port instead of the logger port. The number for raise must include the name of the logger.

BTOBIEXEC-26882 01135608

Log the b2bi_clean execution in the trace file

Issue:

There is no way to detect if b2bi_clean.x4 has been run: nothing is logged in the trace file.

Resolution:

Added new log file for b2bi_clean actions, including the -S option.

BTOBIEXEC-26732 01044297

IDOC packaging does not receive all IDOCs in a single IDOC flat file

Issue:

When SAP sends data to B2Bi, it starts off being sent with a number of IDOCS in one transmission. When it arrives using ALE, the data is split into separate IDOC files rather than the original file containing all of the IDOCS.

Resolution:

The new B2BI_DO_NOT_SPLIT_IDOCS option in System Profile Manager disables IDOC splitting.

BTOBIEXEC-26730 01086431

SetupService throws NoClassDefFoundError

Issue:

The tool for installing / uninstalling the Windows service for Secure Relay, setupService.bat, was failing with class-path related errors.

Resolution:

Class-path issues were fixed, and the Windows service can be installed or uninstalled without errors.

BTOBIEXEC-26723

01133767

01134125

Integrator Message Build Language: DateFormat and %z option

Issue:

The MIME.GetTimeZoneOffset function was documented but the MIME library was not provided with B2Bi.

Resolution:

The library is now provided with B2Bi.

BTOBIEXEC-26518 01134144

The installation of SP1 failed : “java.lang.NullPointerException” error in the update.log files

Issue:

The installation of SP1 fails with the java.lang.NullPointerException error, as shown in the update.log files.

Resolution:

Internal fixes have been made in the installer and the updater to ensure path comparison on Windows is not case-sensitive.

BTOBIEXEC-26517 01134349

Upgrade to B2Bi 2.6 fails in decoding stored keys after upgrade

Issue:

Strings encoded in Base64 as MIME (containing symbols outside the Base64 alphabet) could not be decoded.

Resolution:

A MIME decoder to be used for strings encoded in Base64 as MIME was added.

BTOBIEXEC-26496

01134512

01145960

Unable to search for some CSOS certificates

Issue:

In B2Bi, when retrieving certificates and the result set is broken into pages, the SELECT statement is run for each page. If the ORDER BY ValidTo criteria uses the same value for a high number of certificates, the database would retrieve the SELECT statement for a single page, not for the total values. This means that some certificates could be omitted or retrieved more than one time. This is a known issue for the ordering clause.

Resolution:

When an ordering is used in the search of certificates, a second criteria (with unique values) is added, so the SELECT statement for pages will be done correctly.

BTOBIEXEC-26430 01061111

Vertical Privilege Escalation Issue - forced browsing issue

Issue:

A WebTrader user can view and download the payload of a message for which the user does not have access rights by copying the HTTP request from another legit user.

Resolution:

User access rights to message payload are now properly checked.

BTOBIEXEC-26392 01070327

An SQL command severely impacts the performance of the Oracle database, which causes a System Throttle on multiple B2Bi systems

Issue:

Full table scans for two big tables inside a nested loop were performed. Therefore, the execution of some SQL queries related to processing the response of a RosettaNet 2-way-PiP took too long.

Resolution:

The bad queries were changed and optimized so that indexes from the two tables in question are now used. The new queries are relying on specific RosettaNet data that should always exist for valid flows. If the specific data is missing, a query performing a full table scan on a single table might still be executed. However, this should only happen while processing some specific invalid RosettaNet responses, and should still be faster than the original query, which resulted in full table scans on two different tables.

BTOBIEXEC-26362 01123867

Config Server not reachable: crash when accepted connection exceeds the limit value

Issue:

Config server becomes unreachable when there are many connections.

Resolution:

Increased the socket backlog of the cfgserver processes to 4096 to prevent issues when scripts could not connect to the cfgserver. Note that on Linux the socket backlog is also affected by system-wide sysctl parameters net.ipv4.tcp_max_syn_backlog and net.core.somaxconn; on other platforms other parameters apply.

BTOBIEXEC-26355

01126330

01127111

Unexpected element 'e:lotNumber' encountered

Issue:

Error parsing XML file with unexpected element encountered warning.

The issue was that the old load with BDOC metadata did not clean properly.

Resolution:

Fixed was added. There are no more errors during customer map transactions.

BTOBIEXEC-26309 01123465

[DOC] JMX monitoring needs to be enabled in SSL mode

Updated documentation to include the procedure for allowing remote access to the JMX statistics using an SSL connection.

BTOBIEXEC-26307 01110328

Update from 2.5 to 2.6 not working

Issue:

When started in graphical mode, B2Bi upgrade did not work correctly if ConfigureB2Bi.exe was last ran without port range configuration.

Resolution:

The limitation is removed. You can now edit the Number of porter pool ports field.

BTOBIEXEC-26296

01111287

01132167

Agreement name is not populating for events in Sentinel

Issue:

Outbound agreement name is not populating when copying message events in Sentinel.

Resolution:

Message copying is now enabled by default for outbound agreements.

BTOBIEXEC-26278 01044598

Missing sequence numbers marked as SEQUENCING PLACEHOLDER in queue

Issue:

The queue_util.x4 command line tool was not ignoring placeholders like SEQUENCING PLACEHOLDER, thus generating wrong statistics.

Resolution:

The queue_util.x4 command line tool now ignores sequencing placeholders in order to produce correct statistics.

BTOBIEXEC-26194

01099103

01130386

SFTP embedded server: ls .. exposes all user names

Issue:

The embedded SFTP server exposes all user names when a logged SFTP user executes ls .. from its root folder.

Resolution:

The SFTP embedded server will no longer expose other user names when a logged SFTP user executes ls .. from its root folder.

BTOBIEXEC-26193 01051659

Cannot select application delivery for service after 10 outputs

Issue:

We can only select an application delivery for the first 10 outputs. The drop-down list is disabled for the remaining outputs.

Resolution:

We can select an application delivery for all the outputs for a service with more than 10 outputs.

BTOBIEXEC-26189

01123749

01123280

Homepage slow to display - and slower over time

Issue:

When a B2Bi user clicks the homepage, the server refreshes the TODOs and alerts for all logged-in users, delaying the display of the homepage.

Resolution:

The homepage refreshes the TODOs and alerts only for the requesting user, leaving the refresh for all users to be done by the ToDoManager.

BTOBIEXEC-26005 01062061

Polled exchange point error: Violation of PRIMARY KEY constraint 'PK__PollResultActivi__284DF453'. Cannot insert duplicate key in object 'dbo.PollResultActivity'.

Issue:

Polling multiple files with the same name but different capitalization does not work, and no file can be polled. The duplicate files need to be renamed before the polling can continue.

Resolution:

Files with duplicate names are ignored during the polling action, and the polling is able to process all the other files that have different names. The files with duplicate names will be polled in a future polling cycle, after the system processes the files with the same name that were already polled.

BTOBIEXEC-26000 00930280

[DOC] MapProxyDeployerTool: password in clear

Updated documentation to reflect the new syntax for the commands in the mapProxyDeveloper tool.

BTOBIEXEC-25965 01102292

SSL-enabled Multi instance MQ does not switch to standby server

Issue:

The MQ Multi-instance queue manager, allowing for the usage of a standby server, was not working for MQ clients configured with SSL.

Resolution:

The MQ Multi-instance queue manager configured with a standby server is now working for MQ clients with SSL enabled.

BTOBIEXEC-25952 01097852

Config Server not reachable : crash when accepted connection exceeds the limit value

Issue:

Config server becomes unreachable when there are many connections.

Resolution:

Fixed a crash in the cfgserver process when there were many connections.

HME configuration change notification would leak socket connection in the cfgserver process in case of failure.

BTOBIEXEC-25941 01126330

Impossible to delete the application pickup trigger from UI

Issue:

Impossible to delete the application pickup trigger from the UI.

Resolution:

Fixed two bugs that kept trigger MBC HMEs from stopping normally.

BTOBIEXEC-25912 01125896

Picking up files from embedded SFTP server is not showing the correct event filenames

Issue:

For messages delivered to a No packaging SFTP embedded partner delivery, if users connect with an external client to get their files, the Downloading, Downloaded and Deleted events are not published to te_events.log.

Resolution:

The query for obtaining the message for files has been corrected.

BTOBIEXEC-25900 01118657

[REST API] ComponentBean.configurations-property does not show correct path while creating a component

Issue:

When running a POST or a PUT query on the ComponentResource (/v1/components), the response bean generates a wrong URL for the configurations of the component.

Resolution:

When running a POST or a PUT query on the ComponentResource (/v1/components), the response bean generates the right URL for the configurations of the component.

BTOBIEXEC-25882

01144228

01057300

01057309

Queue monitor crashes when trying to open an entry

Issue:

Queue monitor crashes when trying to open an entry.

Resolution:

Fixed crash in tsclient.exe when opening Queue Monitor.

BTOBIEXEC-25870

01102009

01071718

01089838

Errors during startup after upgrade: "No metadata was found for type "class com.cyclonecommerce.
collaboration.events.MessageSnapshot". The class is not enhanced."

Issue:

The event purge service was unable to delete the events containing references to non-database entity classes.

Resolution:

The code has been updated to allow purging of events that contain references to non-database entity classes.

BTOBIEXEC-25794

01096155

01113507

01099163

mapProxyDeployerTool: password in clear

Issue:

When using the mapProxyDeployer tool, the user and the password are entered in clear in the command line.

Resolution:

The logic of the tool was changed so that only the command [with parameters] is given in the command line. The user is prompted for the username and password, masking the password.

To enable the old usage (for automation purposes), a new property must be set in tuning.properties, secureMapProxyDeployerTool. This property defaults to true.

BTOBIEXEC-25770 01102292

The solution implemented for MQ header override does not provide the dynamic override of the header

Issue:

Context Identity headers for MQ outbound messages were accessible to the user only as static values configurable in the delivery settings.

Resolution:

The user is able to pass custom MQ headers in message attributes, which are later added on the outbound transport message sent by B2Bi.

BTOBIEXEC-25696 01091196

B2Bi RosettaNet - Attachment file name in Content-Id field

Issue:

In case of a received RosettaNet 2.0 message with attachments, the attachment name was taken from Content-Type:name Header and sent to Integrator using the wsAttachmentName attribute.

Resolution:

A new attribute, wsAttachmentFileName, is sent to Integrator, having the value read from the Content-Id header.

BTOBIEXEC-25681 01120542

Disabling concurrent browser sessions is not working for ADMIN user

Issue:

Disabling concurrent browser sessions for a user was not working for the ADMIN user.

Resolution:

Disabling concurrent browser sessions for a user now works for the ADMIN user as well.

BTOBIEXEC-25669 01122047

PeSIT SSL transfer fails randomly to specific B2Bi node

Issue:

PeSIT SSL transfers from external customers to B2Bi failed with the TIMEOUT WHILE WAITING NETWORK TO GET READY error, because the initial value of the protocol timeout was 5 seconds.

Resolution:

The initial value of the PeSIT protocol timeout is now the value provided in the Protocol timeout (seconds) field, which can be modified in the server settings page.

BTOBIEXEC-25667 01102095

RosettaNet Inbound 3B12 Request is identified as Response

Issue:

RosettaNet Inbound 3B12 Request is identified as Response.

Resolution:

Provided support for skipping the parsing of RequestingDocumentIdentifier from an inbound RosettaNet message.

This new behavior can be enabled on a community trading pickup by adding the fixed message attribute IgnoreRequestingDocumentIdentifier with the value true.

BTOBIEXEC-25666 01111834

B2Bi HTTP post and content-type value: prevent add inbound filename into the content type?

Issue:

The name attribute was always added to the Content-Type header for messages sent over HTTP no packaging.

Resolution:

The name can be excluded from the Content-Type using the tuning property http.headers.
excludeNameFromContentType=true
. This only works for HTTP no packaging. Other business protocols using HTTP, such as AS2, are not impacted.

BTOBIEXEC-25659 01118355

Wrong message crashes HME3 tasks

Issue:

The code reached a state were an uninitialized variable was used, causing a crash.

Resolution:

Initialized the variable.

BTOBIEXEC-25611 01053582

RCA Integrator Transfer Queue: Integrator Transfer Queue has reached

Issue:

The following error is returned on the TE node: "Integrator Transfer Queue: Integrator Transfer Queue has reached max capacity b2bi.integrator.transferqueue.max.size".

Resolution:

Integrator can now create a larger number of client connections (SOCKET.CONNECT, FILERD.CONNECT, logger, queue, table and others) on recent operating systems, including all versions of Linux kernel. This fix works properly when the client connections are distributed among several destination ports (it would not help a lot in the case of the archiver problem described below).

Connections from Integrator to Interchange used to send messages were disconnected after 5 seconds during which there was no message to send. The new option, Idle connection timeout sending to Interchange, is now tunable in System Profile Manager, and defaults to 60 seconds. These connections may also be closed from Interchange (Processing configuration> > Configure global processing settings), and the read timeout can be tuned accordingly. This is done to avoid having many TIME_WAIT connections during times of variable message throughput.

Fixed a bug in the archiver. When the filer returned an error for a particular request (for example, because the filer file was deleted), it was treated as a protocol error and the filer connection was broken. In case of many errors, this could result in local TCP/IP port exhaustion, bringing down the machine.

BTOBIEXEC-25598 01106176

CORE_DML_NO_EXTRA_SPACES not working

Issue:

B2Bi Integration Engine does not respond to the
CORE_DML_NO_EXTRA_SPACES configuration variable.

Resolution:

Backported Integrator v3.7.3 behavior.

BTOBIEXEC-25574

01119790

01118065

01119663

Self-signed certificate "Subject alt name" designated as critical could not be used by Interchange B2Bi

Issue:

Certificates with a "Subject alt name" extension as critical cannot be imported in B2Bi, because this is not an unacceptable critical extension for B2Bi Interchange. The full log error entry for this particular extension is "Unhandled CRITICAL extension: OBJECT ID = subjectAltName".

Resolution:

B2Bi certificate validation skips the subjectAltName errors for certificates with critical extension for subjectAltName, allowing such certificates to be imported in B2Bi.

BTOBIEXEC-25564 01119171

Unable to import user certificates when Certificate CA X509v3 Basic Constraints: CA:FALSE

Issue:

Invalid CA certificate having the CA:FALSE extension and end-user certificates issued by such CA could not be used by Interchange B2Bi.

Resolution:

The user can force the Interchange B2Bi certificate validation to skip the CA:FALSE errors for invalid CA certificates, making such certificates and their related end-user certificates operational and valid, both in UI and when used by the trading engine.

BTOBIEXEC-25560 01107490

[XIB MIGRATION] HTTP(S) override User Headers

Issue:

HTTP headers for inbound and outbound messages were not accessible to the user.

Resolution:

The user is able to pass custom HTTP headers in a message attribute, which is later added on the outbound transport message sent by B2Bi.

The user is able to see the HTTP headers of an inbound HTTP transport message received by B2Bi, using a message attribute.

BTOBIEXEC-25557 01100612

Peer message failing when importing partner through autoclone

Issue:

When the system is set up with Peer networking to automatically replicate new partners, importing a new partner profile to the system results in failed peer messages to the peer partners, although the profile is imported successfully.

Resolution:

Fixed. When the system is set up with Peer networking to automatically replicate new partners, importing a new partner profile to the system will clone the partner to peers.

BTOBIEXEC-25554 01103432

BinaryCollaborationBuilder alteration to select specific certificate based on partner

Issue:

Partner certificates cannot be overridden at runtime.

Resolution:

Partner certificates can be overridden at runtime using the DeliverySigningCertId, ReceiptSigningCertId and DeliveryEncryptionCertId attributes.

BTOBIEXEC-25501 01113192

REST API: get wrong message status when message fails into Integration

Issue:

The status of the message that is shown in the API response is not the same as the one in the UI.

Resolution:

The API response and the UI show the same message status.

BTOBIEXEC-25494 01117281

XML Classifier component does not expose the operands

Issue:

Java classifiers from Integrator standalone do not work in B2Bi/CIP.

Resolution:

XMLClassifiers, FinClassifier, and XPathClassifier were modified to work in B2Bi/CIP. Added support in DevelopmentKit and Bootstrap to help in the creation of other classifiers.

Note about XMLClassifier:

If the order of the evaluation is important, then we still cannot add two XMLClassifier components in the same Class Anchor activity. To handle that case, you need to add an XMLClassifier as the first component of Class Anchor, and a FileContentsClassifier as the "else" component (match "." as regexp). If needed, the output of the FileContentsClassifier can be redirected in other Class Anchor activity containing a different XMLClassifier and another "else" component of type FileContentsClassifier. If the order of classifiers evaluation is not important, then two FileContentClassifier components can be added in the same Class Anchor activity.

BTOBIEXEC-25471 01116528

Error installing B2Bi: failed to add system porter task to configuration

Issue:

The following error is returned: Error installing B2Bi: Failed to add system porter task to configuration.

Resolution:

Allowing more than 1300 porter pool ports on the first installation; the new limit is 3580.

BTOBIEXEC-25431 01115270

Peer network update for trading partner results in loss of collaboration setting configuration on peer node in specific scenario

Issue:

If a partner delivery specialization is configured in collaboration settings for a community, cloning the related partner with Peer-Network could delete the delivery specialization on the other B2Bi peer.

Resolution:

Cloning partners via Peer-Network will no longer delete partner delivery specializations defined on the collaboration settings of communities where the partners are subscribed.

BTOBIEXEC-25418 01104227

User list not available in UI

Issue:

The Manage users page does not display any users nor full name and email address from UI user's own account in case database errors occur in session management classes (for example, "Connection timed out (Read failed).").

Resolution:

The logic in the session management classes has been updated in order to properly handle error conditions.

BTOBIEXEC-25415

01065274

01082072

01051105

01114880

OOM issue on CN node after upgrade

Issue:

An Out Of Memory issue and wizard timeout appears when trying to upload a CSOS certificate with an incorrect DEA number, as all system certificates were loaded in memory.

Resolution:

Improved performance of the code that handles the situation where CSOS certificates do not match the DEA number by only loading the related certificates.

BTOBIEXEC-25409

01107664

01103292

01104460

SFTP key exchange option to disable - Vulnerability

Issue:

Two unsecure key exchanges (diffie-hellman-group1-sha1 and diffie-hellman-group14-sha1) are enabled for SFTP.

Resolution:

The two unsecure key exchanges are disabled by default. If the user wants to use one or both of these keys, the key exchanges should be added to the corresponding system property (ssh.unsecured.dh.key.exchanges).

BTOBIEXEC-25371 01050639

UI /help accessible without logging in

Issue:

The help static pages are accessible without authentication.

Resolution:

The help pages are accessible in the same authenticated session (including Help for this page) from <hostname>:<port>/ui/help/.

BTOBIEXEC-25369 01060199

Status not updated in Sentinel

Issue:

When B2Bi receives a message and has on hard-coded partners as the sender/receiver on a trading pickup, the direction of the message is "External".

There is no Sentinel state for rejected messages with this specific direction, thus the event is not sent to Sentinel.

Resolution:

Added new Sentinel state for rejected messages with the "External" direction.

BTOBIEXEC-25367 01105110

Unable to view payload when "Restrict viewing to selected partners" is assigned

Issue:

The "Restrict viewing/management for communities and partners" rights were taken into consideration when allowing users to view payload.

Resolution:

The following rights are taken into consideration:

  • "Restrict searching to communities and partners" when searching for messages
  • "View payloads and backups" when viewing a message
BTOBIEXEC-25332

01090064

01154332

Directory Indexing Vulnerability

Issue:

Directory Indexing Vulnerability was present in B2Bi UI. When an incorrect URL was used for help or other pages, B2Bi would list the directory contents.

Resolution:

Directory listing is no longer allowed in B2Bi.

BTOBIEXEC-24819 01083813

OFTP2 polled message received processed with incorrect OFTP protocol version

Issue:

A polling OFTP V2 exchange point may not work correctly if other server exchange points of type OFTP V1 and V2 are defined on the same community.

Resolution:

A polling OFTP V2 exchange point works correctly even if there are multiple other server exchange points of type OFTP V1 and V2 defined on the same community.

BTOBIEXEC-24817

01087472

01094594

Messages stuck in different CIP queues

Issue:

Some messages are stuck in different CIP queues.

Resolution:

Fixes in the INHOUSE enveloper example and the default INHOUSE:

  • fixed race condition that could cause data loss and other problems
  • fixed the issue that caused the enveloper to be interrupted during enveloping by HME stop, thus losing data
  • added a warning comment about envelopers and global variables

Fixed a number of race conditions in the VDA enveloper.

BTOBIEXEC-24711

01101788

01101070

Unexpected state: Run-time starter is in shut-down state

Issue:

When one of the procengine was blocked or suspended, Integrator stopped with the following warning: Unexpected state: Run-time starter is in shut-down state.

Resolution:

Integrator starter was beginning the start process before a previous request for shutdown, which included the restart of core services, had been completed.

To fix this issue, the first request for shutdown must be completed before continuing with the request for start.

BTOBIEXEC-24700

00983895

01053648

AS2-From id - different behavior in B2Bi 2.3.1 compared to 2.1

Issue:

The messages processed using the AS2 protocol in B2Bi 2.3.1 had the "Http Restart Query Header0" filled with the value determined on the collaboration settings, even if the sender routing ID was not explicitly overwritten.

Resolution:

The "Http Restart Query Header0" is filled with the information provided by Integrator if the sender routing ID is not explicitly overwritten in the collaboration settings.

BTOBIEXEC-24699 01036959

Resending AS4 message causes receipt to fail

Issue:

When a failed AS4 message is resent, the receipt coming from the receiver fails on the sender side with the following error message: EBMS:0302 - InvalidReceipt - Receipts are configured to be unsigned, and the received Receipt does not contain copy of eb:UserMessage element.

Resolution:

When a failed AS4 message is resent, the receipt coming from the receiver is processed successfully.

BTOBIEXEC-24697 01052932

Changes in partner delivery don't trigger peer cloning consistently

Issue:

Changes in partner delivery don't trigger peer cloning consistently. It was reported that not all attributes of partner deliveries trigger the peer cloning on update. Changing Retries in the Advanced tab of an HTTPS partner delivery does trigger the peer cloning, but updating Connect timeout (seconds) on the same page does not trigger it.

Resolution:

The issue was fixed, and now changing any field from the Advanced tab of an HTTPS partner delivery will trigger a peer network partner cloning event.

BTOBIEXEC-24674 01104579

Errors in Control Node log

Issue:

When the flow is initiated using an Integrator pickup, the processing errors and warnings are not sent to Interchange anymore.

Resolution:

The errors and warnings are sent to Interchange, and they are visible in the UI.

BTOBIEXEC-24631

01095856

01092060

Users see "Access Denied" when viewing payload in Message tracker

Issue:

The View payload option in Message tracker does not work as expected with roles the View payloads and backups permission is selected. The error message returned is "Access Denied".

Resolution:

The View payload option is now working correctly with roles where the View payloads and backups permission is selected.

BTOBIEXEC-24624

01090064

01093543

01098205

01078869

01095970

01090985

Non-significant digits are included for the control of reals

Issue:

Zeros are included during control of real numbers, thus blocking the processing of a number with trailing zeros that exceed P.S format values in whole or decimal part of real number.

Resolution:

If padding or trailing are checked, zeros are cut if they exceed the P.S format. Otherwise, zeros are taken off.

BTOBIEXEC-24529 01084664

Remove references for agreements with addressing "ANY / ALL" from the Where used list of Messaging IDs

Issue:

Extra references for agreements with addressing ANY/ALL exist in the Where used list of messaging IDs, even though they are not used (explicitly or otherwise).

Resolution:

No agreements with ANY/ALL references are displayed in the Where used list of messaging IDs, except the messaging ID in question is either used explicitly or as "<PartnerName>[DEFAULT]" for the other party.

BTOBIEXEC-24475 01104119

MT103 message containing a slash after the code is rejected - error [SWI - 28000]

Issue:

MT103 messages containing a slash after the code are rejected.

Resolution:

Now messages are parsed without error, according to the map structure for code 50F.

BTOBIEXEC-24399 01096271

Cannot access tsclient

Issue:

Customer was sometimes not able to connect to tsclient.

Resolution:

tsclient login and other REST API errors were suppressed. Also, the debug flag for these was sometimes lost.

BTOBIEXEC-24282 01051837

AS4 certificate agreement update doesn't work

Issue:

Creating an initial AS4 agreement between a community and a partner works fine. However, when trying to update the agreement, select a new signing/encryption certificate for the community and trigger a certificate update message to be sent to the partner, the following error message is returned: "Error validating the Agreement Update Request Message".

Resolution:

The solution was to change the schema location from "http://docs.oasis-open.org/ebcore/ebcore-au/v1.0/cs01/schema/ebcore-au-v1.0.xsd" to "http://docs.oasis-open.org/ebcore/ebcore-au/v1.0/cs01/schema/ebcore-au-v1.0.xsd" and "http://docs.oasis-open.org/ebcore/ebcore-au/v1.0/cs01/schema/ebcore-cu-v1.0.xsd" to "http://docs.oasis-open.org/ebcore/ns/CertificateUpdate/v1.0 ebcore-cu-v1.0.xsd". Also, a check for protocol compression was added: if the payload is compressed, it will be decompressed before validation against the schema.

BTOBIEXEC-24250

01101090

01101557

Client-side validation bypassed vulnerability

Issue:

When navigating to <hostname>:<port>/ui/webtrader/AddFolder and trying to rename the folder to "<script>alert(1)</script>", the application prevents you from doing so due to special characters. While trying to execute the same request to rename the folder by intercepting it in Burp suite, the customer is able to change it to the specified value.

Furthermore, the customer is able to change or set the name by navigating to <hostname>:<port>/ui/core/users/AddGroupAction.

Resolution:

Now the special characters will be excluded in order to prevent a security vulnerability, and the user will be able to set as password a string containing any printable character.

BTOBIEXEC-24206 01070306

Resource filter autofill issue with Chrome and Opera

Issue:

When selecting an element after filtering, two options remain with selected property on true. Some browsers consider the first option as selected, while others consider the last.

Resolution:

Only one of the options remains with selected property on true.

BTOBIEXEC-24138 01098406

Migrate MQ connections from XIB to B2Bi - location for filling the MQ header fields

Issue:

Missing support of the MQ header fields.

Resolution:

The fix consisted in allowing the user to change the way the context is passed.

A new section, Set context identity data, was added in the UI for all IBM MQSeries deliveries.

  • If this checkbox is not selected, MQOO_DEFAULT_CONTEXT will be used.
  • If this checkbox is selected, MQOO_SET_IDENTITY_CONTEXT will be used, and the user can select the desired values for the three fields:
    • Application identity data
    • Application origin data
    • Put application name

Four new fields have been added for the MqProducer bean:

  • setContextOptionEnabled - Default value = true.
  • appIdentityData - Default value = appIdData.
  • appOriginData - Default value = appOriginData.
  • putAppName - Default value = putAppName.

When running a POST or PUT call, if setContextOptionEnabled is set to false, the values for the other three fields will be ignored, and the defaults will be set.

BTOBIEXEC-24125 01091196

[Mapping Services] Datamapper compilation error

Issue:

Errors occur when simulating a Datamapper project.

Resolution:

Datamapper issues have been fixed.

BTOBIEXEC-24091 01096656

Datamapper simulator server error: "Connection to message processor simulator is broken..."

Issue:

The Datamapper simulator server returns the following error: "Connection to message processor simulator is broken..."

Resolution:

Added database interfaces, missing character set conversion modules and a default uniqueid file to B2Bi Client to enable local simulation of Datamapper maps who use them.

The Datamapper simulation crashed if Sentinel APIs were used in the map. Fixed.

BTOBIEXEC-24086 01096285

Messages stuck in HME1

Issue:

Messages seem stuck in HME1. Actually, these are some missing sequence numbers.

Resolution:

Missing sequence numbers are now marked as "SEQUENCING PLACEHOLDER" in Queue Monitor to prevent the user from mistaking them for real queue entries.

BTOBIEXEC-24074

01099103

01130386

Rosettanet 2.0 HTTP header folding

Issue:

Messages sent using RosettaNet 2.0 contain folding HTTP headers that are not allowed by Jetty version 9.4.11 server, which implements RFC7230 strictly.

Resolution:

Messages sent using RosettaNet 2.0 no longer contain folding HTTP headers.

BTOBIEXEC-24073 01095639

Default maximum number of alerts to be decreased to 100

Issue:

The default maximum number of alerts should not be higher than 100.

Resolution:

Reduced the default maximum number of alerts to 100, as all the duplicate filters (alertmonitor, HME, TA, TG) will not work if the maximum number of alerts is higher, filling the alerter with duplicate data.

This maximum number is now also tunable through the CORE_ALERTER_MAX_ALERTS environment variable.

If the number of alerts is at least half the maximum, and an alert with the same code, severity and type as the one being written already exists in the list, the alert is not written to the disk and is not reported to monitoring clients to avoid killing performance. When this happens, a WARNING is written to the trace.

BTOBIEXEC-24039 01099201

Deleting MessagingID doesn't delete the RoutingId

Issue:

The routing ID was not removed when the corresponding messaging ID was deleted.

Resolution:

The routing ID is removed when the corresponding messaging ID is deleted.

BTOBIEXEC-23984 01094090

B2Bi 2.5 Import/replace service doesn't work correctly

Issue:

When importing a document service in B2Bi UI using the Replace option, the DocumentType of the service is not updated.

Resolution:

When importing a document service in B2Bi Ui using the Replace option, all the information related to the service is updated.

BTOBIEXEC-23928 01090231

Wrong error handling when DMCompiler.x4 fails with the "Errors were detected during compilation" error

Issue:

Wrong error handling when DMCompiler.x4 fails with the "Errors were detected during compilation" error - the errors cannot be located.

Resolution:

When compiling Datamapper projects, monitoring of and display of output of external commands (map generation and compilation) had some race conditions which were fixed.

BTOBIEXEC-23922 01095424

Issues when creating new internal users with SSO SAML user

Issue:

Log in with the SSO user and create an internal user. The internal user does not have an email address set.

Resolution:

The internal user has an email address set.

BTOBIEXEC-23848 01094104

Wrong error handling when the last XML tag is doubled

Issue:

For the first map in a flow with two maps, the second end tag is not treated as error.

Resolution:

Now the error is identified in the first map, as it should be.

BTOBIEXEC-23843 01065213

XML parser differs depending on the DML version used

Issue:

The XML parser returns an error when used with DML 2.1.

Resolution:

Now the XML parser can be used with DML 2.1.

BTOBIEXEC-23825 01072277

Message received successfully by partner but Message tracker shows it as failed in B2Bi

Issue:

Some messages are reported as failed in Message tracker and Message Log, but the receiving partner has confirmed that they have actually received the messages. The problem was generated when the advanced search information related to the messages delivered to multiple endpoints was saved in the database, and was caused by the undersized column length and some database transaction errors.

Resolution:

The column type was changed to accommodate the information size, and the database transaction errors were solved.

BTOBIEXEC-23822 01063698

Failed to get reply from Sentinel: SENTINEL_CLIENTAPI.RECEIVEREPLY: error returned from sentinel client: 'Failed to set attribute 'CoreID' with value 'ci1567436928705.7023@b2b-server_te

The CORE_SENTINEL_MAX_ATTRIBUTE_SIZE environment variable can now be used to truncate attributes that cannot be sent to Sentinel verbatim. By default, this variable is now enabled and set to 3999 bytes. Zero means no limit.

Since patch ISENTINEL_203-01-08_HPUX11_ITANIUM64, errors setting Sentinel event attributes caused system-wide crashes. Fixed.

BTOBIEXEC-23694 01090270

ERROR [Worker29-16709] (EdifactParser.getAsciiInputStream:170) - UNA/B segment not found - causing monitoring alerts

Issue:

The warning triggered by some missing EDIFACT segments from the message was incorrectly logged as error.

Resolution:

The change in code was to lower the level of the message from an Error to a Warning because the parsing error was in fact ignored and the message delivered anyway. Also more information was added to the warning message so in case an EDIFACT parsing error is happening again, will be easier to diagnose.

BTOBIEXEC-23690 01084365

RCA: UI unavailable

Issue:

The user interface becomes unavailable when the authenticated user modifies a message attribute that contains invalid information.

Resolution:

The user interface continues to be available regardless of the errors that may appear during message attribute management.

BTOBIEXEC-23656 01035021

Cannot create a user role that gives read-only access in Integration Engine System Manager

Issue:

Cannot create a user role that gives read-only access in Integration Engine System Manager.

Resolution:

The Message Log permissions are now enforced.

The Message Log operations now behave as follows, for both new installations and upgrades:

  • Resend, Fail over resend, Mark as manually corrected - available for users with Message Log Admin or Grant user to resend messages permission
  • Edit before resend - available for users with either Admin or both Grant user to resend messages and Grant user to edit messages prior resend permissions
  • Inactivate entire flow, Import/Export favorite search - available for users with Message Log Admin permission
BTOBIEXEC-23559 01089820

TO parameter not set in header of email alerts generated by B2Bi

Issue:

The TO parameter was not set in the header of the email alerts.

Resolution:

The TO parameter is now set in the header of the email alerts.

BTOBIEXEC-23544 01086371

[DOC] 45GB+ compressed files fail in SFTP FIPS mode

Issue:

When FIPS is enabled, large files that are encrypted using Triple DES cannot be sent.

Resolution:

Documentation was updated to include the limitation for large files.

BTOBIEXEC-23522 01088318

Copilot unable to launch

Issue:

Copilot cannot be launched sometimes.

Resolution:

Sometimes (randomly or, on some Windows laptops and desktops, always), the libeay32.dll library would fail to load when opening Copilot. Copilot cannot start without this library.

Fixed when FIPS mode is not enabled. Otherwise, the error cannot be fixed currently.

BTOBIEXEC-23368 01080233

When using alternate delivery partner's routing ID in document agreement, AS2 TO ID is not correctly packaged in the outbound AS2 message

Issue:

The messages processed using the AS2 protocol in B2Bi 2.3.1 had the "Http Restart Query Header1" filled with the value determined on the collaboration settings, even if the receiver routing ID was not explicitly overwritten.

Resolution:

"Http Restart Query Header1" is filled with the information provided by Integrator if the receiver routing ID is not explicitly overwritten in the collaboration settings.

BTOBIEXEC-23346 01076420

Gi 5.12 SP13 to B2Bi 2.3.1 SP3 - upgrade stuck when database schema is being created

Issue:

During database upgrade, some queries took much time to complete, and triggered connection timeout errors.

Resolution:

The timeout parameter of the database connection parameter was increased during database upgrade phase.

BTOBIEXEC-23333 01043157

Peer Networking - cloning partners issues

Issue:

When adding, changing or deleting a trading pickup, many Peer Network messages are sent for cloning partner.

Resolution:

Code changes were made so that less Peer Network messages regarding partner profiles are sent. For example, when changing an embedded FTP/SFTP trading pickup, it sends the partner profiles of the partners who use this embedded server or have accounts in the trading pickup under Accounts owned by partners.

BTOBIEXEC-23174 01070718

Access to Logger Utility to certain role or group in B2Bi system - tsclient

Issue:

Access to the Logger Utility from System Manager is not possible.

Resolution:

Access to the Logger Utility from System Manager can now be granted to non-privileged users.

BTOBIEXEC-23133 01081245

Cannot set the debug in a document for a DML component

Issue:

When using a map and a document in a service, Interchange sends the true value when debug is enabled on the document, and Integrator expects the value 1 to further create the maploader.log file.

Resolution:

When debug is activated on a document, Interchange sends the value 1, and Integrator creates the maploader.log file.

BTOBIEXEC-23036 01079145

B2Bi 2.4 can't download file from external SFTP server

Issue:

B2Bi can't download files from the external SFTP server. This issue is caused by a different local/remote MD5 hash check for the same file. When this happens, B2Bi considers that the file may be corrupted.

Resolution:

A new option, Disable MD5 content validation, was added on the maintenance page for external SFTP consumer exchange points (application and trading pickups). The corresponding property in the RestAPI bean, disableMD5Validation, is set by default to false.

BTOBIEXEC-22897 01077957

Cannot view partner and community attributes

Issue:

User having the View trading configuration and View partners configuration roles cannot see any defined partner and community attributes templates.

Resolution:

The defined partner and community attributes templates are visible to users that have only the View trading configuration and View partners configuration roles. The attributes templates fields are disabled if the user does not have the roles to manage trading/partner configuration.

BTOBIEXEC-21739 01060166

Using procmbc_example_huge_splitter.s4 in B2Bi

Issue:

Using procmbc_example_huge_splitter.s4 in B2Bi DIP returns the following error. "The message has no activity branch. Unable to queue message for further activity."

Resolution:

The huge splitter example now recognizes zip files received from Interchange or from the File Connector.

The huge splitter can now be used in the B2Bi DIP; when run in this mode, it now performs recursive expansion of zip files.

BTOBIEXEC-21118 01046245

[DOC] Cannot create new Java instance after call to JAVA.DestroyJvm

Documentation was updated

BTOBIEXEC-19830 01027796

Float numbers with (m,e) pattern padded incorrectly

Issue:

Floats format is invalid with respect to "Pad reals with a leading and trailing zero".

Resolution:

Pad floats accordingly.

BTOBIEXEC-19712 01024001

Old version of containers still deployed, causing delay at startup

Issue:

When many old version containers are added in the autodeploy folder, the deployment process is slowed down significantly because of the errors caused by these old containers. To remove them, customers need to identify and remove them one by one.

Resolution:

A LIST_OLD command was added in the mapProxyDeployer tool for faster identification of the old containers.

A CLEAN_OLD command was added in the mapProxyDeployer tool for faster/bulk removal of the old containers.

BTOBIEXEC-18973 01006415

Support for X509PKIPathv1 not implemented

Issue:

When sending an AS4 message, the following message is returned: "PseCrypto.getX509Certificates is not implemented".

Resolution:

When sending an AS4 message, the message is delivered successfully.

BTOBIEXEC-18135 00999838

Standards Library

Description Internal ID Case ID

FSL:320VI: CodeDevise EUR Norme CFONB

Issue:

CheckConstraint23 was verifying that currency is EUR on field 16.

Resolution:

This validation rule was changed to check EUR on field 12.

STAN-3721 1141304

Mapping CFBON320 to SEPA SCT

Issue:

The mapping rule on AddressLine was generating an error when the input field had 0 or less than 71 characters.

Resolution:

  • If the AddressLine field in input has 0 characters, then no XML tag is created in the output.
  • If the input contains 0 to 70 characters, then a single XML tag is created.
  • If the input contains 71 to 105 characters, then the first 70 characters are mapped in the first XML tag, and the rest are mapped to a second XML tag in the output file.
STAN-3788 1141304

FSL : [EXE - 16046]: Cannot set field "Error" of the attribute "PortalEnveloppe"

Documentation was updated to include the information related to the .s4h files where attributes need to be declared.

STAN-3789 1142121

Check constraint 23 in BDOC CFONB_320_VETR_11.bdoc not aligned with the CFONB 320 rules

Issue:

Check Constraint 23 was verifying field Entete2 and 4.

Resolution:

Check Constraint 23 was verifying field Entete3 and 4. Additionally, a versioning index has been created on each BDOC and on the CFONB map project itself.

STAN-3808 1142715

Field delimiter 0x0A truncated all "00000" for integer

Issue:

The delimiter was included in the last element of each block. As a consequence, the element did not have a fixed length.

Resolution:

The delimiter is included in the parent, so the last element of each block has a fixed length of 160 characters, as per standard specifications.

STAN-3818 1152441

CFONB 160 file accepted with ! character

Issue:

The CFONB 160 standard accepted the ! character as part of the received messages.

Resolution:

The ! character is no longer accepted on the CFONB 160 message.

STAN-3705 1120284

Mapping Services

Description Internal ID Case ID

Inconsistent versions in Mapping Services

Issue:

The Mapping Services displayed versions were inconsistently displayed throughout the product.

Resolution:

The versions have been updated to display the correct information.

MS-5219 01156898

UI problem: cannot change Properties > General > Description

Issue:

Erasing a character in the Properties > GeneralDescription section of a Datamapper map leads to duplicate information.

Resolution:

Characters can now be erased from the Properties > GeneralDescription section of a Datamapper map.

MS-1306 01105499

Integrating Mapping Services with ADFS SSO

Issue:

When B2Bi is integrated with an external IdP, external users could not be used to authenticate from Mapping Services.

Resolution:

A new option to authenticate with external users has been added, provided that B2Bi Server is integrated with an external IdP using OpenId Connect.

MS-1241 01009014

No control when the Datamapper map name exceeds 32 characters

Issue:

For Datamapper maps, if the total length of map names and project names exceeds 32 characters, the name is truncated during deployment.

Resolution:

The total length allowed for the map name and the project name has been increased to 64 characters.

MS-1223

01002483

01082885

Known issues and limitations

Issue or limitation Internal ID
(Case ID)

Datamapper simulation fails when using a B2Bi server upgraded from 2.6 to 2.6 SP1

Issue:

When starting a Datamapper simulation following the upgrade to B2Bi 2.6 SP1, an error related to the SSL connection is displayed, and the simulation does not start.

Workaround:

To change your permissions, run chmod 600 local/config/sysman/mandatory_ssl.pem in <B2Bi_Server_installation_directory>/Integrator.

BTOBIEXEC-28412

Intermittent issue: integration engine nodes do not start after auto-restart into Multi-Cluster

Issue:

Sometimes, following an auto-restart into Multi-Cluster, one or two integration engine nodes remain in Starting state and all tasks remain stopped.

Workaround:

Manually restart the trading engine nodes from the System management page.

BTOBIEXEC-28351

UI does not start on Chrome and Firefox for Passport Integrations

The B2Bi UI does not start on Google Chrome and Firefox for Passport Integrations. This is only supported on Microsoft Edge and Internet Explorer.

BTOBIEXEC-28332

After running ConfigureB2Bi.exe, the Number of online archive tasks input field is disabled when online archiving is enabled

Even though the Enable online archive check box is selected, the Number of online archive tasks input field is disabled, and the value in the field cannot be manually changed.

BTOBIEXEC-28328

Agreement names displayed incorrectly in the UI

Agreement names are displayed both as links and as plain text in the UI.

BTOBIEXEC-28281

[Multi-Cluster] scheduleFullSync is accessing datastoreEncryptionKeys with incorrect relative path

The tool for triggering the full synchronization in a Multi-Cluster environment is not working due to a change in the folder location. In order to make it work, copy the entire datastoreEncryptionKeys folder from $CLUSTER_SHARE/common/conf/encryptionKeys/ to $LOCAL_FILE_SYSTEM/conf/.

BTOBIEXEC-28293

Multi-Cluster Second processing node does not start after upgrade from 2.6

To solve this issue, the user should re-encrypt the passwords of the keystore and truststore (used by Ignite) from agent.properties on the second node using the new datastoreEncryptionKeys from the shared file system.

BTOBIEXEC-27857

Inconsistent behavior for pluggable transports - when manually creating one and importing from a exported community as a partner profile

Pluggable exchange points defined on a community that are exported as partner profile are not correctly imported.

BTOBIEXEC-24285

JSON map in Mapping Services

JSON BDOC type is not supported in the current version of Mapping Services.

MS-1296

TLS/SSL protocol setting available in the UI for specific protocols

The protocols for the HTTPS user interface connection and for all the embedded HTTPS servers can no longer be set from the tuning.properties file. Only the UI can be used for these connection types.

BTOBIEXEC-24803

TLS 1.3 availability

Although available for all the HTTPS protocols in Axway B2Bi, TLS 1.3 is validated and can be used only for HTTPS - No packaging and AS2 embedded servers.

TLS 1.3 support for other protocols will be added in future Service Packs and releases.

BTOBIEXEC-24803

TLS 1.3 not enabled by default in case of upgrade

In order to preserve the existing behavior, the following limitations apply in case of upgrade to B2Bi 2.6 SP1:

  • If the Override SSL and TLS cipher suite option was enabled and any ciphers were selected in the previous B2Bi version, after the upgrade these settings are maintained, but only TLS 1.2 is selected by default. TLS 1.3 can be added manually.
  • TLS 1.3 cannot be set if the UI connection is configured with Secure Relay through DMZ with the Enable security termination option.
  • For HTTPS embedded servers, only TLS 1.2 is selected by default. TLS 1.3 can be added manually.
BTOBIEXEC-25496

AS4 certificate agreements duplicates

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

BTOBIEXEC-25566

[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

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

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

B2Bi in FIPS mode not available with PassPort integration

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

BTOBIEXEC-24481

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 Troubleshoot unexpected trading engine restarts

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.

 
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).

 
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.

 

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.
 

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 SP1:

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

 

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 Troubleshoot unexpected trading engine restarts

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