Set up the Derby database
The SQL used for creating the derby tables, required by the scheduler, is shipped in the Scheduler folder - for me that was /home/jsears/IBM/WebSphere/7/AppServer1/Scheduler.
Name = MyScheduler
Use the API's
The first EJB is the optional one:
And here is the mandatory EJB:
What is most important is how the deployment descriptor looks (take into account that this was coded in a RAD 6 IDE). In particular how the
NOTE: use the following in RAD as the JDBC Driver class if you want to connect RAD to derby: org.apache.derby.jdbc.ClientDriver
Figure out which fixpack you want by visiting the IBM Recommended fixes for WebSphere Application Server page.
Next visit the IBM Maintenance Download Wizard for WebSphere Application Server V7.0 site and download the maintenance wizard:
With the Wizard, once you have extracted and installed it, you'll load the fixpack and basically patch your existing WebSphere install. For me, on Ubuntu 9.04, it was a straight forward process for both my 6.0 and 7.0 installs.
I reused the Built-in Mail Provider @ server level:
...and then created my own mail session:
Mail Providers > Built-in Mail Provider > Mail Sessions
Next I created a very simple servlet, whose doGet method grabs the JNDI context and then uses the JavaMail API to send an email:
Because the SMTP debugging was on I got output that looked like the following and that resulted in an email being sent to me :-)
NOTE: a useful reference is at http://www.ibm.com/developerworks/websphere/library/techarticles/0310_fung_yu/fung_yu.html
After clicking Next I provided the following details
3. Resources > JDBC providers > MySQL JDBC Provider > Data sources > New
Reference The Data Source
I accepted all the defaults when uploading the .war - including the "Map resource references to resources" options, as I had already defined the details previously:
The URL I used, once the application was started, to invoke this servlet was: http://127.0.0.1:9081/ReferenceJNDIdataSource/ReferenceJNDIdataSource
3. On "B1" create a destination, "Q1", accepting all defaults: 
5. Create a new JMS connection factory, accepting all defaults unless shown below: 
6. Create a new JMS queue connection factory, accepting all defaults unless shown below: 
7. The final part is creating an activation specification: 
8. In order for WAS to recognise the JMS details we've just created unfortunately we need to restart WAS. 
...and the bean itself (notice the onMessage method I've fleshed out) 
2. Deploy the .EAR file and provide the following information for the activation specification of: 
3. Test the MDB is listening by sending a message with the Universal Test Client: 
However, the project can just as easily be created / imported in RAD 7.5.n (or a non Rational version of eclipse):
package jsears;
import java.io.IOException;
import java.io.PrintWriter;
import javax.servlet.Servlet;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import org.apache.log4j.Logger;
/**
* Tomcat = http://127.0.0.1:8080/log4j/main
* WebSphere = http://127.0.0.1:9080/log4j/main
*
* @author jsears
*
*/
public class Main extends HttpServlet implements Servlet {
private static final long serialVersionUID = 233300306772977426L;
protected static final Logger logger = Logger.getLogger(Main.class);
private static String sessionId = null;
public static synchronized String getSessionId() {
return Main.sessionId;
}
protected void doGet(HttpServletRequest arg0, HttpServletResponse arg1)
throws ServletException, IOException {
sessionId = arg0.getSession().getId();
logger.debug(sessionId);
PrintWriter out = arg1.getWriter();
out.println(sessionId);
out.close();
}
}
package jsears;
import org.apache.log4j.PatternLayout;
import org.apache.log4j.spi.LoggingEvent;
public class HelperLayout extends PatternLayout {
StringBuffer stringBuffer = new StringBuffer(128);
private String getSessionId() {
return Main.getSessionId() + ": ";
}
public void activateOptions() {
return;
}
public String format(LoggingEvent event) {
return getSessionId() + super.format(event);
}
public boolean ignoresThrowable() {
return true;
}
}
# Set application classloader mode as PARENT_LAST when deploying in WAS as .ear
priority=1
org.apache.commons.logging.LogFactory=org.apache.commons.logging.impl.LogFactoryImpl # HIERARCHY: ALL > DEBUG > INFO > WARN > ERROR > FATAL > OFF
# Everything ###############################################################
#log4j.rootCategory=OFF, file
# application ###############################################################
log4j.logger.jsears=ALL, out, file
# Get rid of various Tomcat "WARN No appenders" complaints
log4j.logger.org.apache.catalina=OFF
# Appender definitions ########################################################
log4j.appender.out=org.apache.log4j.ConsoleAppender
log4j.appender.out.target=System.out
log4j.appender.file=org.apache.log4j.RollingFileAppender
log4j.appender.file.MaxFileSize=5MB
log4j.appender.file.MaxBackupIndex=5
# Tomcat
#log4j.appender.file.File=${catalina.home}/logs/log4j.log
# WAS - e.g. use this line when deploying into WAS
log4j.appender.file.File=${LOG_ROOT}logs/log4j.log
# Appender layouts ##########################################################
log4j.appender.out.layout=jsears.HelperLayout
log4j.appender.out.layout.ConversionPattern=%-5p: %d{dd MMM yyyy HH:mm:ss,SSS}: %C{1},%L: %m%n
log4j.appender.file.layout=jsears.HelperLayout
log4j.appender.file.layout.ConversionPattern=%-5p: %d{dd MMM yyyy HH:mm:ss,SSS}: %C{1},%L: %m%n
Specifying a .war context in WebSphere Application Server 6.0.2.33
Specifying a .war context in WebSphere Application Server 7.0.0.0 ND