Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

What's new in V5.4 - Integration

Suggest edit Updated on October 9, 2012

 

 

 

NewAnnounced in February 2008, Process Commander V5.4 offers dozens of new capabilities for developers, application users, and system administrators, and resolves issues found in earlier versions. This announcement summarizes V5.4 enhancements and new features that support integration of Process Commander applications with external systems, in seven areas:

To learn about V5.4 features in other areas, see What's New in Process Commander 5.4.

Email

Two enhancements are available for processing incoming email:

See:

Portlet Services

Several enhancements improve portlet services:

  • Portlet applications can now be deployed as a WSRP producer. Web Services for Remote Portlets (WSRP) is an OASIS standard that enables portlets deployed on one portal server to be displayed in the portal page of another portal server.
  • Portlet applications now have Log4J logging.
  • The WAR file generated for a portlet now includes a Liferay portal server configuration file, liferay-display.xml, by default.
  • The Process Commander portlet Java classes now maintain the HttpClient object. Your portlet no longer needs to maintain session state by setting the requestor session ID in a cookie.
  • You no longer use the ContextURL parameter to construct URLs to static files such as images. You now can reference files stored as binary or text file rules the same way in the HTML stream rules used for portlets as you do in
    the HTML stream rules that are not used in portlets.

See:


JMS Services and Connectors

You can now identify the Java Message Service resources (connection factories, destinations, and so on) a JMS service or connector interacts with through resource references defined in the Process Commander deployment descriptor file. See How to configure a JMS service or connector to find JMS resources through resource references.

Additional new articles describe JMS design and development in V5.4:


Asynchronous service processing

Services generally process service requests synchronously. That is, they immediately perform their requested processing and return a configured return value while the calling application waits. However, you can configure EJB, HTTP, Java, JMS, MQ, and SOAP services to use the new Queue Manager infrastructure to queue the request for asynchronous execution and the calling application calls back later for the results. See:


SOAP Connectors


Service Accelerator

The Service Accelerator is enhanced to support resource references. See:


Integration with Microsoft Outlook email client

Two new standard flow actions GetAppointmentList and SendMeetingRequest enables users to query the Microsoft Outlook calendars of other operators. Typically they are used in sequence: An operator uses GetAppointmentList first to determine whether another operator is available at a specific time, and then use SendMeetingRequest to make and appointment. See Integrating with Outlook calendars.

* * * * *

 

 

Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us