In order to bring you the best possible user experience, this site uses Javascript. If you are seeing this message, it is likely that the Javascript option in your browser is disabled. For optimal viewing of this site, please ensure that Javascript is enabled for your browser.
Login  |   Cloud ERP  |   Home  |   qad.com




QDoc Requests Without SOAP Headers
In most common implementation scenarios, you configure QXI to process QDoc requests from external applications with appropriate information contained in the SOAP header. However, you can also choose not to include the SOAP header in QDoc requests from external applications that do not natively support Web services that leverage SOAP headers, such as QAD BPM. In that case, you can move the values in the original SOAP header to the session context (dsSessionContext) part in the SOAP body.
The affected SOAP headers include:
Action
To
MessageID
RelatesTo
ReferenceParameters/suppressResponseDetail
ReplyTo/Address
These headers should be added to ddSessionContext as in the following, taking header To as an example:
<qcom:propertyQualifier>QAD</qcom:propertyQualifier>
<qcom:propertyName>To</qcom:propertyName>
<qcom:propertyValue>QADERP</qcom:propertyValue>
For SOAP header ReferenceParameters/suppressResponseDetail and ReplyTo/Address, use suppressResponseDetail and ReplyTo respectively as the property name as in the following:
<qcom:propertyQualifier>QAD</qcom:propertyQualifier>
<qcom:propertyName>suppressResponseDetail</qcom:propertyName>
<qcom:propertyValue>false</qcom:propertyValue>
You must follow these rules:
When the SOAP header includes data, the receiver (the To element) and the sender (the ReplyTo element) must be specified in the SOAP header.
When the SOAP header is empty, the receiver (the To element) must be supplied in the session context (dsSessionContext).
If the data is provided in both the SOAP header and section context, then the values in the SOAP header take precedence.