Article ID:	255
Last updated:	November 02, 2006

Would you like to...

Print this page

Post a comment

User Opinions

No users have voted.

---

How would you rate this answer?

Helpful

Not helpful

Thank you for rating this answer.

SUMMARY

This article explores the possibility of integrating EJBs with your Audium applications.

SYMPTOMS

Developer has one or more EJBs that they would like to access from within their Audium applications, or developer is researching how EJB integration with Audium software works in general.

RESOLUTION

Audium Call Services fully supports integration with EJBs through the use of custom code in your Audium applications. The key requirement is that your application server must be fully J2EE compliant so that it supports EJB integration. You cannot use EJBs on Tomcat for example, because it is not fully J2EE compliant. An application server like Websphere or Weblogic is fully J2EE compliant, and since each includes a servlet container Audium Call Services can run on them as well.

EJBs are server-level components that many enterprise applications use. They allow for greater flexibility and redundancy than servlets alone. They are deployed on an application server in an EAR file, whereas Audium Call Services is bundled in a WAR file.

An EAR file is a higher-level file, which can potentially contain WAR files within it. Some customers bundle Audium Call Services and their custom EJBs into an EAR file.  Please note that there is more to deploying EJBs than writing an element and deploying it to Audium Home; EJBs require more direct integration with an application server, which is why they need to be wrapped around the Audium WAR file. 

Audium software itself does not use any EJBs, so conflicts are not an issue.