Focal Point
Configuring Request Attributes -- Webservice Adapter

This topic can be found at:
http://forums.informationbuilders.com/eve/forums/a/tpc/f/1381057331/m/3091098962

February 04, 2008, 10:12 PM
Dharma
Configuring Request Attributes -- Webservice Adapter
While consuming a webservice from webfocus, is there a mechanism on webfocus to configure so that webservice request gets issued without xsd attributes to each of the element tag.
Eg: Currently after the configuration i am able to generate request as follows:

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<SOAP-ENV:Header>
<m:ServiceInputHeader xmlns:m="http://ns/messages/2003-08">
<m:ServiceName xsi:type="xsd:string">GET_NONPAS_PROSPECT_PERID</m:ServiceName>
<m:ConsumerRole xsi:type="xsd:string">1234567890</m:ConsumerRole>
<m:TimeOut xsi:type="xsd:int">120</m:TimeOut>
<m:ReturnPerfStats xsi:type="xsd:boolean">false</m:ReturnPerfStats>
<m:ServiceVersion xsi:type="xsd:string"/>
<m:SessionID xsi:type="xsd:string">0987654321</m:SessionID>
<m:CorrelationID xsi:type="xsd:string">0987654321</m:CorrelationID>
</m:ServiceInputHeader>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<m:GET_NONPAS_PROSPECT_PERID xmlns:m="http://ns/services/PAS3Services/2003-08">
<m:PROSPECT_ID xsi:type="xsd:string">P12456</m:PROSPECT_ID>
</m:GET_NONPAS_PROSPECT_PERID>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>


Now we need to turn off the xsi attributes against each of elements in soap header and body. So any direction in this regard will be of great help.


dharma
------------------
WF v 7.1.1
OS - Win XP
Output: PDF, EXL2K
April 29, 2008, 01:18 PM
Efrem
New parameters are introduced in the Access File in both the Segment and Id records:
ELEMFORM and ATTRFORM (for the SOAP Body).
HELEMFORM and HATTRFORM (for the SOAP Header).
370 WebFOCUS
Managing Web Services Metadata
A new FORM parameter is introduced in the Field record that describes the element or
attribute.
Acceptable values for the new parameters are qualified and unqualified.
The default behavior, full qualification for all elements in the Header and Body, and no
qualification for the attributes is applied when no new parameters are found in the Access
File.
See the XML Schema Part 0: Primer, which you can access at
http://www.w3.org/TR/2001/REC-xmlschema-0-20010502/#NS, for details about Advanced
Concepts: Namespaces, Schemas & Qualification.