
A Web service configuration (WS Configuration) defines the properties of the Web service at runtime. One or more Web service configurations are assigned to a Web service.
Whenever you generate a client proxy for the Web service, a logical port is generated for each Web service configuration (see: Configure Logical Ports ).
The Web service configurator knows the system landscape and the technical requirements of the application server where the Web service is to be called. In the configuration editor, he or she assigns attributes to features selected in the WSD.
You have created a VI and a WSD.
The transport binding is the same for all configurations of a Web service. Only when you create the first configuration do you have the option of choosing a SOAP or HTTP binding.
| Subnode: | Notes: |
|---|---|
|
Overview |
The URL suffix in the Path field is set automatically. You can change the relative path specification, if required. The system displays information on the WSD and the EJB that are the basis for the Web service configuration. |
|
Security |
Choose the required Authentication Type for the Web service. Only options that do not conflict with the authentication defined already in the WSD are allowed. (See also Creating a Web Service Definition .) If the Authorization option was selected at design time, roles are assigned for the operations of the Web service. You can change the assignment by choosing Use Authorization (see also: Web Services Security ). |
|
Advanced |
You can enter the WSDL port name, the WSDL binding name and the address of the target server. |
Publish the Web service in the UDDI. For more information, see Publishing a Web Service as a Business Service .
You have defined the runtime properties of the Web service, deployed it, and published it in the UDDI if appropriate. The Web service is available for proxy generation on the client side.