Figure out licensing.properties tsa.timezone discrepancy from server timezone

Due to TimeZone issue, sesummarization doesn't summarize data on the QA environment for the mentioned date.

1. Ran ./googlemcc.sh -c /var/local/tsa/config/GoogleMCCReport.emails.txt --split

2..Ran /sesummarize.sh -d3 -S3

3.Verify the database tmp, it doesn't show data.

select * from tmp.searchEngineActivitySummary201212

===============================
email sent to Jeph:

For clarity - when you run export TZ='America/New_York' that only changes the server time in the window you ran it. Once that window is closed, the server time goes back to its default (in this case UTC). If you open another window the TZ is the default.

Jeph, personally I've run into that issue many times on my local machine b/c it wasn't in Sydney time. QA never had to deal with it because their servers were set up in Sydney time. This is something we need to think about because we are going to have clients in multiple time zones. Also, I'd like to avoid bugs being opened because the app seemingly isn't working correctly when the real cause is a TZ discrepancy, like AML-916. It would be great if we could, when licensing.properties file is loaded, run export TZ with whatever TZ is in the properties file. Or maybe there is a better way to handle it.

From: Jennifer Clarke
Sent: Thursday, December 13, 2012 10:33 AM
To: Jeff Theroux
Cc: Caitlyn Duggan; Jeff Brown; Atul Sanagar; Gurpreet Singh; Anil Kumar Halmadgi
Subject: QA server time zone issue

Hi Jeff. The QA jboss server is in UTC, and that was causing problems running googlemcc, sesumm, and whsumm. Caitlyn had me change the server by running, ‘export TZ='America/New_York'’. I wanted to bring this up so it’s not an issue on prod.