Hitachi Solutions, Ltd. All rights reserved. JBoss 3 JBossJava Web Application Server JBoss Application Server. Article on 12 globally recognized linux certifications certified by companies for linux system administrations, engineers and experts. Jenkins Quick Guide. Jenkins Quick Guide. Jenkins Overview. Why Jenkins Jenkins is a software that allows continuous integration. Jenkins will be installed on a server where the central build will take place. The following flowchart demonstrates a very simple workflow of how Jenkins works. Along with Jenkins, sometimes, one might also see the association of Hudson. Hudson is a very popular open source Java based continuous integration tool developed by Sun Microsystems which was later acquired by Oracle. After the acquisition of Sun by Oracle, a fork was created from the Hudson source code, which brought about the introduction of Jenkins. What is Continuous Integration Continuous Integration is a development practice that requires developers to integrate code into a shared repository at regular intervals. This concept was meant to remove the problem of finding later occurrence of issues in the build lifecycle. Continuous integration requires the developers to have frequent builds. The common practice is that whenever a code commit occurs, a build should be triggered. System Requirements. JDKJDK 1. 5 or above. Memory. 2 GB RAM recommendedDisk Space. No minimum requirement. Installation_Guide/beta500/html-single/images/jmx-console.png' alt='Jboss Application Server Download For Centos Install' title='Jboss Application Server Download For Centos Install' />Note that since all builds will be stored on the Jenkins machines, it has to be ensured that sufficient disk space is available for build storage. Operating System Version. Jenkins can be installed on Windows, UbuntuDebian, Red HatFedoraCent. OS, Mac OS X, open. SUSE, FRee. BSD, Open. BSD, Gentoo. Java Container. The WAR file can be run in any container that supports Servlet 2. JSP 2. 0 or later. An example is Tomcat 5. Jenkins Installation. Download Jenkins. The official website for Jenkins is Jenkins. If you click the given link, you can get the home page of the Jenkins official website as shown below. By default, the latest release and the Long Term support release will be available for download. The past releases are also available for download. Click the Long Term Support Release tab in the download section. Click the link Older but stable version to download the Jenkins war file. Starting Jenkins. A monolithic application typically has a single relational database. A key benefit of using a relational database is that your application can use ACID transactions. Open the command prompt. From the command prompt, browse to the directory where the jenkins. Run the following command. D Java jar Jenkins. After the command is run, various tasks will run, one of which is the extraction of the war file which is done by an embedded webserver called winstone. D Java jar Jenkins. Running from D jenkins. Webroot user. home. How To Install A Submersible Well Pump on this page. Sep 2. 9, 2. 01. 5 4 1. PM winstone. Logger log. Internal. INFO Beginning extraction from war file. Once the processing is complete without major errors, the following line will come in the output of the command prompt. INFO Jenkins is fully up and running. Accessing Jenkins. Once Jenkins is up and running, one can access Jenkins from the link http localhost 8. This link will bring up the Jenkins dashboard. Jenkins Tomcat Setup. The following prerequisites must be met for Jenkins Tomcat setup. Step 1 Verifying Java Installation. To verify Java installation, open the console and execute the following java command. OSTask. Command. Windows. Open command console java version. Linux. Open command terminaljava version. If Java has been installed properly on your system, then you should get one of the following outputs, depending on the platform you are working on. OSOutput. Windows. Java version 1. 7. Java TM SE Run Time Environment build 1. Java Hotspot TM 6. Server VM build 2. Linuxjava version 1. Open JDK Runtime Environment rhel 2. Open JDK 6. 4 Bit Server VM build 2. We assume the readers of this tutorial have Java 1. In case you do not have Java JDK, you can download it from the link Oracle. Step 2 Verifying Java Installation. Set the JAVAHOME environment variable to point to the base directory location where Java is installed on your machine. For example,OSOutput. Windows. Set Environmental variable JAVAHOME to C Program. Filesjavajdk. 1. Linuxexport JAVAHOMEusrlocaljava current. Append the full path of the Java compiler location to the System Path. OSOutput. Windows. Append the String C Program FilesJavajdk. PATH. Linuxexport PATHPATH JAVAHOMEbinVerify the command java version from command prompt as explained above. Step 3 Download Tomcat. The official website for tomcat is Tomcat. If you click the given link, you can get the home page of the tomcat official website as shown below. Browse to the link https tomcat. Go to the Binary Distributions section. Download the 3. 2 bit Windows zip file. Then unzip the contents of the downloaded zip file. Step 4 Jenkins and Tomcat Setup. Copy the Jenkis. war file which was downloaded from the previous section and copy it to the webapps folder in the tomcat folder. Now open the command prompt. From the command prompt, browse to the directory where the tomcat. Browse to the bin directory in this folder and run the start. E Appstomcat. 7bin startup. Once the processing is complete without major errors, the following line will come in the output of the command prompt. INFO Server startup in 1. Open the browser and go to the link http localhost 8. Jenkins will be up and running on tomcat. Jenkins Git Setup. For this exercise, you have to ensure that Internet connectivity is present from the machine on which Jenkins is installed. In your Jenkins Dashboard Home screen, click the Manage Jenkins option on the left hand side. In the next screen, click the Manage Plugins option. In the next screen, click the Available tab. This tab will give a list of plugins which are available for downloading. In the Filter tab type Git pluginThe list will then be filtered. Check the Git Plugin option and click on the button Install without restartThe installation will then begin and the screen will be refreshed to show the status of the download. Once all installations are complete, restart Jenkins by issue the following command in the browser. After Jenkins is restarted, Git will be available as an option whilst configuring jobs. To verify, click on New Item in the menu options for Jenkins. Then enter a name for a job, in the following case, the name entered is Demo. Select Freestyle project as the item type. Click the Ok button. In the next screen, if you browse to the Source code Management section, you will now see Git as an option. Jenkins Maven Setup. Step 1 Downloading and Setting Up Maven. The official website for maven is Apache Maven. If you click the given link, you can get the home page of the maven official website as shown below. While browsing to the site, go to the Files section and download the link to the Binary. Once the file is downloaded, extract the files to the relevant application folder. For this purpose, the maven files will be placed in E Appsapache maven 3. Step 2 Setting up Jenkins and Maven. In the Jenkins dashboard Home screen, click Manage Jenkins from the left hand side menu. Then, click on Configure System from the right hand side. In the Configure system screen, scroll down till you see the Maven section and then click on the Add Maven button. Uncheck the Install automatically option. Add any name for the setting and the location of the MAVENHOME. Then, click on the Save button at the end of the screen. You can now create a job with the Maven project option. In the Jenkins dashboard, click the New Item option. Jenkins Configuration. Dear Postgre. SQL Where are my logs When debugging a problem, its always frustrating to get sidetracked hunting down the relevant logs. Postgre. SQL users can select any of several different ways to handle database logs, or even choose a combination. But especially for new users, or those getting used to an unfamiliar system, just finding the logs can be difficult. To ease that pain, heres a key to help dig up the correct logs. First, connect to Postgre. SQL with psql, pgadmin, or some other client that lets you run SQL queries, and run this foo show logdestination. The logdestination setting tells Postgre. SQL where log entries should go. In most cases it will be one of four values, though it can also be a comma separated list of any of those four values. Well discuss each in turn. SYSLOGSyslog is a complex beast, and if your logs are going here, youll want more than this blog post to help you. Different systems have different syslog daemons, those daemons have different capabilities and require different configurations, and we simply cant cover them all here. Your syslog may be configured to send Postgre. SQL logs anywhere on the system, or even to an external server. For your purposes, though, youll need to know what ident and facility youre using. These values tag each syslog message coming from Postgre. SQL, and allow the syslog daemon to sort out where the message should go. You can find them like this foo show syslogfacility. Syslog is often useful, in that it allows administrators to collect logs from many applications into one place, to relieve the database server of logging IO overhead which may or may not actually help anything, or any number of other interesting rearrangements of log data. EVENTLOGFor Postgre. SQL systems running on Windows, you can send log entries to the Windows event log. Youll want to tell Windows to expect the log values, and what event source theyll come from. You can find instructions for this operation in the Postgre. SQL documentation discussing server setup. STDERRThis is probably the most common log destination its the default, after all and can get fairly complicated in itself. Selecting stderr instructs Postgre. SQL to send log data to the stderr short for standard error output pipe most operating systems give every new process by default. The difficulty is that Postgre. SQL or the applications that launch it can then redirect this pipe to all kinds of different places. If you start Postgre. SQL manually with no particular redirection in place, log entries will be written to your terminal josheddie pgctl D PGDATA start. LOG database system was shut down at 2. MST. LOG database system is ready to accept connections. LOG autovacuum launcher started. LOG statement select syntax error. ERROR column syntax does not exist at character 8. STATEMENT select syntax error. In these logs youll see the logs from me starting the database, connecting to it from some other terminal, and issuing the obviously erroneous command select syntax error. But there are several ways to redirect this elsewhere. The easiest is with pgctls l option, which essentially redirects stderr to a file, in which case the startup looks like this josheddie pgctl l logfile D PGDATA start. Finally, you can also tell Postgre. SQL to redirect its stderr output internally, with the loggingcollector option which older versions of Postgre. SQL named redirectstderr. This can be on or off, and when on, collects stderr output into a configured log directory. So if you end see a logdestination set to stderr, a good next step is to check loggingcollector foo show loggingcollector. In this system, loggingcollector is turned on, which means we have to find out where its collecting logs. First, check logdirectory. In my case, below, its an absolute path, but by default its the relative path pglog. This is relative to the Postgre. SQL data directory. Log files are named according to a pattern in logfilename. Each of these settings is shown below foo show logdirectory. Y m dHMS. Documentation for each of these options, along with settings governing log rotation, is available here. If loggingcollector is turned off, you can still find the logs using the proc filesystem, on operating systems equipped with one. First youll need to find the process ID of a Postgre. SQL process, which is simple enough foo select pgbackendpid. Then, check procYOURPIDHEREfd2, which is a symlink to the log destination josheddie ll proc3. Nov 5 1. 2 5. 2 proc3. CSVLOGThe csvlog mode creates logs in CSV format, designed to be easily machine readable. In fact, this section of the Postgre. SQL documentation even provides a handy table definition if you want to slurp the logs into your database. CSV logs are produced in a fixed format the administrator cannot change, but it includes fields for everything available in the other log formats. For these to work, you need to have loggingcollector turned on without loggingcollector, the logs simply wont show up anywhere. But when configured correctly, Postgre. SQL will create CSV format logs in the logdirectory, with file names mostly following the logfilename pattern. Heres my example database, with logdestination set to stderr, csvlog and loggingcollector turned on, just after I start the database and issue one query josheddie develpglog ll. Nov 1. 2 1. 6 3. Nov 1. The CSV log output looks like this josheddie develpglog cat postgresql 2. MST,2. 99. 3,5. MST,0,LOG,0. MST,. 2. MST,2. 99. MST,0,LOG,0. 00. MST,2. MST,0,LOG,0. 00. MST,josh,josh,3. MST,21. 0,0,LOG,0.