When we go for IDOC_AAE or IDOC .......?

[Former Member]

Hi Experts,

I am new to SAP PI 7.3, and need to work on IDOC_AAE in future .

Can anybody suggest me when IDOC_AAE is preferable

suppose there are 40 interfaces having IDOC requirement, so based on what parameters we can decide to work with IDOC_AAE or Simple IDOC adapter.

Thanks

Dhileep

[Former Member]

Hi Dhileep,

With PI 7.30, another IDoc adapter is introduced. This is a java adapter which does not use ABAP services and configuration. In this blog we will examine the configuration requirement for this new java adapter.

Background Info:

With PI 7.30, two new adapters are introduced: Java IDoc and java HTTP adapters. These 2 adapters are useful in the following situations:

1. To bypass message processing in the ABAP stack, by using the Integrated Configuration of the Advanced Adapter Engine (AAE). This will decrease the resource uilization and increase performance. In another word, we will be able to process more messages faster, with less hardware resources (memory and CPU). In some benchmarks, we have been able to increase the performance of message throughput by 10X.
2. To be used in the java-only installation of PI 7.30. PI 7.30 provides two installation options: dual-stack (ABAP and java) and single-stack (java-only). By installing the java-only installation, we can decrease the hardware requirement by half, and we can also decrease the installation time by half. Without the ABAP stack, we will no longer have the "classical" IDoc and HTTP adapter in ABAP, therefore, the need for a java adapter.

The new IDoc adapter is "IDoc_AAE". NOTE: In a dual-stack installation, we can use either the IDoc or IDoc_AAE adapter.

Configuration:

In the blog, we will discuss the recommended configuration. This configuration provides the best logging and tracing capabilities. Also, it allows the sharing of connections for better resource utilization and minimizes configuration errors.

1. RFC Destination Configuration for receiver communication channels: Just as in ABAP, we have to have an RFC destination. But, in this case, this is a java RFC destination.
   1. Go to NWA and click on: Configuration -> Connectivity -> Destination
      
   2. Click on "Create":
      
   3. Enter the required information:
      • Select the local java system as the hosting system.
      • Enter a name for the RFC connection.
      • Select RFC as the destination type.
      • Click on Next.
      
   4. Enter connection information and click Next: (below is an example)
      
   5. Enter logon information and click Next:
      
   6. Enter connection pool settings and click Finish:
      
   7. Perform a "ping" to test the connection.
      
2. RFC Destination Configuration for sender communication channels: When sending IDocs from ERP, an RFC destination to the PI system will be required during the ALE configuration on ERP. In order the create the RFC destination on ERP, a "programid" for an RFC adapter on PI is needed.
   1. In NWA: Configurations -> Infrastructure -> Application Resources
      
   2. Select the resource adapter, inboundRA:
      1. Enter "inbound" in the filter for Resource Name
      2. Click on the filter
      3. Select Resource Adapter, inboundRA
      
   3. Configure the default RFC adapter for sender communication channel:
      1. Scroll down to the bottom half of the page
      2. Click on "Properties"
      3. Enter a value for "MaxReaderThreadCount"
      4. Enter "true" for Local
      The ProgramID, XI_IDOC_DEFAULT_PID, must be used when creating the RFC destination on the ERP system.
      
   4. Create an RFC destination, using SM59, on the ERP syste (not shown here)
3. IDoc_AAE Adapter Configuration:
   1. Receiver Communication Channel: the receiver is where the RFC destination is needed.
      Below is an example of the IDoc_AAE Receiver Communication Channel.
      
   2. Sender Communication Channel: (use default configuration)
      

[Former Member]

Yes you are right , the whole process is to achieve ,bypass the messages  in ABAP Stack and faster message processing.But in what cases we can use the IDOC_AAE , any specific parameters to define an interface to be build using IDOC_AAE only.Let me know , i wanna build the 30 interfaces using IDOC Adapter and remaining by using IDOC_AAE out of 40.Is it possible to do it in this way?????

Regards,

Dhileep

[baskar_gopalakrishnan2]

IDOC_AAE perform much faster than traditional Idoc adapter. The main reason is it works in single java stack whereas converntional works in abap stack. Business requirement wise you can choose any of them. You can try both only in dual stack 7.3. Whereas if you have 7.31 installation you have no option and you can use only idoc_AAE.

>i wanna build the 30 interfaces using IDOC Adapter and remaining by using IDOC_AAE out of 40.Is it possible to do it in this way?????

Yes. it is possible.