On-site Deployment
On-site Deployment (OSD) vs Software as a Service (SaaS)
The following highlights the considerations for each SD Elements option.
|
For security considerations and more detail on how SD Elements is secured, see How is SD Elements secured? |
On-site Deployment (OSD)
This option is available only for Enterprise customers.
-
Additional support costs are captured in the OSD pricing.
-
Backup and monitoring for security and availability is the responsibility of the client’s IT.
-
Updates are generally available within a few days after the update for SaaS.
-
Updates need to be applied by the client’s admin (which is as simple as running a single command on the appliance).
-
Due to lack of access, resolving technical issues takes longer compared to SaaS and is usually done over WebEx.
Software as a Service (SaaS) - Dedicated Instance
This is the default option for all medium and large customers.
-
All customizations available to OSD can be done in SaaS dedicated instances.
-
Provides complete segregation.
-
Each instance has a dedicated server stack: web, application, and database server.
-
The running environments are completely isolated/segregated.
-
Data is backed up hourly and the whole system is backed up daily and stored securely offsite.
-
Data and service restoration can be done in a very short time in case of issues.
-
Firewall and IDS protected and all security activities are monitored by our trained staff according to industry best practices.
-
Monitoring available for application errors.
-
SSO available through SAML Federated authentication. LDAP is normally not possible since corporate LDAP servers are typically not available from the outside network.
-
Theming and other customization available.
Software as a Service (SaaS) - Shared Instance
This option is used for Demo, Proof-of-Concept (PoC), and small clients only.
-
All considerations of SaaS Dedicated Instances are applicable here except for data segregation.
-
Data is segregated at the application level. Each organization will have its own completely isolated space/sandbox.
-
Theming and SSO are NOT available.
-
Localization, such as changing the titles, Business Unit, Application, and Project to custom strings, are not available.
-
Custom Pluggable Reports are not supported.
-
Unless otherwise specified, other basic features such as APIs are available similar to other options.
SD Elements On-site Deployment requirements
SD Elements On-site Deployment is provided in the form of a Virtual Appliance.
Requirements
-
VMWare ESXi 4.1 or more recent
-
Minimum 4 GB memory
-
For CPU requirements see the attached sheet below
-
Minimum 80 GB of disk space / Recommended 128 GB of disk space (see attached sheet for more information)
-
One Static Internal IP
-
DNS name (e.g. sde.)
-
Intranet SSL Certificate for HTTPS (OpenSSL/Apache compatible format)
-
Inbound traffic needed VM:
-
TCP port 80 (HTTP)
-
TCP port 443 (HTTPS)
-
TCP port 22 (SSH) for maintenance/management
-
-
Outbound Intranet SMTP Email access
-
Outbound HTTPS access to sdelements.com domain for fetching updates that are available every 6 weeks
-
Recommended – VPN connection or Webex sharing for SD Elements Debugging/Maintenance
Shipping
-
The Virtual appliance is provided through secure download
Minimum hardware requirements of on-site SD Elements appliance |
|||
Users / Projects |
100 Projects |
500 Projects |
3000 Projects |
---|---|---|---|
100 Users |
|
|
|
500 Users |
|
|
|
3000 Users |
|
|
|