Support/MetricsDashboardPRD/Setup - Revision history

Kelimutu: category -> Support Archive

2021-07-14T09:21:30Z

category -> Support Archive

← Older revision		Revision as of 09:21, 14 July 2021
Line 15:		Line 15:
	# Run /path/to/pentaho/data-integration/kettle.sh -norep -file j_sumo_etl.kjb and make sure it has no errors		# Run /path/to/pentaho/data-integration/kettle.sh -norep -file j_sumo_etl.kjb and make sure it has no errors
	# Cronjob above to run nightly at 4 AM (or whenever.)		# Cronjob above to run nightly at 4 AM (or whenever.)

			[[Category:Support Archive]]
			c

Cww at 17:08, 26 May 2009

2009-05-26T17:08:17Z

← Older revision		Revision as of 17:08, 26 May 2009
Line 1:		Line 1:
	Here's the way that the metrics dashboard works ~~and how to get it set up on (staging/production)~~:		Here's the way that the metrics dashboard works:

	* The scripts (which populate the metrics dashboard) are run using pentaho http://sourceforge.net/project/showfiles.php?group_id=140317&package_id=186321&release_id=682677 which runs on java (must be 1.6 or higher, I think)		* The scripts (which populate the metrics dashboard) are run using pentaho http://sourceforge.net/project/showfiles.php?group_id=140317&package_id=186321&release_id=682677 which runs on java (must be 1.6 or higher, I think)
			* scripts are .kjb and .ktr files (XML files) can be checked out into any directory and then run (using a cron job or manually by doing /path/to/pentaho/data-integration/kettle.sh -norep -file j_sumo_etl.kjb ) where j_sumo_etl.kjb is the name of the parent job file (which then links to the rest.)
			* A ~/.kettle/kettle.properties file (in the home directory) specifies parameters such as database names and logins and passwords (I think this is plaintext) specific to the server. This is not in SVN but will need to be generated manually first time.
			* Table are also not created automatically by the scripts and will have to be created first time using a few scripted SQL commands. The dashboard uses its own database, not just its own tables.

	* scripts are .kjb and .ktr files (XML files) can be checked out into any directory and then run (using a cron job or manually by doing /path/to/pentaho/data-integration/kettle.sh -norep -file mainJob.kjb ) where mainJob.kjb is the name of the parent job file (which then links to the rest.)		So setup tasks:

	* A ~/.kettle/kettle.properties file (in the home directory) specifies parameters such as database names and logins and passwords (I think this is plaintext) specific to the server. This is not in SVN but will need to be generated manually first time.

	* Table are also not created automatically by the ~~scripts~~ and ~~will have~~ to ~~be created first time using a few scripted SQL commands~~.		# Install pentaho and Java 1.6 or higher
			# Check out /projects/sumo/metrics (or some other TBD directory)
			# Create database with appropriate permissions
			# Create tables
			# Create ~/.kettle/kettle.properties specific to the server
			# Run /path/to/pentaho/data-integration/kettle.sh -norep -file j_sumo_etl.kjb and make sure it has no errors
			# Cronjob above to run nightly at 4 AM (or whenever.)

Cww: Created page with 'Here's the way that the metrics dashboard works and how to get it set up on (staging/production): * The scripts (which populate the metrics dashboard) are run using pentaho http...'

2009-05-26T17:02:34Z

Created page with 'Here's the way that the metrics dashboard works and how to get it set up on (staging/production): * The scripts (which populate the metrics dashboard) are run using pentaho http...'

New page

Here's the way that the metrics dashboard works and how to get it set up on (staging/production):

* The scripts (which populate the metrics dashboard) are run using pentaho http://sourceforge.net/project/showfiles.php?group_id=140317&package_id=186321&release_id=682677 which runs on java (must be 1.6 or higher, I think)

* scripts are .kjb and .ktr files (XML files) can be checked out into any directory and then run (using a cron job or manually by doing /path/to/pentaho/data-integration/kettle.sh -norep -file mainJob.kjb ) where mainJob.kjb is the name of the parent job file (which then links to the rest.)

* A ~/.kettle/kettle.properties file (in the home directory) specifies parameters such as database names and logins and passwords (I think this is plaintext) specific to the server. This is not in SVN but will need to be generated manually first time.

* Table are also not created automatically by the scripts and will have to be created first time using a few scripted SQL commands.