Skip to main content

Service Java rules

Suggest edit
Updated on March 16, 2022

Using the Java Business Delegate pattern and the Java Session Facade pattern, the Java service interface makes service rules available to external, Java-based applications as if the service rules were public methods of a Java class.

Note: Service Java rules are no longer being actively developed, and are being considered for deprecation in upcoming releases. Using Service Java rules does not follow Pega development best practices. Consider other implementation options instead.

To use Java service rules, the Pega Platform must be deployed as an enterprise application, not as a Web application. When the Pega Platform is deployed as an enterprise application, two EJBs ( PRServiceStateless and PRServiceStateful ) implement the session facade. They provide the public interface for remote and local access to Pega Platform Java and EJB services.

Java 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 Java services to process service requests asynchronously, which means the service queues the request for asynchronous execution and the calling application calls back later for the results. Additionally, you can configure synchronous Java services to check for specific error conditions that you expect will be temporary — work item locks, for example — and then queue service requests that fail for those reasons for another attempt at a later time.

Access

Use the Application Explorer to see Service Java rules in your application. Use the Records Explorer to list all Service Java rules that are available to you.

Category

Service Java rules belong to the Integration-Services category. A Service Java rule is an instance of the Rule-Service-Java rule type.

Did you find this content helpful? YesNo

Have a question? Get answers now.

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

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