![]() |
|
![]() ![]() ![]() |
Working with Web Services > Viewing or Editing a Web Service Operation File |
|
![]() |
Viewing or Editing a Web Service Operation File |
The Web service Operation File Editor is used to view or edit the Web service operation file. Using the file editor, you can:
Open the Web service Operation File Editor using one of the following methods:
Once open, the Web service Operation File Editor displays the following information about the Web service operation file.
View the information, or edit the following fields, if desired.
Displays the name of the Web service as defined in the WSDL file. | |
Displays which service, or operation, within the Web service this operation uses. The name of this operation is as defined in the WSDL file. | |
Displays one of the following values:
See the W3C Web Services Description Language (WSDL) 1.1 specification. | |
Displays one of the following values:
See the W3C Web Services Description Language (WSDL) 1.1 specification. | |
Displays the name of Java beans package that Dialog Designer uses to implement the Web service. | |
Displays the URL to the location where the Web service resides. | |
Displays the endpoint used to invoke the Web service. The required endpoint for the Web service is available within the WSDL file for the Web service. Note: When deploying the application, this endpoint can be changed to another endpoint, in Configure Web Application Descriptor. This change might be useful, for example, if you have been using a pared-down version of the Web service while developing and testing your application. In this case, you might want to use a different, official version of the Web service with the deployed application. | |
When generating the security token to include in the SOAP message for the Web service request, the password can either be sent as a hash (#), or in the clear. When interfacing to .Net Web services over a secure link, it can be beneficial to not hash the password, since WSS4J and .Net use different hash schemes. | |
Sets the HTTP socket timeout, in seconds, to be used when executing the Web service operation. | |
The URL of the WSDL file for the Web service in standard HTTP or HTTPS format. All Web services has an associated WSDL file that describes what services the Web service provides. Dialog Designer uses this WSDL information to populate the Operation field list. Note: Dialog Designer supports only WSDL files that contain unique method signatures. Note: Dialog Designer does not support operation overloading, or the use of methods with the same name but different parameters. Tip: If a Web service has been previously created, Dialog Designer remembers the URL. For future Web service creations, Dialog Designer automatically populates this field with the URL. Dialog Designer keeps track of the last 20 Web services URLs used in operations. | |
The parameters configured when the Web service was created is displayed, but this can be changed, if desired. Using these fields, variables can be remapped after a Web service operation file is initially created. This is useful for when custom variables are created after creating a Web service operation file. See Mapping Input & Output Parameters (Wizard Page 2 & 3) for more information. | |
The parameters configured when the Web service was created is displayed, but this can be changed, if desired. Using these fields, variables can be remapped after a Web service operation file is initially created. This is useful for when custom variables are created after creating a Web service operation file. See Mapping Input & Output Parameters (Wizard Page 2 & 3) for more information. | |
Indicates how Dialog Designer should authenticate with the Web service host. The authentication configured when the Web service was created is displayed, but this can be changed, if desired. Options are:
| |
. .Identifies the name of the header as expected or returned by the web server. | |
Lets you select the variable (and field if its a complex variable) that contains the data that will be sent in the HTTP request, or the variable that will receive the header value that is returned. | |
Lets you specify if the header is sent (Out), received (In) or sent and received (InOut). |
![]() ![]() ![]() |
©2009, Avaya Inc. All rights reserved.
|