Script Db Autostart Tick Flag

james fenoulhet

New Member
HI
We are running 10.2b patch 7 on windows server 2008R2.

We are looking into automating the shutdown of our DB's for windows updates to take place. By default we have the "autostart" option ticked on each of our DB's. During the windows update process the server may restart serveral times. I would like to be able to script via a bat file a way to untick this flag on the DB config page, is this possible via a proutil or other method, i assume the flag settings must be saved somewhere so must be modifiable.

thanks


upload_2017-7-3_12-25-25.png
 

oli

Member
IMHO, you should rather consider not starting the OpenEdge AdminService.
This will prevent all components (db, appserver,...) to "auto-start".

(The "autostart" flags are saved in the "%DLC%\properties\ubroker.properties" file... but you'd better not edit this file)
 

james fenoulhet

New Member
always happy for alternate solutions\suggestions.
So once we cleanly take down the services and DB, run a script to change the startup type for the Amin service from automatic to manual. so that when the server restarts we should be ok in terms of the admin service not kicking everything back in? Then when we are ready, run an alternate script to change the startup type to automatic? Restart the server and everything should come back up ok.

going to build a load of checks around this process but wanted to try and understand how to prevent the DB's coming back up when we didnt want them to.

thanks for the reply Oli
 

Cringer

ProgressTalk.com Moderator
Staff member
Yes, changing the service to manual will stop everything from starting up. I would agree that this is by far the simplest method of doing what you want to do.
 

cj_brandt

Active Member
I believe ubroker.properties has the properties for the ubroker components and database properties are in conmgr.properties file.
 

james fenoulhet

New Member
I believe ubroker.properties has the properties for the ubroker components and database properties are in conmgr.properties file.
Thanks, out of curiosity is it safe to modify the conmgr.properties file in a text editor or would that be considered unsupported behaviour?
 

Cringer

ProgressTalk.com Moderator
Staff member
It's ok to edit in a text editor, but
1) if you get it wrong nothing works
2) if another process edits at the same time as you then someone's changes will go missing

There is a utility called mergeprop that can be used to edit the properties files, but the syntax is horrible! (My opinion!)
 

TomBascom

Curmudgeon
You're almost forced to at least use dbman and adminserv because they run as services. You can cobble together "scheduled tasks" and proserve but it is nowhere near as easy or reliable as it is on UNIX.
 

Rob Fitzpatrick

ProgressTalk.com Sponsor
If you proserve a DB from a command prompt, it's a user process. If that user exits, their processes die. Not what you want for a broker. ;)
 

Cringer

ProgressTalk.com Moderator
Staff member
The other reason you'd do it is because it's seemingly the way that Progress are pushing. Chatting with Brian Bowman last week, they are working hard on getting OEE and OEM more and more functional. I gather one thing they want to do is to decouple OEM from the Admin Server so that a crashed Admin Server doesn't stop alerting. They will therefore continue to push people to use conmgr.properties etc.
 

TomBascom

Curmudgeon
While I agree that marketing will continue pushing that festering pile of steaming excrement I don't see a causal link in those statements.
 
Top