Accueil > Intranet Michel Buffa > Weblogic / Java EE6 FAQ and Guides

Weblogic / Java EE6 FAQ and Guides

De $1


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 Java DB + sample database + DataSource in Eclipse + in Weblogic

Install and Launch JavaDB

  1. Get this archive that contains JavaDB 10.x + a sample database :,
  2. Unzip it somewhere,
  3. go to <java db install dir>/bin and run startNetworkServer.bat
  4. Notice the presence in the bin dir of a directory named "sample". This is an example database. By default, the derby server locates databases in the bin dir.

Add the connection to the DB admin tool in Eclipse java EE perspective

  1. In Eclipse, in the Java EE perspective, locate a tab called "Data Source Explorer", right click on "Database Connections" and choose "New" in order to add a new connection.
  2. In the next dialog, type in "Der" and choose "Derby" as the database type, click next
  3. Then you must indicate which JDBC driver you are going to use. Choose "Derby Client JDBC driver 10.1", but this is not enough, you need to set the proper jar file to use. So click on the small rounded button at the right '"new driver definition", then on the "jar list" tab. Remove proposed jar and click on the "add jar/zip" button on the right.
  4. Go to <java db install dir>/lib and select the derbyclient.jar file.
  5. Enter the sample database infos: sample/localhost/1527/app/app (app is both the value for user and for password). Unselect the "create database" button. Click on the "test connection" button on the right.


Add the DataSource to Weblogic 12c

In WebLogic 12c, run the admin server from the windows start menu, then open the weblogic admin console (also from start menu). 

  1. Go to the "source de données"/datasources link in the main page. Click on it
  2. Use the nouveau/new button in order to add a datasource,
  3. Select "source de données generiques"/generic datasource in the drop down menu
  4. Next dialog : enter a name for the database : I suggest "SerbySample", enter a JNDI name for accessing the database from a java EE application. I suggest "sample".  Choose "Derby" as the database type. CLick next.
  5. Next dialog click next in order to validate the JDBC driver proposed by default (WebLogic comes with the Derby driver pre-installed)
  6. Next dialog: click next (transactions options),
  7. Next dialog: enter the same infos as when you connected the database to Eclipse: sample/localhost/1527/app/app cick Next    
  8. Next dialog, click "Test the connection", if everything is ok, click next,
  9. Next dialog, check the AdminServer as a target for this database. Do not forget to select the target server otherwise your datasource will not be exposed to external applications.
  10. Click finish.

Installing a MySQL database

We will proceed exactly like we did for javaDB, the only thing that changes is the way we will launch the MySQL server and the name of the JDBC driver.

  1. Get this standalone version of MySQL and the jdbc driver achives from the kit that has been given to you,
  2. Unzip the somewhere, we suggest in C:
  3. Unzip the file somewhere and copy the JDBC driver jar file named mysql-connector-java-5.1.14-bin.jar in your MySQL install dir, for convenience (it will be easier to locate when we will need it)
  4. In order to run MySQL, go to the bin dir and run mysqld.exe. In order to stop the server, just ctrl-c in the DOS window or close the window. If you prefer to run MySQL as a service, you may read this small guide on how to administrate MySQL: MySQL install guidel.pdf  and if you do not know anything about MySQL you may read this crash course in english (but very clear, 20 powerpoint slides): Intro to MySQL.ppt 
  5. The MySQL JDBC driver is already installed in WebLogic but not in Eclipse, in order to be able to add a datasource to the Data sources tab in the Java EE perspective of Eclipse, you will have to proceed like we did for JavaDB, see the previous section. You will have to remove the proposed jar file and add the one from step 3.

I have an exception about the persistence manager that is null

There is a bug in weblogic 12c when working with "web profile" projects and JPA. You can't deploy war files otherwise there will be errors in the persistence unit that is not correctly taken into account. A fix recommended by Oracle consists in setting up the deployment option for the weblogic server to "deploy exploded archives".

In the Java EE perspective, right click on the weblogic server, then go to weblogic/publishing an set the option for exploded archives:


Writing a remote client standalone for an EJB

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

package sessions;

import javax.ejb.LocalBean;
import javax.ejb.Stateless;

* Session Bean implementation class Test
public class DemoSessionEJBRemote implements TestRemote {

   public DemoSessionEJBRemote() {
        // TODO Auto-generated constructor stub

   public String helloWorld() {    return "hello world !";

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

package sessions;

import javax.ejb.Remote;

public interface TestRemote {
    public String helloWorld();

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:

package client;

import java.util.Hashtable;import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import sessions.TestRemote;

public class StandAloneClient {
    private static String INITIAL_CONTEXT_NAME = "weblogic.jndi.WLInitialContextFactory";
    private static String PROVIDER_URL = "t3://localhost:7001";
    private static String JNDI_NAME = "java:global.DemoEAR.DemoEJB.DemoSessionEJBRemote!sessions.TestRemote";

    public static void main(String[] args) throws Exception {
        Context ctx = getInitialContext();
        TestRemote helloEJB = (TestRemote) ctx.lookup(JNDI_NAME);

    private static Context getInitialContext() throws NamingException {
        Hashtable env = new Hashtable();
        env.put(Context.PROVIDER_URL, PROVIDER_URL);
        return new InitialContext(env);

Use JMS and a Message Driven Bean on Weblogic

Installing a JMS queue on WebLogic

Good guide on how to setup a JMS queue here : 

Writing a message driven bean

Note: Message Driven Beans are not supported by the JavaEE 6 "Web profile" (all in one projects with jsf/jsp/servlets/ejb/jpa in one single project, deployed as a single war file). For MDB you need to create an EAR project, and an EJB project (maybe with JPA facet), and maybe a Dynamic Web project (for jsf/jsp/servlets). The MDB should be added into the EJB project. The client servlet we demonstrate here should be added in the dynamic web project.

Normally the Eclipse wizard should ask you for the names of the connexion factory + destination. Here is an example of a MDB that works with the client from the next section.

  •  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.


Example MDB:

package sessions;

import javax.ejb.ActivationConfigProperty;
import javax.ejb.MessageDriven;
import javax.jms.JMSException;
import javax.jms.Message;
import javax.jms.MessageListener;
import javax.jms.TextMessage;

activationConfig = { @ActivationConfigProperty(
propertyName = "destinationType", propertyValue = "javax.jms.Queue"
) },
mappedName = "weblogic.jms.DemoQueue")
public class TestMDB implements MessageListener {

public TestMDB() {
// TODO Auto-generated constructor stub
System.out.println("TestMDB : NEW INSTANCE BUILT !");

public void onMessage(Message message) {
if(message instanceof TextMessage) {

TextMessage txtMsg = (TextMessage) message;
try {
String msg = txtMsg.getText();
System.out.println("Message received: " + msg);
System.out.println("Processing message");
System.out.println("End of processing message");
} catch (Exception e) {
// TODO Auto-generated catch block




 Writing a client for a weblogic queue

Here is an example of a servlet that sends messages to the previous message driven bean. In fact it doesn't know the actual receiver of the message, it just knows the destination where the message is being sent.

Again, double check the names of the connection factory and of the destination. They should exactly match the ones in the weblogic admin console and the ones in the MDB.

package servlets;

import java.util.Collection;
import java.util.logging.Level;
import java.util.logging.Logger;

import javax.annotation.Resource;
import javax.ejb.EJB;
import javax.jms.Connection;
import javax.jms.ConnectionFactory;
import javax.jms.JMSException;
import javax.jms.MessageProducer;
import javax.jms.Queue;
import javax.jms.Session;
import javax.jms.TextMessage;
import javax.servlet.ServletException;
import javax.servlet.ServletOutputStream;
import javax.servlet.annotation.WebServlet;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;

import entities.Book;

* Servlet implementation class DemoServlet
public class DemoServlet extends HttpServlet {
private static final long serialVersionUID = 1L;

    // For JMS and the MessageDrivenBean
@Resource(name = "weblogic.jms.DemoQueue")
private Queue demoQueue;
@Resource(name = "weblogic.jms.democonnectionfactory")
private ConnectionFactory demoMessageFactory;

public DemoServlet() {
// TODO Auto-generated constructor stub

protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
                // Test sending a message with JMS to a Message Driven Bean
try {
sendJMSMessageToDemoQueue("This is a message sent using JMS and a MDB !");
} catch (JMSException e) {

private TextMessage createJMSMessageForjmsLoggingMessages(Session session, String messageData) throws JMSException {
TextMessage message = session.createTextMessage();
return message;

private void sendJMSMessageToDemoQueue(String messageData) throws JMSException {
Connection connection = null;
Session session = null;
try {
connection = demoMessageFactory.createConnection();
session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
MessageProducer messageProducer = session.createProducer(demoQueue);
messageProducer.send(createJMSMessageForjmsLoggingMessages(session, messageData));
String messageClient = "Message sent :" + messageData;
} finally {
if (session != null) {
try {
} catch (JMSException e) {
Logger.getLogger(this.getClass().getName()).log(Level.WARNING, "Cannot close session", e);
if (connection != null) {


Mots clés:
FichierTailleDateAttaché par 
 Intro to MySQL.ppt Visualiser
Aucune description
150 Ko08:05, 13 Oct 2012MichelBuffaActions
Aucune description
4.55 Mo13:15, 12 Oct 2012MichelBuffaActions
 MySQL install guidel.pdf
Aucune description
69.44 Ko08:02, 13 Oct 2012MichelBuffaActions
Images (3)
Voir 1 - 3 sur 3 images | Voir tout
Aucune description
explodedA...  Actions
Aucune description
Snap22.jpg  Actions
Aucune description
Snap21.jpg  Actions
Commentaires (0)
Vous devez être connecté pour poster un commentaire.