1 of 1 people found this helpful
The combination of Overlord (repository) and SwitchYard (application metadata + runtime) would provide this capability. In SwitchYard, we already have the capability to identify which applications are using a specific service artifact module (e.g. a WSDL, XSD, etc.). The next step would be to take this through a service repository like Overlord to handle the workflow associated with adding/changing a deployed artifact. I can't say right now how much of that will be present in SOA-P 6.0, but you might want to run this by the Overlord folks in their forum as well.