You can develop your own DB2 Web services by either creating a new application or using the samples application as follows.
Creating a new DB2 Web Services Application
You can create a new DB2 Web Services application using the WebSphere Studio development tools, such as WebSphere Development Studio Client (WDSC). Refer to Creating a DB2 Web service using WebSphere Studio for an overview of the development process.
Extending the DB2 Web Services Samples Application
You can modify the samples application to develop your own DB2 Web services by either modify the existing DADX files or adding additional DADX files to the application. This can be done without the use of development tools or redeploying the application as follows:
Location of Sample DADX Files
The existing DADX files are found in the following iSeries directories associated with the two DADX Groups, ddx_sample and dxx_travel, associated with the sample application. Both groups are located in the following directory:
/instance_root/installedApps/hostname_instance/DB2 Web Services Samples.ear/DB2Samples.war/WEB-INF/classes/groups
where instance_root is the directory of your server instance. For example,
/QIBM/UserData/WebASE/ASE5/myInstance
where hostname_instance is composed of your system host name and instance name. For example,
myHost_myInstance
Modify existing DADX Files
You can modify an existing DADX file by either adding a new DB2 Web Service operation or changing an existing operation. DADX files can be found in the group directories listed above.
Adding new DADX Files
You can define a new DB2 Web Service by adding a new DADX file to the directories mentioned above. Refer to one of the sample DADX files provided in the directory for an example. The DADX file is placed in one of the group directories listed above.
If you add a new DADX file to the samples application, dds-examples.xml must be updated with information (deployment descriptor) about the new Web service. Below is an example of the deployment descriptor for the DADX file ivt.dadx with values specific to the service highlighted. Refer to Web Services Object runtime Framework: Implementing DB2 Web Services for information about generating deployment descriptors.
<isd:service xmlns:isd='http://xml.apache.org/xml-soap/deployment'
id='http://tempuri.org/sample/ivt.dadx'>
<isd:provider type='com.ibm.etools.webservice.rt.framework.ServiceProvider'
scope='Request'
methods='testInstallation'>
<isd:java class='com.ibm.etools.webservice.rt.dxx.DxxService'/>
<isd:option key='group.name' value='/dxx_sample'/>
<isd:option key='group.path' value='/db2sample'/>
<isd:option key='group.class.name' value='com.ibm.etools.webservice.rt.dxx.DxxGroup'/>
</isd:provider>
<isd:faultListener>org.apache.soap.server.DOMFaultListener</isd:faultListener>
<isd:mappings defaultRegistryClass='com.ibm.etools.webservice.rt.dxx.DxxMappingRegistry'/>
</isd:service>