Embed
Email

B2B ENGLISH

Document Sample

Shared by: Nathan Jameson
Categories
Tags
Stats
views:
147
posted:
8/19/2008
language:
English
pages:
29
B2B by Practice

Dr. Stefan Klose

stefan.klose@web-federation.de



Netweaver, ESA, SAP, R/3, ABAP/4 und mySAP.com sind eingetragene Marken der SAP AG, Walldorf. Alle Rechte vorbehalten. Java, EJB, Sun-One and J2EE sind eingetragene Marken von Sun Microsystems, Inc. Alle Rechte vorbehalten.



http://www.b2bbypractice.org/



Background



 B2B by Practice is driven by developers from ISVs who designed and developed this Open Source Data Exchange Solution

• the experience of more than 50 intercompany data exchange projects influenced the design of B2B by Practice • The business model is based upon the GPL (gnu public licence)

no licence fees professional Services (Software Support and Content) with costs various companies contribute to the solution and offer professional services customers can influence the solution the solution will be improved and maintained on long term



• Status: productive at many customers in germany



2



B2B by Practice: Tenant concept versus Multi-Deployment



the B2B by Practice tenant concept allows data seperation according to legal needs



as an alternative B2B by Practice can be deployed multiple times to achieve data seperation



B2B by Practice



Mail,Files,WebService,..



B2B by Practice



B2B by Practice



B2B by Practice



B2B by Practice

3



Mail,Files,WebService,..



Supported Platforms







J2EE 1.4 & EE 5.0 compatible application server

• • • e.g. SAP J2EE Engine (incl SAP PI), WebSphere,.. Tomcat / JBOSS ….







Datenbases

• • Productive usage: Oracle, MAXDB, DB2, MSSQLServer Test usage: Derby, MySQL







Operation Systems

• no restrictions



Netweaver, ESA, SAP, R/3, ABAP/4 und mySAP.com sind eingetragene Marken der SAP AG, Walldorf. Alle Rechte vorbehalten.Java, EJB, Sun-One and J2EE sind eingetragene Marken von Sun Microsystems, Inc. Alle Rechte vorbehalten.

4



Architecture

 leightweight Architecture

• • • platform independent / scalable seperation between Software and Content (Mapping) developement Model Driven Architecture



 



Persistence and Data Archiving conforms with legal needs P2P Conections instead of open Hub due to legal regulation rules

• E.g: Seperation of data and monitoring due to market roles (GRID, Supplier,..)

- variant 1 : tenant concept - variant 2: multi-deployment (physical seperation)



 



Solution offers roles for Administrators, Support and Data Clearing specialists

• Monitoring views are highly configurable



modifcation free enhancements are possible

• • Custom Mapping Content Custom Coding Content



5



Community: http://www.b2bbypractice.org/



6



Functional Scope Version 1.4.2







Typical project length to migrate an existing solution to B2B by Practice

• • • 1:1 Migration ~ 5-10 days



Content

The first content practices provides mappings conforming to the german electricity and gas regulations all legal requirements are taken into account



   



configurable format recognition (EDI und XML) Channel distributions rules allow flexible determation of Workflow channels

• • repository of preconfigured extentions (e.g. Mapping Tables)



Workflowdefinitions are handled in Channels

with oder without manual interaction or email notifications



Broad repository of Workflow-Steps („Actions“) including many specialities

• • • e.g: message split due to postal codes e.g.:one to one communication e.g:Content for internal system unbundling



7



Functional Scope Version 1.4.2

                Services connect physical systems

• File, Mail, SAP, HTTP,..



Customizing transport tool automatic generation of Documentation based on the actual customizing seperation of standard and customer objects (content and coding) full text search Data specific search based on positions Standalone EDI Analyzer Forms designer Reports and Excel Download Support of Data Clearung and manual processes Forwarding to Mail or Ticketing systems cooperation with cryptographic / signature solutions Archiving incl. SAP integration SAP Status Synchronisation Template & Rule Engine Command Event Parser for fast XML Processing



8



Functional Scope Version 1.4.2

    internationalization User/Role/Authorization concept Tenant concept Adminstration- und Customizing Functions

• • • • • • • Queueing Systemerrros Lockhandling Content(Mapping) Administration Customizing Long Running Transaction Monitor Cluster-Administration

Correlation-handling (e.g. CONTRL, APERAK) View customizing configurable Logging and Tracing Mime Viewer Birt-connection for Reporting







Clearing and IT-Monitoring

• • • • •







Developement support

• • APIs for customer developement Developer Workplace



9



Functional Scope Version 1.4.2 V2.0 ( Q4 2008)



       



grafical Mapping Editor High Performance Converter

• Increase of Performance (~factor 100)



Extended reporting Support functions further adapter (services) e.g. AS2, FTP,.. Further functions based on customer feedback Ready To Run Linux VM-Ware released for productive usage

• at no licence fees



Further features based on community process

• Users Group meeting in Cologne planned



10



Professional Services Offerings

Phase 1 (free):  WebEX to explain solution  Visit reference customers  contact b3p@web-federation.de

Phase 2:  Assessments  Pilot Phase 3:  Implementation project  Training Phase 4:  Content- and DevelopmentSupport (maintenance contract)



11



Screenshots - Statistics



Since August 7th this customer processes more than 20.000 Messages a day (Hardware usage is only 5%) a 75MB Message is processed in 15min

12



SAP Status visible in Monitoring



SAP IDOC Nr



13



CONTRL und APERAK Correlation



14



Cluster usage can be customized very flexible based on Message Size an priority



15



Mass-Processing : Long running transaction monitoring for very big messages



16



Full text search



17



Search and Correlation of incoming and outgoing data



18



Authorization Concept: for Functionality and Systems (Data)



19



Customizing: Content



Maintenance of user, roles and authorizations



20



Format recognition – Command Event Parser



21



maintenance of Workflowdefinitions



22



maintenance of Workflow Steps



23



maintenance of Services



24



Errorviewer / Logviewer



25



Lock Tables



26



Customizing Download and generated documentation



27



More funtions: manual forwarding, Forms-designer, EDI Validation,..



28



Contact



Dr. Stefan Klose stefan.klose@web-federation.de http://www.b2bbypractice.org



29




Related docs
Other docs by Nathan Jameson
Briefing notes from February 2008 IAEA meeting
Views: 48  |  Downloads: 1
Utility Svs Coord Job Description Sample
Views: 14  |  Downloads: 0
Real Estate Free Report Distressed Property
Views: 87  |  Downloads: 2
mak
Views: 243  |  Downloads: 0
IRS Forms and Publications f1040sse
Views: 200  |  Downloads: 1
Picking the Right Gardening Tools free report
Views: 28  |  Downloads: 0
Morrissey
Views: 6  |  Downloads: 0
wthr picks Teacher WorkSheet
Views: 127  |  Downloads: 1
NPC Body Building free report 2008
Views: 74  |  Downloads: 1
By registering with docstoc.com you agree to our
privacy policy

You are almost ready to download!

You are almost ready to download!