svn rev4097 adds a new remoting connector being deployed by the ear. it uses the servlet transport over the http port today. we will have to figure out something later to make this configurable (to allow someone to go over sslservlet port 7443 for security purposes). today, its over unsecured servlet transport , port 7080. We should probably write a subtask jira here so we remember to do this. 

we will have people that will only want to allow remote clients to go over secure transport. It may be as simple as deploying a second service (remote-api-secure-service.xml) that uses the configured https port (i.e. copy remote-api-service.xml and change the transport to sslservlet and the port to the https property).