BIS Link Release Notes

Version: 6.5.1Q6

April 16, 2018

Table of Contents

1 Getting Started 1

2 General Setup Information 2

3 Installation Requirements 3

4 Supported Systems 5
4.1 OS Compatibility Matrix 5

4.2 Virtualization 6

5 Known Issues 7

6 New Features 8

7 Restrictions 9
Copyright (c) 2018 SEEBURGER AG (http://www.seeburger.de). All rights reserved.

If (registered or pending) trademarks are named in this document, the rights of the respective proprietors
apply.

Note: False configuration and/or improper use of communication components may result in significant
charges from your telecommunication provider. Also consider configuration changes initiated by your
telecommunication provider. SEEBURGER is not liable for related additional costs.

Note: Please refer to the Knowledgebase article 13379 for an important notice concerning possible incurred
charges from your telecommunication provider.

Note: The information in this document is proprietary to SEEBURGER. No part of this document may be
reproduced, copied, or transmitted in any form or purpose without the express prior written permission of
SEEBURGER AG.

Note: Export-/Import Regulations

The SEEBURGER AG is a German corporate with subsidiaries in countries worldwide. In daily trading with
our customers and partners, each SEEBURGER corporate deals in compliance with the local export and
import regulations of the specific country.

SEEBURGER standard software is partly based on US technology (tomcat, Red Hat JBoss, Oracle Java
etc.). To be compliant with the US Export Administration Regulation and the Treasury Department regulations
SEEBURGER software and/or technical data may NOT be exported /reexported, either directly or indirectly,
to any destination subject to U.S. embargos or trade sanctions unless formally authorized by the U.S.
Government. Note that said embargoed destinations are subject to change and the scope of what technology
is included in the embargo is specific to each embargoed country. For the most current information on
U.S. embargoed and sanctioned countries, please contact the U.S. Export Administration Regulations and
Treasury Department regulations.

Note: We expressly declare that the document "SEEBURGER Legal Information" (delivered also with your
BIS installation media) is part of this documentation.
BIS Link Release Notes

1 Getting Started

The following Release Notes refer to the BIS Link products release 6.5.1Q6.

The previous release was called BIS Link 6.5.1Q5.

Products compiling BIS Link are:

• SEEBURGER BIS Link (BIS Link)

• SEEBURGER BIS Link Plus (BIS Link Plus)

BIS Link Release Notes - 6.5.1Q6 1

BIS Link Release Notes

2 General Setup Information

Documentation
On the installation media, the location of the documentation is

[installation media]/doc/

Third-Party Components
Sources of some third-party libraries can be found on the installation media in the directory [installation media]/
thirdparty/sources.

BIS Link Release Notes - 6.5.1Q6 2

BIS Link Release Notes

3 Installation Requirements

RAM Min 2GB

Hard Drive 12 GB + space for runtime data (depending on the throughput, cleaning
configuration etc.).

The requirement of 12 GB includes:

• 300 MB installation package (if roll-out installation with BIS Link
Manager is used) or 700 MB (for installations from CD)
• 600 MB size of installed BIS Link
• At least 10GB of free disk space(monitored by the system) - See
chapter "Prevention of "disk full" case" in the Configuration Guide.
Operating System See Supported Systems (page 5) for the list of supported
operating systems
Java Runtime JDK 8.0 (JRE is not supported)
• MS Windows: JDK 8.0 Update 162 is installed by the setup.
• Linux: JDK 8.0 Update 162 is installed by the setup.
• Solaris: JDK 8.0 Update 162 or later must be installed before the
setup is executed.
• AIX: Actual JDK 8.0 must be installed before the setup is
executed
Web Browser • Internet Explorer version 8 , 9, 10, 11.
• Firefox version 10 or higher.
• Google Chrome version 11 or higher.

Note: Older versions of the browser listed above and other web
browser are not supported.

It is highly recommended to use the latest available browser

version.

Screen resolution The Web GUI needs at least screen resolution "HD Ready"(1366 x
768) to display correctly. For productive usage the minimal required
resolution is "Full HD"(1920 x 1080).

The given screen resolutions are requirement to the system

where the web browser is started and not to the system where the
product runs

IP Address • Host has a static IP - Sending and receiving of files is possible.

BIS Link Release Notes - 6.5.1Q6 3

BIS Link Release Notes

• Host has a dynamic IP - Receiving of files only possible using SLMP

polling. Sending of files is possible via SLMP.

Note: It is recommended to use a static IP on the host, where the

BIS Link product is installed.

Database No database installation is needed prior to the SEEBURGER BIS Link

installation. The setup will install a H2 database.
BIS For full functionality this product requires:

• BIS 6.5.2 SP58 or newer.

This product supports with limited functionality(some features will be
missing):
• BIS 6.3.5 Q4 with at least hotfix B6-635Q4-478 or patch containing
this hotfix installed.
• BIS 6.5.2.
Antivirus software After the installation the application database directory - <install_path>/
db - must be excluded from the antivirus software protection.
Otherwise the database file may be corrupted

BIS Link Release Notes - 6.5.1Q6 4

BIS Link Release Notes

4 Supported Systems

Supported Systems

4.1 OS Compatibility Matrix

The following tables list the supported operating systems and hardware architecture for the corresponding
system components:

Installation Type Description

Instance BIS Instance (Any roles: PE,AE,WLH,AS)
Client Can be used to install the SEEBURGER Developer Studio, the SEEBURGER BIC
Mapping Designer and to run the WebStart Client (BIS Frontend).
Express Server Works as All-In-One BIS Instance.
Can be used in a production environment with small data volume.

This means:

• Max. volume (number of EDI transactions (UNH) per day) = 100

Typically installed by article S7500B6 (BIS:Express Standard EDI Solution - Basis).
Portal 6 Installation of B2B Portal

BIS Link Release Notes - 6.5.1Q6 5

BIS Link Release Notes

x = supported | o = on request | - = not supported

• The combination of Instances on different platforms is supported, however, we recommend to use unitary
java VMs on the Instances.
• Updates on previously listed operating systems are supported, as long as the operating system is
mainstream supported by vendor and certified by Oracle Java.
• Other Linux platforms or distributions are not supported.
• No Windows/Linux IA64 platforms are supported
• It is recommended to install the latest available service pack from Microsoft before you start installing /
upgrading an installation!

* x86 (32 Bit) versions are only supported until September 2018

4.2 Virtualization
Virtualization
Running SEEBURGER solutions on virtualized platforms is supported. Please refer to our Support Knowledge
Base [article ID = 12392] to obtain latest information and best practices.

BIS Link Release Notes - 6.5.1Q6 6

BIS Link Release Notes

5 Known Issues

Backend Integration

• In some cases (mostly on Linux systems) the system will wrongly inform the file adapter that the
file is already completely copied to the file port. This will cause the pick up of incomplete files. This
phenomenon can be observed mostly with huge files. A workaround for this issue is to put the files
into the file pick-up port with the temporary file extension (.tmp), and after that to rename them to the
original file name. In the opposite direction, the default configuration of the file storing port uses temp file
mechanism to avoid such problems. Please note that this is not an issue in the file adapter, but a general
issue of the file locking behavior of the different operating systems.
• Runtime pickup port existence verification doesn't work for network shares.
• BIS Link might experience issues in polling scenarios with BIS 6.5.2 SP38-SP43.

Setup

• Part of the installation procedure is to start the default for the system web browser in order to show
configuration web GUI. On some not fully configured Linux systems running Mozilla Firefox the browser
will not open. In other cases, when the Firefox is running in another user session a message box appears
with error "Firefox is already running but doesn't respond.". On such an issue, use the desktop shortcut
to web GUI to start it, or start the browser manually and type the GUI URL written in the last screen of the
installation phase.
• On Windows, the operating system caches the URLs used as GUI shortcuts. As a result, if GUI port is
changed in Configuration Wizard or GUI->Listeners section, the GUI desktop shortcut still may point to
the cached value. Then the shortcut won't open the correct GUI URL in the browser. This can be solved
by entering the correct URL in the browser address bar or by user logout and login into Windows. It will
clear the cache and GUI desktop shortcut will point to the right URL.

BIS Link Release Notes - 6.5.1Q6 7

BIS Link Release Notes

6 New Features

Setup

• As of JDK 1.8.152 Oracle changed the way JCE Unlimited Strength Jurisdiction Policy Files are provided
and used. The product setup procedure was modified to comply with the new policy and to offer an easier
handling of those files. In the case of IBM JDK the procedure is the same like in the previous versions of
the product.
• Introduced shell scripts for installation and management of application deployer service as a daemon
service on Linux.
• Processing queue size and queue processor count are now able to be set in installer.properties prior to
the installation.

Security

• Added support of an explicit TLS (STARTTLS) when sending alerting emails.

PGP

• Added support of import and export of private PGP keys with subkeys.
• Enabled usage of certain variables in the parameters of PGP key generation during setup.

Core

• BIS Message Tracking functionality is extended so that the status control message can be also saved to
a file.
• Optimized the generation of Message Tracking control messages in retry cases to avoid filling the SLMP
queue.
• Ensured transport of ContextID values between BIS Link and BIS serving Message Tracking purposes.
• Added the possibility to configure storing of alert and event history in the database in order to reduce their
size.

Backend Integration

• Processing of empty (0 bytes) files is now enabled by default.

Roll-out

• Pre-compiled production-test process is shipped with SLMP adapter of BIS 6.5.2 (SP 56 or higher
version). So BIS Developer Studio and Process Designer are no longer required to set roll-out scenario.

BIS Link Release Notes - 6.5.1Q6 8

BIS Link Release Notes

7 Restrictions

General

• Generally only a single instance of the product per host is supported. Despite this restriction it is possible
to install and run more than one instance per host but none of them must be installed as Windows service
and they must listen on different ports.

Install/Update

• This version supports update of versions 6.5.1Q4 and 6.5.1Q5. Update of previous versions is not
supported.
• Application update to newer version should be performed on idle times by low processing load. Otherwise
unexpected errors may occur.
• Hotfix installation should be performed on idle times by low processing load. Otherwise unexpected
errors may occur.
• Disabling of screens of GUI installer is not supported.

Windows

• Mapped network drives are not supported as file ports. Use network share(CIFS) functionality instead.
• Microsoft Distributed File System (DFS) is not supported by CIFS functionality. Refer to Configuration
Guide how to set the access to it.
• If the application is run as console it must not be stopped by pressing "x" console window button.
Doing it will terminate the JVM immediately without any clean up at the end. The proper way to stop the
application is to call "shutdown.bat" .
• Any application batch ( .bat ) file, which is started manually must be executed with the option "Run as
Administrator". Otherwise the Windows UAC(User Access Control) could prevent its proper execution.
• Pre-configured Windows installation packages downloaded during the roll-out process are created on-
the-fly in BIS Link Manager. As a result they are not digitally signed. When started they could trigger
warning or error Windows dialogs(depending on configured policy). The warnings/errors should be
ignored and execution of the installation package should be allowed.
• Windows 10 version 1709 ( Fall Creators Update ) introduces new security features that allow users
to control folders and applications access. This product is tested against the default Windows 10 RS3
Security Baseline and no support is provided for other but the default policies. We recommend special
training for system administrators dealing with restricted systems, as we cannot provide support for
system maintenance tasks in this case.
• Every local Windows user has access to BIS Link home directory and its content, including database and
temp directories. In the latter, the Password Reset Token is stored, when requested.

BIS Link Release Notes - 6.5.1Q6 9

BIS Link Release Notes

Linux

• Linux Daemon installation has to be done manually using the provided scripts and instructions.
• BIS Link can be used on RHEL with enabled SELinux with the targeted policy activated in permissive or
enforcing mode with the BIS Link runtime user as SELinux user unconfined_u. We do not provide support
for creating and running BIS Link with confined users or policies different from targeted. We recommend
special training for system administrators dealing with restricted systems, as we cannot provide support
for system maintenance tasks in this case.

Solaris

• Actual JDK 8 must be installed as prerequisite.

• Before starting the setup executable the user must set the variable JAVA_HOME to the root directory of
this JDK.
• Installation as daemon service is not supported.

AIX

• Actual JDK 8 must be installed as prerequisite.

• Before starting the setup executable the user must set the variable JAVA_HOME to the root directory of
this JDK.
• Installation as daemon service is not supported.
• Command line interface to the application Web Services doesn't support AIX.

GUI

• Screen resolution of the system where web browser displays the GUI should be at least 1366 x 768.
• Having too many processed documents in the document history will cause a significant performance
decrease in document monitoring and other GUI activities. An indicator of such a situation is the "System
Info->Database Load" parameter. If its value is "High", actions should be undertaken to either decrease
the count of documents processed by the application or to decrease the age of documents being
removed by the clean-up service. If the value is "Overloaded", these actions become urgent, as keeping
the application in an overloaded state may cause not only performance issues, but processing errors as
well.

BIC

Not supported features and mapping types:

• No automated support of BIS 6 mappings - although many developed for BIS 6 mapping will run
automatically the application is not designed to support complete BIS 6 environment. So there is no
guarantee that any randomly selected BIS 6 mapping will run without changes.
• child mappings
• double conversion
• splitting/merging
• mappings without input or output
• Compliance Check Adapter
• XSLT Convertor integration
• SAP BAPI calls

External variables and counters:

BIS Link Release Notes - 6.5.1Q6 10

BIS Link Release Notes

• Multivariables are not supported.

• Only mode "create if not exist" is supported by counters.
• Only mode "return empty string if not exists" is supported by variables.

PGP

• Creation, export and import of PGP keys require Unlimited JCE Policy Files.
• PGP compression, ASCII-Armor, detached or clear-text signatures are not supported.
• The document type is limited to binary.
• The integrity check cannot be disabled.

Backend integration

• Archiving of sent file and its status file is performed only on successful sending.

Roll-out

• Only BIS Link Manager 6.5.1Q6 can be used for the roll-out of BIS Link 6.5.1Q6 endpoints.

SLMP

• SLMP restart feature is not supported in "Disabled SLMP security" mode. Due to Tomcat issues and
HTTP protocol, no reliable behavior can be guaranteed for every possible network problem.

Processing modules

• Due to the in memory processing and parallel work in modules Xml D-Sig Composer, Xml D-Sig
Decomposer, Xml Envelope Composer and Xml Envelope Decomposer the size of the processed
file must not exceed 10 MB when running the application with the default JVM memory settings.

BIS

• Full functionality of this BIS Link version is achieved via collaboration with BIS 6.5.2 SP58 or higher.
Using previous version of BIS will impose restrictions in some of the features like Message Tracking,
PGP key distribution, etc.

BIS Link Release Notes - 6.5.1Q6 11