A company wants to implement a business rules solution for warranty claims on their widgets. The customer requires that servers should not store any…

The customer's requirements specify a stateless, synchronous, and platform-independent solution with strict contract enforcement for a business rules implementation. Hosted Transparent Decision Services (HTDS) is the standard IBM Operational Decision Manager (ODM) feature for exposing rulesets as web services. An HTDS SOAP service is inherently stateless, synchronous, and platform-independent. It uses a Web Services Definition Language (WSDL) file, which provides a strict contract for objects and constraints, fulfilling all the stated requirements. While SOAP traditionally uses XML, the mention of JSON points to the flexibility of HTDS, which also supports REST/JSON, but the core technology (HTDS) is the correct choice for this scenario.

A. Use a local EJB rule session. A local EJB session is not platform-independent; it is designed for communication within the same Java Virtual Machine (JVM), violating a primary requirement.
B. Implement an MDB with JSON format. Message-Driven Beans (MDBs) are designed for asynchronous communication, which directly contradicts the explicit requirement for synchronous calls.
D. Implement a custom SOAP web service and XML format. While technically feasible, building a custom service is not the best approach when IBM ODM provides a standard, out-of-the-box feature (HTDS) specifically for this purpose.

1. IBM Operational Decision Manager 8.10 Documentation, "Executing rules with Hosted Transparent Decision Services": "You can call a ruleset from any client application by using the hosted transparent decision service (HTDS). HTDS is a ruleset execution component that is packaged as a web application. It provides a stateless, synchronous, and platform-independent interface for ruleset execution." This source directly confirms that HTDS meets the core requirements of being stateless, synchronous, and platform-independent.

2. IBM Operational Decision Manager 8.10 Documentation, "SOAP and REST protocols" section within HTDS documentation: "HTDS supports both SOAP and REST protocols for ruleset execution... For SOAP requests, you can retrieve the Web Service Definition Language (WSDL) file from the Rule Execution Server console... The WSDL file describes the ruleset parameters and is used to generate a proxy client for your application." This confirms that HTDS provides a strict contract (WSDL) for SOAP services, ensuring enforcement of objects and constraints.

3. IBM Redbooks, "Smarter Process: Decision Management and Business Rules" (SG24-7912-01), Section 4.4.2 "Hosted transparent decision services": "HTDS is a web application that provides a stateless interface for ruleset execution... The HTDS application supports both SOAP and REST protocols for ruleset execution." This publication reinforces that HTDS is the standard stateless web service interface for ODM rulesets.