Creating a Web Service Definition  

Use

The Web service definition (WSD) includes:

●     Selection of features

●     Publication of the WSD in the UDDI as a tModel

●     Specification of the path prefix in the Internet Communication Framework

Features such as the communication type, authentication level, or transport properties are assigned in an abstract form. The technical details are defined when the Web service is released for the SOAP runtime.

By assigning these abstract features, you ensure that a WSD can be used for various application servers that have different technical features. The proxy generation on the client side refers to the WSD. Technical details that are predefined in the Web service configuration are configured separately in the WS client runtime.  

Prerequisites

You have created a VI.

Procedure

To create a WSD, proceed as follows:

...

       1.      In the Object Navigator (SE80), choose the package to which you want to assign the Web service.

       2.      Position the cursor on the name of the package. From the context menu, choose Create ® Enterprise Services / Web Services  ® Web Service Definition.

       3.      In the dialog box that appears, enter the required data.

 

       4.      Choose Create. In the Properties tab, the path prefix in the ICF, the name of the WSD, and the VI on which it is based, are displayed.

       5.      Choose the Features tab.

The selection options in the lower section of the screen refer to the features selected in the upper section. The following options are available:

 

Feature:	Selection:	Meaning:
Session-oriented communication	Choose Select Feature.	Choose this feature if communication is to be stateful.
Authentication	Choose one of the following options: ·         No Authentication ·         Basic (user/password) ·         Strong (incl. certificates)	Choose Basic (user/password) if calling a Web service on the client side requires the authentication of the caller with the help of a user ID and a password. Choose Strong if authentication is to be performed using the Secure-Socket Layer (SSL) protocol and X.509 client certificates.
Transport guarantee	Choose one of the following options: ·         None ·         Integrity + Confidentiality	Choose Integrity + Confidentiality if data that is to be passed from Web service clients to the server through SOAP requests is to be encrypted. The SSL then encrypts the data.

Publish the Web service definition in the UDDI as a tModel. Choose the Publish pushbutton on the UDDI tab. To access the UDDI Registry, enter a UDDI Registry, a user name, and a password in the dialog box that appears. (See also Maintaining UDDI Registries.) You need only enter a user and password if you have not entered a default user when setting up the UDDI Registry. The UDDI Registry returns the tModel key of the registered WSD and copies it to the WSD.

When you select Change, the browser for the UDDI client appears. In the Service Definition Details tab, the URL under which the WSDL document for the WSD is stored is displayed.

       6.      Save and activate the WSD.

Result

You have created and published a WSD. This WSD is displayed in the Object Navigator under the Enterprise Services node.

Next step:

Releasing a WSD for the SOAP Runtime

See also:

Using the Secure Sockets Layer Protocol

Using X.509 Client Certificates