About Service Portlet rules |
New | Portlet | History | More... |
Java Specification Request 168 (JSR 168) describes a Java Application Programming Interface (API) for portlets, the small Web applications displayed by portal servers. The portlet integration interface in Process Commander supports the development and deployment of Process Commander portlets that are compliant with JSR 168 through the Rule-Service-Portlet rule type.
The portlet service provides access to a portlet Web application that you create. Your portlet application gathers and processes content from Process Commander and displays the content and the processing results in a portlet window on a portal page in a Web browser. The service package represents the portlet application, and the portlet service rule represents a portlet in the application. The service activity for a portlet service provides the home page — the first Web page that appears in the portlet on startup. Although it is typical to have one portlet service rule in a Process Commander portlet application, you can develop portlet applications with more than one portlet.
The external portlet can operate as a guest, or use the Process Commander single sign-on feature provided through Data-Admin-AuthService data objects. A standard authentication service object named PRPortletService is available to support portlets.
Use the Integration slice () to list the Service Portlet rules in your application. Use the Rules by Type Explorer to list all the Service Portlet rules available to you.
For a comprehensive description of the development process and a sample, see the Pega Developer Network article PRKB-25109About JSR-168 Portlet Services. and related articles.
Service Portlet rules belong to the Integration-Services category. A Service Portlet rule is an instance of the Rule-Service-Portlet rule type.