Configuring CouchDB uuid generation algorithm

CouchDB can generate _id field of documents for you when you store the documents using POST instead of PUT. The algorithm used by CouchDB to generate the _id fields can be changed although the options are small. We can pick below algorithms for couch db to use to generate the _id fields of our documents: (http://wiki.apache.org/couchdb/HttpGetUuids)

1. sequential: 26 hex character random prefix, followed by 6 hex characters of sequence, which is incremented by random amounts. When the 6 character sequence overflows, a new random prefix is chosen. There are no guarantees of ordering, but most inserted documents will be sequentially ordered. This improves insert speed as most B-tree edits do not happen randomly. Also, if the documents are likely to be accessed sequentially, this improves access speeds.
2. random: 32 hex characters generated completely at random.
3. utc_random: First 14 hex characters are microseconds since Jan 1, 1970 (Unix epoch), followed by 18 random hex characters.

To Update the setting ew can use REST api of the couchDB, 

[rozaydin@RO ~]$ curl -X PUT http://localhost:5984/_config/uuids/algorithm -d '"sequential"'

"sequential"

[rozaydin@RO ~]$

As you can see CouchDB responds with the old algorithm it was using to generate the _id fields prior the update. The same configuration should be able to be done using local.ini file however i failed to find the proper name for the setting if you know how please leave a comment :)

Configuring Jetty Server With Security Certificates

Skip to end of metadata

1 Install Jetty

• Download Jetty 9.3.2 version from http://download.eclipse.org/jetty/ and unzip to a directory (This directory will be called Jetty Home)
• go into Jetty Home directory and create a new directory inside this directory with name SECURE_BASE (This directory will be called Jetty Base)
• go into Jetty Base directory and create a new file with name start.ini
• open start.ini with a text editor and edit it to include below lines

# Initialize module server
--module=server
threads.min=10
threads.max=200
threads.timeout=60000
jetty.dump.start=false
jetty.sump.stop=false

--module=deploy
--module=jsp
--module=ext
--module=resources
--module=client
--module=annotations
--module=http
--module=ssl
--module=https

save and exit.

• Execute below command in Jetty Base directory

java -jar ../start.jar

then terminate the process via issuing kill -9 pid command

• create a new directory in Jetty Base directory with name etc.

In the end you should have following directory structure in your Jetty Base directory. (secure-base is Jetty Base in below example)

[rozaydin@RO secure-base]$ pwd
/home/rozaydin/WDH/jetty-9.3.2/secure-base
[rozaydin@RO secure-base]$ ls
etc lib resources start.ini webapps
[rozaydin@RO secure-base]$

2 Create SSL Certificate

Create an SSL certificate by issuing below command please ensure you note the password, this file will be used at https negotiation with the client.

$ keytool -keystore keystore -alias keystore -genkey -keyalg RSA -sigalg SHA256withRSA
 Enter keystore password:  password
 What is your first and last name?
   [Unknown]:  Test Test
 What is the name of your organizational unit?
   [Unknown]:  Software Development
 What is the name of your organization?
   [Unknown]:  Test Test
 What is the name of your City or Locality?
   [Unknown]: Istanbul
 What is the name of your State or Province?
   [Unknown]: Istanbul
 What is the two-letter country code for this unit?
   [Unknown]: TR
 Is CN=
Test Test, OU=Software Development, O=Test Test,
 L=Istanbul, ST=Istanbul, C=TR correct?
   [no]:  yes

 Enter key password for <keystore>
         (RETURN if same as keystore password):
 $

After the execution you should have a file with name keystore at the directory you have issued the command.

2 Configure HTTPS on Jetty

1. Copy the SSL certificate file (keystore file) you have created in previous step to Jetty Base/etc directory

2. Https configuration is determined by 4 configuration files located under Jetty Home/etc directory these files are

• jetty.xml
• jetty-https.xml
• jetty-ssl.xml
• jetty-ssl-context.xml

Open the jetty-ssl-context.xml file and modify below lines accordingly

jetty-ssl-context.xml

<?xml version="1.0"?>
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure_9_3.dtd">
<!-- ============================================================= -->
<!-- SSL ContextFactory configuration -->
<!-- ============================================================= -->
<Configure id="sslContextFactory" class="org.eclipse.jetty.util.ssl.SslContextFactory">
<Set name="KeyStorePath"><Property name="jetty.base" default="." />/<Property name="jetty.sslContext.keyStorePath" deprecated="jetty.keystore" default="etc/keystore"/></Set>
<Set name="KeyStorePassword"><Property name="jetty.sslContext.keyStorePassword" deprecated="jetty.keystore.password" default="test"/></Set>
<Set name="KeyStoreType"><Property name="jetty.sslContext.keyStoreType" default="JKS"/></Set>
<Set name="KeyStoreProvider"><Property name="jetty.sslContext.keyStoreProvider"/></Set>
<Set name="KeyManagerPassword"><Property name="jetty.sslContext.keyManagerPassword" deprecated="jetty.keymanager.password" default="test"/></Set>
<Set name="TrustStorePath"><Property name="jetty.base" default="." />/<Property name="jetty.sslContext.trustStorePath" deprecated="jetty.truststore" default="etc/keystore"/></Set>
<Set name="TrustStorePassword"><Property name="jetty.sslContext.trustStorePassword" deprecated="jetty.truststore.password" default="test"/></Set>
<Set name="TrustStoreType"><Property name="jetty.sslContext.trustStoreType" default="JKS"/></Set>
<Set name="TrustStoreProvider"><Property name="jetty.sslContext.trustStoreProvider"/></Set>
<Set name="EndpointIdentificationAlgorithm"></Set>
<Set name="NeedClientAuth"><Property name="jetty.sslContext.needClientAuth" deprecated="jetty.ssl.needClientAuth" default="false"/></Set>
<Set name="WantClientAuth"><Property name="jetty.sslContext.wantClientAuth" deprecated="jetty.ssl.wantClientAuth" default="false"/></Set>
<Set name="ExcludeCipherSuites">
<Array type="String">
<Item>SSL_RSA_WITH_DES_CBC_SHA</Item>
<Item>SSL_DHE_RSA_WITH_DES_CBC_SHA</Item>
<Item>SSL_DHE_DSS_WITH_DES_CBC_SHA</Item>
<Item>SSL_RSA_EXPORT_WITH_RC4_40_MD5</Item>
<Item>SSL_RSA_EXPORT_WITH_DES40_CBC_SHA</Item>
<Item>SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA</Item>
<Item>SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA</Item>
</Array>
</Set>
<Set name="useCipherSuitesOrder"><Property name="jetty.sslContext.useCipherSuitesOrder" default="true"/></Set>
</Configure>

Here we are setting the password by changing 3 properties listed below, password must be the same as the password that is set to the Certificate file.

<Set name="KeyStorePassword"><Property name="jetty.sslContext.keyStorePassword" deprecated="jetty.keystore.password" default="test"/></Set>

<Set name="KeyManagerPassword"><Property name="jetty.sslContext.keyManagerPassword" deprecated="jetty.keymanager.password" default="test"/></Set>
<Set name="TrustStorePassword"><Property name="jetty.sslContext.trustStorePassword" deprecated="jetty.truststore.password" default="test"/></Set>

4 Run Jetty Server 

After following previous configuration steps, start jetty server by going into Jetty Base directory and issuing command

java -jar ../start.jar

you can access the server using https protocol by using default url https://localhost:8443

Working offline with Maven

While working with projects managed by maven you could run into issues where you have to disconnect your development environment from the internet and continue to work on the code. The experience i had was i had to debug a system deployed to a customer network which had no internet access. I suddenly realized my development environment on my laptop was completely useless. Pretty bad when there are people standing behind you and waiting for you to resolve their problem.

The solution is downloading the maven dependencies to your local by executing below command from the same directory where your pom file is located.

[rozaydin@RO]$ mvn dependency:go-offline

Maven will download all dependencies your project needs and you could be able to continue working with no need to internet access.

Ucuz Elektrik

Türkiye'de elektrik tarifeleri 3 zamanlı olarak ücretlendirilmekteler. Bu zaman (tarife) dilimleri aşağıda listelenmiştir.

Gündüz (T1)      : 06:00 – 17:00

Puant (T2)          : 17:00 – 22:00

Gece (T3)           : 22:00 – 06:00

En ucuz elektrik 22.00 - 06.00 arasında satılırken en pahalı elektril 17.00 - 22.00 saatleri arasında satılmakta. Hali hazırda geçerli olan ücret tarifelerine göre "Mesken" tipi abonelerin tarifeleri aşağıda listelenmiştir. 

Mesken:

Gündüz: 19,7183

Puant:     35,8753 

Gece:      8,0527 

Görüldüğü gibi en ucuz zaman dilimi GECE tarifesi olmaktadır. Eğer enerji tüketimimizin tamamını gece tarifesi üzerinden yaparsak harcadığımız aynı enerji miktarı için 3 kat daha az ödüyoruz. Basit bir örnek verir ise ortalama enerji faturamız aylık 60 lira ise ödeyeceğimiz rakam 20 liraya düşüyor. 1 sene içerisinde yapacağımız tasarruf miktarı 40 x 12 = 480 lira. Az bir rakam değil. 

Peki enerji tüketimimizin tamamını GECE tarifesi üzerinden yapmak mümkün mü ? Eğer enerjiyi depolayabilir isek evet mümkün. Büyükçe şarj edilebilir bir pilimiz olduğunu düşünün, Tarifenin en ucuz olduğu zaman diliminde kendi kendisini otomatik şarj ediyor ve diğer zaman dilimlerinde ise bu pildeki enerjiyi evimizde kullanıyoruz harcadığımız elektrik miktarını kısmadan ciddi miktarda tasarruf sağladık.

İşte bu şekilde şarj edilebilir bir pil artık var. Elektrikli araçları ile ünlü Amerikan "Tesla" şirketi Power Wall adlı ürün ile karşımızda. Power Wall evinizin duvarına monte ettirebileceğiniz oldukça şık bir ürün. Ancak ürünün fiyatı biraz yüksek 3000$ ve 3500$ fiyat etiketine sahip ki Türkiye standartları için bu ciddi bir rakam. Ancak bu ürünlerin muadilleri daha uygun fiyat etiketi ile çok kısa sürede pazara sürülecektir. Bu durumda daha satın alınabilir bir etiket ile elektrik faturalarımızı ciddi miktarda düşürebilir olacağız.

Latitude Longitude Boundaries on World Map

You might have encountered situations where you wanted to get the latitude and longitude boundaries of an rectangular area on world map, I have put together a simple js application using leaflet js and leaflet.draw plugin to provide the functionality.

1. You can access the hosted application from here. 
2. You can access the sources from here. 

Enjoy and please comment if you encounter any issues.

Figure 1 - Boundary Application

How to kill multiple processes from terminal with single line

You might encounter situations where you need to kill group of processes, such as when google-chrome is running. Chrome spawns multiple processes and you might want to shut it down from terminal.

[rozaydin@RO ~]$ ps -e | grep chrome
 5017 ?        00:00:01 chrome
 5027 ?        00:00:00 chrome-sandbox
 5028 ?        00:00:00 chrome
 5033 ?        00:00:00 chrome-sandbox
 5036 ?        00:00:00 chrome
 5055 ?        00:00:00 chrome
 5083 ?        00:00:00 chrome
 5091 ?        00:00:00 chrome
 5107 ?        00:00:00 chrome
 5111 ?        00:00:00 chrome
 5115 ?        00:00:00 chrome
 5123 ?        00:00:00 chrome
 5131 ?        00:00:00 chrome
 5139 ?        00:00:00 chrome
 5142 ?        00:00:00 chrome
 5154 ?        00:00:00 chrome
 5160 ?        00:00:00 chrome
[rozaydin@RO ~]$
 

Killing these processes  one by one is a tedious task instead you can use below command the kill them with one single line. (Bird massacre with single stone)


ps -e | grep <processname> | awk '{system("kill -9 "$1)}'


[rozaydin@RO ~]$ ps -e | grep chrome | awk '{system("kill -9 "$1)}'
sh: line 0: kill: (5033) - No such process
sh: line 0: kill: (5036) - No such process
sh: line 0: kill: (5055) - No such process
sh: line 0: kill: (5083) - No such process
sh: line 0: kill: (5107) - No such process
sh: line 0: kill: (5111) - No such process
sh: line 0: kill: (5115) - No such process
sh: line 0: kill: (5123) - No such process
sh: line 0: kill: (5131) - No such process
sh: line 0: kill: (5139) - No such process
sh: line 0: kill: (5142) - No such process
sh: line 0: kill: (5154) - No such process
sh: line 0: kill: (5160) - No such process
[rozaydin@RO ~]$
[rozaydin@RO ~]$ ps -e | grep chrome
[rozaydin@RO ~]$

How to list rpm dependencies

You can easily list the dependencies the rpm file requires prior installation, this is particularly useful when you are shipping your rpms in a removable media this way you can ensure you have provided all the dependencies.

Open a terminal and type below command,

rpm -qpR name_of_rpm

You will see output like below;

/bin/sh

rpmlib(CompressedFileNames) <= 3.0.4-1

rpmlib(PayloadFilesHavePrefix) <= 4.0-1

...

Building Berkeley DB XML for CentOS systems

Go to this link and download Berkeley DB XML. Version used in this guide is "6.0.17". Once the download complete, unzip the file.

[rozaydin@RO Tutorials]$ ls

dbxml-6.0.17.tar.gz

[rozaydin@RO Tutorials]$ tar -xzf dbxml-6.0.17.tar.gz

[rozaydin@RO Tutorials]$ ls

dbxml-6.0.17  dbxml-6.0.17.tar.gz

[rozaydin@RO Tutorials]$ cd dbxml-6.0.17/

[rozaydin@RO dbxml-6.0.17]$ ls

buildall.sh  db-6.1.19  dbxml  README  xerces-c-src  xqilla

[rozaydin@RO dbxml-6.0.17]$

 DB XML uses  XQilla which is an XQuery and XPath 2 library implemented on top of the  Xerces-C. DB XML requires Berkeley DB as well. So before using it we need to install each of the following dependencies in the following order;

Build and install Berkeley-DB

Build and install Xerces

Build and install XQuilla

Build and install XML-DB

DB XML compilation failed to compile with java 8 switching to java version "1.7.0_72" compilation completed with no errors. Open a terminal switch to root user and set JAVA variables. (PLEASE note you need to use this same terminal for all commands listed below)

[rozaydin@RO dbxml-6.0.17]$ pwd

/home/rozaydin/Desktop/Tutorials/dbxml-6.0.17

[rozaydin@RO dbxml-6.0.17]$ su -

Password:

Last login: Wed Mar  4 12:19:38 EET 2015 on pts/0

[root@RO ~]# export JAVA_HOME=/usr/java/jdk1.7.0_72

[root@RO ~]# export PATH=$JAVA_HOME/bin:$PATH

[root@RO ~]# cd /home/rozaydin/Desktop/Tutorials/dbxml-6.0.17

[root@RO dbxml-6.0.17]#

Now proceed with building Berkeley DB with configure, make, make install use following commands;

[root@RO dbxml-6.0.17]# ls

buildall.sh  db-6.1.19  dbxml  README  xerces-c-src  xqilla

[root@RO dbxml-6.0.17]# cd db-6.1.19/

[root@RO db-6.1.19]# ls

build_android  build_vxworks  build_windows  docs      lang     README  test

build_unix     build_wince    dist           examples  LICENSE  src     util

[root@RO db-6.1.19]# cd build_unix/

[root@RO build_unix]# ../dist/configure --enable-cxx --enable-java

[root@RO build_unix]# make

[root@RO build_unix]# make install

When operation completes this will install Berkeley DB to /usr/local/BerkeleyDB.6.1 directory. Change directory back to where you unzipped XML DB.

[root@RO build_unix]# cd /usr/local/BerkeleyDB.6.1

[root@RO BerkeleyDB.6.1]# ls

bin  docs  include  lib

[root@RO BerkeleyDB.6.1]# cd /home/rozaydin/Desktop/Tutorials/dbxml-6.0.17/

[root@RO dbxml-6.0.17]# pwd

/home/rozaydin/Desktop/Tutorials/dbxml-6.0.17

After this step proceed with building XERCES library.

[root@RO dbxml-6.0.17]# cd xerces-c-src/

[root@RO xerces-c-src]# ls

config        CREDITS  LICENSE      NOTICE    samples  version.incl

config.h.in   doc      m4           projects  scripts  xerces-c.pc.in

configure     INSTALL  Makefile.am  README    src      xerces-c.spec

configure.ac  KEYS     Makefile.in  reconf    tests

[root@RO xerces-c-src]# ./configure

[root@RO xerces-c-src]# make

[root@RO xerces-c-src]# make install

When operation completes this will install XERCES library to /usr/local/bin directory. You should see similar output as below:

test -z "/usr/local/bin" || /bin/mkdir -p "/usr/local/bin"

  /bin/sh ../libtool   --mode=install /bin/install -c CreateDOMDocument DOMCount DOMPrint EnumVal MemParse PParse PSVIWriter Redirect SAX2Count SAX2Print SAXCount SAXPrint SCMPrint SEnumVal StdInParse XInclude '/usr/local/bin'

libtool: install: /bin/install -c .libs/CreateDOMDocument /usr/local/bin/CreateDOMDocument

libtool: install: /bin/install -c .libs/DOMCount /usr/local/bin/DOMCount

libtool: install: /bin/install -c .libs/DOMPrint /usr/local/bin/DOMPrint

libtool: install: /bin/install -c .libs/EnumVal /usr/local/bin/EnumVal

libtool: install: /bin/install -c .libs/MemParse /usr/local/bin/MemParse

libtool: install: /bin/install -c .libs/PParse /usr/local/bin/PParse

libtool: install: /bin/install -c .libs/PSVIWriter /usr/local/bin/PSVIWriter

libtool: install: /bin/install -c .libs/Redirect /usr/local/bin/Redirect

libtool: install: /bin/install -c .libs/SAX2Count /usr/local/bin/SAX2Count

libtool: install: /bin/install -c .libs/SAX2Print /usr/local/bin/SAX2Print

libtool: install: /bin/install -c .libs/SAXCount /usr/local/bin/SAXCount

libtool: install: /bin/install -c .libs/SAXPrint /usr/local/bin/SAXPrint

libtool: install: /bin/install -c .libs/SCMPrint /usr/local/bin/SCMPrint

libtool: install: /bin/install -c .libs/SEnumVal /usr/local/bin/SEnumVal

libtool: install: /bin/install -c .libs/StdInParse /usr/local/bin/StdInParse

libtool: install: /bin/install -c .libs/XInclude /usr/local/bin/XInclude

After this step proceed building XQuilla library (PLEASE note that you need to provide the xerces-c-src directory using ABSOLUTE path not doing so will fail the compilation)

[root@RO xqilla]# ./configure --with-xerces=/home/rozaydin/Desktop/Tutorials/dbxml-6.0.17/xerces-c-src

[root@RO xqilla]# make

[root@RO xqilla]# make install

When operation completes this will install XQuilla library to /usr/local/lib directory.

The last step involves building XML DB in dbxml directory type below commands:

[root@RO dbxml]# pwd

/home/rozaydin/Desktop/Tutorials/dbxml-6.0.17/dbxml

[root@RO dbxml]# cd build_unix/

[root@RO build_unix]# ../configure --enable-java --with-berkeleydb=/usr/local/BerkeleyDB.6.1 --with-xqilla=/usr/local/lib

[root@RO build_unix]# make

[root@RO build_unix]# make install

When operation completes this will install XML DB to /usr/local/BerkeleyDBXML.6.0/ directory. Verify the installation by typing below commands

[root@RO build_unix]# cd /usr/local/BerkeleyDBXML.6.0/

[root@RO BerkeleyDBXML.6.0]# ls

bin  include  lib

[root@RO BerkeleyDBXML.6.0]# cd bin

[root@RO bin]# ls

dbxml  dbxml_dump  dbxml_load  dbxml_load_container

[root@RO bin]# dbxml

bash: dbxml: command not found...

[root@RO bin]# ./dbxml

dbxml>

if you see the prompt you are good :)

sample pom.xml file for javaee rest application

here is the sample pom file i most of the time use to form the basis of my java web application projects. I use slf4j with logback for logging, mockito, junit and jersey test framework for testing and google gson for json conversion.

<?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>org.demo</groupId> <artifactId>demo</artifactId> <version>1.0.0-SNAPSHOT</version> <packaging>war</packaging> <name>demo application</name> <properties> <endorsed.dir>${project.build.directory}/endorsed</endorsed.dir> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> </properties> <dependencies> <dependency> <groupId>javax</groupId> <artifactId>javaee-web-api</artifactId> <version>7.0</version> <scope>provided</scope> </dependency> <dependency> <groupId>javax.ws.rs</groupId> <artifactId>javax.ws.rs-api</artifactId> <version>2.0.1</version> <scope>provided</scope> </dependency> <dependency> <groupId>com.google.code.gson</groupId> <artifactId>gson</artifactId> <version>2.3.1</version> </dependency> <!-- Logging --> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-api</artifactId> <version>1.7.10</version> </dependency> <dependency> <groupId>ch.qos.logback</groupId> <artifactId>logback-classic</artifactId> <version>1.1.2</version> </dependency> <dependency> <groupId>ch.qos.logback</groupId> <artifactId>logback-core</artifactId> <version>1.1.2</version> </dependency> <!-- Test --> <!-- https://jersey.java.net/documentation/latest/user-guide.html#d0e15523 --> <dependency> <groupId>org.glassfish.jersey.test-framework.providers</groupId> <artifactId>jersey-test-framework-provider-grizzly2</artifactId> <version>2.15</version> <scope>test</scope> </dependency> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>4.12</version> <scope>test</scope> </dependency> <dependency> <groupId>org.mockito</groupId> <artifactId>mockito-all</artifactId> <version>1.10.19</version> <scope>test</scope> </dependency> </dependencies> <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <version>3.1</version> <configuration> <source>1.8</source> <target>1.8</target> <compilerArguments> <endorseddirs>${endorsed.dir}</endorseddirs> </compilerArguments> </configuration> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-war-plugin</artifactId> <version>2.3</version> <configuration> <failOnMissingWebXml>false</failOnMissingWebXml> </configuration> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> <version>2.6</version> <executions> <execution> <phase>validate</phase> <goals> <goal>copy</goal> </goals> <configuration> <outputDirectory>${endorsed.dir}</outputDirectory> <silent>true</silent> <artifactItems> <artifactItem> <groupId>javax</groupId> <artifactId>javaee-endorsed-api</artifactId> <version>7.0</version> <type>jar</type> </artifactItem> </artifactItems> </configuration> </execution> </executions> </plugin> </plugins> </build> </project>