Skip to Content

Be the First to Play with a Java-Only Version of PI at TechEd 2010

Do you know that PI 7.3 has 2 installation options, dual-stack and java-only single-stack?

Be the first to work on a java-only PI version!

For the PMC262 session, “Using the Advanced Adapter Extended of SAP NetWeaver PI”, we will be using the single-stack installation of PI 7.3.  In this session we will cover the java IDoc adapter.  Yes, no ABAP will be used to send IDoc messages between backend SAP systems!  You will be able to learn the configuration requirements for both sender and receiver communication channels in an orders request and response scenario with an ECC backend system.

You will also use the new monitoring tools in NWA to track these messages.

Sign up for PMC262 before all the seats are taken.  This is a hands-on session, there are only a limited number of seats available.

You must be Logged on to comment or reply to a post.
  • Gr8 to hear ! Java only
    But what is the advantage of having Java only installation and dual stack installation ?

    Since there wud be a hit with perfromance a bit when routed through Java.U r comment on this ?


    • Hi,
      Java-only installaion takes half as much hardware resources and can be installed in half the time.  I installed one in about 1 hour, not counting the database installation.

      In addition, without the message going thru the ABAP stack, the performance can improved signicantly.  In some tests, the performance improved by 10X.


  • Hi,

    Is the Java-Only version the future of PI? I mean, it seems unnecessary to keep upgrading ABAP stack if the Java stack can handle all the requirements and when the new things like java-IDOC adapter are fully tested?

    I’m an ABAP programmer and it’s more difficult for me for example develop a Java mapping instead of ABAP mapping, but I think if the java monitoring is improved, and the ABAP stack doesn’t provide us with more capabilities, it makes no sense to have 2 stacks.

    In another way to see this, if SAP PI is java only, I think it can be more interesting for companies than doesn’t have other SAP Products like ECC.

    • Hi,
      Both dual-stack and single-stack options will be around for sometimes.  There are many companies using ccBPM, which runs in ABAP.  Eventually, NW BPM, BRM and the java-only PI will be integrated into the same installation instance.

      There is also the migration requirement/cost to move the classical configurations using Receiver Determination/Interface Determination/etc. to the Integrated Configuration of the Advanced Adapter Engine (AAE).

      I would see companies upgrade to dual-stack PI 7.3.  Then, migrate to the AAE-only configurations at their own pace and based on availability of java services such as NW BPM to replace ccBPM.


      • Thanks for your answer William,

        Of course I’m not talking about PI 7.3. But maybe in 2 or 3 versions more, it’s possible than ABAP stack disappears if all the missing capabilities are added to Java stack? And of course giving the customers enought time to migrate the interfaces to java stack

  • Hello William,

    We have been using AAE – ICO in our engagement.. Apart from the other limitations, we find monitoring to be a major pain point .. the purpose is performance and hence no of persistence steps are less.. and that results into much lesser information. Will the PI Java only version behave like the present AAE, or will there be a difference in terms of monitoring?

    • Hi,
      For both dual and single stack, PI 7.30 will have a new set of comprehensive monitoring tools in NWA.  The RWB will still be available, but only for the dual stack.

      There will still be some weakness in the persistency of synchronous messages in AAE, as they are only persisted in memory, without an option to persiste in database.  However, with a release/sp after PI 7.30, the database persistency will be included as an option.


  • Great news : I’ve always considered that dual stack systems are a major architectural error because of the added ressource consumption and the administration nightmare it generates.

    Choose ABAP or JAVA but never both for a single system !

    • >>Choose ABAP or JAVA but never both for a single system !

      i think, its not possible to choose only ABAP.
      either you have to go for ABAP+Java or Only Java.

  • Bill,
    Going Java only , what is the future for SAP JVM with the current restriction of 2GB heap size. Will that continue or will SAP JVM be capable of handling large heap sizes in the future?


    • Hi Vinod,
      I am so glad you asked this question.  The JVM has significantly been improved.  The GC (garbage collection) performance, which has restricted a 4 GB heap memory recommendation is now history.  There will be no longer a memory limitation!  Yes, you can have heap memory size as large as your physical memory.

      You can get a detailed overview of the improvements in all aspects of PI in performance and tolerance area in PMC210 session of the TechEd 2010.  I highly recommend this session and I think you will be impressed.

      PI 7.30 is a significant release in all aspects of the product.


    • ABAP proxy will not be effected.  The ESR will continue to be used for designing the services.  The ABAP backend can continue to generate the proxies from the ESR services via tx:SPROXY.  In the java-only stack, the XI adapter will still be availabe to integrate with the ABAP proxies.


  • Hi Bill,
    As I understand that to utilize BPM in PI 7.3, we have to install the ABAP stack. But in future I am guesing PI will be JAVA stack only. Will BPM be built for JAVA stack in the future or it is moving as its own seperate entity in the SOA ?
    • Hi,
      Currently, CE BPM can be used with PI.  In the future, CE BPM will be bundled with PI in the same installation.