In my experience, the Portal Content Studio is too complex for Web-Publisher with no IT-Background. Also the process to link HTML-Pages/XML-Forms to iViews is not comfortable enought.
To avoid working with the Portal Content Studio, you need other and better tools to create Web-based content and the corresponding Portal Content Objects.
We decided to use a professional Web Content Management System to create and approve Web-based Content (FIRSTspirit). For deploying content and creating the corresponding Portal Content Objects automatically (iViews, worksets, roles) in one step we developed an EP Business Package.
Before we developed the package we defined the main functionallity of our solution:
- The publisher should not be in contact with the complex Portal Content Studio
- The publisher should create addional EP-navigation entries for content-pages without working with the Portal Content Studio and no need to contact an IT-Administrator to link the new content page as a new navigation-entry
- The publisher should not need to have SAP EP Know-how
- The multi-language concept of SAP EP must be implemented also for the content
- The content should be personalized through SAP EP Roles
- The content should be searched and found by TREX
- The search Result should be consider the authorization (Portal Roles assigned to content pages)
- Hyperlinks in the content should be act as portal links
- The Navigation-structure in roles should be mixed with Web-Contend an other Portal Content (e.x. ESS-iViews)
- The content should be editable also in the portal after Deployment
- The creation-logic of Portal Objects should be flexible
- The content-display should automatically changed, when a other portal theme are choosen
We archived all goals with our development.
The communication between the FIRSTspirit and SAP EP based during deployment of content pages is based on WebServices running as a Portal Service.
The Content is deployed on a special Web Application on the Portal Server (JSP-Files).
To integrate the TREX-Search we created content links and used the Standard KM Repository Manager.