PI configuration notes

SAP PI/PO is the Module which integrates all the SAP modules where it acts as a mediator or for interpretation between different SAP systems and also between SAP and Non SAP systems.

Generally PI/PO systems will not be refreshed and it is very complicated.

If we get in to a situation to refresh PI/PO system, below info will be helpful.

Here are couple of notes for PI post configuration

PI SLD Self Registration - SAP Note 1439558

7.10 SP5 Patch 8, 7.11 SP1 Patch 0, 7.30 SP0 Patch 0

PI Demo Client - SAP Note 1304208

7.11 SP0 Patch 0, 7.30 SP0 Patch 0

PI Full Qualified Host Name - SAP Note 1320707

7.11 SP1 Patch 0, 7.30 SP0 Patch 0

PI Adapter Engine in Java Proxy Runtime Mode - SAP Note 1346933

7.11 SP4 Patch 0, 7.30 SP0 Patch 0

PI Robustness Configuration - SAP Note 1400543

7.30 SP0 Patch 0

PI Single Sign-On Configuration - SAP Note 1473556

7.30 SP1 Patch 0

PI Self Test for SAP NetWeaver - SAP Note 1286149

PI Wizards Overview - SAP Note 1286428

Performing a PI system copy SAP Note 1299373

Configuration Wizard: SAP Note 1400543

Parameter description SAP Note 1375656

Adapter Engine cannot be found in Integration Directory

"Adapter Engine can't be found in Integration Directory". We can find this error in integration directory and that we can resolve this issue using the subsequent steps.


To check the above error, attend integration directory click on menu Environment -> Cache Notification,


OR


While creating the channel for any adapter in integration directory, adapter engine won't show.


Reason for getting this error :


While doing the XI post-installation steps, the technical system and business system weren't created in SLD for XI server.


OR


The technical system and business system weren't created properly in SLD for XI server.


Proposed solution:


Technical system and business system to be recreated for XI server.


Steps to create technical system.


Step-1: Go to tcode : RZ70



Step-2: Check whether the hostname & gateway service entered correctly or not. If not enter the right hostname & gateway service than save.



Step-3: Click on "Proposal" button and install the default settings.



Step-4: Click on "Activate the current configuration" in Application toolbar.



Step-5: Click on "Start data collection" in Application toolbar and click yes.



Now go to SLD main screen, check whether the technical system created or not.



Step-1: Click on technical landscape in SLD home page.



Step-2: Choose the technical system type - Web AS ABAP.



Step-3: Find out the technical system created with the name “ on server name” .



Steps to create business system.



Step-1: Go to SLD main screen, click on business landscape and click on new business system.



Step-2: Enter the name of business system.



Step-3: Choose the technical system type "Web AS ABAP" and select the parameters technical system, client (ex: XID on iginsapep , 100).



Step-4: Click on the "Next" button and again "Next".



Step-5: Choose the business system role- Integration Server.



Enter the pipeline URL - http://:/sap/xi/engine?type=entry



Here hostname is server name, HTTPPort: 80.







Finally clicking the "Finish" button, it will create the business system in SLD for XI server.



Go to SLD main screen.

Check the technical system type: Exchange Infrastructure, in Application System column for integration server it should appear " on hostname" (ex: on iginsapep) . The below screen shot will appear after creating the technical system and business system in SLD.

To avoid other inconsistency problems in cache update or RWB, please implement the below oss note.

To appear " on hostname" in Application System column for other XI components Adapter Engine, Integration Directory, Integration Repository and Runtime Workbench/RWB. Refer the OSS note: 764176 and find the below attachment after implementing oss note.

Important Note-1: Add the merchandise “SAP Exchange Infrastructure 3.0” and every one the SWCVs to the above technical system and business system.

Important Note-2:  while creating the business system, if we face the error message “Integration Server already defined there's already Integration Server defined for the chosen technical system . Please select  Application system role.”, then delete the technical system and recreate the technical system using RZ70 and recreate the business system supported the technical system.

There are two ways to see the adapter engine status in Integration Directory.

Clear the integration directory cache  , Environment -> Clear SLD Data Cache.

First: Test the cache notification in ID , Environment menu -> Cache Notification

It shouldn't show any error message 'Adapter Engine not found in Integration Directory'.

Second: Check whether the adapter engine is showing in channel level for any adapter either in sender or receiver.