JaideepBrar, much appreciate responding to your quick response. I would
agree with your rationale that if the implementation does not have any
option (to turn on/off hostname verification), it does not implement it.
May I ask where I could view the code for
"com.day.cq.mailer.DefaultMailService" implementation? Thanks again
The client is using AEM 6.4 SP2. The corporate mail server uses TLS.
hence, in the Day CQ Mail Service, the TLS has been enabled. The
corporate mail server also requires that the mail sender turn off the
hostname verification. Is there any way, the Day CQ Mail Service can
turn off the hostname verification?The alternative would be to write a
custom "send mail" code that has the hostname verification turned off.
Of course, the first preference would be to use the out of of box Day CQ
Mail Service...
smacdonald2008 Since you got in touch with Adobe folks in Aug 2017, is
there any fresh update on the guidance about with Archetype to use for
6.3 and 6.4.Now Archetypes 12, and 13 are available: GitHub -
Adobe-Marketing-Cloud/aem-project-archetype: Maven template to create a
new Adobe Experience Manager (AEM) proj…However, Archetype 11 is the
only one that works for me.For Archetypes 12, and 13, I am
getting:Unable to create project from archetype
[com.adobe.granite.archetypes:aem-project-archet...
Praveen- It is default pom.xml with default host, port, user, and
password. However, since I am usingmvn clean install
-PautoInstallPackage -Daem.host=remoteserver -Daem.port=4502
-Dsling.user=admin -Dsling.password=the default credentials
would be overridden.
Scott-Locally, it works perfectly well. No errors when executing:mvn
-PautoInstallPackage installIt even works well on the AEM instance that
is on another VM on local network
When running the maven clean install command: mvn clean install
-PautoInstallPackage -Daem.host=remoteserver -Daem.port=4502
-Dsling.user=admin -Dsling.password=I am getting:[DEBUG]
Authorization required[DEBUG] Supported authentication schemes in the
order of preference: [ntlm, digest, basic][DEBUG] Challenge for ntlm
authentication scheme not available[DEBUG] Challenge for digest
authentication scheme not available[INFO] basic authentication scheme
selected[DEBUG] Using authentication scheme: ...
Sorry for the late response. Unless you have already figured out the
answers to the questions, here are quick pointers: - Total
articles/stories in site: To get all the pages that meets your search
criteria, I guess you are looking at building search in OSGi using
javax.jcr.query. Queries such as: SELECT * FROM [cq:Page] AS s WHERE
ISDESCENDANTNODE(s, '/content/yourapp'). Take a look at 9 JCR-SQL2
Queries Every AEM Developer Should Know | 6D Labs- Unique id of all
stories: Try jcr:uuid property-...
There are two ways you could achieve your objective of doing one-way
synching from AEM to ASP.NET.The first solution is on the assumption
that you do not want to change ASP.NET – MSSQL relationship. MSSQL would
remain source of truth for ASP.NET and as long as MSSQL tables are
synched up by AEM, everyone is happy. Write a custom workflow in AEM
that has a process step, which calls a service or calls MSSQL database
(probably using ODBC) to populate the tables. There are other methods as
well, dep...
This should have been working archetype 11 (just as archetype 10). So
needs to be reported as MC Stuff suggested. In the meantime, I could get
it to work by:Right click each project > Properties > Project Facets >
[select right project facet as listed below]For [project].it.tests, and
[project].core: Check Bundle module For [project].ui.apps, and
[project].ui.content: Check Content module, Dynamic Web Module, Java,
JavaScript, and Sightly The projects would then show up on Add and
Remove
I was facing this error sometimes back when doing "Export to server"
from content jcr_root. I am using Eclipse AEM Developer Tools 1.1.0.The
way the issue was resolved was to do the vault import once:Go to your
content jcr_root folder, and use the vlt command>vlt import -v
http://localhost:4502/crx . /This seems to have synchronized the crx
with the content. Thereafter, changing the content in Eclipse did not
have any issue in publishing to the crx. Hope that information helps.
