This chapter provides an overview of portals and portlets.
A portal is a web destination that presents information and resources that are diverse in location, technology and derivation through a single point of entry. Content and technology that originate from widespread sources appear to your users as a cohesive set of information and services that are easily available from one location. For example, in a WebCenter Spaces portal, a user can look at all the Worklist items coming from their organization's business applications, the detailed customer information coming from a CRM suite, and the latest sales figure charts coming from a Business Intelligence tool. Despite these multiple sources, to your user, all of this content is available in one place and appears to be coming from a single source.
A portal is a customized solution for an organization with specialized content and a specific look and feel. Portal also provides authentication, authorization and administration tools.
An EnterpriseOne portal is a gateway that serves as a simple, unified access point to JD Edwards EnterpriseOne applications and can include one or more EnterpriseOne portlets. A portal delivers content and applications integrated with the JD Edwards EnterpriseOne system, and provides a collaborative workplace.
A Portlet can be considered as a miniature Web application that is running inside of a portal page along side any number of similar entities. A portlet is a web component which is managed by a portal and can process requests and generate dynamic content.
JD Edwards EnterpriseOne portlets are created using JD Edwards EnterpriseOne Forms Design Aid (FDA). These pre-built portlets allow employees to access JD Edwards EnterpriseOne information and complete tasks through a company intranet site or through the Internet. Many portlets allow personalization to make the interactive experience more efficient for the user.
EnterpriseOne also provide Configurable HTML portlets, which enable you to initialize a portlet to an existing portlet type or create a new portlet definition. In addition, when you initialize a configurable portlet, you define permissions to determine the type of access users have to the configurable portlet. You can grant either View or View, Config access. View permissions allow users to use a configurable portlet, but prevent them from modifying the definition of the portlet. View, Config permissions allow users to modify the definition and the permissions of a portlet. A user who has View, Config permissions basically has the same permissions of a system administrator. Therefore, you should carefully consider the users to which you grant View, Config permissions.
Many portlets are available that provide users with the ability to personalize content using the available functionality in JDE EnterpriseOne FDA portlets.
For more information on using JD Edwards EnterpriseOne Forms Design Aid to create JD Edwards EnterpriseOne portlets, see the JD Edwards EnterpriseOne Tools Form Design Aid Guide.
For more details about Configurable portlets refer to “Setting Up Viewable and Configurable Portlets” in this guide.
For more information on using JD Edwards EnterpriseOne portlets on WebCenter, see the JD Edwards EnterpriseOne Tools Portal Reference for Oracle WebCenter Guide.
For more information on using JD Edwards EnterpriseOne portlets on the JD Edwards Collaborative Portal, see the JD Edwards EnterpriseOne Tools IBM WebSphere Portal Reference Guide.
For more information on WebCenter administration, see the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter 11g Release 1.