While I can get it working using the instructions verbatim, I would prefer to configure some of the connection information externally (i.e. not in the ebj-jar.xml file OR the jboss.xml file). Ideally, this would be in a single resource file where the rar file is introduced.
To configure the WASMQ activation spec an ejb-jar.xml/jboss.xml file is required. There is no external means to do this with the WSMQ rar as it is per EJB (listener) deployment. A certain amount of configuration information for the destinations is available in the admin objects themselves, but for a listener deployment the above mechanism is really the only route.
Actually, in furthering this thread
You could set it up to reference system properties or properties replacement in your ejb-jar.xml file. JBoss provides a properties-service.xml file that can be used to set properties dynamically. So, in your ejb-jar.xml file you could set properties for your WASMQ specific information and keep that information in the properties-service.xml file or set then in your run.sh/bat script,.
More can be found here:
This would at least enable you to externalize this info into one place which from your original post I believe is what you want.
Thanks to genman for this. I had completely forgotten about the dynamic replacement for properties on the host.
Thanks, this did the trick.