Example Options for the SOAP Transformation
|
|
|
OptionsInput File
|
Specify the SAS fileref
associated with request XML file (IN):
|
|
|
Note: RECFM=V specifies that the
input file is in variable format. LRECL=5000 specifies the logical
record length for the input file in bytes.
|
Will the SOAP Request
XML be contained in one file?
|
|
Specify an existing
file that contains the SOAP request XML:
|
C:\SOAPFiles\WeatherGovRequestXML.xml
|
OptionsOutput File
|
Specify the SAS fileref
associated with response XML file (OUT):
|
|
Specify complete path
and filename of response XML file
|
C:\SOAPFiles\SOAPSoapActionOutputFile.xml
|
|
Note: RECFM=V specifies that the
output file is in variable format. LRECL=5000 specifies the logical
record length for the output file in bytes.
|
OptionsAdditional Required Aurguments
|
Will the call be made
to a SAS registered Web service?
|
Note: One example of a SAS registered
service is a SAS Data Integration Studio job that has been deployed
as a web service.
|
Specify the URL of the Web
service endpoint to be called:
|
http://graphical.weather.gov/xml/SOAP_server/ndfdXMLserver.php
|
OptionsSOAP Optionssection
|
Specify an output log
file used for debugging purposes (DEBUG):
|
C:\SOAPFiles\SOAPSoapActionDebug.txt
Note: Includes debugging statements
from the mprint option set.
|
Specify a defined SOAP
action (SOAPACTION):
|
http://graphical.weather.gov/xml/DWMLgen/wsdl/ndfdXML.wsdl#LatLonListZipCode
|
Specify the mustUnderstand
attribute in the SOAP header (MUSTUNDERSTAND):
|
|
OptionsSecurity
|
Will Web authentication
be used?
|
|
Will WS-Security Web
services be used?
|
|
Will an HTTP proxy server
be used?
|
|
Specify the HTTP Proxy
Server Host Name (PROXYHOST):
|
|
Specify the HTTP Proxy
Server Port (PROXYPORT):
|
|
OptionsProperties
|
Is a SOAP envelope to
be included in the XML response?
|
|
OptionsAdditional Options
|
|
Note: Specifies that SAS statements
generated by macro execution are traced for debugging.
|