Back Forward Service SOAP rules
Completing the New or Save As form
  1. About 
  2. New 
  3. Service 
  4. Request 
  5. Response 
  6. Faults 
  7. XML Page 
  1. Advanced 
  2. Test Cases 
  3. History 
  4. More... 

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

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

The class and method name key parts are considered "external" and are unrelated to PRPC classes and methods, for flexibility. For example, a service that is already exported and deployed on a client computer may be changed to call a different PRPC activity. Because the external representation and the WSDL file hasn't changed, you do not need to redeploy and modify the application code on the client computer.

A Service SOAP rule has three key parts:

Field

Description
Customer Package Name

SmartPromptSelect the name of the service package (instance of the Data-Admin-ServicePackage class); this package groups related Service SOAP rules. Choose a name already defined through a Service Package data instance. See About Service Package data instances.
Customer Class Name

Enter a class name to logically group related methods. This name need not match the PRPC class that the activity belongs to, but must be a valid Java identifier. See How to enter a Java identifier.
Customer Method Name

Enter an identifier that describes the function of the PRPC activity that the service calls. 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 SOAP rule, the system filters candidate rules based on a requestor's RuleSet list of RuleSets and versions.

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

Up About Service SOAP rules