Problem Summary: On the Solaris, HP-UX, and Windows platforms, an attempt to use the WSDL cataloger on a zip file fails if the JVM property java.io.tmpdir is set to a value that ends with a forward slash (/). The symptom of the failure is a CatalogingException with a message that states that the cataloger could not find one of the files in the request.
This problem does not occur on Linux, where the default setting of java.io.tmpdir does not end with a forward slash.
Workaround: Change the value of java.io.tmpdir so that it does not end with a forward slash.
Perform the following steps:
Log in to the Application Server Admin Console as described in To Use the Application Server Admin Console in Service Registry 3.1 Administration Guide.
Expand the Configurations node.
Expand the server node, server-config (Admin Config).
Click JVM Settings.
Click the JVM Options tab.
Click Add JVM Option.
In the text field, type the following (all on one line):
On Solaris OS and HP-UX: -Djava.io.tmpdir=/var/tmp
On Windows: -Djava.io.tmpdir=c:\DOCUME~1\ADMINI~1\LOCALS~1\Temp
Follow the instructions in To Stop and Restart the Application Server Domain for the Registry in Service Registry 3.1 Administration Guide.
After performing these steps, you should be able to publish a zip file that contains multiple WSDL files.