Right now, if AMS is not available at startup, decision table operator will start with an empty ruleset. Connection to AMS is not retried ever again.
Reloading of the rules is now achieved through a tricky input stream that only exists during runtime, plus requires active monitoring from our side to notice rules have not been loaded. This is not good enough for production environments.
We would like that decision table operator adds properties to support re-connection to AMS. Please see details on support case 01796393.
We need this for SB 7.X
Thanks a lot
Dear Manish
While AMS server is part of 10.X, Decision Table Operator with connection to AMS is part of 7.X
We kindly ask you to add the feature to the 7.X version of Decision Table Operator as well, the reasong being we don't have any foreseeable plans to migrate to 10.X.
Kind regards,
Alejandro
Hello Alejandro, please note that AMS is not part of 7.x. We will look into this for 10.x.