SEEBURGER Release Notes for - SAP NW Exchange Infrastructure

SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
SEEBURGER Release Notes for
SAP NW Exchange Infrastructure
Release 1.8.2
June 1, 2010
Table of Contents
1 ReleaseNotes 1.7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1 Important
.................................................................................... 4
1.2 General
.................................................................................... 4
1.3 SEEBURGER Data Transmission Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.3.1 Common Adapter Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.3.2 OFTP Adapter (TCP/IP, ISDN, X.31) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3.3 EDIINT AS2 Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.3.4 EbXML HTTP Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
1.3.5 FTP Adapter (FTP and HostFTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
1.3.6 P7/X.400 Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3.7 EDIINT AS1 Adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
1.3.8 HTTP Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
1.3.9 SFTP Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
1.3.10 SeDeB2B Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
1.3.11 Adapter Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
1.4 SEEBURGER Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.4.1 Message Splitter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
1.4.2 CPA Cache Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
1.4.3 StartLocalUp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
1
1.4.4 AttribMapper. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
1.4.5 CharConversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
1.4.6 ReplaceStr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
1.4.7 Zip
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
1.4.8 PayloadInfo. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
1.4.9 PayloadDump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
1.4.10 MessageCleanup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
1.4.11 MessageDump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
1.4.12 Secunet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
1.4.13 Apsec Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
1.4.14 DSig
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
1.4.15 AttachmentRename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
1.4.16 Common . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
1.5 SEEBURGER Converter Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.5.1 Classifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
1.5.2 Converter Adapter/Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
1.5.3 SeeFunctions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
1.5.4 Mapping Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
1.6 SEEBURGER Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.6.1 EDIFACT Secure Authentication (AUTACK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
1.7 SEEBURGER Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1.7.1 Addressbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
1.7.2 Digital Signature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
1.7.3 Message ID Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
1.7.4 Message Splitter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
1.7.5 Message Archiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
1.7.6 Recovery Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
1.7.7 Resource Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
2
1.7.8 Mapping Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
1.8 SEEBURGER Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
1.9 Professional Message Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2 ReleaseNotes 1.8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Copyright (c) 2010 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 cause high costs.
Also consider configuration changes initiated by your telecommunication provider. SEEBURGER is
not liable for related additional costs.
Note: We expressly declare that the document "SEEBURGER Legal Information" (delivered also
with your BIS installation media) is part of this documentation.
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
3
1 ReleaseNotes 1.7
1.1 Important
•
•
•
•
Recovery jobs from adapter version 1.5 do not comply with version 1.7. So remove or process all
jobs that have been created by 1.5 versions before updating to v1.7.
Recovery jobs from v1.6 comply with v1.7.
However, whenever updating to a new major version (e.g. v1.6 to v1.7), ensure to complete all
recovery jobs beforehand by successfully processing them (by fixing configuration issues).
From 1.7Q3 on CommService port can be configured for adapters in Managed Connection Factory
and for the web applications (CommService, MessageIDMonitor) in Property Store. After
reconfiguration always restart the components in following order, or there can be occur problems
with monitoring!
•
•
•
CommService
MessageIDMonitor
Adapters
Attention: MaxDB 7.5 is no longer supported for Professional
MessageTracking!
With release 1.7.4, SEEBURGER Professional MessageTracking only supports Ma
xDB versions 7.6 and 7.7.
1.2 General
•
The Message Archiving solution is no longer part of the standard shipment and is only available as
a Professional Message Tracking solution.
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
4
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Scheduler [BUG#8954] has been fixed: In some cases, after modifying a communication channel,
alarms where no longer triggered. The following error can be found in the log: Alarm names must
be unique!. Alarm not added !
Fixed: Logging might cause extensive CPU usage, even with ERROR level.
Fixed: Memory leak in communication adapter framework.
Fixed: Recovery base prevent empty or corrupt (inbound) jobs.
Fixed [BUG#10909]: Removed properties from HTTP client which was responsible for extended
wire traces on system error output (defaultTrace).
Fixed [BUG#10769]: Simultaneous polling if more than 1 server processes exist, will lead to a
resource reservation error in one of them, which might be confusing. Starting with version 1.7, the
following text will be shown in the channel monitoring of one of the channels:
Skipping polling, another polling/reservation for the channel is active
Dynamic attributes are supported. Details are described in the adapter-specific manual.
Channel monitoring and CCMS alerting is supported.
MessageIdStore reorganization timeout has been reduced to 168 hours. After 7 days, finished
MessageIdStore entries are being removed. Furthermore this value is configurable for each
technical adapter using ManagedConnectionFactory properties (MCFs).
Fixed [BUG#12749]: java.util.ConcurrentModificationException could occur when modules or
adapters used SeeLogger (1.7Q2)
Fixed [BUG#13223]: Recovery - Now not reloading error job pool with every recover timer run
(1.7Q2)
Fixed [BUG#14387]: Channels that have been stopped using communication channel
monitoring/administration are now no longer used for polling and/or delivering messages to the
messaging system! (1.7Q3)
Fixed [BUG#14632]: CommService port can now be configured. This is necessary if more than
one XI instance is used on one host, for example. (1.7Q3)
Fixed [BUG#15410]: Restart of SmartiDS produced problems with adapters/modules using this
datasource. (1.7Q4)
Fixed [BUG#19625]: HP-UX installer did ship a wrong VM (Solution installer as well as the
MessageTracking installer). (1.7Q4)
Fixed [BUG#18988]: SEEBURGER CommService did not provide a data source alias and
therefore sometimes had no access to the database. (1.7Q4)
1.3 SEEBURGER Data Transmission Adapters
1.3.1 Common Adapter Changes
•
•
Fixed [BUG#13150]: Improved internal payload handling of data transmission adapters. (1.7Q3).
Fixed [BUG#14254]: Problems with recovery, e.g. full disk, have not been reported to the adapters
(1.7Q3).
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
5
•
•
•
•
•
•
•
•
•
•
•
Fixed [BUG#14674]: In some special cases CAPI listeners have not been reestablished after CAPI
reconnect (1.7Q3).
Fixed [BUG#15257], [BUG#15292]: On communication layer now also the data packages are
traced in DEBUG log level with enabled TransmissionDataDump (1.7Q3).
Fixed [BUG#15987]: When using dynamic attribute "dtAttachmentName" and the mentioned
attachment was not available, the MainDocument was used as fall back. This has been changed
to report an error in case the attachment is missing (1.7Q4).
Adapters with polling channels and listeners can now be stopped / started via the AAM channel
monitoring (1.7Q4).
The number of parallel output processing can now be configured for each adapter via the
ManagedConectionFactory property "QueueProcessors". The default has been set to 5 parallel
processor, according to the SAP advanced adapter framework (1.7Q4).
Fixed [BUG#16704]: Extended dynamic attribute support to recognize MainDocument for "
dtAttachmentName" (1.7Q4).
Fixed [BUG#16634]: Sometimes a NullPointerException was shown in the AAM monitoring due to
invalid message ids. This has been fixed (1.7Q4).
Fixed [BUG#16409]: On cluster scenarios, two cluster nodes might have generated the same
reservation ID, causing hanging reservations (1.7Q4).
Fixed [BUG#16410]: Fixed a problem, where at adapter restart an adapter did not only clean it's
own resource reservations, but also reservation from other adapters (1.7Q4).
Extended report handling to include the original XI message id within the header field "
refToMessageId" (1.7Q4).
Fixed [BUG#18097]: Fixed shutdown problem, when recovery was active while shutdown was
executed, causing unnecessary NullPointerExceptions (1.7Q4).
1.3.2 OFTP Adapter (TCP/IP, ISDN, X.31)
•
•
•
•
•
•
•
•
•
Fixed [BUG#8854]: TransferID not unique/Orders get rejected.
clusterMode config property added, when this property is set to ‘true’ for ISDN "another application
got that call messages" are reported only as warnings, for TCP by starting of the node "port
already in use" is reported only as warning.
Session pool implemented and session pool configuration properties added: defaultSize,
extendedSize, popInterval.
Fixed [BUG#9280]: Incomplete last record of FIX file not transferred.
Using new Message ID Store states and texts.
XI Message ID is now used as primary ID in Message ID Store for the incoming transfers, making
them search able.
When sending structured files (FIX and VARIABLE format) with EBCDIC encoding, OFTP now
recognizes and supports both line separators – CRLF (0D25) and CRLN (0D15).
When receiving structured files (variable format) with EBCDIC encoding, OFTP now uses LF (25)
as line delimiter.
Fixed [BUG#10590]: OFTP cannot use logical resource in receiver channels
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
6
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Added option for configuring MessageIdStore timeout with the messageIDStoreTimeout Managed
Connection Factory property.
Enhancement [BUG#10769]: If working with listeners, tracing out not only the channel ID, but also
party and service in case of errors.
Fixed [BUG#11022]: By receiving NERP, OFTP cannot lookup the originator and destinator
correctly: Trim the values.
Fixed [BUG#11169]: OFTP handles Throwable instead of exception hiding possible OutOfMemory
errors.
Fixed [BUG#11296]: OFTP sets pending correlation to error after successful transfer if the
connection is broken.
Fixed [BUG#11268]: Wrong channel shown in Message ID Monitor when receiving in some cases.
Fixed [BUG#11714]: ISDN Listener is now started if the MSN contains only digits (in case of
listening to a specific MSN).
Fixed [BUG#9956]: ISDN dialing prefix not used by adapter (1.7Q2).
Fixed [BUG#10885]: OFTP Channel Monitoring: Wrong Communication Channels shown by
receiving (1.7Q2).
Fixed [BUG#12367]: OFTP-XI-OFTP scenario not possible (1.7Q2).
Fixed [BUG#12550]: Received EERP with EERPDEST interchanged with EERPORIG(1.7Q2).
Fixed [BUG#12608]: EERP cannot be sent in the same session (1.7Q2).
Fixed [BUG#12343]: Error receiving EERP that cannot be correlated (1.7Q2).
Fixed [BUG#12876]: Problem by enabled dumping and retry in case of RestartPosition greater
than the size of the dump File (1.7Q2).
Fixed [BUG#13359]: Enhancements in channel monitoring by receiving files (1.7Q2).
Fixed [BUG#13494]: Enhancement in OFTP message id monitor overview. New options to select
entries with specific sender, receiver or subject/dataset name.
Fixed [BUG#12989]: If CAPI connection to the router was lost, there has been no automatic
reconnect after a certain number of retries (1.7Q2).
Fixed [BUG#13563]: Use more detailed error information about excessive record name (1.7Q3).
Fixed [BUG#13506]: Error message in adapter error monitor (1.7Q3).
Fixed [Bug#13902]: By receiving file with fix format, OFTP sends ESID instead of EFNA (1.7Q3).
Fixed [BUG#13903]: OFTP sends v2 formatted EFNA even when the protocol version in use is
lower than 2.0 (1.7Q3).
Fixed [BUG# 13904]: Invalid state after receiving EFNA message (1.7Q3).
Fixed [BUG#15248]: Reconfiguration by recovery of reports needed (1.7Q3).
Fixed [BUG#13751]: Physical disconnection problems when small OFTP session timeout is used
(1.7Q3).
Fixed [BUG#14351]: Problems with session pooling (1.7Q3).
Fixed [BUG#9494]: When incoming files are added as attachments with name "TransferInfo" the XI
message contained to attachments with the same name (1.7Q4).
Fixed [BUG#14343]: Added CAPI error codes to DataTransmissionGuide (1.7Q4).
Fixed [BUG#15608]: Incorrect MessageID store state when initiating via recovery fails (1.7Q4).
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
7
•
•
•
•
•
•
•
•
•
•
•
•
•
Fixed [BUG#16986]: OFTP was not able to use logical choice reservations (1.7Q4).
Fixed [BUG#17086]: Sending of files requesting reports without having report channels created
now fails. In case an incoming EERP cannot be initiated, the EERP will be recovered (1.7Q4).
Fixed [BUG#17293]: Fixed a problem, where OFTP reused a session which was still being
initiated to tie XI system (1.7Q4).
Fixed [BUG#17424], [BUG#17494]: Fixed listener startup/shutdown when OFTP is started/stopped
via the AAM channel monitoring (1.7Q4).
Fixed [BUG#18463], [BUG#18547], [BUG#18765]: Restart of CAPI produced problems with
reregistering the listeners. Retries for reconnect have been extended (1.7Q4).
Fixed [BUG#18353]: More descriptive error message if password is too long (1.7Q4).
Fixed [BUG#18588]: If no free OFTP sessions are available, OFTP does not release the already
acquired reservation (1.7Q4).
Fixed [BUG#18643]: If "Partner sends EERP" is not selected, received MDNs are not transmitted
to the XI system (1.7Q4).
Fixed [BUG#19305]: Socket to router remains open although there was an invalid user/password
specified (1.7Q4).
Fixed [BUG#15572]: Internal state variable of OFTP was not thread-safe, causing race conditions
(1.7Q4).
Fixed [BUG#16802]: Sometimes OFTP shows an exception in log, where it tries to close an
already closed socket (1.7Q4).
Fixed [BUG#18037]: Search for TransmissionReport channel was not done with the original
message's subject, causing only wildcard channels to be found (1.7Q4).
Fixed [BUG#18103]: Removed unnecessary NullPointerException, when no free resources are
available. (1.7Q4).
1.3.3 EDIINT AS2 Adapter
•
•
•
•
•
•
•
•
•
Added new column CorrelationID to MessageIDStoreMonitor Overview. The correlationID is
equivalent to the XI message ID.
Reduced memory usage and updated the AS2 adapter to handle large payload like 2GB or more.
Renamed SSL Certificate labels for sender and receiver channel.
Added keep alive flag to sender and receiver channel.
Fixed [BUG#10732]: Removed catching and processing of Throwable in module core which was
hiding possible OutOfMemory errors.
Message ID Store Monitor timeouts are now configurable over a Managed Connection Factory
property.
EDIFACT (UNB), ANSI (USA) and INHOUSE (block) split integrated into the adapter.
Fixed [BUG#12787]: AS2 now supports forwarding AS2 party -> XI -> AS2 party using the same XI
message ID (1.7Q2).
Fixed [BUG#12316]: AS2 TransmissionDataDump did not work, because dump directory
configuration was missing (1.7Q2).
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
8
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Fixed [BUG#13189]: Changing port range settings in Managed Connection Factory did not have
any effect (1.7Q2).
Fixed [BUG#13433]: Warning finishBackground called - ignored. Should not be used anymore! has
been shown. Removed method call that is not required (1.7Q3).
Fixed [BUG#13757]: Read timeout in server with chunked encoding (1.7Q2).
Problem:
If TransmissionDataDump is enabled, the adapter throws an exception when receiving large files
chunked encoded. The HTTP partner will get an internal server error. With this version, an
exception with chunked encoding will no longer occur.
Fixed [BUG#13669]: If, in Best Effort mode, a negative synchronous MDN is received by the
adapter, the XI message's status of is now set to Error (1.7Q2).
Fixed [BUG#10057]: If Content-Transfer-Encoding header has been missing, 7bit encoding has
been assumed to verify the signature. This has led to errors like “CMS error: invalid signature
format in message: content hash found in signed attributes different”. Now the default
Content-Transfer-Encoding, if header is missing, can be set to 7bit and binary (1.7Q3).
Fixed [BUG#14259]: AS2 initiated DtReports for failed incoming transfer/reception via wrong
channel (1.7Q3).
Fixed [BUG#14362]: Adapter internal Splitter did not support InhouseVDA, but Inhouse VDA
(1.7Q3).
Fixed [BUG#14523]: Some dynamic attributes have been missing in adapter metadata (1.7Q3).
Fixed [BUG#9339]: Wrong MessageIdStore state when initiate fails (1.7Q4).
Fixed [BUG#13165]: Payload missing in TransmissionDataDump (1.7Q4).
Fixed [BUG#16290], [BUG#18081]: AS2 does not shutdown correctly because of a race condition
when counting active tasks (1.7Q4).
Fixed [BUG#17542]: Fixed problem with report channels not being found due to a missing resolve
of the header mapping (1.7Q4).
Adjusted documentation: Restart of Adapter is required in case SSL settings are changed (1.7Q4).
Fixed [BUG#17697]: MDNs did contain two attachments with the same name, one containing the
raw MIME and one the DeliveryReport (XML) (1.7Q4).
Implemented restrictions on maximum incoming processes (return Internal Server Error 500, if too
many requests are coming in). This is configurable via the ManagedConnectionFactory and
applies adapter wide (1.7Q4).
Added the following three dynamic attributes to the adapter metadata, so they can be used within
a receiver determination:dtMsgType, dtAttachmentName, dtExternalMsgId (1.7Q4).
Fixed [BUG#18792]: Problems when receiving negative synchronous MDNs (1.7Q4).
Fixed [BUG#19439]: AS2 did not support a fall back from TLS to SSL in case the partners HTTP
server did not support TLS on IBM VMs (1.7Q4).
Fixed [BUG#20087]: Race condition, when receiving asynchronous MDNs too fast, the state is
reset to "Waiting for reports" (1.7Q4).
Fixed [BUG#15852]: Adapter-internal split did always initiate the split file as "MainDocument"
(1.7Q4).
Fixed [BUG#17857]: When adapter-internal block split is used, and file size exactly matches the
OutputBlockSize an unnecessary 0-byte attachment was generated (1.7Q4).
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
9
•
•
•
Fixed [BUG#18763]: Problem with adapter-internal split, when using UTF-8 as input encoding
(1.7Q4).
Fixed [BUG#18840]: Extended error messages if parameters for adapter-internal split are not
present (1.7Q4).
Added new dynamic attribute "dtExternalMsgId", to be able to set the AS2 message ID (outgoing)
and receive the AS2 message ID (incoming) (1.7Q4).
1.3.4 EbXML HTTP Adapter
•
•
New data transmission adapter (1.7Q2).
There are some restrictions for the EbXML HTTP Adapter:
•
•
•
•
•
•
•
•
•
•
•
•
Multi attachment handling is supported. You can send/receive one or several attachments.
Message ordering not supported.
Sending of ping messages not supported.
Sending of status request messages not supported.
Encoding of attachments not supported.
Fixed [BUG#14555]: It is now possible to configure SSL in the sender channel for outgoing
acknowledgments (1.7Q3).
Fixed [BUG#13152]: Outgoing transfers did not clean up a temporary file (1.7Q4).
EbXML Client caches SSL settings (SSL truststore, check hostname, etc.). The adapter needs to
be restarted, after such settings are changed!
Implemented restrictions on maximum incoming processes (return Internal Server Error 500, if too
many requests are coming in). This is configurable via the ManagedConnectionFactory and
applies adapter wide (1.7Q4).
Fixed [BUG#18078]: Race conditions with counting active tasks, which may block adapter
shutdown (1.7Q4).
Fixed [BUG#18974]: Race condition when receiving an acknowledgment before sending process
is finished. MessageID store entry remains in state PENDING (1.7Q4).
Fixed [BUG#18976]: Fixed class cast exception when trying to send an encrypted message
(1.7Q4).
1.3.5 FTP Adapter (FTP and HostFTP)
•
•
•
•
New Message ID Store states.
Fixed processing of IBMIE reports without messageId. Now FTP is able to process not only
standard reports (DISPATCHED, DISPLAYED, PURGED …) and also command status reports.
Fixed [BUG#8467]: Wrong usage of ErrorType.
Ecodex: Looking for ES* files and generate FAILED reports if they exist. This check is performed
before processing PS* files.
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
10
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Changed default scripts to use command put instead of mput for the following server types: MVS,
GeMarkIII, GeMark3000, IBMIE, ECODEX, EDISwitch and Sterling Commerce.
Forbidden script command mput for the following server types: MVS, EDISwitch, GeMarkIII,
GeMark3000, IBMIE and ECODEX.
(Only HostFTP:) Allow sending of all attachments from the task, if the mput command is used and
wildcards are specified in the HostPath.
(Only HostFTP:) Functionality to use wildcards in the path. The wildcards in the path are resolved
by the FTP adapter with necessary number of recursive FTP server listings. The way to use
wildcards in the path is provided by a new script command rmge.
Fix GeMark pattern to allow non-digit symbols in the IC Control#.
Using XI messageId as a correlationId on the task for Outbound case. For easy correlation
between XI and SEEBURGER monitoring.
Channel monitoring is supported.
Dynamic attributes are supported.
Outbound –FTP can use dtSubject dynamic attribute as a HostPath and dtAttachmentName as an
Attachment name.
Inbound: Besides the common attributes, FTP adds VAN-specific attributes. The complete
information that FTP extracts for VAN message (IBM IE, ECODEX, GeMark, EDISwitch and
SterlingCommerce) and VAN report (IBM IE, ECODEX and GeMark) will be added to the XI
message as specific attributes.
Added option for port range specification for active connection mode (both for Outbound and
Inbound case).
Fixed memory leak if Deliver transmission report is not chosen.
Fixed [BUG#13812]: FTP adapter did not detect all errors (1.7Q3)
Added option to configure Message ID Store timeout with the messageIDStoreTimeout MCF
property.
Fixed some composite address errors with IBM Information Exchange.
Fixed [BUG#12388]: FTP did not get all files from GeMarkIII mailbox due to non matching pattern
(1.7Q2).
Fixed [BUG#12505]: Now printing reports of GeMark3000, GeMarkIII, IBM IE and ECODEX in
FTP log (1.7Q2).
Fixed [BUG#12506]: Now using check for length of user message class due to restrictions of IBM
IE (1.7Q2).
Note: The FTP lock file feature only prevents multiple uploads and downloads while upload is
present. It does not prevent multiple downloads of the same file! See adjusted manual for more
informations (1.7Q4).
Fixed [BUG#18848]:AAM channel monitoring shows report channels as inactive (1.7Q4).
1.3.6 P7/X.400 Adapter
•
Fixed [BUG#9485]: Problems while receiving large messages solved.
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
11
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Fixed [BUG#10024]: There was a problem with incoming messages that have no originator
address within the IPM part of the message. A X.400 message contains two parts, an envelope
and the IPM message. Each part contains information about the x.400 address of the originator,
but within the IPM, this information is optional. Currently, the P7 adapter wants to read the
information from the IPM and fails with a NullPointerException if the information is missing. This
has been fixed.
New feature: The external message ID set by the provider is now visible within the Message ID
Monitor for incoming and outgoing messages. This improves monitoring capabilities.
Fixed [BUG#10392]: P7 receives files form the mailbox, initiates them to XI and deletes them from
the mailbox. This behavior has been changed since the inbound channel processing might be
lasting too long, the message then causes connection timeouts before the message has been
deleted from the mailbox. Another node that is polling the same mailbox can receive the same
message twice. This behavior was changed, so the message is deleted from mailbox before
initiation starts. For that case, it is important to check your system for the existence of some
recovery jobs before updating to this new version! Otherwise, it may occur that a message will be
processed twice.
The timeout value that specifies the adapter's waiting interval for reports and/or notifications can
now be changed via the J2EE Admin. Go to the service ConnectorContainer and select the
X400P7 adapter. Go to the tab ManagedConnectionFactory and then to the sub-tab Properties.
Now the messageIDStoreTimeout property's value can be changed accordingly.
Fixed [BUG#10736]: Fixed memory leak.
Fixed [BUG#10946]: If there is a recovery job for an incoming message, the immediate sending of
notifications does not work.
Fixed [BUG#11656]: P7 failed polling caused by problems with delivery reports from the 400net
(c=NL; A=400net) VAN.
Fixed [BUG#11606]: In case of non-delivery reports the x400p7 adapter does not show a negative
state in the messageidstore monitor - instead "correlated report" is shown.
Fixed [BUG#11753]: P7 request for a delivery-report AND a non-delivery-report. This is not
allowed due to some X.400 restrictions.
Fixed [BUG#10916]: The P7 channel configuration does not longer allow the invalid combination
with TCP/ISDN as transport protocol and “virtual inbound” as message protocol.
Fixed [BUG#12865]: P7 checks for duplicates with identical ID. This can be disabled with a new
attribute within the inbound channel. If the check is active duplicates will be stored within the
…/seeburger/x400p7/duplicates folder. If the check is deactivated the messages will be initiated to
the XI system.
Fixed [BUG#13401]: Received DTReport will now contain the original XI message ID within the
requestMessageId key (1.7Q3).
Fixed [BUG#11134]: Fixed memory leak with undeleted recovery objects (1.7Q2).
Fixed [BUG#12989]: If CAPI connection to router was lost, there has been no automatic reconnect
after certain number of retries (1.7Q2).
Fixed [BUG#10390]: Now sender and receiver parties are shown in Message ID Monitor (1.7Q3).
Fixed [BUG#14826]: Seeburger P7 does not support NonReceiptNotifications. If partner requested
such a notification, Message ID state has been set to "Waiting for delivery-, receipt- or both reports
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
12
•
•
•
•
•
•
•
•
•
•
•
" and never been set to success, because NonReceiptNotifications has never been sent to partner
(1.7Q3).
Fixed [BUG#12552]: XI MessageID was not available within MessageID monitor (1.7Q4).
Fixed [BUG#13293]: Recovered duplicate messages did not get recognized as duplicates, but
rather as new messages and were therefore initiated (1.7Q4).
Fixed [BUG#13401]: DtReport did not contain the XI message ID (1.7Q4).
Fixed [BUG#15771]: Improved error message to contain more detailed error descriptions instead
of the common "InvocationTargetException" (1.7Q4).
Fixed [BUG#15835]: Check if the message is deleted on the tele-box caused an error message on
provider side, this has been fixed (1.7Q4).
Fixed [BUG#16584]: When recovering failed messages, the adapter did not do the party lookup
again (1.7Q4).
Fixed [BUG#16929]: No X400.P7 shutdown possible after recovery of reports (1.7Q4).
Fixed [BUG#17061], [BUG#19726]: Added XI Message ID of original message to the
TransmissionReport (1.7Q4).
Fixed [BUG#17713]: Added message in AAM channel monitoring for received duplicates (1.7Q4).
Fixed [BUG#18157]: P7 was not able to send attachments bigger than 1MB (1.7Q4).
Fixed [BUG#19321]: P7 was not able to read constructed IA5 text (text, which is sent in more than
one block) (1.7Q4).
1.3.7 EDIINT AS1 Adapter
•
•
•
•
Using XI messageID as correlationID in outbound case for easy correlation between XI and
SEEBURGER monitoring.
Dynamic attributes: Besides the common dynamic attributes, the XIAS1 adapter also uses:
content-type, sender address, recipient address, payload name.
Added option for configuration of Message ID Store timeout with the new messageIDStoreTimeout
MCF property.
Fixed [BUG#10722]: There was a wrong usage of infinite timeouts.
1.3.8 HTTP Adapter
•
•
•
•
New data transmission adapter that supports the HTTP protocol (1.7Q2).
Implemented restrictions on maximum incoming processes (return Internal Server Error 500, if too
many requests are coming in). This is configurable via the ManagedConnectionFactory and
applies adapter wide (1.7Q4).
Note: If SSL settings within the communication channel are changed, the adapter needs to be
restarted in order to recognize the new settings!
Fixed [BUG#18687]: When long running HTTP download tasks exceeded the polling interval, the
internal task queue would fill up (1.7Q4).
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
13
1.3.9 SFTP Adapter
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
RSA is only supported in version 4.0.
New data transmission adapter that supports the SFTP protocol (1.7).
Fixed [BUG#13626]: Updated field <Type> in meta data (1.7Q2).
Fixed [BUG#11253]: Now polling in cluster using a logical resource is possible (1.7Q2).
Fixed [BUG#10892] Connection pool fixed, pooling activated, MCF property connectionTimeout
added, prevented closing of clients from outside the pool (1.7Q3).
Fixed [BUG#13841]: Removed STAT call after PUT, file details are generated differently now
(1.7Q3).
Fixed [BUG#15195]: Add JCE unlimited strength check (1.7Q3).
Fixed [BUG#15108]: Added support for AES256-CBC (1.7Q3).
Fixed [BUG#14619]: Problem by multiple polling (1.7Q3).
Fixed [BUG#14833]: RSA FIPS provider cannot initialize (1.7Q3).
Fixed [BUG#15043]: Configuration flag "Deliver transmission report" is missing (1.7Q3).
Fixed [BUG#14681]: Wrong upload if directory not existing (1.7Q3).
Fixed [BUG#14554]: SFTP-Client unable to continue recovery task (1.7Q3).
Fixed [BUG#14494]: Remote filename in response differs from real filename when using SFTP
(1.7Q3).
Fixed [BUG#14960]: Master data: directories are not trimmed (1.7Q3).
Fixed [BUG#14167]: Now using Maverick API 1.3.10 (1.7Q3).
Fixed [BUG#14346]: SFTP now supports “Service Without Party” (1.7Q3).
Fixed [BUG#14471]: Added connection pooling (1.7Q3).
Fixed [BUG#13489]: Message to check the pending keystore was shown before the actual entry
was created, so the actual error message (could not create pending keystore entry) was not visible
(1.7Q4).
Updated underlying Maverick SFTP API to 1.4.3 for better performance.
Fixed [BUG#16185]: Announce SFTP v3 to the partners, as we do not fully support SFTP v4
(1.7Q4).
Fixed [BUG#16227]: A transmission report was always generated, regardless of channel
configuration (1.7Q4).
Fixed [BUG#16896]: Connection might be reset during large file transfers (1.7Q4).
Fixed [BUG#18107]: If no filename is given for sending files, a unique filename will be generated
(1.7Q4).
Fixed [BUG#18321]: Added missing link between recover jobs and MessageID monitor (1.7Q4).
Fixed [BUG#15465]: Password was logged in plain text. Has been removed (1.7Q4).
1.3.10 SeDeB2B Adapter
•
Fixed [BUG#19176]: Sending of MainDocument was not possible (1.7Q4).
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
14
1.3.11 Adapter Metadata
•
Fixed [BUG#11585], [BUG#11636]: Removed warnings when importing meta data to Integration
Repository in newer SPs (1.7Q2).
1.4 SEEBURGER Modules
1.4.1 Message Splitter
•
•
•
•
•
•
•
•
•
•
•
•
•
Added new column check, which displays the validity of the entry in front-end.
Name space is now displayed when editing entries.
Fixed handling of sender agreements that have wildcards for receiver party and receiver service.
Added copying of dynamic attributes (parameter attributeCopyList ) as a semicolon separated list
of dynamic attributes.
Added attributeCopyList to copy dynamic attributes from the original message (parent) to the split
message (child) (1.7Q1).
Fixed [BUG#11995]: Splitter had problems after restart of com.sap.aii.af.app application without
restart of the J2EE engine (1.7Q1).
Changed order of configuration entry creation to lower maintenance times. Drop-down lists sorting
is case-insensitive now (1.7Q2).
Fixed [BUG#12945]: Splitter is now able to split also a business document (MainDocument)
(1.7Q2).
Fixed [BUG#13255]: If multiple splitter modules work on identical XI message ID, and the same
module key for splitter module is used, duplicates have been recognized. This does no longer
occur, as long as same module key is used only once in a channel and parameter for multiple
splits is set (1.7Q2).
Fixed [BUG#13033]: Splitter front-end did not show all available bindings for a channel, but only
last one, that has been created. Thus, usage of multiple bindings for one channel was not possible
(1.7Q2).
Fixed [BUG#14418]: Splitter could corrupt encodings of split files. Now, automatic UTF-8
conversion can be disabled (1.7Q3).
Fixed [BUG#17368]: Display an error, if the module parameter key (used in the communication
channel configuration) is too long, to be used as part of a message id. (1.7Q4).
Fixed [BUG#17712], [BUG#19605]: Error messages for missing splitter configurations have been
extended to be more clear (1.7Q4).
1.4.2 CPA Cache Search
•
New component for searching communication channels.
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
15
1.4.3 StartLocalUp
•
•
•
Manual: Added appendix that describes application of Apache-FOP.
New feature: Added support for dynamic attributes.
New feature: Added sweepFiles setting for deletion of created files.
1.4.4 AttribMapper
•
•
•
New component to execute dynamic attribute “mappings” and settings.
Added function equals(String, String) (1.7Q2).
Added function equalsIgnoreCase (String, String) (1.7Q2).
1.4.5 CharConversion
•
•
•
New module: Added dynamic attributes.
Fixed: Default value in case of sourceEncExp mismatch has been regular expression instead of
value of sourceEnc.
Fixed [BUG#17936]: cfgPayloadExclusiveSet was not interpreted correctly. When not present the
adapter did use no encodings instead of all encodings (1.7Q4).
1.4.6 ReplaceStr
•
•
New module for replacing parts of strings within payloads.
Fixed [BUG#13995]: It was not possible to replace character sequences with new line characters
(1.7Q2).
1.4.7 Zip
•
•
•
•
•
•
•
New feature: Added dynamic attributes.
Fixed [BUG#13213]: useAttribIfSet was not used correctly (1.7Q2).
Fixed [BUG#13214]: Now also reading multiple sources if using dynamic configuration (1.7Q2).
Fixed [BUG#13216]: Now zipping also in GZIP format (1.7Q2).
Fixed [BUG#13224]: Now overwriting target destination if exists (1.7Q2).
Fixed [BUG#13295]: Now recognizing GZIP files correctly in unzip mode (1.7Q2).
Fixed [BUG#16312]: Parameter "mode" can now be set via dynamic attributes (1.7Q4).
1.4.8 PayloadInfo
•
New feature: Added dynamic attributes (1.7Q2).
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
16
•
•
•
Fixed [BUG#13362]: Now writing also to trace file; now writing also message properties (1.7Q2).
Fixed [BUG#12374]: Now using prefix SEEBURGER/PAYLOADINFO: in Audit Log (1.7Q2).
Fixed [BUG#16020]: Added parameter "failOnError" to throw an error in case of problems and use
the system's retry mechanisms (1.7Q4).
1.4.9 PayloadDump
•
Fixed [BUG#16018]: Added parameter "failOnError" to throw an error in case of problems and use
the system's retry mechanisms (1.7Q4).
1.4.10 MessageCleanup
•
•
New component for deleting payloads/attachments from XI message (1.7Q2).
Fixed [BUG#15242]: Attachments which shall be kept are now ordered in the order of the keep
parameters, so that XI MIME message structure can be changed (1.7Q3).
1.4.11 MessageDump
•
•
New component for dumping XI message to file system for debugging purposes (1.7Q2).
Fixed [BUG#14434]: Added parameter "failOnError" to throw an error in case of problems and use
the system's retry mechanisms (1.7Q4).
1.4.12 Secunet
•
•
•
•
New component for generation and verification of detached PKCS#7 signatures of EDIFACT files
(1.7Q2).
Enhancement [BUG#14140]: Support for new XML protocols of Secunet server (1.7Q3).
Fixed [BUG#15302]: In some constellations with network shares and/or mount points, the protocol
file of the Secunet server could not be read properly. Now there is an improved check for
availability (1.7Q3).
Fixed [BUG#16211]: Sometimes the Secunet module did not wait for the complete signature to be
written, which could cause empty or invalid signatures. Now the module waits until no more data is
written (1.7Q4).
1.4.13 Apsec Module
•
This new component generates and verifies detached PKCS#7 signatures of EDIFACT files in
cooperation with Apsec fideAS sign and fideAS verify products (1.7Q4).
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
17
1.4.14 DSig
•
•
•
•
New component used in combination with different other modules (e.g. Secunet module) for
generation and verification of digital signatures of EDIFACT files (1.7Q2).
DSig Info XSD has changed (1.7Q3).
Fixed [BUG#15412]: Problems during deployment of DSig module on some SPs (1.7Q3).
Fixed [BUG#15394]: Fixed values for mode parameter (1.7Q3).
1.4.15 AttachmentRename
•
Fixed [BUG#19485]: Now setting also Content-Description and explicit Content-Type (1.7Q4).
1.4.16 Common
•
•
•
Fixed [BUG#12488]: skipExecution parameter did not resolve dynamic attributes (1.7Q2).
Fixed [BUG#12881]: Logging via location controllers did not work (1.7Q2).
Added feature to use expressions for module parameter values in module chain. Expressions are
the same as known from AttribMapper (1.7Q2).
1.5 SEEBURGER Converter Suite
1.5.1 Classifier
•
•
This module can now deal with empty files. The new parameter errorIfEmpty has been added for
backwards compatibility.
Fixed [BUG#10749]: BIC does not support encoding SeeCp500. If Classifier module detects
encoding SeeCp500, the classifier output can now be changed to Cp500 instead of SeeCp500.
The new behavior can be enabled by setting corresponding module parameter (1.7Q3).
1.5.2 Converter Adapter/Module
•
•
•
•
•
Mappings_partner.sda must be deployed before the adapter. This file provides additional
capabilities to deploy mappings.
Fixed [BUG#11223]: Fixed some problems with dynamic attributes in BIC module (1.7Q2).
Fixed [BUG#13532]: Fixed key detection for Inhouse files with encodings like EBCDIC (1.7Q2).
Fixed [BUG#13723]: getTime returned values with preceding question mark (?) (1.7Q2).
Fixed [BUG#13956]: Since dynamic configuration for modules has been introduced, BIC module
parameter values have been trimmed: Sometimes this caused corrupt delimiter expressions
(1.7Q2).
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
18
•
•
•
•
•
•
•
•
•
•
Fixed [BUG#14085]: SWIFT messages with multiple field delimiters have not been parsed
correctly (1.7Q3).
Fixed [BUG#14128]: BIC runtime had a problem when EDIFACT/ANSI X12/TRADACOMS/CSV
messages with key fields have been used (1.7Q3).
Fixed [BUG#14339]: BIC runtime (EDIFACT low level reader) had a problem with space delimiters
(1.7Q3).
Fixed [BUG#15186]: BIC runtime ignored range settings in message description that contain
decimal separator "." (1.7Q3).
Fixed [BUG#14521]: BIC did not get a connection to the SmartiDS datasource (1.7Q4).
Fixed [BUG#15697]: If saveSourceMsg pointed to an already existing attachment, this attachment
was not overwritten, but instead a second attachment with the same name was added to the XI
message (1.7Q4).
Fixed [BUG#18191]: InhouseVDA MainMapping contained an error, when a mandatory field was
missing (1.7Q4).
Fixed [BUG#18720]: Fixed possible problems in SWIFT messages, which have text fields starting
with "-" (1.7Q4).
Fixed [BUG#19273]: Fixed endless loop when analyzing Edifact messages when using an IBM VM
and default encoding UTF-8 (1.7Q4).
Fixed [BUG#17995]: Fixed problems in the See_Edifact main mapping, when UNG segments are
present (1.7Q4).
1.5.3 SeeFunctions
•
Fixed [BUG#14992]: SeeFunctionsXITables.sda within SeeXIExtendedTools.sca could not be
deployed on SP14 due to following error "the location defined in the component element does not
fit to the location attribute" (1.7Q3).
1.5.4 Mapping Designer
•
•
New feature to create a Mappings_partner.sda from JCN files.
Fixed [BUG#12747]: Fixed problem with segment hierarchy of CREATE commands in mapping
X2E_ORDRSP_D96A (1.7Q2).
1.6 SEEBURGER Solutions
1.6.1 EDIFACT Secure Authentication (AUTACK)
•
•
Fixed [BUG#12696]: Verification fails with padding ISO-9796-2 (scheme 2) and RSA keys (1.7Q2).
Fixed [BUG#13681]: Serial number of certificate missing in USC in AUTACK template (1.7Q2).
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
19
•
•
•
•
•
Enhancement [BUG#11898]: CRL handling implemented: local and remote CRL URL are
supported (1.7Q2).
Enhancement [BUG#11901]: Embedded Signature verification reports for XI (1.7Q2).
Fixed [BUG#13804]: EDIFACT Secure module now supports dynamic attributes (1.7Q2).
Fixed [BUG#14110]: Fixed memory leak in EDIFACT Secure (1.7Q2)
Fixed [BUG#15352]: Service startup blocked until data source was available. Now database
access is loaded asynchronous (1.7Q4).
1.7 SEEBURGER Workbench
1.7.1 Addressbook
•
•
•
•
•
Fixed [BUG#13526]: Entry creation failed with “
com.seeburger.xi.addressbook.AddressbookException: Implicit MessageIdHandler exception:
SQLException while adding MessageId”. This happened if you tried to create an entry for an
existing address book directly after you called an entry for an address book that was not installed
(1.7Q2).
Fixed [BUG#13731]: Addressbook could not be used concurrently by different client applications
(browsers) (1.7Q2).
Fixed [BUG#13733]: New button disappeared and did not re-appear in some special cases
(1.7Q2).
Fixed [BUG#13756]: Tool tips are shown in wrong position (1.7Q2).
Fixed [BUG#17006]: Fixed "session invalid" errors when opening an address book entry (1.7Q4).
1.7.2 Digital Signature
•
•
•
•
•
•
•
New front-end for digital signature. Used in combination with new DSig and Secunet modules
(1.7Q2).
Fixed [BUG#16031]: Fixed sorting on import window (1.7Q4).
Rearranged order of DSIG menu entries, to match the order in with items have to be added
(because of references to each other) (1.7Q4).
Fixed [BUG#16194]: Invalid characters used in text fields could cause missing entries within the
overview (1.7Q4).
Fixed [BUG#16197]: Replaced check boxes for accepted signers with different icons, as these
check boxes were not click-able (1.7Q4).
Fixed [BUG#18796]: Front-end cached database tables, not always showing the real values
(1.7Q4).
Fixed [BUG#18806]: Extended database columns for accepted signers (1.7Q4).
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
20
1.7.3 Message ID Monitor
•
•
•
•
•
•
•
•
•
New feature: Searching for message IDs
Fixed [BUG#10844]: No feature for sorting entries by sender, receiver and subject for OFTP.
Fixed [BUG#10322]: Now showing correlation ID and time stamp in details view for AS2 (1.7Q2).
Fixed [BUG#11599]: Now using state INITIATING in AS2 if initiation to back-end fails (1.7Q2).
Fixed [BUG#13260], [BUG# 13261] and [BUG#13263]: After update from 1.6.x to 1.7.x states of
older transmissions have been shown as UNKNOWN (1.7Q2).
Fixed [BUG#10956]: Removed error message Delete was executed but did not affect exactly one
row, but 0 rows! (1.7Q2)
Fixed [BUG#10941]: Call for CommService start has been called twice. So message Service
already running occurred in logs (1.7Q3).
Fixed [BUG#14788]: CommService port can now be configured for Message ID Monitor and
Recover Monitor via Property Store and Managed Connection Factory (1.7Q3).
Fixed [BUG#18735]: Check input values for date and time (1.7Q4).
1.7.4 Message Splitter
•
•
•
•
Some changes in layout due to performance improvements. See also Message Splitter module
(1.7Q2).
Enhancement [BUG#15291]: Added additional fields for name and description. Added copy and
search functionality. Added buttons for quick deletion of single entries. Now displaying also sender
party (1.7Q3).
Fixed [BUG#15556]: Added sanity checks for input values (1.7Q4).
Fixed [BUG#19757]: If an entry is opened and saved, a duplicate entry was reported (1.7Q4).
1.7.5 Message Archiving
•
•
•
•
•
Message Archiving is no longer part of the SAP XI solution CDs. Instead, this module is delivered
with the Professional Message Tracking Solution of SEEBURGER AG. If you are a new customer
and you need this functionality, please contact SEEBURGER Sales to get more information.
Customers who already purchased an older solution (e.g. v1.3 – v1.6) are allowed to use the
Message Archiving module furthermore.
MT-API (Java): The method MTMasterXI.writeRecord() now implicitly sets the MessgeID and
DocumentID.
MT-API (Java): A new method MTMasterXI.setParent() is available that accepts the XI MessageID
and MT DocumentID as parameters.
MT-API (Java): A new method MTDetailXI.writeRecord() is available that accepts the XI
MessageID and MT DocumentID as parameters.
MT-API (Java): New methods have been added to set/get the master and detail fields more
conveniently: Now it is possible to write master.setFree1(“value”) instead of
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
21
•
master.setField(MTMasterXI.FREE1, “value”); the old setField()/getField() methods are still
available.
Former Message Archiving is now called Message Tracking in SEEBURGER workbench.
1.7.6 Recovery Monitor
•
•
•
•
•
•
Increased performance.
Added sorting and filtering features.
Jobs can now be deleted using the monitor.
Added link from recovery monitor to messageid-store-monitor.
Fixed Attachment Loader to work also in clustered environment.
Fixed [BUG#13755]: Fixed manual restart of max retry reached jobs (1.7Q2).
Problem:
Jobs are not moved from max retry directory to pool directory. The result are duplicate files on the
file system. The recovery monitor still shows one single job. This is no critical bug because the two
jobs are not executed twice, and no data is lost.
1.7.7 Resource Management
•
Fixed [BUG#16302]: Show reservation ID within the reservation monitor.
1.7.8 Mapping Variables
•
Fixed [BUG#18732], [BUG#18733], [BUG#18812]:: Added check for maximum field lengths in the
variables front-end (1.7Q4).
1.8 SEEBURGER Content
•
•
•
•
•
•
•
•
Content Guide is now solution-specific.
Each solution CD contains a Message Catalog with a lot of message descriptions for several
message formats (EDIFACT, ANSI, ODETTE, SWIFT, etc. For more details, please read the
corresponding SAPXI_ContentGuide_<solution>_en.pdf manual.
The FunctionalAcknowledgment document uses changed acknowledgment codes for
accepted/rejected; instead of 7 (accepted) ‘A’ and instead of 4 (rejected) ‘R’ is used for EDIFACT
use cases.
Fixed: Counter have not been working correctly in VDA Split use cases.
Added: Lookup of mappingName in case of partner mappings can be done using the database.
New feature: ANSI: Interchange number is now being set.
Child mappings are using UTF-8 as default destination encoding.
Removed VDA4913 Guide
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
22
•
Fixed [BUG#12872]: On some solutions, file
XI3_0_SEEBURGER_EDI_ADAPTER_3.0_of_Seeburger.tpz was missing (1.7Q2).
1.9 Professional Message Tracking
•
•
•
Professional Message Tracking doesn’t support DB2 databases that are running on AS400.
There are some known issues about MT installer for Linux on some special Linux distributions.
Please refer to the SEEBURGER Knowledge Base and the SAP Notes for more information and
applicable workarounds.
FileStore Module now uses additional table-columns/fields (take care if you are currently using
them) for storage:
•
•
•
•
•
cPartner (XI Sender/Receiver - depends on direction)
cFree1 (XI Sender)
cFree2 (XI Receiver)
cMessageSize
cProcessingTimeStart (on record creation)
•
The FileStore module will not write the new fields if the module parameter “metadataMode” is set
to the value “1.6”.
•
Fixed [BUG#15028]: Additionally the “metadataMode” can now be set globally for all FileStore
module calls in Property Store, so that mass changes, e.g. when updating from 1.6.x to 1.7.x, can
be avoided (1.7Q3).
A new archiving status EXPORTED has been introduced. Its meaning is the same of the old
“ARCHIVED” status. On a database update from a previous release all existing records with
archiving status ARCHIVING will be set to EXPORTED. The meaning of the – now optional archiving status ARCHIVED is now File has been successfully imported by external archiving
system.
The users “xiuser” and “xiadmin” and their respective roles XIUSER and XIADMIN are now
deprecated and may be removed from future releases. Use MTUSER and MTADMIN instead.
On update from a previous release the existing search and result profiles will not be changed. To
use the new default profile of release 1.7 you have to manually import the file
data/MessageTracking/examples/default-profile.xml.
Fixed [BUG#12564]: Logo updated (1.7Q2).
Fixed [BUG#12683]: A value in e.g. cFree1 like "Name" <email@address.com> has been
displayed as "Name" in the front-end (1.7Q2).
Fixed [BUG#13769]: When big amount of entries, an error could occur. Now sorting is only
possible for less than 1000 entries. I.e. the number of results that have to be sorted must be
reduced by application of search filters (1.7Q2).
•
•
•
•
•
•
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
23
•
•
•
•
•
•
•
•
•
Fixed [BUG#13907]: It was not possible in MT installer to use different IDs for Database ID and
SAP System ID (1.7Q2).
Professional Message Tracking web application has been updated. This update includes several
changes in look and usage of front-end. Main aspect has been a performance improvement
(1.7Q3).
Fixed [BUG#15437]: Updated reference to SmartiDS (1.7Q3).
Fixed [BUG#17315]: On newer MaxDB/SapDB (>7.6.00) versions, it was not applicable to add
members to groups due to database exception
com.sap.dbtech.jdbc.exceptions.DatabaseException: [-8013] (at 590): Order column must be
output column (1.7Q4).
Fixed [BUG#12193]: Added missing translations for SmartiAdmin (1.7Q4).
Fixed [BUG#13020]: Disabled default SQL logging (1.7Q4).
Fixed [BUG#15954]: MT-Installer on Linux did ship a 64-bit Java VM and had a problem with
executing the createDB.sh script (1.7Q4).
New feature: Added parameter for Consolidator "RELOADCHILDREN". When set to 1, childrens
are recounted (1.7Q4).
Fixed [BUG#16116]: Microsoft SQL-Driver for MSSQL did not work (1.7Q4).
Attention: Do not use the Microsoft SQL-Driver for the database installation.
Use the default jtds-driver for MSSQL databases.
•
•
•
•
•
Known Issue: [BUG#20083] Groups are not supported on Oracle 9.2 (as of 1.7Q4).
Fixed [BUG#17452]: Added Base- and ExtendedTools to standard Professional MessageTracking
solution (1.7Q4).
Fixed [BUG#16890]: Fixed AIX installer (1.7Q4).
Fixed [BUG#17067]: Horizontal scrollbar was hidden under buttons on Firefox (1.7Q4).
Fixed [BUG#17119]: Configuration of profiles did not work on Internet Explorer 6 (1.7Q4).
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
24
2 ReleaseNotes 1.8
Important
•
•
•
•
•
We strongly recommend finishing all active recovery jobs before updating from previous releases.
Remove the existing commservice application prior to deployment of the latest release (keyname
com.seeburger.xi.webapp.commservice).
Read the complete Release Notes before starting deployment /installation of component of this
release.
The Utility Solution's content has been corrected; i.e. FTP now replaces (the previously shipped)
OFTP.
All SEEBURGER modules now add a MessagingException as cause for ModuleExceptions since
1.8Q2. This allows the SAP file adapter to archive erroneous messages.
General
•
The recovery mechanism for technical SEEBURGER adapters has been reworked to ensure
improved cluster support. Recovery jobs which have been created by a specific J2EE server node
can be processed by another server node if the original node crashes. Major improvements have
been implemented to ensure recovery monitoring and stability.
Note: Please ensure to share the ${sys.global.dir}/seeburger directory on all server
nodes within the cluster. On Unix this directory can be mounted to a shared file
system for example. (${sys.global.dir} usually resolves to /usr/sap/<SID>
/SYS/global, but it is possible to configure it differently, e.g use a UNC path on
Windows).
•
The BIC Runtime and BIC Mapping Designer modules have been improved in order to provide a
deployment concept that allows development of mappings on multiple Mapping Designer
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
25
•
•
•
installation without interference of the individual deployment files. 20 independent mapping user
deployment files can be generated by BIC Mapping Designer; thus allowing independent
development. See the BIC Mapping Designer Configuration Guide for details.
New feature: The SEEBURGER workbench contains now the application System status. It can be
used to collect relevant information for SEEBURGER technical adapters and modules. The
displayed data contains a list of deployed mappings.
Known Issue: During deployment of the Extended Tools, a deployment warning might be displayed
(Error occurred while starting application seeburger.com/SeeFunctionsEar ...). It has no negative
impact on overall deployment status. The affected application will be started automatically as soon
as all dependencies are available (deployed).
Updated readme.txt files which are shipped with each solution (1.8Q1). Master Installation Guide
Added details about importing content into SLD and Repository.
SEEBURGER Workbench
•
•
•
•
•
•
•
Fixed bug #16031: Sorting within the Import window did not work correctly.
Improved data selection for SEEBURGER Workbench import/export functionality.
Improved Message Splitter Configuration to allow adding meta-information for searching and
organizing entries.
Fixed Bug # 18099: Front-ends should export to and import from the global directory (sys/global/)
(1.8Q1).
Fixed Bug#22079: search pattern does work with umlaut (1.8Q2)
Fixed Bug#21347: browser compatibility for "select all" of "import/export" (1.8Q2)
Fixed Bug#18739: Workbench: pattern for filtering not unique (1.8Q2)
SEEBURGER Workbench Mapping Variables
•
•
•
•
•
•
•
Added input checks.
Fixed Bug # 19616: Implement Delete button for each entry ( 1.8Q1). Fixed Bug # 20768: SeeFunctions multi-variable column Info1 should be displayed as Info1
(1.8Q1). Fixed Bug # 20770: Deletion of entries with special characters (like backslash, etc) does not work
(1.8Q1). Fixed Bug # 21038: Functions front-end shows max 100 multi-variables and max 1000
variables/counters (1.8Q1). Fixed Bug # 21180: Multi value variable: In case of missing input wrong field name is displayed
(1.8Q1). Fixed Bug # 21390: Add "group"-column for SeeFunctions-front-end (1.8Q1). SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
26
•
•
Fixed Bug#21729: Extend Mapping variables frontend export with group selection (1.8Q2)
Fixed Bug#22337: ORA-01000: maximum open cursors exceeded (1.8Q2)
SEEBURGER Workbench Message Monitor
•
•
•
Added input checks for date/time values.
Fixed Bug#13933: manual: added note about filters in MIDstore (1.8Q1).
Fixed Bug#26306: MessageIdMontor: Search for primaryId does not work in all adapters (1.8Q2)
SEEBURGER Workbench Address Book
•
•
Fixed Bug#13731: Address book cannot be used concurrently.
Fixed Bug#22515: Addressbook exports all tables but fails on import if table is not deployed
(1.8Q2)
System Status
•
•
•
•
New part of SEEBURGER Workbench which shows a short overview of current system status for
monitoring and debugging purposes.
Fixed Bug # 20987: System Status does not work without BIC (1.8Q1). Enhancement Bug # 21069: System Status Front-end - Policy file check added (1.8Q1). Fixed Bug # 21103: MappingInfoList not deleted if BIC is un-deployed, List not updated upon new
mapping deployment (1.8Q1). SEEBURGER Property Store
•
Fixed Bug # 21182: Property Store - sorting of columns does not work ( 1.8Q1). SEEBURGER CPA Cache Search
•
•
Fixed Bug#24671: party search against max or min Identifiers does not work (1.8Q2)
Fixed Bug#25801: SeeCPACache: Database password exposed. Configurable via PropertyStore
which "attribute-patterns" should be hidden (1.8Q2)
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
27
SEEBURGER Data Transmission Adapters
Common Adapter Changes
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Adapter recovery has been improved for enhanced cluster support and stability. Refer to the
General section for details.
All Adapters do now set protocol specific or (if not available) default encodings for received
messages as dynamic attributes.
All adapters do now have a built-in splitting mechanism providing facilities to split messages in
receiver channels. Detailed descriptions and supported splitting mechanisms can be found in the
adapter-specific configuration guides.
Adapters that have polling mechanisms support polling retries in case of failed connection
attempts or similar errors.
Fixed Bug#15765: Faster shutdown of all adapters. The shut-down behavior did wait for a timeout
to occur.
Fixed Bug#15987: If the specified attachment was not available MainDocument was used instead.
Now all adapters throw an error instead.
Enhancement #15990: In case of initiated reports to the XI system, the XI message now contains
the refToMessagId header.
Fixed Bug#20970: Max Retry job is not moved to retry directory (1.8Q1). Fixed Bug#18907: Improved adapter shutdown behavior (1.8Q1). Fixed Bug#19445: Fix Communication Channel Monitoring start/stop behavior (CallbackInterface
should no longer be used) (1.8Q1). Fixed Bug#19758: Node of Queue Processors must be configurable - added MCF property
(1.8Q1). Fixed Bug#20579: Recovery job is not removed from file system when manual deleted (1.8Q1). Fixed Bug#20597: Initiators should be configurable - added MCF property (1.8Q1). Fixed Bug#20681: Running out of threads during recovery timer run (1.8Q1). Fixed Bug#21123: Resource Management doesn't work with white spaces in resource IDs
(1.8Q1).
Fixed Bug#21524: If task creation fails, the transmission report is not initiated (1.8Q2)
Fixed Bug#21987: MessageIdHandler, remove unnecessary synchronization to improve
performance (1.8Q2)
Fixed Bug#22851: Adapters show the adapter-user's password in debug-logs (1.8Q2)
Fixed Bug#23128: AAMStatusMonitor mixes up party and service for process context (1.8Q2)
Fixed Bug#23799: Recovery timer tries to recover a job which does not longer exists (1.8Q2)
Fixed Bug#25122: RecoveryJob containig umlauts cannot be recovered (1.8Q2)
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
28
OFTP Adapters (TCP, ISDN, X31)
Known Issue: Warning: Do not use the Communication Channel Monitor feature for starting/stopping
communication channels with OFTP(TCP/ISDN/X31) channels!
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Fixed bug # 8670: Improved and correct adapter monitoring.
Fixed bug # 10706: Thread pool configuration corrected.
Fixed bug # 11003: Added additional info to DtReport after receiving messages (Sender and
receiver ODETTE codes, ISDN or TCP details).
Fixed Bug #15529: Send EFPA/EERP before the file is initiated to the XI system. In case the
module chain takes a long time to process, a session timeout might have occurred. If the initiation
fails, the SEEBURGER recovery takes over.
Fixed bug # 15987: Outbound messages could have carried a wrong payload, if the specified
payload did not exist.
Fixed bug # 16420: Messages were stuck and/or one or more of the OFTP processors stopped
working.
Fixed bug # 16421: Removed race condition.
Fixed bug # 17004: Removed deadlock happening during shutdown of the adapter.
Fixed bug # 17494: Listeners seem to be not updated correctly.
Fixed Bug # 17424: Strange behavior when OFTP Sender channel is stopped only in channel
monitoring (1.8Q1). Fixed Bug # 17494: Listeners seem to be not updated correctly (1.8Q1). Fixed Bug # 18643: EERP still transmitted if "Partner sends EERP" not selected (1.8Q1). Fixed Bug # 19462: Timeout notifications by missing EERP are generated with wrong channel ID
(1.8Q1). Fixed Bug # 21140: OFTP waits for reservation timeout to run out even if "no resource available"
message is received (1.8Q1). Fixed Bug # 21168: Missing configuration of "Attachment Name" is not detected (1.8Q1). Fixed Bug # 19883: Concurrently processing OFTP adapters may lead to duplicates (because of
time-stamp based on seconds instead of ms) (1.8Q1).
Fixed Bug#26977: V2 report cannot be verified if 'deliver EERPs' flag disabled - Now if signed
eerp is requested, a check before sending the file is made whether a report channel and
agreement are configured. Report is also verified, even if it is not delivered (1.8.Q2).
Fixed [BUG#26686]: Original V2 payload initiated instead of the processed (1.8Q2)
Fixed [BUG#25743]: CCM does not show error if conflicting listeners detected by adapter startup
(1.8Q2)
Fixed [BUG#26531]: Secure authentication must not be negotiated (1.8Q2)
Fixed [BUG#26436]: TLS listener allows SSL connection (1.8Q2)
Fixed [BUG#25636]: Reauthentication error if channel is restarted after TLS configuration changes
(1.8Q2)
Fixed [BUG#22324]: OFTP does not support proxies (1.8Q2)
Fixed [BUG#21939]: Representative is not removed when startListener fails (1.8Q2)
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
29
•
•
•
•
•
•
•
Fixed [BUG#21806]: check TCP listener grouping (1.8Q2)
Fixed [BUG#21528]: 2 OFTP nodes can generate the same secondary id for OFTP mid store entry
(1.8Q2)
Fixed [BUG#16983]: DtReport should contain more details (1.8Q2)
Fixed Bug#21796: Problems when OFTP2 signed report received, but sign alias missing in report
channel (1.8Q2)
Fixed Bug#22134: Initiation of TransmissionReports fails due to Header Mapping (1.8Q2)
Fixed Bug#22355: Error when initiating received corrupt file task (with OFTPv2) and no report
channel is available (1.8Q2)
Fixed Bug#23186: Pending EERP cannot be sent (1.8Q2)
EDIINT AS2 Adapter
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Fixed Bug #14259: Reports for failed transaction where initiated via a wrong channel.
Fixed Bug #14523: dtSender, dtReceiver, dtAttachmentName, dtMsgType and dtExternalMsgId
have been added to the list of context-object visible via context object within the receiver
determination.
Fixed Bug #16120: Non-caught exception causes data loss, if storeTemp fails.
Fixed bug # 17308: Initiation of corrupt (and possible duplicate) messages fails and leaves recover
jobs behind.
Fixed bug # 17088: Adjust receiver agreement GUI to hide authentication certificate item.
Fixed bug # 17542: AS2 can not find correct Binding for TransmissionReports.
Fixed bug # 13669: Negative sync MDN must set error state.
Fixed bug # 16927: Parameter detectEncoding is not available in Adapter Meta data.
Fixed bug # 17040: AS2 does not create pending certificates for unknown SSL peers.
Fixed bug # 17310: Adapter-internal split not working with payload mode attachment.
Fixed bug # 17543: Asynchronous MDNs can only be received via sender channel of message
protocol type AS2.
Fixed Bug # 13165: Payload is missing in dump file.
Fixed Bug # 11404: AS2 Configuration guide - stati overview not up to date (1.8Q1). Fixed Bug # 19439: IBM JSSE Provider does not support fall back from TLS to SSL (1.8Q1). Fixed Bug # 20080: SMIME content transfer encoding is not recognized (1.8Q1). Fixed Bug # 21082: HTTP keep-alive is always used (1.8Q1). Fixed Bug # 21296: Creation of pending SSL certs fails on IBMVM (1.8Q1).
Fixed [BUG#26644]: Recovery job size up to 80 MB (1.8Q2)
Fixed [BUG#26962]: No valid error handling when wrong protocol is entered (1.8Q2)
Fixed [BUG#21090]: MDN can have more information (1.8Q2)
Fixed [BUG#20749]: wrong error message when report channel is missing (1.8Q2)
Fixed [BUG#26652]: [MsgIdMon] message id starting with letters is not displayed (1.8Q2)
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
30
•
•
•
•
Fixed Bug#22666: HTTP return code for MDNs which are received after timeout changed from 4xx
to 200 OK (1.8Q2)
Fixed Bug#22926: 100% CPU load during HTTP client init due to an issue with HTTP keep-alive
and SSL (1.8Q2)
Fixed Bug#25278: Sync MDN not authenticated when Handle Received MDN is set to "no action"
(1.8Q2)
Fixed Bug#26962: No valid error handling when wrong protocol is entered for async MDNs
(1.8Q2)
EbXML HTTP Adapter
•
•
•
•
•
•
•
•
•
•
•
•
Fixed Bug#13152: EbXML Outbound diaf attachments are not removed after finished task.
Fixed Bug#21296: Creation of pending SSL certs fails on IBMVM (1.8Q1). Fixed Bug#17735: Create report for received corrupt files (1.8Q1). Fixed Bug#18026: Added configuration "compMaxProcesses" to MCF properties (1.8Q1). Fixed Bug#18976: ClassCastException when trying to send an encrypted message (1.8Q1). Fixed Bug#19906: EbXML-HTTP adapter never returns error code "NotSupported" (1.8Q1). Fixed Bug#19907: EbXML does not initiate entries in the Message Id Store for configuration errors
(1.8Q1). Fixed Bug#19908: EbXML does not check the TTL of a received message (1.8Q1). Fixed Bug#22669: Null pointer exception when async and sync acknowledgement is requested
(1.8Q2)
Fixed Bug#22684: configurations still used if use extended settings is not enabled (1.8Q2)
Fixed Bug#22845: If response to acknowledgment has an empty content, ebxml tries to parse it
(1.8Q2)
Fixed Bug#24696: EbXML does not provide correct delivery semantics and split-queue in case of
internal splitter (1.8Q2)
HTTP Adapter
•
•
•
•
•
•
•
•
Fixed bug#18687: HTTP adapter does not use channel ID as target ID (duplicate detection for
tasks does work for polling).
Fixed Bug#21296: Creation of pending SSL certs fails on IBMVM (1.8Q1). Fixed Bug#15525: HTTP Client does not create transmission report if not in QoS: BEST EFFORT
(1.8Q1). Fixed Bug#17356: HTTP Client caches SSL settings (1.8Q1). Fixed Bug#18691: Add MessageIDStore entry for polling (GET) requests (1.8Q1). Fixed Bug#19115: The value of "maxIncomingProcesses" should be given in the log file (1.8Q1).
Fixed Bug#21235: HTTP Client does not enter MID store entries (1.8Q1).
Fixed Bug#22694: HTTP does not use proxy if configured (1.8Q2)
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
31
•
•
•
•
•
Fixed Bug#22800: Removed basic authentication from HTTP Controller metadata as this has to be
configured in the SAP WebAS (1.8Q2)
Fixed Bug#25105: maxPayloadAllowed cuts payload and return 200 OK, it should return an error
status code (1.8Q2)
Fixed Bug#25464: HTTP polling channel caches additional HTTP headers (1.8Q2)
Fixed Bug#25466: Removed unsupported dynamic attributes for basic authentication from adapter
metadata (1.8Q2)
Fixed Bug#25786: Details in MID entry not updated upon retry (1.8Q2)
FTP Adapter and Host FTP Adapter
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Fixed Bug#12502: Polling of wrong reports does not fail the FTP communication.
Fixed Bug#14062: Fixed wrong usage of US_ASCII instead of US-ASCII.
Fixed Bug#15484: Unsupported SYST command does not break FTP communication.
Fixed Bug#15864: Added columns to MessageIDMonitor for filtering.
Fixed Bug#16512: Added new dynamic attributes carrying server information when polling an FTP
box. More information is available in FTP Adapter-specific guide.
Fixed Bug#16928: Fixed some dynamic attributes missing in Receiver Determination.
Fixed Bug#16699: Unable to send payload as MainDocument.
Fixed Bug#17524: Missing or faulty description of Lock File in HostFTP User Manual.
Fixed Bug#18699: Report channels displayed as inactive in Communication Channel Monitor. To
solve the issue: Import latest Adapter Meta data, save and activate your report channels again.
Fixed [BUG#26480]: GXS connection not working with an alpha numeric SNRF (1.8Q2)
Fixed [BUG#26474]: Polling for EBmx ANX FTP Server profile is not working (1.8Q2)
Fixed [BUG#26471]: cwd doesn't accept 200 as a reply code (1.8Q2)
Fixed [BUG#26441]: wrong behavior of dtAttachmentName (1.8Q2)
Fixed [BUG#26461]: HostDir doesn't allow '(' and ')' (1.8Q2)
Fixed [BUG#26437]: if other reports are required, the transmission report should not be set to final
report (1.8Q2)
Fixed Bug#26464: Active mode, fixed port range: all new and retried connections bind on same
port (1.8Q2)
Fixed Bug#26483: Unexpected reply 350 after sending file to GXS Server (1.8Q2)
P7/X.400 Adapter
•
•
•
•
•
Fixed Bug #11588: Updated adapter error messages.
Fixed Bug #12552: Missing link to XI message in MessageID-Store-Monitor.
Fixed Bug #15835: Deleting a P7 message twice produces error log entries on provider.
Fixed Bug #15862: Adjustments of MessageID-Store-Monitor.
Fixed Bug #16584: Fixed recovery problem.
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
32
•
•
•
•
•
•
•
•
•
•
Fixed Bug #17061: P7 TransmissionReport contains useless correlation ID. Fixed Bug #17713: Improved error message/description when receiving duplicates.
Fixed Bug #18157: Problems sending of payloads larger than 1MB.
Fixed Bug # 9321: Key Storage login failure does not result in meaningful error messages (1.8Q1).
Fixed Bug # 17724: if timeout interval too small, then expired report and successful report may
both be received (1.8Q1). Fixed Bug # 19321: P7 does not detect constructed IA5 Text (1.8Q1). Fixed Bug # 19726: Correlation ID is set to wrong value in reports (1.8Q1). Fixed Bug # 20397: Improved handling of corrupt messages (1.8Q1).
Fixed Bug#24183: Implement connection timeouts, if box does not answer (1.8Q2)
Fixed Bug#25823: MessageIdMonitor mixes up From and To column values (1.8Q2)
EDIINT AS1 Adapter
•
•
•
•
•
Fixed Bug #15924: Dynamic attributes have been added to the list of context-objects visible via
context object within the receiver determination.
Fixed Bug #16587: Problems when first attempt of MDN DtReport delivery fails.
Fixed Bug #15104: Documentation: Sample scenario contains an error (1.8Q1). Fixed Bug #19662: The sender agreement of report channel has a redundant configuration field
(1.8Q1). Fixed Bug #21303: Splitter in mode EOIO - problem with default queue name (1.8Q1). SFTP Adapter
Known issues:
•
DSA key support is limited to key sizes of up to 1024bit. Support for larger keys is planned but not
yet available.
Fixed Bugs:
•
•
•
•
•
Fixed bug # 16115: Updated to latest Maverick version 1.4.
Fixed bug # 16185: SFTP/SSH protocol was not configurable.
Fixed Bug #16227: Transmission reports were always created, regardless of the receiver channels
configuration.
Fixed Bug #13489: It was stated that a pending certificate has been created before the actual
certificate was written to the keystore, which resulted in a wrong log message if the actual creation
failed.
Fixed Bug # 21211: Dealing with "dtAttachmentName" (1.8Q1). SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
33
•
•
•
•
•
•
•
•
•
•
•
•
Fixed Bug # 21218: Improved transmission report handling (including SCP handling) (1.8Q1). Fixed Bug # 21300: SFTP client always downloads ssh2 DSA public host key (1.8Q1). Fixed Bug # 21566: Channel status is now "active" by default.
Fixed [BUG#25102]: SFTP seems to ignore the "adapterStatus" for report channels (1.8Q2)
Fixed [BUG#26149]: Adapter specific message helpers should check initiation channels for
delivery semantics (1.8Q2)
Fixed Bug#15108: Add support for cipher suites aes256-cbc/ctr (1.8Q2)
Fixed Bug#21215: SCP doesn't support "append file" mode, removed from AMD (1.8Q2)
Fixed Bug#21300: SFTP client always downloads SSH2 DSA public host key, added option to
prefer RSA key (1.8Q2)
Fixed Bug#22418: Ciphers and other session parameters need to be configurable (1.8Q2)
Fixed Bug#26500: Retrieved files must be persisted more securely during polling (1.8Q2)
Fixed Bug#27017: Put command should use SSH_FXF_TRUNC (1.8Q2)
Fixed Bug#26550: Wrong encoding replacement of default encoding within the AMD (1.8Q2)
SeDeB2B Adapter
•
•
•
•
•
•
•
Fixed Bug #14188: Exceptions while executing SeDeB2B, stating: “Unable to obtain configuration
data!”
Fixed Bug #16108: Dynamic attributes have been added to the list of context-objects visible via “
context object” within the receiver determination.
SeDeB2B Adapter is extended with sending S/MIME capability.
Fixed bug # 10917: Meta data VanMAIL and Sedeb2b do not have common structure.
Fixed bug # 17030: Default QueueName is still visible, if useSplitter is false.
Fixed bug # 17554: Check whether VanMail-based adapters do log correctly.
Fixed Bug # 19175: Channel module configuration has solution-id module in report channels
(1.8Q1).
EdifactSecure/AUTACK Component
Update
If an update is performed, it is vital that the service SEEBURGER-SeeEdifactSecure, which was used
by older versions of EDIFACT Secure Authentication (AUTACK), is un-deployed before.
Configuration
The configuration of the Edifact Secure Authentication Service has been reworked. The service is no
longer configured via the Visual Admin tool, the SEEBURGER Property Store Front-end is used
instead. E.g. the user and password used for accessing certificates and key by the J2EE Keystoreage
Service. The name space for the service properties is http://seeburger.com/xi/EdifactSecure.
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
34
Deployment of KEYMAN Mappings
The deployment procedure of the KEYMAN mappings has been changed. Please refer to the updated
chapter KEYMAN Mapping Deployment in the EDIFACT Secure Setup Guide.
Bug Fixes
•
•
•
•
•
•
•
•
Fixed BUG#15352: Service blocks server start-up when no data source available.
Fixed BUG#12942: Sign and verify of messages with 8bit fails, if platform encoding of VM is
US-ASCII.
Fixed BUG#13124: A certificate is always stored in PENDING store, also in cases where the
certificate is already locally available.
Fixed Bug#16199: "AUTACK - Adressbook: "Toggle Status" unnecessary? (1.8Q1).
Fixed Bug#21146: Manual: KEYMANN deployment - essential information missing (1.8Q1).
Fixed Bug#22882: Check for mandatory module parameters, instead of using a default (1.8Q2)
Fixed Bug#23783: EdifactSecure is not able to retrieve global Counter due to missing reference
(1.8Q2)
Fixed Bug#25690: Editel 94: USR layout defined wrongly (1.8Q2)
SEEBURGER Modules
Common
•
•
Fixed Bug #20429: Added new function getMessageID() for dynamic parameter values.
Fixed Bug # 20888: skipExecution is missing in documentation (1.8Q1). Message Splitter
•
•
•
•
•
•
•
•
•
The Splitter Front-end has been improved to carry additional details for each entry allowing to
search and filter for/by these details.
Fixed Bug #14556: Lookup of bindings did not work, if either Party or Service was not set within
the binding.
Added drop-down list for mapping selection of currently deployed mappings to Splitter front-end.
Fixed Bug # 19576: Thread is not removed from running thread list in error case (1.8Q1). Fixed Bug # 19582: Splitter entries overwrite each other (1.8Q1). Fixed Bug # 19605: More details are needed if the splitting configuration is not given (1.8Q1). Fixed Bug # 19705: Duplicate Splitter configuration entries possible (1.8Q1). Fixed Bug # 19757: Update an entry with the same configuration in the front-end fails (1.8Q1). Fixed Bug # 19937: Splitter Adapter must be restarted to show the new channel in channel
monitoring (1.8Q1). SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
35
•
•
•
•
•
•
Fixed Bug # 21012: Duplicate check is not thread safe (1.8Q1). Fixed Bug#21731: NullPointer exception in MessageSplitter frontend when channel without
binding has been selected (1.8Q2)
Fixed Bug#21837: Splitter seems to lose attributeCopyList in recover case (1.8Q2)
Fixed Bug#23475: Splitter saves RecoverTask in case of an error while initiating (1.8Q2)
Fixed Bug#23504: In case of a detected duplicate in a child split, recover task isn't finished
(1.8Q2)
Fixed Bug#26658: splitter logs in system.err (1.8Q2)
MessageDump
•
Configuration parameter failOnError added. If set to true, the module will throw an error, if dumping
fails, resulting in a retry of the specific communication channel.
PayloadDump
•
Configuration parameter failOnError added. If set to true, the module will throw an error, if dumping
fails, resulting in a retry of the specific communication channel.
PayloadInfo
•
Configuration parameter failOnError added. If set to true, the module will throw an error, if dumping
fails, resulting in a retry of the specific communication channel.
DSig Module
•
•
•
•
•
•
•
Fixed Bug#15394: Mode parameter was not recognized when explicitly set via module
configuration.
Fixed Bug#18806: DB fields are too short.
Fixed Bug#16031: Display error during import of dsig master data in workbench (1.8Q1). Fixed Bug#16193: DSIG-Frontend (Workbench) - order of creating entries not logical (1.8Q1). Fixed Bug#16197: DSIG: "Accepted Signers" - sorting is a little unusual (1.8Q1).
Fixed Bug#22962: During unzip a temp file with hardcoded filename is created (1.8Q2)
Fixed Bug#23149: Deployment of SeeDSigTablesPI.sda fails on DB2 (1.8Q2)
DSig Module
•
Fixed Bug #17936: Payload configuration extraction handles the parameter
cfgPayloadExclusiveSet incorrectly.
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
36
Secunet Module
•
Fixed Bug #16211: Secunet module did not check whether the signature was completely written.
This may cause empty or invalid signatures attached to the XI message.
Apsec Module
•
A new component for generation and verification of detached PKCS#7 signatures of EDIFACT
files integrates the products of Apsec fideAS sign and fideAS verify.
AttachmentRename
•
Fixed [BUG#19485]: Now setting also Content-Description and explicit Content-Type (1.8Q1).
AttribMapper Module
•
•
•
•
•
•
•
Fixed Bug # 20429: Added missing function getMessageID() (1.8Q1). Fixed Bug # 21236: Added functionality to allow AttribMapper extracting bytes from payload
(1.8Q1). Fixed Bug#21236: AttribMapper does not support extracting bytes from payload (1.8Q2)
Fixed Bug#22277: Missing function getRefToMessageID() (1.8Q2)
Fixed Bug#22374: Add expression to get current date as long (1.8Q2)
Fixed Bug#23825: Add null() method to expression language (1.8Q2)
Fixed Bug#24528: Add additional function trim(String) (1.8Q2)
CharsetConversion Module
•
Fixed Bug # 20975: Manual for PCE contains wrong example (1.8Q1). Zip Module
•
•
•
•
•
•
Fixed Bug # 16312: Parameter "mode" can now be set dynamically (1.8Q1).
Fixed Bug#22746: parameter encoding can not be set (1.8Q2)
Fixed Bug#22768: incompatible behavior for parameter "zipFormat" (1.8Q2)
Fixed Bug#22940: During unzip a temp file with hardcoded filename is created (1.8Q2)
Fixed Bug#23026: New parameter failOnNoZip (1.8Q2)
Fixed Bug#25355: zipFormat for unzip should be nullable (1.8Q2)
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
37
StartLocalUp Module
•
Fixed Bug # 20885: StartLocalApp does not allow to escape spaces in parameters on *NIX /
Solaris (1.8Q1). ReplaceString Module
•
Fixed Bug # 21241: added parameter "binaryMode" into manual (1.8Q1). SEEBURGER Converter Suite
General
•
All mappings must be recompiled to work with the current release! Re-use of previously compiled
mappings of versions <=1.7 is not supported.
BIC Mapping Designer and BIC Runtime
Make sure to deploy the Mapping_user.sca shipped with your solution before deploying your own
generated Mapping_user.sca/sda files.
The deployment file for the BIC RA and module has been renamed to SeeBICXI.sca.
Mapping_user.sda, Mapping_sys.sda and Mapping_partner.sda are now wrapped in SCA files.
Warning: It is not possible to install the SEEBURGER MappingDesigner Suite to an
UNC-Path (Windows only)
•
•
•
•
•
•
•
•
•
•
Fixed Bug #18191: InhouseVDA Mainmapping creates an incorrect FunctionalAcknowledgement
in error cases.
Fixed Bug # 13923: "SAPXI_BICMD_config_en.pdf - remove misleading statement
"ActiveMappings" necessary as project name? (1.8Q1)". Fixed Bug # 14521: BIC does not get SmartiDS ConnectionManager (1.8Q1). Fixed Bug # 15653: "Classifier_SetupGuide_unnecessary ? - removed document (1.8Q1)". Fixed Bug # 18917: Improved wrong error message in monitoring (1.8Q1). Fixed Bug # 19204: Missing instructions in Documentation for XI BIC MD 1.8 (1.8Q1). Fixed Bug # 20536: Doku Bug BIC 1.7.3 Swapping (1.8Q1). Fixed Bug # 21108: System Status Mapping List not updated upon deployment of new mappings
(1.8Q1). Fixed Bug # 21145: BIS 6 documentation delivered for XI (1.8Q1). Fixed Bug # 17546: Error if setting variables/counters via BIC-mapping (1.8Q1).
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
38
•
•
•
•
•
•
•
•
Fixed Bug#21895: Mapping classes are instantiated for each loadClass request (1.8Q2)
Fixed Bug#23351: Wrong log message for suppressChildCount parameter (1.8Q2)
Fixed Bug#23575: AttachmentLog filebuffer is not removed in all cases (1.8Q2)
Fixed Bug#23894: 1.8/2.1 Mappings_sys.sca: See_Tradacom is running on error (END:NMST)
(1.8Q2)
Fixed Bug#25145: Swapping fails due to missing SeeMeasure (1.8Q2)
Fixed Bug#26027: BIC module does not report errors on loading configuration data (1.8Q2)
Fixed Bug#26311: NPE if destTargetMsg is set but no MainDocument is available (1.8Q2)
Fixed Bug#26983: getCounter() (used in the modules configuration expression language) increase
the counter two times (1.8Q2)
New BIC Runtime Behavior (Creating Mandatory Destination Fields with
Empty Values)
The BIC runtime behavior of automatic creation and syntax check of mandatory destination fields has
been changed.
•
•
•
If a mandatory field is not filled during the mapping, it is still created automatically. This automatic
creation uses the default value for the field specified in the message description.
If the message description contains no or an empty default value, the BIC runtime creates an error
message 3031 (level 3). This error message has been a warning level 5 in previous versions.
This error is also created when the field is mapped and filled with an empty value.
Also the BICMD default value syntax check has been changed. It is now possible to define an empty
default value (even if that empty value would not match against the field properties.
Problems with backward compliance:
Old mappings might not be backward compliant and will produce error 3031 in the following cases:
•
•
If a mandatory field contains no or an empty default value in the message description file.
In old message description files created by older BICMD versions, this is only possible for fields
with a minLength of 0. This applies for the message formats XML, CSV, TRADACOMS, ANSI X12
and EDIFACT. Whenever such a field is automatically created, error 3031 will be thrown.
If a mandatory field is mapped and filled with an empty value.
In these cases, the mapping or the message description is wrong and should be changed.
Applicable Solutions:
•
•
Add the mapping option/command modifyWarningLevel(3031, 5). This does not solve the mapping
problems, but makes the mapping work as it did before in the previous version.
Change the mapping code and solve the problems in the following way:
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
39
•
•
If a field is created automatically, either specify a non-empty default value in the message
description or map this field in your mapping.
If your mapping copy code copies an empty value to this field, change the copy line the way
that only valid, non-empty values are copied to the field. This could be done by using the
command existField. If the BIC_Basic_V2 language is used, the copy command could also be
replaced with the new existcopy command.
Introduction of Workspaces in BIC Mapping Designer
BIC Mapping Designer now provides management of projects and mappings on workspace level.
(Creation of workspaces for different customers, partners or logical systems).
Introduction of Global Procedures
Global procedures are a combination of user functions and procedures attributes. They are
version-able repository objects. Unlike user functions, you can program the global procedures in BIC
Basic and Java. You have access to the source and destination structures of the mapping, and you
can use the full potential of all BIC Basic functions.
Introduction of Global Codelists
Codelists are now seen in a "global view", i.e. all imported codelists are now available for all projects
under one logical system. Codelists are now version-able in the repository. You can deploy different
versions of codelists in the BIS 6 environment. Please refer to the documentation for more details.
EIAJ and HWSW
The Asian EDI standard EIAJ and its derivate HWSW are now supported by BIC Mapping Designer
and BIC runtime.
BIC Common
Classifier
•
•
The Classifier's component detection of UTF-16 type UNICODE encodings has been changed.
Previously, it reported the exact variant name, e.g. UTF-16LE/UTF-16BE. The new behavior is to
report only UTF-16 in both cases. Due to a JVM issue of SUN (and other manufacturers) , the
following behavior applies: If a component tries to read some data and specifies
UTF-16LE/UTF-16BE as encoding, the JVM does not skip the BOM (Byte Order Mark) bytes, and
this leads to parsing errors. If the encoding given to the JVM is UTF-16 only, the BOM is correctly
skipped.
A new generic classification feature is implemented, allowing the user to specify customer-specific
rules.
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
40
•
•
•
The Classifier can handle string input data (e.g. extracted from a business message).
The detection of EIAJ/CII files is implemented: The fields of the first message group header/trailer
are extracted by default.
Fixed Bug#23201: errorIfEmpty parameter does not work for Classifier module (1.8Q2)
Content Extractor
•
•
Supports the extraction of elements in EIAJ/CII files (only from the message group header/trailer).
Fixed Bug # 19273: EdifactExtractor runs in endless loop (1.8Q1). Splitter
•
The EIAJ/CII message group split is now supported.
SEEBURGER Message Tracking / Message Archiving
Important
•
•
MT Frontend application (including jobs) and database installation are from 1.8.2 on not part of the
solution CDs, but delivered on a separate CD. (1.8Q2)
MT API has been changed from 1.7.x to 1.8. Automatic reset of cLevel in case cClient should be
set has been removed. Manual reset of cLevel is necessary in case the Consolidator job has to
re-import the corresponding record. Wrong usage can lead to misbehavior (wrong children count,
undesired front-end and job effects), so handle with care!
General
•
•
•
•
•
•
•
Fixed Bug#15954: Installer for Linux/Unix-type operating systems did not work due to a 64-bit VM
being shipped and an erroneous shell script.
Fixed Bug#17315: On newer MaxDB/SapDB (>7.6.00) versions it was not possible to add
members to groups due to database exception c
om.sap.dbtech.jdbc.exceptions.DatabaseException: [-8013] (at 590): Order column must be output
column.
Fixed Bug#21257: Added manual mode for FileStore module to set most of the DB columns
directly.
Fixed Bug#21418: Added automatic reset of DB field cLevel for FileStore module, if client shall be
updated and level is >=0 . Added feature to set level explicitly.
Fixed Bug#21419: Added feature for FileStore module to set explicit message and parent
message IDs for records.
Fixed Bug#19775: Update manual for metadata mode and Property Store default value (1.8Q1). Fixed Bug#16890: AIX installer for MT does not write log file (1.8Q1). SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
41
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Fixed Bug#17714: Missing error message in log file in case of problem during deletion of an entry
(1.8Q1). Fixed Bug#19188: "search fails using operators (*,?, >) for column "size" (1.8Q1)". Fixed Bug#19193: ">=" filter not working for datetime value (1.8Q1). Fixed Bug#19214: Installation on MaxDB:"Masterdata" not available in Administration (1.8Q1). Fixed Bug#19264: Calculation of childrenFlag does not work correctly (1.8Q1). Fixed Bug#19292: Error when clicking on "Poboxes -> Overview" (1.8Q1). Fixed Bug#19299: Language switching in portal does affect portlets (1.8Q1). Fixed Bug#19550: Wrong manual "SAP_Archiving_en.pdf" delivered (1.8Q1). Fixed Bug#20070: ProfMT: Error 500 when switching between applications (1.8Q1). Fixed Bug#20112: Portal on ORACLE: Resource not found in Admin-window (1.8Q1). Fixed Bug#20316: Import of workflows takes a long time on Sap DB/Max DB (1.8Q1). Fixed Bug#20404: CSV Export of many pages or all results takes long time (1.8Q1). Fixed Bug#20437: SeeCommonCollection jar is missing (1.8Q1). Fixed Bug#20729: Number of lines in search result overview not shown (1.8Q1). Fixed Bug#20955: Add "SeeXICommonCollection.jar" to ProfMT-CD (1.8Q1). Fixed Bug#21152: Update from 1.7.2 to 1.8 fails (1.8Q1). Fixed Bug#21199: Update from 1.6Q1 not possible (Oracle only) (1.8Q1). Fixed Bug#21386: Job Scheduler is not updated if Consolidator fails (1.8Q1).
Fixed Bug#21257: Extend filestore module to allow setting of any table column (1.8Q2)
Fixed Bug#21914: Extend manual mode to store the payload if set (1.8Q2)
Fixed Bug#22751: In override mode the custom fields are not set (1.8Q2)
Fixed Bug#24905: metadataMode "override" is case-sensitive (1.8Q2)
Fixed Bug#25805: Extend FileStore module to use new showfile servlet syntax (1.8Q2)
Fixed Bug#25936: Extend manual and override mode to be able to set all DB columns without
restrictions (1.8Q2)
Fixed Bug#25940: Extend FileStore to use additional sub directories (1.8Q2)
Fixed Bug#19188: search fails using operators (*,?, >) for column "size" (1.8Q2)
Fixed Bug#19193: ">=" filter not working for datetime value (1.8Q2)
Fixed Bug#19330: MasterData -> Button New within an Archiving System results in 404 (1.8Q2)
Fixed Bug#23881: MT API throws "LOGICAL_SYSTEM_VIOLATION" error to default trace
(1.8Q2)
Fixed Bug#24517: Check exception handling in FileStoreServlet (1.8Q2)
Fixed Bug#25839: Cannot sort entries in details view (1.8Q2)
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
42
SEEBURGER Solution Content
AUTOMOTIVE Solution
•
The mappings SHPMNT05 to SeeDESADV and SeeDESADV to VDA4913 have been removed.
CONSUMER PRODUCTS Solution
•
The mappings related to Rechnungsliste have been removed.
RETAIL Solution
•
The mappings related to Rechnungsliste have been removed.
SEEBURGER Release Notes for - SAP NW Exchange Infrastructure
43
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising