How to deploy an EJB/Web Service to the interface folder

[Former Member]

We have created an EJB, then wrapped a web service around it. We build an Enterprise Application project to deploy the EJB web service to EP as an .ear file. After deployement, the project is deployed to the \j2ee\cluster\server0\bin\ext folder.

We have created another java project which we need to deploy as a .sda file. Therefore we created a Library project and added our .jar file to it. This java class needs to call the EJB. Everything works except when we try to deploy the Library. We need to reference the EJB from the Library project. Unfortunately, it appears that you can only reference jars that existing in the \j2ee\cluster\server0\bin\interfaces and \j2ee\cluster\server0\bin\services folders.

Does anyone know how to deploy the EJB to those folders, or how to get a Library to reference a jar in the \ext folder?

Maximum points awarded tot he first correct answer.

[Former Member · Accepted solution]

Hi Andrew,

The first point of the answer is that you must create your application, it means your entire enterprise application, like a DC Project - Development Component, this is the only way you have to allow your EAR package to see more than an EJB or WAR module as well.

Once you have created your EAR application as I described in the last point, so, you can create inside the development component another simple DC such as a simple Java project such as the library you have created, so in the first enterprise project you can add this library such as an "Used DCs", at this point the IDE will ask you about, how important is your library package?, so you must select through the options (Design, Runtime, Assembly, Deploy) and the relationship (weak or hard), at the NWDS J2EE Perspective, right-click in your EAR projects, you must add the package of your library in the modules used in EAR assembly, as well you might to have previously added the same package in EJB Project Library, you can also do this last steps without create a DC Project.

So, independent where the J2EE container deploy your application, all libraries and packages will be together.

Best Regards