The sections we’re really interested in are 3.1.1 and 3.1.2. These are detailed below.

Regarding production software on a per-CPU and Virtual Machine (VM) basis:

3.1.1 Adobe grants Licensee a license to install and use the Software as Production Software on a per-CPU basis as provided in a separate writing. The total number of CPUs of all of the Computers on which the Software operates may not exceed the total number of CPUs separately licensed. For purposes of this License Metric, (a) all CPUs on a Computer on which the Software is installed shall be deemed to operate the Software unless Licensee configures that Computer (using a reliable and verifiable means of hardware or software partitioning) such that the total number of CPUs that actually operate the Software is less than the total number on that Computer, and (b) a CPU shall mean a single, physical chip with the capability of housing multiple processor cores. If Licensee purchases a 2-CPU Production Software license, then each CPU to which it applies such license must reside in the same Computer. In the event that Licensee desires to apply 2-CPU Production Software licenses to Virtual Machines, then (c) for the Standard version of the Software, the number of 2-CPU licenses required shall be the greater of (i) the number of available physical CPUs for all instances of the Software divided by two (any fractions shall be rounded up for purposes of this provision), or (ii) the total number of Virtual Machines on all Computers on which the Software is installed, and (d) for the Enterprise version of the Software, the number of 2-CPU licenses required shall be the number of physical CPUs on which the Software operates divided by two (any fractions shall be rounded up for purposes of this provision).

The key information here is:

• The Standard license is charged per 2-CPU or per-VM, which ever is greater.
• The Enterprise license is charged per 2-CPU.

But what does this actually mean for Joe Bloggs? Fortunately the guys at Adobe, via Twitter, were on hand to help.

Here is a little table that should whet your appetite:

Regarding production software on a cloud network:

3.1.2 Adobe grants Licensee a license to install and use the Software as Production Software on a Cloud Network on a per-instance basis as provided in a separate writing. The total number of instances that may run on a Cloud Network may not exceed the total number of instances separately licensed. Licensee must purchase and apply 1 instance license to each use of the Standard version of the Software. Licensee may apply 10 instances for each license purchased of the Enterprise version of the Software.

The key information here is:

• The Standard license supports cloud computing, but for each instance, 1 license must be applied.
• The Enterprise license supports up to 10 cloud instances, e.g. on Amazon EC3, Azure, Joyent, Rackspace Cloud etc.

In essence, if you’re going to run a [decent] virtual machine environment, or indeed a cloud environment, it would be far more cost efficient to run ColdFusion Enterprise, since it is costed by the number of virtual machines or increments of 10 cloud instances.

You can download the original Adobe ColdFusion 9 EULA (PDF 400K) from the Adobe website.

The buzz around cloud computing has reached a fever pitch. Some believe it is a disruptive trend representing the next stage in the evolution of the Internet. Others believe it is hype, as it uses long established computing technologies. As with any new trend in the IT world, organisations must figure out the benefits and risks of cloud computing and the best way to use this technology.

What is Cloud Computing and Why is it Important?

In order to understand the core principles of an open cloud, we need to first agree on some basic definitions and concepts of cloud computing itself. First, what is the cloud? The architecture and terminology of cloud computing is as clearly and precisely defined as, well, a cloud. Since cloud computing is really a culmination of many technologies such as grid computing, utility computing, SOA, Web 2.0, and other technologies, a precise definition is often debated.

The key characteristics of the cloud are:

• Scalability on Demand
• Streamlining the data Centre
• Improving Business Processes
• Minimising Startup Costs

Challenges and Barriers to Adoption

Although the cloud presents tremendous opportunity and value for organisations, the usual IT requirements (security, integration, and so forth) still apply. In addition, some new issues come about because of the multi-tenant nature (information from multiple companies may reside on the same physical hardware) of cloud computing, the merger of applications and data, and the fact that a company’s workloads might reside outside of their physical on-premise datacenter.

• Data and Application Interoperability
• data and Application Portability
• Governance and Management
• Metering and Monitering

The Goals of an Open Cloud

Customers expect that the cloud services they use will be as open as the rest of their IT choices. As an open cloud becomes a reality, business leaders will benefit in several ways.

• Choice
• Flexibility
• Speed and Agility
• Skills

Principles of the Open Cloud

Many clouds will continue to be different in a number of important ways, providing unique value for organisations. As cloud computing matures, there are several key principles that must be followed to ensure the cloud is open and delivers the choice, flexibility and agility organisations demand:

1. Cloud providers must work together to ensure that the challenges to cloud adoption (security, integration, portability, interoperability, governance/management, metering/monitoring) are addressed.
2. Cloud providers must not use their market position to lock customers into their particular platforms and limit their choice of providers.
3. Cloud providers must use and adopt existing standards wherever appropriate.
4. When new standards (or adjustments to existing standards) are needed, we must be judicious and pragmatic to avoid creating too many standards.
5. Any community effort around the open cloud should be driven by customer needs, not merely the technical needs of cloud providers, and should be tested or verified against real customer requirements.
6. Cloud computing standards organisations, advocacy groups, and communities should work together and stay coordinated, making sure that efforts do not conflict or overlap.

Conclusion

Although this is a time of great innovation for the cloud computing community, that innovation should be guided by the principles of openness. Industry participants must work together to ensure that the cloud remains as open as all other IT technologies.

The Open Cloud Manifesto can be viewed in full and downloaded from http://www.opencloudmanifesto.org.

Adobe is now offering developers subscribed to the Adobe Enterprise Developer Program access to their own virtual instance of LiveCycle ES through LiveCycle ES Developer Express. LiveCycle ES Developer Express provides a pre-configured, virtualized installation of LiveCycle ES Solution Components in a self-contained development environment. LiveCycle ES Developer Express is hosted on the Amazon Elastic Compute Cloud (Amazon EC2). AEDP members can test, build, store and develop their applications in a cloud-base environment where all LiveCycle ES applications are pre-configured and running. The Adobe Enterprise Developer Program will offer a minimum of 10 hours of runtime per month, with additional hours to be available separately.

What is cloud computing and why is it important?

The term cloud computing, as used by some commentators, refers to the use of scalable, real-time, Internet-based information technology services and resources. This somewhat nebulous concept incorporates software as a service (SaaS), utility computing, Web 2.0 and other recent technology trends. The common theme stresses reliance on the Internet for satisfying the computing needs of users, without them needing knowledge of, expertise with, or control over the technology infrastructure that supports them. An often-quoted example is Google Apps, which provides common business applications online that are accessed from a web browser, while the software and data are stored on Google servers.

The cloud element of cloud computing derives from a metaphor used for the Internet, from the way it is often depicted in computer network diagrams, and is an abstraction for the complex infrastructure it conceals.

How do Adobe and Amazon fit into the equation?

Adobe and Amazon have similar goals. They both want to gain more share of the enterprise market. Amazon needs to convince the enterprise that its version of the cloud is capable of supporting the demands of enterprise applications. On the other hand Adobe wants to convince the developers who already use AWS that LiveCycle is the platform of choice for the enterprise.

What is Adobe LiveCycle?

Adobe’s LiveCycle Enterprise Suite is a J2EE-based server software product used to build applications that automate a broad range of business processes for enterprises and government agencies.

LiveCycle combines technologies for data capture, information assurance, document output, content services, and process management to deliver solutions such as account opening, services and benefits enrollment, correspondence management, request for proposal processes, and other manual based workflows.

What are Amazon Webservices?

Since early 2006, Amazon Web Services (AWS) has provided companies of all sizes with an infrastructure web services platform in the cloud. With AWS you can requisition compute power, storage, and other services–gaining access to a suite of elastic IT infrastructure services as your business demands them. With AWS you have the flexibility to choose whichever development platform or programming model makes the most sense for the problems you’re trying to solve. You pay only for what you use, with no up-front expenses or long-term commitments, making AWS a cost-effective way to deliver applications to customers and clients.

How do they fit together?

Essentially, Adobe has put a Red Hat JBoss J2EE stack on AWS and deployed LiveCycle on the stack. Adobe state that this platform is purely for prototyping, developing and testing applications, rather than production environments, but that is likely to change.

The future

Deploying LiveCycle on AWS has wider implications, not only for Adobe products. By setting up a J2EE stack on AWS it makes it possible to deploy any Java-based application; yes that does mean one developed in Adobe’s ColdFusion or indeed its chief rival, Railo.