We would like to hear if someone is using Endevor for WSDL and how it works for you.
We would like to maintain WSDL, XSD and generate WSBIND files with Endevor and having a WSPARM file with parameters for the bind.
Our tools are IDz and Carma interface.
Even if you don't have exactly that set up it would be interesting to hear how you think it is working for you. And if you felt it was hard to get it to work.
1. The WSDL and XSD type in Endevor do you use the new features in Endevor ?Long Element name (ex: POOrderNrDelivInfoService_v1_0)
2 Do you store this type into USS files direct from Endevor ?No MVS dataset in between?Are you using the batch interface to ADD the element?
3 How do developer EDIT the WSDL/XSD ?BRKarin
Phon has detailed how to set up USS in Endevor. I would also add that if you use packages and package backout, then the base directory should be a directory that is not visible to developers. Use the source output feature in type definition to write the file out to a directory that developers can see. If you do this then backout works the same as it would for normal elements. We do this for our production stage only.