In the simplest terms, Blockchain will be delineated as an information structure that holds transactional records and whereas making certain security, transparency, and decentralization. You’ll additionally think about it as a chain of records keep within the types of blocks that are controlled by no single authority.

What is BlockChain?

Blockchain can be defined as a chain of blocks that contains information. The technique is intended to timestamp digital documents so that it’s not possible to backdate them or temper them. The purpose of blockchain is to solve the double records problem without the need for a central server.

Why blockchain is important?

Business runs on data. The quicker it’s received and also the more accurate it’s, the better. Blockchain is ideal for delivering that data as a result of it provides immediate, shared and fully transparent data keep on an immutable ledger which will be accessed only by permission network members. A blockchain network will track orders, payments, accounts, production, and far more and since members share one view of the reality, you’ll be able to see all details of a transaction end-to-end, providing you with greater confidence, also as new efficiencies and opportunities.

How does it work?

Blockchain could be a system of recording data in an exceedingly means that produces it tough or not possible to vary, hack, or cheat the system. Each block within the chain contains a variety of transactions, and each time a brand new dealing happens on the blockchain, a record of that dealing is supplementary to each participant’s ledger.

Blockchain used for

Blockchain could be a system of recording data in a very method that creates it tough or not possible to change, hack, or cheat the system. A blockchain is basically a digital ledger of transactions that are duplicated and distributed across the complete network of computer systems on the blockchain.

Benefits and needs of Blockchain:

Resilience: Blockchains are often replicated architecture. The chain is still operated by most nodes in the event of a massive attack against the system.

Time reduction: In the financial industry, blockchain can play a vital role by allowing the quicker settlement of trades as it does not need a lengthy process of verification, settlement, and clearance because a single version of agreed-upon data of the shared ledger is available between all stack holders.

Reliability: Blockchain certifies and verifies the identities of the interested parties. This removes double records, reducing rates, and accelerates transactions.

Unchangeable transactions: By registering transactions in chronological order, Blockchain certifies the unalterability, of all operations which means when any new block has been added to the chain of ledgers, it cannot be removed or modified.

Fraud prevention: The concepts of shared information and consensus prevent possible losses due to fraud or embezzlement. In logistics-based industries, blockchain as a monitoring mechanism act to reduce costs.

Security: Attacking a traditional database is the bringing down of a specific target. With the help of Distributed Ledger Technology, each party holds a copy of the original chain, so the system remains operative, even a large number of other nodes fall.

Transparency: Changes to public blockchains are publicly viewable to everyone. This offers greater transparency, and all transactions are immutable.

Collaboration: Allows parties to transact directly with each other without the need for mediating third parties.

Decentralized: There are standards rules on how every node exchanges the blockchain information. This method ensures that all transactions are validated, and all valid transactions are added one by one.

BlockChain applications to know:

• Secure sharing of medical data
• NFT marketplaces
• Music royalties tracking
• Cross-border payments
• Real-time IoT operating systems
• Personal identity security
• Anti-money laundering tracking system
• Supply chain and logistics monitoring
• Voting mechanism
• Advertising insights
• Original content creation
• Cryptocurrency exchange
• Real estate processing platform

Blockchain Course

In this course, we tend to are going to focus on the basics of Blockchain development and also the popular implementation of the technology referred to as Ethereum. By the top of this course, you may understand everything you would like to know to be productive with blockchain development as well as the way to created and put together your development environment from scratch.

Advantages of BlockChain

Here are some advantages of…

• With blockchain, your business process will be better protected with the help of a high level of security.
• The hacking threats against your business will also be reduced to a greater extent.
• As blockchain offers a decentralized platform, there is no need to pay for centralized entities or intermediaries’ services.
• Enterprise blockchain technology enables organizations to use different levels of accessibility.
• Organizations can do faster transactions with the help of blockchain.
• Account reconciliation can be automated.
• The transactions done are transparent and hence, easy to track.

What is the “Blockchain” Certification?

This certificate can give you with the chance to create a foundation towards turning into a strategic business partner inside your organization and together with your clients.

You may have heard of individuals implementing blockchain in several industries and taking this technology a lot of seriously in varied use cases, however, hardly you’ve got heard regarding the benefits of certification and a career in blockchain.

Scope of Blockchain:

Blockchain may be defined as a decentralized and distributed digital ledger that’s used to record transactions across several computers. In easy terms, we are able to contemplate any record inside Blockchain technology as a document shared with a group of individuals. (computers/servers that are also known as blocks).

Here you can see the Agenda of Blockchain:

Conclusion

In the Age of Technology, this is what democracy is supposed to look like. Not a day goes past that we do not hear laments about the stranglehold that big technology firms like Apple, Google, and Facebook have over our online identities. The Bitcoin is that the 1st productive implementation of blockchain. Today, the globe has found applications of blockchain technology in many industries, wherever trust while not the involvement of centralized authority is desired.

If you wanna learn about related this course, then I would suggest you go through DevOpsSchool courses which is a great platform to learn.

Thank you!

The post Complete guide of BlockChain Certification Courses Tutorials and Training appeared first on scmGalaxy.

You must admit that learning Android app development isn’t easy as it look. For the non-programmer there are several steps in the process, and even experienced programmers have quite a bit to learn when adopting Android. If you’re interested in developing new and innovative applications for the world’s #1 mobile platform – here are my six steps to becoming an Android app developer.

Now the questions arise are, Why Android? How to start? Where to start? And many more Question like this. So in this particular blog we will discuss in all this topics and I will try best to answer them all. Let’s start-

Who is an Android App Developer?

An Android App Developer is a Software Developer expertise in designing applications for the Android for mobile platform. This is the only competitor to Apple’s app store. Their job revolves around creating the apps we use on our smartphones and tablets. It is a skilled, entry-level position.

According to the recent studies, demand for Software Developers, which includes Android Developers, is expected to rise a whopping 21 percent through 2024. As an Android developer, you need to be very clear with your job posting and your responsibilities. So, here are some key roles and responsibilities of an Android Developer, that define who can be a successful developer.

These roles and responsibilities define who can be a successful developer.

There are several of specific tasks that an Android app Developer execute to develop Android applications. There are some of the following duties of Android app Developer-

Design and Build Advanced Applications for the Android Platform

In this an Android Developer dedicates most of their time. This development includes of using C / C++, JavaScript and a few other tools to write program code. It requires extreme attention, because one mistyped line of code can spoil the whole program.

Collaborate with Cross-Functional Teams to Define, Design and Ship New Features

An Android App Developer works with Product Development, User Experience and several other departments to define and design new features that users actually want.

Troubleshoot and Fix Bugs in New and as well as on Existing Applications

An Android App Developer’s job isn’t done after an application is completed. In fact they are also responsible for troubleshooting bugs that arise when the app is shipped to users in near future.

Continuously Discover, Evaluate and Implement New Development Tools

Android App Developers have to be up to date by latest trends in mobile application. They have to discover new tools as they hit the market. This requires the ability to adapt to an ever-changing environment.

Work With Outside Data Sources and APIs

An Android App developer spends so much amount of time working with outside data sources and APIs that provided.

How to become an Android App Developer?

Android App Developers can follow an easy pathway to become a successful Android App Developer as they already have an idea about how the applications work.  However, If you are someone, want to start your journey towards becoming an Android App Developer and really gain an advantage in the job market, then start working on these advanced skills many employers prefer in their Android App Developers career-

• Should have strong knowledge of Android SDK and different versions of Android.
• Proficient in programming languages like Java/Kotlin.
• Strong knowledge of Android UI design principles, patterns, and best practices.
• Decent knowledge with SQL.
• Proficient understanding of code versioning tools, such as Git.
• Familiarity with RESTful APIs that connects Android applications to back-end services.
• Experience working with offline storage, threading, and performance tuning.
• Possess the ability to design applications around UI such as touch.
• Ability to understand business requirements and translate them into technical requirements.
• Familiarity with cloud message APIs and push notifications.
• Understanding of Google’s Android design principles and interface guidelines.
• Familiarity with continuous integration.

At last, mastering these skills will definitely help you grow as a successful Android App Developer. And also do note that Android is one such domain where jobs are never out of stock. So start now to be an amazing developer.

Job roles

• Mobile App Developer
• Android Engineer
• Mobile Architect
• Embedded Software Engineer – Mobile
• Lead Software Engineer- Mobile
• Android Developer
• Android Engineer
• Mobile Developer

Why you should choose Android App Developer as a Career?

There are so many reasons why you should go for Android Development. Some notable ones among them are listed below:

Salary

According to the recent studies, the national avg. salary for Software Developers, which includes Android Developers, is $109,300. Those in the bottom 10 percent make less than $57,300, while those in the top 10 percent make more than $183,700. The three states with the highest median salary for Android Developers are California at $128,700, Washington at $123,400 and Massachusetts at $113,600.

Android is an evolving platform

Applications that are created are gaining lot of popularity and are rated top on the Google play store. With the time, Google keeps changing certain functionalities and releasing the new versions. So, you get updates yourself on a regular basis to improvised features that are added to your application. This is also a challenging task to develop, something that can catch the eye of any user.

Easy to learn

The developers out there will definitely feel that the time invested in learning how to develop an Android application is comparatively less than what they invest in other technologies. Have the knowledge of Java and scripting languages like Perl, PHP, and the job is done.

Conclusion

By learning Android development in 2021, you open up for many career opportunities such as freelancing, becoming an indie developer, or working for high profile companies like Google, Amazon, Facebook and more. The demand for native Android developers is still very high, and learning Android development has never been easier thanks to increases in online learning materials. Choosing Android App Developer as Career is a good option in 2021, If you want to learn or want to become an Android App Developer than I would like to suggest you DevOpsscool, One of the best option for this course, provide you best learning experience with in-hand practices, Experts are there to solve your query. Don’t wait for the right time to come, Start your learning today.

I Hope this blog is helpful for you and enough knowledge of Android App Developer.

Thank you!!

The post How to Become an Android App Developer? appeared first on scmGalaxy.

1. Apache: The most popular web server is Apache HTTP Server, which is used by 34.1% of websites in 2021. The BuiltWith Internet services corporation has 62,624,313 live websites that use Apache. 

2. Nginx: Is the second most prominent server, accounting for 33.7% of all active websites in 2021. The web server is distributed under a BSD-style license.

3. Cloudflare Server: Supports web protocols, including SPDY and HTTP/2 and acts as a reverse proxy for web traffic. It is getting more and more popular over years with 18% in 2021.

4. LiteSpeed: Uses the same configuration format as Apache HTTP Server and is compatible with most Apache features. An open source variant is also available. As of April 2020, LSWS was used by 47.6% of websites using HTTP/3. It also sees an increasing trend and takes 18% of the total web server usage.

5. Microsoft-IIS: Supports HTTP, HTTP/2, HTTPS, FTP, FTPS, SMTP and NNTP. It took by about 7% of the total web servers in 2021.

What means web server?

• A Web server is a program that generates and transmits responses to client requests for Web resources.
• A Web server is a program to satisfy client requests for web resources.

What are Web servers examples?

Web servers examples are: Apache web server, IIS, NGINX, Tomcat, PWS.

What are the different types of Web servers?

The most prominent types of Web Servers available in the markets are:

1. Apache HTTP Server Web Server
2. Internet Information Services (IIS) Web Server
3. Lighttpd Web Server
4. Sun Java System Web Server
5. Jigsaw Server Web Server
6. LiteSpeed server Web Server
7. Node.js Web Server

What are the functions of Web server?

• Read any data sent by the user.
• Look up any other information about the request that is embedded in the HTTP request.
• Process the request.
• Generate the result.
• Format the result inside a document.
• Set the appropriate HTTP response parameters.
• Send the document back to the client as HTML file.

The post List of Top 5 Web servers in 2021 appeared first on scmGalaxy.

In January 2009, Webtide announced that Jetty would be moving to Eclipse Foundation. The Jetty project has been created, and the initial Jetty 7 code (with a refactored org.eclipse.jetty package) was checked into Jetty Subversion at Eclipse.
The Java support in Google App Engine is built on Jetty.

Jetty provides an HTTP server, HTTP client, and javax.servlet container. These components are open source and available for commercial use and distribution.
Jetty is used in a wide variety of projects and products. Jetty can be embedded in devices, tools, frameworks, application servers, and clusters. See the Jetty Powered page for more uses of Jetty.

The core Jetty project is hosted by the Eclipse Foundation. The codehaus provides Jetty accessories , integrations, and extensions, as well as hosting older versions of Jetty. See the About page for information about the project structure.

Features Jetty

• Full-featured and standards-based
• Open source and commercially usable
• Flexible and extensible
• Small footprint
• Embeddable
• Asynchronous
• Enterprise scalable
• Dual licensed under Apache and Eclipse

Powered

• Large clusters, such as the Yahoo Hadoop Cluster
• Cloud computing, such as the Google AppEngine
• SaaS, such as Yahoo! Zimbra
• Application Servers, such as Apache Geronimo
• Frameworks, such as GWT
• Tools, such as the Eclipse IDE
• Devices, such as phones
• More…

Reference: 
http://jetty.codehaus.org/jetty/
http://en.wikipedia.org/wiki/Jetty_%28web_server%29
http://www.mortbay.org/jetty/
http://www.eclipse.org/jetty/

The post Jetty – Java-based HTTP server appeared first on scmGalaxy.

• Extended functionality via plugins.
• Free and open source.
• Filters are code.
• Great integration with other Elastic products.

• Handles up to 50,000 messages per second at peak time
• Data filtering and alerting
• Apache 2.0 License project
• Simplify and scale data pipeline management with tags
• More than 200 community-contributed plugins
• Real-time monitoring and alerts system
• Store data in multiple systems
• Collect and correlate web server access logs and application error logs

• Text-based logs from any source
• Custom source groups
• Point-and-click trending graphs
• Automated filters and event parsing
• Full-system RESTful API to integrate with other applications
• Unlimited saved searches and users
• Adaptable interface with multiple views, pages and workspaces
• Unlimited custom dashboards based on any search
• Built-in customizable alerts with triggers

• Leverages Java, Scala and ElasticSearch technologies
• Central syslog monitoring
• Interactive API browser
• Application debugging
• Exception monitoring
• API analytics
• Intuitive search interface
• Comprehensive dashboard

5. Splunk

• Works with Hadoop & NoSQL
• Setup standard searches as real-time alerts
• Trigger automatic responses
• Scale from a single server to multiple data centers
• Deployable to on premise sites, hybrid-cloud, and/or private and public cloud based infrastructures
• Securely make data available
• Supports various use cases including log consolidation/retention, security, compliance reporting, and more
• Perform ad hoc queries

The post Top 5 Log Monitoring Tools | List of Log Monitoring Tools | scmGalaxy appeared first on scmGalaxy.

This tutorial is to setup the SVNServer from base using Apache2 in Ubantu only.

> sudo apt-get update

> sudo apt-get install subversion apache2 libapache2-svn apache2-utils

> sudo addgroup subversion

> sudo mkdir /home/svn

> sudo chown -R www-data:subversion /home/svn

> sudo chmod -R g+ws /home/svn

> sudo svnadmin create /home/svn/myWebsite

sudo vim /etc/apache2/mods-available/dav_svn.conf

& add the following entry at the end of file.

<Location /svn/myWebsite> DAV svn SVNPath /home/svn/myWebsite AuthType Basic AuthName "myWebsite subversion Repository" AuthUserFile /etc/subversion/passwd <LimitExcept GET PROPFIND OPTIONS REPORT> Require valid-user </LimitExcept> </Location>

sudo htpasswd -c /etc/subversion/passwd rajesh

sudo chown -R www-data:subversion /home/svn/myWebsite

sudo chmod -R g+rws /home/svn/myWebsite

sudo /etc/init.d/apache2 restart

sudo htpasswd /etc/subversion/passwd user1

sudo /etc/init.d/apache2 restart

All DONE.

Now you can access the SVN Server using….

http://uvo12exe3iancqqq622.vm.cld.sr/svn/myWebsite/

If you are still not able to open the url, that means you have IPtables services running and stopping you to access the server. For testing, you can stop the sudo ufw stop

The post How to Setup SVN Server with Apache2 in Ubantu? appeared first on scmGalaxy.

ScriptRock’s GuardRail

As DevOps gets more agile, infrastructure needs unit tests too. Enterprise startup ScriptRock offers cloud-hosted testing configuration tools to get you started.

The post Server configuration monitoring and diagnostics appeared first on scmGalaxy.

SVN SERVER SETUP

Step to setting subversion server for administrator:-
1. Check to see if subversion is installed:-
# rpm -q subversion
subversion-1.4.4-1.fc7
or
#svn –version
svn, version 1.5.2 (r32768)
compiled Oct 4 2008, 02:48:59
If you see “package subversion not installed” you will need to install subversion before
proceeding. Otherwise you should see something similar to “ subversion-1.4.4-1.fc7”
2. Login in as root:-
3. Create a directory to hold all your repositories:-
#mkdir /home/svnserver/svn
4. Create a repository. In this example we will create a repository called “repositories”:-
# svnadmin create /home/svnserver/svn
5. list the repository files and directory :-
#ls
conf db format hooks locks README.txt
6. Create a SVN user
6.1 vi /home/svnserver/svn/conf/svnserve.conf
In that file add these three lines:
anon-access=write
auth-access=write
password-db=passwd
Note:- Do not leave space before this three lines.
6.2 Create a password file.
vi /home/svnserver/svn/conf/passwd
In that file add a line for your user:
# add users in the format : user = password
user = mypassword
7. Create a directory to hold all your project in repositories:-
# mkdir /home/svnserver/svn/myproject
8. Try importing source code into the repository. Change to a directory containing the files you want to
check in.
# svn -m “Intailly importing” import /home/svnproject/source/myproject file:///home/svnserver/svn/myproject
9. Start the SVN Server as Daemon:-
#svnserve -d
10. Try checking it out of the repository:- (Check out)
home/user/source# svn co svn://192.168.0.103/home/svnserver/svn/myproject
11. Try checking it in of the repository:- ( Check in)
#svn ci -m “log message” /home/user/source/myproject/

The post SVN SERVER SETUP appeared first on scmGalaxy.

Any Server will (mostly) do   

• CGI will not work without a server
• Your Server must allow CGI
• Your CGI application must be written in a language supported by your server
• You can use probably your existing web server
• If you need to test on your local computer, you may install WAMP/XAMPP
• Each Server has a particular requirements about running  CGI Applications

Prerequisties
Experience in relevant programming language

• Perl
• Php
• Unix Shell
• c/c++
• HTML/CSS

What is CGI
Common Interface Gateway

• How web browsers submit forms and interact with programs on the server
• Used for simple interaction applications
• Can be used with any programming language
• Often called “CGI Scripts”
• Can be written in any language
• Run in the server, not in a web browser
• Must follow server requirements for running applocations

ANY SERVER WILL (MOSTLY) do

• CGI will not work without a web server
• Your Server must allow CGI
• Your CGI application must be written in a language supported by your server
• You can use  your existing web server
• If you need to test on your local computer, you may install WAMP/XAMPP

Some Guidelines for Unix/Apapche users

1. Permission – 755 ( aka rwxr-xr-x)
2. Filename associates
3. .cgi, .pl, .php …etc
4. .httaccess
5. Options+ExecCGI
6. AddHandle cgi-scripts .cgi
7. SetHander cgi-script
8. Access to server log

Some Guidelines for Windows Servers
Many Windows servers do not support perl or PHP
May require ASP or C#
Usually require specific filename extension
.pl for perl
.php for php
.asp or .aspx for ASP
Access to error log
Check with your server web site or support staff

How CGI works

1. Browser Communicates with server over HTTP
2. Browser sends a request to the server consisting of header and optional body
3. Server sends information to the CGI application
4. Environment variables
5. Body may be sent in the STDIN stream
6. Server sends a response consisting of a header and a body

The post Introduction of CGI | What is Common Gateway Interface (CGI)? appeared first on scmGalaxy.

Check CRS Status

[root@racnode1 ~]#crsctl check crs

Check Clusterware Resources

[root@racnode1 ~]# crs_stat -t -v

Stopping the Oracle Clusterware Stack on the Local Server

[root@racnode1 ~]# /u01/app/11.2.0/grid/bin/crsctl stop cluster

CRS-2673: Attempting to stop 'ora.crsd' on 'racnode1'

...

...

Stop Oracle Clusterware stack on all servers in the cluster

[root@racnode1 ~]# crsctl stop cluster -all

Starting the Oracle Clusterware Stack on the Local Server

[root@racnode1 ~]# /u01/app/11.2.0/grid/bin/crsctl start cluster

CRS-2673: Attempting to start 'ora.crsd' on 'racnode1'

...

...

Start Oracle Clusterware stack on all servers in the cluster

[root@racnode1 ~]# crsctl start cluster -all

Check Cluster Nodes

[oracle@racnode1 ~]$olsnodes -n

Confirming Oracle ASM Function for Oracle Clusterware Files

If you installed the OCR and voting disk files on Oracle ASM, then use the following command syntax as the Grid Infrastructure installation owner to confirm that your Oracle ASM installation is running:

[oracle@racnode1 ~]$srvctl status asm -a

Check Oracle Cluster Registry (OCR)

[oracle@racnode1 ~]$ocrcheck

Check Voting Disk

[oracle@racnode1 ~]$crsctl query css votedisk

Check Status Oracle Enterprise Manager

[oracle@racnode1 ~]$emctl status dbconsole

Start Oracle Enterprise Manager

[oracle@racnode1 ~]$emctl start dbconsole

Stop Oracle Enterprise Manager

[oracle@racnode1 ~]$emctl stop dbconsole

All Oracle Instances – (Database Status)

[oracle@racnode1 ~]$ srvctl status database -d racdb

Single Oracle Instance – (Status of Specific Instance)

[oracle@racnode1 ~]$ srvctl status instance -d racdb -i racdb1

Start/Stop All Instances with SRVCTL

[oracle@racnode1 ~]$ srvctl stop database -d racdb

[oracle@racnode1 ~]$ srvctl start database -d racdb

Node Applications – (Status)

[oracle@racnode1 ~]$ srvctl status nodeapps

Node Applications – (Configuration)

[oracle@racnode1 ~]$ srvctl config nodeapps

List all Configured Databases

[oracle@racnode1 ~]$ srvctl config database

Database – (Configuration)

[oracle@racnode1 ~]$ srvctl config database -d racdb -a

ASM – (Status)

[oracle@racnode1 ~]$ srvctl status asm

ASM – (Configuration)

[oracle@racnode1 ~]$srvctl config asm -a

TNS listener – (Status)

[oracle@racnode1 ~]$ srvctl status listener

SCAN – (Status)

[oracle@racnode1 ~]$ srvctl status scan

SCAN – (Configuration)

[oracle@racnode1 ~]$ srvctl config scan

VIP – (Status of Specific Node)

[oracle@racnode1 ~]$ srvctl status vip -n racnode1

[oracle@racnode1 ~]$ srvctl status vip -n racnode2

VIP – (Configuration of Specific Node)

[oracle@racnode1 ~]$ srvctl config vip -n racnode1

[oracle@racnode1 ~]$ srvctl config vip -n racnode2

Configuration for Node Applications – (VIP, GSD, ONS, Listener)

[oracle@racnode1 ~]$ srvctl config nodeapps -a -g -s -l

Verifying Clock Synchronization across the Cluster Nodes

[oracle@racnode1 ~]$ cluvfy comp clocksync -verbose

The post Oracle RAC Cheat Sheet | Oracle RAC Guide | Oracle RAC Reference appeared first on scmGalaxy.

After a quick detour to install Notepad++, I’m on my way to installing Magento. Before I can get into the meat of it, though, I do require a few prerequisites.

From the installation instructions, installing Magento requires:

• Apache 1.3.x or Apache 2
• PHP 5.2.0 and above with Safe mode off
• MySQL 4.1.20 and above

After a brief search, I happened upon a very handy site (Yes, my current dev machine runs Windows 7). No sense reinventing the wheel, so these instructions should do nicely.

I’ve chosen the latest stable release, 2.2.17, MD5-verified and ready to install.

Always one to put the right foot forward… The first thing I’ve done is to immediately download the wrong version (src) instead of the neatly prepped installer (msi) as per the instructions. Round 1 goes to my eagerness, but after a neat revisit to the Apache download page, I’m off in the right direction.

After kicking off the Apache installer, my first instinct was to twitch at the frozen installer progress (Did the instructions forget about that ghastly Windows 7 User Account Control?), but after only a brief pause, the UAC prompt has displayed and the Apache web server installation is back on track.

None the worse for wear, time for the next step.

PHP

I’ve pretty much kaboshed most of the PHP installation instructions, mostly due to its avoidance of the handy PHP for Windows installer. Pointing the installer to the Apache web server’s cgi-bin folder seems like a good idea.

A configuration change…

; Directory in which the loadable extensions (modules) reside.
; http://php.net/extension-dir
; extension_dir = “./”
; On windows:
extension_dir = “ext” ; Uncommented (removed the semicolon at the beginning of) this line

… and I’m back to the instructions. After an update to my environment variables, looks like it’s time for a reboot… and sleep.

I’ll be leaving the MySQL install (and testing Apache web server and PHP) ’til tomorrow.

The post Apache web server Installation Guide, know how to Install Apache web server on Windows 7? appeared first on scmGalaxy.

The volunteer developers behind Apache Tomcat have released version 7.0.6 of the open-source Java servlet container.

“This is the first stable release of the Tomcat 7 branch,” developer Mark Thomas wrote in an e-mail announcing the release on various Tomcat developer mailing lists.

While not a full application server, Tomcat implements the functionality described in the Java Enterprise Edition Web profile specifications. Most notably, it supports version 3.0 of the Servlet API (application programming interface) and version 2.2 of JavaServer Pages, both part of the recently ratified JEE 6. A servlet container manages Java-based applications that can be accessed from a Web browser.

The use of Servlet 3.0 will bring a lot of new capabilities to Tomcat, noted Tomcat contributor Tim Funk, in a presentation at the ApacheCon conference in Atlanta in November.

One big area of improvement is in configuration management for Web applications. Previous versions required all Web app configuration changes to be entered in a central file called web.xml, a process that led to unwieldy web.xml files as well as security risks.

The new approach, called annotations, breaks configuration instructions into multiple files. Separate files are kept for security, for configuring new connections, for initial parameters and for handling third-party libraries.

Other benefits of Servlet 3.0 include advanced cookie management and asynchronous thread support, which should increase the number of connections Tomcat can handle.

In preparation for the release, various beta versions of Tomcat 7 have been distributed since April 2010. Version 7.0.6 fixes some longtime memory leak issues and includes a number of other bug fixes as well.

In addition to making the source code and various binaries available, the development team has packaged a version of the software that can be embedded in other applications.

Tomcat is one of almost 150 open-source projects maintained by the Apache Software Foundation.

The post Apache Tomcat – Tomcat 7 Finalized – Tomcat 7 Introduction appeared first on scmGalaxy.

This article is a summary of a seminar I had on the topic. If it seems like it’s a continuation of an existing discussion that’s because, to some extent, it is. If you haven’t been discussing exchanging your app server, this article probably isn’t very interesting to you.

By putting the application server inside my application instead of the other way around, I was able to leap tall buildings in a single bound.

The embedded application server

This is how I deploy my sample application to a new test environment (or to production):

1. mvn install
2. scp -server/target/-1.0.onejar.jar appuser@appserver:/home/appuser/test-env1/
3. ssh appuser@appserver “cd /home/appuser/test-env1/ && java -jar -1.0.onejar.jar&”

This require no prior installed software on the appserver (with the exception of the JVM). It requires no prior configuration. Rolling back is a matter of replacing one jar-file with another. Clustering is a matter of deploying the same application several times.

In order to make this work in a real environment, there are a many details you as a developer need to take care of. As a matter of fact, you will have to take responsibility for your operational environment. The good news is that creating a good operational environment is not more time-consuming than trying to cope with the feed and care of a big-a Application Server.

In this scheme every application comes with its own application server in the form of jetty’s jar-files embedded in the deployed jar-file.

The advantages

Why would you want to do something like this?

• Independent application: If you’ve ever been told that you can’t use Java 1.5 because that would require an upgrade of the application server. And if we upgrade the application server, that could affect someone else adversely. So we need to start a huge undertaking to find out who could possibly be affected.
• Developer managed libraries: Similar problems can occur with libraries. Especially those that come with the application server. For example: Oracle OC4J helpfully places a preview version of JPA 1.0 first in your classpath. If you want to use Hibernate with JPA 1.0-FINAL, it will mostly work. Until you try to use a annotation that was changed after the preview version (@Discriminator, for example). The general rule is: If an API comes with your app server, you’re better served by staying away from it. A rather bizarre state of affairs.
• Deployment, configuration and upgrades: Each version of the application, including all its dependencies is packaged into a single jar-file that can be deployed on several application server, or several times on the same application server (with different ports). The configuration is read from a properties-file in the current working directory. On the minus side, there’s no fancy web UI where you can step through a wizard to deploy the application or change the configuration. On the plus side, there is no fancy web UI …. If you’ve used one such web UI, you know what I mean.
• Continuous deployment: As your maven-repository will contain stand alone applications, creating a continuous deployment scheme is very easy. In my previous environment, a cron job running wget periodically was all that was needed to connect the dots. Having each server environment PULL the latest version gives a bit more flexibility if you want many test environments. (However, if you’re doing automated PUSH deployment, it’s probably just as practical for you).
• Same code in test and production: The fact that you can start Jetty inside a plain old JUnit test means that it is ideal for taking your automated tests one step further. However, if you test with Jetty and deploy on a different Application Server, the difference will occasionally trip you. It’s not a big deal. You have to test in the server environment anyway. But why not eliminate the extra source of pain if you can?
• Licenses: Sure, you can afford to pay a few million $ for an application server. You probably don’t have any better use for that money, anyway, right? However, if you have to pay licenses for each test-server in addition, it will probably mean that you will test less. We don’t want that.
• Operations: In my experience, operations people don’t like to mess around with the internals of an Application Server. An executable jar file plus a script that can be run with [start|status|stop] may be a much better match.

The missing bits

Taking control of the application server takes away a lot of complex technology. This simplifies and makes a lot of stuff cheaper. It also puts you back in control of the environment. However, it forces you to think about some things that might’ve been solved for you before:

• Monitoring: The first step of monitoring is simple: Just make sure you write to a log file that is being monitored by your operations department. The second step requires some work: Create a servlet (or a Jetty Handler) that a monitoring tool can ping to check that everything is okay. Taking control of this means that you can improve it: Check if your data sources can connect, if your file share is visible, if that service answers. Maybe add application-calibrated load reporting. Beyond that, Jetty has good JMX support, but I’ve never needed it myself.
• Load balancing: My setup supports no load balancing or failover out of the box. However, this is normally something that the web server or routers in front of the application server anyway. You might want to look into Jetty’s options for session affinity, if you need that.
• Security: Jetty supports JAAS, of course. Also: In all the environments I’ve been working with (CA SiteMinder, Sun OpenSSO, Oracle SSO), the SSO server sends the user name of the currently logged in user as an HTTP header. You can get far by just using that.
• Consistency: If you deploy more than one application as an embedded application server, the file structure used by an application (if any) should be standardized. As should the commands to start and stop the application. And the location of logs. Beyond that, reuse what you like, recreate what you don’t.

Taking control of your destiny

Using an embedded application server means using the application server as a library instead of a framework. It means taking control of your “main” method. There’s a surprisingly small number of things you need to work out yourself. In exchange, you get the control to do many things that are impossible with a big-A Application Server.

Reference: http://www.javaworld.com/community/

The post Why and how to use Jetty in mission-critical production appeared first on scmGalaxy.

Link: http://www.collab.net/downloads/subversion/

1. Platform and configuration

   Product: CollabNet Subversion server

   Certified platforms: Windows XP SP2, Win 2003(Standard Edition) R2

   Apache version: 2.2.8

   ViewVC: 1.0.5 (requires ActiveState Python 2.5)

   Repository format: fsfs (bdb support not included)

   Prerequisite: The user needs administrative privileges to install

   and uninstall CollabNet Subversion.

2. IMPORTANT: Apache version upgraded from 2.0 to 2.2

   With the CollabNet Subversion 1.5.0 release, we have upgraded the included

   Apache server version from 2.0 to 2.2. This is consistent with the

   packages we provide for other operating systems, and also upgrades our

   package to the best available version of Apache.

   This is important to existing users because your current Apache 2.0 server

   configuration cannot be automatically updated to the format of the Apache

   2.2 configuration file. If you allow the installer to upgrade your existing

   installation, it backs up your Apache conf, logs, and htdocs folders so

   that you can refer to your previous configuration when configuring your new

   server.

3. Installation tips

     If you install an Apache server, the installer asks you for a

     “Repository URL.” This represents the prefix of the URL which users can

     use to connect to Subversion. If you set this URL to ‘/svn’, then users

     can checkout their repository from:

        http://hostname/svn/repos-name

     We recommend that you use ‘/svn’ as your URL prefix, as this is common

     practice.

4. ViewVC installation

   Users of the Apache web server option can now also have ViewVC automatically

   installed and configured as part of the installation. You must have

   ActiveState’s ActivePython 2.5 installed before installing CollabNet Subversion.

   Download a free version of ActivePython from:

   http://www.activestate.com/Products/activepython/index.mhtml

   You must install version 2.5.x.

5. Upgrade procedure

   When the installer detects a previous version, it offers to upgrade your existing

   installation. However, if you want to add ViewVC to your installation, we

   recommend you use the following process for an upgrade. In general, this is

   the best process for any upgrade scenario:

   1. Stop Apache or Subversion Server services, if running.

   2. Copy/back up any customizations that were done to your Apache installation.

     (For example, your httpd.conf file, a password database, any content you

      added to the htdocs folder, and so on.)

   3. Uninstall the currently installed version.

   4. Manually delete the existing folder if the installer did not remove it. The

      uninstall process does not remove files that were added or modified after

      installation.

   5. Follow the normal install instructions for 1.5.

   6. Manually put back your Apache customizations. NOTE:  You cannot simply copy

      back the previous configuration file. You must make the appropriate edits

      to your new Apache 2.2 version of the configuration file.

6. Post-installation instructions

   The installer created a folder to store your repositories. You are not required

   to use this folder, but if you let the installer install the server to run as a

   service, then the server has also been configured to serve repositories from this

   location. It is a good idea to use the location you specified in the installer.

   A. Using svnserve

      ==============

   To use svnserve as your server, follow these steps:

     1. Open a new terminal (command prompt).

        NOTE: If you have an old command prompt open (prior to the Subversion

              installation), remember to open a brand new command prompt.

     2. Create a subversion repository.

        cd <Repository_Path>

        svnadmin create <Repository_Name>

        For example:

        cd \repositories

        svnadmin create my-first-repos

     3. Setup a password database.

        Using notepad, edit the svnserve.conf file inside the conf directory of your

        repository.

        For example:

        If your repository is C:\repositories\my-first-repos

        svnserve.conf is:

        C:\repositories\my-first-repos\conf\svnserve.conf

        Inside svnserve.conf, you see the following information:

         ### The password-db option controls the location of the password

         ### database file.  Unless you specify a path starting with a /,

         ### the file’s location is relative to the conf directory.

         ### Uncomment the line below to use the default password file.

         #password-db = passwd

       Follow the above instructions, and uncomment the “password-db=passwd”

       line, so that it simply says:

          password-db = passwd

     4. Setup usernames and passwords.

       Next, edit the passwd file. This passwd file is located in the

       same directory as svnserve.conf.

       Inside the passwd file, you see the following information:

       ### This file is an example password file for svnserve.

       ### Its format is similar to that of svnserve.conf. As shown in the

       ### example below it contains one section labelled [users].

       ### The name and password for each user follow, one account per line.

       [users]

       #harry = harryssecret

       #sally = sallyssecret

       To add a new user account, add your own username and password

       inside the [users] section. For example, if your name is “joe”,

       and you want to set your password to “super-secret”, add a

       new line like this:

         joe = super-secret

       Add as many users as you like.

     5. Open Port on Windows firewall.

        Before starting the server, the firewall must be notified that

        this particular port is going to be used. To enable this port in the

        Windows firewall, follow the instructions found here:

    http://www.microsoft.com/windowsxp/using/security/internet/sp2_wfexceptions.mspx

        Note: svnserve.exe is the program name which needs to be added to the

        exceptions list. Alternatively, you can also use the port where

        you decide to run the server. By default, svnserve runs on 3690.

     6. Start svnserve.

        If you elected to have the installer setup svnserve as a service, then open

        the Services application, find the entry for the Subversion server, and take

        the Start option. The service has been configured to start automatically

        on reboot. You can also run this command from the command line:

        net start svnserve

        If you did not install svnserve as a service and want to start the server

        manually, run this command:

        svnserve -d -r <Repository_Path>

        For example: svnserve -d -r C:\repositories

     7. To provide read and write access to anonymous users, modify the

        conf/svnserve.conf file inside the repository.

        anon-access = write

        To restrict an anonymous user from the repository:

        anon-access = none

     8. Check out the repository.

        svn co svn://localhost/<Repository_Name>

        For example: svn co svn://localhost/my-first-repos

     Tip: If you check out your Subversion repository from a different computer,

     replace ‘localhost’ with the IP address or hostname of the machine which

     hosts the Subversion repository.

   B. Using Apache

      ============

   To use Apache as your server, follow these steps:

     1. Configure Apache.

        The installer did these steps automatically based on the repository location

        entered in the installer. This information is only presented if you want to

        manually modify the configuration.

        Use notepad to edit the httpd.conf file inside the httpd\conf directory of your

        CollabNet Subversion Server installation.

        Tip: By default, httpd.conf is in the following directory:

             C:\Program Files\CollabNet Subversion Server\httpd\conf\httpd.conf

        At the bottom of the httpd.conf file, you see a location directive that looks

        something like this:

          <Location /svn>

            DAV svn

            SVNParentPath C:\repositories

          </Location>

        Change the above section to look like the following:

          <Location /svn>

            DAV svn

            SVNParentPath C:\repositories

            SVNListParentPath On

            Require valid-user

            AuthType Basic

            AuthName “Subversion repository”

            AuthUserFile C:\repositories\password-file

          </Location>

     2. Open a new terminal (command prompt).

        NOTE: If you have an old command prompt open (prior to the Subversion

              installation), remember to open a new command prompt.

     3. Create Subversion users.

        Now create usernames with passwords that can be used to authenticate with

        Apache. Use the htpasswd command to create usernames and passwords for the

        Apache server.

        Type the following at the command prompt:

          htpasswd -cm <password-file> <username>

        This command prompts you for a password for the user. Enter the

        password and retype the password when prompted.

        For example: If you want to create a user ‘joe’, and the file at

        “C:\repositories\password-file”, type the following at the

         command prompt:

               htpasswd -cm C:\repositories\password-file joe

        Enter the desired password for the user and retype the password

        when prompted.

        For additional users, use the following command at the command prompt:

        htpasswd -m C:\repositories\password-file joe

     4. Create a Subversion repository.

        svnadmin create <Repository_Path>\<Repository_Name>

        For example: svnadmin create C:\repositories\my-first-repos

     5. Open Port on Windows firewall.

        Before starting the server, the firewall must be notified that

        this particular port is going to be used. To enable this port in the

        Windows firewall, follow the instructions found here:

    http://www.microsoft.com/windowsxp/using/security/internet/sp2_wfexceptions.mspx

        Note: apache.exe is the program name which you need add to the

        exceptions list. Alternatively, you can also use the port where

        you decide to run the server. By default, apache is run on 80.

     6. Start Apache.

        If you elected to have the installer set up Apache as a service, then open

        the Services application, find the entry for Apache/2, and take

        the Start option. The service was configured to start automatically

        on reboot. You can also run this command from the command line:

        net start apache2

        To start the server manually, run the following at the command prompt:

        apache

     7. Checkout the repository.

        svn co http://localhost/svn/<Repository_Name>

        For example: svn co http://localhost/svn/my-first-repos

        Tip: If you check out your Subversion repository from a different

        computer, replace ‘localhost’ with the IP address or hostname

        of the machine which hosts the Subversion repository.

7. Known issues

   When trying to access a repository via ViewVC, you might see an error

   trace that ends with this message:

      ImportError: DLL load failed with error code 182

   This error occurs when you have an older version of the OpenSSL DLLs in your

   PATH ahead of the CollabNet Subversion bin folder. Many Windows applications

   ship the OpenSSL DLLs and many of them also use older versions. To fix this

   problem:

      1. Edit your PATH so that the CollabNet Subversion bin folder is at or

         near the beginning of your PATH.

      2. Reboot so that your Apache service can pick up the change.

8. Back-end support

  If you try to access an existing BDB (Berkeley DB) based repository through

  CollabNet Subversion, then you might receive an alert “Failed to load module

  for FS type ‘bdb’.” This is because CollabNet Subversion does not support BDB.

  CollabNet recommends FSFS over BDB for ease of maintenance and supportability.

9. Support for CollabNet Subversion

   Find out about CollabNet Technical Support at

   http://www.collab.net/services/subversion/

   Information about CollabNet Training, Consulting, and Migration

   services is at http://www.collab.net/services/subversion/training.html

   Join openCollabNet for community support: http://open.collab.net

10 About Subversion and CollabNet

   CollabNet launched the Subversion project in 2000 in response to the demand

   for an open standard for Web-based software configuration management that

   could support distributed development. CollabNet continues to be strongly

   involved with the Subversion project and offers CollabNet Subversion Support,

   Training, and Consulting services.

   CollabNet also provides the most widely used collaborative development

   environment in the world. More than 1,400,000 developers and IT projects

   managers collaborate online through CollabNet. The company is transforming

   the way software is developed by enabling organizations to leverage global

   development talents to deliver better products and innovate faster.

   Visit CollabNet at http://www.collab.net for more information.

The post Process to Install CollabNet SVN Command Line Client in Windows appeared first on scmGalaxy.

Link: http://www.collab.net/downloads/subversion/solaris.html

1. Platform and configuration

Product: CollabNet Subversion client

Platforms: Solaris 10 SPARC

Prerequisite: You must be a superuser (root) to install and uninstall

CollabNet Subversion.

2. Import/Update CollabNet certificate

CollabNet Subversion Solaris packages are signed. As a one-time task,

import the CollabNet certificate using the command:

    sudo pkgadm addcert -ty certificate.pem

The CollabNet certificate is available for download at:

http://www.collab.net/nonav/downloads/subversion/certificate/certificate.pem

NOTE: the certificate has changed between 1.5.0 and 1.5.1 release.  The

certificate used for 1.5.0 had a short expiration date so we have created

a new certificate.  If you have previously installed the 1.5.0 certificate,

you must remove it before installing the new one:

    sudo pkgadm removecert “Alexander Thomas(AT)”

Once it is removed you can install the new certificate.

3. First installation

The command to install the CollabNet Subversion client, if a previous version

has not already been installed, is:

    sudo pkgadd -d /path/to/client-sparc-local

4. Updating an existing installation

The proper way to update a Solaris package is to remove the current version

and then install the new version.  If you have the CollabNet Subversion server

installed, you will need to remove it first.  Again, refer to the readme for

that package before proceeding.

    sudo pkgrm CSVNclnt

    sudo pkgadd -d /path/to/client-sparc-local

5. Post-installation instructions

A. CollabNet Subversion installs into /opt/CollabNet_Subversion, which is

   probably not on the executable search path for your system. Add the directory

   /opt/CollabNet_Subversion/bin to your $PATH environment variable. In order to

   make this change affect all users of your system and persists across reboots,

   add the following line to /etc/profile:

    PATH=/opt/CollabNet_Subversion/bin:$PATH

B. CollabNet Subversion provides man pages and localizations for several

   languages. To take advantage of these features, update your MANPATH and/or

   LOCPATH environment variables to include the CollabNet Subversion directories.

   For example:

    export MANPATH=/opt/CollabNet_Subversion/share/man:$MANPATH

    export LOCPATH=/opt/CollabNet_Subversion/share/locale:$LOCPATH

6. Support for CollabNet Subversion

Find out about CollabNet Technical Support at

http://www.collab.net/services/subversion/

Information about CollabNet Training, Consulting, and Migration

services is at http://www.collab.net/services/subversion/training.html

Join openCollabNet for community support: http://open.collab.net

7. About Subversion and CollabNet

CollabNet launched the Subversion project in 2000 in response to the demand

for an open standard for Web-based software configuration management that

could support distributed development. CollabNet continues to be strongly

involved with the Subversion project and offers CollabNet Subversion Support,

Training, and Consulting services.

CollabNet also provides the most widely used collaborative development

environment in the world. More than 1,400,000 developers and IT projects

managers collaborate online through CollabNet. The company is transforming

the way software is developed by enabling organizations to leverage global

development talents to deliver better products and innovate faster.

Visit CollabNet at http://www.collab.net for more information

The post How to Install CollabNet SVN Command Line Client in Solaris? appeared first on scmGalaxy.

The Subversion client can go through a proxy, if you configure it to do so.

First, edit your “servers” configuration file to indicate which proxy to use. The files location depends on your operating system.

On Linux or Unix it is located in the directory “~/.subversion”.

On Windows it is in “%APPDATA%\Subversion”. (Try “echo %APPDATA%”, note this is a hidden directory.)

The post How to Access SVN when client is under proxy ? appeared first on scmGalaxy.