I have been researching (trying to find out really) on the best practices of calling remote methods on EJB from IS 6.1. In the past, our company has developed a custom Java flow service to initialize the JNDI context on the EJB (the EJB jar in the classpath of IS) and once the handle of the remote interface is obtained, make a call to the method and pass the necessary parameters to the method. But I have often found that this way is very inefficient and not scalable. This was developed when we started using IS 4.x
I am trying to re-architect this process to best utilize the resources available in the new version of IS (6.x). I want to be able to scale this architecture to handle a large volume of messages primarily interfaced for the business solution running on an application server, more specifically Websphere 6.0.1. If anyone can provide some valuable suggestions, I would really appreciate it.