Service HTTP rules Completing the New or Save As form
About  New  Service  Request  Response  History  More...

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

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.

A Service HTTP rule has three key parts:

Field	Description
Customer Package Name	Select 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.
Customer Method Name	Enter an arbitrary identifier that describes the function of the PRPC activity called by this service. See How to enter a Java identifier.

For general information about the New form, see Completing the new rule dialog box. For general information on the Save As form, see How to enter rule keys using Save As.

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.

About Service HTTP rules