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’)
GraphQL is a query language for APIs that was developed by Facebook. It provides a flexible and powerful way to fetch and manipulate data from AEM, making it easier for developers to build applications on top of the AEM platform. In this blog post, we will explore the basics of working with GraphQL in AEM.
What is GraphQL?
First, let's look at what GraphQL is and how it differs from other API technologies. Unlike REST, which uses a fixed structure for requesting and returning data, GraphQL allows developers to specify exactly what data they want to fetch or manipulate in a single query. This means that developers can fetch only the data that they need, reducing the amount of data that needs to be transferred over the network and improving the performance of their applications.
Major advantages of using GraphQL in AEM
Improved flexibility and control over data fetching and manipulation. Because developers can specify exactly what data they want to fetch, they can optimize their queries for performance and avoid fetching unnecessary data.
Improved performance of AEM-based applications. By reducing the amount of data transferred over the network and allowing developers to optimize their queries, GraphQL can help to make AEM-based applications faster and more efficient.
Strongly-typed language for improved reliability. By defining the types of data that can be queried and manipulated using GraphQL, developers can catch errors at compile time rather than runtime, making it easier to debug and troubleshoot their applications.
Easier integration with other technologies and platforms. Because GraphQL returns data in a JSON format, it is easy for developers to integrate AEM with other technologies and platforms, making it a powerful tool for building complex, integrated applications.
Enabling GraphQL in AEM To use GraphQL in AEM, you will need to create a GraphQL endpoint in AEM. This can be done by creating a new GraphQL servlet in the AEM configuration manager, and then adding the required GraphQL schema and queries to the servlet. The schema defines the types of data that can be queried and manipulated using GraphQL, while the queries specify the actual data that should be fetched or manipulated.
Once the GraphQL endpoint has been set up, developers can use it to fetch and manipulate data from AEM. This is done by sending a GraphQL query to the endpoint, which will then return the requested data in a JSON format. Developers can then use this data in their applications, making it easy to integrate AEM with other technologies and platforms.
One of the key advantages of using GraphQL in AEM is that it allows for greater flexibility and control over the data that is fetched and manipulated. Because developers can specify exactly what data they want to fetch, they can optimize their queries for performance and avoid fetching unnecessary data. This can help to improve the overall performance of AEM-based applications, making them faster and more efficient.
In addition, because GraphQL is a strongly-typed language, it can help to prevent errors and improve the overall reliability of AEM-based applications. By defining the types of data that can be queried and manipulated using GraphQL, developers can catch errors at compile time rather than runtime, making it easier to debug and troubleshoot their applications.
How to Test GrahQL integrated in AEM
To test GraphQL in AEM, you can use the GraphiQL tool, which is a browser-based IDE for testing GraphQL queries and mutations. To use it, you will need to enable the GraphiQL servlet in AEM and access it from the AEM Tools console.
Once you have access to GraphiQL, you can start testing your GraphQL queries and mutations. To do this, you can use the built-in editor to write and execute your queries and mutations, and then view the results in the right-hand panel. You can also use the built-in documentation explorer to view the available schema and queries, which can be helpful when writing your own queries.
In addition to using GraphiQL, you can also test GraphQL in AEM using other tools and frameworks, such as Postman or Apollo Client. These tools can be used to test and debug your GraphQL queries and mutations, and can help to ensure that they are working correctly before deploying them in your AEM-based application.
Overall, working with GraphQL in AEM can provide many benefits for developers. It allows for more flexible and efficient data fetching and manipulation, and can help to improve the performance and reliability of AEM-based applications. Whether you are building a new application on top of AEM or looking to improve an existing one, incorporating GraphQL into your development process is well worth considering.
In this blog, we will see the major difference between InDesign, Framemaker and AEM Guides
InDesign
FrameMaker
AEM Guides/XML Doc
Adobe InDesign is an industry-leading layout and page design software for print and digital media.
Adobe FrameMaker is a document processor designed for writing and editing large or complex documents, including structured documents
AEM Guides is a best-in-class multichannel publishing of DITA content used for product documentation, policies and procedures, long-form marketing content managed through a component content management system. Adobe Experience Manager Guides (AEM Guides) was formerly named XML Documentation for Adobe Experience Manager or simply XML Documentation for AEM.
InDesign is more or less a desktop publishing and layout tool.
FrameMaker is better for Structured & Unstructured documentation with various outputs. Structured FrameMaker documents are used to create consistency in documentation. Unstructured FrameMaker documents use tagged paragraphs and does not impose logical structure.
AEM Guides is mainly for structured content management with in Component Content Management system.
InDesign is all about fine-tuning the output. Content takes a backseat here. focuses on page layout. It is not designed for authoring.
FrameMaker is a word processor that focuses on the authoring part. Mainly used for technical writing. It is mainly designed for the writing part for formatted documents.
Easy-to-use WYSIWYG web editor to create granular, presentation-agnostic, variant-free content.
InDesign supports XML, style sheets, and other coding markup
DITA and XML based publishing
Powerful DITA authoring and content management support. Migrate content from Word, XHTML, IDML, and more, to DITA with the out-of-the-box ingestion framework.
Limited features like content creation and design.
Moderate features like content creation with less design capability and advanced publishing.
Features include content reuse, version management, reference management, search and metadata tags management, translation workflows and content health reports to assume complete control of your content
Best for small number of pages. It is complex to maintain a lot of content in InDesign.
Supports larger number of pages.
Supports larger number of pages.
We can create beautiful graphic designs with typography from the world’s top foundries and imagery from Adobe Stock. Great for making brochures or magazines, stationery, flyers and posters to brochures, annual reports, magazines and books
For technical documentation with headings, chapters, and sections, like user manuals, you definitely want to be using a topic-based tool with structured authoring, like FrameMaker.
Delivering content to Adobe Experience Manager Sites, mobile apps, knowledge bases, CRM platforms, IoT Apps, chatbots, PDF, HTML5, EPUB, KINDLE, and more.
Review options: "Share for Review" option within InDesign to initiate collaborative reviews with stakeholders and receive feedback without having to navigate to a different app
FrameMaker supports many ways of setting up review and collaboration which includes multi level reviewers.
Web-based review and collaboration: Allow multiple authors and reviewers to collaborate simultaneously in real time even when operating remotely.
Integrate with Adobe Experience Manager
Integrate with Adobe Experience Manager (through connector)
AEM Guides is installed directly in AEM. Native integration with Adobe FrameMaker, Oxygen & other desktop tools for import and export of DITA (for e.g. AEM Desktop app, WINSCP)
Static metadata information is stored using the Extensible Metadata Platform (XMP) standard for images and files and can be imported and exported.
Static metadata information is stored using the Extensible Metadata Platform (XMP) standard for images and files and can be imported and exported.
Dynamic Metadata support available. The metadata can be imported exported, used for tagging and many other use cases.
No reporting for the content
No reporting for the content
Reporting options Available to get an idea on content reuse, version history, DITA map & Link references.
No OOTB Translation available. The inDesign document should be exported to InDesign Markup (IDML) format and has to be translated with the help of external tralstaors.
Out of the box translation support with XLIFF available in Framemaker. We can also use third party translator by exporting the content.
Industry-leading translation management and localization support by utilizing the AEMs built in translator (both DITA + content) & Third party translator support.
Simple find and search support available.
Flexible search includes searching through a book, bookmap, or DITA map
Comprehensive search and content usage data option available.
In upcoming blog, we will see more details about Adobe RoboHelp
