Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

OlivBur
OlivBur
Offline

Badges

Badges
14

Accepted Solutions

Accepted Solutions
4

Likes

Likes
5

Posts

Posts
25

Discussions

Discussions
11

Questions

Questions
14

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by OlivBur
Customize the badges you want to showcase on your profile
Re: Automating packages deployment: CRX HTTP API/OSGi Installer? - Adobe Experience Manager 16-05-2019
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...

Views

2.8K

Likes

0

Replies

1
Re: Automating packages deployment: CRX HTTP API/OSGi Installer? - Adobe Experience Manager 16-05-2019
Hi Vish.dhaliwal​thanks 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...

Views

2.8K

Likes

0

Replies

3
Automating packages deployment: CRX HTTP API/OSGi Installer? - Adobe Experience Manager 16-05-2019
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?

Views

3.0K

Like

1

Replies

5
Re: AEM 6.5: Adding custom Factory configuration for CORS does not work anymore - Adobe Experience Manager 14-05-2019
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?

Views

1.5K

Likes

0

Replies

0
Re: AEM 6.5: Adding custom Factory configuration for CORS does not work anymore - Adobe Experience Manager 14-05-2019
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 .

Views

1.4K

Like

1

Replies

0
Re: AEM 6.5: Adding custom Factory configuration for CORS does not work anymore - Adobe Experience Manager 14-05-2019
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....

Views

1.4K

Likes

0

Replies

0
Re: AEM 6.5: Adding custom Factory configuration for CORS does not work anymore - Adobe Experience Manager 14-05-2019
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:

Views

1.4K

Likes

0

Replies

0
AEM 6.5: Adding custom Factory configuration for CORS does not work anymore - Adobe Experience Manager 14-05-2019
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...

Views

3.1K

Likes

0

Replies

8
Re: AEM 6.1 SP2 and using the latest HTL version? - Adobe Experience Manager 30-08-2018
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?

Views

1.3K

Likes

0

Replies

0
AEM 6.1 SP2 and using the latest HTL version? - Adobe Experience Manager 30-08-2018
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?

Views

1.4K

Likes

0

Replies

2