We have a requirement ,where both J2EE applications and ESB interfaces need to be developed on the latest stable version.
for J2EE :
6 functions need to be developed
UI for users need to be developed.
There are about 10 interfaces need to be developed for integration 4 external systems.
I'm thinking the best way to do is use J2EE app server for ESB deployments as well , because of no huge integrations and to make use of same App server instead of haveing separate ESB server for ESB deployments.
Can you please share your openion on this and also share , when we should got gor ESB server for ESB package deployments and why?
Appriciated your views on this...
Thank you for your comments to go with Application server for ESB deployments. Yes, JBoss documentation also says the only difference is the boot time will be faster in ESB server.
It will be great , if you can share some more information on scalability & performance difference between Jboss App Server 5.0 & ESB Server 4.9.
1. What is the Performance number of JBoss App. server and performance number of ESB Server ( like how much messges can handle per minute and will support scallability in future integrations growth?)
2. We may use ESB server , only if we have Integrations requirments and when not having Application server.
I believe , we can deploy each ESB instance in App server separate node for fail-over and load balanced, if required (jboss provide in-built load balancer, no need to purchase third party load balancer),along with EJB components in separate node.
please correct me if anywhere and give your comments.
Thank you very much..
Again, if you intend on deploying something in production - use the application server with JBoss ESB installed on top.
The ESB server has faster boot time because the EJB deployer has been removed. In a production scenario, I don't think boot time is a real big consideration (you shouldn't be booting / rebooting a lot), so I'm not sure what you gain using the ESB server. The ESB server is just a 4.2.3.GA version of the application server minus EJB - it is something that was put together for development, where you might start and restart your server many times in a day.
Thank you Tom for your view..
However, we want to have a separeate instance (ESB server) for ESB deployments to have a dedicated server for ESB. Also, we can avoid signle instance running both J2ee appl + ESB services , which also leads to greater perfirmance in futures integrations added to it.
Can you please tell me what is the laetest ESB server supported by RedHat ? ESB server 4.10?