Sanjiv,
I’m not sure that I understand your question.
Perhaps you could give an example of a major J2EE-based commercial application and pose a question about how webMethods might best used in some type of integration scenario with that application.
The optional approach of embedding a J2EE app server like JBoss inside IS allows you to easily deploy EJB-business logic built for another part of the organization inside the “cradled” JBoss server so that any IS Flow or Java service can invoke its methods natively. I’m quite sure that no one envisioned redeploying an entire commercial application in the cradled server.
Organizations that already have EJB-savvy development teams can leverage them for integration development without retraining. Also, any IS Flow or Java service can be accessed natively by EJB’s by generating “iBeans” which get hot-deployed in the cradled JBoss server.
Note: I did not say that you need to be an EJB developer or even a java developer to create webMethods integrations, but if your organization has an existing EJB skill set, those folks can do integration development work without learning any new tools (except perhaps the minor differences between JBoss deployment descriptors and those of their existing app server vendor).
Of course, there are other ways to invoke EJB methods from within webMethods integration services including using the EJB adapter, writing RMI client code or invoking a web service wrapper of the desired method. As always, which method is best depends on the skill set of the organization and the specific requirements of the business.
Mark
#Integration-Server-and-ESB#webMethods-Architecture#webMethods#webMethods-General