Introduction

This page is a good reminder for the Java EE6 developper that plan to use Eclipse indigo with weblogic 12c or greater for developping Servlets/JSPs/EJB/JMS applications.

Installing a JMS queue on WebLogic

Good guide on how to setup a JMS queue here :  http://blog.touret.info/blog/index.php/post/2011/09/22/Mise-en-oeuvre-d-une-file-d-attente-JMS-sur-Weblogic-10.3 (in french)

Writing a remote client standalone for an EJB

You must have at least one EJB that implements a remote interface. Example :

And here is the remote interface (located in the Client project that is automatically created when we do an EAR project):

The client project is just a Java project, but you must add two things so that it compiles and run:

1. Add the EJB project in the build path (the project that contains the EJB you are going to call)
2. Add wlfullclient.jar, a jar with all the client libs you need. This jar needs to be built once, using a command line interface cd in the WEBLOGIC_INSTALL_LIB/server/lib, then run the command "java -jar wljarbuilder.jar". This will take 30s to build the client lib for your installation. At the end, you should find a wlfullclient.jar file. Add it to your build path.

Then you should have such a source code for the standalone client:

Writing a client for a weblogic queue

Here is an example of a client that sends TextMessages to a MessageDriven bean.

It is recommended to double check the JNDI names of the JMS connexion factory and of the JMS destination.

•  Check that the name used in the MDB is the same as the JNDI name you can find in the JNDI tree for your weblogic server. You can do that by looking at the weblogic admin console, on the left, click on "base_domain", then "servers", then in the main page click on the name of your server, then in the main window you should have something like "JNDI tree"... Click on that, a new tab opens in which you can explore the names objects on your server. In the small tree, click on "weblogic" then "jms" then on the connection factory and destination. You will find in the detailed view the JNDI names.
• Check that you used exactly the same names in the annotations of your Message driven bean,
• Check that you used exactly the same names in your client servlet.

Example MDB: