Oracle Determinations Server supports older WSDLs, specifically schema versions 9.1.4 and 9.1.
Oracle Determinations Server Services still uses the following endpoint regardless of WSDL version:
- Java : http://my.server.com/hds/soap
- .NET : http://my.server.com/hds/soap.asmx
To access the Server WSDLs, the following URLs are used:
- Call for latest Server WSDL (9.3)
- Java : http://my.server.com/hds/soap?wsdl
- .NET: http://my.server.com/hds/soap.asmx?wsdl
- Call for versioned Server WSDL
- Java : http://my.server.com/hds/soap/server-wsdl-version/<version>?wsdl
- .NET: http://my.server.com/hds/soap/server-wsdl-version/<version>.asmx?wsdl
Generic Rulebase Services can be accessed using the endpoints:
- Java : http://my.server.com/hds/soap/<rulebasename>
- .NET : http://my.server.com/hds/soap/<rulebasename>.asmx
To access the Generic RulebaseWSDLs, the following URLs are used:
- Call for latest Generic Rulebase WSDL (9.3)
- Java : http://my.server.com/hds/soap/<rulebasename>?wsdl
- .NET: http://my.server.com/hds/soap/<rulebasename>.asmx?wsdl
- Call for versioned Generic Rulebase WSDL
- Java : http://my.server.com/hds/soap/<rulebasename>/<version>?wsdl
- .NET: http://my.server.com/hds/soap/<rulebasename>/<version>.asmx?wsdl
For example, if we deployed MyRulebase in Tomcat and we want to access the 9.1 generic WSDL, the appropriate call would be:
http://my.server.com/hds/MyRulebase/9.1?wsdl
Specific Rulebase Services can be accessed using the endpoints:
- Java : http://my.server.com/hds/soap/specific/<rulebasename>
- .NET : http://my.server.com/hds/soap/specific/<rulebasename>.asmx
To access the Specific Rulebase WSDLs, the following URLs are used:
- Call for latest Specific Rulebase WSDL (9.3)
- Java : http://my.server.com/hds/soap/specific/<rulebasename>?wsdl
- .NET: http://my.server.com/hds/soap/specific/<rulebasename>.asmx?wsdl
- Call for versioned Specific Rulebase WSDL
- Java : http://my.server.com/hds/soap/<rulebasename>/specific/<version>?wsdl
- .NET: http://my.server.com/hds/soap/<rulebasename>/specific/<version>.asmx?wsdl
For example, if we deployed MyRulebase in IIS and we want to access the 9.1.4 specific WSDL, the appropriate call would be:
http://my.server.com/hds/soap/MyRulebase/specific/9.1.4.asmx?wsdl
To illustrate the new feature, we use the GetVersionService:
GetVersionService Request using 9.3 schema
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/
" xmlns:typ="http://oracle.com/determinations/server/9.3/server/types"><soapenv:Header/>
<soapenv:Body>
<typ:get-version-request/>
</soapenv:Body>
</soapenv:Envelope>
GetVersionService Response in 9.3 schema
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/
" xmlns:typ="http://oracle.com/determinations/server/9.3/server/types">
<SOAP-ENV:Header/>
<SOAP-ENV:Body>
<typ:get-version-response>
<typ:determinations-server-version>9.3.1.70</typ:determinations-server-version>
<typ:determinations-engine-version>9.3.1.71</typ:determinations-engine-version>
</typ:get-version-response>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
GetVersionService Request using 9.1.4 schema
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/
" xmlns:typ="http://oracle.com/ruleserver/9.1.4/server/types">
<soapenv:Header/>
<soapenv:Body>
<typ:get-version-request/>
</soapenv:Body>
</soapenv:Envelope>
GetVersionService Response in 9.1.4 schema
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/
" xmlns:typ="http://oracle.com/ruleserver/9.1.4/server/types">
<SOAP-ENV:Header/>
<SOAP-ENV:Body>
<typ:get-version-response>
<typ:ruleserver-version>9.3.1.70</typ:ruleserver-version>
<typ:engine-version>9.3.1.71</typ:engine-version>
</typ:get-version-response>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>