1. When a .rar is deployed, both RADeployer and RAActivator will be used to deploy the file in turn, thus 2 managed connectors are registered to the ManagementRepository for the same .rar file. And only the one registered by RAActivator has the ManagedConnectionFactory.
It depends on how you deploy the file - I suggest that you include an ironjacamar.xml file in the .rar archive where you specify the JNDI bindings. That way RAActivator won't pick up the archive.
Another solution is to disable the RAActivator bean - see the user guide - deploy the archive, and then deploy the -ra.xml file with the JNDI bindings.
The managedconnectionfactory-class will be defined in META-INF/ra.xml, and the class will be put on the jar file which will be put on the rar file. so shall we need the jar file in the classpath out side of the rar file?
No, the .rar archive must be self-contained - e.g. contain all classes. The localtransaction.rar you have attached is incorrect, since it only contains two classes.
I suggest to use the code generator to generate the test archives you need - or use the helloworld example that is in the documentation.