kevingtan

Re: WCMMode disabled is incorrect in publisher - Adobe Experience Manager

HI @Jörg_Hoh , I figured the isWcmDisabled wasn't correct so starting to trace everything.Jsp Code: boolean isWcmEdit = WCMMode.fromRequest(request) == WCMMode.EDIT;boolean isWcmDisabled = WCMMode.fromRequest(request) == WCMMode.DISABLED;boolean isWcmPreview = WCMMode.fromRequest(request) == WCMMode.PREVIEW;boolean isWcmDesign = WCMMode.fromRequest(request) == WCMMode.DESIGN;pageContext.setAttribute("isWcmEdit", isWcmEdit);pageContext.setAttribute("isWcmDesign", isWcmDesign);pageContext.setAttri...

Re: WCMMode disabled is incorrect in publisher - Adobe Experience Manager

Hi all, I figured the problem. It was the name of the jar file.After unpacking the jar file, I left it intact, which cuased problem. According to Adobe, the initial startup will set the runmodes for the whole life of the instance, so the subsequent filename modification won't work. Now the prodecure of the setup will be:unpack the jar filemv cq-default.jar aem65-publish-4503.jar [pattern: prefix--port], as stated from adobe.run puppet to update the configstart the script This works on publisher ...

Re: WCMMode disabled is incorrect in publisher - Adobe Experience Manager

Hi @Jörg_Hoh , it's the default value "dev, s7connect, crx3, author, samplecontent, crx3tar". Both java and jsp code are showing the same value on author and publisher. The process shows the instance is using the custom runmodes:ps -ef | grep -i java java -server -Xms1024m -Xmx2048m -XX:MetaspaceSize=512m -XX:MaxMetaspaceSize=2048m -javax.net.ssl.trustStore=/apps/mysite/crx-quickstart/ssl/trusted.keystore -Djava.awt.headless=true -Xverify:none -noverify -Dsling.run.modes=publish,dev,crx3,crx3tar...

Re: WCMMode disabled is incorrect in publisher - Adobe Experience Manager

When we check the process:ps -ef | grep -i javaWe can seejava -server -Xms1024m -Xmx2048m -XX:MetaspaceSize=512m -XX:MaxMetaspaceSize=2048m -Djavax.net.ssl.trustStore=/apps/crx-quickstart/ssl/trusted.keystore -Djava.awt.headless=true -Xverify:none -noverify -Dsling.run.modes=publish,dev,crx3,crx3tar,nosamplecontent -jar crx-quickstart/app/cq-quickstart-6.5.0-standalone-quickstart.jar start -c crx-quickstart -i launchpad -p 4503 -Dsling.properties=conf/sling.properties So I stopped the process, r...

Re: WCMMode disabled is incorrect in publisher - Adobe Experience Manager

It has been like that. Doesn't look like coming from the line of code.

Re: WCMMode disabled is incorrect in publisher - Adobe Experience Manager

Looks the runmode is author instead of publisher. Don't know why it can't pick the runmodes from the start script.

Re: WCMMode disabled is incorrect in publisher - Adobe Experience Manager

No, it's still the same after installing service pack 11.

Re: WCMMode disabled is incorrect in publisher - Adobe Experience Manager

@ManuMathew1994 Thanks for your instruction. I don't have the permission to download the service pack. Will try that and see what will happen. Thanks again!

WCMMode disabled is incorrect in publisher - Adobe Experience Manager

Hi all, Our AEM 6.5 publisher cannot detect the correct WCMMode. The start script runs with an option "-Dsling.run.modes=publish,dev,crx3,crx3tar,nosamplecontent". JSP code segment:boolean isWcmDisabled = WCMMode.fromRequest(request) == WCMMode.DISABLED;The isWcmDisabled is false in publisher, should be true. Now all the wrong preloads are coming up. It is working on AEM 6.0. Any idea? Thanks! -kt

Re: Customized Rendition Servlet - Adobe Experience Manager

Thank you! I could have made it an array.

Re: Customized Rendition Servlet - Adobe Experience Manager

That was a silly mistake. Thanks a lot!

Customized Rendition Servlet - Adobe Experience Manager

Hi All, We have a customized rendition servlet running fine on 6.0, but fails to run on 6.5 due to the Sling servlet spec changes. According to Apache Sling(https://sling.apache.org/documentation/the-sling-engine/servlets.html), either servlet's paths or resourceTypes must be defined in order for the servlet to take effect. I just define the resourceTypes in the servlet. AEM 6.0 code:// SCR annotations@SlingServlet(selectors = {"preset", "precrop"}, extensions = {"xjpeg", "jpeg", "png"}, methods...

Re: Unable to load tag handler class - Adobe Experience Manager

Hi @Shubham_borole , Really appreciate your help. I just did that, got the same error message. But I did something else interesting. I created a new class 'MyBeanLoader', copied the code from the old class to the new one, renamed the uri value to what you suggested in jsp and .tld. The error is gone. I am crossing my fingers that won't come back. Thanks a lot! kt

Unable to load tag handler class - Adobe Experience Manager

Hi all. Our custom tag stops working after upgrading from AEM 6.0 to AEM 6.5.0. We are using tldgen library(https://github.com/icoloma/tldgen). Here is our pom.xml in 6.0org.apache.maven.pluginsmaven-javadoc-plugin2.6.1**org.tldgen.TldDocletorg.extrema-sistemastldgen1.3private-htmlFolder ${basedir}/target/docs-tldFolder ${basedir}/src/main/resources/META-INF-license NONEtruefalseutf-8generate-resources javadocIn bundle/pom.xml org.extrema-sistemas tldgen 1.3.1 compile It has been working perfect...

Re: AEM 6.0/6.5 oak-run and migration issue - Adobe Experience Manager

All right. I can get the login page back now. It's because AEM is somehow loading up our customized url transformer, which implements the interface org.apache.sling.rewriter.Transformer. This interface is not found so I had to delete the whole transformer config from /crx/de. -K

Re: AEM 6.0/6.5 oak-run and migration issue - Adobe Experience Manager

Hi @kchaurasiya , Thanks for your suggestion. I am wondering if the difference between 6.4 and 6.5 would make the migration only works on 6.4. I have been trying crx2oak at least 5 time with different options and parameters. It looks there is s small progress, but far from enough to make myself feel good. I can start up the 6.5 instance, but the login page stops working. We are using the local login for testing, by the way. We can see all the migrated contents under /crx/de. I have another envir...

AEM 6.0/6.5 oak-run and migration issue - Adobe Experience Manager

Hi All, I am trying to migrate the content from AEM6.0 (Oak 1.0.22) to AEM 6.5 (Oak 1.10.2). Here's what I did,install a fresh copy of AEM 6.5 (/apps/aem65/crx-quickstart/repository)get a copy of the current repository in version 6.0 (/apps/aem60/crx-quickstart/repository)Run the commandjava -Xmx4096m -jar crx2oak-1.8.10-all-in-one.jar segment-old:/apps/aem60/crx-quickstart/repository /apps/aem65/crx-quickstart/repository --datastore=/apps/aem65/crx-quickstart/repository/datastore > ~cms/aem-mig...

Re: Upgrading from 6.0 to 6.4.x - Adobe Experience Manager

Hi Jorg,We are running into the same situation when migrating from aem60 to aem65. We store the aem60 content in a nfs mount point and that is used as a source repository, there are two directories underneath, "index" and "segmentstore". My command is: sudo java -Xmx4096m -jar crx2oak-1.8.10-all-in-one.jar /mnt/tisch.nyu.edu/tsoaauth/aem-crx /apps/aem65/crx-quickstart/repository/, where/mnt/tisch.nyu.edu/tsoaauth/aem-crx is the aem60 repository. But here is what we got:08.09.2021 16:05:54.876 IN...

Re: Upgrade from 6.0 to 6.5 - Continued - Adobe Experience Manager

Thank you very much! It's very helpful! So even if it's a fresh installation, one still has to copy the crx-quickstart directory from 6.0 to the new server in order for the content migration?

180

Upgrade from 6.0 to 6.5 - Continued - Adobe Experience Manager

Hi all, I like to ask a question about an upgrade from 6.0 to 6.5. In short, is there a tool that can migrate the 6.0 content to 6.5 in a separate server, and expect minimal fix? I asked the same question before in a more elaborate fashion, https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/upgrading-from-aem-6-0-to-6-5/qaq-p/367024. We had an internal discussion about it and still have some questions. Our Repository is Apache Jackrabbit Oak 1.0.22 on AEM 6.0 with sp1, sp2...

207

Re: Maven build failed all of a sudden. - Adobe Experience Manager

Thanks for your advice. I actually did something silly, comment out a jsp file where it's referenced by another file.

140

Maven build failed all of a sudden. - Adobe Experience Manager

Hi all,I have been building my AEM 6.0 dev site for years without any related issues as the following. I always run the build command as:mvn -Pinstall -Pinstall-publish clean installIt basically builds the package to the author and publisher the same time. It has been working since the morning but all of a sudden it stopped working. The error is: [INFO] --- content-package-maven-plugin:0.0.20:install (install-content-package) @ base-content ---[INFO] Installing base-content (/Users/kevintan/work...

170

Re: Dispatcher doesn't cache - Adobe Experience Manager

@Asutosh_Jena_, Thanks! I see the dispatcher takes the publisher as the first priority. It is supposed to get the local contents first, but it turns otherwise.Here is the log, where n_t.html is the file directly created in the cache folder: [Thu Mar 18 10:17:36 2021] [D] [40151(140249987221472)] Found farm farm1 for my-dev.nyu.edu[Thu Mar 18 10:17:36 2021] [W] [40151(140249987221472)] Unable to connect to 12.34.56.78:443: Connection refused[Thu Mar 18 10:17:36 2021] [W] [40151(140249987221472)] ...

216

Re: Dispatcher doesn't cache - Adobe Experience Manager

The log tells something pretty much as expected. The dispatcher skips itself and goes directly to the publisher to request the file.I am showing the two different environments so you can see the difference. Case 1, the problematic one:I shut down the publisher. I created a file "n_t.html" directly under the cache folder, here is the log:[Thu Mar 18 10:17:36 2021] [D] [40151(140249987221472)] Found farm farm1 for my-dev.nyu.edu[Thu Mar 18 10:17:36 2021] [W] [40151(140249987221472)] Unable to conn...

217

Re: Dispatcher doesn't cache - Adobe Experience Manager

Thanks for your help! Well, I created a file directly under the cache folder, and expect the dispatcher can serve it to the end users. Looks like it has nothing to do with permissions.

215

Dispatcher doesn't cache - Adobe Experience Manager

Hi All, Recently we had VM migration from an old location to another one. The migration cloned one branch of the whole architecture as the following: author -> publisher -> dispatcher. Nothing changes except the new clone has a new domain name. Now we found a problem, the dispatcher doesn't cache. We can authorize contents from author, the contents will be replicated all the way to the dispatcher, but the dispatcher always skips itself and tries to get contents from the publisher. For instance, ...

327

Re: Upgrading from AEM 6.0 to 6.5 - Adobe Experience Manager

Thanks for your advice, it's really helpful. I am actually doing mostly as you are advising. It's impossible to copy and paste as I am looking deeper into the two different versions.

581

Re: Upgrading from AEM 6.0 to 6.5 - Adobe Experience Manager

Do we have to follow Adobe's Archtype13 structure, or just keep the old if considering the easy way at the first step? Moving to new structure invites a lot of challenges such as package names, dependencies. But I am afraid keeping the old structure will not be compatible with 6.5.

775