Good Morning Everyone, Thank you for giving me this opportunity to be
part of your community. My name is Patrick Yee and I am a software
love to learn about technology. I also enjoy reading and writing, and
playing video games. I am inspired to a game software developer, but in
the meantime I want to be more knowledgeable person with a lot of
@smacdonald2008 ,Do you have the correct development article link or
working package of
is taking to different page. Thanks,Shiv MN
@Nirmal_Jose thanks for the answer, just wanted one clarification. in
the image there are 2 marketing clouds are shown under experience cloud,
I assume that the second one is a commerce cloud, please correct me if I
Hi All,ACS report will be very helpful for this use case. You will get
the "replication status" of the page. Please follow the below steps.1.
Install latest ACS commons on AEM author instance.2. Open path
prefix of your domain name. e.g.
Fill the path e.g. /content/rashidjorvee4. Execute report and download.
Below is the screenshot for better un...
AEM as a cloud service is not AMS (Adobe Managed Service), these are 2
distinct services, and there's also a difference in the technology
between these 2.You can consider AEM as a cloud service (AEMCS) as a
PAAS solution, where Adobe is handling all operational aspects (not sure
what kind of tasks you were thinking of when you mention "devops"). From
your questions the only aspect you (as partner/implementer/developer) is
executing is the deployment, which is completely handled by
Never came across that functionality in AEM.Like Danial stated in the
WEEKEND tutorial (he authored that great content) - AEM does not act as
a source check in and check out tool. You want to use Github (or another
tool) for that functionality. Hope this helps.
If you want some content to be published only via agent-1, and other
content only published via agent-2, you can use the approach described
The application design/code should not be a constraint to support
scalability. I'll take a best practices example here - The app should
not have hardcoded absolute paths that would cease to work on another
server. Similar approach goes for environment variables, shared content
storage, session based use cases etc.