Renewing specific Adobe
certifications is simplified through an alternative to the standard proctored
exam. By following these steps, you can renew your certificates:
1. Engage with Adobe learning
tutorials relevant to your certification.
2. Successfully complete three sets
of assessments.
3. Obtain your renewed certificates
upon completion.
Now once the learning sections are completed, go to course
assessments
·Step 3:
Complete the assessment as given below,.
It will open up non proctored exams.
Once you complete any of the conditions(Below given), your
certificates will be updated.
Option A:
Choose three courses from the available options and ensure you pass each course
assessment with a score of 80% or higher. These assessments are free,
on-demand, non-proctored, and allow open-book referencing. You can retake the
courses as needed until you achieve the required passing score of 80%.
Option B:
Begin by selecting two courses to undertake and ensure you pass each course
assessment with a score of 80% or higher. These assessments are free,
on-demand, non-proctored, and permit open-book referencing. Repeat the courses
if necessary until you achieve the passing score of 80%.
As an AEM Developer, we always wanted a faster deployment process enabled in AEM as Cloud Service Environments. There is a good news for all of us!
Why we need faster deployments?
Being a curious developer, one of the newly developed feature we wanted to test quickly but we know usually a deployment takes an average of 40 minutes in AEM cloud service. The average time for Adobe Experience Manager (AEM) cloud deployment can vary depending on several factors, such as the complexity of the implementation, the size of the content repository, the number of customizations required, and the chosen cloud deployment model. Why the deployments take time on AEM as Cloud Service Environments and what is the relevance of a Rapid Development Environments (RDEs)?
Usually a code deployment on AEM as cloud service goes through a set of code security and quality rules which makes it a slow process. Assume a new feature has to be tested quickly on AEM as cloud which is already working on AEM as cloud local sdk. Using RDE, a developer can quickly deploy the changes and test it. And successful RDE tested code can be deployed through normal AEM as cloud deployment pipelines.
What is the new feature ‘Rapid Deployments’ in AEM as cloud service which enables quick deployments?
Rapid deployments in Adobe Experience Manager (AEM) as a cloud service refers to the ability to quickly and efficiently deploy AEM instances in the cloud. Rapid deployment is achieved through a combination of pre-configured environments, CLi plugins, and configurations.
RDE provides below advantages
-RDE enables a faster development cycles -Efficient Testing on a ‘near to prod’ environment which gives confidence to developers -Enables collaboration between developers to test related features by increasing productivity -Avoids the long waiting deployment process
By default RDE gets set to the most recent AEM version.
How developer works on RDEs
The developer uses command line tools to invoke the RDEs on cloud.
Once the user is done with a feature testing and a successful local build completion, he can use the CLI commands to invoke the RDE deployment. If multiple developers want to use RDEs, they will have to commit the code in feature branch /club the code and use CLI to test the feature at a time.
How do we work with RDEs?
Please ensure the developer is having latest version of Adobe I/O Runtime Extensible CLI . Steps given below,
Step1
$ npm install -g @adobe/aio-cli - To install the Adobe I/O Runtime Extensible CLI, $ aio plugins:install @adobe/aio-cli-plugin-cloudmanager - To Install Cloud Manager plugin $ aio plugins:install @adobe/aio-cli-plugin-aem-rde - To install AEM RDE plugin $ aio aem:rde:status - To verify the AEM RDE plugin installation and configuration
Step 2
Once basic installation is done, we need to configure few things, $ aio config:set cloudmanager_orgid <org-id> - Set the organization id of RDE $ aio config:set cloudmanager_programid <program-id> - Set the program id of RDE $ aio config:set cloudmanager_environmentid <env-id> - Set the environment id of RDE
Step 3
Validate the configurations now using below command, $ aio config:list - To verify the current config values
Step 4
Once above steps are completed, do a code build on developer machine using below command mvn clean install -PautoInstallSinglePackage
Step 5
After successful code build, developer can use CLI commands to push the code/ packages to RDE environment.
Note: If one developer wants to use the RDE for new feature testing, he will have to ensure the RDE is ‘reset’ before new deployments.
A pictorial representation of the RDE development flow is given below.
What all can be deployed using RDE approach
- [+] AEM code & content package (all, ui.apps) - [+] OSGi bundle and config files - [+] Any individual files like HTL, .content.xml (dialog XML) - [+] Apache and Dispatcher configs deployment as a zip file
Is this(RDE) feature available for all readily? This is an on-demand feature at present, we will have to contact Adobe for enabling this feature. But every licensed customer is expected to get an RDE each in couple of weeks from now and additional RDE is license based.
How do we enable it once RDEs are provisioned? In the ‘Environments’ > Add Environment section, we have a new options called ‘Rapid Deployment’. Once you provide necessary details, we can see the new rapid deployment added under environment section.
Will RDE work for sandbox programs? Yes, RDE works for sandbox programs as well as production programs
Few useful commands for RDEs (assuming we have a ‘sample aem wknd guides project’)
