Configuration of JMS Server in Jboss-4.3.0

[rahul9885]

Hello All,

Could anyone please tell me which version supports Jboss Messaging (JBM).( My Target AS is Jboss-4.3[Enterprise Edition])

What are the different configuration files are to be configured in jboss Jboss-4.3 ( Enterprise Edition).

and How to Start JMS Server in Jboss-4.3.0

Any help would be greatly appreciated!!!

Thanks and Regards,
Rahul Aahir

mail : [e-mail]

[peterj]

JBoss EAP 4.3 comes with JBoss Messaging. Look at the docs/examples/jms/example-destinations-service.xml file for examples of how to define destinations. The messaging server starts when you run the app server, no extra commands are required.

Have you read the JBoss Messaging docs???

[rahul9885]

Thanks for Reply.

I have read docs on Jboss Messaging but i have few doubts which are:

My Application was using OpenJMS-0.7.1, now we are migrating it to Jboss Messaging.

1. Do I need to change JMS client code which is sending and receiving messages ?
   
2. Apart from destinations-service.xml, what are other xml file I have to configure so that my application can run ?
   
3. Do these xml files Exsit in jboss messaging (I have got below info d from internet.)
   

• jbm-jboss-beans.xml: This is the JBoss Microcontainer beans file which defines what beans the Microcontainer should create and what dependencies to enforce between them. Remember that JBoss Messaging is just a set of POJOs. In the stand-alone server, it's the JBoss Microcontainer which instantiates these POJOs and enforces dependencies between them and other beans
  
• jbm-configuration.xml : This is the main JBoss Messaging configuration file.
  
• jbm-queues.xml : This file contains predefined queues, queue settings and security settings. The file is optional - all this configuration can also live in jbm-configuration.xml. In fact, the default configuration sets do not have a jbm.queues.xml file. The purpose of allowing queues to be configured in these files is to allow you to manage your queue configuration over many files instead of being forced to maintain it in a single file. There can be many jbm-queues.xml files on the classpath. All will be loaded if found.
  

• jbm-users.xml : JBoss Messaging ships with a security manager implementation which obtains user credentials from the jbm-users.xml file. This file contains user, password and role information. For more information on security.
  
• jbm-jms.xml  : The distro configuration by default includes a server side JMS service which mainly deploys JMS Queues, Topics and ConnectionFactorys from this file into JNDI. If you're not using JMS, or you don't need to deploy JMS objects on the server side, then you don't need this file.
  
• logging.properties : This is used to configure the logging handlers used by the Java logger
  
• log4j.xml  :This is the Log4j configuration if the Log4j handler is configured.
  

Thanks and Regards,

Rahul Aahir

[peterj]

1) No. As long as you are coding purely to the JMS spec there are no code changes required. If you have OpenJMS-specifc calls, then you will need to remove them.

2) No. However, JBoss Messaging uses the HSQLDB as the JMS database. If you want ot need to use a different database (highly recommended for production), then there are several other files that have to be changed. The Messaging docs have a chapter on how to do this:

http://docs.jboss.org/jbossmessaging/docs/userguide-1.4.5.GA/html/configuration.html#conf.changingds

(Though, reading that section it doesn't go into that much detail. I have anohter resource that explains in in more depth but that resource is not free. I can procide thel ink if you like.)

3) Why are you relying on internet posts rather than on the documentation? Did you look for these files and did they exist? If they didn't exist, what does that tell you about the posts you read?? One things you have to be careful of is that there have been a number of different messaging services associated with JBoss AS, and even Messaging has gone through various transformations with files coming and going. Thus many of thep ost you read could be out of date. It is best to go with the odcumentation.