Starting with V10.0, Cora SeQuence has been renamed to Cora Orchestration.
V10.x
Software requirements
Required software for building and deploying Cora Orchestration applications.
| Database | SQL Server 2016 SP1 (Enterprise or Standard editions) and later. For actual database version compatibility with target version, see this article. |
| Target server* | Operating system: Windows Server 2016 and later IIS URL Rewrite Module 2, Version 7.2.1993 Download URL: "https://download.microsoft.com/download/1/2/8/128E2E22-C1B9-44A4-BE2A-5859ED1D4592/rewrite_amd64_en-US.msi" SilentInstallArguments="/q /norestart" /> Additional software:
|
| Building machine** | Operating system: Windows 10 or Windows Server 2016 and later Additional software:
|
* Target server: server where you deploy the Cora Orchestration application.
** Building machine: computer where you build the applications and package them for deployment.
Minimum hardware requirements
Following are the minimum hardware requirements for a basic Cora Orchestration configuration. The actual configuration should take into consideration the implementation's expected volume and performance requirements.
Development environment
- Single-server deployment: all Cora Orchestration components are deployed on the same server.
| Server type | RAM | CPU | Storage | Count |
|---|---|---|---|---|
| Windows server | 8 | 2 | 100 GB | 1 |
| SQL server* | 16 | 4 | 1000 GB | 1 |
Production environment
- Two back-end servers: Administration site, ADSS, BRS, JES
- Two front-end servers: Flowtime site, WebAPI site
- Load balancing: Each pair is coupled by a load balancer
| Server type | RAM | CPU | Storage | Count |
|---|---|---|---|---|
| Windows server | 8 | 4 | 100 GB | 4 |
| SQL server* | 32 | 4 | 2000 GB | 1 |
* For both environments, the SQL server can be replaced by Azure SQL Managed Instance.
Licensing
For information on how to activate your license, see Activate your Cora Orchestration license, in this article.
Required accounts
For a successful deployment, you need to set up the following accounts.
| Account | Description | Account Type | Requirements |
|---|---|---|---|
| Deployment Account | Used to deploy Cora Orchestration applications. | A domain user account or Local Account |
|
| Application Pool Identity Account | Used to run Cora Orchestration Administration site and the Flowtime website. | A domain user account or Local Account |
|
| Cora Orchestration Database Account | SQL Server account that is used to create the Cora Orchestration database, and used by the application to communicate with the database server. | SQL account |
|
| Cora Orchestration Windows Services Account | Used to run the Background Runtime Windows Service, Job Execution Service, and optionally, the Active Directory Synchronization Windows service. | A domain user account or Local Account |
Best practice |
V9.x
Software requirements
Required software for building and deploying Cora SeQuence applications.
| Database | SQL Server 2016 SP1 (Enterprise or Standard editions) and later |
| Target server* | Operating system: Windows Server 2016 and later Additional software:
|
| Building machine** | Operating system: Windows 10 or Windows Server 2016 and later Additional software:
|
* Target server: server where you deploy the Cora SeQuence V9.x application.
** Building machine: computer where you build the applications and package them for deployment.
Minimum hardware requirements
Following are the minimum hardware requirements for a basic Cora SeQuence configuration. The actual configuration should take into consideration the implementation's expected volume and performance requirements.
Development environment
- Single-server deployment: all Cora SeQuence components are deployed on the same server.
| Server type | RAM | CPU | Storage | Count |
|---|---|---|---|---|
| Windows server | 8 | 2 | 100 GB | 1 |
| SQL server* | 16 | 4 | 1000 GB | 1 |
Production environment
- Two back-end servers: Administration site, ADSS, BRS, JES
- Two front-end servers: Flowtime site, WebAPI site
- Load balancing: Each pair is coupled by a load balancer
| Server type | RAM | CPU | Storage | Count |
|---|---|---|---|---|
| Windows server | 8 | 4 | 100 GB | 4 |
| SQL server* | 32 | 4 | 2000 GB | 1 |
* For both environments, the SQL server can be replaced by Azure SQL Managed Instance.
Licensing
For information on how to activate your license, see Activate your Cora SeQuence license, in this article.
Required accounts
For a successful deployment, you need to set up the following accounts.
| Account | Description | Account Type | Requirements |
|---|---|---|---|
| Deployment Account | Used to deploy Cora SeQuence applications. | A domain user account or Local Account |
|
| Application Pool Identity Account | Used to run Cora SeQuence Administration site and the Flowtime website. | A domain user account or Local Account |
|
| Cora SeQuence Database Account | SQL Server account that is used to create the Cora SeQuence database, and used by the application to communicate with the database server. | SQL account |
|
| Cora SeQuence Windows Services Account | Used to run the Background Runtime Windows Service, Job Execution Service, and optionally, the Active Directory Synchronization Windows service. | A domain user account or Local Account |
Best practice |
