Should I install a JMS provider to virtualize JMS?
Can someone detail it step by step?
Because I new to Lisa and I have tried virtualizing web service and JDBC. Now I need to try JMS as well.
Thanks in Advance
Do you need to virtualize JMS for a customer engagement, or just for your own edification? If it's the former then we're going to need more details. But if it's just for a learning experience then there is an education course you can take that covers the basics of messaging virtualization.
The course Kevin refers to above is, CA LISA r7.5: Messaging Virtualization 300. Recommend searching for it by course code, 88ADO30010. CA Employees can do so via learn.ca.com. Customers and Partners can search via education.ca.com.
Here is a 8.x DevTest project and narrative around JMS virtualization using LISA Bank.
Did you get an answer to your question? If so, could you mark the correct answer as such? Thanks!
Can I get the JMS jars for Demo server?
You can use the attached LISA Project and step-by-step directions to get familiar with virtualizing using JMS. As Bhavin said, you do not need additional jars when you use the attached project with LISA Bank.
I am using this documentation and have deployed the LiveService.vsm and trying to validate them using the live service test file. and getting the above error in the service itself.
Try using my jbossmq-destimations-service.xml file in lieu of the one provided in the demo at C:\root\DemoServer\lisa-demo-server\jboss\server\default\deploy\jms
What other configuration file did you modify? Please let me know if this helps.
All i have changed is that the lisa bank application runs on 8080 - I have just modified it to run on 8001 as I have some other process running on 8080. I tried using your xml for jboss however I dont think thats the issue. Its looking for factory class so I believe its missing some jars. I am using 8.0.1. So the demoserver Jboss has all the jars and it seems its looking for workstation i.e client jars when I am trying to execute the liveTest.tst.
> Message: Object Factory JNDI Name: ConnectionFactory not found in JNDI context org.jnp.interfaces.NamingContextFactory:jnp://localhost:1099
This means that it can find the jars, and it can connect to JBoss, but the JNDI lookup for 'ConnectionFactory' is not finding anything by that name. That's unusual; 'ConnectionFactory' is typically the default JNDI name for the JMS Connection Factory in JBoss. That's definitely the case for the JBoss demo server distributed with DevTest.
Either you're running a different JBoss server with a different configuration on that port, or something is wrong with your demo server.
Retrieving data ...