In NetWeaver (NW) 7.0x system the /wpccontent repository was specifically for use with WPC (Web Page Composer) 1.0.
If you want to index the WPC content in a NW 7.0x system you have to create an index on /wpccontent repository.
In NW 7.30 or higher releases, the old WPC application is replaced with WPC 2.0 and the content stored in the /wpccontent repository is copied over to the new repositories used by WPC 2.0 (Staging Area and Global Shared Content) and transformed so that it is usable/compatible with the new application. Once the content has been migrated from the /wpccontent repository to the new repositories, this repository becomes redundant and the content is no longer usable in the WPC application.
The WPC content in a NW 7.30 or above system cannot be indexed in the same manner as standard KM repositories. If you want to index the WPC content in a 7.30 system or above, then it will be necessary to do so via the exact steps outlined in the following help documentation:
While doing the steps in the document you might encounter some issues.
- SAP NetWeaver Enterprise Portal from 7.3x onwards
- Web Page Composer
Connect a New Filter to the Web Repository, Repository Filter, Repository Filters, CRM Namespace Filters, Create a new Index, portal_indexing_wr, portal_indexing_ws, Configure Delta Indexing, com.sap.km.appl.portal.index.provider, UpdateInterval(minutes), enableQuickLinkInSearchResults, Configure the Search UI, km.appl.portal.indexing.framework, IndexPropertiesServiceWrapper, ActivatePortalSearch, , KBA , EP-PIN-WPC , Web Page Composer , EP-PIN-WPC-WCM , Web Content Mgmt (Content Library, Web Resources, KM Integ.) , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.