More about Service Portlet rules
 

Authentication

A portal server manages the authentication of its users. Therefore, when the Process Commander portlet is called, a user is already identified and there is no reason for that user to identify himself again to Process Commander. The user credentials and identity are available, but this data must be transferred from the portal server to Process Commander. The transfer of credentials is managed through the Process Commander 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

C-1105 You can generate harness forms for work objects that are JSR-168 compliant, through fields on the HTML tab. See:

• Harness rules — Completing the HTML tab
• Section rules — Completing the HTML tab

Debugging with the Snoop portlet

Many portlet vendors include a debugging portlet. See Pega Developer Network article PRKB-21753 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 Tracer tool   — Tracing services. C-2430

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 Pega Developer Network article PRKB-24048 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 PRKB-25032 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 Pega Developer Network.

Inbound Public render parameters

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

	service
	About Service Package data instances Harness form — Completing the HTML tab Section form — Completing the HTML tab
	Atlas — Standard Service Portlet rules

About Service Portlet rules