Menu

Rapid Development Environment (RDE) in AEM as a Cloud Service

Rapid Development Environment (RDE) in AEM as a Cloud Service is a new environment that you could include in your dev or prod instance on demand for quick deployment, this helps the AEM developers to quickly deploy the changes from local machine build just like we are doing package and bundle install using package manager.
Since AEM as CS package manage doesn't allow to deploy the code changes due to immutability of the system, but AEM as CS package manager allow to upload and install the content packages that includes paths like /content, /etc. 
Here, instead of using package manager for deployment RDE is using AppBuilder and pushing the locally build zip, jar files in AEM as CS RDE instance. Below are the detail about the Rapid Development Environment in AEM as CS development environment setup and uses of it.

How to setup Rapid Development Environment in AEM as CS?

1. First we need to enable the RDE instance for that you have to contact Adobe CSE/Support to get that enable under your license.
2. We need to install node and adobe cli to make the development setup and running in local machine.  
To enable and setup follow the steps given here: How to set up Rapid Development Environment | Adobe Experience Manager

How to use Rapid Development Environment in AEM as CS?

Using Rapid Development Environment is easy using adobe cli, for every task we have to just run one liner command on cli. To learn more and see the steps and action that is possible with RDE please follow the steps given in this document; How to use Rapid Development Environment | Adobe Experience Manager

Rapid Development Environment is going to make the developer life easy and this could be use by a developer at a time. Multiple developers could also use but that required very frequent sync between developers code. The biggest advantage of rapid development environment is that; we now use a full AEM as cloud service instance as a local. Where one can make the changes and deploy the code on cloud service without commit, and running the cloud manager CICD pipeline which taking approximately 40 minutes to make our code live on any AEM CS instance. 

References

at No comments:
Labels: , ,

10 most beautiful buildings around world

Here are 10 buildings around the world that are widely regarded as beautiful:
  1. Taj Mahal, India
  2. Sydney Opera House, Australia
  3. Sagrada Familia, Spain
  4. Eiffel Tower, France
  5. St. Basil's Cathedral, Russia
  6. Burj Khalifa, UAE
  7. Guggenheim Museum, USA
  8. Neuschwanstein Castle, Germany
  9. Petra, Jordan
  10. The Parthenon, Greece

1. Taj Mahal, India

Taj Mahal, Agra, India

2. Sydney Opera House, Australia

Sydney (AU), Opera House -- 2019 -- 2280

3. Sagrada Familia, Spain

4. Eiffel Tower, France

5. St. Basil's Cathedral, Russia


Храм Василия Блаженного №2
6. Burj Khalifa, UAE

7. Great Pyramids of Giza, Egypt

8. Neuschwanstein Castle, Germany

9. Petra, Jordan

10. The Parthenon, Greece

at No comments:
Labels: , , , , ,

How to create an experience fragment in AEM?

Below are the steps to create an Experience Fragment (XF) in AEM:
  1. Open AEM and navigate to the Assets console.
  2. Click on the Experience Fragments folder on the left side of the console.
  3. Click on the "Create" button at the top of the console and select "Experience Fragment" from the dropdown menu.
  4. Fill in the required fields in the "Create Experience Fragment" dialog box, including the XF's name, title, and description. You can also select a thumbnail image to represent the XF.
  5. Click on the "Create" button to create the XF.
  6. Once the XF has been created, you can begin authoring it by clicking on the "Open" button next to its name in the Assets console.
  7. The authoring mode for an XF is similar to the standard AEM authoring environment. You can add components and content to the XF, as well as define variations that can be used to tailor the XF for different audiences or use cases.
  8. Once you have finished authoring the XF, you can publish it to make it available for use in your AEM sites. To publish the XF, select it in the Assets console and click on the "Publish" button at the top of the console. You can choose to publish the XF as a draft or a final version, and select the channels or audiences that should have access to it.
  9. After the XF has been published, you can use it in your AEM sites by adding it as a component to a page or template. When the page or template is rendered, the XF will be displayed with its defined content and variations.
at No comments:
Labels: , , , ,
Subscribe to: Posts (Atom)