Click to see subtopics & related topics:Only full versions of Harmony Enterprise support cloud deployment. You cannot deploy the single-user version of Harmony Enterprise with an SE license in the cloud.
We provide guidance for clients who want to set up Harmony Enterprise in the cloud. This guidance includes requirements and configuration information for cloud installation. If you have questions, contact us.
Tip: If you want help setting up your cloud environment, recommended partner consultants are listed by AWS and Azure.
This is a brief summary of our recommended setup:
- You can run Harmony Enterprise with Windows Virtual Desktop (Azure) or AppStream (AWS)
- The Harmony Enterprise SQL database is hosted with Azure SQL (Azure) or RDS (AWS)
- The Gemalto License Server is hosted on a virtual machine
- All the above resources must be set up in the same region and virtual network
Disclaimers
IHS Markit does not offer direct cloud hosting of Harmony Enterprise or services to set up a cloud environment.
We outline a recommended approach for setting up the Harmony Enterprise application (versions 2020.2 and later), its database, and license server. While other configurations are possible, they are not supported by IHS Markit.
We reference Microsoft Azure and AWS options. Other cloud providers may be used in a similar fashion, but they have not been tested and verified by IHS Markit.
Assumptions
We expect that all of the components of the cloud environment are configured prior to installing software, licenses, database migrations, or builds. This includes a functional cloud environment with active directory (AD) configuration (if using AD sign on), database permission (both Harmony Project / Storage and any proprietary production databases), firewall settings, security group configuration, port openings etc.
Limitations
Be aware of the following:
- Harmony Enterprise connects via SQL databases, and users cannot connect to or create .hldb files. Users can import or extract .hldb files while working in the cloud with the exception of AppStream instances.
- Well Security has been observed to perform poorly in some operations in cloud environments. At this time, we do not recommend using Well Security for cloud databases, and if it is required, users will observe better performance when connected as SQL users.
- The Well Security tool for managing well access cannot connect to a Harmony Enterprise database using Azure AD. On Azure, a SQL administrator user is required to manage Well Security.
- Analytics Explorer has not yet been confirmed as adequately connecting in cloud environments.
- Standalone licenses and commuters cannot be used in cloud environments.
Considerations for Management and IT
We strongly recommend working with qualified cloud architects and engineers for your cloud deployment.
- A thorough understanding of the total cost of ownership, the current environment, and the resource requirements on pre- and post-deployments are imperative for a successful migration. We recommend working with certified cloud architects and engineers for any cloud-related deployments.
- Existing issues must be addressed prior to migration. Moving to the cloud does not resolve system inefficiencies, poor database builds, or application performance.
- Database Support must be aware of the limitations, differences, and lack of certain features associated with managing and supporting databases in cloud environments.
- A proper change management process should be followed. We strongly recommend evaluating deployments in Development / Test environments, and getting user signoffs before migrating to production.
- A Harmony Enterprise user needs read-only access to the client’s proprietary production database, and write access to the Harmony Project / Storage database.
- Prior to migration, all users must be logged out of the Harmony Enterprise database.