| Author |
Message
|
| HarryHill |
 Posted: Wed Feb 16, 2011 8:57 am Post subject: WSDL Config Management Best Practice |
 |
|
Newbie
Joined: 01 Feb 2011
Posts: 5
|
When creating a webservice in WMB, once you've created the WSDL and generated the 'deployable WSDL' to drag onto your SOAP input node if you subsequently need to amend the WSDL what process do you use:
Do you edit the deployable wsdl and msxd's in the message set
do you maintain the wsdl external to WMB and re-import
or some othe rmechanism?
What's the best practice? |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Wed Feb 16, 2011 9:22 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
If you're starting from a WSDL, that you are then creating a message set from - update the WSDL and then rebuild the msgset and the deployable WSDL.
If you're starting from a message set, then update the message set and regenerate the WSDL from it.
Basically, make the update to whatever is the "original" document, and then regenerate and/or reimport from there. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Feb 16, 2011 9:46 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Remenber that the WSDL is the contract definition between the provider and the consumer. BOTH sides need to have access to it.
IMHO, when the intercafe spec is stable then the WSDL (and any needed XSD's) should be made available so that the conumers can do their dev work.
I prefer to use the WSDL that is held in the Source control system as the definitive contract document. Then both sides can use it and find the holes sooner rather than later.
This is however very differen from the way that SAP works. From my experience the BAPI dev can't publish his WSDL (if it is going to be exposed as a web service) until they have done all their dev work. It can cause a blockage especially if you are operating in an agile environment.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| HarryHill |
| Posted: Thu Feb 17, 2011 1:08 am Post subject: |
|
|
Newbie
Joined: 01 Feb 2011
Posts: 5
|
| smdavies99 wrote: |
Remenber that the WSDL is the contract definition between the provider and the consumer. BOTH sides need to have access to it.
IMHO, when the intercafe spec is stable then the WSDL (and any needed XSD's) should be made available so that the conumers can do their dev work.
I prefer to use the WSDL that is held in the Source control system as the definitive contract document. Then both sides can use it and find the holes sooner rather than later. |
The deployable WSDL and msxd's are in the source control system as they are part of the message set projects. So should we just use these as the definitive contract or are there any reasons why this might not be a good idea. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Feb 17, 2011 2:18 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
to turn your argument on its head,
Why should you not consider the WSDL that is the Main Branch of your Source Control System as the definitive version?
After all, it is not in a develpment branch so....?????
 
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| HarryHill |
| Posted: Thu Feb 17, 2011 3:02 am Post subject: |
|
|
Newbie
Joined: 01 Feb 2011
Posts: 5
|
| smdavies99 wrote: |
to turn your argument on its head,
Why should you not consider the WSDL that is the Main Branch of your Source Control System as the definitive version?
After all, it is not in a develpment branch so....?????
|
Not sure I understand where you are coming from. My Deployable WSDL in my Message Set project *is* in the main branch of my source control system. The question is are there any downsides to using this as my definitive version and when changes are required use the WSDL design tool in the Broker Toolkit? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Feb 17, 2011 6:00 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
I think what smdavis99 is saying is that as per the SOAP standard, the WSDL you generate is the actual binding contract between the provider and the consumer - and as such this should be treated as the master document to create changes. This would mean that you would edit the WSDL, use it to generate (or regenerate) the message definitions, and then regenerate the deployable WSDL.
But if you're only ever producing the WSDL by generating it from the message definitions, I'm not sure that's required.
 |
|
| Back to top |
|
|
|
|
