The post How to Start and Stop Nagios Core | Nagios Tutorial appeared first on scmGalaxy.

How to start and stop Naxios XI Server?

How to stop Naxios XI Server?

service nagiosxi stop

service npcd stop

service ndo2db stop

service nagios stop

service postgresql stop

service mysqld stop

service httpd stop

How to start Naxios XI Server?

service httpd start

service mysqld start

service postgresql start

service nagios start

service ndo2db start

service npcd start

service nagiosxi start

The post Steps to Start-Stop Nagios XI Server | Nagios XI Tutorial appeared first on scmGalaxy.

What’s new in Rational Build Forge?

What if your software development organization could vastly accelerate the build and release process?

• Enabling you to manage your development system from virtually anywhere.
• Freeing your developers from the most repetitive, mundane tasks.

What if you could do all this while leveraging your existing investments? That’s where IBM Rational Build Forge software can help.

IBM Rational Automation Framework is a customizable framework that provides automation of environment build-outs, configuration management and application deployments on heterogeneous middleware platforms. Rational Automation Framework helps cut operational costs, improves productivity, and enables you to gain control over complex middleware environments.

• Podcast: All new Rational Automation Framework and Rational Build ForgeThe newest releases of Build Forge and Rational Automation Framework are now available. This podcast provides an overview of the new features and improved functionality of these products. Hear the details from the developers who built them.

Getting started with Rational Build Forge

Rational Build Forge is multifaceted software with many uses, from basic build capabilities to advanced integrations with other IBM and open source software.

With basic-use tutorials, you can begin by creating and running a simple Hello World project, and move on to address more complex features such as environments, dot commands and adaptors. Each of the following tutorials will take about 30 minutes to complete. You can walk through the step-by-step instructions in the tutorial documents while watching the narrated videos.

1. Creating and scheduling a project in Build Forge (Hello World)

• Video
• Tutorial (65KB)

2. Libraries and pass/fail chains

• Video
• Tutorial (113KB)

3. Administration (controlling user access)

• Video
• Tutorial (176KB)

4. Log Filters (with Apache Ant)

• Video
• Tutorial (208KB)

5. Environment Variables

• Video
• Tutorial (414KB)

6. Dot Commands

• Video
• Tutorial (798KB)

7. Agent Update

• Video
• Tutorial (92KB)

Integrating Rational Build Forge across the application life-cycle

Learn how to make Rational Build Forge even more powerful by combining its capabilities with those of other IBM Rational software. With the following resources, you can quickly gain an understanding of the benefits of integration and begin implementing these integrations within your organization.

• Demo: Rational Team Concert/Build ForgeThis demo shows how integration between IBM Rational Build Forge and IBM Rational Team Concert bridges the gap between collaborative lifecycle management and enterprise release engineering. You will learn to:

• Create a Rational Build Forge environment that stores Rational Team Concert connection information.
• Write a Rational Build Forge project that uses the JazzJBE adaptor to integrate with Rational Team Concert source control, and leverages the Rational Team Concert build toolkit Ant tasks to publish rich build results from Rational Build Forge into Rational Team Concert.
• Set up a Rational Build Forge engine and build definition in Rational Team Concert
• Run the Rational Build Forge project from Rational Team Concert.

• Webcast: Build and deploy automation powered by JazzThis webcast provides an overview of the new integration capabilities with IBM Rational Build Forge 7.1.3, IBM Rational Team Concert and IBM Rational Asset Manager. See how these tools work together seamlessly to manage enterprise assets using lifecycle management technologies. The IBM Rational deployment planning and automation solution enables you to execute reliable and repeatable deployments driven by deployment plans. Watch this replay to see the solution in action.
• Article: Integrating Rational Build Forge with Rational ClearCase and Rational ClearQuestThis article explains how to set up and configure these IBM Rational products to work together. It lists the adaptor template samples and identifies the environment variables that need to be added before running the adaptor.
• White paper: Adaptors (291KB)In Rational Build Forge, an adaptor helps with much more than just complex execution flow and decision making. It can also support emailing multiline variables to users, dynamic notification groups, custom BOM additions and project execution control. This white paper details the flexibility and power of adaptors and how to use them effectively.

The post Getting started with Rational Build Forge appeared first on scmGalaxy.

Please go through the link to find video for the Introduction to Git with Scott Chacon of GitHub

The post Introduction to Git with Scott Chacon of GitHub | Git Overview appeared first on scmGalaxy.

Windows Resource Kits
The Microsoft® Windows Resource Kit Tools are a set of tools to help administrators streamline management tasks such as troubleshooting operating system issues, managing Active Directory®, configuring networking and security features, and automating application deployment.

Task and Responsibilities

• Deployment
• System administration scripting
• Directory services
• Networking and internetworking
• Internet services
• Custom and automated installations
• Registry
• Security
• Policy-based administration
• Server management
• Clustering and load balancing
• Performance management
• Troubleshooting

About the Windows Server 2003 Resource Kit
Once you have download and installed the resource kit (very easy process), you are pretty much set up, now all you need to do it work with each tool so you know what they can do, and that’s the intention of this article series.

After the installation, go to Start => All Programs => Windows Resource Kit Tools => Command Shell

Download – http://www.microsoft.com/en-us/download/confirmation.aspx?id=17657

If you do a dir, you will see the directory listing for all the files listed here. Each file has a brief description of what it does:

Clearmem.exe: Clear Memory
Compress.exe: Compress Files
Confdisk.exe: Disk Configuration Tool
Consume.exe: Memory Consumers Tool
Dh.exe: Display Heap
Delprof.exe: User Profile Deletion Utility
Diskuse.exe: User Disk Usage Tool
Gpmonitor.exe: Group Policy Monitor
Instsrv.exe: Service Installer
Memmonitor.exe: Memory Monitor
Vrfydsk.exe: Verify Disk

Reference – http://www.windowsnetworking.com/articles-tutorials/windows-2003/Windows-Server-2003-Resource-Kit.html

What is Windows Service?
Windows Service applications run for a long time and are mostly used in server environments therefore they are usually called long-running applications. Capability to create windows service is one of the powerful features of .net.

Windows Service applications do not have any user interface or they do not produce any visual output. Services can run in the background while a user is performing or executing any other task in the foreground. If any user messages are generated, they are written to the Windows Event Log.

Windows Services are controlled by the Service Control Manager that helps to start, stop or pause the windows service, as needed.

Examples of windows services include task scheduling, running message queues, file indexing, plug and play device detection etc.

In the source code, Windows Service extends the System.ServiceProcess.Service class.

All Windows Services that are built in .NET need to extend this class. Visual studio includes the following methods by default, which are overridden by the service when it is created.
Dispose – clean up any managed and unmanaged resources
OnStart – control the service startup
OnStop – control the service stoppage

How to create Windows Service?

• Select a new project from File menu.
• Expand “Visual Basic” tab and select “Windows”.
• Then select Windows Service in it and specify the name of the service.
• Then right click on the form and select Add Installer.
• Project Installer gets added.
• Select ServiceInstaller1, go to properties and set DisplayName, ServiceName and set StartType as Automatic.
• Then select ServiceProcessInstaller1 and set Account property as LocalSystem.

Windows troubleshooting For Build Issues

• OS Environment issues
• Application Configuration settings
• OS Memory Utilization
• Disk I/O activies
• Services running
• Network issues

Chkdsk
The Windows Chkdsk (check disk) utility can find and fix common problems with disks and storage devices.

Disk Cleanup utility
The Disk Cleanup utility is a simple tool in Windows XP and Windows Vista that can remove temporary files from your PC, thus freeing up hard disk space.

The post Introduction of Windows Internal | Windows Internal Overview | Windows Internal Quick Guide 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.

My Perforce Streams log can be found in following location.

http://community.scmgalaxy.com/pg/file/read/40841/know-more-about-perforce-streams

The post Quick Start Guide – Perforce Streams – Perforce Guide appeared first on scmGalaxy.

Perforce Replication

Replication is the duplication of server data from one Perforce Server to another Perforce Server, ideally in real time. You can use replication to:

• A replica server can function as an up-to-date warm standby system, to be used if the master server fails. Such a replica server requires that both server metadata and versioned files are replicated.
• Reduce load and downtime on a primary server by Long-running queries and reports, builds, and checkpoints can be run against a replica server, reducing lock contention.
• Perforce administrators can configure the Perforce Broker to redirect commands to read-only replica servers to balance load efficiently across an arbitrary number of replica servers.

NOTES:

• For checkpoints and some reporting tasks, only metadata needs to be replicated.
• For reporting and builds, replica servers will need access to both metadata and versioned files.
• With the 2010.2 release, the Perforce Server now replication between Perforce servers of both metadata and versioned files.

Limitation:

• Replication is unidrectional, and replica servers are intended for read-only purposes
• Bidirectional replication is not supported, because any changes made to a replica server can be overwritten by changes made to the master Perforce server.

System Requirement:

• All replica servers must be at the same release level as the master server. Prefebalily 2010.2 to use both command (p4 pull and p4 replicate).
• All replica servers must have the same Unicode setting as the master server.
• All replica servers must be hosted on a filesystem with the same case-sensitivity behavior as the master server’s filesystem.
• All replica servers must be hosted on a filesystem with the same case-sensitivity behavior as the master server’s filesystem
• p4 replicate and p4 pull (when replicating metadata) do not read compressed journals. Therefore, the master server must not compress rotated journals until the replica server has fetched all journal records from older journals
• The master and replica servers must have the same time zone setting.

Challenge
Issues 1: The master and replica servers must have the same time zone setting

Today I was just going through P4 replication features with the correspondence of Disaster recovery(Replication), as well as bbalance load efficiently using p4 broker and p4 replica.

We can have cross-geo Disaster recovery(Replication) setup as soon as, we have same time zone setting in both (master and replica) server.  Replica server is unidirectional (read-only) so making same time zone in two difference location would not make any difference since all development activities will be happening though master servers/proxies only.

But
I learned that if we go replication with cross geo then we will not be able to take advantage of balance load efficiently as follows.

• We will not be able to take advantage of using replica server to reduce load and downtime on a primary server by Long-running queries, builds, and checkpoints in distributed geo environment.
• Perforce Broker to redirect commands to read-only replica servers to balance load efficiently across an arbitrary number of replica servers will not be having any advantage due to long distance and command will take more time to process in distributed geo environment.

Issues 2: p4 replicate and p4 pull (when replicating metadata) do not read compressed journals. Therefore, the master server must not compress rotated journals until the replica server has fetched all journal records from older journals

The replication process is designed to have as little latency as possible between the replica and the master; the compression/decompression of the journal
and manipulation of compressed data introduces additional delay and complexity which in turn increases the potential difference between the state of the master and the replica.

To Setup Replication
p4d -r $P4ROOT “-cset replica1#startup.1=p4 pull -i 2”

p4d -r $P4ROOT “-cset replica1#startup.1=p4 pull -u -i 2”

To unset Replication

p4d -r $P4ROOT "-cunset  replica1#startup.1"

To list all server configuration variables, 

use –cshow:

p4d -r $P4ROOT -cshow

This blog work still in progress…Still in Progress…

Reference

http://www.perforce.com/perforce/r10.2/manuals/p4sag/10_replication.html
http://www.perforce.com/perforce/doc.current/manuals/cmdref/pull.html
http://www.perforce.com/perforce/doc.current/manuals/cmdref/configure.html#1040665
http://www.perforce.com/perforce/doc.current/manuals/cmdref/replicate.html#1046521
http://kb.perforce.com/article/1099
http://kb.perforce.com/article/1352/accessing-server-configuration-variables
http://kb.perforce.com/article/1099
http://www.perforce.com/perforce/r10.2/manuals/p4sag/10_replication.html

The post Perforce Replication – What is Perforce Replication ? appeared first on scmGalaxy.

Apache Subversion 1.7 has Arrived

Subversion 1.7.0 has been officially released today.  With the release of Subversion 1.7 comes the release of Subversion Edge 2.1.0.  This release of Subversion Edge brings you the server binaries for Subversion 1.7.0 as well as the latest release of Apache httpd.  In addition to the inclusion of the Subversion 1.7 server binaries this release of Subversion Edge brings a number of other nice improvements including the addition of a complete 64-bit Windows binary stack.  As with all previous Subversion Edge releases you can simply update your existing installation from the Subversion Edge web console.  There are no other special considerations, the update mechanism handles all details.

I encourage all users to update their Subversion Edge servers to this release so that you and your users can enjoy the new features brought from this release as well as the improved performance and fixes that comes with Subversion 1.7.  Look for updates to your favorite Subversion clients to follow shortly.

Source: http://blogs.collab.net/subversion/2011/10/subversion-1-7-0-released/

The post Apache Subversion 1.7 has Arrived | What’s new in Subversion 1.7 ? appeared first on scmGalaxy.

Perforce 2011.1 released 11/07/2011

Perforce Release 2011.1 is now available. Check for platform and component availability.

Source: http://www.perforce.com/aggregator/sources/2

The post Perforce New Version , Perforce 2011.1 released | Perforce 2011.1 Overview appeared first on scmGalaxy.

Stable CVS 1.11.23 has been released. Stable releases contain only bug fixes from previous versions of CVS. This version includes an efficiency fix that reduces checkouts of very old revisions from an O(n^2) operation to an O(n) one, as well as yet another Windows file time stamp handling fix (bug #22781), and some other minor fixes and efficiency improvements. We recommend this upgrade for all CVS clients and servers!

Please take a look at the NEWS file from the CVS source distribution and the CVS 1.11.23 manual for more information about the changes contained in this release.

CVS can be downloaded from the GNU download server within four hours of this announcement or one of the mirrors after 24 hours or so (make sure to check the ”’non-gnu”’ directory on the mirrors). (This release may be obtained from Savannah download server prior to appearing on the GNU download server, but please don’t use the already heavily loaded Savannah download server unless you have to.) For other ways to obtain CVS, please read How to get GNU Software.

URL: http://savannah.nongnu.org/projects/cvs

The post Stable CVS Version 1.11.23 Released, What’s new in Perforce CVS 2011.1, let’s find? appeared first on scmGalaxy.

What is POM
A Project Object Model or POM is the fundamental unit of work in Maven. It is an XML file that contains information about the project and configuration details used by Maven to build the project. It contains default values for most projects. Examples for this are the build directory, which is target; the source directory, which is src/main/java; the test source directory, which is src/main/test; and so on.
The POM was renamed from project.xml in Maven 1 to pom.xml in Maven 2. When executing a task or goal, Maven looks for the POM in the current directory. It reads the POM, gets the needed configuration information, then executes the goal.
Some of the configuration that can be specified in the POM are the project dependencies, the plugins or goals that can be executed, the build profiles, and so on. Other information such as the project version, description, developers, mailing lists and such can also be specified.

Super POM
The Super POM is Maven’s default POM. All POMs extend the Super POM unless explicitly set, meaning the configuration specified in the Super POM is inherited by the POMs you created for your projects. The snippet below is the Super POM for Maven 2.0.x.
The snippet below is the Super POM for Maven 2.0.x.
4.0.0
Maven Default Project

central
Maven Repository Switchboard
default
http://repo1.maven.org/maven2

false

central
Maven Plugin Repository
http://repo1.maven.org/maven2
default

false

never

target
target/classes
${artifactId}-${version}
target/test-classes
src/main/java
src/main/scripts
src/test/java

src/main/resources

src/test/resources

target/site
release-profile

performRelease

true
org.apache.maven.plugins
maven-source-plugin

attach-sources

jar

true
org.apache.maven.plugins
maven-javadoc-plugin

attach-javadocs

jar

true
org.apache.maven.plugins
maven-deploy-plugin

true

Minimal POM
The minimum requirement for a POM are the following:

• project root
• modelVersion – should be set to 4.0.0
• groupId – the id of the project’s group.
• artifactId – the id of the artifact (project)
• version – the version of the artifact under the specified group

Here’s an example:

  4.0.0

  com.mycompany.app

  my-app

  1

A POM requires that its groupId, artifactId, and version be configured. These three values form the project’s fully qualified artifact name. This is in the form of ::. As for the example above, its fully qualified artifact name is “com.mycompany.app:my-app:1”.
Every Maven project has a packaging type. If it is not specified in the POM, then the default value “jar” would be used.
Project inheritance
Elements in the POM that are merged are the following:

• dependencies
• developers and contributors
• plugin lists (including reports)
• plugin executions with matching ids
• plugin configuration
• resources

The Super POM is one example of project inheritance, however you can also introduce your own parent POMs by specifying the parent element in the POM, as demonstrated in the following examples.

The post Project Object Model – What is POM? appeared first on scmGalaxy.

Introduction to CVS

CVS is a version control system, an important component of Source Configuration Management (SCM). Using it, you can record the history of sources files, and documents. It fills a similar role to the free software RCS, PRCS, and Aegis packages.
CVS is a production quality system in wide use around the world, including many free software projects.
While CVS stores individual file history in the same format as RCS, it offers the following significant advantages over RCS:

• It can run scripts which you can supply to log CVS operations or enforce site-specific polices.
• Client/server CVS enables developers scattered by geography or slow modems to function as a single team. The version history is stored on a single central server and the client machines have a copy of all the files that the developers are working on. Therefore, the network between the client and the server must be up to perform CVS operations (such as checkins or updates) but need not be up to edit or manipulate the current versions of the files. Clients can perform all the same operations which are available locally.
• In cases where several developers or teams want to each maintain their own version of the files, because of geography and/or policy, CVS’s vendor branches can import a version from another team (even if they don’t use CVS), and then CVS can merge the changes from the vendor branch with the latest files if that is what is desired.
• Unreserved checkouts, allowing more than one developer to work on the same files at the same time.
• CVS provides a flexible modules database that provides a symbolic mapping of names to components of a larger software distribution. It applies names to collections of directories and files. A single command can manipulate the entire collection.
• CVS servers run on most unix variants, and clients for Windows NT/95, OS/2 and VMS are also available. CVS will also operate in what is sometimes called server mode against local repositories on Windows 95/NT.

The post Introduction to CVS | Know ABout CVS | Quick Start Guide appeared first on scmGalaxy.