SEEBURGER Release Notes for

SAP NW Process Integration

Release 2.2.1

December 3, 2013
Table of Contents

1 ReleaseNotes 1.8 6

2 Release Notes 2.1 21

2.1 Installation Requirements 21

2.1.1 Upgrade 22

2.1.1.1 Important 22

2.1.1.2 General 23

2.1.1.3 BIC Mapping Designer 24

2.1.2 SEEBURGER Workbench. 24

2.1.2.1 Message Monitor 25

2.1.2.2 Property Store 25

2.1.2.3 Recovery Monitor 25

2.1.2.4 Resource Management 25

2.1.2.5 SeeFunctions Front-end 25

2.1.2.6 System Status 26

2.1.2.7 Key Center Front-end 26

2.1.2.8 SeeCPACacheSearch 26

2.1.3 SEEBURGER Data Transmission Adapters 26

2.1.3.1 Common Adapter Changes 26

SEEBURGER Release Notes for SAP NW Process Integration 1

 2.1.3.2 Redesign of TransmissionReports (2.1Q3) 28

2.1.3.3 AUTACK 29

2.1.3.4 EbXML-HTTP Adapter 30

2.1.3.5 EDIINT AS2 Adapter 30

2.1.3.6 FTP Adapter and Host FTP Adapter 32

2.1.3.7 HTTP Adapter 32

2.1.3.8 OFTP Adapters (TCP, ISDN, X31) 33

2.1.3.9 P7/X.400 Adapter 35

2.1.3.10 SFTP Adapter 36

2.1.4 SEEBURGER Modules 37

2.1.4.1 General 37

2.1.4.2 Apsec Module 38

2.1.4.3 AttachmentRename 38

2.1.4.4 AttribMapper 38

2.1.4.5 CharsetConversion 38

2.1.4.6 DSig Module 38

2.1.4.7 Mailwrapper 39

2.1.4.8 MessageDump 39

2.1.4.9 PayloadDump 39

2.1.4.10 PayloadInfo 39

2.1.4.11 PGP Module 39

2.1.4.12 ReplaceString 40

2.1.4.13 StartLocalApp 40

2.1.4.14 Zip 40

2.1.5 SEEBURGER Converter Suite 40

2.1.5.1 General 40

2.1.5.2 BIC Mapping Designer and BIC Runtime 41

2.1.5.3 BIC Common 43

SEEBURGER Release Notes for SAP NW Process Integration 2

 2.1.6 SEEBURGER Message Tracking / Message Archiving 45

2.1.6.1 Known Issues 45

2.1.6.2 New Features 45

2.1.6.3 General 46

2.1.7 SEEBURGER Solution Content 47

2.1.7.1 General 47
2.1.7.2 AUTOMOTIVE Solution 48

2.1.7.3 CONSUMER PRODUCTS Solution 48

2.1.7.4 RETAIL Solution 48

2.1.7.5 Utility Solution 48

3 ReleaseNotes 2.2 49
3.1 Important Information 49

3.1.1 General 49

3.1.2 Upgrade 49

3.1.3 Known Issues 50

3.1.3.1 BIC Mapping Designer 50

3.2 SEEBURGER Data Transmission Adapters 52

3.2.1 General 52

3.2.2 AS2 53

3.2.3 EbXML-HTTP 53

3.2.4 Edifact Secure 53

3.2.5 FTP 54

3.2.6 HTTP 54

3.2.7 OFTP 54

3.2.8 PGP 54
3.2.9 SFTP 55

3.2.10 X400 / P7 55

SEEBURGER Release Notes for SAP NW Process Integration 3

 3.3 SEEBURGER Modules 55

3.3.1 General 55

3.3.2 Apsec 55

3.3.3 DSig 56

3.3.4 Message Splitter 56

3.3.5 Payload Dump 56

3.3.6 Replace String 56

3.3.7 Start Local App 56

3.3.8 Zip 56

3.4 SEEBURGER Converter Suite 57

3.4.1 General 57

3.4.2 BIC Mapping Designer 57

3.4.2.1 Workspace Folders 57

3.4.2.2 Mapping Editor 58

3.4.2.3 Message Editor 58

3.4.2.4 Debugger 58

3.4.2.5 Migration from Older Versions 58

3.4.3 BIC Runtime 58

3.4.4 BIC Compiler 59

3.4.5 BIC Module 59

3.4.6 Classifier Module 59

3.4.7 SeeFunctions 60

3.4.8 Standard Mappings 60

3.5 SEEBURGER Workbench 60

3.5.1 Digital Signature 60

3.5.2 Error Monitor 60

3.5.3 Mapping Variables 60

3.5.4 Recovery Monitor 60

SEEBURGER Release Notes for SAP NW Process Integration 4

 3.5.5 SEEBURGER CPA Cache Search 61

3.5.6 System Status Frontend 61

3.6 SEEBURGER Professional Message Tracking 61

3.6.1 MT-API (Java) 61

3.6.2 Filestore Module 61

Copyright (c) 2013 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: The information in this document is proprietary to SEEBURGER. No part of this document
may be reproduced, copied, or transmitted in any form or purpose without the express prior written
permission of SEEBURGER AG.
Note: We expressly declare that the document "SEEBURGER Legal Information" (delivered also
with your BIS installation media) is part of this documentation.

SEEBURGER Release Notes for SAP NW Process Integration 5

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

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

SEEBURGER Release Notes for SAP NW Process Integration 6

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

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 Workbench Message Monitor

Added input checks for date/time values.

Fixed Bug # 13933: manual: added note about filters in MIDstore (1.8Q1).

SEEBURGER Workbench Address Book

Fixed Bug#13731: Address book can not be used concurrently.

System Status

New part of SEEBURGER Workbench which shows a short overview of current system status for
monitoring and debugging purposes.

SEEBURGER Release Notes for SAP NW Process Integration 7

 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 Data Transmission Adapters

Common Adapter Changes

Adapter recovery has been improved for enhanced cluster support and stability.
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 shutdown 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 does not work with white spaces in resource IDs
(1.8Q1).

SEEBURGER Release Notes for SAP NW Process Integration 8

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]: Re-authentication error if channel restarted after these 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 Process Integration 9

 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)

EDIINT AS2 Adapter

Fixed Bug #14259: Reports for failed transaction where initiated via a wrong channel.
Fixed Bug #14523: dtSender, dtReceiver, dtAttachmentName, dtMsgType and dtExternalMs
gId 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)

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

SEEBURGER Release Notes for SAP NW Process Integration 10

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

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

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)

SEEBURGER Release Notes for SAP NW Process Integration 11

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

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

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

SEEBURGER Release Notes for SAP NW Process Integration 12

 Fixed Bug # 21566: Channel status is now "active" by default.
Known issue: DSA key support is limited to key sizes of up to 1024bit. Support for larger keys is
planned but not yet available.
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)

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 undeployed 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 Frontend 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.

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.

SEEBURGER Release Notes for SAP NW Process Integration 13

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

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).
Fixed Bug # 21012: Duplicate check is not thread safe (1.8Q1).

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.

SEEBURGER Release Notes for SAP NW Process Integration 14

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-Front-end (Workbench) - order of creating entries not logical (1.8Q1).
Fixed Bug # 16197: DSIG: "Accepted Signers" - sorting is a little unusual (1.8Q1).

DSig Module

Fixed Bug #17936: Payload configuration extraction handles the parameter cfgPayloadExclusiveS
et incorrectly.

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

SEEBURGER Release Notes for SAP NW Process Integration 15

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

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.

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

SEEBURGER Release Notes for SAP NW Process Integration 16

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

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

SEEBURGER Release Notes for SAP NW Process Integration 17

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

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)

SEEBURGER Release Notes for SAP NW Process Integration 18

Splitter

The EIAJ/CII message group split is now supported.

SEEBURGER Message Tracking / Message Archiving

Important

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
com.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).
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 # 19928: SAP_Archiving_en.pdf - wrong screenshots from installer (1.8Q1).
Fixed Bug # 20070: ProfMT: Error 500 when switching between applications (1.8Q1).

SEEBURGER Release Notes for SAP NW Process Integration 19

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

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 Process Integration 20

2 Release Notes 2.1

2.1 Installation Requirements

Hardware Requirements (All Releases)
To get detailed information, please refer to the additional document SEEBURGER Adapter Master
Installation Guide for SAP NW Process Integration / SAP Exchange Infrastructure. The required hard
disk size extremely depends on the installed adapters and modules and the tasks which have to be
performed (number and type of messages, archiving requirements, type of mappings, etc.). Also note
that some business processes may have additional requirements (regarding interfaces or
adapter cards) which have to match the data transmission requirements of the workflows. They also
may require installation of additional software components or services.

Attention: For ISDN communication, the adapters use an ISDN router. ISDN cards
are not supported!

For further information, please read the manual SEEBURGER Data Transmission Guide for SAP NW
Process Integration.

Attention: Check SAP Note 965084 for latest information about general issues and
supported hardware.

General
Release 2.1.x requires SAP NW PI 7.1 SP6 / SAP NW PI 7.11 SP2 or as of 2.1Q5 SAP NW PI 7.30
SP0 and above and includes the same feature set as release 1.8.x for SAP XI 3.0/7.0!

SEEBURGER Release Notes for SAP NW Process Integration 21

 Attention: Check SAP Note 890721 for latest information on SAP SP stack
compliance of SEEBURGER releases.

Attention: User-based access has been enabled with Release 2.1Q3. When
upgrading from 2.0.x or 2.1.1/2.1.2, make sure to either assign the required
permissions to the user (see configuration guide) or remove the adapterUser value
for the adapters in use.

Attention: The adapter installers have been removed from the solution CDs. They
only copied the CD content to a configurable directory on the hard disk. This can
also be achieved with means of the operating system. (2.1Q5)1.2.1 Important

Fixed Bug#18441: Master Installation Guide gives wrong information for adapterUser (2.1Q1)
Fixed Bug#18020: Improve Master Installation Guide to include a detailed log configuration how-to
(2.1Q1)
Fixed Bug#20871: Updated readme.txt files for all solutions (2.1Q1)
Fixed Bug#18096: Master Installation Guide - outdated screenshot (recovery)(2.1Q1)

2.1.1 Upgrade
Refer to the SAP Note 1167474 if you are planing to perform an upgrade from 1.x releases. For 2.1.1
and higher, the OFTPTablesPI.sca file needs to be deployed as New software component before
updating the OFTP Adapter's SCA files. Pay attention to section SEEBURGER Message Tracking /
Message Archiving when upgrading
Professional Message Tracking!

Attention: User-based access has been enabled with Release 2.1Q3. When
upgrading from 2.0.x or 2.1.1/2.1.2, make sure to either assign the required
permissions to the user (see configuration guide), or remove the adapterUser value
for the adapters in use.

2.1.1.1 Important
We strongly recommend finishing all active recovery jobs before updating from previous releases.

SEEBURGER Release Notes for SAP NW Process Integration 22

 Remove the existing commservice application prior to deployment of the latest release (keyname
com.seeburger.xi.webapp.commservice).
Read this document completely before starting deployment / installation of component included in
this release.
Read the Master Installation Guide completely before deployment or Installation of any component
included in this release.

Attention: If you upgrade from v2.1Q0, make sure to update every adapter
including Base and Extended Tools. All SEEBURGER adapters and tools deployed
within an SAP system have to be updated to v2.1Q1.

Attention: Adapters relying on Bouncy Castle (especially AS2!) may experience

problems with security features when used on systems where adapters like RNIF
with enabled security features are running.

Attention: Starting with version 2.1Q3, all adapters return an empty payload for
BestEffort scenarios which include a receiver channel . Reports (including
TransmissionReports) are handled exclusively over the sender channels of type
report.

2.1.1.2 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 any other server node if the original node crashes. Major improvements have been
implemented to ensure recovery monitoring and stability.

Note: Please make sure 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).

BIC Runtime and BIC Mapping Designer have been improved to provide a deployment concept
which allows development of mappings on a multiple Mapping Designer installation without
interfering the individual deployment files. 20 independent mapping user deployment files can be

SEEBURGER Release Notes for SAP NW Process Integration 23

 generated by the BIC Mapping Designer; thus allowing independent development. Please refer to
the BIC Mapping Designer Configuration Guide for details.
Known Issue: During deployment of the Extended Tools, a deployment warning might be
reported (Error occurred while starting application seeburger.com/SeeFunctionsEar ...). This error
has no negative impact on overall deployment status. The affected application will be started
automatically as soon as all dependencies are available (deployed).
Known Issue: When security features of the adapters (any technical adapter or components like
EdifactSecure/AUTACK) are used, you may experience errors showing the message java.sec
urity.NoSuchAlgorithmException: Error constructing implementation. This error has only been
experienced after deploying a component without restarting the J2EE servers afterwards. Restart
all J2EE nodes to resolve the issue.

Note: During an upgrade via SAP JSPM, a P4RuntimeException may

occur, e.g. Caused by: java.io.StreamCorruptedException: invalid stream
header. This is probably due to an error while accessing the SAP keystore.
Note that with 2.1Q3, user-based access has been re-enabled. I.e. correct
adapterUser and adapterUserPassword settings need to be applied to the
ManagedConnectionFactory properties (refer to the corresponding installation
guides). If this error persists, try disabling channels which need access to the SAP
keystore upon adapter start (e.g OFTPv2 sender channels with TLS enabled)!

2.1.1.3 BIC Mapping Designer

If an earlier version of the BIC Mapping Designer is installed and has to be updated, the installation
folder has to be set to the old installation root folder.

Note: The installation does not select the old installation folder automatically.

2.1.2 SEEBURGER Workbench.

Fixed Bug #13731: Address book could not be used concurrently from different hosts/browsers.
Fixed Bug #16031: Sorting within the import window did not work correctly. Improved data
selection for SEEBURGER Workbench import/export functionality.
Fixed Bug#18099: Front-ends should export to and import from the global directory (sys/global/)
(2.1Q1). Added download option for exported files and upload option for previously exported files
out of the web browser (2.1Q1).

SEEBURGER Release Notes for SAP NW Process Integration 24

 Fixed Bug#20444: Import/Export feature does not check for required values (2.1Q3).
Fixed Bug#21347: Browser compatibility for "select all" of "import/export" (did not work with
Internet Explorer) (2.1Q3).
Fixed Bug#22079: search pattern does work with umlaut (2.1Q3).
Fixed Bug#22515: Exports all tables, but fails on import if table is not deployed (2.1Q4).
Fixed Bug#27224: wrong encoding in case of umlauts in search filter (2.1Q5).

2.1.2.1 Message Monitor

Fixed Bug#18735: MID Store: Date/time values should be checked (2.1Q1).

Fixed Bug#13933: Improved description of filters in MIDstore (2.1Q1).
Fixed Bug#30957: Search for some message IDs did not work due to wrong uppercase
conversion (2.1Q5)

2.1.2.2 Property Store

Fixed Bug#18036: Sorting does not work for imported site of the Property Store's front-end
(2.1Q1).
Fixed Bug#21182: Property Store - sorting of columns does not work (2.1Q3).

2.1.2.3 Recovery Monitor

Fixed Bug#21441: Recovery Monitor doesn't set the delete/cancel/recover buttons to class
"inactive", if they are "disabled" (2.1Q3).

2.1.2.4 Resource Management

Fixed Bug#16397: Added export function for RM reservations (2.1Q1).

Fixed Bug#21123: ResourceManagement does not work with white spaces in resource ids (if
whitespace is at a specific position) (2.1Q3).
Fixed Bug#21637: improve error messages in ResourceManagement (2.1Q3)

2.1.2.5 SeeFunctions Front-end

Fixed Bug#18812: Invalid input not reported properly (2.1Q1).

Fixed Bug#19616: Implement delete button for each entry(2.1Q1).
Fixed Bug#20768: SeeFunctions Multivariable column Info1 should be displayed as Info1(2.1Q1).
Fixed Bug#20770: Deletion of entries with special characters (like backslash, etc) does not
work(2.1Q1).
Fixed Bug#22109: SeeFunctions Front-end details view for counters does not work (2.1Q3).

SEEBURGER Release Notes for SAP NW Process Integration 25

 Fixed Bug#21038: Functions-Front-end shows max 100 multi-variables and max 1000 variables/
counters (2.1Q3).
Fixed Bug#21390: Add "group"-column for SeeFunctions-front-end (2.1Q3).
Fixed Bug#21180: Multi-value Variable: in case of missing input wrong field name for "info1" is
displayed (2.1Q3).
Fixed Bug#22337: ORA-01000: maximum open cursors exceeded in case large backup is to be
imported on Oracle (2.1Q4)
Fixed Bug#24235: Special characters not supported in function front-end (2.1Q4).

2.1.2.6 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 deployed BIC(2.1Q1).
Fixed Bug#21455: SystemStatus Support Zip now includes the adapters version.txt (2.1Q3).
Fixed Bug#21108: MappingInfoList not updated upon deployment of new mappings (2.1Q3).

2.1.2.7 Key Center Front-end

Fixed Bug#23801: KeyCenter front-end does not support special characters (2.1Q4).
Fixed Bug#23802: Problem if the certificate name contains brackets (2.1Q4).
Fixed Bug#23813: Reset view in KeyCenter front-end (2.1Q4).
Fixed Bug#23822: Exception if importing results in an empty view list (2.1Q4).

2.1.2.8 SeeCPACacheSearch

Fixed Bug#24344: SeeCPACache: Database password exposed (2.1Q4).

Fixed Bug#24671: Party search against max or min Identifiers does not work (2.1Q4).

2.1.3 SEEBURGER Data Transmission Adapters

2.1.3.1 Common Adapter Changes

Adapter recovery has been improved for enhanced cluster support and stability.
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.

SEEBURGER Release Notes for SAP NW Process Integration 26

 Adapters which have polling mechanisms support polling retries in case of failed connection
attempts or similar errors.
Fixed bug #15765: Faster shutdown of all adapters. The shutdown 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 (after 20 retries) is not moved to retry folder (2.1Q1).
Fixed Bug#18092: Old MaxRetryReached jobs are moved to job instead of retry folder (2.1Q1).
Fixed Bug#20557: Inbound transaction handling (rollback) doesn't work correctly (TxRollback...)
(2.1Q1).
Fixed Bug#20597: Number of parallel inbound processors (sender channels) should be
configurable(2.1Q1).
Fixed Bug#19758: No of parallel outbound processors (QueueProcessors) must be
configurable(2.1Q1).
Fixed Bug#20681: Running out of threads during recovery timer run (in case of huge number of
recovery jobs) (2.1Q1).
Fixed Bug#18661: RecoverManager is removed before Adapter shutdown (Shutdown race
condition) (2.1Q1).
Fixed Bug#18763: In-Adapter-Split may have problems with UTF-8 input encoding (2.1Q1).
Fixed Bug#16410: Adapter restart might clean reservations of adapters on other J2EE nodes
(2.1Q1).
Fixed Bug#15646: In-Adapter-Split: ANSI X12 Split instead of ANSI Split parameter value (2.1Q1).
Fixed Bug#19445: Stopping 1 sender channel may lead to ChannelStoppedExceptions for other
sender channels (2.1Q1).
Fixed Bug#18840: In-Adapter-Split should check the availability of parameters (2.1Q1).
Fixed Bug#20688: In-Adapter-Split file type detection did not work correctly for EBCDIC files on
systems with an IBM VM and system encoding set to one of the Unicode variants (UTF-8, UTF-16,
etc) (2.1Q3).
Fixed Bug#21296: Creation of pending SSL certificates failed on IBM VM. This affects all HTTP
based adapters (HTTP, AS2, EbXML-HTTP) (2.1Q3).
Fixed Bug#21459: Limitation of incoming requests did not work properly. This affects all HTTP
based adapters (HTTP, AS2, EbXML-HTTP) (2.1Q3).
Fixed Bug#21527: Not supported XI acknowledgments are not correctly reported to the system
(2.1Q3).
Fixed Bug#21673: In case an adapters supports multiple attachments the dynamic attribute
dtAttachmentName was always set to MULTIATTACHMENT even if only one attachment has
been received. (2.1Q3).
Fixed Bug#21508: Adapters now check whether JNDI registration succeeded. (2.1Q3). Starting
with version 2.1Q3, all adapters return an empty payload for BestEffort scenarios which include
a receiver channel. Reports (including TransmissionReports) are handled exclusively over the
sender channels of type report. (2.1Q3).

SEEBURGER Release Notes for SAP NW Process Integration 27

 Fixed Bug#21524: If task creation fails, the transmission report is not initiated (2.1Q4)
Fixed Bug#23128: Alerting: Mixed up party and service for process context (2.1Q4)
Fixed Bug#23884: Implement API extension for Integrated Configuration (2.1Q4)
Fixed Bug#25162: Adapters show the adapter-user's password in debug-logs (2.1Q4)
Fixed Bug#23799: Recovery timer tries to recover a job which does not longer exists (2.1Q4)
Fixed Bug#25123: RecoveryJob containing umlauts cannot be recovered (2.1Q4)
Fixed Bug#27592: Running out of threads during recovery timer run (2.1Q5)
Fixed Bug#28774: OutOfMemory due to dead thread references (2.1Q5)
Fixed Bug#30751: On very rare circumstances in case multiple cluster nodes on one system are
started in the same millisecond, it is possible that duplicate XI Message IDs could have been
generated (2.1Q5).

2.1.3.2 Redesign of TransmissionReports (2.1Q3)

As of release 1.8Q1 and 2.1Q2 the transmission reports have been unified for all SEEBURGER
communication adapters. A list of common specific data keys for all adapters can be found below:

messageRequestId
creationdate
jobid
adaptertype
nodecaption
originalchannel
originalchannelid
deliverysemantics
from
fromservice
to
toservice
connection
originaddressid
destinationaddressid
channel
channelid

Note: The structure of the transmission report has not been changed. For more
details about the structure, please refer to the file dtreport.xsd.

SEEBURGER Release Notes for SAP NW Process Integration 28

Changes have only been applied to the specific data key/values. If you relied on specific keys make
sure to check the new reports, if there are new keys which fit your use case better. Reports are never
returned as a response (BestEffort).

2.1.3.3 AUTACK

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

2.1.3.3.2 Configuration

2.1.3.3.2.1 General Configuration of the Service

The configuration of the EDIFACT Secure Authentication Service has been reworked. The service
is no longer configured via the Visual Admin tool, but the SEEBURGER Property Store front-end
is used instead (e.g. the user and password used for accessing certificates and key by the J2EE
Keystorage service). The name space for the service properties is http://seeburger.com/xi/EdifactSecu
re.

2.1.3.3.2.2 Default User of J2EE Keystorage Service

The default user for accessing the J2EE Keystorage Service, which is defined in the previously
mentioned SEEBURGER Property Store. The new values are:

adapterUser = seeaut
adapterUserPassword = adapter71

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

2.1.3.3.4 Bug Fixes

Fixed Bug#15352: Service blocks server start-up if no data source available.

Fixed Bug#12942: Sign and verify of messages with 8 bit fails if platform encoding of VM is US-
ASCII.
Fixed Bug#13124: A certificate is always stored in PENDING store, also if the certificate is already
locally available.
Fixed Bug#13862: Different comparison of MessageDirection (2.1Q1).
Fixed Bug#15352: Service blocks if data source not available (2.1Q1).

SEEBURGER Release Notes for SAP NW Process Integration 29

 Fixed Bug#16199: AUTACK Adressbook: Toggle Status unnecessary (2.1Q1)".
Fixed Bug#16552: SAP_EdifactSecure_Setup.pdf not up-to-date (2.1Q1).
Fixed Bug#22882: Check for mandatory module parameters (Operation and Profile), instead of
using a default (2.1Q4)
Fixed Bug#23783: EdifactSecure is not able to retrieve global Counter due to missing reference
(2.1Q4)
Fixed Bug#25689: Editel 94: USR layout defined wrongly (2.1Q4)
Fixed Bug#29869: format error in See_REGISTER_KEYMAN (2.1Q5)
Fixed Bug#30724: VerifyEmbedded can not read signature from USR segment for EDITEL
(2.1Q5)
Fixed Bug#30873: VerifyEmbedded can not verify GS1 Headter/trealer (2.1Q5)

2.1.3.4 EbXML-HTTP Adapter

Fixed Bug#22684: Configurations still used if use extended settings is not enabled (2.1Q4).
Fixed Bug#22685: Meaningless information in audit log if initiate a message with non-existent
payload (2.1Q4).
Fixed Bug#22845: If response to acknowledgment has an empty content, EbXML tries to parse it
(2.1Q4).
Fixed Bug#24696: EbXML does not provide correct delivery semantics and split-queue in case of
internal splitter (2.1Q4).
Fixed Bug#26875: SAX Parser error in case of schema-validation (2.1Q4).

2.1.3.5 EDIINT AS2 Adapter

Fixed Bug#14259: Reports for failed transaction where initiated via a wrong channel.
Fixed Bug#14523: dtSender, dtReceiver, dtAttachmentName, dtMsgType, and dtExternalMs
gId have been added to the list of context-object visible via context object within the receiver
determination.
Fixed Bug#16120: Non-cached 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".
Fixed Bug#17542: AS2 can not find correct binding for transmission reports.
Fixed Bug#13669: Negative sync MDN must set error state.
Fixed Bug#16927: Parameter detectEncoding is not available in Adapter Metadata.
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 AS2.
Fixed Bug#9339: Wrong Message status in IDStore (2.1Q1).

SEEBURGER Release Notes for SAP NW Process Integration 30

 Fixed Bug#13165: Payload is missing in dump file (2.1Q1).
Fixed Bug#13669: Negative sync MDN must set error state (2.1Q1).
Fixed Bug#14523: Standard dynamic attribute support is missing in AS2 (2.1Q1).
Fixed Bug#16972: XI AS2 adapter can't handle duplicate messages (2.1Q1).
Fixed Bug#17897: QoS EOIO used, also if useSplitter is false (2.1Q1).
Fixed Bug#18024: Configurable ?"compMaxProcesses?" within MCF.properties (2.1Q1).
Fixed Bug#18050: AS2 manual should be updated (2.1Q1).
Fixed Bug#18051: Transmission report with wrong field (2.1Q1).
Fixed Bug#18081: Potential deadlock while shutting down the adapter (2.1Q1).
Fixed Bug#18112: Update of 1.7.4 recovery job fails (2.1Q1).
Fixed Bug#18471: The "subject" of a as2 message is incorrect in message monitor of
SEEBURGER workbench (2.1Q1).
Fixed Bug#18480: AMD - value with name QueueName not available (2.1Q1).
Fixed Bug#18792: Negative reports are not initiated correctly, sendFile operation does not have
ERROR state (2.1Q1).
Fixed Bug#18916: dtExternalMsgId attribute is not supported (2.1Q1).
Fixed Bug#20080: SMIME content transfer encoding is not recognized (2.1Q1).
Fixed Bug#20514: Sending encrypted messages with unknown certificate produces an empty
HTTP post (2.1Q1).
Fixed Bug#21082: HTTP keep-alive is always used regardless of channel configuration (2.1Q3).
Fixed Bug#22648: Change default adapterUser and adapterUserPassword (2.1Q3).
Fixed Bug#23531: Add support for additional HTTP Headers in AS2 receiver channel (2.1Q4).
Fixed Bug#25121: Sync MDN not authenticated when Handle Received MDN is set to "no
action" (2.1Q4).
Fixed [BUG#26643]: Recovery job size up to 80 MB (2.1Q4).
Fixed [BUG#26660]: No valid error handling when wrong protocol is entered (2.1Q4).
Fixed [BUG#27008]: MDN can have more information (2.1Q4).
Fixed [BUG#22648]: Change default adapterUser and adapterUserPassword (2.1Q4).
Fixed [BUG#16290]: AS1/AS2 does not shutdown due to running processes (2.1Q4).
Fixed [BUG#26653]: [MsgIdMon] message id starting with letters is not displayed (2.1Q4).
Fixed [BUG#20749]: wrong error message when report channel is missing (2.1Q4).
Fixed Bug#26304: MessageIdMontor: Search for primaryId does not work (2.1Q4).
Fixed Bug#22666: HTTP return code for MDNs which are received after timeout (2.1Q4).
Fixed Bug#25198: When receiving a negative MDN, the status within the MessageIDStoreMonitor
changes to MIC not verified (2.1Q4).
Fixed Bug#25667: wrong error message when report channel is missing (2.1Q4).
Fixed Bug#29005: Encrypt/Decrypt fails, because of lost CommandMap when used together with
SAP Rnif adapter (2.1Q5)
Fixed Bug#29645: Wrong date in MDN and initiated messages/reports (2.1Q5)
Fixed Bug#22996: MDN without subject, leads to NPE (2.1Q5).

SEEBURGER Release Notes for SAP NW Process Integration 31

2.1.3.6 FTP Adapter and Host FTP Adapter

Fixed Bug #12502: Polling of negative reports doesn't fail the FTP communication.
Fixed Bug #14062: Fixed wrong usage of US_ASCII instead of US-ASCII.
Fixed Bug #15484: Unsupported SYST command doesn't break FTP communication.
Fixed Bug #15864: Added columns to MessageIDMonitor filtering.
Fixed Bug #16512: Added new dynamic attributes carrying server information for polling an FTP
box. More information available in the FTP adapter's manual.
Fixed Bug #16928: Fixed some dynamic attributes missing in Adapter Metadata.
Fixed Bug #16699: Unable to send payload as MainDocument.
Fixed Bug#17524: Missing or faulty description of Lock File in the Host FTP user manual (2.1Q1).
Fixed Bug#18710: Utility Solution contains OFTP adapter instead of FTP adapter (2.1Q1).
Fixed Bug#18848: Channel monitoring error (2.1Q1).
Fixed Bug#22650: Default adapterUser is changed to seeftp.
Fixed Bug#26481: GXS connection not working with an alpha numeric SNRF (2.1Q4) Fixed
Bug#26475: Polling for EBmx ANX FTP Server profile is not working (2.1Q4).
Fixed Bug#26472: cwd doesn't accept 200 as a reply code (2.1Q4).
Fixed Bug#26440: wrong behavior of dtAttachmentName (2.1Q4).
Fixed Bug#26462: HostDir doesn't allow '(' and ')' (2.1Q4).
Fixed Bug#26435: if other reports are required, the transmission report should not be set to final
report (2.1Q4).
Fixed Bug#26465: In active mode with fixed port range all new and retried connections are bind to
the same port (2.1Q4).
Fixed Bug#26484: Unexpected reply 350 after sending file to GXS Server (2.1Q4).
Fixed Bug#27284: Messages are initiated although they are not deleted from the server (2.1Q5).

2.1.3.7 HTTP Adapter

Fixed Bug#17356: HTTP Client caches SSL settings (2.1Q1).

Fixed Bug#17413: Warning in log file for setting platform encoding in CC (2.1Q1).
Fixed Bug#17687: Added note on adapter restarted (/required if SSL settings are changed)
according to documentation (2.1Q1).
Fixed Bug#18025: Added configurable compMaxProcesses within MCF.properties file (2.1Q1).
Fixed Bug#18391: Store request parameter as attachment (2.1Q1).
Fixed Bug#18687: HTTP adapter does not use channel ID as target ID (2.1Q1).
Fixed Bug#19115: The value of maxIncomingProcesses should be indicated in the log file (2.1Q1).
Fixed Bug#21235: HTTP Client did not add any MessageID Store entries for processed messages
(2.1Q1).
Fixed Bug#18691: Add MessageIDStore entry for polling (GET) requests (2.1Q3).
Fixed Bug#15525: HTTP Client does now create transmission report for sent files (2.1Q3).

SEEBURGER Release Notes for SAP NW Process Integration 32

 Fixed Bug#22651: Change default adapterUser and adapterUserPassword to "seehttp" and
"adapter71" (2.1Q4).
Fixed Bug#22694: HTTP does not use proxy if configured (2.1Q4).
Fixed Bug#22820: not supported dynamic attributes have been removed from the adapter meta
data (2.1Q4).
Fixed Bug#25106: maxPayloadAllowed now returns 500 Internal Server Error, if exceeded
(2.1Q4).
Fixed Bug#25787: details in MID entry not updated in case of an retry (2.1Q4).

2.1.3.8 OFTP Adapters (TCP, ISDN, X31)

Attention: Known Issue: Do not use the Communication Channel Monitor feature
for starting/stopping communication channels with OFTP (TCP/ISDN/X31) channels
prior to versions 1.7.4, 1.8.1 and 2.1.1!

Attention: For receiving files, the TransferInfo or TransferInfoXML is no longer

provided as XI message attachment. Only the content of the received file is
provided.

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. If the module
chain takes a long time to process, a session timeout might have occurred. In case 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 which might lock up the adapter.
Fixed Bug #17004: Removed deadlock happening during shutdown of adapter.
Fixed Bug #17440: Extended msg duplicate check for incoming messages.
Fixed Bug #17293: OFTP erroneously re-uses session when its DataConversion thread is still in
use.
Fixed Bug #17416: Implemented recovery for outgoing EERPs, fixed search key for the EERP
task that must be different.
Fixed Bug #9494: TransferInfo might be added 'twice' (2.1Q1).

SEEBURGER Release Notes for SAP NW Process Integration 33

 Fixed Bug #14343: Error codes are not documented (2.1Q1).
Fixed Bug #15608: Incorrect MessageIdStore Monitor states (2.1Q1).
Fixed Bug #17086: Implement recovery of incoming reports (2.1Q1).
Fixed Bug #17250: OFTP documentation is vague about using SFID entry (2.1Q1).
Fixed Bug #17494: Listeners seem not to be updated correctly (2.1Q1).
Fixed Bug #17806: Split OFTP-SCAs into one table- and three adapter-scas (2.1Q1).
Fixed Bug #18103: NPE when resource reservation cannot be created (2.1Q1).
Fixed Bug #18535: Error description in case of password too long not precise enough ( 2.1Q1).
Fixed Bug #18588: OFTP does not release reservation for outgoing transfers, if session cannot be
established (2.1Q1).
Fixed Bug #18643: EERP still transmitted if "Partner sends EERP" not selected (2.1Q1).
Fixed Bug #18918: Exception in case of EERP lookup in recovery (2.1Q1).
Fixed Bug #15572: Setting and using the value of OftpProtocol state is not thread safe (2.1Q1).
Fixed Bug #18463: ISDN Listener restart does not always work correctly (2.1Q1).
Fixed Bug #18765: Restart remote capi and ISDN listener by adapter start does not always work
(2.1Q1).
Fixed Bug #16191: Warning while importing meta data OFTP-TCP (2.1Q1).
Fixed Bug #17424: OFTP channels can now be stopped and started via communication channel
monitoring (2.1Q1).
Fixed Bug #21168: When given, dynamic attribute dtAttachmentName in Receiver channel now
defines the payload, which has to be sent even when payload type in channel is MainDocument
(2.1Q1).
Fixed Bug#21184: OFTP can now initiate a message with payload mode attachment (2.1Q1).
Fixed Bug#19462: Timeout notifications of missing EERPs have been initiated via the wrong
channel (2.1Q3).
Fixed Bug#17424: If multiple sender channels only differ within the dataset name, stopping one
channel might result in not receiving any files (2.1Q3).
Fixed Bug#21168: Missing configuration of Attachment Name can not be detected (2.1Q3).
Fixed Bug#22351: Reports which cannot be correlated are no longer initiated (2.1Q3).
Fixed Bug#22355: If there is no configured channel for 'receive corrupt file' report, a proper
exception is thrown instead of NPE (2.1Q3).
Fixed Bug#22134: Initiation of transmission reports no longer fails due to Header Mapping
(2.1Q3).
Fixed Bug#21796: If signed EERP verification fails, OFTP session is no longer closed, error is
displayed in channel monitoring (2.1Q3).
Fixed Bug#22324: OFTP now supports proxy usage in the outgoing case (2.1Q3).
Fixed Bug#22652: 'Adapter user' and 'Adapter user password' are changed as following (2.1Q3):

ISDN - user: 'seeofi', password: 'adapter71'

TCP - user: 'seeotp', password: 'adapter71'
X31 - user: 'seeox31', password: 'adapter71'

SEEBURGER Release Notes for SAP NW Process Integration 34

 Fixed Bug#21806: Grouping of TCP listeners now is based on the following attributes: Host, port,
'useTLS', 'TLSServerAlias', 'TLSClientsAlias'. Conflicting are listeners, which have the same host
and port, but different TLS settings. They belong to different partitions and on module start, all
conflicting listeners are not started. If a conflicting representative is removed/deactivated, there is
no other representative from this partition and there is a single different conflicting representative
on the same interface, the second will be automatically started. If a listener has 'useTLS' disabled,
but has a TLS client/server alias assigned, the TLS aliases are ignored, and considered as empty
strings in partitioning (2.1Q3).
Fixed Bug#21528: In MessageIdStore 2 OFTP nodes could generate the same secondary id
for OFTP mid store entry. The primary and secondary id of the entries are now switched. For
backward compatibility, entries in the old model can still be correlated. Support for such entries is
done for a period, determined by the message timout value. You can disable the support for such
entries with a new flag in Managed Connection Factory properties - OldMIDStoreSupport. When
support period is over and this flag is still true, a warning will be displayed in log and in channel-
independent monitoring each time the adapter is started. To avoid these warnings, set the flag to
false when you see the warnings (2.1Q3).
Fixed Bug# 16983: In Transmission and Receipt report is added now the payload size, calculated
in bytes (2.1Q3).
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 (2.1Q4).
Fixed [BUG#26664]: Original V2 payload initiated instead of the processed (2.1Q4).
Fixed [BUG#26532]: Secure authentication must not be negotiated (2.1Q4).
Fixed [BUG#26438]: TLS listener allows SSL connection (2.1Q4).
Fixed [BUG#22478]: Invalid transition by polling and failed incoming transfer (2.1Q4).
Fixed [BUG#22652]: Change default adapterUser and adapterUserPassword (2.1Q4).
Fixed [BUG#22324]: OFTP does not support proxies (2.1Q4).
Fixed [BUG#21939]: Representative is not removed when startListener fails (2.1Q4).
Fixed [BUG#21806]: check TCP listener grouping (2.1Q4).
Fixed Bug#23186: Pending EERP cannot be sent (2.1Q4).
Fixed Bug#25715: NPE when V2 report received and there is no MIDStore entry for it, now only a
warning is shown in log and the report is not initiated anymore (2.1Q4).
Fixed Bug#26124: TLS aliases must be ignored when filtering listener with useTLS=false (2.1Q4).
Fixed Bug#22756: OFTP TCP can not be updated from 2.1.1 to OFTP V2 2.1.3 with JSPM in case
there exist SSL listeners (2.1Q4).
Fixed Bug#25634: Re-authentication error if channel restarted after tls configuration changes
(2.1Q4) .

2.1.3.9 P7/X.400 Adapter

Fixed Bug #11588: Updated adapter error messages.

Fixed Bug #15835: Deleting a P7 message twice produces error log entries on provider.

SEEBURGER Release Notes for SAP NW Process Integration 35

 Fixed Bug #15862: Improved MessageIdStore-Monitor.
Fixed Bug #16584: In recovery cases the inbound lookup must be performed again.
Fixed Bug #17061: P7 TransmissionReport contains useless correlation id.
Fixed Bug #15771: Replaced InvocationTargetException with better error descriptions.
Fixed Bug#12552: Missing link to XI message in MessageIdStoreMonitor (2.1Q1).
Fixed Bug#13401: DtReport does not contain original xi msg id (2.1Q1).
Fixed Bug#15771: All exceptions occur as ?"InvocationTargetException?" in AuditLog (2.1Q1).
Fixed Bug#16584: P7 recovery problem (2.1Q1).
Fixed Bug#16915: P7 problem with sending notifications from recovery (2.1Q1).
Fixed Bug#16929: P7 does not shutdown after sending notifications from recovery (2.1Q1).
Fixed Bug#17061: P7 TransmissionReport contains useless correlation id (2.1Q1).
Fixed Bug#17713: Missing error message in monitoring (in case of duplicate message?) (2.1Q1).
Fixed Bug#17724: If the timeout interval is too small, then the expired report and the successful
report may both be received (2.1Q1).
Fixed Bug#18157: P7 cannot send attachments bigger than 1MB (2.1Q1).
Fixed Bug#19321: P7 does not detect constructed IA5 Text (2.1Q1).
Fixed Bug#19726: CorrelationId is set to the wrong value in reports (2.1Q1).
Fixed Bug#25769: MessageIdMonitor mixes up From and To column values (2.1Q4)
Fixed Bug#24183: Implement connection timeouts, if box does not answer (2.1Q4)
Fixed Bug#27531:
com.seeburger.xi.p7.config.CPACacheQueries.lookupMatchingInboundChannels throws
exception if channels are stopped (2.1Q5)

2.1.3.10 SFTP Adapter

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 # 17002: Transmission reports are sent to the XI system for existing report even if the
report channel is inactive.
Fixed bug # 16896: Connection is reset during transmission.
Fixed bug # 14946: SFTP tries to poll directory while doing polling for * - added check for
unavailable directory.
Fixed bug # 16480: File permission mask changed.
Fixed bug # 17281: SSHTransport is not closed when there is authentication failure.
Fixed Bug#15465: Password logged in plain text in adapter log file (2.1Q1).

SEEBURGER Release Notes for SAP NW Process Integration 36

 Fixed Bug#16185: SFTP version not configurable (2.1Q1).
Fixed Bug#18321: Link between MIDMonitor and RecMon is missing (2.1Q1).
Fixed Bug#18374: SCP must be supported by sending files (2.1Q1).
Fixed Bug#21300: With an attribute Prefer RSA Key in SFTP adapter meta data, now the key type
for authentication on the server can be selected (RSA or DSA). Default value is false. (2.1Q1).
Fixed Bug#15108: Add support for cipher suites aes256-cbc/ctr (2.1Q3).
Fixed Bug#21211: Dealing with "dtAttachmentName" (2.1Q3).
Fixed Bug#21215: Removed "append file" mode for SCP (not supported by protocol) (2.1Q3).
Fixed Bug#21218: Implemented transmission reports for SCP (2.1Q3).
Fixed Bug#21503: SFTP metadata contained solution-id module in report channel. Has been
removed. (2.1Q3).
Fixed Bug#21566: AMD: adapterStatus should have default "active" for channel status. (2.1Q3).
Fixed [BUG#26228]: SFTP seems to ignore the "adapterStatus" for report channels (2.1Q4).
Fixed [BUG#26150]: Adapter specific message helpers should check initiation channels for
delivery semantics (2.1Q4).
Fixed [BUG#27099]: Polling must not initiate file when delete not possible (2.1Q4).
Fixed Bug#25800: Put command now uses SSH_FXF_TRUNC (2.1Q4).
Fixed Bug#25127: Two messageID entries for one transaction (2.1Q4).
Fixed Bug#26499: Retrieved files will be initiated immediately after polling / deleting from server
(2.1Q4).
Fixed Bug#26538:Defaults for connection parameters have changed to SHA1, AES 128 CBC and
DH group exchange (2.1Q4).
Fixed Bug#26549: Wrong encoding replacement (2.1Q4).
Fixed Bug#23985: possible data loss when channel subject contains wildcards and delete file is
set to true (2.1Q4).
Fixed Bug#27955: Preferred MAC is now configurable (2.1Q5).
Fixed Bug#30759: SFTP adapter hangs due unset socket timeout (2.1Q5)
Fixed Bug#27470: SFTP does not work correctly with old adapter meta data (2.1Q5)
Fixed Bug#28214: Key length check only needed for key generation (2.1Q5)

2.1.4 SEEBURGER Modules

2.1.4.1 General

Fixed Bug#25141: Modules are not able to access SeeFunctions within the expression language,
due to missing reference (2.1Q4).
Fixed Bug#26340: ModuleExceptions will be reported as permanent errors for the XI file adapters
archiving functionality (2.1Q4).
Fixed Bug#22206: added new feature of parameter checking (showValidationInfo=true) (2.1Q4).
Fixed Bug#30166: Evaluate basic parameter skipExecution before module is called (2.1Q5).

SEEBURGER Release Notes for SAP NW Process Integration 37

2.1.4.2 Apsec Module
New component for generation and verification of detached PKCS#7 signatures of EDIFACT files in
cooperation with Apsec fideAS sign and fideAS verify products.

Fixed Bug#18806: DB fields are too short(2.1Q1)

2.1.4.3 AttachmentRename

Fixed [BUG#19485]: Now setting also Content-Description and explicit Content-Type (2.1Q1)

2.1.4.4 AttribMapper

Fixed Bug#20429: Missing function getMessageID() has been added (2.1Q1).

Fixed Bug#21236: AttribMapper does now support extracting bytes from payload (2.1Q3).
Fixed Bug#22374: Add expression to get current date as long (2.1Q4).
Fixed Bug#23825: Add null() method to expression language (2.1Q4).
Fixed Bug#23921: add function "evaluateXPath(attachmentName, XPathExpression)" (2.1Q4).
Fixed Bug#24528: Add additional function trim(String) (2.1Q4).
Fixed Bug#30770: Expression evaluator has problem with NOT operator and braces (2.1Q5).

2.1.4.5 CharsetConversion

Fixed Bug#17936: "Payload configuration extraction" deals the "cfgPayloadExclusiveSet"

incorrectly (2.1Q1).
Fixed Bug#20975: Manual for PCE contains wrong example (2.1Q1).

2.1.4.6 DSig Module

Fixed Bug#15394: Mode parameter was not recognized if explicitly set over the module
configuration.
Fixed Bug#16193: DSIG-Frontend (Workbench): Order of creating entries not logical (2.1Q1).
Fixed Bug#16194: DSIG: Workbench-effect with special characters (2.1Q1).
Fixed Bug#16197: DSIG: ?"Accepted Signers?" - sorting is a little unusual (2.1Q1).
Fixed Bug#18796: DSig front-end seems to cache connections or DB results (2.1Q1).
Fixed Bug#15907: Zip files containing filenames with special characters cannot be read (2.1Q3).
Fixed Bug#23149: Deployment of SeeDSigTablesPI.sda fails on DB2 (2.1Q4).
Fixed Bug#22962: During unzip a temp file with hard-coded filename is created (2.1Q4).

SEEBURGER Release Notes for SAP NW Process Integration 38

2.1.4.7 Mailwrapper

Fixed Bug#23339: Implement module to wrap SAP mail adapter calls and update
MessageTracking in case an error occurs (2.1Q4).

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

2.1.4.9 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.
Fixed Bug#16810: If parameter targetFile is not present a NPE is shown in audit log with no further
message.(2.1Q1).
Fixed Bug#16018: Module chain proceeds after error while dumping (2.1Q1).

2.1.4.10 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.
Fixed Bug#16020: Module chain proceeds after error while printing infos (2.1Q1).

2.1.4.11 PGP Module

Fixed Bug#23801: KeyCenter front-end does not support special characters (2.1Q4).
Fixed Bug#23802: Problem if the certificate name contains brackets (2.1Q4).
Fixed Bug#23822: Exception by importing results in empty view list (2.1Q4).
Fixed Bug#24041: Need support for AES encryption (2.1Q4).
Fixed Bug#25967: Certificate with long name can only partly displayed in keycenter front-end
(2.1Q4).
Fixed Bug#25970: E-mail address bracketed with "<>" can not be displayed in keycenter front-end
(2.1Q4).
Fixed Bug#25952: Keycenter front-end try to parse username from userID, which is sometimes
empty (2.1Q4).
Fixed Bug#26601: Decryption uses incorrectly only signing key (2.1Q4).
Fixed Bug#28896: PGP Key Center front-end caches passwords from Property Store (2.1Q5).
Fixed Bug#29761: PGP Key Center front-end can use different users for keystore access and
front-end login when using the new keystore access mode (2.1Q5).

SEEBURGER Release Notes for SAP NW Process Integration 39

2.1.4.12 ReplaceString

Fixed Bug#18606: ReplaceString module does not replace 0D 0A in Cp500 files (2.1Q1).
Fixed Bug#22049: Added parameter "showValidationInfo" where module parameters are validated
(2.1Q3).
Fixed Bug#27548: Replacing last character in file (2.1Q5).
Fixed Bug#30453: java.lang.ArrayIndexOutOfBoundsException when patterns overlap
(2.1Q5)1.5.13 Secunet.
Fixed Bug #16211: Secunet module did not check if the signature was completely written, which
could cause empty or invalid signatures being attached to the XI message.

2.1.4.13 StartLocalApp

Fixed Bug#20885: StartLocalApp doesn't allow to escape spaces in parameters on *NIX / Solaris
(2.1Q3).

2.1.4.14 Zip

Fixed Bug#16312: Parameter "mode" can not be set dynamically (2.1Q1).

Fixed Bug#22037: Warning message in the Auditlog if "zipFormat" or "mode" is misspelled
(2.1Q3).
Fixed Bug#23026: New parameter failOnNoZip (2.1Q4).
Fixed Bug#22746: parameter "encoding" can not be set in unzip mode (2.1Q4).
Fixed Bug#22940: During unzip a temp file with hard coded filename is created (2.1Q4).
Fixed Bug#30349: Temporary directory for unzip can not be created (2.1Q5).
Fixed Bug#30683: Zip module extracts folders as 0 byte payloads (2.1Q5).

2.1.5 SEEBURGER Converter Suite

2.1.5.1 General
All mappings must be re-compiled in order to work with the current release! Re-use of previously
compiled mappings of versions <=1.7 is not supported.

SEEBURGER Release Notes for SAP NW Process Integration 40

2.1.5.2 BIC Mapping Designer and BIC Runtime

Warning: It is not possible to install the SEEBURGER MappingDesigner Suite to an

UNC-Path (Windows only).

2.1.5.2.1 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 BIC Mapping Designers 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 BIC Mapping Designer 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.

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

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 exi

SEEBURGER Release Notes for SAP NW Process Integration 41

 stField. If the BIC_Basic_V2 language is used, the copy command could also be replaced with the
new existcopy command.

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

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

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

2.1.5.2.5 EIAJ and HWSW

The Asian EDI standard EIAJ and its derivate HWSW are now supported by BIC Mapping Designer
and BIC runtime.

2.1.5.2.6 Fixed Bugs

Fixed Bug#13923: SAPXI_BICMD_config_en.pdf: "ActiveMappings" necessary as project name

(2.1Q1).
Fixed Bug#14521: BIC does not get SmartiDS ConnectionManager (2.1Q1).
Fixed Bug#15410: BIC seems to lose DB connection if datasource settings are changed (2.1Q1).

Fixed Bug#15653: Classifier_SetupGuide_unnecessary (2.1Q1).

Fixed Bug#15655: SAPXI_FunctionalAck_en.pdf: Screenshot not up to date (2.1Q1).
Fixed Bug#15697: BIC Mdoule: saveSourceMsg does not overwrite attachment (2.1Q1).
Fixed Bug#16639: BIC Module cannot load HTTPServletRequest (2.1Q1).
Fixed Bug#18008: SAPXI_BICMD_config_en.pdf: Screenshot out of date (2.1Q1).
Fixed Bug#18009: SAPXI_FunctionalAck_en.pdf: Partially not up-to-date (2.1Q1).
Fixed Bug#18052: ERROR when opening KEYMAN mappings (2.1Q1).
Fixed Bug#18191: InhouseVDA Mainmapping creates a wrong FunctionalAcknowledgement when
there is an error (2.1Q1).
Fixed Bug#18629: BIC module fails due to NullPointer in ClassifierResult (2.1Q1).

SEEBURGER Release Notes for SAP NW Process Integration 42

 Fixed Bug#18917: Wrong error message in monitoring (2.1Q1).
Fixed Bug#19777: Extend documentation: forcemode for JSPM must be set in order to deploy
mappings (2.1Q1).
Fixed Bug#20536: Docu Bug BIC 1.7.3 Swapping (2.1Q1).
Fixed Bug#19273: EdifactExtractor runs in endless loop (2.1Q1).
Fixed Bug#21108: MappingInfoList not updated upon deployment of new mappings (2.1Q3).
Fixed Bug#22145: Creation of mappings_partner wrongly documented (2.1Q3).
Fixed Bug#23575: Temporary attachment log is not deleted in case of a conversion error. Log file
can be kept with property store flag deleteLog in namespace http://seeburger.com/xi/BIC set to
false.
Fixed Bug#21895: Mapping classes are instantiated for each loadClass request (2.1Q4).
Fixed Bug#23351: Wrong log message for suppressChildCount parameter (2.1Q4).
Fixed Bug#23894: 1.8/2.1 Mappings_sys.sca: See_Tradacom is running on error (END:NMST)
(2.1Q4).
Fixed Bug#26028: BIC module does not report errors on loading configuration data (only a general
exception is shown) (2.1Q4).
Fixed Bug#26222: AttachmentLog file buffer is not removed in all cases (2.1Q4).
Fixed Bug#22871: Swapping failed. (2.1Q4).
Fixed Bug#26028: BIC module does not report errors on loading configuration data (2.1Q4).
Fixed Bug#26312: Exception if destTargetMsg is set to a specific name but no MainDocument is
available (2.1Q4).
Fixed Bug#26917: ClassLoader exceptions during BIC starting (2.1Q4).
Fixed Bug#26953: Keyman Mapping not working due to missing references (2.1Q4).
Fixed Bug#26982: getCounter() increase the counter for two times (2.1Q4).
Fixed Bug#26953: Keyman Mapping not working due to missing SeeConfig-client.jar (2.1Q5).
Fixed Bug#28516: Error in Mapping Designer when masking single characters (2.1Q5).
Fixed Bug#29486: useAttribIfSet does not work (2.1Q5).
Fixed Bug#30353: Incoming EDIFACT messages fails when UNA segment does not have a
standard value (2.1Q5).

2.1.5.3 BIC Common

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

SEEBURGER Release Notes for SAP NW Process Integration 43

 A new generic classification feature is implemented, allowing the user to specify customer-specific
rules.
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 (2.1Q4).
Fixed Bug#24796: showInAuditLog of Classifier does not work (2.1Q4)S

2.1.5.3.2 Content Extractor

Supports the extraction of elements in EIAJ/CII files (only from the message group header/trailer).

2.1.5.3.3 Splitter

The EIAJ/CII message group split is now supported.

Fixed Bug#14556: Splitter can not lookup binding, if receiver party OR receiver service are not set
(2.1Q1).
Fixed Bug#17331: Seeburger Splitter problem with version 2.0.1 PI7.1 SP6 (2.1Q1).
Fixed Bug#17368: Shorten IDs for MessageIdMapper to allowed DB column length (2.1Q1).
Fixed Bug#17857: built-in splitter produces an empty payload when filesize%blocksize=0 (2.1Q1).

Fixed Bug#18147: Splitter frontend doesn't save current selection when searching (2.1Q1).
Fixed Bug#19576: Thread is not removed from running thread list in error case (2.1Q1).
Fixed Bug#19582: Splitter entries overwrite each other (2.1Q1).
Fixed Bug#19605: More details are needed if the splitting configuration is not given (2.1Q1).
Fixed Bug#19705: Duplicate Splitter configuration entries possible (2.1Q1).
Fixed Bug#19757: update an entry with the same configuration in the front-end fails(2.1Q1).
Fixed Bug#19861: drop-down list input enhancement (2.1Q1).
Fixed Bug#19937: Splitter Adapter must be restarted to show the new channel in channel
monitoring (2.1Q1).
Fixed Bug#21012: duplicate check is not thread safe (2.1Q1).
The Splitter front -end has been improved to carry additional details for each entry (now 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.
Added recovery functionality to the SEEBURGER Message Splitter. Now the mode MESSAGE
ASYNC can be used without message loss in error cases. The SEEBURGER MessageID Monitor
now displays split messages and the SEEBURGER Recovery Monitor shows messages which
could not be initiated to the SAP system. (2.1Q1).
Fixed Bug#17950: warning information for all modules are expected (2.1Q3).

SEEBURGER Release Notes for SAP NW Process Integration 44

 Fixed Bug#21837: Splitter seems to lose attributeCopyList in recover case (2.1Q3).
Fixed Bug#21731: NullPointer exception in MessageSplitter frontend when channel without
binding has been selected (2.1Q3).
Fixed Bug#22325: synchronized block in ThreadStarter can cause deadlock problem (2.1Q3).
Fixed Bug#22517: recovery task should be saved as early as possible (2.1Q3).
Fixed Bug#23475: Splitter saves RecoverTask in case of an error while initiating (2.1Q4).
Fixed Bug#23504: In case of a detected duplicate in a child split, recover task is not finished
(2.1Q4).
Fixed Bug#26367: search with parentIdRef and timestamp does not work in MID (2.1Q4).
Fixed Bug#26710: splitter logs in system.err (2.1Q4).
Fixed Bug#27020: Memory improvements when deserializing big recovery jobs (2.1Q5).
Fixed Bug#27752: Recovery in EOIO mode (async) doesn't guarantee the correct order (2.1Q5).
Fixed Bug#27782: In case AUTACK is present on the system, MessageSplitter cannot be updated
to the latest version (2.1Q5).
Fixed Bug#30277: Implemented cleanup of old MesageIdStore entries (2.1Q5).

2.1.5.3.4 SeeFunctions / Permanent Variables

Fixed Bug#16824: SeeFunctions servlets are missing LoginSession (2.1Q1).

Fixed Bug#18732: MappingVariables: case of ?"too long value?" of variable not caught (2.1Q1).
Fixed Bug#18733: MappingVariables: In case of multivalue variables there should be a length
limitation of the input field (2.1Q1).
Fixed Bug#17546: Error if setting variables/counters via BIC-mapping (2.1Q3).

2.1.6 SEEBURGER Message Tracking / Message Archiving

MT Frontend application (including jobs) and database installation are from 2.1.4 on not part of the
solution CDs, but delivered on a separate CD. (2.1Q4).

2.1.6.1 Known Issues

When upgrading from previous versions, versions prior to 2.1Q2 (2.0.0, 2.0.1, 2.1.0 and 2.1.1)
may have problems and should not be used! The reporting feature may have problems with when
uploading files which have upper case letters.

2.1.6.2 New Features

A reporting feature has been added, which allows to create used-defined reports based on jasper
reports.

SEEBURGER Release Notes for SAP NW Process Integration 45

2.1.6.3 General

Major upgrade with performance improvements.

Fixed Bug #15954: Installer for Linux/Unix-based 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 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.
Fixed Bug #19550: Obsolete documentation has been updated (e.g. include DB2 information).
Known issue: User/group management problems with Oracle 9i (tested on 9.2.0.6.0).
Fixed Bug#15643: Missing SQL-Scripts in Archiving - Manual (2.1Q1).
Fixed Bug#15954: Installer for MT does not work correctly on Linux (2.1Q1).
Fixed Bug#15956: BISMT Mandanten: cClient not converted by consolidator (2.1Q1).
Fixed Bug#16116: Problems with the SQL driver from Microsoft (2.1Q1).
Fixed Bug#17067: Horizontal scroolbar in firefox not usable (2.1Q1).
Fixed Bug#17316: Cannot upload message description (2.1Q1).
Fixed Bug#17665: MTs Archiver throws error (2.1Q1).
Fixed Bug#17714: Missing error message in log file in case of problem during deletion of an entry
(2.1Q1).
Fixed Bug#17796: PI Message Mappings fail due to transactional data source (2.1Q1).
Fixed Bug#17803: MTMasterXI.writeRecord(String id) causes java.lang.IllegalArgumentException:
Null value (2.1Q1).
Fixed Bug#18083: Manual does not describe manual creation of MT data source (2.1Q1).
Fixed Bug#18299: MTDetailXI.setField() throws NullPointerException in PI Message Mappings
(2.1Q1).
Fixed Bug#18420: MTMasterXI.setDirectionOut() sets wrong direction (2.1Q1).
Fixed Bug#18751: Latest version not installable under MSSQL (2.1Q1).
Fixed Bug#18900: Password change dialog doesn't work correctly (2.1Q1).
Fixed Bug#19188: "Search fails using operators (*,?, >) for column ?"size?" (2.1Q1)".
Fixed Bug#19190: Archive job doesn't seem to work with MSSQL (2.1Q1).
Fixed Bug#19214: Installation on MaxDB:?"Masterdata?" not available in Administration (2.1Q1).
Fixed Bug#19264: Calculation of cChildrenFlag does not work correctly (2.1Q1).
Fixed Bug#19329: Very strange behaviour of MT-frontend after update (2.1Q1).
Fixed Bug#20070: ProfMT: Error 500 when switching between applications (2.1Q1).
Fixed Bug#20112: Portal on ORACLE: Resource not found in Admin-window (2.1Q1).
Fixed Bug#20316: Import of workflows takes a long time on Sap DB/Max DB (2.1Q1).
Fixed Bug#20404: CSV Export of many pages or all results takes long time (2.1Q1).
Fixed Bug#20729: Number of lines in search result overview not shown (2.1Q1).
Fixed Bug#13020: SQL Log - disable by default (2.1Q1).

SEEBURGER Release Notes for SAP NW Process Integration 46

 Fixed Bug#21257: Extend file store module to allow setting of any table column (2.1Q3).
Fixed Bug#21418: No reset of cLevel in case client is set (2.1Q3).
Fixed Bug#21419: Allow setting of explicit message ids for records (2.1Q3).
Fixed Bug#19188: Fixed search using operators (*,?, >) for column "size" (2.1Q3).
Fixed Bug#21449: Installer for MT does not show the LogFile (Windows) and reports an error
although the installation was successful. (2.1Q3)
Fixed Bug#21608: Users with umlauts in name or password corrupt the user management
(2.1Q3).
Fixed Bug#19193: Search filter ">=" not working for datetime values (2.1Q3).
Fixed Bug#19299: Language switching in portal does not affect portlets (2.1Q3).
Fixed Bug#21809: Remove reference to BIC from MT. BIC is no longer needed for the deployment
of the MessageArchiving.sca (2.1Q3).
Fixed Bug#19929: The "SmartiDS_<DBMS>".xml files have been removed (not needed for PI 7.1,
data sources are configured within the NWA) (2.1Q3).
Fixed Bug#21445: MT-Installer could not load the DB2 license jar (2.1Q3).
Fixed Bug#25806: Extend FileStore module to use new showfile servlet syntax (allows to use the
standard BIS6 MessageTracking) (2.1Q4).
Fixed Bug#25941: Extend FileStore to use additional sub directories (performance issues in case
the message-id starts always with the same characters) (2.1Q4).
Fixed Bug#26638: Extend manual mode to store the payload if set (2.1Q4).
Fixed Bug#21386: Job Scheduler is not updated if Consolidator fails (2.1Q4).
Fixed Bug#22313: Archiving: Store BIC log when executing mapping for index file creation
(2.1Q4).
Fixed Bug#22828: Parsing JSP fails due to usage of java.lang.String (2.1Q4).
Fixed Bug#24517: Check exception handling in FileStoreServlet (2.1Q4).
Fixed Bug#24518: Check exception handling in Archiving (there were catched Throwables)
(2.1Q4).
Fixed Bug#25437: Cannot sort entries in details view (2.1Q4).
Fixed Bug#25962: Update from 1.6Q1 not possible (Oracle only) (2.1Q4).
Fixed Bug#26254: Warning during deployment: Cannot load servlet (2.1Q4).
Fixed Bug#22827: Catching exceptions silently in SmartiServlet (2.1Q4).
Fixed Bug#24904: Filestore: metadataMode "override" was case-sensitive (2.1Q4).
Fixed Bug#28814: Deployment of Professional Message Tracking fails (2.1Q5).

2.1.7 SEEBURGER Solution Content

2.1.7.1 General

Fixed Bug#15427: API jars/archives for import into repository should deliver a version info (2.1Q1).

SEEBURGER Release Notes for SAP NW Process Integration 47

 Fixed Bug#17995: Error in EDIFACT MainMapping Structure (2.1Q1).

2.1.7.2 AUTOMOTIVE Solution

The mappings SHPMNT05 to SeeDESADV and SeeDESADV to VDA4913 have been removed.
Fixed Bug#19666: Content tpz 2.1.0 for automotive contains old SeeFunctions jar(2.1Q1)

2.1.7.3 CONSUMER PRODUCTS Solution

The mappings related to Rechnungsliste have been removed.

2.1.7.4 RETAIL Solution

The mappings related to Rechnungsliste have been removed.

2.1.7.5 Utility Solution

Fixed Bug#18710: Utility Solution contains OFTP adapter instead of FTP adapter (2.1Q1).

SEEBURGER Release Notes for SAP NW Process Integration 48

3 ReleaseNotes 2.2

3.1 Important Information

3.1.1 General
SEEBURGER components deliver their tables as separate software component archives (SCA).
This reduces the risk of data loss because of undeployed tables. Now it is possible to uninstall
components while keeping database tables.
The Professional MessageTracking now comes on two separate CDs. The CD-
ProfMessageTrackingApp containing the database installer and the web front end, and the CD-
ProfMessageTracking containing the API Jar as well as the SEEBURGER FileStore module.
The SEEBURGER global directory is now configurable to support PI systems on Windows clusters
as well.

3.1.2 Upgrade
The following components are no longer used, and can be undeployed:

com.seeburger.messagesplitter.apiwrappers
com.seeburger.xi.functions
com.seeburger.xi.functions.log.lib

Warning: Since version 2.2.0, accessing a non-existing variable will automatically

create that variable with an empty value!

SEEBURGER Release Notes for SAP NW Process Integration 49

3.1.3 Known Issues
The SEEBURGER Adapter Wrapper module does not work in Integrated Configuration scenarios.
This also affects the standalone Advanced Adapter Engine Extended (which only provides
Integrated Configuration).

3.1.3.1 BIC Mapping Designer

Note: Do not use the suggested installation path for 64-bit Windows-based
systems (C:\Program Files(x86)\...), because it contains special characters
(brackets and a blank). It is recommended that you use a short base path for the
installation. Select a base directory on a non-system drive, e.g. D:\BICMD220.

If an earlier version of the BIC Mapping Designer is installed and has to be updated, the installation
folder has to be set to the old installation root folder.

Note: The installation does not select the old installation folder automatically.

3.1.3.1.1 Windows 7 / Windows 8

Generally Windows 7 and Windows 8 are supported. See below for additional restrictions.

Warning: Do not use the suggested installation path for 64-bit Windows-based
systems (C:\Program Files(x86)\seeburger\BIS\), because it is not possible to run
the installation in Windows 7 on this path!

Note: This version installs a signed version of the program. In Windows 7 this can
lead to a window warning after the installation that the program was not installed
correctly. If this warning occurs after the last step, which shows Install Complete |
click Done to quit the installer and activate the Done button.

SEEBURGER Release Notes for SAP NW Process Integration 50

3.1.3.1.2 BIC Header and Trailer Handling

With introducing the field attributes InterchangeID, GroupID, MessageID and the corresponding 'End'
ids, it is possible to support header and trailer handling not only for the well known message formats
like EDIFACT etc., but also for other message formats, too. This means the memory consumption
of the writer is better, because parts of the message can be written during the conversion. The only
restriction here is XML; for XML this automatic functionality is not supported.

3.1.3.1.3 BIC Global Procedures

In cases of BIS upgrade scenarios where global procedures exist that accept parameters of the
type Integer number, or have a return value of the type Integer number, those global procedures
are changed (in BIC MD 6.3.4) and redeployed after the upgrade. All dependent mappings and
global procedures must also be redeployed. This is due to changes in the BIC global procedures
types' system (which changes method signatures) and the fact that method signatures are "statically
resolved" at compilation time. If the dependencies are not redeployed as well, an error of type java.lan
g.NoSuchMethodError may result.

3.1.3.1.4 BIC Runtime Change in Format Handling/Processing

Since version 2.2 the format handling and processing has changed. Please refer to the topics
Formatting Improvements and Format Specification for Message Descriptions in the BIC Mapping
Designer Command Reference manual for detailed descriptions.

3.1.3.1.5 Compiling HL7 Mappings

HL7 message descriptions contain a lot of option fields. The compiler checks all fields, if they are
mapped in the mapping or not. So the compilation for such mappings can take longer. To avoid this,
it is possible to disable the compiler warnings. Menu Window Preferences opens a preferences
dialog with a section Compiler warnings and errors. Here it is possible to switch the warnings to
disable. e.g. warning 0035 "Unimplemented optional record program". Just select Disabled instead of
Warning in the combo box of the ID 0035.

3.1.3.1.6 BIC Mapping Designer Online Help

The online help of BIC Mapping Designer describes the commands for creating mappings. Within the
description all warning and error IDs are listed, which can occur for the command. The IDs are linked
to the main documentation. In the online help it opens the correct document, but does not jump to the
ID with the function Search it is possible to find the ID. Within the PDF file the link directly jumps to
the correct ID in the main document.

3.1.3.1.7 BIC Mapping Designer Editors

In the preferences of the BIC Mapping Designer it is possible to select your own editors for the
different use cases in BIC Mapping Designer. There are also system editors defined (e.g. System

SEEBURGER Release Notes for SAP NW Process Integration 51

Editor, Test environment alternative text editor). The information about the editors are read from the
operation system.
*.txt OS has notepad as editor for all files with extension txt BIC Mapping Designer will open all
*.txt files with notepad
*.xml OS has Opera Browser for all files with extension xml BIC Mapping Designer will open all
*.xml files with Opera Browser

3.1.3.1.8 BIC Mapping Designer Import

During the import of messages, which contain the key word 'qualifier' in the description of fields,
the Mapping Designer offers to mark such fields as 'IsQualifier' automatically. This has effects the
compare module and not the BIC runtime. It offers a possibility to sort some records during the
compare process, so the sequence of the records do not matter.
*.abc OS has no editor defined for files with extension abc BIC Mapping Desinger will throw an
error, if the System editor is used for open a file with *.abc.

3.2 SEEBURGER Data Transmission Adapters

3.2.1 General
The SEEBURGER Message Monitor has been rewritten. It now has enhanced filtering capabilities.
Additionally it has been unified, so it has the same look for all SEEBURGER adapters.
Additionally, the interface now has the concept of transactions, which consist of the main
messages and the corresponding reports. This allows for tracking each message individually, and
it's easy to see if the message itself resulted in an error, or if the report failed.
The SEEBURGER Recover Monitor as well as the Message Monitor have been enhanced to show
a history of errors which belong to the corresponding recover job / transaction.
These errors are also included in the download job operation.
SEEBURGER adapters which support polling (e.g. HTTP, FTP, X.400 / P7 or SFTP) now trigger
a polling immediately if the adapter is started in a period which has pollings configured. The same
applies for channel changes / activation.
Fixed issue with recovery when the recovery store was on a mapped Windows share.
Fixed issue with the automatic recovery which could consume all available threads.
Recovery jobs and message id entries are now compressed
Last automatic retry now causes an alert if failed.
Fixed an issue where the adapters could generate duplicate UUIDs.
Added hashing to duplicate checking if the ID's exceed the SAP's maximum length for IDs instead
of truncating.
Fixed a possible memory leak in transaction handling in PIO systems >= 7.1
Cleanup of the message monitor tables has been moved to the SAP scheduler and can now be
configured with much more flexibilty.

SEEBURGER Release Notes for SAP NW Process Integration 52

 By default, adapters no longer use dynamic attributes for sending. It can still be enabled via
channel configuration. Old channels aren't affected.
Downloading recovery jobs from the front end now includes a list of errors which caused the
recover job.
Fixed listener start and listener restart errors in cluster environments. (2.2.1)
Fixed SEE_BPATTACH table definition for DB6 (DB2 LUW) (2.2.1)
Fixed scheduler (used in adapters which support polling) skipping first planned alarm (2.2.1)
Improved performance of the used logging mechanism on newer SAP JVMs (2.2.1)
Extended the adapters to make use of the "Channel Ping" functionality, also known as adapter
selftest (2.2.1)

3.2.2 AS2
Added the AS2 IDs to the dynamic attributes.
Fixed state of incoming messages in the SEEBURGER Message Monitor in case of failed
initiation.
Fixed the report channel lookup in case of synchronous MDNs.
Fixed an issue where the adapter incorrectly reported a duplicate, and failed to send the message.
Fixed key size configuration for RC2 encryption algorithms (always the default key size of 128 was
used). (2.2.1)
Added a thread pool for pending asynchronous MDNs. This reduces the application thread count
usage when MDNs cannot be sent due to network issues. (2.2.1)
Add support for SHA2 algorithms (2.2.1)

3.2.3 EbXML-HTTP
Fixed issue in recovery when a report couldn't be sent back to the partner.
Fixed issue when delivery reports and transmission reports were used in parallel.
Fixed exception when an EbXML message without a payload is received.

3.2.4 Edifact Secure

USH for GS1 generated wrongly
Verification of AUTACK needed during interchange register
Problem during payload processing with EDC filtered AUTACK
Correlation operation does not report adapter errors
Public key name in created KEYMAN is always uppercase
NPE by getting Certificate during correlation because not present USC segment in AUTACK
format error in See_REGISTER_KEYMAN within traces
UNB Counter and USH counter are not configurable

SEEBURGER Release Notes for SAP NW Process Integration 53

 VerifyEmbedded can not read signature from USR segment for EDITEL
Built-In split of generated AUTACKs was not working. NullPointerException: while trying to get the
length of an array loaded from local variable 'buf' (2.2.1)

3.2.5 FTP
Fixed final flag of the transmission report if other reports are required.
HostDir now allows '(' and ')'.
Active mode, port range: All new and retried connections bind on same port.
Polling for EBMX ANX FTP Server profile was not working.
Adapter internal split didn't work.
Messages are initiated although they are not deleted from the server.
Gemark III list operation did not allow white spaces in the sender id.
Added support for the simpler list command "NLST" (2.2.1)
Added support to change to the target directory before uploading files (2.2.1)
Added support for Covisint (2.2.1)

3.2.6 HTTP
In BestEffort mode (synchronous call) and HTTP method "GET" the response will now be returned
to the caller.
Fixed an issue preventing access to SSL encrypted sites which used wildcard SSL certificates.
Extended the HTTP Adapter with logical resource synchronization (2.2.1)

3.2.7 OFTP
Fixed issue where OFTPv2 accepted SSLv2 connections to a TLS listener.
TransferInfo attachment has been removed.
SSL/TLS listener now refuses to start when the server key is missing.
In some cases the startup time has been increased considerably.
Fixed issue with listener grouping in case the network interface wasn't specified
A separate channel configuration for signed EERP verification has been added (V2 only)

3.2.8 PGP
Passwords are now encrypted in the module configuration (separate configuration parameters are
used, refer to the documentation for details).
Fixed issues were not all parameters could be set via dynamic attributes.
Fixed user caching issues in the front end.

SEEBURGER Release Notes for SAP NW Process Integration 54

 Fixed compatibility with older PGP products (e.g PGP 6.5.8)

3.2.9 SFTP
Remote commands can now be executed before or after a file has been up / downloaded.
Within one directory multiple filename patterns can be used to download files.
A maximum file size can be configured. Files greater than that will not be polled from the server.
Check for complete file has been added. SFTP now checks if the file size did not change for a
configurable amount of time and only polls the file thereafter.
Dual authentication support (key + password) authentication has been added.
Prevent unlimited waits for broken sockets.
Fixed check if the report channel (used for transmission reports) is available.
Added a configuration option to fail if a file with the same name is already available on the server
to prevent overwritten files.
Removed unnecessary entry from the message monitor if no transfer actually took place.

3.2.10 X400 / P7
The X.400 / P7 adapter now supports strong authentication support.
P7 now sends messages as 84 standard.
Fixed an issue when searching for inbound channels and some channels have been stopped.
Disabling the duplicate check did not work. (2.2.1)

3.3 SEEBURGER Modules

3.3.1 General
New functions for string conversion have been added to the evaluation engine available in the
module configuration. Newly available are: trim(), upper() and lower()
The module configurations evaluation engine did not behave correctly when using braces and the
NOT operator.
Enhanced export and import mechanisms. Several issues with timeouts and large datasets have
been fixed. (2.2.1)

3.3.2 Apsec
Fixed issues with using the evaluateXPath() function in the module configuration

SEEBURGER Release Notes for SAP NW Process Integration 55

3.3.3 DSig
DSigInfo XSD was missing "Unpacked" element in document type (2.2.1)

3.3.4 Message Splitter

MessageSplitter front end now remembers the last sort order as long as the session is active.
Deserializing big recovery jobs required huge amount of free memory. This has been drastically
reduced.
Support for getCounter(), getVariable() and evaluateXPath() functions in the module configuration.
Alerting added if last automatic recovery retry fails.
Added queue monitor to the System Status front end, to see if messages queue up.
Recovery now only processes up to five jobs in parallel and doesn't interfere with current jobs.
Fixed issue in MessageSplitter front end where creating and copying configuration entries for a
"Communication Component Without Party" scenario was prohibited with a pop-up "Please set a
valid Party." (2.2.1).
Splitter Frontend did not allow to create a configuration without sender party. (2.2.1)

3.3.5 Payload Dump

Fixed issue where the module didn't close all streams.

3.3.6 Replace String

Fixed issue when trying to replace the last character of an attachment.
Fixed exception when patterns overlapped.

3.3.7 Start Local App

Counter handling was not thread safe (could lead to duplicate counters).
Fixed timestamp format (leading zeros could be missing).
Fixed possible resource leak where closing streams could be missed.

3.3.8 Zip
Fixed issue where directories were extracted as 0-byte files.

SEEBURGER Release Notes for SAP NW Process Integration 56

3.4 SEEBURGER Converter Suite

3.4.1 General

Attention: If you upgrade from a previous version, please note that all mappings
have to be recompiled in order to work!

Attention: Sometimes redeployment of mappings without restarting the system

causes class-loading issues. Restart the system if such issues occur!

3.4.2 BIC Mapping Designer

Introduction of a Mapping/Message/Global procedure compare view. This topic is described in the
manual BIC Mapping Designer Operation, chapter Compare.
Regular expression support. (Automatic import via Schema is supported). This topic is described
in the manual BIC Mapping Designer Operation, chapter Regular Expressions.
Import of SAP IDoc Parser structures. The settings for SAP and the import to the BIC Mapping
Designer is described in the manual BIC Mapping Designer Operation, chapter Import of SAP
IDoc Parser Structure.
Code lists are now supported by drag and drop and code completion in the mapping panel. This
topic is described in the manual BIC Mapping Designer Operation, chapter Code Completion and
Drag & Drop.
Mapping printing is extended. It is possible to print only the mapping elements used in the
message. The printing is described in the manual BIC Mapping Designer Operation, chapter Printi
ng.
Folders for source, build, backup, log, and process data files can be now set for each workspace.
This topic is described in the manual BIC Mapping Designer Operation, chapter Workspace Folder
Preferences.
Refresh (F7) of the project view is parses the source folder and updates the view.
The behavior of all file choosers has been improved.You are now able configure the default
folders for several locations like the default source file folder or reference files folder in the test
environment. refer to the documentation for more details.

3.4.2.1 Workspace Folders

The files of a workspace are separated in different folders depending on their use. The folder for
source, build, backup, log and process data can be set to different folders.

SEEBURGER Release Notes for SAP NW Process Integration 57

3.4.2.1.1 Workspace Wizard

A new workspace wizard for the creation of new workspaces allows to set the workspace folders,
the runtime, the configuration and to import objects from other installations and from a repository
during the creation of a new workspace. Please refer to topic Workspace Wizard in the BIC Mapping
Designer Operation manual.

3.4.2.2 Mapping Editor

The variable panel now allows a copy and paste operation to another variable panel, or to the
mapping editor panel.
For fields with a code list, the code completion offers the possibility to create a select case
statement with all code values.

3.4.2.3 Message Editor

The search now allows to search for values in the messages. Please refer to topic Message Editor |
Search Dialog in the BIC Mapping Designer Operation manual.

3.4.2.4 Debugger
The debugger integrated into the BIC Mapping Designer now supports the debugging of child
mappings and global procedures. Please refer to topic Bic Mapping Debugger in the BIC Mapping
Designer Operation manual.

3.4.2.5 Migration from Older Versions

If the installation of the BIC Mapping designer finds an older version in the installation folder, a
migration tool is called. The tool will perform the following steps for every workspace in the installation:

Copies the most important configuration files to the new folder (configuration of the demo mode,
license handling, the test environment settings, juprefs.properties). Settings for the last state
of the project view (e.g. selected element), the last opened mapping and message panels are
not migrated. If the BIC Mapping Designer is started again, it starts with the settings of a fresh
installation.
Sets the source folder to the old source folder.
Renames the folder for the compiled mappings to backup, so they are not used for new tests. (All
mappings have to be compiled for tests in the BIC Mapping Designer again).

3.4.3 BIC Runtime

The BAPI adapter now uses JCO 3. JCO 2 is no longer supported! This topic is described in the
manual BIC Mapping Designer Command Reference, chapter Functions for SAP BAPI Calls.

SEEBURGER Release Notes for SAP NW Process Integration 58

 BIC now automatically sets/reads the encoding to / from the attachments in the BIS environment.
Introduction of a new data type "hashmap". This topic is described in the manual BIC Mapping
Designer Command Reference, chapter Arrays and Hashmaps.
Improvements in the format handling. The old behavior is still used for the old mappings in the
default case, but the new behavior can be switched on. The new behavior is a default setting for
new mappings. This topic is described in the manual BIC Mapping Designer Command Reference,
chapter Formatting Improvements.
Improved list of error and warning descriptions. A list of all errors and warnings are described in
the manual BIC Mapping Designer Command Reference, chapter List of Errors/Warnings.
Support of CRLFs between key and data fields in INHOUSE formats.
Swift support of repeatable fields with CRLFs as field delimiter.

3.4.4 BIC Compiler

The BIC compiler detects unmapped fields during the compilation of a mapping. This means the
compiler throws errors or warnings if a field which is not mapped is detected in the input or output
structure.
The BIC compiler also checks if all values from a code list are mapped within a select case
statement and an else case statement with a thrown error exits. If this is not implemented, a
compiler warning is thrown. The mapping editor in the BIC Mapping Designer supports the
mapping developer via code completion to create the correct select case statement.
It is possible to switch these warnings to errors, so it is not possible to compile mappings with not
mapped fields or missing code list values in select case statements.

Please refer to the topic Troubleshooting not mapped data in the BIC Mapping Designer Operation
manual.

3.4.5 BIC Module

Added error reporting if configuration could not be loaded correctly.
Fixed error when the XI message does not have a MainDocument attached.
Fixed issue where the getCounter() function was evaluated twice on each module call.
Fixed issue with useAttribIfSet which didn't expose all parameters to be set via dynamic attributes.
Fixed issue with the evaluateXPath() function.
Enhanced error message if mappingName was not set.
Added support for non printable characters as source and destination delimiters.

3.4.6 Classifier Module

Fixed issue with "errorIfEmpty" parameter

SEEBURGER Release Notes for SAP NW Process Integration 59

3.4.7 SeeFunctions
Prevent logging to STDERR and use the SAP logging API instead.
Fixed an issue with corrupted configuration files which resulted in a "PermstoreException: Could
not read properties Failed to invoke method. Reason : java.lang.reflect.InvocationTargetException"
when trying to access variables or counters from PI message mappings. (2.2.1)

3.4.8 Standard Mappings

Wrong GS date format set in "FunctionalAcknowledegement_to_A_997_ALL"
Incoming EDIFACT messages fails when UNA segment not standard value
Mappings_sys: Wrong FunctionalAcknowledgement output using See_Tradacom MainMapping
No split per UNH in EDIFACT UNG mappings
Encoding is not transported to child mapping if UNH/ST split is disabled
Wrong segment position in FunctionalAcknowledgement when conversion error occurs

3.5 SEEBURGER Workbench

3.5.1 Digital Signature

Fixed empty result page when saving a signature server profile.

3.5.2 Error Monitor

Provided new front end to view errors and warnings of SEEBURGER components like adapters
(2.2.1).
ErrorMonitor DB table SEE_ERRORMONITOR could be deployed on DB6 (DB2 LUW) (2.2.1)

3.5.3 Mapping Variables

Fixed updating existing values via the import mechanism.

3.5.4 Recovery Monitor

Fixed Recovery Monitor issue where the monitor was not able to delete or download jobs due to
classloading issues (2.2.1)

SEEBURGER Release Notes for SAP NW Process Integration 60

3.5.5 SEEBURGER CPA Cache Search
Added configuration options to hide passwords in the CPA Cache Search front end. Please see
the manual for details.
Fixed issues where long values in channels could not be displayed.

3.5.6 System Status Frontend

Provided insight into adapter internal queueing. Queues can now be monitored. (2.2.1)
Improved System Status Frontend for cluster. Now all cluster nodes can be monitored. (2.2.1)

3.6 SEEBURGER Professional Message Tracking

3.6.1 MT-API (Java)

Added methods for setting the cFreeDecimal1 - 5 as BigDecimal from within SAP Message
Mappings
Removed SEEBURGER configuration layer from MT-API to work around class loading issues in
the PI mapping runtime. This should fix "Unknown data source 'SmartiDS2'." (2.2.1)
Provided an API to access FileStore from within PI mappings. (2.2.1)

3.6.2 Filestore Module

Added a second method for sub-directory organization in case the XI message ID was not evenly
spreaded on some systems.
Extend the filestore module to be able to use the new filestore servlet syntax.
Manual mode can now store the playload if set.
The module didn't propagate all errors correctly.
Separated module and front end distribution.
In override mode, values with empty strings overrode the default values.

SEEBURGER Release Notes for SAP NW Process Integration 61