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.


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)

    Integrated Configuration in the AAE should be used with IDoc_AAE to take advantage of the performance improvments.

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Markus Karsch
    Hi William,
    I couldn’t find any information on metadata cache in SAP help for IDoc_AAE in PI 7.30. Does IDoc_AAE also uses a metadata cache and do we still need to manually refresh metadata if new IDoc version was created? Or does IDoc_AAE read metadata for every IDoc conversion per RFC?
  2. Niki Scaglione
    Hello William,
    Thank you for sharing this blog.
    Considering ONLY AEX system (PI ava stack), I’m facing same issues trying to test Idoc scenarios.
    1. It seems that RFC destination XI_IDOC_DEFAULT_DESTINATION is Mandatory and should point to an ABAP application server (otherwise I get error in the InboundRA). This is also mentioned into SAP Help Page http://help.sap.com/saphelp_nw73/helpdata/en/c2/91865252c84716b3b8be394851c9c0/frameset.htm. Is this correct?
    2. If as you reccomended, I set Default (instead of manual) in the field RFC Sender Parameters of CC sender than the RFC Destination used for any scenario is always XI_IDOC_DEFAULT_DESTINATION that is pointing to the same SAP System (ABAP). What is the solution for connecting a different SAP system?
    3. Is possible to use only local gateway for registering all the Program_id for Idoc sender scenarios?
    4. While restarting PI J2EE Engine, IDOC Metadata must be reloaded or not?

    Thank you in advance,

    1. Sridhar Raju Mahali

      Hello Niki,


      Answering to the point number 2. Create your own Resource Adapter such as inboundRA_<SID> by cloning inboundRA and maintain different SAP system details.Per Say, In NWA, Destinations:- XI_IDOC_DEFAULT_DEST_<SID> .

      Go to Configuration >> Infrastructure >> Application Resources >> Create New Resource >> New Resource Adapter. Clone inboundRA to inboundRA_<SID> and maintain above destination here, and choose RFC server parameters: FROM NWA. Other alternative is, choose ‘Manual’ in communication channel rather than Default(Recommended).



      Sridhar Raju Mahali


Leave a Reply