Skip to main content

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

Service EJB rules - Completing the New or Save As form

Updated on August 16, 2022

Service EJB rules - Completing the Create, Save As, or Specialization form

Note: Beginning in Pega Platform 8.6, EAR deployments of Pega Platform are deprecated. In the upcoming 8.7 release, EAR deployments will not be supported. As a result, in Pega Platform 8.7, Service EJB rules will also no longer be supported. For more information on the alternatives for EAR-related rules, see Deprecation of EAR deployments in Pega Platform 8.6.

Records can be created in various ways. You can add a new record to your application or copy an existing one. You can specialize existing rules by creating a copy in a specific ruleset, against a different class or (in some cases) with a set of circumstance definitions. You can copy data instances but they do not support specialization because they are not versioned.

Based on your use case, you use the Create, Save As, or Specialization form to create the record. The number of fields and available options varies by record type. Start by familiarizing yourself with the generic layout of these forms and their common fields using the following Developer Help topics:

This information identifies the key parts and options that apply to the record type that you are creating.

Note: Create a Service Package data instance before creating a Service EJB rule; the name of the Service Package data instance is the first key part of a collection of Service EJB rules.

Create a Service EJB rule by selecting Service EJB from the Integration-Services category.

A Service EJB rule has three key parts:

Customer Package Name Select the name of the service package (instance of the Data-Admin-ServicePackage class). The service package must exist before you can create the service rule. See About Service Package data instances. If your application is to process requests from this service asynchronously through a background agent, define a Service Request Processor data instance ( Data-Admin-RequestProcessor-Service class) with this Customer Package Name value as key.
Customer Class Name Enter the name of the service class. This is an arbitrary text value that is a Java identifier, not an instance of the Rule-Obj-Class class. The service package name and service class name group service rules. See How to enter a Java identifier.
Identifier Enter the name of the service method. This name is an arbitrary identifier; it is not related to a Rule-Method instance. The service method named describes what the service rule does. See How to enter a Java identifier.

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