Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
former_member190293
Active Contributor
2,849


As many of us know, one of the new features introduced in SAP NetWeaver 7.3 EHP1 is the possibility of using custom XSLT Processor to support XSLT 2.0 transformations.

There is a wonderful blog written by chris.christoffersen which describes the steps need to be done in order to enable this new feature in PI/PO systems.

One thing: some users reported in comments, that after applying all necessary settings and performing all steps external proccessor stiil wasn't involved in XSLT mappings.

After some investigations, including attempts with different XSLT processor's JARs, the hint was found withing SAP Help page, describing this new feature:

To enable the use of external transformers, a new property has been introduced in the exchange profile.

Yes, the key difference between PI Dual Stack and PI AEX/PO systems is that PI Dual Stack reads parameter com.sap.aii.ibrun.server.mapping.externalTransfomer from Exchange Profile, while PI AEX/PO system takes this parameter from service XPI Service: AII Config Service.

Thus, to enable the external XSLT processor in PI Dual Stack system we should access Exchange Profile by following URL:

http://server:port/webdynpro/dispatcher/sap.com/com.sap.xi.exprofui/XIProfileApp

find parameter in parameters tree:



and set its value to "true" (mark checkbox).

Viola! Now our PI Dual Stack system is ready to work with XSLT 2.0 transformations.

Regards, Evgeniy.

4 Comments
Labels in this area