This document describes some of the new features available in PI 7.3 EHP1.
Single Stack ESB:
Hardware requirement reduced by 50% compare to dual stack installation.
- Up to 60% less in energy conceptions and easy maintenance.
- Higher volume scenarios can be handled effectively.
Integration Flows:
Enterprise Integration Patterns is heart for any middleware implementations, Patterns can help in easily realizing common integration challenges. Each pattern-based integration flow lists all the steps required in SAP Net Weaver PI to realize the scenario.
One Central ES Repository for Multiple PI Domains:
Optionally a single ES Repository can be leveraged for multiple PI domains.
- Central governance incl. re-use of design objects across multiple PI domains.
- Largely improved flexibility for landscape setup.
- The ES Repository from any PI domain, i. e. double stack or Java Only PI with / without non-central adapter engines, can be leveraged for other PI domains.
- But: One domain can only use one ES Repository: Either its own or another domain‘s one.Local ES Repository is disabled; Central ES Repository will belong to all PI domains of SLD model
- Central SLD required.
- Configuration via CTC template and optionally also manual.
Logging of Synchronous Messages:
- Synchronous messages can be logged optionally on Java Only PI.
- Logging can be configured via global parameter (default) and scenario specific (also for asynchronous scenarios).
- Support also in user defined message search to search for payload values.
Integration with FTP Proxy Server via File / FTP Adapter:
- File / FTP adapter supports direct integration with FTP proxy server without any work around.
- Host name and port of FTP proxy server can be configured in FTP connection parameter settings of File / FTP communication channel with transport protocol FTP.
Completion of Java IDoc Adapter:
- Functionality of ABAP IDoc adapter fully included in Java IDoc adapter.
- IDoc packaging on receiver side to simplify IDoc processing, increase performance , simplify monitoring & error handling
- IDoc flat file module support for IDoc packages (multiple IDocs in a single IDoc flat file of same message / IDoc types).
JMS Adapter Enhancements:
- Support of further security standards (SSL Support), simplified configuration for integration with IBM Web sphere AS, optimized connection pooling for integration with MQ version 6.
- Support for Web sphere AS 7
- JMS connection pool optimization-Connection pooling with MQ version 6;not required anymore for MQ version 7(default configuration setting)
- JMS topic support –MQ set ClientId, Include Client Id and further connection settings for MQ in channel configuration (previously these were required as additional parameters).
Principal Propagation for SOAP Adapter (XI Protocol):
- Principle propagation between ABAP and Java proxies based on SAP logon / assertion ticket.
- Supported now additionally via XI message protocol of SOAP adapter, similar to SOAP & RFC protocol as well XI message protocol in Integration Server.
- Message execution under propagated user
- Based on trusted relationship configured between SAP Net Weaver PI and sender as well receiver system.
Completion of Integration between Java Proxies and SOAP Adapter:
- All scenarios for communication between SOAP adapter and Java Proxy Runtime via XI 3.0 message protocol are supported.
- For acknowledgements provider Java proxies and SOAP adapter can run on any Adapter Engine
- Consumer Java proxies and SOAP adapter can run on any Adapter Engine
- With this the limitations in SAP Net Weaver PI 7.3 for integration between Java proxies and SOAP adapter (XI protocol) are removed in EHP1 for SAP NetWeaverPI 7.3.
Integrated Stack:
- Common deployment of AEX and BPM/BRM on one single System ID.
- Reliable connectivity between messaging and process layer via proven Java Proxy Runtime.
- Preserve your investments by calling PI mappings (Java, XSLT) from within a BPM process.
- Model-driven development environment based on BPMN standard
- Leverage SAP NetWeaver BRM for business rules.
- Reduce TCO with single System ID installation.
- Reliable connectivity between BPM and PI/AEX at lower costs (as an alternative to WS-RM).
- Enhance mapping capabilities within a BPM process by calling PI mappings (e.g., calling XSLT).
