Header

Fault

Endpoint alias within a binder for a consumer web service descriptor

When refreshing a web service connector, Integration Server deletes the consumerWSDName_ folder and all elements contained in that folder and its subfolders. Integration Server will not recreate any elements manually added to the folder or its subfolders. Integration Server will not recreate modifications made to any of the original elements in the consumerWSDName_ folder.

Refreshing a web service connector does not change the structure of the fault in the output signature. That is, when you refresh a web service connector for a web service descriptor created using an Integration Server version prior to 8.2, the web service connector output signature retains the SOAP fault document that is specific to the SOAP protocol (i.e., SOAP 1.1 or SOAP 1.2). Similarly, if you refresh a web service connector for a web service descriptor created using Integration Server 8.2, the web service connector’s output signature will continue to have the generic SOAP fault structure. For more information about how the output signature of web service connector depends on the version of the Integration Server on which the web service descriptor is created, see Web Services Developer’s Guide.

If the Validate Schema using Xerces property is set to true for a web service descriptor, Integration Server validates the schemas associated with a consumer web service descriptor when you refresh the web service connector.

Refreshing web service connectors is different than refreshing a web service descriptor. When refreshing web service connectors, Integration Server uses the original WSDL document to recreate the web service connectors and the contents of the consumerWSDName_ folder. When refreshing a web service descriptor, Integration Server uses an updated version of the WSDL document to regenerate the web service descriptor and its associated IS elements. For more information about refreshing web service descriptors, see About Refreshing a Web Service Descriptor.

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.