OSG Accounting Services - Gratia

[mysqld]
datadir=VDT_LOCATION/vdt-app-data/mysql5/var
user=mysql
port=NNNNN
socket=VDT_LOCATION/vdt-app-data/mysql5/var/mysql.sock

key_buffer = 16M
max_allowed_packet = 1M
table_cache = 64
sort_buffer_size=512
net_buffer_length=8
read_buffer_size=256
read_rnd_buffer_size=512
myisam_sort_buffer_size = 8M

# Required for InnoDB
log-bin=mysql-bin
log_bin_trust_function_creators=1
innodb_buffer_pool_size = 16M
innodb_additional_mem_pool_size = 2M
# Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 5M
innodb_log_files_in_group = 2
innodb_log_buffer_size = 8M
innodb_file_per_table
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50
expire_logs_days = 7

[client]
port=49152
socket=VDT_LCOATION/vdt-app-data/mysql5/var/mysql.sock

Location of my.cnf file
Another consideration that should be taken into account is the location of the my.cnf file. It has been stored in the VDT_LOCATION/mysql5/var directory . The VDT_LOCATION/vdt-app-data/mysql5/var directory may be a more suitable location as any changes to the my.cnf for a local environment, may want to be carried forward when upgrades are performed.

Installation Notes

1. Untar the file under $VDT_LOCATION to populate ./tomcat/v55/gratia:
   tar xf gratia_services_v1.00.5.tar
2. If and only if it does not already exist, create and configure the DB schema:
   1. Create the empty database schema ( CREATE DATABASE `gratia`; )
   2. Create two users: one that has full control over the gratia schema from localhost and one that has only SELECT and EXECUTE privilege. We suggest using "gratia" and "reader" for the full-control and restricted users, respectively. We suggest using the mysql-administrator utility from the MySQL-GUI-tools package available from the mysql.com website. You'll probably need to run it from the MySQL server and connect to localhost as the DB user root to have the necessary privileges. First create the user, then add hosts. We recommend specifying IPs only (not DNS names). Use the tabs to find the schema privileges and use the selection mechanism to initiate the desired privileges for each user for each host. We recommend against having wild cards, especially for the root user. For the coomand-line mysql client, this would be something like:

      grant all on gratia.* to admin@localhost identified by 'pwd';
      grant select,execute on gratia.* to reader@localhost identified by 'pwd';
      

3. Modify ./tomcat/v55/gratia/service-configuration.properties to contain the correct database and user information you defined in the previous step, as well as the correct name for the Birt services:

     service.rmi.rmibind=//HOSTNAME:17000
     service.rmi.rmilookup=rmi://HOSTNAME:17000
     service.mysql.driver=com.mysql.jdbc.Driver
     service.open.connection=http://HOSTNAME:8880
     service.secure.connection=https://HOSTNAME:8443
     service.mysql.url=jdbc:mysql://DBHOSTNAME:DBPORT/gratia
     service.mysql.user=DBUSER
     service.mysql.password=DBPASSWORD
   
     service.reporting.user=reader
     service.reporting.password=reader
   
     service.reporting.engine.home=BIRT-HOME

   For the current release, BIRT-HOME should be birt-v20.

4. Modify the $VDT_LOCATION/tomcat/v55/gratia/post-install.sh making sure that it is mode 0700 and owned by the tomcat-executing user: the line requiring configuration reads:

   cat MAGIC_VDT_LOCATION/tomcat/v55/gratia/${proc} | mysql -B --force --unbuffered --user=root --password=ROOTPASS --host=localhost --port=PORT gratia
   

   ROOTPASS, PORT and MAGIC_VDT_LOCATION must all be substituted correctly for the command to work.

Starting and Stopping Gratia Services

For this version of gratia-services, you must start and stop the service by starting tomcat

• Start the service using Tomcat:
  service tomcat-55 start
• In contrast to previous versions, all schema updates are handled from within tomcat in the right order. However, post-install.sh must be configured properly to enable execution of those SQL fragments that require SUPER privilege (see above).

NOTE Database updates may take place during the initial deployment of the collector which may take some time, especially if the schema contains a large amount of data.

gratia_reporting_v1.00.5.tar

1. Deploy all .war files under Tomcat.

Download shortcuts

Current release

• v1.00.5 services.
• v1.00.5 reporting.

Older Releases

• v0.36: services, reporting.
• v0.34: services, reporting.

Backlinks

Child Topics

Immediate children of this topic include the following:

• GratiaProbePreRelease
• ProbeInstallation

Major Updates

-- JohnWeigand - 10 May 2008 - For v0.34 removed references to gratia-security web service. Added InnoDB? attributes for MySql

-- ChrisGreen - 12 Sep 2007 - Update to 0.27.5 for VDT to fix calendar image problems and one report.

-- ChrisGreen - 11 Sep 2007 - Update for major release 0.27.3 to VDT.

-- ChrisGreen - 14 Jun 2007 - Update for major release 0.24

-- ForrestChristian - 03 Jan 2007 (edits only for linking from ITB)

-- ChrisGreen - 11 Oct 2006

-- PenelopeConstanta - 30 Aug 2006