Web Service Application

In the Web-based modeler, the web services are invoked using the JAX-WS 2.0 library.

In case you import a model from Eclipse-based modeler which contains the classes generated through Axis 1.2 in web service application, then the engine won't be able to execute the model.

Viewing and Editing Properties
- Configuration
- Comments

Viewing and Editing Properties

Following properties should be specified:

Figure: Web Service Application - Configuration

UUID - A unique identifier ID gets generated as an identifier for client server communication
ID - An ID generated automatically based on the application name. If element with the same name exists then during ID generation, a numerical suffix gets added to the ID. If the element is renamed, the ID gets regenerated.

The UUID and ID options are displayed only when you switch to Integrator profile.

Application Name - Specify name of the application
Description - Specify the description
Public Visibility - By default, this check box is selected. It indicates that the element is visible and available for reference from any other model.

Configuration

WSDL URL - Specify location of the Web Service WSDL and click Load. The URL must have the following format:
```
<protocol>:<path>/<document>
```
You can also specify the path of WSDL URL from local file system. In case of file, the URL should be, for example,
```
file:/development/assets/TestService.wsdl.
```
On Windows, if the document is not on the default device C but on device Y, you can use the format:
```
file:/Y/path-on-Y/document.wsdl
```
When you Load a WSDL, first Service, Port and Operation are automatically selected and displayed. As an effect structured data types for the selected operation are created.
Service - Service to be invoked from the services listed in the previously loaded WSDL specification.

Figure: Web Service Application - Endpoint

Port - Selects the port to be invoked from the ports provided by the previously selected service.
Operation - Selects the operation to be invoked from all operations provided by the previously selected port. Note that Structured Types will be created implicitly with the definition of the Web Service Application Type, but only SDTs required for the selected Operation will be created. Creating SDTs via manual import of WSDLs is not supported.
Style - Displays the encoding style used for the chosen operation.
Protocol - Displays the protocol used for the chosen operation.
Use - Displays the message used for the chosen operation.
Include WS Addressing EPR - Specifies that at runtime a WS-Addressing Endpoint Reference will be included into the request message.
- Implementation - Specifies the implementation (Generic Resource / Process Manager Specific) of the above WS-Addressing endpoint.
Authentication Required - Specifies whether at runtime any standard caller authentication information is included into the request message.
- Mechanism - Specifies the authentication mechanism (WS-Security / HTTP Basic Authentication).
- Variant - Specifies the WS-Security variant (Username / Password or Username / Password Digest).
Endpoint - If you select the Dynamically Bound Services option from the Service drop-down list, then the Endpoint option is displayed. You can specify the endpoint for the web service. It means that the URL in WSDL file can be different and at the runtime, the user can change the URL. The dynamically bound service provides an extra access point where you can specify at runtime the concrete endpoint.

Comments

Click the Comments tab to add comments for the application. To add the comment, specify the comment in the text box and click Submit. The newest comment gets displayed at the top of the table. To delete the comment, select the comment and click the Delete icon. The user, who has submitted the comment, only that user can delete the comment. If the other user selects the comment or no comment is selected, the Delete icon remains in disabled state.

Figure: Comments