In the store the clerk ask me if I have a mac or pc. So I told im I have a pc. The next question was which windows I use and I told him linux. He replied that he is not sure if this will work.

For the rest out there it will work, probably not as good when you have itunes, but you can upload your music and thats all I care about.

First install the gnupod, which is a command line tool for managing your ipod. Ubuntu has already a package for gnupod.

sudo apt-get install gnupod-tools

Plug in the ipod shuffle and it should be automatically mounted at
/media/IPOD/.

After that we have to initialize the ipod file system.

gnupod_INIT -m /media/IPOD/

All you need now is a tool to sync your music with the ipod shuffle. I use gtkpod and it works fine for me.

The keynote speakers are Michael Crandell (RightScale), Elizabeth Woodward (IBM) and Jürgen Höller (SpringSource).

For this example I have used VirtualBox 4.1 as virtualization tool. I can recommend you VirtualBox when you want to try out some examples and you do not want to screw up your setup.

GlassFish 3.1 Installation

First we have to install Java. Ubuntu does not longer have the sun-jdk in their repository. (see https://lists.ubuntu.com/archives/ubuntu-security-announce/2011-December/001528.html)

So for this example we are going to use OpenJDK 7 which is available in Ubuntu and is also the Java 7 reference implementation.

sudo apt-get install openjdk-7-jdk

After a new installation of the Ubuntu server unzip is not yet installed, so you have to apt-get it. Later we need unzip to unpack some archives.

sudo apt-get install unzip

There ist no Ubuntu package for GlassFish, but the installation is quite simple. I recommand you the to download the GlassFish Server Open Source Edition 3.1.1 (Zip archive) and unzip it to /opt/glassfish.

wget http://download.java.net/glassfish/3.1.1/release/glassfish-3.1.1.zip
sudo unzip glassfish-3.1.1.zip -d /opt

For an automatically start up of GlassFish we need to create a traditional sysvinit script.

sudo vim /etc/init.d/glassfish

The content of the start script should look as follows.

#!/bin/bash

GLASSFISH_HOME=/opt/glassfish3
case "$1" in
start)
    ${GLASSFISH_HOME}/bin/asadmin start-domain domain1
    ;;
stop)
    ${GLASSFISH_HOME}/bin/asadmin stop-domain domain1
    ;;
restart)
    ${GLASSFISH_HOME}/bin/asadmin stop-domain domain1
    ${GLASSFISH_HOME}/bin/asadmin start-domain domain1
    ;;
*)
    echo "usage: $0 {start|stop|restart}"
    ;;

esac

exit 0

The last step is to make the script executable and to install our script as System-V style script with update-rc.d.

sudo chmod 755 /etc/init.d/glassfish
sudo update-rc.d /etc/init.d/glassfish defaults

Now we can start glassfish with our start script.

sudo /etc/init.d/glassfish start

After GlassFish is started you can access the admin console on http://localhost:4848.

MySQL 5.1 Installation

We use the MySQL version which is already packged with the Ubuntu server.

sudo apt-get install mysql-server-5.1

Out of the box MySQL allowes only connections from localhost. To change that we have to edit /etc/mysql/my.cnf. Open the MySQL configuration file and comment out the following line.

#bind-address = 127.0.0.1

After the restart of MySQL we cann now connect from our network to the MySQL server.

sudo /etc/init.d/mysql restart

It’s time to create a MySQL database and user which we can use from glassfish as DataSource. To create a MySQL database and user you have to login to the mysql server as root.

mysql -u root -p

The following SQL commands create the database glassfish_db and the mysql user glassfish which is allowed to access the database form the external network.

create database glassfish_db;
grant usage on *.* to 'glassfish'@'%' identified by 'glassfish';
grant all privileges on glassfish_db.* to 'glassfish'@'%';

You should now be able to connect as user glassfish to the MySQL database glassfish_db. When you don’t want to work with the console I would suggest you the MySQL Workbench.

mysql -u glassfish -p

GlassFish DataSource configuartion for MySql

To use MySQL with GlassFish we need the MySQL Connector/J which is the official JDBC driver for MySQL. Copy the JDBC driver to the GlassFish lib directory.

unzip mysql-connector-java-5.1.18.zip
sudo cp mysql-connector-java-5.1.18/mysql-connector-java-5.1.18-bin.jar \
  /opt/glassfish3/glassfish/lib/

The next thing we have to do is to restart GlassFish and configure our DataSource.

sudo /etc/init.d/glassfish restart

Login to the GlassFish admin console and create two JDBC Connection Pools one of them as XA DataSource.

• MySqlDataSource
• MySqlDataSourceXA

The two DataSources should have the following settings:

DataSource

• Pool Name: MySqlDataSource
• Resource Type: javax.sql.DataSource
• Database Driver Vendor: MySQL
• Datasource Classname: com.mysql.jdbc.jdbc2.optional.MysqlDataSource

XA DataSource

• Pool Name: MySqlDataSourceXA
• Resource Type: javax.sql.XADataSource
• Database Driver Vendor: MySQL
• Datasource Classname: com.mysql.jdbc.jdbc2.optional.MysqlXADataSource

Both DataSources need at least the following additional properties. Which are required to connect to the MySQL Database.

Additional Properties:

• ServerName: localhost
• Port: 3306
• User: glassfish
• Password: glassfish
• DatabaseName: glassfish_db

In the GlassFish admin console you can check if both DataSources are properly configured. When you click on the ping button you should receive a ping succeeded.

JDBC Resources:

For both DataSources we create now a JDBC resource with a JNDI name.

• JNDI Name: jdbc/MySqlDataSource
• Pool Name: MySqlDataSource

• JNDI Name: jdbc/MySqlDataSourceXA
• Pool Name: MySqlDataSourceXA

Finally

After that we can now use the two DataSources in our Java EE application.

The MySQL Workbench did not start up correctly and I got a
message from windows that the program crashed.

I also tried to install the MySQL Workbench as MSI package but I got
an error message that the Visual C++ 2010 redistributable package was not found.

To solve the problem you can download the Visual C++ 2010 redistributable package at
http://www.microsoft.com/download/en/details.aspx?id=5555

After you have installed the Visual C++ 2010 redistributable package, the MySQL Workbench ZIP (Archive) version will start up correctly on Windows.

When you are new to maven and want a broad overview how you can use maven in different setups then this book is just right for you. This book is ideal addition for beginners which want to get started with maven very quickly. But when you want a detailed overview about the internals of maven this is not the right book for you.

Personally for me the interesting part was the chapter Extending Apache Maven. In this chapter it’s explained how you can easily write a apache maven plugin (MOJO).

Conclusion

So if you are new to maven and want a broad overview then this book is just right for you. It will give you in a quick way answers to common problems and how to solve them.

If you have already experience with maven and use it with a SCM and CI server like Hudson, then this book is definitively not for you.

Should I buy the book?

It depends how experienced you are with maven? But to be honestly some years earlier this book would be great to save us some time for our project setup. It’s also a good addition to the other packt publishing book Apache Maven 2 Effective Implementation.

After the two day course you can take the online assessment to receive the PSM I certificate. You can also take the online assessment without the two day course but I would not recommend it, because you changes to succeed will not as good when you take the course.

This was not my first assessment in English for a certificate, but honestly I was not so easy as I tough to pass.

For someone which English is a foreign language there are some tough and complex questions.

When you take the course, read and and understand the scrum guide, have some experience with scrum and prepare yourself with the open assessment then you have a good change to pass the exam.

When you have a Ubuntu 64bit system you probably get the following error during the installation which was base on my previous post during an apt-get update.

W: Failed to fetch http://oss.oracle.com/debian/dists/unstable/Release
Unable to find expected entry  main/binary-amd64/Packages in
Meta-index file (malformed Release file?)

E: Some index files failed to download, they have been
ignored, or old ones used instead.

Or when you install the packages manually you would get the following error:

dpkg: error processing libaio_0.3.104-1_i386.deb (--install):
 package architecture (i386) does not match system (amd64)
Errors were encountered while processing:
 libaio_0.3.104-1_i386.deb

So you have the download the packages libaio_0.3.104-1_i386.deb and oracle-xe-universal_10.2.0.1-1.1_i386.deb.

• http://oss.oracle.com/debian/dists/unstable/main/binary-i386/libaio_0.3.104-1_i386.deb
• http://oss.oracle.com/debian/dists/unstable/non-free/binary-i386/oracle-xe-universal_10.2.0.1-1.1_i386.deb

After that we must force the installation with option –force-architecture.

sudo dpkg -i --force-architecture libaio_0.3.104-1_i386.deb
sudo dpkg -i --force-architecture oracle-xe-universal_10.2.0.1-1.1_i386.deb

Now we can configure the Oracle XE.

sudo /etc/init.d/oracle-xe configure

In this configuration we change the apex default port from 8080 to 8081 because when you want to install GlassFish later there will be no conflict. GlassFish use 8080 as the default port an we want to keep it that way.

Specify the HTTP port that will be used for
Oracle Application Express = 8081

Specify a port that will be used for the
database listener = 1521

Specify a password to be used for database
accounts (SYS and SYSTEM) = system

Do you want Oracle Database 10g Express
Edition to be started on boot  = yes

After that we only must add the ORACLE_HOME and modify the PATH variable in our bashrc file.

ORACLE_HOME=/usr/lib/oracle/xe/app/oracle/product/10.2.0/server
PATH=$PATH:$ORACLE_HOME/bin
export ORACLE_HOME
export ORACLE_SID=XE

export PATH

To install GlassFish an use with a Orcle XE Database go back to my previous post:
http://blog.rueedlinger.ch/2010/09/glassfish-3-and-oracle-10g-xe-on-ubuntu-linux-9-10/

Reference:
How To Install Oracle XE in Ubuntu 64 Bit, Aldiantoro Nugroho, 2008, http://littlebrain.org/2008/05/12/how-to-install-oracle-xe-in-ubuntu-64-bit/

I wrote this blog post because I wanted to use GlassFish and Oracle XE on my laptop to test some examples and I thought maybe someone else could find this step by step guide useful.

Oracle 10g XE installation

Note: Some of the explanation how to install Oracle on ubuntu is based on the wiki entry from the ubuntu site. See https://help.ubuntu.com/community/Oracle10g.

Ubuntu 64bit

If you try to follow this tutorial with an Ubuntu 64 bit check out the following site post Oracel 10g XE on Ubuntu 10.10 (64bit).

Before we install Oracle XE with apt-get we need to download and add the Oracle public key as trusted key.

wget http://oss.oracle.com/el4/RPM-GPG-KEY-oracle
sudo apt-key add RPM-GPG-KEY-oracle

Add the Oracle sources to /etc/apt/sources.list file.

deb http://oss.oracle.com/debian unstable main non-free

Update the sources and install Oracle XE.

sudo apt-get update
sudo apt-get install oracle-xe-universal

After the installation we can configure our Oracle XE installation with the following command.

sudo /etc/init.d/oracle-xe configure

The script asks for some configurations settings. It is important that you set the port for Oracle Application Express not to 8080, because GlassFish will use this port for the web applications. So we use instead the port 8081 for the Oracle Application Express (APEX).

Specify the HTTP port that will be used for
Oracle Application Express = 8081

Specify a port that will be used for the
database listener = 1521

Specify a password to be used for database
accounts (SYS and SYSTEM) = system

Do you want Oracle Database 10g Express
Edition to be started on boot  = yes

Note: When the option startup on boot is set to NO then you will have problems to start and stop Oracle XE with the /etc/init.d/oracle-xe script. See http://forums.oracle.com/forums/thread.jspa?threadID=944382 for more details.

When you have problems (set started on boot = NO) this workaround could help. Start Oracle XE with

sudo /etc/init.d/oracle-xe enabled
sudo /etc/init.d/oracle-xe start

and stop it with

sudo /etc/init.d/oracle-xe stop
sudo /etc/init.d/oracle-xe disabled

Note: With the script argument enabled / disabled you specifies if Oracle XE should automatically start when the system starts up.

The next step is to adjust the PATH settings, so that we can use sqlplus on our command line. The PATH variable is set in the .bashrc file.

.bashrc

ORACLE_HOME=/usr/lib/oracle/xe/app/oracle/product/10.2.0/server
PATH=$PATH:$ORACLE_HOME/bin
export ORACLE_HOME
export ORACLE_SID=XE

export PATH

After the installation there are some shortcuts (Start Database, Run SQL Command Line, etc.) in our start menu so we need to add our system user to the dba group so that we are allowed to use them.

sudo usermod -g dba my_user

We create a directory where Oracle can store our tablespaces and give the system user oracle the rights to this directory.

sudo mkdir /var/local/oracle
sudo chown oracle /var/local/oracle/

Setup the database

To create a tablespace and database user we start sqlplus as database user system.

sqlplus system/my_password

For our example we create a tablespace glassfish_app and a database user. I created just a simple tablespace with the size of 10M and a maximum size of 200M. Be sure that your project have other requirements and adjust this settings to your need. See http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_7003.htm for more details.

CREATE TABLESPACE glassfish_app DATAFILE '/var/local/oracle/glassfish.dbf'
     SIZE 10M
     AUTOEXTEND ON NEXT 200K
     MAXSIZE 200M;

For the tablespace glassfish_app we create our user glassfish and give him all rights. In a more serious environment you have to specify the privileges a bit better than I did.

CREATE USER glassfish
    IDENTIFIED BY glassfish
    DEFAULT TABLESPACE glassfish_app;

GRANT ALL PRIVILEGES TO glassfish;

GlassFish installation

Download the Platform-independent GlassFish (Full Platform) 3.0.1 ZIP from the GlassFish homepage and unzip the file.

unzip glassfish-3.0.1.zip

There should now be the directory glassfishv3 with the follwing content.

glassfishv3
            |-- bin
            |-- glassfish (1)
            |-- javadb (2)
            |-- mq (3)
            '-- pkg

1. GlassFish the application server
2. The Derby database
3. Open MQ the message broker

Next we need to install Java SDK 6.

sudo apt-get install sun-java6-jdk

Note: GlassFish Installations require JDK 6. The minimum and certified version required version is 1.6.0_20. This is not a problem with the newest update of Ubuntu Linux 9.10 (Karmic Koala).

Again we modify our .bashrc file and add the GlassFish directory to the PATH variable. Set the $GLASSFISH_DIR variable to the directory where you have unzipped your GlassFish installation.

.bashrc

GLASSFISH_DIR=/home/mr/bin/glassfishv3
GLASSFISH_HOME=$GLASSFISH_DIR/glassfish
DERBY_HOME=$GLASSFISH_DIR/javadb
OPEN_MQ_HOME=$GLASSFISH_DIR/mq

PATH=$PATH:$GLASSFISH_HOME/bin:$DERBY_HOME/bin:$OPEN_MQ_HOME/bin
export GLASSFISH_HOME
export DERBY_HOME
export OPEN_MQ_HOME

export PATH

To use the scripts from Open MQ and Derby we put their bin directories also into the PATH variable.

The next step is to add the Oracle JDBC driver to the GlassFish lib directory. You should find the Oracle JDBC driver ojdbc14.jar in $ORACLE_HOME/jdbc/lib. Copy the ojdbc14.jar in your GlassFish domain lib/ext directory. The default domain in GlassFish is named domain1, so when your domain has a different name you should replace domain1 with your GlassFish domain name.

cp $ORACLE_HOME/jdbc/lib/ojdbc14.jar \
    $GLASSFISH_HOME/domains/domain1/lib/ext

Note: When you want to install GlassFish 3 as service then these blog entries could help you:

• http://blogs.sun.com/foo/entry/how_to_run_glassfish_v3
• http://blogs.sun.com/foo/entry/run_glassfish_v3_as_a

GlassFish configuration

Now we have to start GlassFish and go to the GlassFish admin console http://localhost:4848

asadmin start-domain

Note: By default there is no password set. A password can be set in the menu Enterprise Server > Administrator Password.

We create now our Connection Pool with the following settings.

Pool Name: OraclePool
Resource Type: javax.sql.DataSource
Datasource Classname: oracle.jdbc.pool.OracleDataSource

In the additional properties we have to set password, username and the connection url.

URL: jdbc:oracle:thin:@localhost:1521:xe
Password: glassfish
User: glassfish

To test the connection click on the ping button. When all settings are valid you should receive a “ping succeeded”.

Note: When the ojdbc14.jar is note found you should get a message like Class name is wrong or classpath is not set for : oracle.jdbc.pool.OracleDataSource Please check the server.log for more details.

The next step is to create a JDBC resource. Here we specify the Connection Pool and a JNDI name for our JDBC resource which can be used by our next Java EE project.

JNDI Name: jdbc/dbOraclePool
Pool Name: OraclePool

Finally…

So it’s time for the fun part create a Java EE project which uses our new JDBC resource.
I hope this post was useful and you get a quick start to setup your development infrastructure.

log4j:WARN No appenders could be found for logger (com.foo.xxx).
log4j:WARN Please initialize the log4j system properly.

This happens when your application or a framework like spring, hibernate, etc. tries to make a log statement and log4j is not yet initialized. The point is that you must configure your log4j before your application or framework tries to log something.

Old School Servlet Approach

In a web environment you could use a servlet with load-on-startup which specifies that the servlet should be loaded when the web application is started.  In that servlet you could initialize log4j, but that’s the old-fashioned way

<servlet>
  <servlet-name>log4j-init</servlet-name>
  <servlet-class>com.foo.Log4jInit</servlet-class>
  <init-param>
    <param-name>log4j-init-file</param-name>
    <param-value>WEB-INF/classes/log4j.lcf</param-value>
  </init-param>
  <load-on-startup>1</load-on-startup>
</servlet>

See http://logging.apache.org/log4j/1.2/manual.html for more Details.

EJB 3.1 Approach

With Java EE 6, especially EJB 3.1 we have the possibility to write an EJB 3.1 Application Startup Bean which can do the initialization of log4j for use.

@Singleton
@Startup
public class Log4jStartupBean{

   @PostConstruct
   private void startup() { ... }

   @PreDestroy
   private void shutdown() { ... }

    ...
}

What we need is our log4j.xml configuration file. I choose the approach to put the configuration file it in the META-INF directory and get the file path with Class.getResource(String name). An alternative could be to use System.getProperty(String key) to get the file path to a system wide log4j configuration file set by your application server or by resource injection @Resource(name=”…”) from the EJB container.

For the META-INF approach a typical mavenized project with a resources folder is all we need.

my-app
|-- pom.xml
`-- src
    |-- main
    |   |-- java
    |   |   `-- com
    |   |       `-- mycompany
    |   |           `-- app
    |   |               `-- Log4jStartupBean.java
    |   `-- resources
    |       `-- META-INF
    |           `-- log4j.xml
    `-- test

Note: When your EJB 3.1 project is a WAR module and you use the META-INF approach you have to add the resources directory as webResources by the maven-war-plugin. See http://maven.apache.org/plugins/maven-war-plugin/

So now we just need to initialize log4J in the startup() Method in the Log4jStartupBean class.

@Singleton
@Startup
public class Log4jStartupBean{

   private static final String LOG4J_XML = "/META-INF/log4j.xml";
   private Logger logger = null;

     ...

   @PostConstruct
   public void startup() {
	URL url = this.getClass().getResource(LOG4J_XML);

	if(url == null || url.getFile().length() == 0) {
		throw new RuntimeException("Log4j config file "+ LOG4J_XML +" not found");
	}

	DOMConfigurator.configure(url.getFile());
	logger = Logger.getLogger(this.getClass());
	logger.info("logger initialized with "+ LOG4J_XML + "...");
         ...
   }
 ...
}

In this example code we used the DOMConfigurator class to configure log4j with a XML file. More information about the XML configuration can be found on the log4j wiki page.
You could use a log4j properties file for the configuration but then you have to use the PropertyConfigurator class.

When you have other singelton startup beans and these beans also need to use log4j, we must determine the starting order of the beans with the @DependsOn Annotation.

For further Reading about EJB 3.1 I would recommend you the following sites:

• http://blogs.sun.com/enterprisetechtips/entry/a_sampling_of_ejb_3
• http://openejb.apache.org/singleton-ejb.html

Note: How to configure multiple log4j for different war modules in a single EAR see http://stackoverflow.com/questions/762918/how-to-configure-multiple-log4j-for-different-wars-in-a-single-ear

Note: I tested this example with GlassFish 3.0.1 as WAR module.

Pencil is available as standalone application for linux and windows and can also be used as firefox plugin. For the next GUI prototyping session I will definitely give it a try.