We've been talking about SAP NetWeaver Process Integration moving to a pure Java world for some time now. Volker Stiehl, a chief product expert at SAP AG, has introduced technologies developed in to fit this strategy, including the Advanced Adapter Engine Extended (AEX), which Volker mentioned early last year in a couple of SAP Professional Journal articles (including the one linked above). The significance of AEX is that it could combine with SAP NetWeaver Business Process Management to allow for a more integrated experience regarding business processes.
This year, Volker has introduced a new offering called SAP NetWeaver Process Orchestration. I introduced it in a blog post last month. In short, it's a combined installation of SAP NetWeaver BPM, SAP NetWeaver Business Rules Management (BPM), and AEX, all on one Java Virtual Machine.
One of SAP NetWeaver Process Orchestration's features (with the 7.31 version, which is in Ramp-Up) is the ability to build integration scenarios within SAP NetWeaver Developer Studio. It's possible with the introduction of two perspectives -- the E
nterprise Service Repository (ESR) perspective and the Process Integration (PI) Designer perspective. These replace the Swing-based Enterprise Services Builder and Integration Builder (respectively).
In his latest SPJ article, Volker describes an integration scenario with the ESR perspective -- one article would not do justice to both perspectives. The good news is that Volker is working on a second article to explain the PI Designer perspective as well, so the full capabilities will be clear. Below is a sneak peek of the process model Volker used for the article, which SPJ subscribers can read here: Build Integration Scenarios Entirely within SAP NetWeaver Developer Studio: The Enterprise Services Repository Perspective.