Thanks Joerg for your feedback. I have created now a Daycare ticket for
the missing documentation.According to the "pure" OSGi Installer
approach, I thought more of uploading the package or bundle directly to
the "install" folder/node below /apps in the JCR repository, so not the
install folder in the filesystem.I think a main challenge here is the
deployment of configurations. Depending on which configurations you
upload, the Felix container restarts several or even all bundles, which
causes th...
Hi Vish.dhaliwalthanks for response. Yes I'm aware of the
content-package-maven-plugin.I think actually too, that the usage of the
CRX HTTP API is like the more structured way.But I have heard once at
some AEM/Sling Conference, that the installation handling via the OSGi
Installer is much more stable because the Installation via the CRX
PackageManager does not respect properly the OSGi bundle lifecycle
specifics, etc.To make sure the installation was successful via OSGi
Installer we could check...
Hi,I would like to automate a bit the deployment of CRX/Vault packages
to AEM instances. As of now I know about these two possibilities:- CRX
HTTP Service API: Using cURL or some other tool to
upload/install/uninstall/etc. packages via CRX- Sling OSGi Installer:
Simply uploading bundles or vault packages to som ".../install" or
".../config" folders. The OSGi Installer then picks these packages for
installation.What do you use or do you prefer?Or what's the Adobe AEM
recommended approach?
Ahh interesting - because as I did the same procedure as you described,
I did not receive a config node name with a Dash in between the Factory
PID name and Identifier...which AEM version did you use?
Ahh so we have found now the solution: We needed to rename the config
xml file to
"com.adobe.granite.cors.impl.CORSPolicyImpl-IDENTIFIER.xml".So we needed
to add a Dash between the Factory PID and the IDENTIFIER.Before we added
manually via the Felix Config console the additional config and then we
simply packaged up the stored config nodes from the CRX. But this
procedure seems not to work for Factory configs.Actually this is also
documented here: Configuring OSGi in a special Note box .
As you can see JaideepBrar in my previous comment with the Screenshot,
we used actually the same PID
("com.adobe.granite.cors.impl.CORSPolicyImpl.c9d2e058-2403-43ac-8755-a5693ddf4ae8")...that's
why we are a bit confused....
Hi JaideepBrar,sorry need to correct my initial description: The
configuration worked so far for one added custom configuration, but it
is displayed not right below the "Adobe Granite Cross-Origin Resource
Sharing Policy" in the Felix Configuration view, which was a bit
confusing.Screenshot:
We tried to update our CORS configuration in AEM 6.5.0.0 according to
this help article: Adobe Experience Manager Help | Understanding
Cross-Origin Resource Sharing (CORS) with AEM .But this does not seem to
work (anymore). If we follow the guide and add it to your package and
deploy it again. It does not recognize it as an instance of the CORS
configuration factory component.We have the same issue with adding a
custom Logging to the LogFactory, as documented here: Monitoring and
Maintaining You...
Yes that's true.But I mean I would like to use the latest Features which
came with the new HTL version in AEM 6.3, e.g. easy Date formatting,
etc.See post here from Feike: New HTL-features in AEM6.3 - Experience
Delivers Is it easy possible to use them in AEM 6.1 too?
I would like to use the latest HTL features like the Date Formatting on
our current AEM 6.1 SP2 instance.My idea would be to simply install the
latest HTL bundles.What do you suggest?
Hi @kautuksahni,I have done this, but then the AEM instance is not
available anymore, also not via the SSL configured port as I have
already mentioned in my initial question.I have checked this on a
vanilla AEM instance.
Hi @sureshr19072451,it is recommended to set a new Password for the
"replication-receiver" user. You can do this by simply login as admin
and change the password of this user.
Hi,I have followed this tutorial: SSL By Default and now I would like to
disable the "http" Access.Where do I Need to configure this? There is a
Felix HTTP Service OSGi configuration, but I'm not very sure how the
Granite SSL Connector Config relates to the Felix HTTP Service config.I
tried once to simply disable http, but then I couldn't Access AEM
anymore, also not via https.Do I Need to enable then "https" in the
Felix HTTP Service config? And does this config then uses the keystore
from the ...
Which url do you use to execute your click request to your servlet?It is
Best Practice to register your serlvet with a resourceType and if needed
some selector or extension. With this you simply then can call an url
like this for example: /content/myweb/par/componentOne.htmlThen in the
Servlet you will have the current resource available with
request.getResource(). From this you can easily read your authored data
or also adapt it to some Sling model, etc.
Hi,I don't know how your content is structured and what you exactly try
to achieve, but it Looks like that you may also solve this Problem, by
simply refactoring your code such you clearly separate the concerns or
also restructuring your content.For me it Looks like that this
"StandardConfig" actually should not have any references to a request
and that this concern may be moved to the StandardRateService which
handles all These loading of These rate configurations (via Service
users for example...
Hi,I have tried to configure the replication from Author to Publish via
SSL/TLS.I have followed this documentation: Replicating Using Mutual SSL
But I can't find the following OSGi config for the "Apache Felix Jetty
Based HTTP Service" which is named there as follow:Enable HTTPS To Use
Granite KeyStore (org.apache.felix.https.use.granite.keystore)I just can
see the other configurations like configuring the path to the keystore
and truststore, etc.I'm using AEM 6.3.1.2 (SP1 with CFP2).Do you have...
Hi,here some other solution, how we have made it:We simply use the Power
of the Apache Sling Framework (https://sling.apache.org) and their
Resource Resolution mechanism (Sling's URL decomposition).Follow these
steps:Create some jsp/htl script which simply outputs the plain text
content or reading the string content from some property, according to
Sling's Resource resolution mechanism you simply can name the file with
EXTENSION.SCRIPT_EXTENSION, e.g. txt.jsp or txt.htmlAdd the content,
e.g. Add...
You mentioned that it works if you login before (e.g. with CRXDE). So I
assume that you don't handle properly in your 404 code the use case if
someone is not logged in. You need to check the permissions and
depending on the result you'll need to redirect to the login page.I
would recommend to check the AEM default 404 handler code, there you
will see all the different cases it handles.
Do you use any custom JS? Have you checked the browser console for js
errors? Maybe your JS clashes with some JS in the edit mode or with the
additional rendered html for the edit bars, etc.
Hi,we usually have used a "AEM 6.x parent pom" for our projects, which
we have created manually. This AEM parent pom defined simply the correct
versions of the needed depedencies for the specific AEM version.
Currently the "uber-jar" approach is the way to manage these AEM
dependencies as far as I have seen. But this approach actually breaks
the idea of managing transparently the dependencies in your project. As
a developer I would like to have the control over my dependencies during
development...
The "Standard rollout config" should handle this properly with the
"referencesUpdate" action, see [1].It may be that your root node of your
live copy has not set the "cq:isDeep" property to "true", because this
is needed in order to update properly all the references in the live
copy tree. [1]
http://docs.adobe.com/docs/en/cq/5-6-1/administering/multi_site_manager.html#Specifying
Default Rollout Configurations
