Limitations of DADX Web services

The following are limitations of DADX Web services, or problems that you may encounter while creating a DADX Web service.

DADX Web services

The following restriction applies when generating a WSDL document from a DADX file:When creating a DADX web service, occasionally the message "IWAB0177E Error generating WSDL from a DADX file." will appear. In most cases this message is an indication of some database related problem and the server console log should be consulted for details on the problem. Also, check the following:

In a DADX group you can specify a JDBC net driver. For DB2® the net driver class is COM.ibm.db2.jdbc.net.DB2Driver. For earlier versions of DB2, db2java.zip needed to be added to the server classpath, and this zip file contains the driver. However, with DB2 version 8.1 and later, the file db2jcc.jar also needs to be added to the server classpath. The file is usually located in the same directory as the db2java.zip file. Ensure that The DB2 client level on your machine is at the same fixpack level as the DB2 server that you are connecting to.

Multiple outputs in DADX Web services: Normally, multiple outputs in a Web service is not supported by our tools. However, in the case of DADX Web services, multiple outputs are allowed if the Use Document Style group property is set to true. In this case, when document style is true, multiple outputs are combined together into a single XML document.

DADX generation support: Although user defined functions are listed in the Generate DADX wizard, there is currently no support for generating DADX from user defined functions. Support is only available for DADX generation from DAD files, stored procedures and SQL statements. Selecting a UDF will cause a simple DADX skeleton file to be generated.

Setting up a DADX group with datasource information:If the WebSphere® Application Server is being used to host a DADX Web service and the DADX group is configured to access the database via a datasource, then the group.properties file for the DADX group should use the following initialContextFactory property: initialContextFactory=com.ibm.websphere.naming.WsnInitialContextFactory

Also, the web.xml file for the project containing the DADX group needs to have the following added. (Given that the datasource JNDI name is jdbc/hospital.)
<resource-ref id="ResourceRef_1058550453092">
<res-ref-name>jdbc/hospital</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>CONTAINER</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>

Feedback