The list of available remote "managers" that the CLI can access (i.e. the list of remote EJBs we make accessible to the CLI) is not automagically generated but rather hardcoded in the form of the org.rhq.bindings.client.RhqManager enumeration.

To add a new remote interface to our remote API you simply need to add an entry to this enumeration, filling all the necessary info (the "${Blah}" are replaced by actual values at build time by maven resources) and rebuilding the bindings module.

The crude method of deploying is then to copy the new jar to $RHQ_SERVER/jbossas/server/default/deploy/rhq.ear/lib and the $CLI_HOME/lib (and restarting the server and the CLI). The proper way is to rebuild the RHQ from source and redeploy the server and the CLI.