skip to main content
Corticon Server: Integration & Deployment Guide : Service contract examples : Examples of XSD and WSDLS available in the Deployment Console : Decision-service-level XML schema, FLAT XML messaging style

Try Corticon Now
Decision-service-level XML schema, FLAT XML messaging style
When Decision Service is selected in input option 1 of Deployment Console: Service Contract Specifications, the XML Messaging Style input option 4 becomes inactive (grayed out). This occurs because the XML Messaging Style option at the Decision Service level, (input property 13 of Deployment Console: Decision Service Deployment Properties) becomes the governing setting.
As many sections are identical from one type to another, the following links connect to the relevant sections in Vocabulary-level XML schema, FLAT XML messaging style, with variances noted:
*CorticonRequestType and CorticonResponseType - This section of the XSD is identical to the Vocabulary-level FLAT version with the exception of the following lines in each complexType:
<xsd:attribute name=decisionServiceName use=required
fixed=DecisionServiceName type=xsd:string />
Notice that the name of the Decision Service you entered in section 2 of Left Portion of Deployment Console, with Deployment Descriptor File Options Numbered is automatically inserted in fixed=DecisionServiceName.
*WorkDocumentsType - One line in this section differs from the FLAT version. This attribute value indicates the HIER XML Messaging Style selected in the Deployment Console:
<xsd:attribute name=messageType fixed=HIER use=optional />
*VocabularyEntityNameType and VocabularyAttributeNameTypes - The structure of this section of the XSD is identical to the Vocabulary-level FLAT version. However, a Decision-Service-level service contract will contain only those entities and attributes from the Vocabulary that are actually used by the rules in the Decision Service. This means that a Decision-Service-level contract will typically contain a subset of the entities and attributes contained in the Vocabulary-level service contract.