Limitations of SAP PI 7.3(single-stack Java installation)
Limitations of SAP PI 7.3(single-stack Java installation)
Introduction
Two options while installing SAP PI 7.3 :
1.) Single stack Java installation
2.) Traditional Dual stack installation
*This presentation will cover limitations of Single stack installation.
*But in some of the case alternatives will be provided.
*SAP introduced the Advance Adapter Engine (AAE) in PI 7.10. The AAE provides end-to-end message processing to be executed completely in the java-stack. This increases performance significantly since messages will no longer be passed back-and-forth between the ABAP and the java stacks. With this java-only processing, a new configuration object is also introduced in the Integration Directory to configure the end-to-end scenarios. This new configuration object is “Integrated Configuration Object”, or ICO, and is used to configure the scenarios which will only be processed in the java-only engine.
*With PI 7.30, AEX was created. AEX, a java-only ESB, is built on AAE
*The dual-stack installation continues to be available as an installation option. The architecture remains unchanged from the previous releases.
Note: *Please note the distinction between AAE and AEX
*AAE: AAE is an adapter engine which provides message processing in the java-only stack. AAE is installed in both dual-stack and single-stack PI installations of PI 7.1 and above.
*AEX: AEX is a java-only installation of PI, which uses the AAE.
1.) Decentralized adapter Engine doesn’t work in ICO/ ICO works with only same type of adapter engine.
*Error while assigning different adapter engine in sender and receiver communication channel: “Assigned sender and receiver communication channels are not configured for the same adapter engine; ensure that all channels are configured for the same adapter engine”
*So, If you want to work on Java based adapter and decentralized adapter engine then use classic configuration, as classic configuration supports both java based adapter and classic configuration. This can be monitor in SXMB_MONI transaction of ABAP stack.
Even this functionality is not supported on PI 7.3.1
2.) Advance Adapter Engine can not use Idoc adapter. As Idoc adapter is based on ABAP stack
*AAE cannot use Idoc adapter as Idoc adapter is based on ABAP stack but in PI 7.3 (Java stack) we have IDOC_AAE adapter available.
*If you still want to work with IDOC adapter only then install Dual stack
3.) Advance Adapter Engine can not use HTTP adapter.As HTTP adapter is based on ABAP stack
*AAE cannot use HTTP adapter as HTTP adapter is based on ABAP stack but in PI 7.3 (Java stack) we have HTTP_AAE adapter available.
* If you still want to work with HTTP adapter only then install Dual stack.
4.) AAE cannot use the WS adapter. As WS is an ABAP adapter
*If you want to work with WS adapter then install Dual stack.
Note: For all ABAP based adapter
*We can assign only java based adapter in ICO. It will not allow to assign ABAP based adapter in ICO as they are on Integration Engine.
*For Ex. Below are the list of ABAP and JAVA based adapters for a communication component
Below are the list of communication channels available in ICO for a communication component
Only Java based adapters are available in ICO
5.) ccBPM is not available for AAE
*ccBPM is not available for AAE. As ccBPM uses ABAP’s work-flow engine to orchestrate the messages.
*In case if it is required in your project then install Dual Stack.
6.) Extended Receiver Determination is not available in ICO
*Extended receiver Determination have used earlier in classic configuration.
![clip_image009[1]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgWd4aLPlarnMCQSftLKkThtk7nOChVoifCWDD0VQljpfqLiGNnBXd2XGKMhW_GCfW8RQu5Rw7NARXi08VxYGt-5_3QwXDdJaSLJt6TEcXehLMXuDYRZtOj0BU4_jUlHk_wOUHOatAhsGXW/s1600-h/clip_image009%25255B1%25255D%25255B2%25255D.gif "clip_image009[1]"){kind=small}
How ever Routing based on XPath expression is available
![clip_image009[2]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiSj0JZMWEWtKE8uPJS-H_ex8j8dQSGMOhSSMZA6jHu_-uFBH1hmGBvCC1uf9sU-1o5etAIIXd9a7jhLisZvGovYvSfS_RcefQcFHCqCnUwD13BElr77QdZgJc1i1039Ekq5ONbPgOkXZcj/s1600-h/clip_image009%25255B2%25255D%25255B2%25255D.gif "clip_image009[2]"){kind=small}
*Install Dual Stack for Extended Receiver determination in case it is required
7.) Using Integration Directory’s Receiver Rule is not available
*Receiver Rule is not available using Integration Directory
8.) Parameterized Mapping
*Using mapping parameters in Operations Mapping is not available in ICO.
![clip_image009[3]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiBqsdq5-42r40M3p9WD-9NbHyJxr8UG6uDD78aSa7HCwK2oov-ee2AVGgEAOJa2A28BYi4rzoWVljWNodRjgIQrS3QlzBfBYBswPgO90ldJD9jtv66zqrluSJnjcR1k1CFiPT44tHW5l33/s1600-h/clip_image009%25255B3%25255D%25255B2%25255D.gif "clip_image009[3]"){kind=small}
*No parameterized mapping in ICO
*This is still available with Dual Stack
![clip_image009[4]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj5pbGxr07CYtWfHe45XKLx_CqH_3ckX8AFlLbQaBKdE5fXOXYkoJ7oSelbsdhvisr78_huWtbVUwH0NwQ6ihTNbeTP7V-vpygIR4lO0XPcqwBZjeo3-MDj3SpbWoveFTVCcKyRE1hl8SJa/s1600-h/clip_image009%25255B4%25255D%25255B2%25255D.gif "clip_image009[4]"){kind=small}
9.) ABAP mapping cannot used by AAE
*ABAP mapping is executed in ABAP, therefore cannot be used by AAE.
ABAP mapping is present in PI 7.3 with Dual stack installation.
10.) AAE does not support “Maintain Order at Run Time”
*Maintain Order at run Time is not available in ICO. This was available in Classic configuration.
with Dual stack installation functionality of Maintain order at Run Time can be achieved with Java based adapter
*Below is the result of Maintain Order at Run Time in classic configuration for Java Based adapter.
11.) No more SXMB_MONI transaction
No message will be available in SXMB_MONI transaction of PI(ABAP Stack) system for Configuration scenario which are based on ICO.
But in SAP PI 7.3 we still have many option for monitoring the message in NWA for Single stack.
Summarizing AAE Limitations
AAE limitation in ICO for PI7.3 and PI 7.31 release:
Terms to understand
*AAE : AAE is an adapter engine which provides message processing in the java-only stack. AAE is installed in both dual-stack and single-stack PI installations of PI 7.1 and above.
*AEX: AEX is a java-only installation of PI, which uses the AAE. With PI 7.30, AEX was created. AEX, a java-only ESB, is built on AAE, but with all the ABAP dependencies removed
*ICO: “Integrated Configuration Object”, or ICO, and is used to configure the scenarios which will only be processed in the java-only engine.
*Classical configuration : Integration Directory configuration with Receiver Determination, Interface Determination, Sender and Receiver Agreements, and Communication Channels. These configurations are what we will call as “classical” configuration, and will be processed by both ABAP and java engines.
Contact:+918008002022
What is new in SAP NetWeaver PI 7.3 EHP1
by http://scn.sap.com/people/rajasekhar.reddy14
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).
Contact:+918008002022
PI 7.1 EHP1 Delta Features over PI 7.1
1. Service interface generation for WSDL import into ESR
The import of externally defined WSDL files into the ESR and the creation of service interface objects are supported via a wizard. The service interface definitions can be modified once they are imported into the ESR. The external services can be directly used for proxy generation. Multiple WSDL files can be imported.
2. Classification support in ESR
Classifications, which provide an option to add a semantic meaning, can be directly assigned in the ESR to one service interface or to a group of service interfaces. The ESR also allows searching for services by their classifications.
3. Security profile settings for service interfaces
Security levels can be directly assigned to the service interfaces in the ESR. The security level value is sent to the provider system during proxy generation and defines the minimum security configuration of the service definition.
4. Where-used list in Services Registry
The Services Registry allows searching for Service Groups. A Service Group bundles all services that are provided by the same logical service provider. If a service definition is assigned to a Service Group, it indicates that the service is used by a consumer. Service Groups can be published in SR and enable configuration of multiple services in one go.
5. Add information to services published in the Services Registry
The publication wizard of the Services Registry supports to classify the published service, add provider system information and a link to the documentation of the service, and add user name and password if the service requires authentication.
6. User defined usage profiles in the ESR & Service Registry
The ESR allows creating customized usage profiles to define sets of object types, software component versions and business modeling filters that are of interest to different user groups. The usage profiles can be assigned to specific users, roles, or groups, and are personalized filters that provide a fine granular control of who can view and edit SOA artifacts; with this a simplified UI is offered since all the other SOA artifacts are hidden. The Services Registry supports an elaborate authorization concept for its users and provides user-specific views on the content of the Services Registry. Security permissions can be defined that assign User Management Engine (UME) roles to classifications.
7. Cleanup of Services Registry
In the SAP NetWeaver Administrator tasks can be defined that provide information about invalid URLs and URLs that cannot be reached. The jobs can be either scheduled to run on a periodic basis or triggered as an event when required. Based on the information about the unavailable entities it can be decided to either correct a service endpoint or to remove the service definition from the Services Registry.
8. Generation of outbound interfaces based on inbound interfaces
The ESR provides a wizard to automatically create an outbound service interface for a given inbound service interface and assign a link between the service interfaces to indicate that the two interfaces match. The outbound service interface and the inbound service interface can reside in the same or in different software component versions.
9. Content Based Routing (CBR), Receiver Split+(RS) & Operation-dependent receiver determination in Advanced Adapter Engine (AAE)+
The integrated configuration, that determines the routing condition for the local processing on the AAE, supports the configuration of different receivers for different message payload values; i. e. a message that is processed locally on the AAE can be sent to different receivers depending on values of the message payload. The integrated configuration supports configuration of multiple receivers; i.e. a message that is processed locally on the AAE can be sent to multiple receivers. The receiver determination, that determines the routing condition on the Integration Server, supports definition of different receivers for different operations of same outbound SI.
11. Integration Directory API supports new objects types
The Integration Directory API, that provides a web services based API to access, edit, and activate objects in the Integration Directory, supports new object types and attributes that have been introduced with SAP NetWeaver PI 7.1, such as direct connections.
12. Enhanced search for communication channels
The Integration Directory allows searching for communication channels with adapter type specific attribute values; e. g. to search for communication channels with adapter type File/FTP who has configured a specific file name.
13. Scenario view in Integration Directory
The scenario view in the Integration Directory allows grouping assigned objects according to configuration scenarios.
14. Enhancements of Adapter Engine Java SE
Remote configuration: The remote configuration allows to add, start, and change remote adapter instances of the Adapter Engine Java SE; a message containing the configuration information is sent from the central Integration Server to local Adapter Engine Java SE.
Empty file handling: The empty file handling controls how the File/FTP sender adapter of the Adapter Engine Java SE handles empty files: The messages with empty files can be either processed or stopped with the creation of an error message.
Prevent overwriting files: The File/FTP receiver adapter of Adapter Engine Java SE allows to control whether files with names that already exist in target directory are to be overwritten.
15. Configuration based on Process Component Interaction Models
The model configurator, that creates the relevant configuration objects in the Integration Directory and groups them in a configuration scenario, allows to use one or multiple Process Component Interaction Models from the Enterprise Services Repository as a template for configuration; i. e. the Model Configurator creates the configuration objects in the Integration Directory based on the SOA artifacts saved in the Process Component Interaction Models together with additional assignments.
16. XI message protocol is supported in the AAEThe XI message protocol is supported via the SOAP adapter. With this messages that are sent to or received from ABAP proxies, other AAE's or Partner Connectivity Kits can be processed locally on AAE. The SOAP adapter is enhanced to accept XI message protocol.
17. End to end IDoc packaging
IDoc sender adapter allows optionally processing an IDoc package that reaches inbound channel of Integration Server from sender to receiver as IDoc package, i.e. IDoc package is not split into single messages that might have to be collected in integration process.
18. IDoc conversion adapter module
The IDoc conversion adapter module allows to convert an IDoc Xml message payload to an IDoc flat file format and vice versa. This IDoc conversion adapter module can be used together with a Java based sender and receiver adapter, optionally with local processing on the AAE, in order to connect to systems with IDoc entry points.
19. WS-Secure Conversation 1.3
This standard defines how to establish and maintain a persistent context for a secure session over which multiple web service invocations might be sent without requiring authentication each time. Currently supported is WS-Secure Conversation for SCT over SSL bootstrap.
20. User-defined message search for business criteria
A new, user-defined message search is available in the message monitoring that allows to search for business relevant information criteria contained in the message payload, such as sales order number or customer ID, as well as adapter-specific message attributes, such as file name for the File/FTP adapter. This new, user-defined message search does not require TREX. The previously introduced index-based message payload search using TREX is still available as well.
21. Cross domain message status overview
The SAP NetWeaver Administrator for PI offers a message overview for all domains that are connected to the SAP NetWeaver Administrator for PI. This enables an overview of the message processing at many levels, from the entire system landscape over domains to individual components, such as Integration Engines, Advanced Adapter Engines, Business Process Engines; therefore this is one further step towards monitoring the overall landscape of SAP NetWeaver PI systems.
22. PI monitoring and configuration capabilities available through SAP Solution Manager
The SAP Solution Manager, which is the central, IT role-based administration and monitoring infrastructure across the whole SAP landscape, provides direct access to main configuration and monitoring capabilities of SAP NetWeaver PI, such as SAP NetWeaver Administrator for PI or SOA Manager.
23. SOA configuration for connectivity of WS & consumers based on SOA Manager
The configuration for connectivity enables the configuration of groups of web services and web service clients in one go; i. e. multiple web services and web service clients do not have to be configured individually, but can be assigned to a configuration setting. The configuration is based on reusable objects, such as Service Groups; as mentioned above, Service Groups bundle all services that are provided by the same logical service provider.
24. Enhancement in migration controller for smooth upgrades of Java proxies to PI 7.1
The migration controller can automatically modify Java proxy based applications of previous SAP NetWeaver PI releases (SAP PI 7.0, SAP XI 3.0) and deploy the modified proxies to the target location of SAP NetWeaver PI 7.1.
SAP PI 7.3 Certification Books (BIT100,BIT400,BIT430,BIT460)
Hi Are you looking for SAP PI 7.3 Certification Books
1.BIT100_EN_Col95_FV_Part_A4 (2011)
2.BIT400_EN_Col95_FV_Part_A4_Notes(2011)
3.BIT430_EN_Col95_FV_Part_A4 (2011)
4.BIT460_EN_Col95_FV_Part_A4_Notes(2) (2011)
4 Books ((
Paypal ac : sapmdmtutorials@gmail.com
Once you pay the money send a conformation mail to info@sapnwtraining.com
We will send Download links.
All books for knowledge sharing purpose only. all rights reserved by SAP
SAP PI 7.3 Online Training
SAP PI 7.3 Online Training
For More Information contact
Vist :sapnwtraining.com
cell:918008002022
Subscribe to:
Posts (Atom)
