Java EE overview and WebLogic operations

Java EE Overview

and

WebLogic Operations

JEE: Where we are?

2003

2006

2009

2013

OCCAS 5.x

JBoss EAP 6.x

List of JEE6 Specs

Vendors

Topics

JNDI
Cluster-wide timers
JMS
JDBC
Thread
EJB
WLST

Java Naming and Directory Interface

Look up objects in a network
API
- a mechanism to bind an object to a name
- a directory-lookup interface that allows general queries
SPI
- LDAP
- DNS
- file system

Naming

Efficient naming conventions always form a tree (directory).

Interface

Cluster-wide JNDI updates

The updates need some time to finish.
It is the cause of JNDI naming conflicts.
- An EJB is un-deployed from the Admin Server;
- Immediately, the EJB is deployed from the Admin Server;
- Got conflicts... because updates on the way;
- Wait some time, the EJB can be deployed successfully!

In-depth Readings

Cluster-Wide JNDI Naming Service

Programming JNDI for WebLogic

Monitoring

JNDI is per server

Cluster-wide timers

Is able to perform load balancing and failover
Continues to function as long as one cluster member is alive

InitialContext ic = new InitialContext(); 
commonj.timers.TimerManager jobScheduler =(common.timers.TimerManager)ic.lookup
   ("weblogic.JobScheduler");
commonj.timers.TimerListener timerListener = new MySerializableTimerListener();
jobScheduler.schedule(timerListener, 0, 30*1000); 
// execute this job every 30 seconds