Try OpenEdge Now
skip to main content
Open Client Introduction and Programming
Generating Proxies and Web Service Definitions : Specifying generation settings : Web Service client details

Web Service client details

The Web Service client type generates deployment information for an OpenEdge Web service definition.
Note: You can also change the deployment settings for this client type during deployment to a OpenEdge Web Services Adapter (WSA).
Client Details for the Web Service client type displays the following deployment settings:
*Namespace — In this field, enter a value for the Web service target namespace. This value is typically used to version the Web service in any WSDL that you generate. You can specify any value that meets the following requirements:
*Uniquely identifies the Web service and its elements in the WSDL file
*Uniquely identifies the Web service for the WSA instance where it is deployed
*Meets the requirements of an XML namespace value (a valid URN or URL)
For example:
For more information on using the target namespace for Web service versioning, see the sections on versioning Web services in OpenEdge Application Server: Administration.
Note: The Namespace field for the Web Service client type and the Namespace field for the Sonic Web Service client type are linked. If you change the Namespace setting for one client type, it is automatically updated for the other client type.
*Generate Test WSDL — If you check this box, ProxyGen generates a WSDL file with the specified style/use (See the WSDL Style radio buttons).
*URL for WSA — In this field, enter the URL of the Web services adapter instance to which this Web service is deployed. This value can be modified at deployment time. For more information on this URL, see the sections on Web services administration in OpenEdge Development: Web Services.
*SOAP Action — These radio buttons specify how you want the string value for the SOAP Action Header to appear in the WSDL file for each SOAP message: Blank or User-defined (any value you enter, including blank).
If you select both User-defined and the Append Object Name check box, the name of the Web service object is appended to the value you enter, to form the SOAP Action Header value.
*WSDL Style — These radio buttons specify the format for SOAP messages supported by the Web service. The selected style/use must match the SOAP format supported by the client applications you intend to support.
Style refers to the communications style. Some applications communicate by exchanging messages as remote procedure calls (RPCs), while others communicate by exchanging messages as XML documents.
Use refers to the syntax or format of each message itself. The formatting of the messages can be encoded according to a set of encoding rules or represented literally using XML schema standards.
Select one of the following style/use combinations:
*Document/Literal — This option is the default because the entire SOAP message is defined in a single entity.
*RPC/Literal — This option defines the entire SOAP message in a single entity and formats the message literally using XML schema standards.
*RPC/Encoded — This option is not recommended. Although this option is legal for Web Services, it is not WS-I compliant, because the message cannot be validated since not all of the SOAP body is defined by XML schema.
For more information on the WSDL style and use attributes and how they affect Web service client communications, see OpenEdge Development: Web Services.
Note: To deploy the Web service to the Web Services Adapter (WSA) with multiple SOAP encoding styles, you must either generate the Web service with a unique Namespace value (different version) for each SOAP encoding style or you must deploy the Web service with each SOAP encoding style to a different WSA instance. For more information on the WSA and how to deploy Web services to it, see the OpenEdge Management or OpenEdge Explorer online help.
Caution: >A single deployed Web service can support a single SOAP encoding style. To support multiple encoding styles, change the output directory ( field described in the Output Directory) to avoid overwriting any WSDL file already generated for this Web service.
*Suffix — These options specify the content and formatting of the generated WSM file and optional test WSDL file (See the Generate Test WSDL check box):
*PortType/Binding — In this field, enter a custom suffix for the PortType and Binding name in the WSDL file. If you check the Use Default box, this field is disabled and displays the default value for the suffix (Obj).
*Web Service — In this field, enter a custom suffix for the Service name in the WSDL file. If you check the Use Default box, this field is disabled and displays the default value for the suffix (Service).