Alex Joh's Blog

Developing SPA app with AngularJS, Spring, SpringBoot, REST, and MyBatis - 2. Unit Testing Introduction From the first posting, we just created simple application and run the application using maven and SpringBoot. From this tutorial, we will try to figure out how to do the unit testing with SpringBoot Recommend Syntax and UI for atom seti-ui seti-syntax or monaki theme To find out best theme downloads from atom, please visit Atom theme download site Folder structure root/pom.xml root/src/main/java/AngularSpring.java root/src/main/test/AngularSpringTest.java Setting up the Unit Testing When you add spring-boot-starter-test into the POM file, following 4 libraries will be added; Spring Test — integration test support for Spring applications. JUnit — The de-facto standard for unit testing Java applications. Hamcrest — A library of matcher objects (also known as constraints or predicates) allowing assertThat style JUnit assertions. Mockito — A Java mocking fram

Developing SPA app with Atom, AngularJS, Spring, SpringBoot, REST, and MyBatis - 1. Setup Environment Introduction I believe the SPA(Single Page Application) will be the direction of future software development and this will be my first small project to develop SPA using following major components; AngularJS for the front-end, Spring REST for the back-end, Spring Boot for running environment, and MyBatis for the database persistence layer. I am a big fan of MyBatis because of flexibility, performance, and easy way to implement MVVM framework. One of main reason to develop this sample is to understand the structure of AngularJS and Spring framework. If you develop applications with STS or Eclipse, these IDEs will do everything for you, but sometimes it is hard to understand what happening behind scene. If you are not familiar with Spring Boot project, I strongly recommend to read Official SpringBoot Start Document Reference article Should You Use Spring Boot in Your Next Proje

Upgrading graylog from 1.2 to 1.3 Dec 10, 2015 Recently version 1.3 was released and this is the instruction to upgrade from 1.2 to 1.3 from ubuntu 14.04     sudo wget https://packages.graylog2.org/repo/packages/graylog-1.3-repository-ubuntu14.04_latest.deb   sudo dpkg -i graylog-1.3-repository-ubuntu14.04_latest.deb   sudo apt-get update   sudo apt-get dist-upgrade   You will see the following packages for graylog   The following packages will be upgraded:   graylog-server graylog-web liboxideqt-qmlplugin liboxideqtcore0   liboxideqtquick0 oxideqt-codecs   During installation, please select No for the question about changing the server.conf file. If you overwrite this configuration file, you will need to update the server.conf file again. For the detail, please review the my previous posting about installing icinga, graylog, and cacti.   Written with StackEdit .

Installing Icinga 2.4.1, Graylog 1.2.2, and Cacti 0.8.8 Date: Dec 7, 2015 Overview Before investing to commercial monitoring software, I decided to use open source product and final choice is Icinga for monitoring, Graylog for log collection, and Cacti for graph. The MySQL is the choice because of the Cacti. The Cacti doesn’t support the Postgresql. Version - Ubuntu: 14.04 - Icinga: 2.4.1 - Icinga Web: 2.1.0 - Graylog Server: 1.2.2 - Graylog web: 1.2.2 - Java: 7.x - MongoDB: 2.6.11 - ElasticSearch: 1.7 - Cacti: 0.8.8 Useful command Checking contents in the package Using dpkg alex@monitoring:~$ sudo dpkg -l icinga2 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==============-============-============-================================= ii icinga2