#sitNL presentation sap teched berlin v3

30
SAP PI brings the final divorce between ABAP and Java Paul van Os, Oxolution 2010 SAP PI brings the final divorce between ABAP and Java Oxolution

description

SAP PI brings the final divorce between ABAP and Java by Paul van Os (Oxolution)

Transcript of #sitNL presentation sap teched berlin v3

Page 1: #sitNL presentation sap teched berlin v3

SAP PI brings the final divorce between ABAP and Java

Paul van Os, Oxolution 2010 SAP PI brings the final divorce between

ABAP and Java Oxolution

Page 2: #sitNL presentation sap teched berlin v3

2

• Federated PI

• AEX

• Java only instances

• Performance boosts

• JVM improvements• JVM improvements

• Configuration assistant

• XI 3.1 protocol

• Queue handling

• Things to ponder…

SAP PI brings the final divorce between

ABAP and Java Oxolution

Page 3: #sitNL presentation sap teched berlin v3

2

• Federated PI

SAP PI brings the final divorce between

ABAP and Java Oxolution

Page 4: #sitNL presentation sap teched berlin v3

Federated PI landscape

• Central

• Distributed

• Federated

SAP PI brings the final divorce between

ABAP and Java Oxolution

Page 5: #sitNL presentation sap teched berlin v3

2

• AEX

SAP PI brings the final divorce between

ABAP and Java Oxolution

Page 6: #sitNL presentation sap teched berlin v3

Single Stack capabilities via AAE

Advanced Adapter Engine Extended

SAP PI brings the final divorce between

ABAP and Java Oxolution

Page 7: #sitNL presentation sap teched berlin v3

AEX 1

• Single Stack

– reduced TCO Fast installation Less hardware fast restart

• Speed up to 10 times faster

• 1 monitoring• 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

Page 8: #sitNL presentation sap teched berlin v3

AEX 2

• Integrated scenario from PIS

• XML validation redesign (ESR schema based)

• Large binary to binary file transfer

• Time-out config per comm channel• 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

Page 9: #sitNL presentation sap teched berlin v3

2

• PI 7.3 Java only

SAP PI brings the final divorce between

ABAP and Java Oxolution

Page 10: #sitNL presentation sap teched berlin v3

PI 7.3 Value proposition

SAP PI brings the final divorce between

ABAP and Java Oxolution

Page 11: #sitNL presentation sap teched berlin v3

ES Repository 7.3 (CE7.3 and PI7.3)

SAP PI brings the final divorce between

ABAP and Java Oxolution

Page 12: #sitNL presentation sap teched berlin v3

Service bus

SAP NetWeaver PI 7.3

SAP PI brings the final divorce between

ABAP and Java Oxolution

Page 13: #sitNL presentation sap teched berlin v3

2

• Performance boosts

SAP PI brings the final divorce between

ABAP and Java Oxolution

Page 14: #sitNL presentation sap teched berlin v3

Performance 1

• Message blacklisting

– Identifies possible disruptive messages

• Flag them as suspicious upon server restart

• Cancel upon second restart

SAP PI brings the final divorce between

ABAP and Java Oxolution

• 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

Page 15: #sitNL presentation sap teched berlin v3

2

• JVM improvements

SAP PI brings the final divorce between

ABAP and Java Oxolution

Page 16: #sitNL presentation sap teched berlin v3

JVM improvements 1

• Advanced garbage collection and improved

JVM instability detection:

SAP PI brings the final divorce between

ABAP and Java Oxolution

Page 17: #sitNL presentation sap teched berlin v3

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

SAP PI brings the final divorce between

ABAP and Java Oxolution

restarts due to unhandled JVM exceptions

• 16 GB JVM nodes (big files)

• Background GB runs constantly for good

response and stability

Page 18: #sitNL presentation sap teched berlin v3

2

• Simplified configuration

SAP PI brings the final divorce between

ABAP and Java Oxolution

Page 19: #sitNL presentation sap teched berlin v3

Simplified Configuration 1

SAP PI brings the final divorce between

ABAP and Java Oxolution

Page 20: #sitNL presentation sap teched berlin v3

Simplified Configuration 2

SAP PI brings the final divorce between

ABAP and Java Oxolution

Page 21: #sitNL presentation sap teched berlin v3

2

• CPA cache

SAP PI brings the final divorce between

ABAP and Java Oxolution

Page 22: #sitNL presentation sap teched berlin v3

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

SAP PI brings the final divorce between

ABAP and Java Oxolution

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

Page 23: #sitNL presentation sap teched berlin v3

2

• XI 3.1 protocol

SAP PI brings the final divorce between

ABAP and Java Oxolution

Page 24: #sitNL presentation sap teched berlin v3

XI 3.1 protocol

• For communication between PI components

– Integration Server <-> Adapter Engine

– Integration Server <-> Integration Server

• Leads to performance improvements,

SAP PI brings the final divorce between

ABAP and Java Oxolution

• Leads to performance improvements,

especially on Adapter Engine

• Easier and faster EO message processing

between PI components

• Works out of the box

Page 25: #sitNL presentation sap teched berlin v3

2

• Queue handling

SAP PI brings the final divorce between

ABAP and Java Oxolution

Page 26: #sitNL presentation sap teched berlin v3

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

SAP PI brings the final divorce between

ABAP and Java Oxolution

– Relieves administrator monitoring queues

– Prevent inconsistent qRFC status for unhandeld

exceptions

– Long awaited functionality

– Rebalancing queue’s

Page 27: #sitNL presentation sap teched berlin v3

2

• Adapter specific news

SAP PI brings the final divorce between

ABAP and Java Oxolution

Page 28: #sitNL presentation sap teched berlin v3

Adapter

• PI 7.3 allows to control the resources usage

per adapter channel

– Some adapter allow control for maximum parallel

connections

SAP PI brings the final divorce between

ABAP and Java Oxolution

connections

• No channel can clog up the adapter

• Business critical interfaces always get resources

Page 29: #sitNL presentation sap teched berlin v3

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…

SAP PI brings the final divorce between

ABAP and Java Oxolution

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

Page 30: #sitNL presentation sap teched berlin v3

Questions ?

SAP PI brings the final divorce between

ABAP and Java Oxolution