Escenic Portlets
All content stored in the Escenic Content Engine can be presented and used in an Oracle Portal. Escenic provides a set of standard portlets, as examples of how to use content stored in the Escenic Content Engine in a portal environment. These portlets are JSR-168 compatible, and can be customized as is, or be used as a basis for further development.
General Architecture
Both Oracle Portal and Escenic Content Engine require their own database scheme on a database server. These two database schemes can either run on the same physical database server, or they can run on two different database servers.
Oracle Portal and Escenic Content Engine can share the same users on the LDAP server, or they can have separate user repositories. In the first case, the users will usually be created through the Oracle Portal user administration. The newly created users can then be imported into Escenic and then be assigned different roles and groups through the Escenic Content Engine web interface.
Escenic Portlets
There are five Escenic portlets available, listed below. The documentation included with each portlet provides detailed information, including guidelines for template developers on how these portlets can be customized to fit desired design and layout.
The Escenic portlets typically consists of two JSP files: The portlet and a configuration template used to configure/edit default values for the portlet through the Oracle Portal framework.
- Menu Portlet: Displays all the Escenic sections in a hierarchy.
- Content Portlet: The Content Portlet has two main purposes; to display the content of section FrontPages, and to display the content of articles.
- Latest Articles Portlet: Lists the latest articles from Escenic Content Engine.
- Search Portlet: Simple and advanced search interfaces for searching in content stored in the Escenic Content Engine. The result is also displayed in a portlet.
- Search Simple Input Portlet: A portlet that interfaces a simple search and sends the search query to the Search Portlet.
