These steps are detailing a Joomla 1.5.17 install onto a dedicated Centos 6.3 linux web server connecting to a Microsoft Exchange Server to send SMTP email.

You may have to use sudo or sudo -u root depending on how your server is setup to execute many of these commands.

Is sendmail installed?  Is it the latest version?

• Get sendmail installed

Check what version of Sendmail is installed on your box

 rpm –qa sendmail

Update to the most recent version.

 sudo yum install sendmail

You may also need this to create your cf file

sudo  yum install sendmail-cf

• Get sendmail running

You may have to shut down postfix because you can’t have sendmail and postfix running at the same time

sudo  /etc/rc.d/init.d/postfix stop

Or

sudo service postfix stop

Next you should make sure that the sendmail service is running

sudo service sendmail restart

Then check it’s status

sudo service sendmail status

You want to see something like this:

sendmail (pid  15687) is running…

sm-client (pid  15696) is running…

Make sure sendmail starts up if your restart your box

sudo chkconfig sendmail on

Are your Configuration Settings Correct?

• /etc/mail/sendmail.mc

Replace this line in sendmail.mc

DAEMON_OPTIONS(`Port=smtp, Addr=127.0.0.1 Name=MTA’)dnl

with

DAEMON_OPTIONS(`Port=smtp, Name=MTA’)dnl

You may have to define this host as well:

define(`SMART_HOST', `yourSMTPserverDomain')dnl

Save the file and restart sendmail again

Can Httpd send emails?

Check your email settings here:

getsebool -a | grep mail

if httpd_can_sendmail is off then you will have to run this command to turn it on.  It will take a minute so just wait.

sudo -u root setsebool -P httpd_can_sendmail on

Restart sendmail again and make sure it’s running.

• Try sending a test email:

/usr/sbin/sendmail youremail@gmail.com

-> Press Enter

Type:  ”Subject: test”

-> Press Enter

Type ‘.’

-> Then press enter again

Setup you Server in the Joomla back end Admin Console

Site -> Global Configuration -> Server

• Try sending a test email through the  Joomla back end admin console:

Then you can send a test email using:  Tools -> Mass Mail.

Other problems?

Having trouble finding files?

Use this command to find files:

find / -name 'filename'

If you have any other problems check the mail logs:

sudo tail -f /var/log/maillog

Jasper does not offer the ability to drill down on data. But, what is possible is to have a summary report which can be blown up using a hyperlink to a detailed report. For simplicity let’s call the Summary report as ‘Main report’ and Detailed report as ‘Subreport’.

Steps for the Main Report

• Identify an element (Header label etc.) in the main (Summary) report that you would want to create a hyperlink on.

• Right click on hyperlink and follow as below:

Hyperlink Target = Self                            Hyperlink Type = ReportExecution

• Add two parameters, first one would have the report path

_report : “/reports/samples/ClientAddress”  (Double quotes are important)

• The second parameter will be the parameter defined in second report

ClientID : $F{Client_ClientId}

Step for the Sub Report

• This report will have a parameter called ClientID

Save both the reports in Repository and run the first one. Click on the link and it would take you to the second report.

That is, by and large, the general understanding people have about what a BI solution basically does. So what can’t it do? When data is aggregated, analyzed, and reports are churned out, there is a considerable portion of time spent on doing quality check on the data reported. But there is a catch. What happens to the garbage that is already in the data? Yes, we are talking about the age-old garbage in, garbage out principle. The quality check can very well unearth these anomalies in the data but when they come from the source, i.e., from the point of data-feed, there isn’t much that the BI tool/person can do at the report writing stage to fix those errors. This is especially true in those cases where database providers are separate from the BI team that works with the data.

Needless to say, errors like that can be costly. Imagine a case of wrong billing which invariably leads to uncollected receivable. Now imagine a few hundred, or may be thousands of cases like that. The losses, when they pile up, are significant. A 2002 study conducted by The Data Warehousing Institute (TDWI) estimated that poor quality customer data costs U.S. businesses a massive $611 billion a year. More recently, Ovum published a research paper where they estimate the total cost of bad data quality in US to be $700 billion – a sizable 30% of their revenues.

However, the good news is that this is a problem that is clearly solvable. Maintaining rigorous data quality is entirely possible, as long as the key decision-makers in a company recognize how crucial this task is and therefore treat it as a project in its own right. It calls for a well thought-out strategy. Here are a few steps we recommend from our experience to tackle the data quality beast:

1. Recognize that it is not entirely up to the IT department or BI vendor to fix these errors. The often cited barrier to improving data quality is lack of commitment to the cause by key decision makers in the company. Almost half of the 647 survey respondents in TDWI’s Data Quality survey had no plans for improving their data quality. It takes a strong and willing collaboration between all the users of data – the business users, the data analysts or report writers and the IT department/database provider.
2. Decide on a workable method to eliminate errors. The business users and BI analysts can work together to come out with reports that alert erroneous data feed as soon as they happen. At the same time, they need to bring these error prone entries to the attention of the data-feed application providers (if different from the BI guys), so that they can embed checks and balances in the application to prevent incorrect entries. We followed this approach with one of our clients, spending a considerable chunk of our time in identifying areas that require data validation and building reports to support the validation process. Within weeks, our client was able to recoup over a million $ worth of receivables.
3. Define a formal process for this task and define the scope of the project. Build a list of error-prone areas and set timelines to correct each of these issues. It is important to recognize that this is an evolving process and therefore the timelines set must be realistic.
4. Transparency is key. Everyone needs to be on the same page about ongoing progress on the project.
5. A lot of data quality problems arise out of training issues and this must be duly noted and acted upon by the concerned managers in the organization.

A solid investment in a formal approach like this will eliminate the pain points for all the parties involved. More importantly, it leads to sizable long-term financial savings for the company that may be used to seeing a lot of money go down the drain due to data quality issues. But the most beneficial outcome of this is that it gradually leads people to gain faith in the data at their disposal so that the decision-making process is not unduly hindered by lack of reliable information.

I hope someone will find this link very helpful – http://mohammadthalif.wordpress.com/2011/10/08/how-to-install-java-sun-jdk-in-centos-6-2/

The most important command was : # update-alternatives – -config java
So, if your server has openjdk or any other jdk version, you need to run the update to get sun(oracle) JDK effective.

Happy installing

Jyot

We are using:

Grails 1.3.7

STS 2.5

Go into your project’s BuildConfig.groovy

/[Your_Project_Name]/grails-app/conf/BuildConfig.groovy

Find the repositiories section:

repositories { grailsPlugins() grailsHome() grailsCentral()

// uncomment the below to enable remote dependency resolution
// from public Maven repositories
//mavenLocal()
mavenCentral()
//mavenRepo "http://snapshots.repository.codehaus.org"
//mavenRepo "http://repository.codehaus.org"
//mavenRepo "http://download.java.net/maven/2/"
//mavenRepo "http://repository.jboss.com/maven2/"

}

Search for mavenCentral().
Uncomment this line out. This will then enable remote dependency resolution.

Then try the install-plugin command on the command line.

Here is an example:

install-plugin mail

or

install-plugin http://plugins.grails.org/grails-mail/tags/RELEASE_1_0-SNAPSHOT/grails-mail-1.0-SNAPSHOT.zip 

If running install-plugin on the command line does not work for you, you can try the plugin manager.

Right-click your project -> Grails Tools(Towards the bottom) -> Grails Plugin Manager.

Search for your plugin then install and click the OK button.

http://stackoverflow.com/questions/7905714/grails-install-plugin-does-not-work-for-me/7921928#7921928

The Groovy script I had authored seemed simple and straightforward to me.  I logged in, cd’d to its location on the server, typed the name of the script, and hit enter.

Six hours later, the prompt returned.

You can imagine I was not a happy camper, constantly executing queries on the database to answer the question: “Is it really doing anything? Is it hung?”
Row by row the data was deposited.  Six long hours later, I wearily logged off and crawled into bed just as the sun began to peek over the horizon.
I did not want to repeat this. 
So, I did a little research.  Hopefully what I learned can help others avoid this very costly oversight.

Enter Groovy’s  batchUpdate feature.  Perhaps I’m just a little late to this party, but from a novice’s perspective, Approach 1 (see listing) seems perfectly reasonable: for each row in one table, insert the data into another table.

Approach 1: “Brute Force”


// This took more than 6 Hours

mssql.withTransaction

{

cachesql.eachRow(”select * from HDL.TransactionJournal where TransactionDate between ‘2010-08-01′ and ‘2011-08-01′ “)

{ row ->

mssql.execute(”insert into[dbo].TransactionJournal (ID, TransactionDate,TxCode,TxType) values (?,?,?,?)”, [row.ID,row.TransactionDate, row.TxCode,row.TxType])

}

}

After running this script and painstakingly monitoring its progress overnight, I embarked on a quest to determine the better way to do this.  After a bit of searching, I discovered Groovy’s batchUpdate. 

I quickly rewrote my script, and the same data transfer took 3 minutes.  That’s right – from 360 minutes to 3.  How’s that for two orders of magnitude’s difference?

The concept is this: do a mass insert, and commit every x number of rows, instead of inserting and committing each row singly.  The higher you set the parameter for committing, the faster it will run.

Approach 2: Same Data Shuffling, Much Faster Performance

// This took 3 mins

mssql.withTransaction

{

//it commits after each 10K insert

def updateCounts = mssql.withBatch(10000, “insert into[dbo].TransactionJournal (ID,TransactionDate,TxCode,TxType) values (?,?,?,?)”,

[row.ID,,row.TransactionDate, row.TxCode,row.TxType]“)

{ ps ->

cachesql.eachRow(”select * from dbo.TransactionJournal where TransactionDate between ‘2010-08-01′ and ‘2011-08-01′ “)

{ row ->

ps.addBatch([row.ID,row.TransactionDate, row.TxCode, row.TxType])

}

}

}

The underlying lesson learned here is a fairly standard one, which is, when doing something that looks like batch processing in a database, make sure to use batch processing (within a transaction) to ensure optimal performance. 

Groovy’s batch processing feature was introduced in November 2010 with the release of 1.7, so anyone who picked up Groovy prior to that (like myself) may be accustomed to working around this previously missing feature.

Hopefully this article will help others avoid the mistake of quickly whipping up a script like this – only to sit and watch it execute, not-so-quickly.

First step: Keywords

- Whether you have had your site for awhile or are just starting, finding relevant and significant keywords is important.

- Keywords should produce high value and high volume, but they should not be difficult. If your keyword that is used often with a lot of competition, that keyword will not help you as much as needed. Still use it, but look for other closely related keywords with less difficulty.

Second step: On-page Optimization

- Images should have image names describing the image itself. The images used should be relevant to the site and also be almost descriptions of your keywords themselves.

- If using wordpress (or any blog), make titles and headings using your keywords.

- Do not use title tags too much. Most search engines look down upon repetitive keywords and bring down your ranking.

Third step: Links

- Links that are used in tweets are significant for SEO.

- Use shortening twitter tools for links (bit.ly, etc) and customize the link to have your keywords in shortened link.

- Use keywords in tweets and posts for all social media.

- Use a link tracking site (opesiteexplorer.com) to see popular competition’s backlinks and attempt to get involved with some of those links as well.

- Use Google Analytics  to see any errors on your site. If these crawl errors are overlooked, it could affect the traffic to your site.

- Use canonical URL tags for your pages. These will help  search engines to link all duplicated content to the original page and link.

//Added the code to prevent the users navigating away.

Window.addWindowClosingHandler(new Window.ClosingHandler() {

public void onWindowClosing(Window.ClosingEvent closingEvent) {

closingEvent.setMessage(”Do you really want to leave the page?”);

}

});

Start up the Local Server

• Click Start -> Microsoft SQL Server 2008 R2 -> SQL Server Configuration Manager
• Set the SQL Server(SQLEXPRESS) and SQL Server Browser to automatic start mode.
• Right click -> Properties -> Service Tab

SQL Server 2008 Server Settings

Login to Local Server

• Now open up SQL Server Management Studio and Connect to Object Explorer and select Server Name: [Your PC name]\SQLEXPRESS
• Example:  8540P-KL\SQLEXPRESS
• To find your PC name:  Right click My Computer -> Properties -> Computer Name tab
• Login using windows authentication:  Using the user name [Your Domain]/[Your User Name]

SQL Server 2008 Login Settings

Setup User Account

• In SQL Mgmt Studio -> Expand your local Server -> Security -> Right click on Logins -> New Login

• Uncheck Enforce password policy, password expiration and user must change pw(Since this is local)

• Default database -> Your Database

• User Mapping Page -> Map to your db and grant db_owner role

• Status Page -> Grant Permission to connect and Enable Login

SQL Server 2008 User Settings Local DB

Setup Access Permissions/Settings for User

• Right click your Local Server -> Properties -> Security Tab -> Enable SQL Server and Windows Authentication Mode

• Open SQL Server Configuration Manager -> SQL Server Network Configuration -> Protocols for SQLEXPRESS -> Enable TCP/IP

SQL Server 2008 Server Permissions

Database Properties File for Spring Project

• database.url=jdbc:jtds:sqlserver://[local PC Computer name];instance=SQLEXPRESS;DatabaseName=[db name];

• database.username=[Your user name]

• database.password=[Your password]

• database.driverClassName=net.sourceforge.jtds.jdbc.Driver

Thank you and feel free to post any additional questions below.

–

Chris Anatalio