The Sonic Web Service client type generates deployment information for a Sonic Web Service definition.
Note: You can also change the deployment settings for this client type during deployment to a Sonic ESB container.
Client Details for the Sonic Web Service client type displays the following deployment settings:
Namespace — In this field, enter a value for the Sonic Web Service target namespace. This value is required for all SOAP-based applications. It must be unique for the service. The default is urn:tempuri-org.
Note: The Namespace field for the Sonic Web Service client type and the Namespace field for the 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.
WSDL Style — The encoding style of the binding. Select one of the following options:
Doc/Literal — Specify this option if you want the entire message to be defined as a single entity and you want the generating of the messages represented literally using XML schema standards. This is the default as it is the recommended encoding style.
RPC/Literal — Specify this option if you want each parameter to be defined as a separate entity and you want the formatting of the messages represented literally using XML schema standards.
RPC/Encoded — Specify this option if you want each parameter to be defined as a separate entity and the formatting of the messages to be encoded according to a set of encoding rules. This option is not recommended. Although this option is allowed, the message cannot be validated since not all of the SOAP body is defined by XML schema.
Entry Endpoint — The Sonic ESB endpoint name for invoking the service. The endpoint is an abstract name with an underlying query or topic. If the endpoint does not exist, ProxyGen creates it. You must create the underlying queue in Sonic for this to work properly. The default is .Entry appended to the AppObject name (for example, MyAppObj.Entry). Uncheck the Use Default option to specify a different name.
Reject Endpoint — The Sonic ESB endpoint name for rejected messages sent to the service. The endpoint is an abstract name with an underlying query or topic. If the endpoint does not exist, ProxyGen creates it. You must create the underlying queue in Sonic for this to work properly. The default is .Reject appended to the AppObject name (for example, MyAppObj.Reject). Uncheck the Use Default option to specify a different name.
Fault Endpoint — The Sonic ESB endpoint name for faults returned from the service. The endpoint is an abstract name with an underlying query or topic. If the endpoint does not exist, ProxyGen creates it. You must create the underlying queue in Sonic for this to work properly. The default is .Fault appended to the AppObject name (for example, MyAppObj.Fault). Uncheck the Use Default option to specify a different name.
Container Name — The name of the Sonic ESB container in which to deploy the service. ProxyGen does not create the container if it does not exist. The default is the Sonic ESB container created when you install the OpenEdge Adapter for Sonic ESB. However, there is no initial value for this field.
AppServer URL — The URL of the AppServer to connect the Sonic ESB container to. The default is the esbbroker1 session-free AppServer installed with OpenEdge by default. The initial value of this field is AppServerDC://localhost:3091.
Sonic ESB Service — These options specify the location of files for the ESB:
Filename — The base filename for the WSM and WSDL files. This is the same name as the AppObject.
Overwrite Files — Check this option if you want to overwrite existing WSM and WSDL files in SonicFS. If you leave this option unchecked and the files already exist in SonicFS, ProxyGen does not deploy the Sonic Web Service and generates a message stating that deployment did not proceed.
Resource Dir — The path in SonicFS where you want to store the WSM and WSDL files.
Advanced — Click this button to access the Advanced Sonic ESB Options dialog box which allows you to specify settings for the Sonic Domain Manager where the Sonic Web service is to be deployed. For a detailed description, see the Advanced Sonic ESB Options dialog box.
Namespace — In this field, enter a value for the Sonic Web Service target namespace. This value is required for all SOAP-based applications. It must be unique for the service. The default is urn:tempuri-org.
