ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum IndexWebSphere Message Broker SupportUpdating WSDL for Integration service

Post new topicReply to topic
Updating WSDL for Integration service View previous topic :: View next topic
Author Message
brokerDev
PostPosted: Wed May 10, 2017 6:20 am Post subject: Updating WSDL for Integration service Reply with quote

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.

Any comments/suggestions welcome.

Thanks
Back to top
View user's profile Send private message
timber
PostPosted: Wed May 10, 2017 8:28 am Post subject: Reply with quote

Yatiri

Joined: 25 Aug 2015
Posts: 646

Good question. I'd like to know the answer too.

A similar question could be asked for REST services and the associated Swagger/OpenAPI specification.
Back to top
View user's profile Send private message
brokerDev
PostPosted: Thu Jun 15, 2017 10:19 am Post subject: Reply with quote

Acolyte

Joined: 21 Jun 2006
Posts: 53

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).
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Thu Jun 15, 2017 11:01 am Post subject: Reply with quote

Grand Poobah

Joined: 18 Nov 2003
Posts: 19209
Location: LI,NY

Seems all way to heavy

I used to do it like this:
  • Create a different project/library and keep the development version of wsdl and xsds there. Any changes will be made there...

  • Then import the wsdl into the correct flow/application/library, this creates the missing parts for the wsdl to become a deployable Wsdl.


There ... done...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexWebSphere Message Broker SupportUpdating WSDL for Integration service
Jump to:



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
Protected by Anti-Spam ACP


Theme by Dustin Baccetti
Powered by phpBB 2001, 2002 phpBB Group

Copyright MQSeries.net. All rights reserved.