Message Driven bean external configuration for JBoss with IBM MQ

Question

I am working on a Notification Service using IBM MQ messaging provider with JBoss eap 6.1 environment. I am successfully able to send messages via MQ JCA provider rar i.e. wmq.jmsra.rar file. However on consumer part my current configuration looks like this

    @MessageDriven(   
    activationConfig = {   
            @ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Queue"),   
            @ActivationConfigProperty(propertyName="destination", propertyValue="F2.QUEUE"),
            @ActivationConfigProperty(propertyName="providerAdapterJNDI", propertyValue="java:jboss/jms/TopicFactory"),
            @ActivationConfigProperty(propertyName="queueManager", propertyValue="TOPIC.MANAGER"),
            @ActivationConfigProperty(propertyName="hostName", propertyValue="10.239.217.242"),
            @ActivationConfigProperty(propertyName="userName", propertyValue="root"),
            @ActivationConfigProperty(propertyName = "channel", propertyValue = "TOPIC.CHANNEL"),
            @ActivationConfigProperty(propertyName = "port", propertyValue = "1422")   

    })

My problem is that consumer of this service does not want to add any port numbers, hostName, queueManager properties in these beans. Also they do not want to use ejb-jar.xml to externalize these configs. I have researched and found that we can add a domain IBM Message Driven Bean but with no success. Any suggestions on what I can do here to externalize all these configurations ?

EDIT: Adding --> The JCA resource adapter is deployed at consumer end if it makes it any easier.

Thanks

Note when you try to use mdb as a tag, it gets translated to ms-access. I edited the tags based on what I think you want. — HansUp, Sep 20 '13 at 15:59

score 1 · Answer 1 · edited Mar 01 '15 at 16:12

You can actually externalize an MDBs activation spec properties to the server configuration file.

Create the ejb-jar.xml file, but do not put the actual value in the file, use a property placeholder:

<activation-config-property>
    <activation-config-property-name>hostName</activation-config-property-name>
    <activation-config-property-value>${wmq.host}</activation-config-property-value>
</activation-config-property>

Do this for all of the desired properties.

Ensure that property replacement for Java EE spec files (ejb-jar.xml, in this case) is enabled in the server configuration file:

<subsystem xmlns="urn:jboss:domain:ee:1.2">
   <spec-descriptor-property-replacement>true</spec-descriptor-property-replacement>

Then, in the server configuration file, provide values for your properties:

<system-properties>
    <property name="wmq.host" value="10.0.0.150"/>

Once your MDBs are packaged, you will not need to change any of the files in the MDB jar - just provide the properties in the server configuration.

score 0 · Answer 2 · answered Oct 14 '13 at 07:17

you can avoid to add host name, port number and so on in MDB, you just want to define destinationType in MDB, and rest of the thing u can configure in your application server, like Activation Specification, Queues and Queue Connection Factories. I have done the same thing but i used IBM Websphere Application Server.

Message Driven bean external configuration for JBoss with IBM MQ

2 Answers2