Different ways of configuring the Link Checker Service in CQ 5.6?

[LinearGradient]

Hi,

What is/are the proper way/s of configuring the Link Checker Service?

So far, creating a .config text file under /apps/cq/linkchecker/config/com.day.cq.rewriter.linkchecker.impl.LinkCheckerImpl.config has worked, but looks like creating the config under /apps/<myapp>/config does not work, contrary to what's mentioned in the following links:

• http://helpx.adobe.com/experience-manager/kb/CQ53HowToExcludeURLsFromTheLinkChecker.html
• http://docs.adobe.com/docs/en/cq/current/deploying/configuring_osgi.html.

What would happen if there were different LinkChecker config files under /apps/app1/config, apps/app2/config, etc.? As The Link Checker can be bound to only one config file, how can there be multiple configs for different apps? How can it be verified in /system/console/configMgr that each app is picking up its own config?

Also, I assume both sling:OsgiConfig nodes and textual .config files should work, but again, putting a sling:OsgiConfig node under /apps/myapp/config was not getting picked up by the system.

Finally, is there a web console page available that can be used to test what a link will be transformed to, similar to how /system/console/jcrresolver lets you test url mapping? Basically, a page where I can enter some HTML (e.g. <a href="https://nonexistingdomain.example.com">Foo</a>), to see if the link is transformed to text or stays intact?

Thanks in advance.

[smacdonald2008]

Here is a community article that talks about this subject:

http://www.wemblog.com/2011/10/how-to-make-sure-that-links-are-always.html

This is written by one of our AEM community members Yogesh. If you feel that this is not covered enough in the core AEM docs - open a ticket here:

http://helpx.adobe.com/marketing-cloud/experience-manager.html

[Jörg_Hoh · Accepted solution]

Hi,

Basically it doesn't matter which folder you choose for your configuration, if the folder is at level 2-4 (in /apps or /libs) and has the name "config" (so /apps/x/y/config or /apps/x/config are fine). You should avoid to have multiple configurations for the same service (unless it's a service factory) in the repository, as it's getting non-deterministic which one is actually taken.

You can have only a global configuration for the linkchecker, it doesn't have a notion of multiple applications.

AFAIK there is no possibility to check if a certain link is considered valid or invalid from a linkchecker point of view (besides looking at the repository). But an OSGI Webconsole to have this would be a nice feature.

Jörg