The new support tool was built to supply a clear picture regarding the existing appintegrator iViews in the portal and their system aliases.
After scanning an entered PCD location: ‘pcd:portal_content/…’ while clicking the ‘Find iViews’ button we get 2 tables: one with all the appintegrator iViews on that PCD location (also inside pages, roles, etc) and one with all their system aliases.
On the first table we have the option to test our iviews while clicking the ‘Test iView’ button
Other terms

Portal, appintegrator, AI, Application Integration, iview, support tool, system alias
Reason and Prerequisites

Running SAP portal with AI iviews
Solution

Steps to run the Support Tool:
1. Download the attached PAR file: ‘AIiViewsViewer.zip’ Unzip it and deploy it in your portal.
2. To start the tool navigate to: ://: /irj/servlet/prt/portal/prteventname/HtmlbEvent/prtroot/AIiViewsViewer.AIViewer Or to ://: /irj/servlet/prt/portal/prteventname/HtmlbEvent/prtroot/PortalAnywhere.Go and then start AIViewer application.
3. The default PCD location is ‘pcd:portal_content’ which is not the recommended location to use since it will scan all of your PCD and this could take a very long time or maybe even crash the search due to missing memory resources on portals that has huge number of iViews. The recommended way is to uncheck the ‘Use default location’ option and to specify a more specific PCD location such as: ‘pcd:portal_content/every_user’ and then click on the ‘Find iViews’ button to get the results.

1. AI iViews not working when located in Dynamic NavigationSymptom When trying to perform an action in an AI iView (e.g. – BSP, WebDynpro ABAP and etc…) that located in Dynamic Navigation area, a session error from the backend is thrown...