It looks like JSR 286 and WSRP 2.0 portlets could get along. You'd have to figure out how to do that though. Here's the relevant info from the Cisco docs:
The Cisco Workplace Portal front-end uses Apache Pluto 1.1 libraries as the framework.
Portlets developed using APIs which meet the Java Portlet Specification (JSR168, JSR286) standards
may be deployed along with Service Portal. Once deployed, these will appear in Portal Designer as
“Third-Party Portlets” and can be added to portal pages. For more information on how to maintain JSR
portlets and other content in the Portal Manager solution, refer totheCisco Service Portal Designer
And then some information from the JSR-286:
JSR-286 is the Java Portlet specification v2.0 as developed under the JCP and created in alignment with the updated version 2.0 of WSRP. It was developed to improve on the short-comings on version 1.0 of the specification, JSR-168. Some of its major features include:
Inter-Portlet Communication through events and public render parameters
Serving dynamically generated resources directly through portlets
Serving AJAX or JSON data directly through portlets
This document explains the logic to develop Tidal Enterprise
Orchestrator workflow to automate the process of creating vCenter
Resource Pool* vSphere Power CLI must be installed either on the TEO
server or vCenter* vMA can also be used to achieve the same...
IntorductionCisco Process Orcehstrator (CPO) ships with the webservices
adapter that can be used to make Web Service API call to REST or SOAP
based applications. Before a sample workflow to make SOAP API calls
using CPO, lets understand some of the fundam...