By default, only CQ admin user can impersonate others for testing purposes. Often times, you need a non-admin user to test out others' account. For that, it is possible for a non-admin user to impersonate another person as long as it was set-up before hand.

This post is about what I learned a good "lead magnet" (the free offer you make to get visitors’ email addresses) idea for building an opt-in email list. If you believe opt-in email-list is valuable to your business, but you're short of idea building up the list effectively, this marketing idea is it.

If you're bootstrapping a company and looking to name your brand or business, you need to do some brand name research so that you can have a brand name of yours to work on. Brand name research is to make sure the brand name you choose is available for you to own. If the name is already owned by someone else but you don't know, you might get a cease and desist letter from the trademark owner. The purpose of brand name is to be unique, so you don't want to accidentally step on other's toe.

Ever suspect your Java app leaking memory but not sure which class it is potentially causing OOM? 

In this post, I recommend Eclipse Memory Analyzer (MAT) for developers to analyze heap dumps so you can chase down leak suspects. MAT is much easier to use and read than stand-along jhat unix command, and while monitor memory usage using VisualVM is helpful, MAT gives you specific hints about which classes may be the suspects.

It is not uncommon that you need to watch the runtime performance of a Java application on a server. In this post, I'll show you how to set up a target JVM so you can monitor its cpu, heap memory, threads usage from a specific JMX client - VisualVM. VisualVM is similar to JConsole, a JMX-compliant monitoring tool, but is more advanced. 


To use a JMX client, the setup you need to do first are:

1. On the Target server where JVM runs, you need to enable JMX Agent for the JVM.
   
2. On the local machine where you want to monitor your Java application from, you need a JMX client. For this post, I chose VisualVM.
3. To prevent other JMX client from accessing your JMX Agent, you want to turn on authentication when your JMX client connects to your JMX Agent.

With JMX agent enabled for a JVM, you can use a JMX Client (JConsole or VisualVM) to tap into your JVM to monitor its performance and memory usage at runtime. Your java runtime is not enabled with JMX by default unless you explicitly specify to turn it on.

Production CQ instances deserves tighter security policy. OOTB CQ is too loose in security. For example, you don't need to open your production for client software like CRXDE to access it, nor do you want to open up WebDAV if not necessary. Most importantly, the default password of the super user 'admin' have got to be changed, which is not a straightforward process as you'd expect. 

In this post, I outlined specific steps that I took to tighten up security of our CQ Author and Publish nodes in a production environment. If you are planning to launch a public facing CQ, you can go through the same checklist.