W H I T E P A P E R

BUSINESS INTEGRATION SERVERThe gateway to your business partners

2

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.1 Whitepaper Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.2 Integration Trends . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.3 BIS 6 Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 7

2. BIS 6 Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 - 9

3. BIS 6 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

4. Process-/Service Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4.1 Process Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 - 13

4.2 Process Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4.3 Prozessausführung . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4.3.1 Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

4.3.2 Transformation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 - 16

4.3.3 Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4.3.4 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

4.4 Process Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4.5 Process Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

5. Additional Portal Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

5.1 B2B:Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

5.1.1 Message Tracking/Process Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

5.1.2 Reporting Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

5.1.3 Target Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

5.1.4 Task Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 - 25

5.2 Partner Enablement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

5.2.1 Data Distribution Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

5.2.2 EDI/B2B Roll-Out-Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

6. System Structure and Implementation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

6.1 Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 - 28

6.2 Implementation Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 - 29

6.3 Internal Structure – Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 - 31

6.4 Function Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 - 33

6.5 Release-Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

7. Product Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Content

3

1.1 Summary

This whitepaper gives a technical overview of

SEEBURGER’s next generation Business Integration

Server (BIS 6) which has superior technical features

and offers a comprehensive range of applications for

a company.

The main focus is on present process cycles within

business process phases which are supported by

BIS 6, ranging from process development to process

analysis.

SEEBURGER’s portal applications take another focal

point. They extend BIS 6 with browser based user inter-

faces and thus allow the involvement of employees in-

to current automated processes (Human Interaction).

This paper describes the BIS 6 service oriented system

architecture and gives a compact presentation of pro-

duct features. Technical implementation details, back-

ground on SEEBURGER’s services and optional mo-

dules are demonstrated, together with the SEEBURGER

BIS 6 Release-Strategy and complementary products.

This document specifically relates to IT executive ma-

nagers and technical staff of companies which already

have been involved in business integration processes

and which are now looking to realize a more efficient

process execution solution for their company. The tech-

nical demonstration of current integration approaches

within the area of corporate requirements is a compre-

hensive decision support by means of searching for the

right integration strategy (picture 1).

1. Introduction

BIS 6 – Products

Business Process Management

B2B Gateway

Business Process Monitoring

Business Process Development

Business Process Execution

Transport

Transformation

Adapter

Component

Proc

ess

Partner Enablement

B2B:Portal

Self-Service

Small Partner Connectivity

B2B Operational Dashboard

Event & Exception Management

Process Visibility

Activity Monitoring & Analytics

picture 1picture 1

B2B:Portal

Self Enablement

4

1.2 Integration Trends

The increasing automation by means of integration and

business process management systems demonstrates

a current trend within B2B contract, shipment and pa-

yment processes. Standardized processes are transacted

fully automated and being monitored with management

tools used by department employees. In case of error or

escalation the responsible employees are being involved

to interactively solve the problem. This involvement also

occurs within partial automated processes like purchase

orders which have to be approved by the responsible

person before the bill is sent.

Consolidations in the course of corporate IT organizati-

ons are also a trend. The IT departments of several com-

panies are being centralized and from now on service

units with centralized applications provide essential IT

services. This service structure is reflected within SOA

structures.

In order to leverage resources of several computer no-

des, high increasing data volumes are approached by

structured BIS 6 installations. Also, for security reasons

it is possible to outsource communication into a DMZ.

The implemented software solution requirements for in-

tegrated data and document transfers with national and

international business partners, as well as in between

internal systems, highly increase as a result of the cur-

rent integration trends:

• Managing increasing complexity of on-going processes

• Managing increasing number of business partners

• Connecting increasing number of involved IT systems

• Diversification through increasing country

specifications

• Rapid high volume data management

• Comprehensible display of automated processes

controlled and monitored by department employees

• Organizing and controlling manual intervention

by employees in case of approvals, breakdowns,

errors and escalations

• Demand for quicker reactions on new business

requirements

• Observing statutory provisions for electronic

business management processes

• Increasing cost pressure and rationalization

requirements

• Higher data protection and security requirements

• 100 % partner integration

5

1.3 Business Integration Server (BIS 6) – Product

BIS 6

SEEBURGER’s next generation Business Integration

Server (BIS 6) is addressed as an integration and busi-

ness process management platform which handles all

current, future and classic requirements related to the

internal and external business integration of trading

partners and applications.

BIS 6, as a Message Oriented Middleware (MOM) and

B2B Gateway, commands a superior any-to-any conver-

ter for EDI/B2B as well as XML Formats. The Mapping De-

signer offers the ability to develop individual mappings.

It includes capabilities of a traditional Enterprise Ser-

vice Bus (ESB) and Business Process Management Sys-

tems (BPMS). Also, the integration solutions provide a

comprehensive supply of communication modules and

application connectors.

The integrated Process Engine is based on Business Pro-

cess Execution Language (BPEL) Standards and makes

any business process application possible. The Process

Designer as a process development tool supports the

standardized demonstration of business processes as

Business Process Modeling Notation (BPMN) Graphics

and integrates functional and technical processes in

one application. The functional layer provides the do-

cumentation and specification of processes through

business analysts, while the technical layer shows the

implementation of the active solution (picture 2).

A sophisticated Trading Partner Management (TPM)

enables visibility and time-saving business partner

management without redundancies.

Cross-functional collaboration on process modeling

Design Interface for business analysts Interface for implementers

picture 2picture 2

6

B2B:Portal

SEEBURGER’s B2B:Portal Module extends BIS 6 functio-

nality to observe and notify when human intervention is

necessary thus involving users into current automated

business processes.

B2B:Portal Message Tracking gives the administrator

insights on usually covert information flows.

The Target Monitoring module continuously compares

the information flow with the adjusted user expectati-

ons and interferes proactively in case information does

not get through or arrives unexpectedly.

The Reporting Framework with its graphic Report De-

signer assists the evaluation and demonstration of

processes which occur at the BIS 6 system controlled

interfaces of the company.

The Task Manager application enables the process inte-

gration of corporate users with business partners. The

completion and correction of incomplete or defective

data, the situational decision about further processing

workflows, for instance defective data from business

partners, or the check and approval of vouchers for

entries are just a few scenarios that the Task Manager

provides. The disconnection between data integration

and interactive workflow is no longer an issue. BIS 6 is

therefore not just a system for both application cases

but rather allows their combination to one integrated

business process, thus creating more visibility and

efficiency.

Partner Enablement

Partner Enablement enables portal applications to in-

volve more trading partners or trading partner groups

into the automated management of business proces-

ses.

From Roll-Out-Portal, to system-controlled connection

of trading partners, to self-services for administra-

tors and users and even to complementary data ex-

change solutions, the integration of companies into

the automated world of process management knows

no boundaries.

The following graphic shows the interplay with human

intervention and the technology with the result of a vast

automation of management processes.

7

Vast Automation – Interplay between human intervention and the technology

Mapping Designer Adapter Service

ConversionService

ComponentService

TransmissionService

SAP XI/PI, Baan, ...

XML, EDIFACT, ANSI,

CSV, ...

Zip, Encrytion, Signature, Splitting,

Merging, ...

JMS, SOAP, OFTP, X.400, HTTP, MQ, ...BPE

Broker/ESB (JMS/RMI/

...)

SEEBURGER Business Integration Server

Users/trading partners

Technical execution layer

Process Designer

Repository Service

Rules Engine

Inspector

Logging/Auditing

Trading PartnerManagement

picture 3picture 3

8

Modern and Future-Proof

SEEBURGER’s Business Integration Server (BIS 6) is a

J2EE Standard-based, platform autonomous applicati-

on. Within its structure the system provides a Service

Oriented Architecture (SOA).

The implementation is based on general availability

and industry standards such as: e. g. BPEL, BPMN, XML,

SOAP, UDDI, JavaEE. The use of these standards allows

flexibility in using the BIS 6 system. Thus, the system

can play the backbone role within the construction of

a SOA landscape. It can also stand as a platform for

the supply of specific integration services such as: e. g.

EDI, B2B or A2A Communication and/or Conversion

Services, if a backbone is not yet available.

Versatile and Upgradeable

BIS 6 is modularly structured and the solutions spectrum

is versatile, which can be realized with the support of

available BIS 6 modules. It ranges from classic EDI/B2B

data exchange with the integration of internally involved

systems (EAI/ESA), to illustrate complete business pro-

cesses from voucher entries to interactive production

steps. The modularity allows the applications to adapt

to its requirements which are set up by a company on

its customer and supplier base integration capabilities

in the supply chain. The modular architecture, which

expresses itself technically within pertinent frameworks

and interfaces, is concurrently based and guarantees

that SEEBURGER shortly reacts to new and future cus-

tomer given requirements through the supply of new

function modules.

Flexibility

Alongside the modularity, which allows flexible solution

arrangements, SEEBURGER also provides development

tools to its customers.

The Eclipse based BIS:DeveloperStudio comprises of

graphic tools for process modeling in order to define

mappings for different information formats as well as

a program environment to create customer based func-

tions within numerous user exits, which the systems

offers.

Thus, the user receives an option to flexibly create inte-

gration scenarios by individual needs or desires.

The integrated Version Management (based on CVS

or Subversion) supports the company within the ful-

fillment of statutory provisions for the traceability of

electronically managed processes (GoBS).

Safe, High Performance, Scalability

BIS 6 supports clustering. In connection with a clus-

tering applicable hardware, BIS 6 scenarios can be

created with high availability. The configurable Parallel

Processing and Multithreading, arrange performance

scalability with the use of reusable and multi core com-

puter systems.

The options to specifically outsource internet commu-

nication modules to separated working stations within

the DMZ, instead of working with the DMZ Proxy Solu-

tions, provide the required security regarding partner

integration with the use of the internet.

2. BIS 6 Capabilities

9

An intelligent Queue-Node-Concept makes it possible

to center computing time-intensive processes such as:

e. g. conversion or safety operations (coding/signature)

to dedicated work stations. In case such a work station

is not sufficient to manage ongoing processes, it is pos-

sible to dynamically activate additional nodes, i. e. via

configuration and without system shutdown.

Transparency

Automated ongoing processes have to be monitored

both technically and functionally. Therefore the Front-End

BIS 6 Systems provide monitors, which are customized

to different user roles. BIS 6’s technical monitoring tool

– the BIS:Inspector – focuses on administrators and

users. In a consolidated view, key data about the system

process instances is sorted by status and stage class.

The user has now the ability to gradually »navigate into«

input and output parameters and execute the time of

individual process steps.

By the use of the browser based B2B:Portal Modules

administrators receive transparent insights into the ex-

change of document data. Thereby, statistic evaluations

indicate trends and development within the exchange of

document data.

picture 4picture 4

BIS 6 Capabilities

BIS 6

Flexible

Process Templates User Exits CVS

Standard Mappings DeveloperStudio

Eclipse

Versatile & Upgradable

EDI B2B A2A

ESB BPM

Safe, High Performance,

Scalability

Clustering Signature Queue-Node-Concept

Coding DMZ

Modern & Future-Proof

J2EE UDDI Platform Autonomous SOA BPEL BPMN

XML SOAP

Transparency

Business MonitoringKey Data

Technical MonitoringStatistics KPI

10

BIS 6 applicable to multiple applications and tasks

within a company. Especially in the following application

fields where SEEBURGER preconfigured solution sets:

• B2B/EDI Gateway manages the exchange of business

processes and therefore provides automated inte-

gration of suppliers and customers. Preconfigured

business solutions are available.

• EAI/ESA platform for the automated integration of

internal applications and processes.

• ESB as within SOA concepts and/or as an integration

services platform. Either supply as a single service

(e. g. conversion) or as a complex EDI service.

• Document and Process Management for the

definition and demonstration of document based,

interactive processes (workflows) such as: e. g.

releases, demand requirements etc.

• BAM and BI Platform for decision support via compila-

tion, processing and evaluation of important key data

for the different ongoing business processes.

• Managed File Transfer Center to control and monitor

file transfers between applications, locations and

partners.

Any mixture between the functions within the mentioned

application fields is possible at any time.

3. Overview BIS 6 Applications

11

Within the automation of business processes software

solutions are required, which are able to map, manage

and monitor all types of processes. Processes differ in

private and public processes. Private processes occur

in-house and under the exclusive involvement of inter-

nal systems and resources. Public processes involve

external processes and resources with customers and

suppliers.

To a great extent SEEBURGER’s BIS 6 provides a soft-

ware solution which automates both public and private

processes for the company.

According to the process automation requirements,

BIS 6 features a process oriented architecture, which is

described in five Business Process Life Cycle phases:

Process Development, Process Management, Process

Designer, Process Monitoring and Process Analysis.

All Business Process Life Cycle required modules

(e. g. Process Designer) are available and the pro-

cess required functionalities are procured as Services

(e. g.Conversion Service).

4. Process-/ Service Oriented Structure

Process and Service Orientation with BIS 6

picture 5picture 5

ERP EDI

Private Processes

Company

Public Processes

Customers, Suppliers etc

SCM Legacy etc. B2B Web etc.

Orchestration LayerPortal Applications

Orchestration LayerProcess Development Tools and Mapping Design

Service LayerAdapter Service, Transformation Service,Component Service, Transport Service

Integration LayerData Integration, ESB

Development Managem

ent Process

M

onito

ring

Ana

lysis

BusinessProcess

Life Cycle

12

4.1 Process Development

BIS:DeveloperStudio with Process Designer

Regarding Process Development BIS 6 provides all re-

quired tools and options to both organizationally and

technically define private and public processes.

Therefore, BIS 6 uses the open standards such as BPEL

(Business Process Execution Language) and BPML (Busi-

ness Process Modeling Language) for modeling and

monitoring ongoing processes.

Process Development takes place within the BIS:De-

veloperStudio, which is an integrated, graphical deve-

lopment environment based on Eclipse. The Process

Designer, which is implemented as an Eclipse Plug-in

along other tools, is a function module within the BIS:

DeveloperStudio.

With the Process designer a business analyst can graphi-

cally models XML scripts without dealing with the XML

layer. The individual BPEL based processes can there-

fore be defined rapidly and conveniently (Workflows,

Subworkflows, Loops, Try/Catch, typed Variables, XML

Scheme, Correlations and Scripting).

Moreover, the BIS:DeveloperStudio provides further

support to the process modeler and analyst, which is

needed in order to create a complete, executable solu-

tion. That includes, e. g., a XML Scheme Editor, and a

Scripting Environment with a SDK to create customized

components. For instance, if existing applications have

to be integrated within a company, as well as an Editor,

to individually create the structure of the Trading Part-

ner Management.

All elements which belong to one solution, are being

managed by the Workspace within the BIS:Developer-

Studio. Inside of the solution, the BPEL process is just

one component even though it is the most important.

BIS 6 BPEL based Process Management and Process

Definition provides the following Advantages:

• Enhanced visibility of ongoing processes

• One interface between process involved compon-

ents and public and private processes

• Easy, fast and flexible process development and

changes

• Through the Process Designer, using BPEL, process

development or adaption is not just an option for

software developers anymore

• Transaction security and error handling within the

process

• Definable troubleshooting and escalation chain

• Support of long ongoing processes

• Support of correlations and parallel processes

• Support and rather integration of Web-Services

within processes

• Support of synchronized and unsynchronized

processes

• Integration of SOA based infrastructures

13

Process Transport Mechanisms

For the transport of solutions into a live system, the

BIS:DeveloperStudio provides a Wizard with which a

transport object is provided. Then it is deployed on the

BIS-Central Instance using the deployment function.

For the development stage of processes the Developer-

Studio can be integrated into a (CVS).

Process Design

Development System

BIS 6

Activation for Production

QA System

BIS 6

BIS 6

Deployment Wizard

Solution Transport File

CVS

picture 6picture 6

Productive System

Approval

Activation

for ApprovalBIS:DeveloperStudio

Process Designer

14

4.2 Process Management

Front-End for Configuration and Monitoring

Within BIS:Front-End, BIS 6 provides the necessary

process management tools which are required in order

to manage and configure processes, as well as invol-

ved components and systems. BIS:Front-End is a Java

Web Start based Client-Server application. The Client-

Software is automatically installed on the users’ work-

station within the first call. In case of a software update,

which only has to be run on the server, the update will

automatically take place on the client side.

BIS:Front-End consists of:

• User administration and administration of user

privileges

• Standard, permissions and event management

• Activation management and revision Control

• Specifications of processes

• Trading partner management

(partner specific settings/process guidelines)

• Components and run-time management

• Controlling of priorities and load sharing

(e. g. queues)

• Monitoring of system status, processes,

and connections etc.

4.3 Process Design

Within the center of BIS 6 the Process Design is located

using the Process Engine which manages the technical

processing of defined private and public processes.

The BPEL based Process Control guarantees secure

transaction management as well as an efficient load

and resource management with components involved

in the process.

Thereby simple installations are supported as well com-

plex scenarios where different process components are

shared across several computers.

Besides the aforementioned basis functions, the major

task of the Process Design layer lies within the chore-

ography of four core function areas according to the

created process definition. Those areas will be shortly

demonstrated in the following.

15

4.3.1 Adapters

Adapters serve as a bi-directional connection within

external applications and systems. Thereby, BIS 6 ad-

apters can be used based on the system connection,

for data exchange.

Since BIS 6 provides a diversity of preconfigured ad-

apters for different systems, a rapid and configurable

connection of these systems can be realized without

complex interfaces.

From classic ERP adapters like, SAP, Baan or JDE, to

Web-Services and database adapters, to specific host

integrations, there is hardly a gap which cannot be

bridged by an available adapter.

4.3.2 Transformation

The different systems create the most diverse data

formats. Additionally, there are multiple regional and

industry specific massage standards.

In order that the systems can communicate with each

other, a central tool is required, which translates bet-

ween the different formats. With its translation layer,

BIS 6 provides a functionality which enables a conver-

sion of almost any structured data formats.

Among the supported message formats are: Flat-Files

(in-house messages), CSV-Formats (comma separated

vectors), EDI Standards like the Europe leading EDIF-

ACT with its subsets such as: e. g. EANCOM, EDIFICE,

EDIFURN etc., the North America typical ANSI X.12

Standard or the UK popular TRADACOM Standard, the

regional automotive standards VDA, ODETTE, GALIA,

CAP, ARUA, banking standards like DTA, SWIFT, SEPA,

Japanese EDI Standards like EAIJ, HSWS, the aviation

and defense industry standard AECMA, all DTD/SCHE-

ME based XML messages like ebXML, cXML, xCBL,

openTrans, CIDX, PIDX, RosettaNet and application spe-

cific formats like IDOC and XML IDOC, Oracle In-house

Messages etc.

Besides these data based standards, the BIS 6 conver-

sion engine can directly convert into a database or call

to it or directly communicate with interfaces such as:

e. g. SAP BAPIs.

16

The translation requirements are being defined in the

form of Mappings using an additional tool, the Mapping

Designer.

During the transfer into the runtime environment map-

pings are compiled to executable Java classes which

make the conversion, in comparison, extremely quick.

The Mapping Designer provides a graphic user interface,

inclusively drag&drop mapping functions, the graphic

demonstration of to be translated message structures

and an easy-to-learn script language directly on the

business analyst.

Thus, mappings can be created easily by non-software

developers. The integrated test environment makes the

mapping development very efficient.

One mouse click makes it possible that messages can

be compiled and converted and the result can automati-

cally be aligned with provided reference messages.

The Mapping Designer consists of the Mapping Repo-

sitory which manages the access of developers to the

mapping source code and provides revision control and

archiving management (picture 7).

Thus BIS 6 operates as the universal translator between

systems and applications. Complex individual develop-

ments are being saved and can be completed fast and

flexibly with the provided tools.

Collaborative Mapping Design with Revision Control and Archiving Management

picture 7picture 7

Test SystemMapping Repository

Mapper Mapper Mapper Mapper

Productive System

17

4.3.3 Transport

Data must not only be extracted or deployed to diffe-

rent systems, it also needs to be transported securely

between systems, applications and between trading

partners.

Hereby, the capability is needed to operate both as a

sender and as receiver of data. Therefore, BIS 6 provi-

des multiple different transport functionalities as well

as for transport.

BIS 6 provides all popular transport types:

• Basis protocols like email via SMTP/IMAP/POP3,

FTP/S, SFTP, JMS, HTTP/S and P7/SSL.

• Pre-configured adapters for the connection of Van

Providers required for EDI operations such as: e. g.

the Telebox400 (DE), Atlas400 (F), GXS (global), MCI

(USA), IBM (global), AT&T (global), Exite (AUS) etc.

• ODETTE File Transfer Protocol (OFTP) in all variations

(X.25, X.31, ISDN, TCP/IP – ENX and OFTP V2 for

internet data exchange).

• Protocols, allowing a secure and reliable message

transfer via internet: EDIINT, AS1, AS2, AS3 (EDI over

INTernet), RNIF

• (RosettaNet), ebMS (ebXML messaging), CIDX

(Chemical Industry Data eXchange) etc.

• Transport mechanisms based on Web Service

Protocols (SOAP, SwA (SOAP with attachments)) etc.

The BIS:DeveloperStudio includes tools that also pro-

vide the option to integrate on the customer side for

available communication applications within a project.

BIS 6 therefore provides all functionalities regarding

transaction security (guaranteed transactions, one-time

transactions, transactions via alternative ways etc.) as

well as data security (data confidentiality and identity

privacy towards sender and receiver, protocol-depen-

dant).

Adapters have a resource management available which

enables the reservation of communication channels,

in the case of incoming and outgoing connections,

certain partners, certain protocols or messages display

different priorities.

All adapters also support the sending and receiving of

different identities (multi-client capability).

The BIS 6 system architecture allows the operation of

all communication protocols within the DMZ, that is

within a through firewalls disconnected internal net-

work area of the network. This occurs within internet

communication.

The Systems internal messaging results from Web Ser-

vice Calls (attachments, Complex XML Types) and JMS

Queues.

18

4.3.4 Components

Conversion and communication within partners and

applications belong to the core functions of integrati-

on scenarios. There are multiple additional functions,

though, which an integration server must be able to

perform including:

• Batching of messages

• Splitting of messages on the basis of different

criteria (message type, receiver etc.)

• Merging of messages

• Compressing of messages

• Coding and Signatures

• Insertion of sequence numbers

• Classifying of messages

• Extracting message information

(e. g. for content-related forwarding)

For all these components the BIS 6 package includes a

broad selection of process components which can be

used as pre-defined modules within the processes.

As a result of these pre-defined process components,

complex processes can be rapidly realized without

investing major development time.

It is furthermore possible, at any time, to either use

or integrate local or foreign function components.

BIS 6 provides the BIS:DeveloperStudio several options

(Web-Services, API and Script Integration) for this.

More integration components are available within the

following describing B2B:Portal applications.

19

4.4 Process Monitoring

BIS 6 supports Process Monitoring in multiple ways.

The monitors within BIS:Front-End provide a standard

user-interface in order to monitor and track defined

processes. The users also has the option to intervene

ongoing processes:

• Process overview

• Process monitoring of involved components and

systems

• Error and escalation monitoring

• Monitoring of data transports

• Insight into indepth data

• Visualization of data streams

• Transaction and error management

• Manual processes changing (stop, continue,

cancel etc.)

• Centralized, revision-safe logging of all involved

processes, systems and components

In order to analyze cause of an error the system provides

documentation for previous or completed processes,

protocols and trace data. BIS:Front-End provides access

on system protocols (log viewer) also in case of multiple

installation.

On a system level there are two options to define so-

called monitors. Monitors observe system internal

counts and react in the event adjusted limits are too

high or too low. It is possible to tie an action to the

event of excess or shortfall:

• Creation of SNMP traps for external systems

• Creation of a JMX message

• Activation of email transmission

Error recovery on a process level can even be provided

directly within the process definition. In the event certain

process, component(s) or a group of process step have

errors, error recovery immediately sends out an error

alert.

Within the process of error recovery the process imple-

menter pinpoints what needs have to be completed in

order to resolve the problem. Typical actions are:

• Sending an email to the involved users and/or to

partners

• Sending an alert to the management

• Create a task within the B2B:Portal Task Manager.

Thus, a user is prompted to clarify the issue and he

has to choose among several process through action

tools provided.

• In case of transport errors: Message transport th-

rough an alternative means can be configured within

the master data

20

To receive an overview of the system status, BIS:Front-

End provides the so-called Inspector and Dashboard.

The Dashboard gives an insight into the capacity level

of software and software environment on the basis of

using key data and graphic demonstration.

At the administration level within the Inspector each

process status that takes place in the system can be

followed and a drill-down function enables the tracking

of individual components down to the parameter level

(picture 8).

The B2B:Portal Operational Dashboard provides an

option to even present the system status to administra-

tors within the company (from Version 6.4).

4.5 Process Analysis

The B2B:Portal Reporting Framework enables a process

analysis using statistics based on selectable key data.

In section 5 this will be explained in greater detail.

Application Options:

• Overview Process Capability/Process Progress/Trend

Analysis

• Providing Data for additional services

• Identification of Error Rates per Partner/System

• Identification of most frequently errors and their cause

picture 8

21

Portal Human-Machine Interface

The management of business processes today is, whe-

rever possible, fully automated by IT systems. However,

daily businesses require an insight into the processes

in order to intervene in case of error alerts or to meet

releasing decisions within processes.

Therefore, SEEBURGER developed a portal which serves

as an interactive interface between integration solution

and employer. The portal provides a use-friendly inter-

face to administrators or responsible officials and gives

them an insight into automated processes or the option

to interfere in ongoing processes (picture 9).

5.1 B2B:Portal

B2B:Portal consists of multiple standard function mo-

dules. Following the modular concept of BIS 6, those

modules can be used and arranged according to specific

customer needs.

The user gets access via a web browser. The access can

be from a central website, which can either be accessed

over the internet or made accessible internally to busi-

ness partners.

The hierarchy based user administration controls which

functions the user is allowed to employ and which data

he can see and edit therein.

5. Additional Portal Features

Exemplary EDI Business Process with Employee Interaction via Portal

Sending Shipping Order

Invoice Reception Process

Correct

Book Data

Integration Platform/Center

Inhouse File

corrected EDI File

Administrator/Center ERP System

Identification ERP-System book Data

Receive Data

Prove

Invoicing

Yes

Valid Carrier code?

EDI File (IFTMIN)

Invoice (Paper)

Customer

picture 9picture 9

22

Document Search Screen for Employees

5.1.1 Message Tracking/ Process Monitoring

With Message Tracking message streams and processes

can be mapped. The typing of data is defined within the

BPEL Process. Message Tracking is a B2B:Portal appli-

cation. It enables the user to research within recorded

messages and data, thus gaining an insight into auto-

mated business processes and their status.

Configurable filter functions enable the rapid locating

of electronically exchanged messages such as orders,

dispatch notifications and invoices. If necessary, the

documents can be visualized and printed out for manu-

al editing intentions.

picture 10picture 10

23

5.1.2 Reporting Framework

The Reporting Framework is based on an integration

which belongs to the common »JasperReport« appli-

cation. As a source, reports can be based on any XML

data or database table. In order to create a report, the

user has multiple graphic designer tools; commercial

and free implementations available.

The XML-based created process definitions can be

registered within the portal and linked with user autho-

rizations.

The report creating run-time components, which are

integrated within the portal, are both available as a

processor component and integrated as a B2B:Portal

application. Thus, reports can be executed very flexibly

»on demand«, to a certain user interaction, or they can

be shared, event- or time-driven, and created in the

background.

Typical Application Options:

• Creation of Statistics based on Message Tracking/

Process Monitoring recorded Data.

• Creation of Accounting Reports to invoice performed

BIS 6 Services for the Customer

• Error Frequency Report within Processes, Partners,

System

• Visualizing XML Messages within the Process for,

e. g., Email Transport

• Visualizing XML Messages which are connected to

Message Tracking

• Statistics to develop Data Quality or Reaction Time for

Customers who are in the Introduction Stage within

Electronic Process Management

• Measuring EDI/B2B Degree of Utilization if there is a

EDI/B2B Target Quota mentioned within the Contract

Companies with a central EDI/B2B Management are

typically given Service Level Agreements (SLA). Accor-

ding to the business process, process times can be

set which are monitored and evaluated by the portal

(picture 11).

The IT department requires this information in regards

of data throughput, load sharing etc.

The results can be documented as a PDF, RTF, CSV or

HTML file.

picture 11

24

5.1.3 Target Monitoring

Target Monitoring serves as the automatic monito-

ring of EDI data transfers in regards to the accurate

processing of electronic business documents. That

involves either the registration of important

documents, such as important orders, which

are urgently expected on a routine basis, or

the monitoring of documents and required

subsequent documents. The monitoring of

Service Level Agreements (SLAs) is also pos-

sible with Target Monitoring.

In case the given process times can not be

upheld, an alert is sent to the defined user.

5.1.4 Task Manager

The Task Manager application shows the tasks to be

completed by the user (picture 13).

Tasks can be addressed to individual users or

to certain user groups. Within a group, the Task

Manager makes sure that a task automatically is

deleted on the groups’ task list, in case a group

member has already completed the task.

The Task Manager provides a configurable notifi-

cation and an escalation service. This service

monitors due-dates of tasks and reacts, in case

the processing was not done in time. The esca-

lation management is configurable on a multi-

level basis and offers different action options for

each level: reminder e-mail, giving back the task

to the group, allocating the task to a specific user role

etc. All interactions are recorded within the audit log.

picture 13

picture 12

25

The Task Manager provides configurable message in-

formation and escalation service. This service monitors

due-dates of tasks and immediately intervenes in

case a process is not running on-time. The escalation

management can be a multi-level configuration and

each level provides different scopes of actions such as:

email reminder, return task to group, set up task to cer-

tain hierarchy role only etc. All interactions are saved

within the Audit Log.

Thus, the Task Manager also supports companies with

the management and controlling of sub-steps for an al-

most fully automated overall process, which require the

action of a non-automated input. A typical example for

such sub-steps is the accounting- or payment-approval

for invoice documents by an authorized person.

Other applications are, for example, the selection of a

preconfigured action as a reaction on occurring errors

within process management and revision, and then the

completion of defective and incomplete data sets.

5.2 Partner Enablement

Partner Enablement provides even more portal appli-

cations for companies. This enables automated data

transfer via web-based communication channels, or a

system supported connection can be provided to se-

lected business partners as well as to business partner

groups, into the electronic data interchange.

5.2.1 Data Distribution Center

The Data Distribution Center (DDC) is an application

which provides electronic mailboxes via the internet.

Partners have the option to download important busi-

ness documents (picture 14). The DDC automatically

informs partners via email when new documents have

been provided for download. The DDC monitors the

download status and intervenes when the download

process is not taking place within the permitted time-

frame. Data downloaded by partners is automatically

transferred to BIS 6 for further processing.

picture 14

26

Applications:

• Initialization of Electronic Datasets as XML or

CSV Data for Partners who do not require an

EDI Connection.

• Initialization of PDF Documents for Partners without

integration potential.

• Exchange of CAD/CAM Data, bi-directional.

In this case, there is an extension to support the

ODETTE-ENGDAT Standards.

• Emergency System Application. In Case the EDI

Connection is interrupted (VAN or ISDN connection

failure) data is provided via Electronic Mailboxes

within the Internet.

5.2.2 EDI/B2B Roll-Out-Portal

An EDI/B2B Roll-out, the connection of multiple part-

ners within a short time, is an organizational challenge.

Therefore, the Roll-Out-Portal was developed to support

the connection of business partners for user-compa-

nies. Routine jobs within the partner connection, such

as guidelines delivery, the gathering of partner com-

munication parameters, as well as communication and

conversion tests, are process-controlled by the portal. A

detailed connection status monitoring comprehensive

partner and process statistics exemplifies the Roll-out

success.

EDI/B2B Roll-Out Modules

System-Controlled

Partner Connection/

Test Center

Roll-out

picture 15picture 15

• Web Applications

• Individual Master Data Entry by Partner

• Automatic Tests of Sending/Receiving Processes

• Management of Certificates and Automated

Information before Expiration Date

• Individual Checking of Messages towards

provided Guidelines

• Support of multiple EDI Standards

(EDIFACT, ODETTE, ANSI, VDA)

• Monitoring with Task Manager

• Email Communication

CommunicationMaster Data Test Center

OFTP classic, OFTP V2

AS2

Compliance Test Center

INVOICE

DESADV

Telebox

27

6.1 Architecture

From a technical perspective, BIS 6 is a JavaEE-based

application, which implements a B2B/EDI Gateway.

The core engine is a BPEL standard-based Workflow

Machine which enables choreography of all available

services to processes.

BIS 6 is developed as a distributable system, to flexibly

manage the biggest data loads with the distribution on

several workstations.

The administration is effected by a central Front-End,

which is self-installed by Java Web Start at the custo-

mers’ computer and which permanently updates itself.

The system software uses Failover Cluster methods

in order to protect the BIS 6 central instance against

breakdowns, while it also provides internal mechanis-

ms to manage nodes on which individual services are

implemented.

BIS 6 is available for all platforms which provide an

adequate 64-bit Java Runtime Environment (JRE), such

as: Windows (with SUN JRE), Linux (with SUN or IBM

JRE), AIX, Solaris and HP-UX. Therefore, through the

support of the 64-bit technology, highly developed

storage systems can ideally be used, which is shown

according to the optimal performance.

Please consult the release notes for the actual ope-

rating system versions and system requirements of a

specific version.

Services running inside the BIS 6 architecture interact

with each other via JMS or RMI. All user interactions,

such as the connection between GUI client and server,

are based on HTTP/S.

BIS 6 System Architecture

J2EE Application Server

SEEBURGER Business Integration Server

Process MonitoringConfiguration Services

Human Interaction andPortal Services

BP Development and Deployment Services

Process Management ServicesTransformation

Service

Transport Service

Component Service

Adapter Service

JRE 1.5

OS (Windows, UNIX)

Serverhardware Unit

JRE 1.5

OS (Windows, UNIX)

Serverhardware Unit

Scalability

Availability

picture 16picture 16

6. System Architecture and technical Implementation

28

BIS 6 requires a system database. Databases sup-

ported include, Oracle and MS SQL Server, and with

some restrictions, MAxDB. As an J2EE Application, the

SEEBURGER BIS, will be shipped with a pre-configured

JBOSS Application.

6.2 Installation Scenarios

Depending on customers’ needs BIS 6 scenarios can be

customized.

Examples:

Fully centralized Installation

The whole system is implemented on a machine, in-

cluding all components and the system database. This

scenario is typical for a single server, which does not

require particular safety requirements, but only a minor

load, thus providing a quick solution installation. The

installation is fully supported by a CD-setup.

Centralized Installation with distributed Service

Components (Nodes)

Unlike the first scenario, here, certain services are

outsourced to dedicated servers. Thus, the load is

distributed on multiple systems and therefore higher

performance is reached. The installation is supported

by a so-called Node-Setup which is based on a central

Software-Repository. It is guaranteed that on all nodes

the same or a compatible software status is installed.

This scenario is also typical, in case high security re-

quirements exist, e. g., by the use of internet commu-

nication components, such as EDIINT AS2, RosettaNet

or OFTP V2. Here, communication components are

installed separately within the firewall »DMZ«.

29

picture 17

Centralized Installation with separated Database

Since the system database plays an important role

within the BIS 6 system, it is often recommended, to

distribute the central instance for higher performance.

The database is installed on a dedicated server or,

for instance, on a passive connection to the Failover

Clusters from BIS 6. In the event connectivity fails,

the remaining connections take over the application

load. Thus, higher system stability is reached and,

simultaneously, an ideal use of the system provides

more availability for additional resource use within the

normal system.

The scenario of a separated system database also takes

place, in the event an existing company-wide database

server, such as the Oracle RAC Server, is implemented

for the BIS 6 database.

Completely decentralized Installation

The core engine, GUI Server, all component services,

database etc., are each connected through networks

and installed on a dedicated system (picture 17). This

procedure is in terms of implementation and mainte-

nance the most complex and therefore only used for

extraordinary applications. It provides the advantage

that every component can be deployed and ideally

configured for its system environment (Hardware, JVM,

Security Zone, Cluster Process etc.).

In terms of the individual, application-customized hard-

ware specifications, SEEBURGER provides guidelines

within the system documentation.

Minimal System Requirements and Range:

INTEL DualCore CPU 3 GHz, 4 GB RAM, 250 GB HDD with

7.200 U/min, Monitor 1240x1024, Windows 2003 Ser-

ver, MS SQL Server 2005 Express Edition or SUSE and

rather RedHat Linux , MAXDB 7.6 or Oracle 10g Database

and SUN JRE 1.5.

30

6.3 Internal Architecture – Function Modules

Core functions of BIS 6 are the receiving, the conversion

and the forwarding of messages. Other optional func-

tions comprise of archiving, security, etc. The design

is focused on the most important challenges, such as,

interoperability, scalability and flexibility of each appli-

cation, which enables the distribution of these applica-

tions over multiple heterogeneous platforms.

Main Layers

Essentially, BIS 6 consists of three layers: persistence,

communication (internal), as well as application and

service layer (picture 18).

Persistence Layer

The persistence layer has the function to save data

structures inbetween the processes. Within BIS 6, user

and meta data is saved from ongoing processes into

the non-volatile storage such as a file system WebDav

or a relational database (e. g. Oracle) via an abstraction

framework (SeeDIAF).

Communication Layer: RMI and JMS

This layer exchanges data between applications and

services and makes the communication platform for all

process types. The process can be completed within a

separated environment through Remote Method Invo-

cation (RMI), in order to enhance the scalability. Within

the central Workflow Engine, for pending messages,

data is exchanged by JMS.

Architectural Layer with Function Modules

SeeDIAF

Persistence Layer

DBMS

RMI, JMS

Communication Layer

Application and Service Layer

Workflow Engine

Adapter Engine(in)

AS2 HTTP HF

Correlator Engine

BIC.Proc.

StoreService TPM ...

Invoker Service

FTP MailBIC

Node...

StoreNode

Adapter Engine(out)

Allocation

DirectWLH

picture 18 picture 18 * from Version 6.4.x

IDOC...

Initiator (Rule Engine)

Allocation *

31

Application Layer and Service Layer

This layer consists of internal and external interfaces

as well as services for standard and special functions.

In order to receive and to forward messages, different

Engines take action, such as: Adapter Engine, Workflow

Engine, and Rule Engine.

The Workflow Engine can be retrieved through customi-

zed configuration on different layers (Design, Configu-

ration and Process Layer).

• Messages are received via the Adapter Engine (e. g.

AS2, HTTP, Hotfolder, IDOC und FTP) and forwarded to

the Initiator. The Initiator owns the task of setting pro-

cess instances. The Rules Engine decides which BPEL

process script needs to be deployed and sets up the

stored initial configuration within the applied rule.

The rules are being maintained within BIS 6 Front-

End. The process script is interpreted by the Workflow

Engine which administers appropriate actions, such

as: BIC Processor, Memory Service.

• The message can then be processed through a Corre-

lator Engine. For example, the BPEL process interpre-

ts the conversion as a BIC processor, a memory ser-

vice for archiving and Trading Partner Management

(TPM) for validation and auto- forwarding.

• In order to distribute the system load simultaneously,

the message within a process can also be dispatched

with Message Queue. The forwarding is either opera-

ted by:

– Work List Handler (WLH), which manages tasks in

separated environments, such as: conversion on a

BIC adapter, data archiving on a memory adapter

and resources reservation (e. g. ISDN forwarding)

– Direct Process: supports asynchronous activities

of the same services for high performance re-

quirements (supported though publish/subscribe

model).

BIS 6 is designed so that different hardware and soft-

ware solutions can be supported within a separated

environment. The system is very flexible in terms of

on-demand arrangements of services and activities.

Also, it is scalable, to enable individual configurations

within the system configuration to manage and balance

system load.

32

BIS 6

6.4 Function Modules

BIS 6 is available in different levels (picture 19) and

function modules (picture 20) can be purchased based

on individual needs.

This provides an Integration Solution for SEEBURGER

customers, which is customized to a company’s needs.

The following list gives a general insight to the

current availability of BIS 6 modules. These lists are

continuously updated.

System Overview

Runtime Standard Enterprise Enterprise Service Bus

248N

•–––

•xxx

••xx

•••x

Test/QA/Development System x x x •

Move-to-Production – x • •

Cold Standby System x x x –

Fail Over Cluster – • • •

Priority Control – x • •

Logical Systems – x • •

System DB Oracle – x • •

Developer Studio – x • •

Process Designer Plug-in – x x •

Mapping Designer Plug-in – x x •

x optional • inclusive – not possible

picture 19

Cores

33

Function Modules

Communication

International VANs

GE, IBM, AT&T, TDE, SedeB2B, AZERTIA,

ALLEGRO, INTESA, EBMX, EXITE, MCI EDI*NET,

FORD SOLMIS, Sterling CommerceNet,

Covisint, ATLAS/400, Carrefour, KPN SWISS,

Telebox/400 etc.

Point to Point Connections

OFTP, X.25, TCP/IP, ISDN, PMX, GALIA, JIT,

OFTP V2 etc.

Internet-based Communication

TECCOM, papiNet, FTP, HTTP(S), HPSB, ebMS -

ebXML, RosettaNet, EDIINT AS1-3, SMTP/

POP3/IMAP, scp/sftp, Web-Services,

BIS 6:SpokeUnit etc.

Internal Communication

JMS, VCOM etc.

Converter

INHOUSE, EDIFACT, XML, SQL Datenbank, CSV,

TRADACOM, ANSI X.12, SWIFT, AECMA, CII

Syntax (EIAJ, HSWB) etc.

Connectors

SAP, BAAN, Oracle applications, Host, AS/400,

RDX, CommerceOne, ARIBA, Archive etc.

Security

S/MIME, OpenPGP, COM-SECURE, EDIFACT

Signature, XMLDSIG etc.

picture 20

34

6.5 Release-Strategy

Since the appearance of electronic data interchange

SEEBURGER has consistently developed solutions to

meet market needs. Solutions range from classic EDI

management, to the B2B and EAI scenario extension

with XML Web Support, to the current market approach

BPM and SOA.

The current BIS 6 product uses tried and true techno-

logy from previous applications. SEEBURGER started

over 20 years ago with »SUBELKE« and the »Electronic

Communication Unit« and has evolved overtime with

WinELKE NT and BIS 5.

SEEBURGER’s development process for BIS 6 is based

on the Rational Unified Process (RUP). This develop-

ment process manages the complete product life cycle

from the requirement analysis, including the classic

project development phases (specification, implemen-

tation, test), to the roll-out at the customer site.

As a general rule the BIS 6 Release Plan is designed

to release 1-2 releases per year. The latest is Release

6.3.2Q2. Every 2-3 months new service releases are

presented, which contain error corrections and small

model specific options.

The release planning takes place on a short term with

maximum 6-8 months in advance. Within these rela-

tively short release periods is a guarantee that modified

requirements, new standards etc. are to be updated as

quickly as possible.

In case an error occurs or a new critical requirement is

determined, SEEBURGER provides a Hotfix-Process to

the customer.

The management of these processes and the monito-

ring of compliance is operated by SEEBURGER’s quality

management department, which directly reports to the

board of directors.

35

Professional Services

SEEBURGER provides both product and services to its

customers. These services range from the requirement

analysis, solution design and to the support of instal-

lation, configuration and testing of the products in the

customer environment.

Professional Services most likely occur in bigger pro-

jects which require an individual planning process.

Within technical workshops the basic conditions and

objectives from the customer are gathered, then, the

technical feasibility is checked leading to the solution

concept.

SEEBURGER provides leading industry expertise within

the management of automated business processes.

Managed Services

SEEBURGER offers comprehensive Managed Services.

Those range from single automated managed proces-

ses, the general available B2B platform to individual

outsourcing projects with a dedicated server within the

SEEBURGER data center. In case companies decide to

integrate outsourced integration applications back into

their company and develop an internal B2B platform,

already deployed processes and mappings can be di-

rectly implemented. The complete SEEBURGER product

portfolio is available as a Managed Service.

Support

SEEBURGER provides customized support for custo-

mers. Software maintenance is provided, which provi-

des new software versions for licensed products. Addi-

tionally, support contracts include a “Hotline Service”.

There, the individual contract levels differ in terms of

availability and reaction time. Support offerings can

include global support, 24 hours a day, 7 days a week,

365 days per year provided in the German and English

language.

SEEBBURGER Academy

The SEEBURGER Academy provides workshops and trai-

nings around the SEEBURGER product portfolio. Also in-

cluded are market relevant topics such as archiving and

digital signature. The training takes place with certified

trainers in small groups at the SEEBURGER Academy

or can be organized on-site of a customer. In case an

international training is needed, the trainings can also

be presented in English or in the local language.

7. Product Services

36

Marks Information

© Copyright 2009 SEEBURGER AG. All rights reserved.

The information in this document is proprietary to

SEEBURGER. Neither any part of this document, nor the

whole of it may be reproduced, copied, or transmitted

in any form or purpose without the express prior written

permission of SEEBURGER AG. Please note that this

document is subject to change and may be changed by

SEEBURGER at any time without notice. SEEBURGER‘s

Software product, the ones of its business partners may

contain software components from third parties.

SAP®, SAP® R/3®, SAP NetWeaver®, SAP® NetWea-

ver, ByDesign®, SAP BusinessByDesign®, ABAP™ are

registered trade marks of the SAP AG or the SAP AG

Deutschland (Germany), as well as Microsoft®, Win-

dows®, Outlook®, NT®, Word®, EXCEL® and Power-

Point® are the ones of the Microsoft Corporation.

Linux is the registered trademark of Linus Torvalds in

the U.S. and other countries. UNIX and X/Open are re-

gistered trademarks of the Open Group.

Adobe, the Adobe Logo, Acrobat, PostScript and Reader

are trademarks or registered trademarks of Adobe Sys-

tems Inc., in the U.S. and/or other countries.

JavaScribt is a registered Mark of Sun Microsystems,

Inc., used under license for technology invented and

implemented by Netscape.

Oracle is a registered trademark of Oracle Corporation.

HTML, XML, XHTML and W3C are trademarks or registe-

red trademarks of W3C®, World Wide Web Consortium,

Massachusetts Institute of Technology. Java is a regis-

tered trademark of Sun Microsystems, Inc. JBOSS is a

registered Mark of the JBOSS Inc.

4avis®, 4classification®, 4everything®, 4invoice®,

4invoice WEBflow®, 4order®, BIS:explore®, BIS:

open®, BIS:open UX®, BIS:pdx®, BIS:plm®,

FAX2XML®, Free Form Interpreter Kontierung Dialog

Workflow®, FreeFormation®, FreiForm®, iMartO-

ne®, Paper2ERP®, Paper-to-ERP®, SEEBURGER®,

SEEBURGER Business-Integration Server®, SEEBURGER

DocumentSuite®, SEEBURGER Logistic Solution Profes-

sional®, SEEBURGER Web Supplier Hub®, SEEBURGER

Workflow®, SEEBURGER-CASEngine®, SEEBURGER-

invoiceCONSOLE®, SEEBURGER-WEBflow®, Smart-

RetailConnector®, TRAVELinvoice®, WebVERA®,

WinELKE® and other products or services of

SEEBURGER which appear in this document as well as

the according logos are marks or registered marks of

the SEEBURGER AG in Germany and of other countries

worldwide.

All other products and services names are marks of

the mentioned companies. All contents of the present

document are noncommittal and have a mere informa-

tion intention. Products and services may be country-

specific designed.

All other mentioned company and software designati-

ons are trademarks or unregistered trademarks of the

respective organisations and are liable to the corres-

ponding legal regulations.

37

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

• This document is a preliminary version and not

subject to your license agreement or any other

agreement with SEEBURGER. This document

contains only intended strategies, developments,

and functionalities of the SEEBURGER product and

is not intended to be binding upon SEEBURGER to

any particular course of business, product strategy,

and/or development. Please note that this

document is subject to change and may be changed

by SEEBURGER at any time without notice.

• SEEBURGER assumes no responsibility for errors or

omissions in this document. SEEBURGER does not

warrant the accuracy or completeness of the infor-

mation, text, graphics, links, or other items contai-

ned within this material. This document is

provided without a warranty of any kind, either

express or implied, including but not limited to the

implied warranties of merchantability, fitness for

a particular purpose, or non-infringement.

• SEEBURGER shall have no liability for damages of

any kind including without limitation direct, special,

indirect, or consequential damages that may result

from the use of these materials. This limitation shall

not apply in cases of intent or gross negligence.

• The statutory liability for personal injury and defective

products is not affected. SEEBURGER has no control

over the information that you may access through

the use of hot links contained in these materials and

does not endorse your use of third-party web pages

nor provide any warranty whatsoever relating to

third-party web pages.

Imprint: SEEBURGER AG · Edisonstraße 1 D-75015 Bretten (near Karlsruhe) · info@seeburger.com ·www.seeburger.comSEEBURGER BIS 6 Release engl. – Version 3.4 – 01/10 © Copyright SEEBURGER AG 2009All product names mentioned are the property of the respective company. © SEEBURGER AG

Germany

HeadquartersSEEBURGER AGEdisonstraße 1D-75015 Bretten (near Karlsruhe) Phone + 49 (0) 72 52.96-0Fax + 49 (0) 72 52.96-2222info@seeburger.dewww.seeburger.de

HamburgSpaldingstr. 77aD-20097 HamburgPhone + 49 (0) 40.2388240info@seeburger.dewww.seeburger.de

KöthenKonrad-Adenauer-Allee 13D-06366 KöthenPhone + 49 (0) 34 96.50 81-0info@seeburger.de

International

USASEEBURGER, Inc.1230 Peachtree Street NESuite 1020Atlanta, GA 30309, USAPhone + 1 770 604 3888 Fax + 1 770 604 3885info@seeburger.comwww.seeburger.com

Asia PacificSEEBURGER Asia Pacific Ltd.Level 3, Three Pacific Place1 Queen’s Road EastHong KongPhone + 852 2584 6220Fax + 852 2588 3499infoasiapac@seeburger.com

ChinaCHINA HQSEEBURGER China Inc.Suite 523-526, 5/F Cimic Tower 800 Shangcheng Rd.200120 Shanghai, P.R. ChinaPhone + 86 (0) 21 5835 7779Fax + 86 (0) 21 3887 0999 infochina@seeburger.comwww.seeburger.cn

SEEBURGER China Inc.CBD International MansionC529, 5/FNo.16 Yongan DongliChaoyang, Beijing, 100022Phone + 86 (0) 10 6563 7565Fax + 86 (0) 10 6563 7562infoasiapac@seeburger.com

JapanSEEBURGER KKNishi-Gotanda Sign Tower 5th Floor1-33-10 Nishi-GotandaShinagawa-ku, Tokyo 141-0031Phone + 81-(0)3-6303-9120Fax + 81-(0)3-6303-9124infoasiapac@seeburger.com

AustriaSEEBURGER Informatik GmbHSchlachthausgasse 29/Top B02A-1030 WienPhone + 43 (0) 1 212 2859-0Fax + 43 (0) 1 212 2859-111info@seeburger.atwww.seeburger.at

BeneluxSEEBURGER Benelux B.V.Het Poortgebouw – Beech Avenue 54-60Schiphol-RijkNL-1119 PW, the NetherlandsPhone + 31 (0) 20 658 6137Fax + 31 (0) 20 658 6111infoNL@seeburger.comwww.seeburger.nl

SEEBURGER BelgiumRegus Brussels AirportPegasuslaan 5B-1831 DiegemPhone + 32 (0) 2/709 29 28Fax + 32 (0) 2/709 22 22infoBE@seeburger.comwww.seeburger.be

BulgariaSEEBURGER Informatik EOODGrigorij Gorbatenko Strasse 6k-s Mlados IBG-1784 SofiaPhone + 359 29745-100info@seeburger.comwww.bg.seeburger.com

Czech RepublicPhone + 43 (0) 1 212 2859-200info_cz@seeburger.comwww.seeburger.cz

Eastern Europe &South Eastern Europe(except Hungaria, Czech Republic,Bulgaria & Turkey)Phone + 49 (0) 7252.96-1172se-europe@seeburger.comwww.seeburger.com

FranceSEEBURGER France S.A.R.L.87, rue du Gouverneur Général EbouéF-92130 Issy Les Moulineaux (Paris)Phone + 33 (0) 1 41 90 67 50Fax + 33 (0) 1 41 90 67 59info@seeburger.frwww.seeburger.fr

Great Britain/IrelandSEEBURGER UK Ltd.Heathrow Boulevard 4280 Bath RoadWest DraytonMiddlesexUB7 0DQPhone + 44 (0) 20 8564 3900Fax + 44 (0) 20 8897 8295info@seeburger.co.ukwww.seeburger.co.uk

ItalySEEBURGER Informatica SRL UnipersonaleVia Frua, 14I-20146 MilanoPhone + 39 02 45 48 53 68Fax + 39 02 43 51 01 10info@it.seeburger.comwww.seeburger.it

Spain/PortugalSEEBURGER Informática S.L.Pso. Infanta Isabel, 27-1 Izq.E-28014 MadridPhone + 34 91 433 69 89Fax + 34 91 434 12 28 info@es.seeburger.comwww.seeburger.es

Sweden/ScandinaviaSEEBURGER Svenska ABNora Torg 5 S-18236 DanderydPhone + 46 (0) 8 544 99 140Fax + 46 (0) 8 544 99 149info@seeburger.sewww.seeburger.se

SEEBURGER Svenska ABHisingsgatan 30S-417 03 GöteborgPhone + 46 (0) 31 339 15 25Fax + 46 (0) 31 339 15 26info@seeburger.se

SwitzerlandSEEBURGER Informatik AGMarktstrasse 13CH-8853 LachenPhone + 41 (0) 55 451 06 90Fax + 41 (0) 55 451 06 91info@seeburger.chwww.seeburger.ch

TurkeyPhone + 49 (0) 72 52.96-1592info@seeburger.com.trwww.seeburger.com.tr

Middle East & AfricaPhone: + 49 (0) 72 52.96-1172mea@seeburger.comwww.seeburger.com