New Features and and Functions Functions:: AEM Sites Author Touchopt i mi zedAut hor i ng Ex per i enc eMa Manager6i nt r odu cesat ouc hop t i mi z edex per i e nc eaut hor i ngus eri nt er f ac e.Thi sa l l owsc ont entedi t or s t ol e v er a get a bl e t san dc omp ut er swi t ht o uc hs c r e ent oe ffic ffic i e nt l yc omp os ee x pe r i e nc es .Th ei mp r o v ede di t o r si n cl u de i npl ac et e xtandi mageedi t i ng. Touchopt i mi zedUI-AConsol e t es TheSi c on so l eoft h et o uc ho pt i mi z edUIa l l o wsy out ona v i g at ea ndma ma na gey ou rwe bs i t e ,u si n gt h eh ea de rb a r ,
na vi gat i onr ai l ,t ool bar ,ac t i oni c ons( appl i c abl ef ort hes el ec t edr es our c e)a ndwhens el ec t ed,s ec ondar yr ai l s( f or e x ampl e,r ef er enc es ,t i mel i neandsear c h) :
Touchopt i mi zedUI-PageAut hor i ng
Yo uc aned i tapa gewi t ht h et o uc ho pt i mi z edUI ,u si n g( f o re x a mp mp l e )t h ec omp on en tb r o ws er :
NSI GHT CONTENTI Co nt e ntI n s i g htp r o v i d esi n f o r ma t i o na bo utp ag ep er f o r ma nc eus i n gwe ba na l y t i c sa ndSEO r e c omme nd at i o ns .Us e Co nt e ntI n s i g htt oma ma k ed ec i s i o nsa bo uth owt omo mo di f yp ag es ,o rt ol e ar nho wp r e v i o usc h an ge sha v ec ha ng ed p er f o r ma nc e.Fo re v er yp ag et h aty o ua ut h or ,y o uc anop enCo nt e ntI n si g htt oan al y s et h ep ag e. AEM brings in interesting information to help a content author create better content. Content Insight brings Insight brings charts about how your content is doing on the site site or it could be a list of recommendations recommendations from third party providers. These providers (like BrightEdge BrightEdge)) can seamlessly integrate with AEM when enabled. ow to access content insight!
NG APPAUTHORI Creating a Mobile Application
The following procedure uses the Touch UI to create a mobile application.
. !n the rail" clic# Apps.
$. %lic# or tap the %reate icon.
&. '!ptional( !n the Ad)anced tab" pro)ide a description for the application" and change the ser)er U*+ if re,uired.
-. '!ptional( If ou are using /hone0ap 1uild to compile the application" on the 1uild tab" select the %on2guration to use.
3. To create a /hone0ap build con2guration" clic# Manage %on2gurations.
4. '!ptional( If ou are using Site%atalst to trac# application acti)it" on the Analtics tab" select the con2guration to use.To create a Mobile App on2guration" clic# Manage %on2gurations.
5. '!ptional( To pro)ide an application icon" clic# the 1rowse button" select the image 2le from our 2le sstem" and clic# !pen.
6. %lic# %reate.
GI T ALASSETMANAGEMENT DI ( DAM) Met adat aandsear chenhancement s
Search made easier. Enhancements in metadata management and search allow power users and end users of digital asset management to wor# more e7cientl" and customi8e sstem beha)ior in these areas through UI. 1ul# metadata editing" automated metadata assignments upon ingestion" smart collections 9 sa)ed searches" and de2ning metadata forms for assets and faceted search are all a)ailable with optimi8ed UIs Metadata Schema Editor: Abilit to customi8e the metadata based on an asset tpe Metadata /rocessing /ro2le: Abilit to appl prede2ned meta data to assets that are uploaded in a folder
AEM Sites Architecture and !a# J ac kr abbi tOaki saneff or tt oi mpl ementas c al abl eandper f or manthi er ar c hi c al c ont entr epos i t or yf or us east hef oundat i onofmoder nwor l d c l as swebs i t e sandot herd emandi ngcon t en ta ppl i c at i on s.
WHYOAK J ac kr abbi t2. xi sas ol i dandf eat ur er i c hc ont entr epos i t or yt hatwor k swel l es pec i al l yf ort heneeds oft r adi t i onal webs i t esandi nt egr at edc ont entmanagementappl i c at i ons .Ho we ver ,t het r endsi n us erex pec t at i ons( e spec i al l yf orper s onal i z ed,i nt er ac t i v eandc ol l abor at i v ec ont ent ) ,appl i c at i on ar c hi t ec t ur es( d i s t r i but ed,l oos el ycoupl ed,mul t i pl at f or ms ol ut i onswi t hl ot sofdat a)andhar dwar e des i gn( hor i z ont al r at hert hanv er t i c al s cal i ng)hav er ender eds omeoft heor i gi nal J ac kr abbi t d es i gnde ci s i o ns( whi c hd at eba ckal mo s tade c ad e)o bs ol e t ean dt h er ei snoe as ywa yt o i nc r e ment a l l yu pd at et hedes i g n. J ac k r a bbi tOakai mst oi mpl ementasc al abl eandper f or manthi er ar c hi c al c ont entr epos i t or yf or us ea st hef oundat i onofmo der nwo r l dc l as swe bs i t esandot herdema nd i ngcont entappl i c at i on s. Th er e po s i t o r ys h ou l di mp l e me nts t a nd ar d sl i k eJ CR,We bDAVa ndCMI S,a ndbeea s i l y ac c es si bl ef r om v ar i ouspl at f or ms ,es pec i al l yf r om J av aSc r i ptc l i ent sr unni ngi nmoder nbr ows er en vi r onment s .Thei mpl ement at i ons houl dpr o vi demor eout of t hebo xf unc t i onal i t yt hant y pi c al No SQLd at a ba se swh i l ea ch i e v i n gc o mp ar a bl el e v el sofs c al a bi l i t yan dpe r f or ma nc e .
"ith AEM #.$ the content repository is based on OAK (Jackrabbit3, JSR283
(JCR2.0) specication)! Main ob%ectives of new &ak content repository! Enhance scalability
1etter support for big repositories
Multiple distributed cluster nodes for high a)ailabilit
Impro)e /erformance
'mprove erformance
/arallel writes
rite performance
Support for man child nodes and A%+s
The &ak Microernel A' provides the layer for actual storage of content. *urrently+ there are two Microkernel implementations available in AEM#!
"arMK an# MongoMK The "arMK (#e$a%lt) uses tar files as storage and in MongoMK the repository is kept in Mongo ,B.
AEM forms & '"RO*C"'O "O A+M ORMS AEM forms e;tends engaging web and mobile e;periences to enterprise forms and documents" allowing organi8ations to complete comple; digital interactions while impro)ing user e;periences and e;tending business reach. AEM forms includes authoring" managing" and publishing of forms with wor#
engaging end=to=end e;periences. >esigned to wor# across web and mobile channels" AEM forms can be e7cientl integrated into our business processes" reducing paper processes and errors while impro)ing e7cienc. AEM forms le)erages and e;tends the capabilities of our e;isting in)estments in ?FA forms and Adobe +i)e%cle solution
2 'S"A--' A CO'*R' A+M ORMS In AEM @uic#Start" ou are limited to the following capabilities of AEM forms: • • • •
%reating and Managing Adapti)e Forms 'without ?FA=based templates( Using Forms /ortal components to +ist adapti)e forms on a eb /age Using Forms Manager to create and Manage adapti)e forms Submiting forms and handling AEM wor#
Install AEM forms add=on pac#age to enable the following capabilities of AEM forms: • •
•
• • •
Support for ?FA=based form Template=based Adapti)e Forms Support to manage and use ?FA=based forms in AEM forms UI" forms portal components" and adapti)e forms. %onnectors to integrate Enterprise %ontent Management sstems 'E%Ms( with forms wor#ocument ser)ices A/I" which includes: . Forms ser)ice $. !utput ser)ice &. Assembler ser)ice -. >oc Assurance ser)ice" which includes: 3. Signatures ser)ice 4. %erti2cation ser)ice 5. *eader E;tension ser)ice
3 A*"/OR' A+M ORMS Create an a#aptie $or1 base# on an A or1 "e1plate
Follow these steps to create an adapti)e form. . Access AEM forms Author instance at http:99ser)erB:portB9Ccustom=conte;t= if=anD. $. Enter our credentials on the AEM login page. !n the left panel" clic# the Forms lin#. Note: For a default installation" the login is admin and the password is admin.
&. %lic# and select %reate adapti)e form.
-. The a)ailable templates are displaed. %lic# a template to select it and clic# Ne;t. Note:To get the complete template pac#age including ad)anced templates" install the AEM forms pac#age. For more information" see AEM forms pac#age.
3. Enter a name" title" and description for the form
4. In the Add /roperties tab" select the Form Model tab.
5. Select a form template from the list of forms displaed in Forms Manager. Associate ?FA Form Template with an Adapti)e Form
6. %lic# %reate.
hen ou open the adapti)e form in editing mode" ou can access the form template components in the %ontent Finder" from the adapti)e form data model tab. From this tab ou can drag=and=drop the ?FA form components in to our adapti)e form.
CR+A"' A C*S"OM AA4"'5+ ORM "+M4-A"+ An Adapti)e Form template is speciali8ed AEM /age Template" with certain properties and content structure that is used to create Adapti)e Form. The template has precon2gured laouts" stles" and basic initial content structure. !nce ou create a form" an changes to the original template content structure are not re
Na)igate to %*?>E +ite on our authoring instance.
•
• • •
•
Under the 9apps director" create the folder structure for our application. For e;ample" if the application name is training" create a folder with this name. Tpicall" the application folder contains components" con2guration" templates" src" and installation directories. For this e;ample" create the components" con2guration" and templates folders.
Na)igate to the folder 9libs9fd9af9templates. %op the simpleEnrollmentTemplate node. Na)igate to the folder 9apps9training9templates. *ight=clic# it and select /aste. If necessar" rename the template node ou copied. For e;ample" rename it as from=template.
•
•
Na)igate to the location 9apps9training9templates9form=template9cr:content.
Modif the cr:title and cr:description properties for the cr:content node to distinguish the template from the template ou copied.
•
•
• •
•
The cr:content node of the modi2ed template contains the guide%ontainer and guideformtitle components. guide%ontainer is the container that holds the adapti)e form. The guideformtitle component displas the application name" description" and so on. Instead of guideformtitle" ou can include a custom component or the parss component. For e;ample" remo)e guideformtitle" and add a custom component or the parss component node. Ensure that the sling:resourceTpe propert of the component references the component and the same is de2ned in the page component.sp 2le.
Na)igate to the location 9apps9training9templates9form=template9cr:content. !pen the /roperties tab and change the )alue of the c,:design/ath propert to 9etc9designs9trainingdesign. Now create a 9etc9designs9trainingdesign node for the c,:/age tpe.
Create an a#aptie $or1 page co1ponent! •
•
• •
•
Modif the )alue of the propert sling:resourceTpe for 9apps9mcompan9templates9enrollment=template9cr:content to 9apps9training9components9page9formpage. %op the node 9libs9fd9af9components9page9base to the folder 9apps9mcompan9components9page. *ename the copied component to formpage. For the formpage node" set )alue of the propert sling:resourceSuperTpe to training9components9page9contentpage. The contentpage component is the base page component for our site. !ther page components can e;tend it. *emo)e script 2les under formpage" e;cept head.sp" content.sp" and librar.sp. The sling:resourceSuperTpe component" which is contentpage in this case" includes all su ch scripts. eaders" including na)igation bar and footer are inherited from the contentpage component. !pen the 2le head.sp.
•
•
•
•
•
•
•
The GS/ 2le contains the line Cc,.include scriptHlibrar.sp9D.
The librar.sp 2le contains the guide.theme.simpleEnrollment client librar" which contains the stling for the adapti)e form.
The page component formpage has an e;clusi)e head.sp 2le that o)errides the head.sp 2le of the contentpage component. Include all scripts in the head.sp 2le for the contentpage component to the head.sp 2le for the enrollmentpage component.
In the content.sp script" ou can add additional page content or references to other components that are included when a page renders. For e;ample" if ou add the custom component applicationformheader" ensure that ou add the following reference to the component in the GS/ 2le:
Cc,:include pathHapplicationformheader resourceTpeHtraining9components9applicationformheader9D
Similarl" if ou add a parss component in the template node structure" also include the custom component.
6 A+M S'/"-7 RACK+"S +"+S'O
Sightl is the new TM+ templating sstem introduced with Adobe E;perience Manager 4.J. The AEM Sightl 1rac#ets E;tension pro)ides a smoother de)elopment wor#
• •
•
Sightl snta;=highlightingL code=completion for Sightl e;pressions" data=sl= bloc# elements and Use= A/I Ga)a obectsL bidirectional snchronisation.
/O9 "O 'S"A-- "/+ A+M S'/"-7 RACK+"S +"+S'O . !pen 1rac#ets. In menu ile" select +:tension Manager;
2. Enter sightl in the searc< bar and loo# for the AEM Sightl 1rac#ets
E;tension.
&. %lic# 'nstall. -. *estart 1rac#ets when as#ed.
9ORK' 9'"/ "/+ A+M S'/"-7 RACK+"S +"+S'O "/+ CO"+"=4ACKA+ 4ROJ+C" After the e;tension has been installed" ou can start de)eloping AEM components b either opening a content=pac#age folder from our 2le sstem with 1rac#ets or b creating the structure for one from within the editor. The proect has to contain at least: . a crroot folder 'e.g. mproect9crroot( $. a 2lter.;ml2le 'e.g. mproect9META=INF9)ault92lter.;ml(L for more details about the structure of the2lter.;ml 2le please see the or#space Filter de2nition.
S 7C/RO'SA"'O S+""'S In order to snchronise our content to and from an AEM ser)er ou need to de2ne our Snchronisation Settings. This can be done b going to Sig D 4ro?ect Settings... The menu entr can also be accessed through shortcuts: O=Shift=/ on a Mac or %trl=Shift=/ on a /%.
The Snchronisation Settings allow ou to de2ne: . the ser)er U*+ 'e.g. http:99localhost:-3J$( $. the username used for snchronising content &. the userPs password The settings will be sa)ed in our proectPs root folder" in the .brac#ets.son 2le" e.g.mproect9.brac#ets.son. e donPt recommend sa)ing this 2le in our S%M sstem.
S 7C/RO'S' CO"+" The AEM Sighl 1rac#ets E;tension pro)ides two tpes of content snchronisation.
1.A%to1ate# s>nc
is allowed to be snchronised b the 2ltering rules de2ned in 2lter.;ml" these 2les will be snced to the AEM ser)er on=sa)eL for .content.;ml2les their parent folders will be snchronised .
2.Onde ma ndbi di r e ct i ona ls ync hr oni s at i on through the /roect E;plorer conte;tual menu entries = +:port to Serer or '1port $ro1 Serer = if the selected entr belongs to the crroot folder
.
full content=pac#age snchronisation through the Sightl top=le)el menu" b selecting either: +:port Content 4ackage = O=Shift=E on a Mac" %trl=Shift=E on a /% '1port Content 4ackage = O=Shift=I on a Mac" %trl=Shift=I on a /%
The AEM Sightl 1rac#ets E;tension adds a noti2cation icon on the main toolbar" in the bottom right corner of the 1rac#ets window. After a snchronisation operation is performed the noti2cation iconPs colour changes to indicate the snchronisation status: green = all 2les ha)e been snchronised successfull ellow = some of the 2les were not snchronised successfull red = none of the selected 2les were snchronised
blue = a snc operation is in progress o)ering with our mouse cursor abo)e the noti2cation icon will ma#e a tooltip appear with a summar of the last snchronisation operation. %lic#ing on the noti2cation icon will open the Snchronisation Status report dialog" oKerring more detailed information about each 2le from the content tree ou snchronised.
The AEM Sightl 1rac#ets e;tension also supports .)ltignore 2les for e;cluding content from snchronising to and from the repositor .
