We are on AEM 6.3.3.5. We also use AEM Forms Server on a completely
separate set of servers. When we upgrade AEM from 6.3 to 6.5, must we
also upgrade AEM Forms server? I'm not asking if it's best practice to
upgrade both at the same time, because it surely would be nice to do. We
are trying to minimize the effort for Phase I of our upgrade, and
deferring the upgrade of AEM Forms Server could save us time.Thanks very
much for any helpful advice you can offer.-Nestor
Appreciate you suggesting a possible alternative gauravb10066713. For
now, we only have one affected workflow (maybe two), so
writing/maintaining additional and possibly unsupported custom workflow
code doesn't quite seem worth the trade-off of manually
enabling/disabling the workflow launcher. We still might give your
suggestion a shot if we have time, and if so, will let you know how it
goes. Thanks again gauravb10066713.
Very logical idea, and I tried something similar before posting, but no
dice. I even tried it again in case I missed something the first try,
both with and without the square brackets for runModes value in
.content.xml. Thanks so much gauravb10066713 for your awesome
suggestions and time.
gauravb10066713, thanks again for commenting. We do use different
runmodes on all our servers. Unlike regular osgi configs for stuff like
com.day.cq.mailer.DefaultMailService.xml, the workflow launcher config
is in one folder, and the file is named .content.xml. For our example
workflow,
it's:-ui.content/src/main/content/jcr_root/etc/workflow/launcher/config/my_custom_workflow/.content.xmlIt's
not that we only want to run it or not run it on certain servers, it's
that we'd like different config...
Hi gauravb10066713. The runModes property only limits where this single
configuration gets applied for the specified workflow launcher. We're
trying to use multiple configurations that are selectively applied to
different servers. The runModes property might be part of the solution,
but it doesn't help with the multiple configurations piece (unless
there's more to it that I'm not seeing).Thanks very much for your input.
We're using AEM 6.3.3.2. Is it possible to customize configurations in
our source code for individual workflow launchers on a per environment
basis, similar to OSGI configs? The goal is that each Maven build will
apply the custom settings to each workflow on a per environment basis.
We'd like to avoid manually changing settings after deployment.With OSGI
configs, we have various config folders in our ui.apps project that
might apply to individual servers (DEV, QA, etc.). Each server uses
custom ...
Jorg, thanks for your additional perspective. Very nice to know that the
added complexity could even cause us unexpected issues. Going to follow
the KISS principle!
smacdonald2008, thanks a lot for the quick reply. It definitely helps!
Based on your answer (and well known expertise), I think we'll avoid
including namespaces in our custom property names. Good to know it's an
option, but not a hard rule.
If your company is named MyCo and you sell books, you might want to
store properties like total pages for book nodes in the JCR. Are you
supposed to name your company's custom JCR properties so that they start
with a namespace? If so, should your custom properties always start with
the namespace jcr: or something else like myco: (inspired by your
company name)? We've seen consultants use both, e.g., totalPages or
jcr:totalPages.We're just trying to be consistent with what the rest of
community i...
The answer we were looking for was a combination of what arunp99088702
and dan.klco (and others) said below.AEM provides components that might
closely match a Sling API version, but those components are updated over
time and details change. It's not an "All Sling 9" or "All Sling 10"
implementation.However, just to get an idea of which versions of the
Sling API that different versions of AEM most closely match (at least at
a certain point in time), look
here:https://helpx.adobe.com/experience-...
Well, I am unable to edit my original question. dan.klco, your answer
is obviously not incorrect. I wish I could mark both answers correct,
but the original one I accepted was the correct answer to my question.
dan.klco, awesome of you to clarify things. I understand how this post
could confuse other readers, but I really was just looking for the
"base" version of Sling that's supported by AEM 6.3 and 6.4. The answer
I accepted was perfect for our needs, but might cause others to jump to
wrong conclusions. Makes perfect sense how the AEM implementation is not
exactly all Sling version 9 or 10. We just needed to know, in general,
which set of API docs to use for reference (e.g., we wouldn't want to
use...
smacdonald2008 and Ratna Kumar, first thanks for your replies. I tried
to make it clear in the original post that I already know I can look at
the various Sling bundles and versions in the web console. It doesn't
answer the question.The documentation on the official Apache Sling site
is written to cover a specific version of Sling, even though Sling has
many pieces. That's all I'm trying to determine--what version of Sling
as referenced on the official Apache Sling site is implemented by AEM?
...
smacdonald2008 thanks for your reply, but that is the same link I was
referring to in my original post--it doesn't answer the question. Next
time I'll be sure to include any external links so they're not
referenced in replies.Somebody from Adobe must know the answer to this
seemingly simple question, or at least be able to find out from an Adobe
architect. Just need to know what version of the Sling API specification
that AEM implements for versions 6.3 and 6.4. Sorry if I sound
frustrated, but...
Can someone please tell me what version of the Sling specification AEM
implements, and how we can look this up for each version of AEM? I'm not
looking for a list of Sling-related bundle versions in the web console,
but rather the single, general Sling specification version. Sling is
currently at version 10. I saw a stackoverflow post that says AEM 6.3
implements Sling 9, but don't know how to confirm this.Thanks for your
help.-Nestor
We did away with the Filter completely. In the sling model class, we
@Inject SlingHttpServletRequest, use a @PostConstruct method to start
our custom logic. Going to mark this complete as the scope of the
question grew too large. Thanks for providing ideas.
Hi smacdonald2008 . Thanks for your response. Based on that, we updated
our dispatcher.any file. We set it for everything to go through
uncached, and it works as expected, but that is obviously too extreme.
/rules { /0000 { # the globbing pattern to be compared against the url #
example: * -> everything # : /foo/bar.* -> only the /foo/bar documents #
: /foo/bar/* -> all pages below /foo/bar # : /foo/bar[./]* -> all pages
below and /foo/bar itself # : *.html -> all .html files /glob "*" /type
"de...
Hi navinkaushal, thanks for replying. Please let me know if you need
additional details.On Dispatcher, it's for anonymous users. On Author
and Publish, we must authenticate to access links.We aren't using a
servlet. The filter already has access to the request and response. A
SlingModel injects a SlingHttpServletRequest into the model. It uses
that injected request to read an attribute set by the filter.1. In
Filter's doFilter() method, Filter calls
slingHttpServletRequest.setAttribute("some_key...
I've seen posts about issues using an HttpSession object for
setting/getting attributes with AEM. Do those same issues apply to
setting/getting attributes for a SlingHttpServletRequest? One post
(non-Adobe) mentioned it affected Dispatcher caching, but not sure how
reliable the source was. Another post mentioned receiving a new
HttpSession on every request.From a javax.servlet.Filter, we call
slingHttpsServletRequest.setAttribute(), and from a Model class we call
slingHttpServletRequest.getAttri...
We have a license for aem 6.3, and use the aem jar for local development
(i.e., we rename author as aem-author-4502.jar and rename publish as
aem-publish-4503.jar). We see lots of notices for service packs,
hotfixes, cumulative fixes, security updates, etc. Does adobe update
that base jar with these various updates, and make it available for
download? Would be nice for new developers to start with an updated jar
without having to apply all those updates. If so, is there a link for
existing custo...
Thanks all three of you for your helpful replies. While technically I
was looking for official documentation, it's good to know that there are
several options for implementing a solution. shankarappa, your approach
seems like a very flexible solution that will best meet our needs
long-term, so chose yours as the correct answer--much appreciated.
Again, thanks smacdonald2008 and Ratna Kumar as well.
For non-AEM websites, there's usually a clearly defined web root folder
where you can place files like robots.txt. In AEM (v6.3), it's a bit
more complicated with the Author, Publish, and Dispatcher instances.
Adding a robots.txt should be simple, but I'm not sure how to do it in
AEM, and I can't find definitive documentation. We don't need info about
what the robots.txt file should contain--we just need the steps for
getting it on our new AEM site.Do we simply send our robots.txt file to
a serv...
smacdonald2008, thanks for all your replies. I'll follow up with
@kautuksahni to make sure the community isn't aware of anything already
going on with this concept. If not, I'll give it a shot.
smacdonald2008, you are providing very useful info, however it doesn't
answer the question. The custom utility would:be installed through
package manager.not modify any content/properties in your jcr_tree
(unless there was an configurable option implemented to also save
missing images into your sandbox DAM).have a configurable server name as
one of its properties (the server with the images in its
DAM).dynamically handle all the logic for streaming any images from an
external server if it doesn...
smacdonald2008, thanks for posting again. I think that will definitely
come in handy. Still, I'm really asking if there's a way to serve the
images from an external server without having them stored in my local
sandbox's DAM. I don't want my sandbox DAM to be externally located
either, which I saw is one option folks are using for solutions
involving Docker. Again, thanks for helpful info--it just doesn't answer
my question.
kautuksahni, thanks so much for forwarding it to that team. Looking
forward to hearing any ideas and/or knowledge about any existing
community projects that cover this.
