"Is there a place to change the Binding of the WSDL environment wise?" For example the same WSDL will be used in DEV,TST and PRD and to give the path of the WSDL, Bizagi provides an Application "Interfaces" to give different path of the wsdl per environment wise, but then the question is that the content of the WSDL never changes environment wise, so the option to change the Binding of the WSDL per environment makes more sense. Using the Port Name will still not solve the issue as it will still require n number of WSDLs to be created for n number of environments. Experience and the norm with other tools is to keep the WSDL in a central repository or in case of Bizagi to keep it may be the path of the WSDL in the Db and then provide a widget like Vocabulary or Environment variable to change the Binding. From tools perspective Bizagi also doesnt store the WSDL anywhere and that probably is the reason why it cannot allow to change things on the binding level, to be a strong ESB , I will recommend storing of the WSDL with the package and then deployment of the package in different environment does the rest.
↧