Additional Blogs by Members
cancel
Showing results for 
Search instead for 
Did you mean: 
Former Member
0 Kudos

I have seen in SDN forum, many of them posted

"Adapter Engine cannot be found in Integration Directory"

. We can find this error in integration directory and we can resolve this issue using the following steps.



To check the above error, go to integration directory click on menu Environment -> Cache Notification, find the below screen shot.




OR




While creating the communication channel for any adapter in integration directory, adapter engine will not show. Check the below screen shot.




Reason for getting this error :


While doing the XI post-installation steps, the technical system and business system were not created in SLD for XI server.


OR


The technical system and business system were not created properly in SLD for XI server.






Proposed solution:


Recreate the technical system and business system for XI server.



Steps to create technical system.


Step-1:

Go to tcode : RZ70




   

 

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



Important Note-2:

Suppose while creating the business system, if you get the error message

“Integration Server already defined There is already Integration Server defined for the selected technical system . Please select role Application system.”

, then delete the technical system and recreate the technical system using RZ70 and recreate the business system based on the technical system.





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



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



First:

Check the cache notification in ID , Environment menu -> Cache Notification



It should not show any error message

'Adapter Engine not found in Integration Directory'

.



Second:

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








I hope this blog is very helpful to resolve the adapter engine issues.

9 Comments