Pointing Decisions at a new Database
Comments
-
I’d like to get some guidance on re-pointing an existing instance of Decisions to a new database.
If you can please let me know the steps/config changes needed and any “gotchas”.
-
A Decisions server can be pointed at a new database by:
[ul][li]Running the Decisions installer last used to install or update the server[/li][li]Checking Change settings on update[/li][li]Clicking Update[/li][li]Without changing anything else, modifying the database connection properties[/li][li]Finishing the update[/li][/ul]
The new target database for the installation can be a pre-existing Decisions database or a new database. When using a restored Decisions database, there are a few potential gotchas. They can be avoided by:
[ul][li][url=https://support.decisions.com/forum/topic2969-database-system-validation-issue.aspx]Setting up a databaseid.txt file[/url][/li][li]Including [b]any[/b] custom modules the old Decisions server had[/li][li]Moving the contents of the old servers filestoragelocation as defined in its settings.xml file at C:Program FilesDecisionsDecisions Services Manager to the filestoragelocation defined for the new server[/li][li]Using an installer of the same version or higher than the version last used with the restored database[/li][/ul]
[i]edited by james.hartzell@decisions.com on 11/20/2020[/i]
Howdy, Stranger!
Categories
- 2.1K All Categories
- 18 General
- 155 Installation / Setup
- 991 Flows
- 86 Rules
- 203 Administration
- 204 Portal
- 433 General Q & A
- 600 Forms
- 282 Reports
- 3 Designer Extensions
- 38 Example Flows
- 32 CSS Examples
- 1 Diagram Tile
- 5 Javascript Controls
- 139 Pages
- 1 Process Mining
- New Features
- 150 Datastructures
- 50 Repository
- 169 Integrations
- 25 Multi-Tenant
- 21 SDK
- 40 Modules
- 38 Settings
- 20 Active Directory
- 12 Version 7
- 34 Version 8