SEI Cloud Version
SEI can be deployed in two ways, as cloud or on-premises. Most features available on-premises are also available in the cloud. What follows covers what's managed automatically in the cloud version, and the few areas where its behavior differs from on-premises.
In the cloud version, data reaches SEI through DataSync, a synchronization layer that keeps your databases up to date. Data can be synchronized in three different ways: cloud-to-cloud, on-premises-to-cloud, or hybrid.
The connection type depends on where your data sources are. If your ERP or another business solution already runs in the cloud, a DataSync connector sends its data to SEI Cloud, which is a cloud to cloud connection. If your ERP database is on your own servers, DataSync installed there sends the data instead, an on-premises to cloud connection. A hybrid setup combines both, with some data sources in the cloud and others on your servers, all reaching the same SEI Cloud environment.
Advantages of the cloud version
One of the main reasons to choose the cloud version is that the infrastructure work is handled for you. The table below describes what is automatically taken care of.
| Advantage | What's managed automatically |
|---|---|
| Monitor availability | System availability is monitored, with current status published on the public status page. |
| Maintain the application | Updates, patches, and fixes are applied automatically, so no upgrade window needs to be scheduled or managed. |
| Manage capacity | Infrastructure is managed automatically, including load monitoring, performance tuning, and capacity planning for storage, software, and connections. |
| Include licensing | SQL Server licensing is included and requires no separate management. |
| Back up and restore data | The internal SEI database restores to any point in time within the last 35 days, and the data warehouse within the last day, with weekly backups kept for 2 weeks and monthly backups kept for 2 months. All backups are stored in multiple locations. Disaster recovery targets an RPO of 4 hours and an RTO of 24 hours. |
| Track incidents | Centralized logging is used to detect and track incidents. |
Limitations of the cloud version
Because the cloud environment is closed and multi-tenant, certain features are restricted or unavailable.
| Limitation | What changes in the cloud version |
|---|---|
| No distribution module | Distribution jobs can't deliver to a network folder in the cloud version. |
| Only cloud data warehouse | Only the SEI Cloud data warehouse is accessible, and all data must be synchronized to the data warehouse using DataSync. Administrators and ADMCA users can still add environments beyond Production, copy and paste data source details, and set a data source as the data warehouse. |
| No Active Directory authentication | Active Directory authentication is not supported. Use OAuth2, SAML2, or user accounts instead. |
| Central Point Configurator inaccessible | Central Point Configurator is not accessible. Any changes must be submitted through support instead, including disabling product notifications, enabling SQL Execution Logging or View Usage Logging, and adjusting dashboard export resolutions for PDF scenarios. |
| Limited DataSync connectors | The Microsoft Excel, Microsoft Access, and ODBC connectors are not available, since the cloud is multi-tenant and external ODBC connectors can't be installed directly. If one is needed, DataSync can run on a separate server instead (on-premises, Cloud Sage, or a partner server), then the data can be uploaded to SEI Cloud from there. |
| No Remote Desktop access | Since SEI Cloud is a closed, multi-tenant environment, connecting to a machine using Remote Desktop is not possible, which also means internal logs can't be viewed directly to investigate issues. |
| Fixed sender address | For Send Comment and Email features, the sender's name still appears as the display name, but the underlying email address is fixed to noreply@nectari.com. |