jprofiler

jprofiler.

install jprofiler.

jprofiler is java profiling tool, it also includes feature to profile cpu,memory,threads.

getting started with jprofiler.

1. download latest version
ref: jprofiler

2) Insatall the software.

3) intigrate with ide(eclipse).
steps to intigrate.

a) start jprofiler.
b) go to session ->IDE intigration ->select IDE-> eclipse (version). click on intigrate.

c) start eclipse.
d) go to windows->prespective->custom prespective->Action set visiblity->check profiler.
intigration is done


2) how to run jprofiler on project.

a) select the project.
b) right click and run ->profile ->profile configuration-> choose the project
c)choose ->apache tomcat-> source (remove the default if there are any).
d)add the project source directory.click on profile.
e) jprofiler will start window with statistics.

install grunt server and start the grunt server

install grunt server and start the grunt server

1) install grunt server.
cmd : npm install -g grunt-cli

2) start grunt server.
note : after creation of yeoman project go to directory
cmd : grunt server

install/install mysql in rhel linux

install/install mysql in rhel linux
ref :
https://dev.mysql.com/doc/mysql-repo-excerpt/5.6/en/linux-installation-yum-repo.html
1) get the URL for the mysql rpm
sudo wget http://dev.mysql.com/get/mysql57-community-release-el7-8.noarch.rpm

2) sudo yum install mysql57-community-release-el7-8.noarch.rpm


3) now install the server.
cmd : sudo yum install mysql-community-server

4) sudo service mysqld start

5) remove the mysql server.
cmd : yum remove mysql mysql-server

install tomcat on linux

install tomcat

go to /temp dir
sudo wget http://redrockdigimark.com/apachemirror/tomcat/tomcat-7/v7.0.69/bin/apache-tomcat-7.0.69.tar.gz

2) unzip file
tar xzf apache-tomcat-7.0.69.tar.gz

3) move the folder to tomcat7

mv apache-tomcat-7.0.69 /usr/local/tomcat7

4) start the tomcat server.
go to the ./bin/startup.sh

output :
cmd : ./bin/startup.sh
Using CATALINA_BASE:   /usr/local/tomcat7/apache-tomcat-7.0.69
Using CATALINA_HOME:   /usr/local/tomcat7/apache-tomcat-7.0.69
Using CATALINA_TMPDIR: /usr/local/tomcat7/apache-tomcat-7.0.69/temp
Using JRE_HOME:        /usr/java/jdk1.8.0_45/jre
Using CLASSPATH:       /usr/local/tomcat7/apache-tomcat-7.0.69/bin/bootstrap.jar:/usr/local/tomcat7/apache-tomcat-7.0.69/bin/tomcat-juli.jar
Tomcat started.

5) set up user account in conf/tomcat-users.xml.

<!-- user manager can access only manager section -->
<role rolename="manager-gui" />
<user username="manager" password="abc" roles="manager-gui" />

<!-- user admin can access manager and admin section both -->
<role rolename="admin-gui" />
<user username="admin" password="def" roles="manager-gui,admin-gui" />


6) change the port to 8082

go to conf/server.xml  and change the default port from 8080 t0 8082

 <Connector port="8082" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" />

7) connect to tomcat :
http://xx.xxx.xxx.xxx:8082/manager/html

Install maven on redhat linux

Install maven on redhat  linux

wget : to retrieve content from server

REF : maven mirror

1) wget http://mirror.olnevhost.net/pub/apache/maven/binaries/apache-maven-3.2.1-bin.tar.gz

1.1)
create the apache-maven if not exist.
command :
sudo mkdir -m a=rwx /usr/local/apache-maven

1.2) Go to apache-maven directory and execute the command.
maven

1.3) extract the file
command : tar xvf apache-maven-3.2.1-bin.tar.gz

1.4) export the path
1.4.1) export M2_HOME=/usr/local/apache-maven/apache-maven-3.2.1
1.4.2)export M2=$M2_HOME/bin
1.4.3) export PATH=$M2:$PATH

1.5) verify maven version
mvn -version

output :

Maven home: /usr/local/apache-maven/apache-maven-3.2.1
Java version: 1.8.0_45, vendor
Java home: /usr/java/jdk1.8.0_45/jre
Default locale:
OS name: "linux",

REF : 1) stackoverflow
           2) linux

Maven Build Lifecycle 

• validate - validate the project is correct and all necessary information is available
• compile - compile the source code of the project
• test - test the compiled source code using a suitable unit testing framework. These tests should not require the code be packaged or deployed
• package - take the compiled code and package it in its distributable format, such as a JAR.
• integration-test - process and deploy the package if necessary into an environment where integration tests can be run
• verify - run any checks to verify the package is valid and meets quality criteria
• install - install the package into the local repository, for use as a dependency in other projects locally
• deploy - done in an integration or release environment, copies the final package to the remote repository for sharing with other developers and projects.

Ref : maven build URL