You are on page 1of 15

SEELink Release Notes

Version: 6.3.0Q1

July 4, 2014
Table of Contents

1 Getting Started 1

2 General Setup Information 2

3 Installation Requirements 3

4 Supported Systems 5
4.1 Virtualization 6

5 Known Issues 7

6 New Features 8

7 Restrictions 10
Copyright (c) 2014 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: We expressly declare that the document "SEEBURGER Legal Information" (delivered also with your
BIS installation media) is part of this documentation.
SEELink Release Notes

1 Getting Started

The following Release Notes refer to the SEE Link products release 6.3.0Q1

The previous release was called 6.2.0Q1.

Products compiling SEE Link are:

• SEEBURGER Secure Link (SEE Link)


• SEEBURGER Secure Link Plus (SEE Link Plus)

SEELink Release Notes - 6.3.0Q1 1


SEELink Release Notes

2 General Setup Information

Documentation
On the installation CD-ROM, the location of the documentation is

[CD-ROM]/doc/

SEELink Release Notes - 6.3.0Q1 2


SEELink Release Notes

3 Installation Requirements

RAM Min 2GB


Hard Drive 12 GB + space for runtime data (depending on the throughput, cleaning
configuration etc.).
Operating System See Supported Systems (page 5) for the list of supported
operating systems
Java Runtime JDK 7.0 (JRE is not supported)
• MS Windows: JDK 7.0 Update 55 is installed by the setup.
• Linux: JDK 7.0 Update 55 is installed by the setup.
• UNIX: Actual JDK 7.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 1024 x 768 to display
correctly. For productive usage the minimal required resolution is "HD
Ready"(1366 x 768). For better performance "Full HD"(1920 x 1080) is
recommended.

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.


• 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


SEE Link product is installed.

Database No database installation is needed prior to the SEEBURGER Secure


Link installation. The setup will install a H2 database.

SEELink Release Notes - 6.3.0Q1 3


SEELink Release Notes

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

SEELink Release Notes - 6.3.0Q1 4


SEELink Release Notes

4 Supported Systems

Microsoft Windows Family

Attention: You are forced to install the latest available ServicePack from Microsoft before you start
installing / upgrading a SEE Link installation!

Operating System Kernel Supported


Windows Server 2003 (R2) x86 (32 bit) X
Standard/Enterprise
Windows Server 2003 (R2) x64 (64 bit) X
Standard/Enterprise
Windows Server 2003 (R2) for IA64 (64 bit)
Itanium
Windows Server 2008 Standard/ x86 (32 bit) X
Enterprise
Windows Server 2008 (R2) x64 (64 bit) X
Standard/Enterprise
Windows Server 2008 (R2) for IA64 (64 bit)
Itanium
Windows Server 2012 x64 (64 bit) X
Windows XP (not Home Edition) x86 (32 bit) X
Windows XP (not Home Edition) x64 (64 bit) X
Windows Vista (not Home Edition) x86 (32 bit) X
Windows Vista (not Home Edition) x64 (64 bit) X
Windows 7 (not Home Editions) x86 (32 bit) X
Windows 7 (not Home Editions) x64 (64bit) X
Windows 8 ((Pro and Enterprise x86 (32 bit) X
Editions)
Windows 8 (Pro and Enterprise x64 (64bit) X
Editions)
1
Due to the memory limitations, a 32-bit Java process can only handle small- to medium-sized volumes. We
recommend 64-bit Java installations.

2
Supported operating systems are marked with "X"

SEELink Release Notes - 6.3.0Q1 5


SEELink Release Notes

UNIX/Linux Operating Systems

Operating System Kernel Supported


Red Hat Enterprise Linux (5, 6) x64 (64 bit) X
Novell SUSE Linux Enterprise x64 (64 bit) X
Server (10, 11)
Oracle Solaris 10 x64 (64 bit) X
IBM AIX (6.1, 7.1) POWER6,7 X
HP HP-UX (11iv2, 11iv3) IA64 (64 bit)
(Oracle Solaris 10, 11) SPARC
(Linux Kernel 2.6, 3.0-3.3) x86 (32 bit)
1 X

(All Itanium Linux) IA64 (64 bit)


1
Due to the memory limitations, a 32-bit Java process can only handle small- to medium-sized volumes. We
recommend 64-bit Java installations.

2
Supported operating systems are marked with "X"

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

SEELink Release Notes - 6.3.0Q1 6


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

Setup

• Part of the new 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.
• Remote installation in command line mode via SSH terminal fails if the SSH terminal application has
set the DISPLAY variable(X11 redirection is enabled). Workaround is to disable X11 redirection in the
terminal.

SEELink Release Notes - 6.3.0Q1 7


SEELink Release Notes

6 New Features

Core

• H2 database file monitoring and preventing its growth beyond certain configured limit. When this limit is
reached, the application ceases the processing, anerror event is reported and an alert is triggered.
• H2 database is now split into several files. This feature is available only by new installation.
• All application listeners now have configurable timeout

GUI

• Full support of Internet Explorer 10 and 11


• Manual database compact button.
• Cleanup service has now separate settings for documents in success, error and "in processing" state.
• Adaptable dashboard data actualization. After the database file exceeds a configured value, the
dashboard data will be updated on regular base and not on every request.

Setup

• Configuration Wizard transitions which require application restart are performed now in the same web
browser window
• .IBM AIX operating system is now supported

Backend integration

• Configurable maximal number of files to be polled from pickup port within a minute.

Web Services

• Configurable maximal number of files to be present in web service storing port


• Command line(via shell scripts) interface to SeeLinkFileTransferService.

SLMP

• SLMP .streaming support . Provides dramatic improvement in transfer speed of large files.
• SLMP Resume is supported in “polling from partner” scenario.
• Variables representing sending and receiver SLMP ID are now available by sending.

SEELink Release Notes - 6.3.0Q1 8


SEELink Release Notes

Java

• .Shipped with the installation JDK is actualized to Java 7 Update 55

SEELink Release Notes - 6.3.0Q1 9


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

Windows

• Mapped network drives are not supported as file ports. Use network share(CIFS) functionality instead.
• 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 SEE 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.

Linux

• Linux Daemon installation has to be done manually using the provided scripts and instructions.

Solaris

• Actual JDK 7 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.
• If the user wants to run the JDK in x64 mode he must update /bin/"setenv.sh" adding "-d64" switch to java
executable options
• Installation as daemon service is not supported.

AIX

• Actual JDK 7 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.

SEELink Release Notes - 6.3.0Q1 10


SEELink Release Notes

• 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 1024 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.

Install/Update

• 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.
• The pre-configured alerting rules for the new features are available only by new installation.

Web Services

• Shipped with SEE Link 6.0.1Q1 FileTransferService is no longer supported. Instead use the newer SeeLi
nkFileTransferService

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

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

SEELink Release Notes - 6.3.0Q1 11


SEELink Release Notes

Backend integration

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

Roll-out

• Only SEE Link Manager 6.3.0Q1 can be used for the roll-out of SEE Link 6.3.0Q1 endpoints.

SEELink Release Notes - 6.3.0Q1 12

You might also like