More about Service Portlet rules


A portal server manages the authentication of its users. Therefore, when the Pega Platform portlet is called, a user is already identified and there is no reason for that user to identify himself again to the Pega Platform. The user credentials and identity are available, but this data must be transferred from the portal server to the Pega Platform. The transfer of credentials is managed through the Pega Platform single sign-on feature.

Single sign-on is implemented through the authentication service data object ( Data-Admin-AuthService ). For portlets, single sign-on is implemented by default through a standard portlet authentication service named PRPortletService.

You can use the standard portlet authentication service to manage the identification of the portlet users. Change the default settings to values that are appropriate for your system and modify the authentication activities as necessary.

Portlet-compliant harness forms

You can generate harness forms for work items that are portlet compliant, through fields on the HTML tab. See:

Debugging with the Snoop portlet

Many portlet vendors include a debugging portlet. See PDN article How to debug portlets with the Snoop portlet.

Debugging with the Tracer

You can trace the operation of a Service Portlet rule and the service activity it calls. See Tracing services.

Debugging with the Liferay Portal Server

The open source LifeRay Portal application server, a variant of the Apache Tomcat server, can be helpful in testing Service Portlet rules. See PDN article How to set up Liferay Portal Server (v3.6.1) to run JSR-168.

Web Services for Remote Portlets WAR

You can generate a portlet.war Web archive (WAR) file that can be deployed as an OASIS Web Services for Remote Portlets (WSRP) producer. For information, see PDN article How to deploy a Process Commander portlet as a WSRP producer in WebLogic Portal Server.

Performance statistics

For information on configuring the Performance tool for services and interpreting the results, see Testing Services and Connectors, a document in the Integration Services section of the PDN.

Inbound Public render parameters

Public render parameters received by PRPortlet are mapped to the pyInboundPortletServiceData clipboard page by the Rule-Service-Portlet.Run activity.