B2Bi 2.3.1 Release Notes

Document version: October 12, 2017

Caution   Do not start B2Bi 2.3.1 until you have installed B2Bi Patch 1. This patch must be installed after the B2Bi 2.3.1 installation and before B2Bi 2.3.1 is started.

Product version requirements

B2Bi 2.3.1 operates with the following product versions:

Axway product Version
B2Bi Client 2.3.1
Mapping Services 3.3.1
GDHA WebTrader

2.4.1

(and newer)

Note   The GDHA WebTrader option is in RA (Restricted Availability) status as part of the B2Bi 2.3.1 release. The standard WebTrader is in GA (General Availability) status, included with the B2Bi 2.3.1 release.

 

The following Standards Libraries are included in B2Bi 2.3.1:

Standards Library Version
Core EDI 1.6.0
Extended B2B 1.5.0
Financial 3.4.0

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

Axway product Version
PassPort 4.6.0

Sentinel

4.2.0
Transfer CFT 3.2.4

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

New features and enhancements

CSOS feature

B2Bi 2.3.1 now includes an updated version of the optional Controlled Substances Ordering System (CSOS) feature. This CSOS feature update (from CSOS Interchange 5.12) includes the following changes:

Note   The B2Bi CSOS feature is a licensable option.
  • Includes a new and separate role-based permission that controls the CSOS user’s ability to update existing (past) CSOS orders. This is separate from the existing permission to approve pending CSOS orders. Both of these permissions are supported for internal and external (such as SSO enabled) users. See the Axway B2Bi Administrators Guide for more details.
  • Improved CSOS Order (EDI 850) to CSOS PO Acknowledgement (EDI 855) linking for Buyer side and Supplier side CSOS servers. The default linking logic has been updated to support all traditional DEA NDC encoding values and is now also configurable. For additional details, see BTOBIEXEC-6085. For assistance, contact Axway support.axway.com.
  • Improved CSOS Buyer side order updating and audit tracking, allowing line item updates for each matching PO Acknowledgement received. Also, this version allows Buyer ad-hoc side updates to line items to track other changes to the CSOS order line items.
  • Improved CSOS Supplier side CSOS schedule validation matching the order requested schedules to the DEA certificate used to authorize the order; the default schedule validation logic is now also configurable. For additional details, see BTOBIEXEC-7329. For assistance, contact support.axway.com.

CSOS certification

Axway B2Bi Version 2.3 has successfully passed the audit requirements as established by the U.S. DEA for a Drummond Certified™ Controlled Substances Ordering System (CSOS). With this certification, Axway reinforces its commitment to delivering compliant and interoperable solutions that are easy to implement and integrate. Axway B2Bi for CSOS extends Axway’s leadership in this market.

SHA2-MAC algorithms support

B2Bi now supports SHA2 with HMAC data integrity algorithms (hmac-sha2-256, hmac-sha2-512) for SFTP exchanges. As with other algorithms, it is possible to control/override SSH algorithms for encryption for outgoing transfers and B2Bi accepts SHA2-HMAC algorithms for incoming exchanges.

Elliptic Curve Cryptography support for TLS / SSL connections

B2Bi now supports ECDSA based cipher suites for TLS / SSL connections. This feature makes it possible to use the cipher suites offering forward secrecy (Elliptic Curve Cryptography) to secure transmissions.

Certificates with ECDSA keys can be used for SSL/TLS connections only; although, not used for payload signing and encryption.

Note   Generating a self-signed certificate with ECDSA key is currently not supported.

SSH/SFTP protocol with ECDSA key algorithm

B2Bi now supports SSH/SFTP protocol with ECDSA keys. The supported curves include NIST P256, NIST P384, and NIST P521 .

Message format and version support

B2Bi provides support for the creation and exchange of the following additional message formats and /or versions:

  • EDIFACT D16B
  • X12 7040
  • X12 Railroad (AAR) 7040

Integration Services

Several new enhancements have been added to Integration Services:

  • It is now possible to define and use global runtime objects for integrations developed and maintained in the Integration Services interface hosted on the server side - in line with the functionality provided in the Integration Services interface provided on the client side. The ability to reuse and share system resources ensures more efficient message processing in B2Bi at a lower footprint.
  • Integrations can now be managed at the server side. This is useful when the maintenance of flows is shared between multiple members of a team.
  • All deployed integrations now have a date stamp and origination identification, which is stored in the workspace for the project as well. This makes it easier to match development changes to runtime impact.

ENTSOG (AS4) compliance

The Drummond Certified AS4 solution in B2Bi 2.3.1 is now also compliant with the ENTSOG profile - as published in Q4 2016.

GCM Encryption (AS4)

For the exchange of AS/4 messages (inbound and outbound), B2Bi now supports the use of GCM encryption (AES/GCM- 128-bit, AES/GCM - 192-bit, AES/GCM - 256-bit)

Prevent storage of clear-text data

B2Bi now supports the ability to prevent the storage of (non-encrypted) backups of messages processed through the system for SFTP based exchanges. This is an optional behavior which can be activated per SFTP exchange point definition. Additional protocols are planned for future updates.

RosettaNet

B2Bi users can now leverage additional RosettaNet features, including the processing of message exchanges, as defined in PIPs. Each PIP specification provides a document type definition (DTD) file and a message guideline document. The DTD file defines the service-content message structure. The message-guideline document, which is a human-readable HTML file, specifies element-level constraints. Together, they provide a complete definition of the business process. Enhancements in this area include:

  • Single-action (one-way PIP) and two-action (two- way PIP) that provides asynchronous activity exchange patterns used by B2Bi in the RNIF 2.0.
  • The Notification of Failure (NoF) used to handle failure when it is possible that the other trading partner is not executing the PIP (for example, has not started processing or has already completed processing).
  • The Non-Repudiation mechanism that allows B2Bi to ascertain the integrity and origin of a RosettaNet 2.0 business message that is transmitted and received from the trading partner.

See the Axway B2Bi Administrators Guide for details.

Peer Networking

B2Bi now has a shared secret for peer networking.


Fixed problems

Case ID Internal ID Description
00822957 BTOBIEXEC-2386

Upgrade from 5.10.1 - Passport Integration breaks

Issue: Upgrading from Interchange 5.10.1 to higher versions when PassPort integration was enabled was not working without manual configuration.

Resolution: The upgrade finishes correctly and the product can be used without any manual intervention during configuration.

00852435 BTOBIEXEC-3783

Cannot login to B2Bi Server Manager with long password

Issue: The Interchange UI allows the user password to be set for maximum length of 50 characters. While trying to login to system manager (tsclient) users with longer passwords receive an invalid login error.

Resolution: The user can now successfully login with the set password length of up to 50 characters.

00885090 BTOBIEXEC-4020

B2Bi unzip does not work for gzipFixed

Issue: The JMC jar integration was not working as designed.

Resolution: The JMC jar integration/registration with Integration Services client tool is fixed. Also, a procedure on how to use the B2Bi Unzip resource is added to the B2Bi 2.3.1 Administrator Guide.

00884396 BTOBIEXEC-4066

Cloning trading partners, Select All button

Issue: When cloning trading partners, Select All only selects partners on the current page.

Resolution: Additional radio buttons have been added. Clone All clones all available partners and Clone selected clones only the selected ones.

00888588 BTOBIEXEC-4206

Manage Connection jdbc url limitation of max length 128

Issue: When a JDBC connection was made, the limit for the URL field was 128 characters.

Resolution: Now, when JDBC connection is made, the limit for the URL field is 2048 characters (the same as for the "Value" column of the "ApplicationConnectParameters" table).

00888712 BTOBIEXEC-4227

Search functionality by RoutingID no longer available

Issue: In Message Tracker (Message Handler Rules, Exchanges Points, and so on), for each From, To, or Pick Party button, there is no longer the option to search via the RoutingId.

Resolution: In Message Tracker, for each From, To, or Pick Party button, you can, once again, search via the RoutingId.

00869277 BTOBIEXEC-4422

POST request can be replaced with GET and will modify the db

Issue: A POST request can be replaced with GET and will modify the db interchange wide.

Resolution: If a GET request should only be a POST, the GET is rejected with a notification.

00875205 BTOBIEXEC-4592

Save changes on WebTrader user role page removes view permission

Issue: For WebTrader classic, role settings can be edited. Once modified, the role was losing the ui:webtraderuser.view permission.

Resolution: The WebTrader roles no longer lose the ui:webtraderuser.view permission when modified.

00894142 BTOBIEXEC-5059

Error after importing dtd - extra fields causing issues

Issue: Errors occurred when a dtd was imported.

Resolution: Multiple changes were made to the DTD Importer and the XSD Schema importer to properly handle cxml dtd files.

00895274 BTOBIEXEC-5155

The porter.mem not recreated when corrupted

Issue: The porter.mem was not recreated if corrupted.

Resolution: The porter.mem is now reinitialized if a corruption occurs.

00894870, 00886265 BTOBIEXEC-5512

Cross-Site Request Forgery (CSRF) vulnerability

Issue: A CSRF vulnerability was reported.

Resolution: The vulnerability was fixed with the changes completed for BTOBIEXEC-4422 and now all POST requests send the OWASP_CSRF_TOKEN.

00888925 BTOBIEXEC-5519

Tail.exe is not compatible with Windows

Issue: The tail.exe, delivered with B2Bi by default, is not compatible with the supported version of Windows.

Resolution: Tail.exe is now compatible with the supported Windows platform.

00869332 BTOBIEXEC-5619

Number of retries for HTTP send

Issue: The number of retries performed by Integrator for HTTP send not only trigger when the HTTP Server is not available but also when specific error responses occur.

Resolution: Retries are no longer made for specific HTTP codes. Also, no retries are executed even if there are retries left.

00890415 BTOBIEXEC-5760

Peer Network WebTrader user certificate not submitted

Issue: If a WebTrader partner was created with the self registration user, its certificate was not part of the peer network profile export sent to the connected peers.

Resolution: When a WebTrader partner is created with the self registration wizard, its certificate is also automatically cloned to all defined peer network partners.

00887027 BTOBIEXEC-5829

Output file name (.xml) changed in Integrator

Issue: When the filename contains the pattern ".xml" in the middle of the file, B2Bi removes the ".xml".

Resolution: Now, the delivery file name is the same as the original file name, even when it contains ".xml".

00890211 BTOBIEXEC-6085 Improve CSOS E222 display and 850-855 EDI linking

Issue: After a valid transfer of 850 order and 855 order approval, when viewing the sent files in message tracker, you would see wrong values for NDC and UPC codes of an item if the codes would be placed somewhere other than the expected one in an item row. For the 855 order approval, if a product would have a substitute, the codes would not be linked correctly.

Resolution: Now, the codes are shown correctly for each item not dependent of where they are placed in the product item row of the 850/855 file and when a substitute is given it is correctly shown with codes. The following system properties are added to allow tuning of the xpaths where the NDC value is taken from:

  • csos.xpath.850.ndc - default value is: segment/element[@code=235 and (value='N1' or value='N2' or value='N3' or value='N4' or value='ND')]/following-sibling::element[@code=234 and 1]/value
  • csos.xpath.855.po.ndc - default value is: loop[@code='ACK']/preceding-sibling::segment[@code='PO1']/element[@code=235 and (value='N1' or value='N2' or value='N3' or value='N4' or value='ND')]/following-sibling::element[1]/value
  • csos.xpath.855.ack.ndc - default value is: loop[@code='ACK']/segment[@code='ACK']/element[@code=235 and (value='N1' or value='N2' or value='N3' or value='N4' or value='ND')]/following-sibling::element[1]/value

Do not modify these xpath values. For assistance, contact support.axway.com.

00841889 BTOBIEXEC-6255

Vulnerability: Sensitive Information in GET Parameters

Issue: In several URLs the user ID was passed as a parameter (for example, xxx?userId=billy), presenting a possible security issue.

Resolution: The user ID has been replaced by userOID in the URL, which is an internally-generated value (for example, XXX?userOID=163895).

00904677 BTOBIEXEC-6272

Vulnerability: "Cross-Site Scripting: Reflected" while using B2Bi Admin UI

Issue: Some pages were vulnerable to XSS, presenting a possible security issue.

Resolution: The XSS vulnerable reported pages are now fixed.

00800251 BTOBIEXEC-6342

Vulnerability: Sensitive information in URLs

Issue: UserID was accessible in various URLs, presenting a possible security issue.

Resolution: The UserID is no longer accessible in URLs.

00905531 BTOBIEXEC-6389

Problems processing user names with spaces

Issue: When the username contained spaces, navigating to the "Change Password" page created an error.

Resolution: User names with spaces no longer generate errors when trying to change a password.

00851280, 00848070 BTOBIEXEC-6404

Failure to initialize a business document (related to a schema import)

Issue: The error reporting mechanism between DML compiler and DML components had a mismatch between function usages.

Resolution: Now, the mechanism properly returns the errors, and does not cause any crashes for Mapping Services.

00903699 BTOBIEXEC-6443

Unable to add multiple SFTP account using Swagger API in embedded SFTP Application pickup

Issue: Multiple SFTP and FTP users could not be added to Embedded SFTP/FTP application pickups using the Rest APIs.

Resolution: Multiple SFTP/FTP users can now be added to Embedded SFTP/FTP application pickups using the Rest APIs.

00903077 BTOBIEXEC-6601

Standard random number generators do not provide a sufficient amount of entropy

Issue: Security tests revealed two Insufficient Entropy problems caused by the use of the java Random class.

Resolution: Insufficient Entropy problems were removed by using java's SecureRandom class.

00891301 BTOBIEXEC-6603

Incomplete documentation on Web Services Trading Pickup

Issue: Documentation was missing the steps to setup and test a Web Services pickup exchange with any WSDL.

Resolution: Updated B2Bi Administrator Guide to add missing information regarding custom WSDL and WSDL2 files.

00877818 BTOBIEXEC-6620

Wrong in-house agreement used when multiple Receiver message identifiers are defined

Issue: A processing error occurred when a colon character (:) is used as a field separator.

Resolution: Added a note in the B2Bi Administrator Guide for the user to not use the colon character (:) as a field separator in messaging identifiers or detectors.

00903071 BTOBIEXEC-6627

Code quality issues

Issue: Code quality issues were identified within Interchange.

Resolution: The code quality issues within Interchange are resolved.

00903074 BTOBIEXEC-6666

Improper validation of certificate with host mismatch

Issue: If there was no private security information or truststore, a 'trust all' trustmanager was made.

Resolution: If there are no private security information or truststore, an exception is made instead of using a 'trust all' TrustManager.

00903067 BTOBIEXEC-6675

OS command injection vulnerability

Issue: A B2Bi user could configure post processing and error scripts in the UI to run scripts in unsecured locations.

Resolution: A new user permission is added to prevent users from configuring scripts. Also, a new entry is added to filereg.xml to insure that all scripts are located under the Interchange folder. This adds a level of security to the scripts.

00845249 BTOBIEXEC-6691

Non-CSOS related X12 820 and 880 fail in CSOS environment with EDI-Linking enabled

Issue: Messages were failing in the CSOS environment due to missing or outdated OBOE rules xml definitions.

Resolution: If the EDI identifier tries to find an OBOE rule that does not exist, it will not fail the message; although, it will provide/log a warning (once per TE lifecycle) that indicates the missing rule file:
"Document type: xxx not supported for edi document identification. Update oboe rules and restart."

If the rule file is there and there is another exception, then that will always be logged and it will affect the flow as before. OBOE rules XML files that are delivered by default (in the conf/tx/oboe_rules folder): 810, 840, 850, 855,894, 997. Contact support.axway.com if additional EDI rule files are needed for other message document types.

00895271 BTOBIEXEC-6722

Remove xib_clean.x4 from the B2Bi delivery

Issue: xib_clean.x4 is still delivered in <B2Bi>/Integrator/4edi/pgm. In B2Bi, b2bi_clean.x4 should be used to clean up the data.

Resolution: Removed the xib_clean.x4 from delivery.

00907661 BTOBIEXEC-6726

Slow response with "Show related messages" in message tracker UI

Issue: "Show related messages" option was running too slow and it was not documented how to fix the issue.

Resolution: Updated the B2Bi Administrator Guide to include an optional index that you can add to your database if the message processing from the "Show related messages" option is running too slow.

00884197 BTOBIEXEC-6739

"bad_record_mac" with GCM cipher in FIPS mode

Issue: When in FIPS mode, TLS GCM ciphers were enabled and could be used during trading, but they would not work. The issue is due to the Entrust FIPS implementation used by B2Bi, that has issue with GCM ciphers.

Resolution: TLS GCM ciphers are no longer available when in FIPS mode.

00903076 BTOBIEXEC-6772

Inadequate Encryption Strength

Issue: The RSA key size from the certificate request sent to a CA via the PKIX protocol was inadequate (1024).

Resolution: The key size is increased to 2048, in par with the current security standards.

00903070 BTOBIEXEC-6779

Vulnerability: CRLF injection vulnerability

Issue: "Simple" log messages in the server logs (for example, non-stack traces) containing CR or LF characters would log those characters into the logs.

Resolution: "Simple" log messages in the server logs containing CR or LF characters no longer log those characters into the logs; preventing CRLF log injection attacks.

00821189, 00887819 BTOBIEXEC-6803

Loading components type Document / Post detection takes time

Issue: Loading components type Detection / Post detection was taking too much time.

Resolution: Performance is now improved when loading component details from Integrator.

  BTOBIEXEC-6854

OS command injection

Issue: Users could configure post processing and error scripts in the UI to run scripts in unsecured locations.
Resolution: A new user permission has been added to prevent users from configuring scripts. Also, a new entry has been added to filereg.xml to insure that scripts are all located under the Interchange folder. These add a level of security to the scripts.

00891522 BTOBIEXEC-6863

Backup location not displayed in message tracker if shared not available

Issue: The Interchange backup folder was being re-created on the local disk if share was not available.

Resolution: The share is not recreated at runtime unless a new one is being set from the UI or a system import is executed.

00893470 BTOBIEXEC-6920

Incorrect translation error generated - Message log/trace

Issue: An error from the first message was displayed in message log on the second message.

Resolution: Fixed errors not related to message being processed.

00910215 BTOBIEXEC-6963

JMS Correlation Id not parsed in the Interchange JMS transports

Issue: JMS Correlation Id was not parsed in the Interchange JMS transports. Also, there was no way to have it set on outbound transfers.

Resolution: JMS Correlation Id now parses as designed.

  BTOBIEXEC-7156

Older SFTP clients are not able to connect to the embedded servers

Issue: The documentation did not include a list of the applicable cipher suites.

Resolution: The B2Bi Security Guide now contains a list of ciphers needed on the client for a successful connection when a new embedded or external SFTP server is defined in a FIPS environment.

00903086 BTOBIEXEC-7179

Vulnerability: Directory Traversal

Issue: The validation was disabled by default to avoid problems for existing customers.

Resolution: WARNs are now present after system import with Integrator App pickups/deliveries where the paths are outside of the "common" directory.

00897291 BTOBIEXEC-7235

Intermittent NPE on client disconnect from embedded SFTP server

Issue: Occasionally, NullPointerExceptions were encountered during trading on SFTP using an embedded server.

Resolution: The SFTP Maverick jars have been updated and trading is successful on SFTP.

00835751 BTOBIEXEC-7265

Sentinel monitoring: FileName not displayed in B2Bi_Message

Issue: FileName is displayed on all events.

Resolution: FileName no longer displays on all events.

00913471 BTOBIEXEC-7279

Request to accept 128 character as username and password in Global External SMTP server

Issue: The user name and password fields for the Global External SMTP server were limited to 50 characters in the database. The password was also limited to the same value in UI, but the user name had no limit.

Resolution: Both the user name and password fields of the Global External SMTP server support values up to 128 characters. Now, The UI does not allow a greater value than the supported value.

00912982 BTOBIEXEC-7293

B2Bi does not recognize the Metadata "ConnectionId" JMS attribute when polled from JMS server

Issue: The ConnectionId metadata was reset in the no packaging receiver and any related connection closed if the ConnectionId metadata was set on an inbound message.

Resolution: Closing the connection is now prevented in the no packaging receiver if the ConnectionIdExternallySupplied metadata is set on the inbound message.

- BTOBIEXEC-7329

CSOS Schedule validation for supplier system

Issue: CSOS orders were not fully validated to match the DEA approval certificate issued drug schedule authority in all cases.

Resolution: The CSOS Supplier side order validation logic now fully validates the requested drug schedule(s) against the authorized drug schedule(s) of the CSOS Buyer side DEA certificate used to approve the order. This validation is performed on the Supplier side system per the DEA rules and the Drummond Group certification. The following system properties are added to allow tuning of the schedule validation logic and of the xpath where the schedule value is taken from:

1. csos.schedule.validation – the default value is ‘true’ in order to be fully DEA compliant with CSOS order processing. Axway does not recommend disabling this setting.

2. csos.xpath.850.schedules – defines the 850 PO XPath to find the REF:72 segment containing the listed drug schedule in the CSOS 850 order. The system property should be set to XPath to find the REF:72 segment by default. Please do not try to modify this xpath value unless you have a deep understanding of how xpaths work.

00914502 BTOBIEXEC-7370

EDI 5010 ST03 Missing after enveloping

Issue: The ST_1705 field in the X12 transaction set header are removed by the X12 enveloper.

Resolution: The fields are no longer missing.

  BTOBIEXEC-7441

Documentation to remove Interchange trading data is incorrect

Issue: Incorrect references for removing data were in the documentation.

Resolution: Removed the incorrect references to remove data during the upgrade from the B2Bi Interchange Upgrade Guide.


Standards Library

Case 
ID
Internal ID Description
00901650 STAN-1202

Wrong pattern in SEPA Business Documents

The CstmrtoBnkDrctDbtClcDatstV70.bdoc from the SEPA_EPC_2014_V7_0 standard contained an invalid pattern for certain ID fields. The pattern has been removed from all SEPA_EPC_2014_V7 bdocs.

00902881 STAN-1306

Update SEPA usage rule for the field 2.1 (Cd) : remove COR1

The enumeration for the field 142 (Cd) of the Business Documents CstmrtoBnkDrctDbtClcDatstV70.bdoc and SEPA_SDD_pain_008_01_02.bdoc still included the "COR1" value. The "COR1" value has been removed from the enumeration list for the (Cd) field.

00908053 STAN-1486

Impossible to register JMC FEX

It was impossible to register the JMC fexmap-basics-dataaccessjmc.jar as described in the B2Bi 2.3.0 documentation. Updated the procedure in the Financial Standards Library Installation Guide and Financial Standards Library Administration Guide.

 


Known issues and limitations

Case 
ID
Internal ID Description
MS-125

Datamapper simulation cannot run from a new workspace

Issue: When you start Mapping Services 3.3.0 with a new workspace, the Datamapper simulation to a Runtime Server will not work until after a deployment is made to that Runtime Server. The local Datamapper simulation will continue to work as designed.

Workaround: Before you run the Datamapper simulation you must deploy the project to the B2Bi server.

RDBTOBI-5377 Peer Networks: Partner user accounts are not correctly cloned to peers

Issue: In peer network environments with auto-cloning of trading pickups enabled, when you have communities that include partner user accounts (FTP, SFTP, WebServices, AS4,...) the user accounts are not correctly cloned.

Workaround: If have enabled auto-cloning of trading pickups, you must also enable auto-cloning of partners.

RDBTOBI-5240

B2Bi tasks are not restarting on the remaining node

Issue: During run of B2B_QA_System_Test_Failover_NFS_SecondarySystem_Power_MultipleTE_Outbound_GI_GI test, after the failover scenario, the remainig node is not restarting the tasks in order to continue processing the files.

Workaround: When adding multiple TE nodes it is recommended to increase the number of cluster threads that can be configured in the <b2b_install>/Interchange/conf/jvmArguments.xml, by adding the following inside the first NodeType element (the one that has no type and class attributes).

This must be done for ALL machines from the cluster.

<Property key="axway.cluster.threadpool.core.size">150</Property>

<Property key="axway.cluster.threadpool.max.size">150</Property>

- RDBTOBI-2601

JMS queues are not available

Issue: JMS queues are not available and some input files are not processed.

 

RDBTOBI-1657

Export of WebTrader as a non-sponsored profile includes settings of Global Embedded Server, and import fails
Issue: When exporting a WebTrader as a non-sponsored partner profile and then importing into a sender instance of B2Bi as a trading partner, the import wizard reports that an Embedded Server with an incorrect name was found. Analysis of the import results shows that the Embedded Server exchange point was omitted. Furthermore, the Embedded Server should not be included in the original export.

RDBTOBI-1651

No packaging JMS for WebTrader community delivery exchange should not be used by external partners

Issue: The implementation of WebTrader requires a No Packaging JMS trading pickup on the community/sponsor. This particular exchange point is for internal use only between WebTraders and B2Bi. When exporting a WebTrader as a "non sponsored partner profile" to be imported into a remote system (as a regular partner), the trading pickups of the sponsor are incorrectly included.

00852428 RDBTOBI-1524

Misleading error message during login to B2Bi System Manager

Issue: When creating a user without administrator and Access API permissions, but with all other privileges, when the user tries to log into the System Manager, the unexpected error "System not available yet" is generated.

- RDBTOBI-1135 System import/export: Components defined in a service are not exported in the correct order

Issue: If you have multiple components of the same type in a service and use the "Move component up" or "Move component down" tools to change the component display order in the UI, the new order is not conserved when you export and then import the service to a new system.
Workaround: After importing a service with multiple components of the same type, be sure to verify the component order, and manually re-order them if necessary.

00851137 RDBTOBI-1097

procmbc_example module readme file missing

Issue: procmbc_example module has no readme file (in $CORE_ROOT/readme).

RDBTOBI-685 Unable to use TLSv2 cipher - SSL_RSA_WITH_RC4_128_SHA in MQ8
Issue: When setting the cipher suite value to SSL_RSA_WITH_RC4_128_SHA in B2BI, B2Bi fails to make calls to MQ. The supported TLSv2 cipher does not work after upgrade to B2Bi 2.3.1, which uses Java 8, update 66.
Workaround:
  1. Go to <B2Bi_install_directory>\Interchange\conf and open jvmArguments.xml in an editor.
  2. Add the line:
  3. <Option>Djava.security.properties=../conf/mysecurity.conf</Option>
  4. Create a new file in the ../conf directory called mysecurity.conf. In this newly created file, add the line:
  5. jdk.tls.disabledAlgorithms=SSLv3, MD5withRSA, DH keySize < 7683
  6. This line enables the RC4 encryption algorithm, which allows the cipher SSL_RSA_WITH_RC4_128_SH.
  7. Restart B2Bi.
RDBTOBI-653 Processing of DML maps with m107804_NamespaceMultiplePrefixes fail on all platforms.
RDBTOBI-307

When you "Resend" a message from Document Tracker, in Sentinel the event displays unexpectedly as a "Delivered" event within the same CycleID. This incorrect event type labeling will be corrected in a future release of B2Bi.

RDBTOBI-294 JMS Trading Agreements display as correctly configured (green icons), but connections are not established.
RDBTOBI-246 Upgrade to B2Bi 2.3.1 - Export and import of components fails

Issue: After you upgrade to B2Bi 2.3.1 from an earlier version of B2Bi, if you use either the system backup or selective export tool to back up a component, delete the backed up component in the UI, and then attempt to restore the deleted component, the import of the deleted component fails.

Workaround: After the upgrade to B2Bi 2.3.1, open the component's configuration page and save the component configuration without making any changes. The export and import of the component should execute successfully.

 

D-102799

B-102303

SSO: Unexpected error when accessing metadata profile on 6080 port

When accessing the SSO Metadata URL to view the Service Provider configuration on non-sso port (6080), when no service provider certificate is selected (SSO configuration is incomplete ) an unexpected error is displayed in the UI.

D-102522

B-99706

AS4: Selecting "Synchronous response generated in backend" option on an asynchronous message exchange causes failed receipt status

When the ‘Synchronous response generated in backend’ option is enabled on receiver's AS4 HTTP(S) Trading Pickup, and the receiver consumes a negative receipt over a new asynchronous connection, the receiver keeps the connection open for a User Message reply. However, since there is no User Message reply for a negative receipt, the receipt status ends in 'Failed' when all the retries are exhausted.

00817449 B-103307 Transfers from whitelisted partners fail when "Match IP Address Against Partner Definition" is selected on a pickup with DMZ security termination

Issue: When you configure a pickup with both "Enable IP address checking in DMZ" and "Match IP Address Against Partner Definition" selected, and then consume a message from a trading partner whose IP address in included in the master whitelist, the IP address passes the IP filtering in the DMZ Router Agent, but fails in the trading engine.

Workaround: You should not configure both community-allocated user accounts and partner defined IP ranges together with "Match IP Address Against Partner Definition". In order to enable message consumption, you must do one of the following:

  • Deselect "Match IP Address Against Partner Definition" (leaving "Enable IP address checking in DMZ" selected), or
  • Change the user credentials to be explicitly owned by the same partner.

 

D-101399

B-102430

A remote client should not connect directly to the embedded secured server when "Enable security termination in DMZ" is selected

When configuring a SSL secured B2Bi embedded server (HTTPS/FTPS), and when the server DMZ ports settings have both "Enable DMZ port forwarding" and "Enable security termination in DMZ" options selected, the remote unsecured client generates connection errors in the following cases:

  • HTTPS server – The client can send a message directly on the server with a HTTP partner delivery (the URL starts with http://)
  • FTPS server - The client can send the message with a FTP partner delivery in both explicit and implicit SSL modes. In the explicit mode there is an exception on the client side “Client closed connection before all replies could be sent” however the message transfer is made successfully.
  • SFTP server - It is not possible to use a non-secured client since it doesn’t have an non-secured version.
D-99122

Failure of FORCE_SYNC command on Solaris 11

Issue: In Solaris 11 environments, when running FORCE_SYNC to force the synchronization of maps, the synchronization fails.

Workaround: Add the following line to $CORE_ROOT/profile : unset LC_ALL LC_CTYPE.

 
M-149162 Windows failover: Missing Interchange control numbers during a failover

Issue: When configuring an outbound X12 enveloper with the Interchange control number generator specified as $icid:9$, in the event of failover the generated control numbers are not consecutive.

Note   Consecutive control numbers are not guaranteed in the case of failover. This is not considered to be a product defect.
M-144708

Peer Network: When Peer Network messages fail due to transport errors, the messages are resent

Issue: Peer Messages for configuration synchronization are now sequenced to provide configuration integrity to the remote peer system. Retrying transport errors for peer messages may delay all related peer activity for up to one hour using the default retry settings. It is desirable to retry peer messages a number of times at the connection level but to not block all other peer messages going to the same remote peer network. Reliable messaging setting are only applied after the message is successfully sent and only if the message protocol requests receipts so they are not a factor at the transport level.

Work around: Change the peer delivery exchange to force the connection level retries to fail faster, as follows:

  1. In the B2Bi UI, select the peer partner delivery exchange in Peer Network > Manage peer network.
  2. Select "Partner Delivery" and select the peer communication exchange.
  3. Select the "Advanced" tab.
  4. In the "Retries" field enter the value "10".
  5. Check the “Use custom retry intervals” checkbox.
  6. In the “Custom retry intervals: field enter “1,1”
  7. Click "Save changes". This will force the transport level connection up to 10 times 1 minute apart.
M-139276 Sentinel Tracked Object field type limitation

Issue: For Sentinel Tracked Objects, the Sentinel type 'Long String' is not supported in the DML used in Mapping Services. This leads to an attribute length "0" when deploying to a B2Bi integration engine.

Workaround: For B2Bi integration engine processing, the 'Long String' data type is identical to 'String'. In Sentinel Tracked Objects, use the 'String' data type in place of 'Long String' to avoid errors.

- M-137103

B2Bi clustered implementations with X.400 subsystems: Starting any trading engine temporarily stops the X.400 subsystem

In B2Bi active/active clustered configurations with an X.400 delivery exchange configured, when stopping and then restarting any trading engine in the environment, the X.400 subsystem is temporarily suspended for a period of approximately 15 seconds, which causes a temporary suspension of X.400 services.

The resolution of this defect is being studied for a future release.

M-122568

System import limitation: Processing fails on messages that were in "Retry Scheduled" state

Issue: In cases where you stop the trading engine node and import a system backup and then restart the node, any messages that were in "Retry Scheduled" state will fail on send attempts after restart. This is because the system import logic modifies the outbound ID of the target exchange partner. These in-process messages that are failed and any existing messages already in a “Failed” or “Delivered” state are now not possible to Resend or Reprocess.

  • Caution 1: The rejectInprocessMessages tool cannot be used to initiate the reprocessing of these particular kinds of stuck messages. Using the rejectInprocessMessages tool changes the message status to Failed, which will qualify those messages for purging later on, however, the tool does not supply info that will enable the Failed messages to be reprocessed.
  • Caution 2: You must stop the entire B2Bi application (on all cluster nodes) before attempting to run the rejectInprocessMessages tool.
M-112634

MQSeries server access

Issue: In some cases, the MQ jars that are updated in B2Bi 2.3.1 enable additional MQ 7.x security features. Depending on your configuration, you may need to do one or more of the following:

  • Update channel authentication records
  • Add or update authentication or object authorities
  • Add an MQ user to an Interchange MQ exchange point that formerly worked anonymously

B2Bi 2.3.1 installs updated MQ Series jars. You may need to modify the MQSeries configuration in order to enable an existing MQ 7.x configuration to work after upgrading to B2Bi 2.3.1.

Work around: Axway recommends that you contact your MQ administrator if problems are noted.

Miscellaneous issues

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

  • SAP Metadata Browser plugin not supported
  • Issue: B2Bi supports the transfer of IDocs to and from SAP using ALE. However, the use of the B2Bi Metadata Browser to directly view SAP IDOC reports is no longer supported.
  • Workaround: To view SAP IDOC reports, export the reports from the SAP system and use them in the Metadata Browser to create ADF files. For details about creating and viewing ADF files, see the B2Bi Operator Guide / Metadata Browser chapter.
  • Failover and sequential delivery
  • The ability to deliver messages in sequence in the case of a failover is not always guaranteed.
  • API Connector and Datamapper ADF Metadata Browser plugins not supported
  • The Metadata Browser plugins for the API Connector and Datamapper ADF should not be used. They will be removed in a future release.
  • PassPort integration issue with integration engine tools
  • When you configure the integration engine with PassPort access management, the B2Bi integration engine client tools lose the ability to distinguish between different levels of user privileges(view/modify/execute). Access to individual tools can either be granted or not granted.
  • Web Services provider mode configuration using Mapping Services RouteTo block
  • When a Web Services provider flow with attachments is configured that uses a Mapping Services map with a RouteTo block, B2Bi copies the inbound request attachment attributes onto the output response. This results in the inbound attachments being forwarded back to the originator of the Web Service request.
  • Web Services provider mode HTTP connection fails to close
    Issue – When you configure Web Services provider mode for one-way communication with faults returned to client, on the Web Service trading pickup you must normally select the option "Synchronous response generated in backend" in order to enable sending of the fault file to the requesting service consumer. However, if the incoming request message does not trigger a fault and is correctly delivered to the back end, the HTTP connection is kept open until timeout on the client side.
  • Workaround – For a one-way Web Service provider configuration, do not select the option "Synchronous response generated in backend". This prevents the provider from sending a fault message, but allows the connection to close normally after receiving the client request message.
  • General Web Services limitations
    • B2Bi 2.x supports Web Services on the trading (partner side), but not on the application side.
    • By default, WS-Addressing must be used in provider mode. To disable the need for WS-addressing, refer to the alternate axis2NoWSAddressing.xml file in your WS pickup configuration.
    • The B2Bi WSDL wizard currently only supports the generation of WSDL definitions. These definitions cannot be edited afterwards. To change the WS interface, you must either regenerate a new WSDL using the wizard, or edit the WSDL manually.
  • Web Services provider flow: "check input attributes" and "check output attributes" not persisted on B2Bi server
  • Issue: In Mapping Services, when you create an enumeration in a BusinessDoc leaf (in the Attributes/Enumeration tab), and then use the BusinessDoc in a Flow in which the "check input attributes" and "check output attributes" options are selected, these options are not persisted when you deploy the map to a B2Bi server.
  • Resolution: You must manually select the "check input attributes" and "check output attributes" options in the B2Bi user interface (Service/Service details/Component details).
  • RHEL 6 requirement for X.400 support
    By default, the Red Hat Enterprise Linux 6 x86_64 operating system installs without installing a 32-bit library (/lib/ld-linux.so.2) needed by the trading engine X.400 subsystem. To enable B2Bi with X.400 installed on RHEL 6, install the package glibc.i686 from the RHEL installation media.
  • Upgrade limitation: Alternate party in an agreement is used even when an outbound agreement for enveloping is specified
  • Resolution: In the B2Bi UI, manually edit each inbound agreement / document agreement, setting the Partner Routing ID to one that belongs to the community on the remote system.
  • This occurs when the upgrade logic creates a document agreement inside an inbound agreement, and where the output in the document agreement refers to an outbound agreement for enveloping and also has the “Use alternate delivery partner” option selected. In this case, the Routing ID that is selected is the one that matches with the Messaging ID of the agreement, which leads to errors. The correct Routing ID should be one that reflects the identity that is used by the communication partner.
  • Upgrade limitation: Use of trading engine transports on the application side through Message Handler re-routing
  • Issue: After upgrading from B2Bi 1.x to B2Bi 2.x, in some cases trading fails due to the way partner routing ID’s are selected by the upgrade logic.
  • If you had a B2Bi 1.x implementation in which a "U-turn construct" was employed to enable the use of the Trading Engine transports on the application side, this logic must be manually reconfigured after the upgrade.
  • Secure Relay installation on AIX platforms
  • For installations on AIX platforms, both B2Bi Server and Secure Relay must use the same operating system.
  • SAN file system hotfix requirement
  • Issue: Two SAN 6.2 cluster nodes show different contents of a file on CFS share.
  • Workaround: In order to run B2Bi on SAN 6.2, you must obtain the VxFS 6.2.0.003 HotFix from Symantec Support and apply the HotFix to each Veritas cluster node.
  • Upgrade: Not all Document Tracker "warning" entries are displayed
    When you install B2Bi 2.3.1, the Document Tracker provides an additional search filtering criterion: "warning".
  • Only "warning" type Document Tracker entries that are generated after installing B2Bi 2.3.1 can be filtered (and optionally displayed) in search results when you use this filtering criterion. "Warning" type entries that were generated in B2Bi 2.3.1 before applying upgrades are not be filtered.
  • Swagger API client: Swagger user can continue to execute operations after logout
  • When using Chrome and Firefox browsers, after logging out of a Swagger session, a user can call operations as though they had not logged out. This problem occurs because these browsers remember, and automatically provide, the login credentials. Credentials are cleared from memory when the browser window is closed.
  • Swagger API client: Swagger user cannot log in using the login method
  • Issue: The REST login method asks for the authorization header, which is a single string composed of a hash of the username and password. However, in most cases, users only know their username and their password.
  • Workaround: The user can call directly the desired operation. This triggers the login, causing the browser to display a user-friendly prompt for the username and password.
  • With ebXML intermediary (SMTP), message cannot be delivered to external SMTP server
  • When setting up an ebXML intermediary (SMTP), an embedded SMTP server must be used for the receiver. If the external SMTP server is used, the trading to the receiver fails.
  • FTPS outbound transfer fails when Secure Relay Routing Agent runs on AIX
  • Issue: For B2Bi installations with Secure Relay, when the Secure Relay Routing Agent (RA) runs on an AIX machine, FTPS outbound transfers fail when any of the following cipher suites are used as overrides on the partner delivery:
    • SSL_RSA_WITH_DES_CBC_SHA
    • SSL_DHE_RSA_WITH_DES_CBC_SHA
  • Work around: Select an alternate cipher suite on the partner delivery.
  • Sequential delivery: Trading engine blocks sequential delivery when message-handling timeout threshold is engaged
  • For messages that are consumed on exchange pickups with sequential delivery activated, when the message handling time-out 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.
  • Upgrade: PostTransfer and Document B2BX Application Components display 1.5.0 values in the 2.3.1 UI
  • After upgrading from B2Bi 1.5.0 to B2Bi 2.3.1, PostTransfer and Document B2BX Application components still display 1.5.0 values. These fields should normally be displayed only on the 2.3.1 Service object that uses the Component. If this occurs, open the affected Component and Service definitions and save the objects. This will resolve the issue.
  • Upgrade: After upgrade, export/import of an Agreement that contains multiple Document Agreements fails
  • This issue occurs only in the following context:
    1. You upgrade from B2Bi 1.5.0 SP11 to B2Bi 2.3.1.
    2. You perform a B2Bi System Configuration Export that includes an Agreement that has multiple Document Agreements, where two or more of the Document Agreements are not unique. One of the Document Agreements is enabled and the non-unique Document Agreements are disabled.
    3. You clean the database and import the exported B2Bi System Configuration.
  • The result is that the non-unique Document Agreements are not imported.
  • 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.

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

  • 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. Go to the Axway Documentation portal at http://docs.axway.com to find documentation for this product version. Additional documentation may be available at Axway Support at https://support.axway.com.

For step-by-step instructions on how to configure B2Bi 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 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 © 2017 . All rights reserved

 

Related Links