Developing Web services with the workbench

Developing Web services involves creating and adding operations to them, optionally configuring XSL transformations of the request messages and result messages for your operations, and deploying the Web services to Web servers for testing.

1. Configuring the workbench for developing and deploying Web services
   Before you can develop Web services, create a data development project and associate that project with a supported database.

2. Optional: Selecting the default deployment options for all Web services in a project
   You can specify how to deploy all of the Web services within a data development project.

3. Optional: Adding parameters to Web services
   You can add to Web services parameters that set optional properties within a supported database that a Web service performs operations against and optional properties of the connections between the Web service and the database. You can add these parameters by default to the Web services that you create within a data development project, or you can add them when deploying individual Web services.

4. Creating Web services
   When you create a Web service, you create an empty container that you subsequently add database operations to.

5. Adding database operations to Web services
   To add SQL operations to Web services, you can create new SQL scripts in the

   New Operation window or drag and drop existing scripts that are in a data development project onto a Web service. To add calls to stored procedures, you can also drag and drop stored procedures from the database where they are deployed onto a Web service.

6. Editing Web services
   You can change the name of a Web service and the namespace URI that is associated with the Web service. You can use the namespace URI to group together Web services that have similar functions, have one owner, or access the same data source.

7. Editing operations
   You can change the names of the operations that belong to a Web service. If an operation is based on an SQL statement, you can edit the statement. If the operation calls a stored procedure and meets certain criteria, you can generate a detailed XML schema for the operation.

8. Optional: Sharing Web services with members of your development team
   Other members of your team might be responsible for testing and deploying the Web services that you create. You can export the Web services into a compressed file and send this file to those team members. They can import the services from the file into a data development project in their own workspaces.

9. Optional: Customizing messages that client applications send to and receive from Web services
   You can customize the XML tagging of the messages that client applications send to and receive from Web services.

10. Configuring Web servers to run Web services
    The supported Web servers that you want to deploy Web services to must be configured before you can deploy Web services.

11. Adding Web servers to and removing them from the Servers view
    If you want the workbench to deploy Web services to Web servers for you, add those Web servers to the

    Servers view.

 

Related concepts

Support for the DB2 native XML data type in Web service operations

 

Related tasks

Deploying, undeploying, and testing Web services

Migrating Web applications that were developed for the Web Object Runtime Framework (WORF)

Adding operations that are based on SQL scripts

Adding operations that are based on calls to stored procedures

 

Related reference

Supported Web servers, SOAP engines, and databases

Supported message protocols

Mapping of SQL and JDBC data types to XML data types

---