Repository Server Questions
Comments
-
[font=Roboto, Arial, Helvetica, sans-serif]While reading through (https://documentation.decisions.com/docs/installation-requirements-self-hosted-environment), we came across Repository Server, what is the purpose, and is it necessary? We plan on upgrading our 2012 servers to 2019 servers and from 4.16 to the latest version of Decisions. W[/font][font=Roboto, Arial, Helvetica, sans-serif]e currently have three separate environments for our Decisions servers, would we need one repository server for each environment, or can our three environments share the one repository server? Also, does it need to be its own server, or can it co-exist with the Decisions Rule server?[/font]
-
[font=Roboto, Arial, Helvetica, sans-serif]A Decisions Repository server is used for organization, version control, auditing, and deployment of Decisions projects. Having a repository is not a requirement but can be extremely useful depending on the number and complexity of projects your organization may be using. Its utility can be likened to using GitHub for traditional software development. [/font][font=Roboto, Arial, Helvetica, sans-serif]One repository can be used between any number of Decisions servers, whether they are production, QA, UAT, development, or disaster recovery servers. To answer your other question, it does have to run on a separate server and requires its own non-production license.[/font]
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