Changing target namespaces
When you generate the WSDL of a SOAP hosted transparent decision service (HTDS) or the
WADL of a REST transparent decision service, you can change the namespace of the transparent
decision service to avoid naming conflicts when more than one description file is generated at the
same location.
About this task
When more than one description file is generated at the same location, naming conflicts can arise
because the parameters might not be the same for different transparent decision services. Such is
the case, for example, when more than one transparent decision service are added to a business
integration project in IBM® Integration Designer. To avoid such
conflicts, the URI for transparent decision service requests and responses, and their parameters,
includes the ruleset name. The following example the URL for a ruleset named
PreTradeChecks.
<wsdl:definitions name="PreTradeChecksDecisionService"
targetNamespace="http://www.ibm.com/rules/decisionservice/Execution/PreTradeChecks"
...
The schema importation mechanism references schema components from other schema
documents.
...
<xsd:import namespace="http://www.ibm.com/rules/decisionservice/Execution/PreTradeChecks/param"/
...The names of decision requests and responses are prefixed with the RuleApp name. For example:
<xsd:element name="PreTradeChecksRequest
...
xsd:element name="PreTradeChecksResponse"
The value of the target namespace must be an absolute URI. To ensure the uniqueness of the target namespace, you can change the definition of this attribute in the Ruleset Parameters section of the ruleset view.