Sage Exception Error On Playback

[sflamm]

I had inquired about this before as well... I think that is more aligned with end-user expectation. A knob would work well which by default could align them all but could be checked off in the advent that users want independent configuration of BMT/Phoenix (which I find a much more unlikely scenario).

I hope that this will be considered/implemented.

[stuckless]

Originally Posted by PiX64

is there any hope for a global settings page which will allow an admin to set all of the properties files on extenders?

There is certainly a possibility that the settings could be applied in the context of a given extender... but then I'd have to allow you to "connect" as a currently connected extender and then use the UI context to set the properties. I've thought about it... but it's not high on my list of things of complete

[sflamm]

Perhaps a good in between step would be to allow BMT to read all of the client properties files and output an updated set of files for the clients. Then the end-user can 'stop' the clients and 'deploy' the updated properties files as a process flow within BMT.

So the flow could be:

1. user uses BMT to set properties
2. user presses 'apply' to commit server changes
3. on 'apply' BMT queries user if the user would like to update clients as well (assume 'yes')
4. user is instructed to manually 'stop' clients
5. BMT reads each client properties file, updates and deploys / copies the updated properties file to each client (requesting username/password for clients if necessary for software extenders)
6. user is instructed to 'start' clients

Thoughts?

[stuckless]

Originally Posted by sflamm

Perhaps a good in between step would be to allow BMT to read all of the client properties files and output an updated set of files for the clients. Then the end-user can 'stop' the clients and 'deploy' the updated properties files as a process flow within BMT.

So the flow could be:

1. user uses BMT to set properties
2. user presses 'apply' to commit server changes
3. on 'apply' BMT queries user if the user would like to update clients as well (assume 'yes')
4. user is instructed to manually 'stop' clients
5. BMT reads each client properties file, updates and deploys / copies the updated properties file to each client (requesting username/password for clients if necessary for software extenders)
6. user is instructed to 'start' clients

Thoughts?

It's a very good idea, i won't dispute that. You have to realize, I have very limited time (especially this past few months) and as a result, I need to prioritize any work that I do on Phoenix and BMT. Given that this is something that I've never needed to do, then it gets a low priority

[sflamm]

Understood - your efforts are appreciated. I know how difficult it us to manage your real home/work responsibilities and find extra time for this.

BMT rocks. Thanks.