Adobe AEM as a Service (AEM)

Adobe AEM service can provide your project with a web content management system, equipped with a wide range of powerful tools. The service includes VMs with an installed Adobe AEM (versions 6.0, 6.1 and 6.2 are supported), and gives users the facilities of convenient website development and management.

The AEM Service is available only for EPAM and AWS regions

An AEM cluster represents a set of AEM instances: single author instance and publish instances as many as needed for project. Replication is configured from author instance to all publish instances within the cluster. In addition, there is one dispatcher above author instance (hosted on it), needed for caching pages.

EPAM Orchestrator supports two technologies of creating AEM clusters and deploying AEM as a Service - AEM Basic and AEM PaaS Mode.

In AEM Basic, the cluster is formed by creating an author instance with a dispatcher and a number of publish instances with one dispatcher above all publish instances (hosted on the first one) acting as a load balancer.

In AEM PaaS Mode you also create a cluster of author and publish instances, however, the technology of its creation is different. Each instance, both author and publish, is created with its own dispatcher. Replication is configured from author instance to all publish instances within the cluster. In addition, there is one dispatcher above author instance (hosted on it), needed for caching pages..

AEM as a Service is delivered in cooperation with Content Management Competency Center, who are responsible for the application initial settings and performance. In case you encounter any issues with the service usage, please address the Competency Content Service Desk.

Have a Question?

The current page gives the general information on the service and the main workflows. However, while working with the services, our users encounter new questions they need assistance with. The most frequently asked questions on EPAM Cloud Services are gathered on the Cloud Services FAQ page.
Visit the page to check whether we have a ready answer for your question.

Related CLI Commands

The table below provides the list of service-related commands and their descriptions:

Command Short Command Description
or2-manage-service ... -s aem -a -c cluster-name or2ms Creates a new cluster in the specified project and region
or2-manage-aem or2aem Used to create a new cluster and perform environment manipulations
or2-manage-service... -s aem-author-paas -a --customize or2ms Starts an AEM author instance in the specified project and region
or2-manage-service... -s aem-publish-paas -a --customize or2ms Starts an AEM publish instance in the specified project and region

Further on this page, you can find the examples of the commands usage for the Adobe AEM as a Service manipulation.

Service Activation

AEM Basic

There are two ways to activate the service:

  • By calling the or2-manage-service Maestro CLI command:

    or2ms -s aem --activate -p project -r region -h shape -c cluster_name
    where -h/--shape is an optional parameter specifying the shape of the author instance (MEDIUM is the default and the smallest possible one).
  • By calling the or2-manage-aem (or2aem) command with the activate-cluster action:

    or2aem -p project -r region -s shape -a activate-cluster -c cluster_name
    where -s/--shape is an optional parameter specifying the shape of the author instance (MEDIUM is the default and the smallest possible one).

Both commands, when called, initiate running of an author instance, used to create and manage content and to administer a website. By default, this is a MEDIUM CentOS6_64-bit instance. You can change the shape by using the optional --shape parameter, but the shape should not be smaller than MEDIUM.

The cluster name should be unique for a project within a region.

EPAM Orchestrator supports two versions of AEM - 6.0 and 6.1. The 6.0 version is the default one and is activated when the version is not specified explicitly. To activate AEM version 6.1, use the or2aem or or2ms command with the -v/--version parameter:

or2aem -p project -r region -s shape -a action -v version

Service Customization

AEM Service is activated by a Maestro Stack execution which refers to the default parameter values. However, when the AEM service is activated by means of the or2-manage-services (or2ms) command, the service configuration can be customized. For that purpose, run the or2ms command with the --customize option:

or2ms -s aem --activate -p project -r region -h shape -c cluster_name --customize

With customization enabled, the stack execution allows modifying the default parameter values. The following parameters can be customized during service activation:

Description Type Default Value Min Value Max Value Required
AEM Minimum Heap Size number 128 128 256 No
AEM Maximum Heap Size number 2048 2048 4096 No
AEM PermGen Size number 512 512 1024 No
Java Version* string 7 No
AEM Version* string 6.0 No
AEM license URL string empty No
Initial Dispatcher** string empty No

*Currently, changes to these parameters will have no effect on service activation

**Only for aem-publish instances

Parameter customization is not required for proper service activation. Use the --customize option to adapt the service settings to suit your project requirements.

After the command is executed, the system prompts for parameter values one by one showing the default ones, as well. You can specify a custom value when necessary or skip a parameter to keep the default setting.

AEM PaaS Mode

To activate the AEM as a Service in PaaS Mode, use the or2-manage-service Maestro CLI command specifying aem-author-paas as the -s/--service-name parameter value:

or2ms -s aem-author-paas --activate -p project -r region --customize

This command will start an AEM author instance and create an AEM environment. In AEM PaaS Mode, AEM versions 6.0, 6.1 and 6.2 are supported.

Please note that the command when run will request the environment name to be input.

To start an AEM publish instance and add it to the environment, use the same command with aem-publish-paas as the -s/--service-name value:

or2ms -s aem-publish-paas --activate -p project -r region --customize

By default, both types of instances will be started as MEDIUM CentOS6_64-bit virtual machines. You can change the shape by using the optional --shape parameter, but the shape should not be smaller than MEDIUM.

Service Customization

AEM PaaS Mode (both author and publish instances) is activated by a Maestro Stack execution which requires certain custom parameters to be specified. For that purpose, the or2ms command has to include the --customize option.

or2ms -s aem-author-paas --activate -p project -r region --customize

With customization enabled, the stack execution allows modifying the default parameter values. The following parameters can be customized during service activation:

Description Type Default Value Required
AEM version string 6.2 No
Environment string empty Yes
AEM instance port number 4502 No
AEM dispatcher apache version string 2.4 No

After the command is executed, the system prompts for parameter values one by one showing the default ones, as well. You can specify a custom value when necessary or skip a parameter to keep the default setting.

Only the 'Environment' parameter is mandatory for AEM PaaS Mode activation. 'Environment' defines the name of the environment in which AEM as a Service in PaaS Mode will be used and links author and publish instances to each other. Specify a unique environment name and make sure that the same name is used for author and publish instances.

Service Manipulations

AEM Basic

EPAM Orchestrator supports the following commands for AEM service manipulations:

  • To get information about the AEM service in your project, use the or2-manage-aem (or2aem) command with the describe action. The command response provides service element details including login URLs and user name/passwords for each element of the cluster:
or2aem -p project -r region -a describe
  • To create a new publish instance, run the or2-manage-aem (or2aem) command with the attach-publish action:
or2aem -p project -r region -s shape -a attach-publish -c cluster_name
  • To detach an existing publish instance and terminate it, use the or2-manage-aem (or2aem) command with the detach-publish action:
or2aem -p project -r region -a detach-publish -i instance_id
  • To deactivate an AEM cluster, use the or2-manage-aem (or2aem) command with the deactivate-cluster action:
or2aem -p project -r region -a deactivate-cluster -c cluster-name

To deactivate a cluster, you need to detach all relative publish instances from it first.

AEM PaaS Mode

When the AEM PaaS Mode has been activated, you can retrieve its details with the or2-describe-services command:

or2dser -p project -r region

To deactivate AEM PaaS Mode, you have to deactivate all service instances one by one. Use the or2ms command with the --deactivate option:

or2ms -s aem-author-paas --deactivate -p project -r region -i instance_id

Web UI

The service provides UIs for both author and publish instances.

For AEM basic, the URLs and login/passwords are given in the or2aem -a describe command response

Use these credentials to login to the necessary instance UI:

Access to AEM in the PaaS Mode is granted via the URL provided in the response to the or2dser command:

Use the admin/admin credentials to log in.

Pricing

The service usage price is defined by the price of the VMs engaged in each cluster.

The default parameters of an AEM instance are:

  • Shape: MEDIUM
  • Image: CentOS6_64-bit

One cluster needs at least two instances - an author and a publish one. Therefore, the approximate monthly cost of a cluster case of 100% and 24/7 load is about $117.17 in EPAM-BY1 region (as to 11/09/2015). The price can vary depending on the region.
To get more detailed estimations, please, use our Cost Estimator tool.

References

More information on the AEM Service can be found in the EPAM Cloud Services Guide. For detailed description of the Maestro CLI commands used to manage the AEM Service, refer to the Maestro CLI User Guide.