you can find AEM process PID by using:ps -ef | grep java | grep cq-quickstart

Sorry for a typo in my previous post. Here is the query, that works on my test env and returns a page where a Content Fragment includes a word "winter":path=/content/we-retail/ustype= cq:Pagegroup.p.andgroup.1_fulltext=wintergroup.2_fulltext=contentfragment

You need to request a Classic Target account from Target Support. AEM is still using a Classic Target API to connect to Target. By default, Classic Target Account is not assigned when Tagert is provisioned to an organization.

You can try a query similar to:type=nt:unstructurepath=/content/we-retail/us1_group.1_property=sling:resourceType1_group.1_property.value=weretail/components/content/contentfragmentfulltext=winter

What is your business case, that you need to disable indexes and force a traversal search? Traversal search will significantly affect performance and as a result, the AEM server might not responsive at all.

You need to troubleshoot by accessing your AEM directly and you can also employ OSGI "Recent requests" tab at /system/console/requests. It will help to identify the configuration/service that is responsible for redirection

"Unable to load remote blob" is a known issue. The thing that is causing the sync to fail almost every time is a timeout error. The journal file gets updated after every sync cycle whose duration depends on the no. of changes and the volume of the repository. As a possible solution, try to increase ...

Most likely your page "sling:redirectStatus" property is set to 302:

It seems like you are using new IMS to Target connection. The reason that XF exported as an HTML is a known limitation of the current implementation of IMS->Adobe IO -> Target connection. In order to be able to export to Target as XF you need to use an old (deprecated) way by employing a Target Clas...

It seems that you are using new IMS to Target connection. The reason that XF exported as an HTML is a known limitation of the current implementation of IMS->Adobe IO -> Target connection. In order to be able to export to Target as XF you need to use an old (deprecated) way by employing a Target Clas...