Saturday, June 17, 2017

Load balancing using Nginx in Windows

Nginx is pronounced as "Engine x".
Nginx is a open-source HTTP server, reverse proxy and a load balancer.
Download Location: Nginx 1.10.2.zip

Extract the nginx zip file.
Before starting nginx there are sequence of steps to be done.

1. We will consider to work on this with two tomcat's set up. I have launched two tomcat's running on different ports 8081 and 8082. (Make sure to change listen port as well)
2. Let's have a sample war file that is deployed in both tomcats and start them.
Location to download sample war file and nginx configuration: https://github.com/raviteja548/blog-files/tree/master/nginx
3. Nginx config(nginx.conf) file has directives and those which are placed in configuration file are to be in main context.
4. let's create an upstream in http directive as below.

upstream tomcat_servers{ 
least_conn; server 127.0.0.1:8084; 
server 127.0.0.1:8085; 
}

You can name upstream as you wish. least_conn is the name of algorithm on which load balancing has to happen. Add servers on which your application is running on.
5. create a server directive as below
server { 
listen 80; 
server_name localhost;
location / { 
proxy_pass http://tomcat_servers; 
proxy_next_upstream     error timeout invalid_header http_500;
proxy_connect_timeout   2;
}
}

By default listen port is 80.
6. At the end nginx config should look like this.
#user  nobody;
worker_processes  1;

#error_log  logs/error.log;
#error_log  logs/error.log  notice;
#error_log  logs/error.log  info;

#pid        logs/nginx.pid;


events {
    worker_connections  1024;
}


http { 
upstream tomcat_servers{ 
least_conn; server 127.0.0.1:8084; 
server 127.0.0.1:8085; 
} 


    # another virtual host using mix of IP-, name-, and port-based configuration
    #
    #server {
    #    listen       8000;
    #    listen       somename:8080;
    #    server_name  somename  alias  another.alias;

    #    location / {
    #        root   html;
    #        index  index.html index.htm;
    #    }
    #}


    server { 
listen 80; 
server_name localhost;
location / { 
proxy_pass http://tomcat_servers; 
proxy_next_upstream     error timeout invalid_header http_500;
proxy_connect_timeout   2;
}
}

}

7. Navigate to nginx home directory and start it using command "start nginx"

8. Based on nginx configuration we access webapplication using url http://localhost/hello-world/ but nginx internally takes care of routing request to both tomcats i.e sending alternate request to each tomcat since the algorithm used is least connect.
9. Routing to each tomcat can be verfied adding logs.
Below screenshot to show load balancing between configured servers for different requests.

Wednesday, March 29, 2017

Sunday, October 23, 2016

Trigger Jenkins Build Using SVN PostCommit hook



This post explains about triggering jenkins build as soon as you commit files/changes to svn repository.

There are two ways to achieve this.

1. Poll repository to find if any changes done in your project location. But with this approach there is a chance of build skips since polling is done in a particular interval. This is ideally not preferable as it increases load on server, building jobs even when there are no changes detected.

2. Configure SVN repository to trigger post-commit hook which can trigger jenkins build.

This post covers 2nd way in detail.

Location of hooks folder: SVN hooks can be found right in the place where repository is created which contains directory name hooks. You can find all the type of hooks which are supported by svn.

By default all the extensions of hooks are .tmpl, in order to make them executable the extension should be changed to .bat/.exe in a windows environment.

3. Post Commit hook by default receives two arguments. They are received in an order REPOS and REV

REPOS: is the location when svn repository is created. EX: "file:///E:/WORK/svn" (on windows)

REV : is the revision value generated for every commit. EX: 18928

4. It is necessary to get an idea about utility svnlook which is a command-line utility for examining different aspects of a Subversion repository. It does not make any changes to the repository—it's just used for “peeking.” svnlook is typically used by the repository hooks explore much about "svnlook --help"

3. Triggering jenkins build on post commit will involve a series of steps i.e

a) Initially a property has to be set on the project location as a keyvalue pair. Make sure you commit property name and value changes to svn ex: name:ci:buildurl value:jenkins-job-build-url



b) Finding out which directories were updated on commit.

"svnlook" with option "dirs-changed" has the ability to find out directory changes on postcommit using revision number EX: >svnlook dirs-changed E:\WORK\svn -r 392 ( 392 is revision number, command execution would result below)
>testproj/trunk/src/main/java/testproj/

c) Extraction svn-properties on the directory that resulted in change.

"svnlook" with option "propget" and valid arguments can result in property name that was set to project.

EX:> "svnlook propget E:\WORK\svn ci:buildurl testproj/trunk/src/main/java/testproj/"

> http://localhost:8080/job/testproject/build?delay=0sec

("testproj/trunk/src/main/java/testproj/" is the folder that was updated during a commit in step b and ci:buildurl is the property name, E:\WORK\svn is the repository location)

4. Using the value obtained from step C execute curl command to run jenkins build

EX: curl -X POST http://localhost:8080/job/testproject/build?delay=0sec

5. After all the subsequent steps you can find jenkins building the job.

6. This is a sample post-commit hook attached below.

   
setlocal  
set REPOS=%1  
set REV=%2

FOR /F %%i in ('svnlook dirs-changed E:\WORK\svn -r %REV%') do SET dirloc=%%i 
 
FOR /F %%i in ('svnlook propget E:\WORK\svn ci:buildurl %dirloc%') do SET PROP=%%i

if defined %PROP%
curl -X POST %PROP%

Tuesday, June 14, 2016

Quick start to heroku applications


Nexus Repository Manager

Nexus is a repository manager & stating repository in which files can be uploaded using maven. Alternatively files can be also uploaded via curl commands.
This tutorial outlines to install Nexus also covers artifacts upload using maven & files upload using curl commands.
1. Download latest nexus war file from http://www.sonatype.org/downloads/nexus- latest.war
2. Deploy the war file in any webserver.
3. Launch nexus home page http://localhost:8081/nexus-2.13.0-01/#welcome
4. Default username and password to login are admin & admin123
5. You can create your own Repository from views/Repositories section
6. Add a hosted repository using the sample configuration shown in image.

7. Have curl in classpath to upload files into repository. Example: curl --upload-file upload.zip -u admin:admin123 -v http://localhost:8081/nexus-2.13.0-01/content/repositories/targus/upload.zip Repository url can be found navigating to corresponding repository and in summary section

8. Files uploaded can be found in the browse storage section of the respective repository.

Sunday, October 11, 2015

FindBugs Jenkins Integration

Jenkins installation & integration with firebugs documentation available in the link. Download here Maven plugin for findbugs report generation.
<reporting>
    <plugins>
        <plugin>
            <groupId>org.codehaus.mojo</groupId>
            <artifactId>findbugs-maven-plugin</artifactId>
            <version>2.5.2</version>
            <configuration>
                <!--
                    Enables analysis which takes more memory but finds more bugs.
                    If you run out of memory, changes the value of the effort element
                    to 'low'.
                -->
                <effort>Max</effort>
                <!-- Reports all bugs (other values are medium and max) -->
                <threshold>Low</threshold>
                <!-- Produces XML report -->
                <xmlOutput>true</xmlOutput>
            </configuration>
        </plugin>
    </plugins>
</reporting>
Command to generate find bugs report : mvn clean compile site

Wednesday, July 15, 2015

PEM File Creation

PEM:Privacy Enhanced Mail is a Base64 encoded DER certificate
PEM files are used to represent Certificate/PrivateKey in an understandable format. They have a distinct header and footer for every key, where the body is composed of Base64 encoded Key.
They are represented as shown below for (Certificate/PrivateKey/Certificate Signing Request/PublicKey)
-----BEGIN RSA PRIVATE KEY-----
MIICWwIBAAKBgQCpF26VoB9/Au3Ct/dBFW5kfXFU8IkK+G3CG4slkVX2mwBtvLyb
mFAuQ3RXvmX6tZxeUgwN7m+pZH+Y94lgAIpvcnzBEh8FFxwu0jy17uw+4ler5Soy
YRGV8TYOeQHqoHS44clTG28T2RYy9lkRqTIkkCyo5ViyD7GVQVUgjR31LQIDAQAB
AoGAFmkioPYd9ol+1aXoQVoDzZHKqYVPxIJ0mZto78u5ZvvYLLMtFDo1tkv+aXq0
rWvQk7ewHVCSwBKvzqhQLscjkbZqBdhnkBsyDQTcTQ+0sf8RGDHhBz2A1gGrBFhB
rWc9wGuk7CFHUCrUL0ZXBquMM1KCd/+Fdg2+OQzcoJd9/AECQQDkLdyiaG4Y/lFM
i4wtIf9rNVP4a1jHcYk1Ll7wvymY+v0e9zNVqKbkHaZ4/tyvD3MzVXZCByJZoFu4
sCWRK9WBAkEAvbVF3E7jxrQNTNRqLyQW6v0cmNSCSUfDkYANRuO+d6xvvT2HgrYs
SiL8h4qDLkbM/LTvf9lxb8vSlUSt/3ctrQJAP70767YmQx8PkMVOg/ECS21bJoK+
CwCBJnTsmm2b7hr2iCbflScGb6SEsznmZZR4Rrex0CH0C3tLA91YsSPAgQJAa1Wc
6UFZbpuAyu+EBJgOv3XmMDJMZNnNtQ0Wdf11TpCpyBCAE1yvQmL5LlcYUZ6NbI2S
1Gta2z4fL4VkTR5JIQJAQE6QBPguRRYLFyDa6db+QyeJ1iBHy3I8XvK9bem+Dsby
Km2l2KzLk3IpIEniqjLcoCQzFd5jp8m5VfjMx1doQQ==
-----END RSA PRIVATE KEY-----

-----BEGIN PUBLIC KEY-----
MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCpF26VoB9/Au3Ct/dBFW5kfXFU
8IkK+G3CG4slkVX2mwBtvLybmFAuQ3RXvmX6tZxeUgwN7m+pZH+Y94lgAIpvcnzB
Eh8FFxwu0jy17uw+4ler5SoyYRGV8TYOeQHqoHS44clTG28T2RYy9lkRqTIkkCyo
5ViyD7GVQVUgjR31LQIDAQAB
-----END PUBLIC KEY-----


-----BEGIN CERTIFICATE-----
MIIBmjCCAQMCBgFOkeZMojANBgkqhkiG9w0BAQsFADATMREwDwYDVQQDEwhSYXZp
VGVqYTAeFw0xNTA3MTQxMzI3NDVaFw0xNTA2MjkyMTQ1NTZaMBMxETAPBgNVBAMT
CFJhdmlUZWphMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCpF26VoB9/Au3C
t/dBFW5kfXFU8IkK+G3CG4slkVX2mwBtvLybmFAuQ3RXvmX6tZxeUgwN7m+pZH+Y
94lgAIpvcnzBEh8FFxwu0jy17uw+4ler5SoyYRGV8TYOeQHqoHS44clTG28T2RYy
9lkRqTIkkCyo5ViyD7GVQVUgjR31LQIDAQABMA0GCSqGSIb3DQEBCwUAA4GBAIh6
cNhWToRwhaJBykHXPqiaqPDA8n0xtq65dBiUQWOKeoXw0I7+LKUUzfHfb4wGZoLK
W2rBnNCY1BtpasqtAkdZ/Q+keJQd9xBcPqnKGUEqxxX7omB7cKYuhw9C+rGn/K1J
Ci1xlYBWuRsMd3A064fSHV0Adu+ru9YaWyS5+aLU
-----END CERTIFICATE-----


Java Program to generate PEM files.
package bc;

import java.io.File;
import java.io.FileWriter;
import java.io.PrintWriter;
import java.math.BigInteger;
import java.security.KeyPair;
import java.security.KeyPairGenerator;
import java.security.SecureRandom;
import java.security.Security;
import java.security.cert.X509Certificate;
import java.util.Date;

import javax.security.auth.x500.X500Principal;

import org.bouncycastle.jce.provider.BouncyCastleProvider;
import org.bouncycastle.openssl.PEMWriter;
import org.bouncycastle.x509.X509V1CertificateGenerator;

public class PEMWrite {
    public static void main(String[] args) throws Exception {
        generateSelfSignedX509Certificate();
    }

    static {
        // adds the Bouncy castle provider to java security
        Security.addProvider(new BouncyCastleProvider());
    }

    /**
     * Generate a self signed X509 certificate with Bouncy Castle.
     */
    static void generateSelfSignedX509Certificate() throws Exception {

        // yesterday
        Date validityBeginDate = new Date(System.currentTimeMillis() - 24 * 60 * 60 * 1000);
        // in 2 years
        Date validityEndDate = new Date(System.currentTimeMillis() + 2 * 365 * 24 * 60 * 60 * 1000);

        // GENERATE THE PUBLIC/PRIVATE RSA KEY PAIR
        KeyPairGenerator keyPairGenerator = KeyPairGenerator.getInstance("RSA", "BC");
        keyPairGenerator.initialize(1024, new SecureRandom());

        KeyPair keyPair = keyPairGenerator.generateKeyPair();

        // GENERATE THE X509 CERTIFICATE
        X509V1CertificateGenerator certGen = new X509V1CertificateGenerator();
        X500Principal dnName = new X500Principal("CN=RaviTeja");
        certGen.setSerialNumber(BigInteger.valueOf(System.currentTimeMillis()));
        certGen.setSubjectDN(dnName);
        certGen.setIssuerDN(dnName); // use the same
        certGen.setNotBefore(validityBeginDate);
        certGen.setNotAfter(validityEndDate);
        certGen.setPublicKey(keyPair.getPublic());
        certGen.setSignatureAlgorithm("SHA256WithRSAEncryption");
        X509Certificate cert = certGen.generate(keyPair.getPrivate(), "BC");
        System.out.println(cert);

        // PEM format representing Certificate
        PEMWriter pemWriter = new PEMWriter(new PrintWriter(System.out));
        pemWriter.writeObject(cert);
        pemWriter.flush();

        //Loads Private Key as PEM format into private_key.pem file
        File file = new File("private_key.pem");
        PEMWriter pw1 = new PEMWriter(new FileWriter(file));
        pw1.writeObject(keyPair.getPrivate());
        pw1.flush();
        pw1.close();

        //PEM format representing PrivateKey
        pemWriter.writeObject(keyPair.getPrivate());
        pemWriter.flush();

        //PEM format representing PublicKey
        pemWriter.writeObject(keyPair.getPublic());
        pemWriter.flush();
        pemWriter.close();

    }
}