markus_bulla_adobe

Adobe Experience Manager

Adobe Campaign Classic

Adobe Campaign Standard

Adobe Experience Platform

Adobe Analytics

Adobe Audience Manager

Adobe Target

Adobe Experience Cloud

Adobe I/O Cloud Extensibility

Adobe Advertising Cloud

Marketo

Magento

Adobe Creative Cloud

Adobe Document Cloud

Workfront, an Adobe company

Your achievements

0% to

Tip / to gain points, level up, and earn exciting badges like the new

Open Alerts Bar

Community profile markus_bulla_adobe Employee

Senior Technical Architect

Germany

14 BADGES

Learn more

Joined the community 24-08-2017 10:46:18 AM

Send a message

Online

View leaderboards

Profile

Trophy case

Top badges earned by markus_bulla_adobe

Give Back

Betreff: Where is the deleted page Archived in TOUCH UI 6.4 - Adobe Experience Manager

Hi @mriz!You are probably referring to the following dialog: That's a question I get a lot from my customers.For AEM as a Cloud Service, there is a "Restore" button available once you have selected a page. It will open a dialog to restore a page/tree: Unfortunately, this restore functionality is not yet implemented for Touch UI in AEM 6.4 nor 6.5. 😕I expect it to be made available with one of the next updates / service packs for AEM 6.5, but have no insight into the exact roadmap or timeline. A...

Betreff: Access-Control-Allow-Origin missing in response - Adobe Experience Manager

Hi @TB3dock!At a first glance, your OSGI configuration looks ok and things should work as expected.For further debugging I would refer your to the Troubleshooting section of the "Understanding CORS" documentation page. Please create a logger for the com.adobe.granite.cors package on DEBUG (or even TRACE) level and see if you can find additional insights on the matter. Apart from that one general note. I'm sure you are aware of this and obviously you're currently in a troubleshooting/debugging wo...

Betreff: servlet and cors - Adobe Experience Manager

Hi @TB3dock! The required CORS configurations should be done as OSGI configurations on the "Adobe Granite Cross Origin Resource Sharing Policy" as pointed out in the documentation that you already mentioned. OSGI configurations are a common pattern in the AEM tech stack and you will find some additional explanations in some of your older threads on OSGI config topics. You should place an according OSGI config file (either XML or JSON format) in your code base, specifically into the ui.config mod...

Betreff: Migration from 6.1 to 6.4 steps - Adobe Experience Manager

Hi @manikanthar1295!Please refer to my answer on this thread [1].The recommendation is the same for most (if not all) versions of AEM. [1] https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/upgrade-6-2-to-6-5/qaq-p/406024 Citing my answer here for your ease: There are different approaches to upgrade from older AEM versions to newer ones.In place upgrade - basically stopping your instance, replacing the quickstart.jar with the newer version and starting it again.Upgrade to ...

Betreff: Request to Complete Move Operation Workflow trig... - Adobe Experience Manager

Hi @dominik_lackovi! Some remarks to your observations here:If you are using the actual "admin" user, it's almost impossible that there are any permission-related issues. The concept of the admin-user is fundamental to AEM and in more than a decade of AEM experience I have never seen any authorization issues for the admin user.For the OOTB "administrators" user group and their members things are slightly different, still quite unlikely to have permission issues as described.If a user tries to mo...

Betreff: *ERROR* [qtp55964443-107234] org.apache.felix.ht... - Adobe Experience Manager

Hi @Shivanna! Please try the following:Have you double checked on the credentials used for that request?Is your Jenkins server allowed to send these requests to the target instance (IP in allow list)?Have you tried the same request from the Jenkins servers command line, e. g. with CURL?Have you tried providing the credentials within your Groovy script (apply it to the HttpClient) instead of sending them as query parameters?Have you tried providing the credentials in the "user:password@host:port/...

Betreff: AEM 6.5 : package org.apache.sling.scripting.jsp.jasper.runtime.JspWriterImpl does not exist - Adobe Experience Manager

Could you please share the complete error message with some context? Are you seeing the error at build time (Maven) or at run time (AEM logs)?

Betreff: Does AEM have any sort of distributed caching wh... - Adobe Experience Manager

Hi @TB3dock!I'm not sure if I understand your use case 100% correct.I'll just leave some general advice with regards to caching.When working with AEM, you can leverage several levels of caching:Browser caching (setting according headers on your HTTP response)Usually, this can be applied best for long living resources, such as JS and CSS files or certain images (e. g. a logo). But with shorter TTLs (time to live), this can also be leveraged for HTML pages or other responses (e. g. XHR). General a...

Betreff: Store data request on live server. Need to refre... - Adobe Experience Manager

Hi @adobecq-venkat!While there are different ways to store and synchronize user generated data on/between publish instances (@Vaibhavi already pointed out Sling Content Distribution), I would not recommend any of them for actual order data in terms of e-commerce or similar transactional data. AEM and especially the publish tier is not the right place to manage or store transactions and orders. For online stores, AEM is usually integrated with some kind of e-commerce system (see [1]), e. g. lever...

Re: Upgrade 6.2 to 6.5 - Adobe Experience Manager

It's hard to say without detailed knowledge, but it is not uncommon that the repository is smaller after migrating to a new, fresh instance. One step that I missed to mention in my initial post is that as a pre-work it is usually recommended to cleanup everything no longer needed from the old instance (e. g. old packages) and run the according maintenance cleanup jobs (workflow and version purgen, compaction) to reduce the repositiory size. This will help with a smoother migration and speed up t...

Re: Upgrade 6.2 to 6.5 - Adobe Experience Manager

Hi @Manikumar! There are different approaches to upgrade from older AEM versions to newer ones.In place upgrade - basically stopping your instance, replacing the quickstart.jar with the newer version and starting it again.Upgrade to a new environment - setting up a new environment with the target version and migrating your project (content, code, configurations, etc.) to that new environment.From my experience the most reliable and clean way is a combination of these two approaches:Setup a new, ...

Re: abort processing of the request - Adobe Experience Manager

Hi @anelem1760873! Usually, you would include your filter into the filter chain and override the doFilter() method as @bilal_ahmad outlined in his code example.Depending on your understanding of how to "block/abort" the request, you could do one of the following:Check for the right condition and send an appropriate HTTP response (e. g. 404 Not Found or any other 4xx or 5xx code that makes sense for your use case) - exactly what @bilal_ahmad mentioned. You can find a simple example of a LoggingFi...

Re: how to get admin session using service user - Adobe Experience Manager

Hi @manikanthar1295!Please refer to the following documentation:https://experienceleague.adobe.com/docs/experience-manager-65/administering/security/security-service-users.htmlIt points tohttps://sling.apache.org/apidocs/sling7/org/apache/sling/jcr/api/SlingRepository.html#loginService-java.lang.String-java.lang.String-What you need to do: SlingRepository.loginService()orResourceResolverFactory.getServiceResourceResolver() Hope that helps!

Betreff: AEM project release managment - Adobe Experience Manager

Hi @mitadiana!Release Management is a very broad topic and there is no one-size-fits-all approach here. Every AEM project has different prerequisites, dependencies, requirements, etc. While there are some smaller projects that do release builds manually, most projects have some kind of CI/CD chain in place that helps them automate this task. Often this is based on an already established tool set. So the bottom line here is: use what you already have in place and/or are comfortable to work with. ...

Betreff: Permission sensitive caching dispatcher - Adobe Experience Manager

Hi @trc41594544!There are two prerequisites for it:You need to add the according dispatcher configuration (the /auth_checker section mentioned in the documentation you linked and posted by @asutosh_jena) andyou need to have your authorization checker servlet up and running on your AEM instance. If you are now requesting any page that matches the defined filter rules of the auth_checker section from the dispatcher, the following will happen:The dispatcher will send a HEAD request to the auth serv...

Betreff: Filter rejects: GET /bin/customservlet - Adobe Experience Manager

Hi @Antony6790!As @asutosh_jena already mentioned, the trailing slash may be an issue in your rule and the rewriting should not be necessary.In addition to that, please review your full set of filter rules in the dispatcher configuration and make sure that there is no deny-rule placed after your servlet allow-rule and that the ID of your allow-rule is unique (the leading /0123 numbering if you're following the default pattern). Please note: the ID numbering of filter rules is not required to be ...

Re: Project bundles does not start after couple of builds... - Adobe Experience Manager

Hi @hptarora! If your project bundle is not able to resolve all required dependencies/services it will not be able to start.Please check the services that are marked in red on the detail view of your bundle and make sure that the according services are available. Once all required dependencies are available, the bundle should be able to start. You may also try to start the bundle manually through Web Console (/system/console/bundles). If it fails (e. g. due to missing dependencies) this will thr...

Betreff: AEM Non-licensed version 6.5.0 - Adobe Experience Manager

This is an issue with your local Maven build of the frontend module caused by node / npm. The build process has issues to execute the required binaries. Unfortunately, I'm neither a node/npm expert nor do I have a Windows machine at hand to test it. However, once you get this build issue sorted, things should work as expected. Have you checked the two points that I mentioned in my initial answer (location of node.exe that is mentioned in the error message and moving the project to another folder...

Betreff: Content Migration from CQ5 to Contentful - Adobe Experience Manager

Hi @Kailash07! There are several ways to export content from AEM. Let me list some of them:@asutosh_jenaalready mentioned the .infinity.json selector+extension that exposes the content structure in a JSON format. It will list the whole content hierarchy with all subnodes. Be aware: depending on the size of your content tree you may want to split the query for certain subtrees of the content hierarchy and not just query the root node. You can build a CRX content package of your content. If you un...

Betreff: AEM Non-licensed version 6.5.0 - Adobe Experience Manager

Hi @Heena91! Regarding the licensing: AEM does not stop working or omit styling or other developments based on a missing license. I assume that you are working with a development license. If there are any concerns with regards to your license, please reach out to your Adobe representative (e. g. the person who provided the quickstart jar to you). Anyways, this should not affect your local development from a technical point of view. Looking at the error message that you provided in one of the ans...

Betreff: Dispatcher critical issue - Adobe Experience Manager

That's not a lot of information to work with.As @asutosh_jena already pointed out, please verify your configuration syntax and double check on the logs of Apache httpd and dispatcher (error.log, dispatcher.log, other custom logs if there are any). In general, adding a new farm should not do any harm (assuming that the configuration of the farm is correct). However, there may be situations where simple changes may break something. I've seen httpd no longer starting up after adding another vhost d...

Betreff: .cfg.json file not working - Adobe Experience Manager

SimpleServlet.Config.class refers to the inlined interface definition of my configuration interface: public static @interface Config. In your case with a dedicated config class you would have to point the @Designate annotation to that configuration class. See also https://docs.osgi.org/javadoc/r6/cmpn/org/osgi/service/metatype/annotations/Designate.html and https://felix.apache.org/documentation/subprojects/apache-felix-metatype-service.html

198

Betreff: .cfg.json file not working - Adobe Experience Manager

Here is what I did: I made the existing class com.mysite.core.servlets.SimpleServlet configurable through an OSGI config. Steps required: added an inline Config interface with my desired config values; added the @Designate(ocd=SimpleServlet.Config.class) annotation to the class; added a variable to hold my config value to SimpleServlet; added an activate(...) method and assigned the value taken from the config to the previously defined variable. Apart from that I have added a config file as mysi...

230

Betreff: .cfg.json file not working - Adobe Experience Manager

I just tried a simple example in the AEM Maven archetype generated project and things worked out pretty straight forward.

233

Betreff: Managing permissions on DAM - Adobe Experience Manager

While technically the size of a private folder or the number of assets inside that folder is not an issue in itself, this sounds a bit like trying to skip step 1 from my initial answer. The concept of private folders provides an agile ad-hoc collaboration workflow. If you are trying to establish a standard workflow for your organization, then a properly designed and implemented workflows backed by an authorization concept is the right way to go.

Betreff: AEM video upload to Vimeo - Adobe Experience Manager

In general that should be possible with one caveat: IMO it would be a better idea to store the video inside of AEM before pushing it to Vimeo. This would allow for an asynchronous push to Vimeo and would not block the user until that is finished. It would also allow to retry the upload from AEM without a need for the user to upload it again to AEM. You can add a cleanup job/step after that push to Vimeo has been confirmed to be successfully finished. That said, I'm not aware of an existing integ...

103

Betreff: .cfg.json file not working - Adobe Experience Manager

The important part - where the binding happens - is the declaration that is annotated with "@AttributeDefinition". That's what you need to align with the keys in the config file. If you want to keep the "getFoo" naming you need to update your config file to reflect that exact key ("getTimeout" instead of "timeout"). You're right: the declaration is technically a method, but used somewhat differently in this context. You may want to check the example from the Maven archetype that I mentioned earl...

270

Betreff: .cfg.json file not working - Adobe Experience Manager

I would recommend to rename the variable identifiers in your Java class. getFoo usually indicates a method but this definition is actually the parameter definition. So "foo" would be a better name compared to "getFoo" here.

284

Betreff: .cfg.json file not working - Adobe Experience Manager

Please make sure thatYour json file name matches the Service PID (see web console UI below "Configuration Information"; this part is cut off in your screenshot).The keys in your json file match the configuration keys of your service (see web console; key is in brackets after the parameter description). According to your shared code (variable definition is the key) and the screenshot this is currently "getHttpVersion", "getEndpoint", "getTimeout", "getLogResponse" instead of your currently used k...

286

Betreff: Where to put config files - the missing piece. - Adobe Experience Manager

The content of the config json file needs to reflect the the properties that you define in your OSGI service. It's just a key-value-list of the parameters. You can double check on the required keys in the OSGI web console config manager UI by opening your service configuration. The key is always listed in brackets after the property description (below the input field). You'll also see the PID (required for the naming oif your file) in the dialog at the bottom.

100

Likes given to

User

Count

Likes from

User

Count

Guidelines

Cookie preferences