Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

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.

Introducing Services

Updated on September 10, 2021

 This presentation is part of the Services and Connectors Self-Study Course.


Incoming service requests are associated with the combination of a Service Package, Service Rule, and service Activity. 

A Service Package is an instance of Data-Admin-ServicePackage and identifies an Access Group, thereby granting necessary authorization to the service request. A Service Package is specific to a particular integration protocol, such as SOAP or JSR-94, and contains a list of one or more Service Methods called Service Rules.  Service Rules are specific to the integration protocol, such as Rule-Service-SOAP for SOAP and Rule-Service-JSR94 for JSR-94.

Service Rules always call Activities.  Since Activities can do just about anything, all functionality available in PRPC, whether it be declarative expressions or creating work, can all be done via a service request. Both the Service Rule and service Activity can manipulate the clipboard.  Configuration of the Request and Response parameters are done from within the Service Rule.  Sometimes the packaging of Service Rules within a single Service Package yields additional functionality.

PRPC contains many wizards that help support it being executed as a service.  PRPC can publish a WSDL file that allows external systems to call a PRPC service using SOAP.  PRPC can import Javabeans, generating data class structures in support of JSR-94 integration.

Depending on the integration method chosen, some services can be generated via a wizard and others are manually created.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us