I would never install JBoss AS from an RPM package, not even in production! In fact, I never install any Java components using the package manager - I always download them from the respective web sites so that I know what I am getting and where they get installed.
But if your sysadmin insists on using an RPM, then I would use "ls -al", and follow all of the @#$% symlinks (one symlink I can understand, but i've seen 4 or 5 to get to the bottom of things) to determine exactly where the server directory is located and do my copying there using the actual directory path.
Thanks for the immediate reply. I used ls -al to follow all bleeping links resulting in higher blood pressure. I'm not quite sure what the advantage of the rpm file installation other than installing jboss updates (if there are such a thing). Are you familiar with any RedHat/JBoss best practices that I can use as ammunition to persuade sysadmin to use zip file vs rpm file installation? I searched the Internet and this site not finding anything specific.
Sorry, but I don't know of any official recommendations or best practices in this regard. But you'll find numerous instances of my recommendation both in this forum and at Java Ranch. IIRC, others have suggested the same.
I do not know if RedHat supplies patches to the JBoss AS installed via an RPM (a JBoss team member might know or could find out). I rather doubt it because the community edition is never patched (though you can apply patches yourself); if you need automatic patching you have to get the enterprise edition (and pay RedHat more $$$).
Thanks Peter. You certainly gave me good information for some arm twisting.