Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
SAP PI brings the final divorce between ABAP and JavaPaul van Os, Oxolution 2010   SAP PI brings the final divorce between...
2•   Federated PI•   AEX•   Java only instances•   Performance boosts•   JVM improvements•   Configuration assistant•   XI...
2• Federated PI          SAP PI brings the final divorce between                 ABAP and Java Oxolution
Federated PI landscape• Central• Distributed• Federated                SAP PI brings the final divorce between            ...
2• AEX        SAP PI brings the final divorce between               ABAP and Java Oxolution
Single Stack capabilities via AAEAdvanced Adapter Engine Extended           SAP PI brings the final divorce between       ...
AEX 1• Single Stack    – reduced TCO Fast installation Less hardware fast      restart•   Speed up to 10 times faster•   1...
AEX 2•   Integrated scenario from PIS•   XML validation redesign (ESR schema based)•   Large binary to binary file transfe...
2• PI 7.3 Java only           SAP PI brings the final divorce between                  ABAP and Java Oxolution
PI 7.3 Value proposition      SAP PI brings the final divorce between             ABAP and Java Oxolution
ES Repository 7.3 (CE7.3 and PI7.3)            SAP PI brings the final divorce between                   ABAP and Java Oxo...
Service busSAP NetWeaver PI 7.3    SAP PI brings the final divorce between           ABAP and Java Oxolution
2• Performance boosts         SAP PI brings the final divorce between                ABAP and Java Oxolution
Performance 1• Message blacklisting  – Identifies possible disruptive messages     • Flag them as suspicious upon server r...
2• JVM improvements        SAP PI brings the final divorce between               ABAP and Java Oxolution
JVM improvements 1• Advanced garbage collection and improved  JVM instability detection:               SAP PI brings the f...
JVM improvements 2• Process unlimited file sizes• Deliver constant response times for sync mess.• Avoid inconsistent messa...
2• Simplified configuration          SAP PI brings the final divorce between                 ABAP and Java Oxolution
Simplified Configuration 1       SAP PI brings the final divorce between              ABAP and Java Oxolution
Simplified Configuration 2       SAP PI brings the final divorce between              ABAP and Java Oxolution
2• CPA cache         SAP PI brings the final divorce between                ABAP and Java Oxolution
Reworked CPA• Reworked cache refresh leads to:  – More robust and faster processing• Optimized object loading during full ...
2• XI 3.1 protocol          SAP PI brings the final divorce between                 ABAP and Java Oxolution
XI 3.1 protocol• For communication between PI components  – Integration Server <-> Adapter Engine  – Integration Server <-...
2• Queue handling         SAP PI brings the final divorce between                ABAP and Java Oxolution
Error’s and Queue’s• EO messages assigned to a queue block when  in error  – Now, error message is moved to another queue ...
2• Adapter specific news          SAP PI brings the final divorce between                 ABAP and Java Oxolution
Adapter• PI 7.3 allows to control the resources usage  per adapter channel  – Some adapter allow control for maximum paral...
Things to ponder• PI 7.3 java only does not mention what to do  with BPM… and they are o so present!!!• Integration with C...
Questions ?SAP PI brings the final divorce between       ABAP and Java Oxolution
Upcoming SlideShare
Loading in …5
×

#sitNL presentation sap teched berlin v3

1,327 views

Published on

SAP PI brings the final divorce between ABAP and Java

by Paul van Os (Oxolution)

Published in: Technology
  • Be the first to comment

  • Be the first to like this

#sitNL presentation sap teched berlin v3

  1. 1. SAP PI brings the final divorce between ABAP and JavaPaul van Os, Oxolution 2010 SAP PI brings the final divorce between ABAP and Java Oxolution
  2. 2. 2• Federated PI• AEX• Java only instances• Performance boosts• JVM improvements• Configuration assistant• XI 3.1 protocol• Queue handling• Things to ponder… SAP PI brings the final divorce between ABAP and Java Oxolution
  3. 3. 2• Federated PI SAP PI brings the final divorce between ABAP and Java Oxolution
  4. 4. Federated PI landscape• Central• Distributed• Federated SAP PI brings the final divorce between ABAP and Java Oxolution
  5. 5. 2• AEX SAP PI brings the final divorce between ABAP and Java Oxolution
  6. 6. Single Stack capabilities via AAEAdvanced Adapter Engine Extended SAP PI brings the final divorce between ABAP and Java Oxolution
  7. 7. AEX 1• Single Stack – reduced TCO Fast installation Less hardware fast restart• Speed up to 10 times faster• 1 monitoring• Support for HTTP and IDOC• Interface and mapping split• User defined message search• Enhanced integration with SM SAP PI brings the final divorce between ABAP and Java Oxolution
  8. 8. AEX 2• Integrated scenario from PIS• XML validation redesign (ESR schema based)• Large binary to binary file transfer• Time-out config per comm channel• Pub and sub for JMS Topics• Stand alone or in combination with PI• Using AEX as manual fail over system• Eclipse based tools SAP PI brings the final divorce between ABAP and Java Oxolution
  9. 9. 2• PI 7.3 Java only SAP PI brings the final divorce between ABAP and Java Oxolution
  10. 10. PI 7.3 Value proposition SAP PI brings the final divorce between ABAP and Java Oxolution
  11. 11. ES Repository 7.3 (CE7.3 and PI7.3) SAP PI brings the final divorce between ABAP and Java Oxolution
  12. 12. Service busSAP NetWeaver PI 7.3 SAP PI brings the final divorce between ABAP and Java Oxolution
  13. 13. 2• Performance boosts SAP PI brings the final divorce between ABAP and Java Oxolution
  14. 14. Performance 1• Message blacklisting – Identifies possible disruptive messages • Flag them as suspicious upon server restart • Cancel upon second restart – Avoid multiple server restarts – Status DLNG will be blacklisted and all messages which is already listed will be NDLV – Search in monitoring – Restart by administrator SAP PI brings the final divorce between ABAP and Java Oxolution
  15. 15. 2• JVM improvements SAP PI brings the final divorce between ABAP and Java Oxolution
  16. 16. JVM improvements 1• Advanced garbage collection and improved JVM instability detection: SAP PI brings the final divorce between ABAP and Java Oxolution
  17. 17. JVM improvements 2• Process unlimited file sizes• Deliver constant response times for sync mess.• Avoid inconsistent messaging status or restarts due to unhandled JVM exceptions• 16 GB JVM nodes (big files)• Background GB runs constantly for good response and stability SAP PI brings the final divorce between ABAP and Java Oxolution
  18. 18. 2• Simplified configuration SAP PI brings the final divorce between ABAP and Java Oxolution
  19. 19. Simplified Configuration 1 SAP PI brings the final divorce between ABAP and Java Oxolution
  20. 20. Simplified Configuration 2 SAP PI brings the final divorce between ABAP and Java Oxolution
  21. 21. 2• CPA cache SAP PI brings the final divorce between ABAP and Java Oxolution
  22. 22. Reworked CPA• Reworked cache refresh leads to: – More robust and faster processing• Optimized object loading during full cache refresh using temporary files, cache queries in memory• Changed CPA cache refresh update on adapter engine leads to less memory consumption and less communication over server nodes• Speeds up pipeline processing, less read!! SAP PI brings the final divorce between ABAP and Java Oxolution
  23. 23. 2• XI 3.1 protocol SAP PI brings the final divorce between ABAP and Java Oxolution
  24. 24. XI 3.1 protocol• For communication between PI components – Integration Server <-> Adapter Engine – Integration Server <-> Integration Server• Leads to performance improvements, especially on Adapter Engine• Easier and faster EO message processing between PI components• Works out of the box SAP PI brings the final divorce between ABAP and Java Oxolution
  25. 25. 2• Queue handling SAP PI brings the final divorce between ABAP and Java Oxolution
  26. 26. Error’s and Queue’s• EO messages assigned to a queue block when in error – Now, error message is moved to another queue – Relieves administrator monitoring queues – Prevent inconsistent qRFC status for unhandeld exceptions – Long awaited functionality – Rebalancing queue’s SAP PI brings the final divorce between ABAP and Java Oxolution
  27. 27. 2• Adapter specific news SAP PI brings the final divorce between ABAP and Java Oxolution
  28. 28. Adapter• PI 7.3 allows to control the resources usage per adapter channel – Some adapter allow control for maximum parallel connections • No channel can clog up the adapter • Business critical interfaces always get resources SAP PI brings the final divorce between ABAP and Java Oxolution
  29. 29. Things to ponder• PI 7.3 java only does not mention what to do with BPM… and they are o so present!!!• Integration with CE? What’s the future for PI?• SAML…. IM helps a little bit, but then again…• Java only monitoring under construction… even michal krawczyk had some issues during Teched hand on experience• Performance of PI really is better! SAP PI brings the final divorce between ABAP and Java Oxolution
  30. 30. Questions ?SAP PI brings the final divorce between ABAP and Java Oxolution

×