Understanding Using Project Copy and Exported WSDL and WADL

When you generate WSDL or WADL for a service operation, the system sets an internal flag on the service operation that indicates that WSDL/WADL has been generated or exported for the specific service operation.

The system uses the same repository for WSDL and WADL documents. The WSDL metadata object is used for project copy of WSDL and WADL. There is no WADL metadata object only WSDL.

You may later decided to use Project Copy to copy the service operation to a new database. But you may decide not to or simply neglect to copy the exported WSDL or WADL to the new database.

Even though you have not copied the WSDL/WADL to the new database, the internal flag that says WSDL/WADL has been generated is still set on the service operation. As a result, the system expects WSDL/WADL to exist in the new database, when it does not. When this condition exists, the system displays a status message on the message definition(s) of messages referenced in the service operation.

When this condition exists, the options are:

• Clear the internal WSDL/WADL exported flag on the service operation.

  Information about how to perform this task is discussed in this section.

• Use Project Copy to copy the WSDL/WADL to the new database.

  See Lifecycle Management Guide: Copying Projects.

• Regenerate the WSDL/WADL on the new database using the Provide Web Service wizard.

  See Providing Non-REST Web Services, Providing REST Web Services, and Providing OpenAPI REST Web Services.