Configuring a web service endpoint

You can configure the endpoint of a SOAP or REST decision web service, typically to point to a proxy URL rather than to the computer that generates the WSDL or WADL file.

About this task

If you use a load balancer or proxy, you can configure the web service to point to the proxy URL rather than to the computer that generates the WSDL or WADL file. A web service specifies a single interface that the service supports, and a list of endpoint locations where that service can be accessed. To direct the messages through another endpoint, you must rewrite the endpoint URL of the service. After you have changed the web service endpoint, you can execute the service without reliance on the computer that generated the WSDL or WADL file.

You can change the web service endpoint in two ways:

You can use the Rule Execution Server console as explained in this procedure.
You can also use an API to overwrite the URL of the web service to call in the generated stub. For example, in Axis (see the Apache Axis page at http://axis.apache.org/axis/index.html), a ServiceLocator class is available in the web service client classes that are generated with Rule Designer. The ServiceLocator class defines the getExecutionPreTradeChecksPort method, which takes a URL as a parameter. The name of this class depends on the name of the ruleset. For example:
```
PreTradeChecksDecisionService_PortType pt = locator.getExecutionPreTradeChecksPort (URL);
```

Procedure

To configure a web service endpoint in the Rule Execution Server console:

Start your application server (or the sample server), open the Rule Execution Server console, and sign in to it.
Click the Explorer tab, expand the RuleApp that you want, and select a ruleset to open the Ruleset View.
At the bottom of the Ruleset View, click Show HTDS Options.
To the side of the Web service endpoint URL, click the Edit icon.
Type the custom URL in the field and click the Save icon. This URL specifies the physical address at which the service can be accessed. You can cancel by clicking the Undo arrow next to the Save icon.

Results

If, for a SOAP web service, you select 7.0, 7.1, or 7.1.1.3 as the Compatibility mode in the generation options, the version number is appended to the endpoint and automatically saved in the generated WSDL file. For example: <soap:address location="http://localhost:9080/DecisionService/ws/execution/1.0/PreTradeChecks/1.0/v70"/>

Restriction: In Operational Decision Manager 8.5, no compatibility options are available for WADL generation.