| << Back to previous view |
|
[QB-662] Is it possible to take old service parameters when upgrading on Windows?
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 3.0.10 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Trivial |
| Reporter: | Alexey Shumkin | Assigned To: | Robin Shen |
| Resolution: | Won't Fix | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Environment: |
Operating System Windows 2003 5.2, x86
JVM Java HotSpot(TM) Client VM 11.3-b02, Sun Microsystems Inc. QuickBuild Version 3.0.10 - Tue Oct 05 17:03:37 MSD 2010 |
||
| Description |
|
My QB server is running under Windows (AD) user account (not LOCAL SYSTEM account).
It is annoying when QB server upgrades DB with migrate.bat and recreates service so I need to setup it's parameters again and again. I upgrade QB with following steps: 1. Stop QB service 2. Rename old QB folder (e.g. append .bak to name) 3. Name new QB folder as previous QB instance was named 4. Then run migrate.bat As far as QB detects that is is installed as service. It would be nice then if QB detected path of installation has not changed so there`s no need to recreate service. |
| Comments |
| Comment by Robin Shen [ 08/Oct/10 07:57 AM ] |
|
You may edit the file "conf/wrapper.conf" and add below parameters:
wrapper.ntservice.account=<domain\account> wrapper.ntservice.password=<password> Then every time QuickBuild is migrated, the service account setting will be remained. |