Back Forward Service HTTP rules
Completing the Create, Save As or Specialization form
  1. About 
  2. New 
  3. Service 
  4. Request 
  5. Response 
  6. History 
  7. More... 

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

Based on your use case, the Create, Save As or Specialization form is used to create the record. The number of fields and available options vary by record type. Start by familiarizing yourself with the generic layout of these forms and their common fields:

This help topic then identifies the key parts and options that are applicable to the record type you are creating.

NOTE: Before you begin creating a Service HTTP rule, create or identify a Service Package data instance; the name of the service package becomes the first key part of the Service HTTP rule.

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

Key parts:

A Service HTTP rule has three key parts:

Field

Description
Customer Package Name

SmartPromptSelect the name of the Service Package data instance for this 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 a name that logically groups related service methods (service rules). This name is unrelated to Rule-Obj-Class instances; it must be a valid Java identifier. See How to enter a Java identifier.

Identifier

Enter an arbitrary identifier that describes the function of the PRPC activity called by this service. See How to enter a Java identifier.

Rule resolution

When searching for a Service HTTP rule, the system filters candidate rules based on a requestor's RuleSet list, which defines the RuleSets and versions the requestor can access.

Circumstance-qualified and time-qualified resolution features are not available for Service HTTP rules. The class hierarchy is not relevant to Service HTTP rule resolution.

Up About Service HTTP rules