Invoke Web Service Lite (Magic xpa 3.x)
The Invoke Web Service Lite operation lets you call a Web Service directly.
The Invoke Web Service operation is based on the Systinet Server Java (SSJ) product. This integration has many advantages, such as WS-security. However, Java and SSJ must always be installed, even on the client side. If you do not need the functionalities of SSJ and want to avoid unnecessary installations, then you can use the Invoke Web Service Lite operation.
The cached files will be stored in the SOAPLITE folder under the folder defined in the SOAP Client Modules Path environment setting.
The timeout for the retrieval phase is defined in the HTTP Timeout environment setting in the Magic.ini file.
|
Note:
|
A Magic xpa array cannot be automatically converted into a complex type of an Invoke Web Service, nor can it be returned as a complex type when Magic xpa serves as a Web service provider.
|
When you select the Invoke Web S Lite operation, you can use the WSDL Assistor to create a new service or select a service that has been defined in the Service repository as a SOAP Lite service type. Double-click on the cell to the right of Web S Lite or press F5 to open the Web Service dialog box with the following properties:
|
|
|
|
Service
|
You can select the Web Service defined as a SOAP Lite service type; for example, Airport Temperature. You can zoom from the Service field to display the Web Service list.
|
|
Soap Action
|
Magic xpa displays the request identifier specified in the Web Service Provider’s Web Service Description Language (WSDL).
|
|
Style
|
You can select either the Remote Process Call or Document, as described below.
-
Remote Process Call – Magic xpa sends arguments to the remote Web Service according to the argument types defined in the calling task. A developer must send matching arguments according to the types defined by the Web Service provider.
-
Document – Magic xpa sends one argument as an outgoing XML document and receives one incoming XML document as the returned value of the call. A developer must generate these documents according to accepted XML schemas as described in the Web Service Provider’s WSDL.
|
|
Input XSD
|
Displays the file location of the Input XML Schema, a local copy of the schema from the WSDL. This is relevant only for Document style.
|
|
Output XSD
|
Displays the file location of the Output XML Schema, a local copy of the schema from the WSDL. This is relevant only for Document style.
|
|
Operation
|
Enter the method name as defined in the WSDL of the Web Service Provider; for example, getTemperature. This field is for Remote Process Calls.
|
|
Name Space
|
A unique identifier for the service as defined in the WSDL; for example, capeconnect:AirportWeather:com.capeclear.weath. This field is for Remote Process Calls.
|
|
Return Value
|
Enter a variable to receive the response returned from the Web Service. If you have selected a Web Service operation from the WSDL Assist dialog box, the data type appears next to the Return Value field.
|
|
Completed Successfully
|
Enter a boolean variable that indicates whether the Web Service is completed.
|
|
Fault
|
Enter a fault string that is returned when the Web Service fails.
|
|
Assist button
|
You can click the Assist button to open the WSDL Assist dialog box.
|
Note: Alphanumeric attributes for arguments, return value and fault will allow for Blobs with content=Ansi or Unicode. Blobs with content=binary will default to Unicode, that is, outgoing arguments will be assumed to be Unicode and incoming byref arguments/return-value will be saved as Unicode.
The Web Service properties (Alt+Enter) are:
Condition
Service
Operation
Arguments
Return Value
Fault
The Online and Rich Client Samples projects (program CN17 and RCN17)
