Web Services Client Resource (Magic xpi 3.x)
If you want to consume a Web service, you need to first define the Web service parameters in the Magic xpi Resource Repository. Later on, when you drag the Web Services service to the flow area, you can configure this service to work with these parameters.
You can configure your Web Services Client resource by defining the following parameters, or by searching for the service in the UDDI registry (parameters in bold are mandatory).
|
|
|
|
WSDL URL
|
The service WSDL URL or file location. For example, http://localhost/AsymEncryptPolicyService/AsymEncryptService.asmx?WSDL.
You can enter the service WSDL URL or file location manually, or you can click  to browse for the required file path. Alternatively, you can use environment variables in this parameter.
|
|
Service Endpoint URL
|
This field lets you control the service endpoint URL that the Web services step calls. For example, http://localhost/AsymEncryptPolicyService/AsymEncryptService.asmx
You can either enter the endpoint URL, or click  to open the Environment Variables List. Here, you can select an environment variable to use as an endpoint URL.
|
|
UDDI Service Key
|
The Web service's key in the UDDI registry.
|
|
UDDI Binding Key
|
The binding key for the service in the UDDI registry.
|
The Web Services Client resource also gives you the following additional buttons:
|
|
|
|
UDDI
|
Searches for a service in a UDDI registry. For more details, click here.
|
|
Configure
|
Opens the Web Services Operations dialog box. For more details, click here.
|
Note:
|
You must implement this stage to create a valid resource.
|
|
|
