Posts Tagged Continous Integration

Virtual Development Server: Provide Docker images in docker registry for Oracle XE Database and others

For later creation of containers as needed in the deployment process we have first to build docker images whenever we do not find suitable one in docker hub.

For most of my development I need a oracle database. On the internet you can find a lot of Dockerfile’s for this, but no ready image. This is because for running a database you have to accept a license and this happens when you download the installation software. For private testing this license often is free.

The basic cycle for all of this images is the same on my side:

  1. Find a Docker image
  2. If not found download required Software and build a Docker image
  3. Build the Docker image
  4. Push the images to private docker registry or the public registry DockerHub

Fortunately Oracle provides recently on GitHub a lot of working Dockerfile’s for building different product images. The creator Gerald Venzl desribes in this blog how to create an Oracle EE image.

Following you find an example for building Oracle XE Image.

First you have to clone the git repository to a directory of you choice, I choose C:\shared\scmlocal\docker-images.
Put the downloaded installation source in the subdirectory C:\shared\scmlocal\docker-images\OracleDatabase\dockerfiles\ as described in GitHub.
Next we have to map this directory to our virtualbox via following vagrant instructions. Additional we prepare port forwarding for accessing later the database from our host system.

  # Port Forwardings for:
  # - Oracle database port "forwarded_port", guest: 1521, host: 1521
  # Oracle Application Express (APEX) "forwarded_port", guest: 8080, host: 8080
  # map Oracle Docker Images installation path
  config.vm.synced_folder "C:\\shared\\scmlocal\\docker-images", "/docker-images", :mount_options => ["dmode=777","fmode=777"]

After that restart the virtualbox and connect to it via

vagrant halt
vagrant up
vagrant ssh

In the output you can see this mapping.

    default: 1521 (guest) => 1521 (host) (adapter 1)
    default: 5000 (guest) => 5000 (host) (adapter 1)
    default: 8080 (guest) => 8080 (host) (adapter 1)
    default: /docker-images => C:/shared/scmlocal/docker-images

Now you create build the image with the Oracle XE (-x) database version (-v) via the provided scripts from oracle. -i skips the MD5 checksum check, as the checksums are not checked in as UNIX text format and so does not work in our vagrant on windows / oel virtualbox combination.

cd /docker-images/OracleDatabase/dockerfiles
./ -v -x -i

Now you have to wait some time. When the process is ready, you get at the time of this writing an image with the binaries installed.

docker images
REPOSITORY          TAG                 IMAGE ID            CREATED              SIZE
oracle/database         624d78c89ccb        About a minute ago   1.203 GB
registry            latest              c6c14b3960bd        5 weeks ago          33.28 MB
oraclelinux         latest              1988eb5b3fc6        6 weeks ago          278.2 MB

Next we tag this image for pushing to the local docker repository, which we have created in the first blog of this series and is up with every vagrant up of our virtualbox. After that we push it to the registry.

docker tag oracle/database: localhost:5000/oracle/database:
docker push localhost:5000/oracle/database:

In the output we see the succesful push.

The push refers to a repository [localhost:5000/oracle/database]
345dfbce8859: Pushed
dd4b46d40894: Pushed
11327e04fac0: Pushed digest: sha256:82058ca2c5c201ff46471a8db4d9569da9869d420727595884050f94dad0ec85 size: 955

Now we will check, if we can create a Docker container from our image in the registry and the database is working in it. Therefore at first we delete the oracle/database and oraclelinux images from our virtualbox. Then we create the container.

docker rmi 624d78c89ccb -f
docker rmi 1988eb5b3fc6
sudo docker run --shm-size=1g -p 1521:1521 -p 8080:8080 --name="db11.2.0.2-xe" --restart unless-stopped localhost:5000/oracle/database:

In line 3 we pull the image from the local registry, start a container, open the ports 1521 and 8080 to the virtualbox and give the container a name.

Unable to find image 'localhost:5000/oracle/database:' locally Pulling from oracle/database

10ec637c060c: Pull complete
1902f66bc90b: Pull complete
dd8942200fe1: Pull complete
Digest: sha256:41ce1015c8f68ce063e855e7afa96000ededeef1e197e2181bc04c9577d73a1b
Status: Downloaded newer image for localhost:5000/oracle/database:

Oracle Database 11g Express Edition Configuration
This will configure on-boot properties of Oracle Database 11g Express
Edition.  The following questions will determine whether the database should
be starting upon system boot, the ports it will use, and the passwords that
will be used for database accounts.  Press <Enter> to accept the defaults.
Ctrl-C will abort.

Specify the HTTP port that will be used for Oracle Application Express [8080]:
Specify a port that will be used for the database listener [1521]:
Specify a password to be used for database accounts.  Note that the same
password will be used for SYS and SYSTEM.  Oracle recommends the use of
different passwords for each database account.  This can be done after
initial configuration:
Confirm the password:

Do you want Oracle Database 11g Express Edition to be started on boot (y/n) [y]:
Starting Oracle Net Listener...Done
Configuring database...Done
Starting Oracle Database 11g Express Edition instance...Done
Installation completed successfully.

SQL*Plus: Release Production on Tue Sep 6 09:41:22 2016

Copyright (c) 1982, 2011, Oracle.  All rights reserved.

Connected to:
Oracle Database 11g Express Edition Release - 64bit Production

PL/SQL procedure successfully completed.

SQL> Disconnected from Oracle Database 11g Express Edition Release - 64bit Production
db_recovery_file_dest_size of 10240 MB is 0.98% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Starting background process CJQ0
Tue Sep 06 09:41:19 2016
CJQ0 started with pid=26, OS id=759
Tue Sep 06 09:41:24 2016
XDB installed.
XDB initialized.

In line 9 you can see the autogenerated passwords.
When line 46 appears, you can connect to the database.
With following command you can change the passwords of SYS and SYSTEM:

sudo docker exec db11.2.0.2-xe /u01/app/oracle/ LetsDocker

You see following output:

SQL*Plus: Release Production on Tue Sep 6 15:49:34 2016
Copyright (c) 1982, 2011, Oracle.  All rights reserved.
Connected to:
Oracle Database 11g Express Edition Release - 64bit Production
User altered.
User altered.

As long as you not remove or manually stop the container, it restarts with the virtualbox now via:

vagrant halt
vagrant up

At the moment you cannot make your database instance data persistent for this container, I have opened an issue for this, but Gerald Venzl has promised to to implement this later.

Here you find the source code for this blog.

That’s it.


  • GitHub – oracle-docker-images Official source for Docker configurations, images, and examples of Dockerfiles for Oracle products
  • Creating and Oracle Database Docker image (Developing using Oracle technologies)
  • , , , , , , , , , , , ,

    Leave a comment

    Virtual Development Server: Add swapfile to VirtualBox as requirement for installing Oracle or build Oracle docker images

    As I want later build Oracle docker images, some of this need a swapfile.

    Per default my used Vagrantbox, does not have one, so later steps will fail.

    As in the last blog I use a Vagrant shell provider.

      # add swapfile to the box
      config.vm.provision :shell, :path => ""

    This calls the script in the created VirtualBox machine.
    Make sure, that you create your swapfile on a supported file system.

    # size of swapfile in megabytes
    # does the swap file already exist?
    grep -q "swapfile" /etc/fstab
    # if not then create it
    if [ $? -ne 0 ]; then
      echo 'swapfile not found. Adding swapfile.'
      # allocate the disk space
      sudo fallocate -l ${swapsize}M /home/swapfile
      # only owner can read and write
      sudo chmod 600 /home/swapfile
      # sets up swap area in the file
      sudo mkswap /home/swapfile
      # enable file for paging and swapping
      # if this comes with "swapon failed: Invalid argument", 
      # check if the filesystem is supported for swap, xfs eg. is not
      sudo swapon /home/swapfile
      # mount the swapfile at boot
      echo '/home/swapfile none swap defaults 0 0' >> /etc/fstab
      echo 'swapfile found. No changes made.'
    # output results to terminal
    df -h /home/swapfile
    cat /proc/swaps
    cat /proc/meminfo | grep Swap

    Now you have to recreate the VirtualBox machine via

    vagrant destroy
    vagrant up

    In the output you can now see, how the swapfile is added.

    ==> default: Running provisioner: shell...
        default: Running: C:/Users/torst/AppData/Local/Temp/
    ==> default: swapfile not found. Adding swapfile.
    ==> default: Setting up swapspace version 1, size = 2150396 KiB
    ==> default: no label, UUID=20ff8dbf-6282-4ba6-abe4-05c04c74aac8
    ==> default: Filesystem              Size  Used Avail Use% Mounted on
    ==> default: /dev/mapper/linux-home  3.8G  2.4G  1.5G  63% /home
    ==> default: Filename                           Type            Size    Used    Priority
    ==> default: /home/swapfile                          file               2150396 0       -1
    ==> default: SwapCached:            0 kB
    ==> default: SwapTotal:       2150396 kB
    ==> default: SwapFree:        2150396 kB

    Here you find the source code for this blog.

    That’s it.


  • Increasing swap size.
  • , , , , , , , ,

    Leave a comment

    Virtual Development Server: Add enough ram and disk space to VirtualBox for further server components

    As I want later build docker images and run docker containers I have to provide enough disk space for this.

    Per default the Vagrantboxes have vmdk disks, these have a static size and are to small for my purposes.

    Therefore I convert the disk, which comes with the box, via Vagrant VirtualBox provider from vmdk to vdi, so that it allocate only the used disk space in the host system.
    Additional I add a second big disk:

      # virtualbox provider
      config.vm.provider "virtualbox" do |vb|
        # name in VirtualBox = "Development Server"
        # configure 16 GB memory 
        vb.customize ["modifyvm", :id, "--memory", "16384"]
        # clone the original vmdk disk into a dynamic vdi disk, which only allocate the used space on the host
        if ARGV[0] == "up" && ! File.exist?("#{ENV["HOME"]}/VirtualBox VMs/#{}/#{}.vdi")
          # configure the SATA controller for second disk port, for other box you may have another controller
          vb.customize [
            "storagectl", :id, 
            "--name", "SATA", 
            "--controller", "IntelAHCI", 
            "--portcount", "1", 
            "--hostiocache", "on"
          # clone the original disk, for other box you may have another disk name
          vb.customize [
            "clonehd", "#{ENV["HOME"]}/VirtualBox VMs/#{}/box-disk2.vmdk", 
                 "#{ENV["HOME"]}/VirtualBox VMs/#{}/#{}.vdi", 
            "--format", "VDI"
          # attach the cloned disk to the controller
          vb.customize [
            "storageattach", :id, 
            "--storagectl", "SATA", 
            "--port", "0", 
            "--device", "0", 
            "--type", "hdd",
            "--nonrotational", "on",
            "--medium", "#{ENV["HOME"]}/VirtualBox VMs/#{}/#{}.vdi" 
          # delete the original disk to release it's space
          vb.customize [
            "closemedium", "disk", "#{ENV["HOME"]}/VirtualBox VMs/#{}/box-disk2.vmdk", 
        # create addtional big dynamic vdi disk for docker images
        if !File.exist?("#{ENV["HOME"]}/VirtualBox VMs/#{}/#{}_docker.vdi")
          # create addtional big dynamic vdi (200 GB)
          vb.customize [
            "--filename", "#{ENV["HOME"]}/VirtualBox VMs/#{}/#{}_docker.vdi", 
            "--format", "VDI", 
            "--size", 200 * 1024
          # attach the addtional disk to the controller
          vb.customize [
            "storageattach", :id, 
            "--storagectl", "SATA", 
            "--port", "1", 
            "--device", 0, 
            "--type", "hdd",
            "--medium", "#{ENV["HOME"]}/VirtualBox VMs/#{}/#{}_docker.vdi"
      # shell provider
      # format the additional disk and add the free space to the box
      config.vm.provision :shell, :path => ""

    Lines 64..66 adds the additional disk space to a logical volume via a Vagrant shell provider, which calls the script in the created VirtualBox machine.
    Resizing the first disk does not work, as therefore the machine has to be booted, which cannot be handled with Vagrant.

    # exit immediately if a command exits with a non-zero status.
    set -e
    # activate debugging from here
    set -x
    if [ -f /etc/disk_added_date ] ; then
       echo "disk already added so exiting."
       exit 0
    # show diskspace of the logical volume before adding the disk
    df -h /dev/mapper/linux-root
    # partitioning the disk
    sudo fdisk -u /dev/sdb <<EOF
    # initialize the partition for use by logical volume manager
    sudo pvcreate /dev/sdb1
    # add the partition to volume group linux
    sudo vgextend linux /dev/sdb1
    # increase the size of the logical volume /dev/mapper/linux-root
    sudo lvextend --extents +51199 --resizefs /dev/mapper/linux-root
    # mark that the disk was added
    date > /etc/disk_added_date
    # show diskspace of the logical volume after adding the disk
    df -h /dev/mapper/linux-root

    Now you have to recreate the VirtualBox machine via

    vagrant destroy
    vagrant up

    In the output you can now see, how the logical volume grows:

    ==> default: Running provisioner: shell...
        default: Running: C:/Users/torst/AppData/Local/Temp/
    ==> default: ++ '[' -f /etc/disk_added_date ']'
    ==> default: ++ df -h /dev/mapper/linux-root
    ==> default: Filesystem              Size  Used Avail Use% Mounted on
    ==> default: /dev/mapper/linux-root   16G  1.9G   14G  12% /
    ==> default: ++ sudo fdisk -u /dev/sdb
    ==> default: Welcome to fdisk (util-linux 2.23.2).
    ==> default:
    ==> default: Changes will remain in memory only, until you decide to write them.
    ==> default: Be careful before using the write command.
    ==> default:
    ==> default:
    ==> default: Command (m for help): Partition type:
    ==> default:    p   primary (0 primary, 0 extended, 4 free)
    ==> default:    e   extended
    ==> default: Select (default p): Partition number (1-4, default 1): First sector (2048-419430399, default 2048): Using default value 2048
    ==> default: Last sector, +sectors or +size{K,M,G} (2048-419430399, default 419430399): Using default value 419430399
    ==> default: Partition 1 of type Linux and of size 200 GiB is set
    ==> default:
    ==> default: Command (m for help): Selected partition 1
    ==> default: Hex code (type L to list all codes): Hex code (type L to list all codes): Changed type of partition 'Linux' to 'Linux LVM'
    ==> default:
    ==> default: Command (m for help):
    ==> default: Device does not contain a recognized partition table
    ==> default: Building a new DOS disklabel with disk identifier 0xb4c74c64.
    ==> default: The partition table has been altered!
    ==> default:
    ==> default: Calling ioctl() to re-read partition table.
    ==> default: Syncing disks.
    ==> default: ++ sudo pvcreate /dev/sdb1
    ==> default:   Physical volume "/dev/sdb1" successfully created
    ==> default: ++ sudo vgextend linux /dev/sdb1
    ==> default:   Volume group "linux" successfully extended
    ==> default: ++ sudo lvextend --extents +51199 --resizefs /dev/mapper/linux-root
    ==> default:   Size of logical volume linux/root changed from 15.62 GiB (4000 extents) to 215.62 GiB (55199 extents).
    ==> default:   Logical volume root successfully resized.
    ==> default: meta-data=/dev/mapper/linux-root isize=256    agcount=4, agsize=1024000 blks
    ==> default:          =                       sectsz=512   attr=2, projid32bit=1
    ==> default:          =                       crc=0        finobt=0
    ==> default: data     =                       bsize=4096   blocks=4096000, imaxpct=25
    ==> default:          =                       sunit=0      swidth=0 blks
    ==> default: naming   =version 2              bsize=4096   ascii-ci=0 ftype=0
    ==> default: log      =internal               bsize=4096   blocks=2560, version=2
    ==> default:          =                       sectsz=512   sunit=0 blks, lazy-count=1
    ==> default: realtime =none                   extsz=4096   blocks=0, rtextents=0
    ==> default: data blocks changed from 4096000 to 56523776
    ==> default: ++ date
    ==> default: ++ df -h /dev/mapper/linux-root
    ==> default: Filesystem              Size  Used Avail Use% Mounted on
    ==> default: /dev/mapper/linux-root  216G  1.9G  214G   1% /

    Here you find the source code for this blog.

    That’s it.


  • VirtualBox : Extend Virtual Disk and File System
  • Resizing disk space on vagrant box
  • , , , , , , , , ,

    Leave a comment

    Virtual Development Server: Creating Virtualbox machine including docker containers with Vagrant

    As I want to decouple my development server from my computer as much as possible I want to create first a virtual machine with linux.

    Because I have used Oracle Virtualbox in the past successfully, I will use it here too.

    As I want have later a reproducible environment via Infrastructure as code, I give Vagrant a try for this. As source code management system I use GIT, my remote repository is located at GitHub.

    As I don’t want create a new linux from scratch, I have looked for a ready system at Vagrantboxes, which contains a new Oracle Linux version, and find a Oracle Linux 7.1 x86_64 system with Chef and Puppet preinstalled.

    Before I could start, I had to install on my Windows 10 computer Vagrant 1.8.5 and Oracle Virtualbox 5.0.16. Don’t use the 5.1 Version, as at this is not yet supported by vagrant 1.8.5.

    For automatic update of the Oracle VM VirtualBox Extension Pack, which is delivered with the ready box and is required for use of shared folders and more, you should install following plugin as described here:

    vagrant plugin install vagrant vbguest

    Next I have created a directory of your choice and init there a Vagrantfile by calling

    vagrant init

    Then I changed the Vagrantfile as following, see the inline comments for documentation:

    Vagrant.configure(2) do |config|
      # Use the mentioned ready OEL 7 linux box = ""
      config.vm.box_url = ""
      # Create a private network "private_network", type: "dhcp"
      # persistant storage for all docker container
      config.vm.synced_folder "C:\\shared\\virtual_storage", "/virtual_storage", :mount_options => ["dmode=777","fmode=777"]
      # virtualbox provider
      config.vm.provider "virtualbox" do |vb|
        # name in VirtualBox = "Development Server"
      # Docker Private Registry container for storing later builded docker images, which are not in the Docker Public Registry at
      config.vm.provision "docker" do |d| "registry", image: "registry", daemonize: true, args: "-d -p 5000:5000 -v /virtual_storage/docker_registry:/var/lib/registry"

    Run next from the created directory

    vagrant up

    Following you see the output

    Bringing machine 'default' up with 'virtualbox' provider...
    ==> default: Importing base box ''...
    ==> default: Matching MAC address for NAT networking...
    ==> default: Setting the name of the VM: Development Server
    ==> default: Clearing any previously set network interfaces...
    ==> default: Preparing network interfaces based on configuration...
        default: Adapter 1: nat
        default: Adapter 2: hostonly
    ==> default: Forwarding ports...
        default: 22 (guest) => 2222 (host) (adapter 1)
    ==> default: Booting VM...
    ==> default: Waiting for machine to boot. This may take a few minutes...
        default: SSH address:
        default: SSH username: vagrant
        default: SSH auth method: private key
        default: Warning: Remote connection disconnect. Retrying...
        default: Vagrant insecure key detected. Vagrant will automatically replace
        default: this with a newly generated keypair for better security.
        default: Inserting generated public key within guest...
        default: Removing insecure key from the guest if it's present...
        default: Key inserted! Disconnecting and reconnecting using new SSH key...
    ==> default: Machine booted and ready!
    [default] GuestAdditions versions on your host (5.0.26) and guest (5.0.12) do not match.
    Loaded plugins: ulninfo
    Package kernel-uek-devel-4.1.12-32.el7uek.x86_64 already installed and latest version
    Package gcc-4.8.5-4.el7.x86_64 already installed and latest version
    Package 1:make-3.82-21.el7.x86_64 already installed and latest version
    Package 4:perl-5.16.3-286.el7.x86_64 already installed and latest version
    Package bzip2-1.0.6-13.el7.x86_64 already installed and latest version
    Nothing to do
    Copy iso file C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso into the box /tmp/VBoxGuestAdditions.iso
    mount: /dev/loop0 is write-protected, mounting read-only
    Installing Virtualbox Guest Additions 5.0.26 - guest version is 5.0.12
    Verifying archive integrity... All good.
    Uncompressing VirtualBox 5.0.26 Guest Additions for Linux............
    VirtualBox Guest Additions installer
    Removing installed version 5.0.12 of VirtualBox Guest Additions...
    Removing existing VirtualBox non-DKMS kernel modules[  OK  ]
    Copying additional installer modules ...
    Installing additional modules ...
    Removing existing VirtualBox non-DKMS kernel modules[  OK  ]
    Building the VirtualBox Guest Additions kernel modules
    Building the main Guest Additions module[  OK  ]
    Building the shared folder support module[  OK  ]
    Building the shared folder support module[  OK  ]
    Building the graphics driver module[  OK  ]
    Doing non-kernel setup of the Guest Additions[  OK  ]
    You should restart your guest to make sure the new modules are actually used
    ==> default: Checking for guest additions in VM...
    ==> default: Configuring and enabling network interfaces...
    ==> default: Mounting shared folders...
        default: /vagrant => C:/shared/scmlocal/blog
        default: /virtual_storage => C:/shared/virtual_storage
    ==> default: Running provisioner: docker...
        default: Installing Docker onto machine...
    ==> default: Starting Docker containers...
    ==> default: -- Container: registry

    In lines 1..24 you see the loading of the ready box and booting with the defined network
    In lines 25..50 the version of the VirtualBox GuestAdditions of the box is checked and after that replaced with the actual installed VirtualBox version. This happens only on the first “vagrant up” call.
    In lines 57..58 Docker is installed as a Vagrant Docker provider is called in the Vagrantfile line 20 and it does not exist in the box before.
    In lines 59..60 a Docker Private Registry container is started via loading docker image from the Docker Public Registry. In a later blog we will use this Docker Private Registry container to hold our own created docker images like database and development tools. The pushed images are saved to a mapped host volume of my windows 10 computer.

    You can connect to the virtualbox directly via

    vagrant ssh

    The you can see the downloaded Docker Private Registry images and the started container from this image:

    [vagrant@oraclelinux7 ~]$ docker images
    REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE
    registry            latest              c6c14b3960bd        13 days ago         33.28 MB
    [vagrant@oraclelinux7 ~]$ docker ps
    CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                    NAMES
    739c1c9926b1        registry            "/ /etc/"   5 minutes ago       Up 5 minutes>5000/tcp   registry

    You can now stop the Development Server via

    vagrant halt

    If you startup again the server via

    vagrant up

    the provision steps are not replayed until you destroy the server or explicitly call the provision again via

    vagrant provision

    Here you find the source code for this blog.

    That’s it.

    , , , , , , , ,

    1 Comment

    #Javaland 2016 conference day 2


    This was my second day:

    Michael Tamm (optivo GmbH): Feature Toggles on Steroids

    Very good summary off all topic’s covering feature toggles. Wish I had this summary 2 years before, were we have evaluated this. Unfortunately furthermore no solutions for declarative frameworks like Oracle ADF with it’s wizards and xml configurations, which later generated code. Ironic answer to my question: “Don’t use frameworks – use Java”

    Alexander Casall (Saxonia Systems AG): User Experience for techies

    Now comes someting completely different. As least I had expected. No techniques etc.. There are really german standards “Ergonomics of human-system interaction” in ISO 9241 – 110 (Dialogue principles) and ISO 9241 – 210 (Ergonomics of human-system interaction). I have to read this, if it really would help in development, or the presenter interprets this on its own. Nice and surprising presentation.

    Adam Gowdiak (Security Explorations): Java (in)security (Keynote)

    The presenter is really angry about Oracle and co. and the security in Java. Nevertheless it seems he has specialized only on this topic and earn this money on this. So I doesn’t know, if somebody or another product is better. What about security in OpenJDK? And what are now my alternatives? A little depressing keynote.

    Lars Röwekamp (open knowledge GmbH): Courage to professionalism

    I don’t know, what I had expected here, but this was a nice surprise too. The talk was about to find a common language between customer, analyst, developer and other roles. The patterns “Rich Entities” and “Value Objects” helps to find a way out of the helper, util and manager class hell and seems to improve the readability of the code for all stakeholders. But how will this fit in declarative Frameworks like Oracle ADF and it’s generated classes? Have to think about it. Very good speaker!

    Wolfgang Weigend (Oracle Deutschland): Build and Monitor Cloud PaaS with JVM’s Nashorn JavaScripts

    Unfortunately the worst presentation comes from Oracle itself. To be fair: this presentation should be held by Bruno Borges, which was prevented to come to Javaland. Tip: Never hold a presentation, which is created by another person, if you don’t know, what he know about the subject. But I’m not sure if I had understood more, if Bruno had held the presentation. I didn’t find a red thread in the slides. And I must add, I didn’t really find an alternative presentation in this time slot.

    Alexander Heusingfeld, Tammo van Lessen (innoQ Deutschland GmbH): When Microservices Meet Real-World Projects: Lessons Learned

    Interesting presentation but the topic was missed. This had little to do with Microservice, more what a consultant or any person has to learn on his way from Junior to Senior: communicate, communicate, communicate. Especially when you want to change something.

    Stephan Kaps (Bundesversicherungsamt): Flyway vs. LiquiBase – Battle of the database migration tools

    I wanted to do this comparison several times before, but had never enough time. Now I’m relative sure that I will start with Liquibase in my next private project before I develop the application. This was the subjective winner of the battle too. I’m overwhelmed by the mass of features of both tools. Very good summary!

    Architecture Kata

    This was a nice workshop to plan the application and technical architecture of a given small set of requirements. Result for me: the many participants from a lot of other companies comes to very similar architecture depending on the assumption they made. In real life you have to communicate again and again with your stakeholders to get answered all of the questions and get quick feedback from them. I have urgently to refresh my knowledge of tools for UML diagramming and graphical presentations. And for structured proceeding maybe I should look for TOGAF training?


    This was inspiring conference, which gives me a lot of fresh ideas and reminders for some spilled goals for my private and company projects. I think we’ll see us next year!

    That’s it!

    , , , , , , , , , , , , , , , ,

    Leave a comment

    “Bob the Builder: Build/Deploy of #ADF enterprise applications” – I’m a speaker at #DOAG2015:


    Today my presentation is confirmed:  “Bob the Builder: Build/Deploy of ADF enterprise applications”.

    I will speak over our experiences with following

    • build tools
    • deployment tools
    • architecture
    • versioning & branching
    • continuous integration
    • hot deployment in development
    • compile & runtime dependencies

    If you speak german and you are interested in some of this, you should come and attend DOAG 2015.

    , , , , , , , , , ,

    Leave a comment

    Slides for my german presentation “Quality Assurance for ADF projects” available

    I have presented today on DOAG Development 2014 in Dusseldorf. For all non DOAG members – you can find the german presentation on slideshare too.


    , , , , , , , , , , , , , , , , , ,

    Leave a comment

    Quality Assurance for ADF projects

    If you speak german and you are interested in quality assurance for your ADF projects you should come and attend my presentation at DOAG Development on 06/04/2014 in Dusseldorf.

    I will show you, how you can implement in the JDeveloper IDE and in Continous Integration server Jenkins:

    • static code analysis with PMD, FindBugs and Checkstyle
    • Task’s
    • Commit tests with JUnit, Mockito and Powermock for Mockito
    • Code coverage for commit tests with JaCoCo
    • Acceptance tests with JUnit and Selenium

    See you!


    , , , , , , , , , , , , , , , , , ,


    %d bloggers like this: