Problems with Web Services (SOA)

Indication:

Running the sample client (described in section “Runtime Operations” of the Web Services manual) fails with errors of the form:

FTL(PSFPTPC002): Exception java.lang.NoClassDefFoundError in provisioning request Request for requestID request: org/apache/commons/codec/binary/Base64

Reason:

You are probably using a customized copy of the sample client of DirX Identity V8.0B, and you have updated your runtime environment with the jar files of the sample client shipped with your installation.This problem cannot occur when using the sample client as shipped with your installation and installed in install_path/provisioningServices.

Solution:

Ensure that the classpath in your runtime environment is computed so that the file commons-codec.jar is on the classpath.For details about suitable classpath computation, see DirX Identity Migration Guide, section “Manual migration”, subsection “General Aspects”, subsection “Web Services Clients”.

Indication:

Running web services on the embedded Tomcat of the Java-based Server can cause memory problems.

Reason:

Up to now, web service clients cannot be informed about low memory conditions.

Solution:

In a production environment, always run web services on a separate Tomcat installation. This strategy prevents memory problems in the Java-based Server.