Tuesday, 10 June 2014

Replication agents & DAM


Replication agents:
-----------------------------
They help to publish the content. Replication agents are mapped to publication. So when we need more than one publish environment, we need replication agents for each one.
Access replication agents through Tools>Replication


Publish flow:

Once site is developed it should be activated by going website> activate
It send alert to replication agent, the request will be put in a queue will be formed for it.
We can restrict continuous attempts of publish through Agents>Setting>Extended> connect time out.
Settings
On modification - helps to publish a page immediately after modification
Activating (publishing) more pages together in AEM/Adobe cq
Access replication tree using below url.
http://localhost:4505/etc/replication/treeactivation.html
Now activate more pages by selecting pages or entire directory.
How to publish a Component immediate after creation or modification?
Push component to publish through Crxde lite by selecting component, then go to replication tab, click on replicate. This will send component immediately to publish.



We have manual way of publishing through build bundle-> install to publish environment. Easier solution to publish content is,we can use direct replicate for the package. For this ensure you configured replication agents.




DAM:
----------
Thumbnails are created automatically in DAM because it is defined default by Adobe in workflow:
http://localhost:4505/cf#/etc/workflow/models/dam/update_asset.html : step> Thumbnail creation
Use sidekick > DAM workflow to create dam related workflows.
All items we uploaded can be seen in CRXDE through http://localhost:4505/crx/de/index.jsp#/content/dam
References section gives the list of all references from pages for an image. Double click on image and see right top (renditions,versions,references)
Securities:
Change admin or author passwords:
------------------
1)
http://localhost:4505/crx/explorer/index.jsp > 'Content explorer' opens below url
http://localhost:4505/crx/explorer/browser/index.jsp
now
Security > change password.
2)
http://localhost:4505/crx/explorer/index.jsp > 'User Administration' opens below url
http://localhost:4505/crx/explorer/ui/usereditor.jsp?ck=1402297401235&Path=/home/users
Select a>admin>change password
Create or delete users canbe done through http://localhost:4505/useradmin.
All users’ preferences can be done through above url.

OSGi component Vs CQ component:
OSGI-Backend part- business component;
CQ-front end part
OSGI bundle can have many no of osgi components and each component can have many services.

-------Similar Posts---------------
Mapping of requests in AEM
Interact With AEM
Run Modes
AEM
Apache Sling in AEM

-------------------------------------

Debug mode:
In start.bat > CQ_JVM_OPTS parameters : add>
-agentlib:jdwp=transport=dt_socket,server=y,address=30303.suspend=n
Read More:
http://helpx.adobe.com/experience-manager/kb/CQ5HowToSetupRemoteDebuggingWithEclipse.html

AEM/ Adobe CQ: Version controlling



AEM/ Adobe CQ: Version controlling

CQ uses svn by default.
Filevault ( VLT)is used when we need crx file system to be available in local system(like accessing code using eclipse).
Create back up of crx code using file vault
To set up the filevault, we need to unzip the filevault file and configure its bin path to system path variable.
Export project from CQ to local machine
c:\CQ5_training\backup>vlt --credentials admin:admin export -v http://localhost:4505/crx /apps/training .
Above command creates a jcr_root folder in backup folder and put all files from crx
Import Project from Local file system to CQ
c:\CQ5_training\backup>vlt --credentials admin:admin import -v http://localhost:4505/crx . /apps/training
Once user credential is entered, it is not required again bcz, the user credential is saved in user directory> vault folder as an xml file.
Checkout just directory structure, not entire project
backup>vlt -co http://localhost:4505/crx/-/jcr:root/apps/training .

Identify locally modified files, execute below command.
jcr_root>vlt -st

Identify difference in local and crx files, execute below command.
jcr_root>vlt -diff complex/components/test.jsp
jcr_root>vlt diff will give all changed fields comparison in jcr_rot checked out directory

commit changes to code repository:
All files:
jcr_root>vlt - ci
Single file commit:
jcr_root>vlt - ci filename

Note: ci,st,diffcommaond only works withchecked out code , not exported code.

-------Similar Posts---------------
Mapping of requests in AEM
Interact With AEM
Run Modes
AEM
Apache Sling in AEM

-------------------------------------

Filevault commands reference:
Command             Description
export             Export the Vault filesystem

  import            Import a Vault filesystem

  checkout (co)      Checkout a Vault file system

  analyze            Analyze packages

status (st)        Print the status of working copy files and directories.

update (up)        Bring changes from the repository into the working copy.

info               Displays information about a local file.

commit (ci)        Send changes from your working copy to the repository.

revert (rev)       Restore pristine working copy file (undo most local edits).

resolved (res)     Remove 'conflicted' state on working copy files ordirectories.

propget (pg)       Print the value of a property on files or directories.

proplist (pl)      Print the properties on files or directories.

propset (ps)       Set the value of a property on files or directories.

add                Put files and directories under version control.

delete (del,rm)    Remove files and directories from version control.

diff (di)          Display the differences between two paths.

rcp                Remote copy of repository content.

  sync               Control vault sync service

  console            Run an interactive console


Workflow, performance monitoring, logging in AEM


Workflow:

Used to automate process involved in page creation to publish.
http://localhost:4505/libs/cq/workflow/content/console.html
Launcher workflow enables to automate the workflow in AEM.
·         Instance tab shows running workflows which can be suspended or cancelled.
·         Models list all work flows created.
·         Archive : shows completed workflows
·         Failures: Shows all the failed workflows.

Error /Failure in Workflow custom process "Process implementation not found: "
The reason may be you are creating bundle using CRXDELite and below codes are commented.
#Export-Package: *
#Import-Package: *

Solution:So you have to uncomment to get the workflow success.

-------Similar Posts---------------
Mapping of requests in AEM
Interact With AEM
Run Modes
AEM
Apache Sling in AEM

-------------------------------------

Performance:
Logging
Request.log files will have all requests logged. Monitoring this log is the best way to track performance issues. We can also use some profilers to tackle the performance issues.
Tool helps to track last few requestsAuthor\crx-quickstart\opt\helpers > rlog.jar
To access logs,
From command prompt reach to the location of rlog.jar then > execute java -jar rlog.jar -n 10  ../../logs/request.log will give all slowest responses.
Readable: http://dev.day.com/docs/en/cq/current/deploying/performance.html
Timing chart URL will also help to find the performance timing of any page loading.
Common performance improvement methods: http://helpx.adobe.com/experience-manager/kb/performancetuningtips.html

AEM/CQ Common issues




Rectify Content Assist issue in AEM/ Adobe CQ(5.6)
-------------------------------------------------
We need CRXDE to have installedfuture pack to get content assist for JSP pages
Download link: http://blogs.adobe.com/livecycle/2012/06/developers-faq-on-cq5-5.html
·         Missing crx de libs(missing-crxde-libs.zip) to be install through package manager.
·         Now rename or delete user>.crxde folder, restart the crxde so that content assist works fine.

  -------Similar Posts---------------

Mapping of requests in AEM
Interact With AEM
Run Modes
AEM
Apache Sling in AEM
-------------------------------------
Notes: Some times cq5.6 gives error on jsp pages. Remove below codes to avoid issues:
header.jsp
<cq:include path="toptoolbar" resourceType="foundation/components/toolbar"/>
footer.jsp
<cq:include path="toolbar" resourceType="foundation/components/toolbar"/>



Error /Failure in Workflow custom process "Process implementation not found: "
The reason may be you are creating bundle using CRXDELite and below codes are commented.
#Export-Package: *
#Import-Package: *

Solution:So you have to uncomment to get the workflow success.