Re: Service brokered route services binding issues
Christian Brinker
Hi Sergio,
on first glance this looks, as you seems to be a problem of your catalog definition because the cloud controller only checks the returned JSON and the return messages/status codes of the service broker. No other sanity checks are done. So first I would start by setting bindable to "false" because it a route service is not generally not able to bind to an app. It binds to a route. The name of the property may seem to be a bit confusing here. The rest of the definition seems to me correct. But maybe I missed something. Then I would proceed with the Service Brokers endpoint return codes. Do you log the messages send from/to the service broker from the cloud controller? The route binding as user provided service does not use the service broker api at all. So this does not interfere with your problem. But good to here your service works. Greets Christian On Tue, 23 May 2017 at 17:07 Sergio Rozenszajn <sergio.rozenszajn(a)sap.com> wrote: Hi,-- E-Mail: cbrinker(a)evoila.de evoila GmbH Wilhelm-Theodor-Römheld-Str. 34 55130 Mainz Germany Geschäftsführer: Johannes Hiemer Amtsgericht Mainz HRB 42719 Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential and/or privileged information. If You are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden. |
|