Refresh a web service descriptor only if you are familiar with the original WSDL document, the changes in the updated WSDL document, and the web service descriptor. Designer does not provide a list of changes to the web service descriptor as part of the refresh. You will need to use your knowledge of the WSDL document changes and the web service descriptor to ensure that operations, services, pipeline mapping, and other aspects of the web service descriptor work as expected.

During refresh, mappings between variables might break or be lost. This is particularly true when the web service descriptor has manually added headers or faults and the updated WSDL document has new headers or faults of the same name.

During refresh of a consumer web service descriptor, Integration Server deletes and recreates the contents of the consumerWSDName_. This includes all of the document types, Integration Server schemas and web service connectors generated from the original WSDL document. Any changes made to these elements will be lost. For web service connectors, this includes maps (links) between variables in the pipeline, variables added to the pipeline, variables dropped from the pipeline, and values assigned to pipeline variables.

During refresh of a WSDL first provider web service descriptor, Integration Server deletes and recreates the contents of the docTypes folder. Changes made to the IS document types and IS schemas generated from the original WSDL document will be lost.

Because Integration Server deletes and recreates the contents of the consumerWSDName_ folder, docTypes folder, connectors folder, and services folder during refresh, do not place any custom elements in these folders. These folders are reserved for elements created by Integration Server for the web service descriptor only. Before refreshing a web service descriptor, remove any custom elements from these folders.

If you used an IS element created by Integration Server for the web service descriptor with another IS element that is not associated with the web service descriptor, refreshing the web service descriptor might break the other usages of the IS element. For example, suppose that you used an IS document type created for an input message as the input signature of a service not used as an operation in the web service descriptor. If the input messages is removed from the updated WSDL document upon refresh, the other service will have a broken reference. The service will reference a document type that no longer exists.

If you refresh a WSDL first provider web service descriptor for which web service clients have already been created, the web service clients will need to be recreated. Consumers will need to recreate their web service client using the new WSDL document that Integration Server generates for the provider web service descriptor.

During refresh, Integration Server regenerates the web service descriptor using the functionality and features available in the Integration Server version on which the web service descriptor was originally created. After refreshing the web service descriptor, the Created on version property value is the same version of Integration Server as before the refresh. Refreshing a web service descriptor on the latest version of Integration Server does not update the web service descriptor to include all the web service features and functionality available in the current version of Integration Server. If you want the web service descriptor to use the features available with the current version of Integration Server, delete the web service descriptor and recreate it using Designer and the current version of Integration Server.

If you are using the local service development feature, using versions of Subversion prior to 1.7 as your VCS client might cause issues while refreshing web service connectors. Software AG recommends that you use Subversion 1.7 or higher as your VCS client.