AEM/CQ5 : Xpath)

Showing posts with label Xpath). Show all posts

AEM 6.2 Screens

Statement-

Solution: Steps to create new AEM screem Project and Device registration.

http://localhost:8080/screens.html/content/screens --> click on create

Select screen template -->click on Next

Select Master Pages(applications, channels, devices & locations) , enter project title and name -->click on create

Create Sample Project

Steps to create a channels

Navigate to Sampleproject -->Select Channels -->click on create

select Sequence channel -->Next

Enter the title : SampleChannels --> click on Create

Now Sequence channel has been created under the channels.

Steps to author content for the Sequence Channel

Edit the SampleChannels page under touch UI mode

Add the image and Transition component in the edit mode and see the display in preview mode

Steps to create Location:

Navigate to sample Project --> Select Locations folder --> click on create

Select the Lcoation template --> Click on Next

Enter the Location Title --> Click on create

Now location page has been created

Steps to add the display to the locations

/SampleProject/locations/ Select samplelocations --> click on create

Select the Display Template --> Click on Next

Enter the display title --> click on create

Now Display page has been created.

Steps to assign the Channels to the Display created in the above steps

Navigate to the SampleProject/locations/samplelocations --> Select SampleSingleDispaly -->click on Assign channel

Enter the Channel role(some description), Channel created in the above steps , Support events(intial load ..etc) --> click on save

Steps to Install the AEM screen Palyer:

Download AEM screenpalyer for desktop/laptop/mobile or for chrome browser and install it.

AEM screenpalyer for Chrome Browser :

https://chrome.google.com/webstore/detail/aem-screens- player/fbolnednpdinoakkaellgbpedpkmpmip?utm_source=gmail

Post the installation of Screen player Go to this URL : http://localhost:/content/mobileapps/cq-screens-player/firmware.html

Steps to Register the Device for AEM Screens Display

Navigate to /SampleProject -->Select the Device --> Click on Device Manager

Here it shows the Device in which AEM screen player was installed --> click on the Device registration -->

Device with token ID will be displayed

Select the Device and click on Register device

Now it will generate unique ID for that device in to Validate --> click on validate

Enter the device display name and click on Register, That's it

Finally assign this Device to Display -i.e SampleSingleDisplay created under locations. follow the steps to configure as shown in below screenshots.

Click on Assign display

Browse to the path to select the samplecahnnel.

Assign the Channels - SampleChannels that was created

Finally click on assign and then Finish - it will display the Device assigned to Display details as shown below. That's it.

Last but not least click on the preview icon of device to see the channel content for registered device.

Note:
Troubleshooting and Device monitoring Reference URL.https://helpx.adobe.com/experience-manager/6-3/sites/administering/using/monitoring-screens.html

Introduction to AEM screens :
https://helpx.adobe.com/experience-manager/kt/eseminars/gems/aem-introduction-to-aem-screens.html

Screen concepts :
https://helpx.adobe.com/experience-manager/6-2/sites/administering/using/screens.html

Deploying screens:
https://helpx.adobe.com/experience-manager/6-2/sites/deploying/using/screens.html

AEM Purge tool Maintenance or Purge tool Scheduler configurations

Configure to run the Purge version tool to run on weekly basis : follow the steps mentioned in the screenshot.

Scheduler name : Weekly or Daily or monthly based on the need

Purge paths : list of Path name

Purge recursively : traverse the tree while purging for the configured path, enable

Max Version : 5

Max Age in days : 30

AEM Version Auto Purge configuration in Felix Console

Steps for the Auto purge configuration based on the parameter configuration in DAY CQ WCM Version Manager in felix console

Careful while enabling these options based on the business need.

Create version on Activation - Enable
Enable Purging : Check the box
purge paths : Specify the list of paths to be considered for purging
Implicit version paths : path for implicit versioning for active paths
Max version age : Max age in days
Max number versions : Max Version

How to purge Versioning in AEM

Statement : How to purge Versioning in AEM

Environment details:

AEM 6.2
URL to purge for Versioning of content : http://localhost:8080/etc/versioning/purge.html

Scenarios when Versions are created:

AEM creates a new version of pages or nodes when you activate the page post updating the content.
Additional Versioning can be created based on request through versioning tab of side kick and these versions will be stored in the repository and can be retrieved or rolled back to the older version as and when required.

Scenarios when Version will not be created:

without changing any content if you are trying to activate the page, Versioning will not be created. Message will be shown stating that version will not be created because there is no change in the content.

Disadvantages of Versioning:

These versions are never purged and repository size will grow over time,hence repository need to managed.

Advantage of Versioning:

As and when required based on the business need, pages can be reverted back to older version.
New version will be created.

Ways to Manage the Repository :

Purge Version Tool
Version Manager

Purge Version Tool:

URL to purge for Versioning of content : http://localhost:8080/etc/versioning/purge.html

Advantages of Purge version tool:

Reduce the size of repository by removing older version of nodes.
Used for monitoring and maintaining the repository
It allows us to removed older versions of nodes or Hierarchy of nodes according to the parameter set in the below screenshot.

Max Version to Keep : Maximum version to be kept in the repository.

When this number exceeds, older version will be removed.

Max Version in Days : Maximum days of any version to be kept in the repository

When this age exceeds, Older version will be deleted.

Dry run : Simulation of Version purging

Purge : Actually deletes the older version of nodes.

Recursively : Traverse the tree to purge the configured path.

Lets dry run the Purge version tool for the path : /content as shown below.

Under Dry run console :

Post Dry run you can observer retained v.2.0* that means this version of node has been retained from deleting because it has not exceed the configured parameter values.

Now changing the Max version to 1 and Max age to 10

Observations:

- Shows some version purged which are highlighted in red

- Some node shows which are retained.

Auto Purge configuration in Felix Console:

Steps for the Auto purge configuration based on the parameter configuration in DAY CQ WCM Version Manager in felix console

Careful while enabling these options based on the business need.

Create version on Activation - Enable
Enable Purging : Check the box
purge paths : Specify the list of paths to be considered for purging
Implicit version paths : path for implicit versioning for active paths
Max version age : Max age in days
Max number versions : Max Version

Purge tool Maintenance or Purge tool Scheduler configurations

Configure to run the Purge version tool to run on weekly basis : follow the steps mentioned in the screenshot.

Scheduler name : Weekly or Daily or monthly based on the need

Purge paths : Path name

Purge recursively : traverse the tree while purging for the configured path

Max Version :

Max Age in days :