Mediachase distributes two packages: SDK and Full Source Code Package. The SDK package is generated and built from the Full Source code package. It is preferable to work with the SDK package. It is much simpler, more productive, and easier to upgrade later on. The Full Source code package should be used as a reference and for debugging purposes. It will also be useful when certain bugs are found in the core platform and need to be fixed right away--so you do not have to wait for a public release to eliminate critical bugs.
While these packages serve different technical purposes, the licensing options are essentially the same. The SDK and Full Source Code package, once installed, allows developers to develop only within a "localhost" environment without a license. In order for a developer to install and use the SDK or Full Source Code within a non-localhost environment, they will need a Developer License registered with a list of server domains and IPs specifically used for development. For example, dev.mysite.com, since it is not localhost, will need to be added to the Developer License. When the solution is deployed on a QA/staging server for testing, that requires a free QA license. Finally, when the solution is deployed to a production server, a Production Deployment License is necessary. The SDK becomes the primary development environment, while developers can compile new DLLs from the Full Source Package to add/update existing DLLs in the SDK package.
This guide details the types of ECF licenses available and how to activate these licenses. You will also learn how licensing affects the two different ECF packages available to customers, SDK and Full Source Code. Licensing is comprised of three basic types: Developer, QA/Staging, Production Deployment. Each of these licenses play a critical role in the development life-cycle of an ECF solution.
- Developer: By default, Working with SDK Package and Working with Full Source Code Package only allows developers to work in a "localhost" environment. If you want to develop on a remote development server, you can request a custom license based on your development environment -- i.e. dev.mysite.local or ServerName. You have to be a paid customer in order to receive the Full Source Code package.
- QA/Staging: If you have purchased the Full Source Code license or a Production Deployment license, we provide a QA/Staging license for free. This type of license allows you to create quality assurance (QA) and staging environments before your solution is deployed into production. Like a Developer License, QA//Staging domains or ServerNames need to be registered with the license. This license has a one year time-out.
- Production Deployment: Production Deployment Licenses need to be purchased and are necessary for deploying a live, public website. There are two sub-types of Production Deployment Licenses:
- Unlimited Sites Deployment License - This entitles you to an unlimited number of public sites.
- Two-Site Deployment License - This enables you to launch up to two live production sites.
Sometimes a customer's requirements go beyond our typical licensing blueprint. In these situations, we can generate non-standard licenses. You will need to notify us before purchase what your needs and requirements are before we issue your license.
There are two ways to successfully license and activate the ECF. We will typically issue a product key that is generated when a license request has been made. A license key consists of 25 alpha-numeric characters separated by dashes (xxxxx-xxxxx-xxxxx-xxxxx-xxxxx). By entering a license key, your installation of ECF is licensed and usable beyond a "localhost" environment. The Licensing Engine will then query our licensing server to verify its validity and activation status.
A .LIC is an alternative method of licensing and activating ECF. A .LIC is a file containing a guid that is uploaded and installed via the Licensing Installation form within Commerce Manager or Command Prompt. We will issue .LIC files only if there are product key activation failures, primarily due to restrictive firewall protections that prevent communication with our licensing server.