Generic vs Specific Data Model     

Rulebase services are provided in two forms, Generic and Specific.  Each of these forms have their own WSDL and service endpoints; for example, if I deploy MyRulebase to the Oracle Policy Automation Determinations Server, it will create the following two sets of services:

    1. the generic MyRulebase services with an endpoint at http://my.server.com/hds/myrulebase with the WSDL available from http://my.server.com/hds/myrulebase?wsdl
    2. the specific MyRulebase services with an endpoint at http://my.server.com/hds/myrulebase/specific with the WSDL available from http://my.server.com/hds/myrulebase/specific?wsdl

 

Both the specific and generic services offer the same services:

 

The difference between the two services is that the Specific service has a WSDL and Schema specifically generated to suit the rulebase, whereas the generic service uses the same schema for every rulebase.

The Assess and GetScreen services can make use of the Specific Schema.  Because the Specific schema is more meaningful, it is recommended that you use Specific services when using Rulebase operations.

The session data for a specific request is different from generic session data. To see the difference between generic and specific, see the following Assess Request Message example that includes both the generic and the specific request:

Example: Assess Request xml