Trading Networks 10.3 | Administering and Monitoring B2B Transactions | Service Development Help | Working with Web Services | About Refreshing a Web Service Descriptor | How Refresh Affects a Web Service Descriptor
 
How Refresh Affects a Web Service Descriptor
Integration Server handles the updating of each web service descriptor element or associated IS element differently depending on:
*The web service descriptor element, such as an operation, binder, or header.
*The type IS element.
*Whether the web service descriptor element or IS element changed since the web service descriptor was first created.
*Whether the updated WSDL document contains an element that corresponds to the web service descriptor element or IS element.
The following table provides details about how Integration Server handles specific IS elements during refresh.
For this element...
During refresh Integration Server...
IS document type
Deletes all of the document types thatIntegration Server generated from the WSDL document. Integration Server then creates new document types using the updated WSDL document. Any changes made to the original document types will be lost.
IS schema
Deletes all of the IS schemas that Integration Server generated from the WSDL document. Integration Server then creates new IS schemas using the updated WSDL document. Any changes made to the original IS schemas will be lost.
Service
Does one of the following for the skeleton services generated for operations in the original WSDL document:
*If logic has been added to the skeleton service or service properties have been set and the corresponding operation exists in the updated WSDL document, Integration Server merges the logic into the refreshed service and ensures that the property values match the values set prior to refreshing.
*If logic has not been added to the skeleton service, service properties have not been set, and the corresponding operation exists in the updated WSDL document, Integration Server recreates the empty skeleton service.
*If a service corresponds to an operation that does not exist in the updated WSDL document, Integration Server removes the operation that corresponds to the service from the web service descriptor. Integration Server keeps the service in the “services” folder.
Note:Integration Server considers a renamed operation to be a new operation.
Web service connector
Deletes and recreates all web service connectors. Any changes made to a web service connector, including changes for pipeline mapping, will be lost.
connectors folder
Deletes the connectors 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.
consumerWSDName_ folder
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.
docTypes folder
Deletes the docTypes 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.
responseServices folder
Does the following with the contents of the responseServices folder:
*For new operations in the updated WSDL document, Integration Server adds new response services.
*For modified operations, Integration Server updates the response services including merging in any logic that was added.
*For deleted operations, Integration Server removes the operation that corresponds to the service from the web service descriptor. Integration Server keeps the response service in the “responseServices” folder.
services folder
Does the following with the contents of the services folder:
*Adds new skeleton services for new operations in the updated WSDL document.
*For modified operations, updates the skeleton services including merging in any logic that was added. For more information, see the “Service” row in this table.
*For deleted operations, Integration Server removes the operation that corresponds to the service from the web service descriptor. Integration Server keeps the service in the “services” folder.
The following table provides details about how refreshing a web service descriptor affects the contents of the web service descriptor itself.
For this web service descriptor element
During refresh Integration Server...
Binders
Updates the binders to reflect any new port information in the WSDL document. Integration Server also updates the operations for each binder to reflect any new or removed operations in the updated WSDL document. Integration Server updates the SOAP action values assigned to operations in binders to reflect any changes in the updated WSDL document.
Header/Fault
For a header/fault defined in the WSDL document, Integration Server does one of the following:
*If the updated WSDL document does not contain the header/fault, Integration Server removes the header/fault from the web service descriptor. Integration Server also deletes the document types used to define the header/fault documents from the docTypes folder.
*If the updated WSDL document contains the header/fault, Integration Server keeps the header/fault in the web service descriptor. Integration Server recreates the document types used to define the header/fault documents and places them in the docTypes folder.
*If the updated WSDL contains a new header/fault, Integration Server adds the header/fault to the web service descriptor. Integration Server adds the new document types used to define the header/fault documents to the docTypes folder.
For a header/fault that was added manually after the web service descriptor was created, Integration Server adds the document types that define the header/fault to the refreshed web service descriptor.
Note:
If a header/fault that was added manually after the web service descriptor was created has the same name as a header/fault in the updated WSDL document, Integration Server replaces the manually added header/fault with the header/fault that Integration Server generates programmatically from the WSDL document. This might result in broken mappings or unexpected behavior in the handler service associated with the header/fault.
Handler
Integration Server adds handlers defined in the previous version of the web service descriptor to the refreshed web service descriptor.
Operations
Updates the operations to reflect any new or removed operations in the updated WSDL document.
Policy
Attaches any polices added in the previous version of the web service descriptor to the refreshed version of the web service descriptor.