java ee - Using .BINDING File with MDB in Jboss EAP6.4 -

-

i writing standard java ee 5 application , need consume jms messages (hornetq) mq serverv8. mq admin has provided .bindings file mq configuration. after searching web, not able find way use .bidings file mdbs. have tried using standard activation spec. works fine. that, jms properties need in jboss or ee specific configuration files. can please tell way use .bindings file mdb?

how decide jndi , initial context factory name ?

while possible use .bindings file mdb activation specification, turns out impractical. can specify destination in both .bindings file , mdb activation spec, not connection factory. attributes configure connection factory (i.e. host, port, channel, etc.) configured individually in activation spec.

what can use .bindings file configure jms messaging bridge mq jboss. then, mdb listens on local hornetq destination. in order working, need to:

1) create ibm mq client module. messaging bridge not using ibm jca. on unix mq server, find client jars in /opt/mqm/java/lib/ directory.

i created module following jar files:

./system/layers/base/com/ibm/wmqclient75 ./system/layers/base/com/ibm/wmqclient75/main ./system/layers/base/com/ibm/wmqclient75/main/com.ibm.mq.tools.ras.jar ./system/layers/base/com/ibm/wmqclient75/main/com.ibm.mq.axis2.jar ./system/layers/base/com/ibm/wmqclient75/main/com.ibm.mq.headers.jar ./system/layers/base/com/ibm/wmqclient75/main/ldap.jar ./system/layers/base/com/ibm/wmqclient75/main/cl3nonexport.jar ./system/layers/base/com/ibm/wmqclient75/main/providerutil.jar ./system/layers/base/com/ibm/wmqclient75/main/connector.jar ./system/layers/base/com/ibm/wmqclient75/main/jta.jar ./system/layers/base/com/ibm/wmqclient75/main/com.ibm.mq.soap.jar             ./system/layers/base/com/ibm/wmqclient75/main/com.ibm.mq.jms.nojndi.jar ./system/layers/base/com/ibm/wmqclient75/main/com.ibm.mq.jar ./system/layers/base/com/ibm/wmqclient75/main/com.ibm.mqjms.jar ./system/layers/base/com/ibm/wmqclient75/main/rmm.jar ./system/layers/base/com/ibm/wmqclient75/main/jms.jar ./system/layers/base/com/ibm/wmqclient75/main/com.ibm.mq.commonservices.jar ./system/layers/base/com/ibm/wmqclient75/main/fscontext.jar ./system/layers/base/com/ibm/wmqclient75/main/com.ibm.mq.pcf.jar ./system/layers/base/com/ibm/wmqclient75/main/cl3export.jar ./system/layers/base/com/ibm/wmqclient75/main/jndi.jar ./system/layers/base/com/ibm/wmqclient75/main/com.ibm.mq.jmqi.jar ./system/layers/base/com/ibm/wmqclient75/main/dhbcore.jar ./system/layers/base/com/ibm/wmqclient75/main/module.xml

my module.xml file:

<?xml version="1.0" encoding="utf-8"?>  <module xmlns="urn:jboss:module:1.0" name="com.ibm.wmqclient75"> <resources> <resource-root path="com.ibm.mq.commonservices.jar" /> <resource-root path="com.ibm.mq.headers.jar" /> <resource-root path="com.ibm.mq.jar" /> <resource-root path="com.ibm.mq.jmqi.jar" /> <resource-root path="com.ibm.mqjms.jar" /> <resource-root path="com.ibm.mq.pcf.jar" />  <resource-root path="connector.jar" /> <resource-root path="dhbcore.jar" /> <resource-root path="fscontext.jar"/> <resource-root path="providerutil.jar"/> </resources>  <dependencies>    <!-- add dependencies required jms bridge code                -->    <module name="javax.api"/>    <module name="javax.resource.api"/>    <module name="javax.jms.api"/>    <module name="javax.transaction.api"/>    <module name="org.jboss.remote-naming"/>    <!-- depend on org.hornetq module since send messages  -->    <!-- hornetq server embedded in local as7 instance           -->    <module name="org.hornetq"/> </dependencies> </module>

2) can load configure bridge:

<subsystem xmlns="urn:jboss:domain:messaging:1.4"> .... .... ....             <jms-bridge name="wmqbridge" module="com.ibm.wmqclient75">             <target>                 <connection-factory name="xaconnectionfactory"/>                 <destination name="jms/queue/test"/>             </target>             <source>                 <connection-factory name="mqcf"/>                 <destination name="mqqueue"/>                 <context>                     <property key="java.naming.factory.initial" value="com.sun.jndi.fscontext.reffscontextfactory"/>                     <property key="java.naming.provider.url" value="file:///${jboss.server.data.dir}/bindings/"/>                 </context>             </source>             <quality-of-service>once_and_only_once</quality-of-service>             <failure-retry-interval>500</failure-retry-interval>             <max-retries>1</max-retries>             <max-batch-size>1</max-batch-size>             <max-batch-time>1000000</max-batch-time>             <add-messageid-in-header>true</add-messageid-in-header>         </jms-bridge>     </subsystem>

note refernnce module:

<jms-bridge name="wmqbridge" module="com.ibm.wmqclient75">

my names destination , connection factory, found in .bindings file:

                <connection-factory name="mqcf"/>                 <destination name="mqqueue"/>

i created directory under standard data directory named bindings , placed .bindings file in it:

<property key="java.naming.provider.url" value="file:///${jboss.server.data.dir}/bindings/"/>

that messages locally on destination can access.

  • doug

Comments

Post a Comment

Popular posts from this blog

ios - RestKit 0.20 — CoreData: error: Failed to call designated initializer on NSManagedObject class (again) -

-
this error has shown on many times, seems. prominent answer issue seems restkit 0.20 — coredata: error: failed call designated initializer on nsmanagedobject class however, solution posted doesn't work me. let's start beginning: i want upload file server. want parse response make sure uploaded. if not, try again later. model has boolean variable called nsnumber *senttoserver purpose (in coredata, bool saved nsnumber ) . because don't know whether sending going successful, save entity coredata model first before sending via restkit. when post request successful, server returns json string this: {"id":14,"created":true} notice that, of course, id not set on coredata model yet, both id , created new informations model. here's model: @interface recording : nsmanagedobject @property (nonatomic, retain) nsstring * audiofilepath; @property (nonatomic, retain) nsdate * createdat; @property (nonatomic, retain) nsstring * deviceid; @...
Read more

java - Digest auth with Spring Security using javaconfig -

-
so i'm trying create digest authentication spring following documentation trying translate xml "requirements" in java requirements. let's have xml in docs: <bean id="digestfilter" class= "org.springframework.security.web.authentication.www.digestauthenticationfilter"> <property name="userdetailsservice" ref="jdbcdaoimpl"/> <property name="authenticationentrypoint" ref="digestentrypoint"/> <property name="usercache" ref="usercache"/> </bean> <bean id="digestentrypoint" class= "org.springframework.security.web.authentication.www.digestauthenticationentrypoint"> <property name="realmname" value="contacts realm via digest authentication"/> <property name="key" value="acegi"/> <property name="noncevalidityseconds" value="10"/> </b...
Read more

laravel - PDOException in Connector.php line 55: SQLSTATE[HY000] [1045] Access denied for user 'root'@'localhost' (using password: YES) -

-
my .env: app_env=local app_debug=true app_key=myappkey app_url=http://localhost db_connection=mysql db_host=localhost db_port=3306 db_database=gestiontaller db_username=root db_password='root' cache_driver=file session_driver=file queue_driver=sync redis_host=127.0.0.1 redis_password=null redis_port=6379 mail_driver=smtp mail_host=mailtrap.io mail_port=2525 mail_username=null mail_password=null mail_encryption=null i've tried password ", ' , without, restarting server every time. i've tried changing localhost 172.0.0.1. yes, password correct, running mysql -u root -p introducing password root in prompt can go mysql. users table: +------------------+-----------+ | user | host | +------------------+-----------+ | debian-sys-maint | localhost | | mysql.sys | localhost | | root | localhost | | root1 | localhost | +------------------+-----------+ i've added homestead.yaml this: database_port: 3306 ...
Read more