Is not as easy as you think it would be. Hence our experience is not complete on this and we can only supply some first steps that you need to perform. However, an actual deployment of EMI components or the EMI Framework on a WAS was never successful. We believe the reason lies within the startup order of the ejb-jars and their dependencies with each other for example in the monitoring service.
Configuration
You need to set the following custom JVM settings.
To do so: Log into the administration console of your WAS. Got to: Server > server 1 > Process Definition > Java Virtual Machine > Custom Properties. Add the values to the properties and restart you server.
// Fix for context and dependency injection in startup // EJBs. See http://www-01.ibm.com/support/docview.wss?uid=swg1PM62774 com.ibm.ws.cdi.immediate.ejb.start = true
Messaging
You need to set up a messaging service to be able to use the EMI framework in your applications. In theory you can pick any message queue available in the market. We provide detailed setup instructions for:
