Posted: Wed May 10, 2017 6:20 am Post subject: Updating WSDL for Integration service
Acolyte
Joined: 21 Jun 2006 Posts: 53
Is it possible to 'update' an Integration Service so that it uses a new WSDL or does a new Integration Service have to be created each time the WSDL is updated?
Background:
We have the underlying schemas and WSDL in a shared library. We then created the Integration Service by referencing the WSDL from the shared library. All good so far. We then had to make changes to the WSDL and XSDs. We changed the XSDs and WSDLs and then re-imported into the shared library. Still all good.
The issue was that when we now go into the Integration Service Description folder, it shows a big red cross with a message 'Failed to create the part's controls'. The Integration Service becomes unuseable and undeployable once the underlying WSDL is altered in any way.
The only solution I found was to create a new Integration Service and then recreate/copy the flows and ESQL from the old Integration Service to the new Integration Service.
Is there an easier way of updating an Integration Service after making changes to the underlying WSDL or is there a v.tight binding between a WSDL and Integration Service? I tried 'cleaning' but that made no difference. Is this just expected/known behaviour? From what we have seen, this is not the behaviour for Applications. Maybe this is what we need to use instead?
I am using toolkit V10 FP 6. I have looked at the fix list for FP7 and FP8 and I cannot see anyhting in there specifically relating to fixes for this toolkit error.
We came up with this workaround. I tested the exact steps below and they work. I don't know if this would be officially supported by IBM though?? We raised a PMR about this very issue. The response was that "there is no facility to do this".
Here goes...
1. Import new WSDL into the existing Shared Library
- Accept the option to overwrite existing XSDs and WSDLs in the Shared Library
2. Open Java EE perspective
3. Locate the 'deployable' message flow
4. Right-Click and select "Open With Text Editor"
5. Amend the following values to match up with what is in the new WSDL:
- selectedPortType => portType from new WSDL
- selectedBinding => binding from new WSDL
- targetNamespace => targetNamespace from new WSDL
6. Reset the default editor to open the message flow:
- Right-Click on the 'deployable' message flow and select "Open With Message Flow Editor".
7. Message flow should open in graphical view with no errors. Close the message flow.
8. Still in the Java EE perspective, locate the service.descriptor file
9. Right-Click and select "Open With Text Editor"
10. Change the value for portType to match the value from the new WSDL file
11. Reset the default editor to open the service.descriptor file:
- Right-Click on the service.descriptor file and select "Open With Integration Service Editor".
12. Service should open in graphical view with no errors. Close the service window.
13. Delete the exiting shared library for the service and the service itself from the execution group
14. Deploy the updated shared library for the service to the EG
15. Deploy the updated service to the EG
16. Bob's your uncle (or badda bing badda boom depending on which side of the Atlantic you reside).
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum