Hosted transparent decision services

Interceptors

You can specify that the service uses interceptors by setting the InterceptorEnabled parameter to true in the web.xml file.

<context-param>
   <param-name>InterceptorEnabled</param-name>
   <param-value>true</param-value>
</context-param>

Asynchronous execution of transparent decision services

By default, transparent decision services are parsed synchronously to force execution of the most up-to-date version of a ruleset. To execute an old ruleset until the parsing of the new ruleset is finished, set the AsynchronousRulesetParsing parameter in the web.xml of the transparent decision service to true.

<context-param>
   <param-name>AsynchronousRulesetParsing</param-name>
   <param-value>true</param-value>
</context-param>

XML schema

The XML binding mechanism uses the WSDL and schema files to build new XOM types. The schema files must be associated with a package name. The new XOM types are defined under the provided package. The list of schema files in the dynamic XOM path makes up the root XML schema files from which a complete list is computed. That list includes the dependencies. Root schemas are also included in their own schema dependencies. You can use Rule Designer to control whether this dependency is included in the ruleset archive.

Java XOM

public class MyLoan{
private double requestAmount;
public MyLoan(double requestAmount)
{
  this.requestAmount = requestAmount;
}
public double getRequestAmount() {
return requestAmount;
}
}

If this class is the only input parameter of the ruleset, the default generated WSDL contains only the following lines:

<xs:schema targetNamespace="http://www.ibm.com/rules/decisionservice/MyRuleApp/MyRuleset">

  <xs:complexType name="myLoan">
    <xs:sequence/>
  </xs:complexType>
  
</xs:schema> 

However, if you add the following JAXB annotations:

import javax.xml.bind.annotation.XmlElement;
import javax.xml.bind.annotation.XmlRootElement;

@XmlRootElement(name="my-loan", namespace="http://www.acme.com/loan")
public class MyLoan {

  @XmlElement(name="requestAmount")
private double requestAmount;

public MyLoan(double requestAmount) {
  this.requestAmount = requestAmount;
  }

public double getRequestAmount() {
return requestAmount;
}
}

And if this class is the input parameter of the ruleset again, the generated WSDL contains the following lines:

<xs:schema targetNamespace="http://www.acme.com/loan">

  <xs:complexType name="my-loan">
    <xs:sequence>
      <xs:element name="requestAmount" type="xs:double"/>
    </xs:sequence>
  </xs:complexType>
  
</xs:schema>

XML binding for Java types

Hosted transparent decision services support the first-level elements of the simple Java types, and the corresponding XML binding parameters in the WSDL code. A simple Java type is the finest-grain type from which a complex Java type can be expressed. A mapping table is provided in XML serialization of Java types.

WSDL generation

A WSDL file is a file that describes a web service. See the W3C web page Web Services Description Language . The format of a WSDL file is independent of the language that generates it. You can use WSDL files to generate client code. For more information about the available clients, see the page Invoking web services with Java clients.

The WSDL file that is generated by the transparent decision service references the XML schema types that are packaged in the RuleApp. You can use a tool such as Web Tools Platform (WTP) to generate a web service Java client. For more information, see the page Web Tools Platform (WTP) Project.

You can configure the WSDL generation through the Rule Execution Server console. You can configure the location and the web service endpoint. For more information, see Setting HTDS options.

WSDL generation configuration

Before you view or download the WSDL code for a hosted transparent decision service, you can configure the WSDL generation. Here are the available options:

1. Define target namespaces in the HTDS WSDL options of a ruleset. See Changing target namespaces.
2. Configure the web service endpoint. See Configuring the web service endpoint.
3. If you deployed the HTDS archive to a different server than localhost, you can change the location of the archive for that ruleset. See Configuring the transparent decision service location.
4. If you intend to import the transparent decision service into an IBM® Integration Designer project or to a different computer, download the WSDL file with the appropriate compatibility and zip parameters. See Setting HTDS options.

The following diagram illustrates this workflow.

Web service URLs and options

http://<server>:<port>/DecisionService/ws/<rulesetName>[/<rulesetVersion>]/<ruleAppName>[/ruleAppVersion>]?WSDL[&[&<options>]]*

Your request returns status codes to the calling client. For more information, see HTTP status codes and XML serialization.

Monitoring of transparent decision services