This guide contains advanced configuration information for system administrators working with the SweGrid Accounting System (SGAS). It provides references to information on procedures typically performed by system administrators, including installing, configuring, deploying, and testing the installation.

	Important
	This information is in addition to the basic Globus Toolkit prerequisite, overview, installation, security configuration instructions in the GT 4.0 System Administrator's Guide. Read through this guide before continuing!

Building from source is only needed if you need to modify or test the source code for some reason.

The source code is available in the same installer tar ball as the binaries, in the file sgas-4.0.1-src.tar.gz. To build from source, extract the files in that tar ball and run the make-dist script contained therein.

Source code is available via AFS. To retrieve the latest code set your CVSROOT environment variable to: /afs/pdc.kth.se/src/packages/SweGrid/SourceRepository. Then export the code by running the following command:

cvs export -D today accounting

If you don't have access to AFS you can also download a nightly checkout of the code from http://www.sgas.se/source/.

This information is in addition to the basic configuration instructions in the GT4.0 System Administrator's Guide.

The accounting system is an orthogonal component that complements an installation of (in particular) GRAM. Integration with WS GRAM is ongoing and not included in this tech preview.

At this point in time, detailed deployment and configuration information can be found at http://www.sgas.se/docs/SGASInstallConfig.pdf.

At this point in time, detailed deployment and configuration information can be found at http://www.sgas.se/docs/SGASInstallConfig.pdf.

A test suite for an SGAS installation is provided. To use it run:

build.sh run-test

after you have installed the system.

On Windows systems, use the build.bat script instead of build.sh.

Normal considerations in regards to deployment of Grids, Web Services and protection of GSI credentials apply. The bank should preferrably be deployed on a separate machine.

SGAS has been built using an asynchronous allocation/charge model, to minimize the impact on the job submission process and to avoid the possibility for deadlocks or stalls.

Detailed error messages, such as stack traces are not logged to the command line utility (sgas-admin) output but instead are written to an error log file. The default location of this file is ./sgas-admin.log. The location and other SGAS admin log properties can be changed in the file etc/sgas-client/sgas-admin-log4j.properties in the SGAS installation directory. The errors displayed in the command line tool share the same correlation id (CID) as the errors in the error log file.

If you encounter problems or need assistance, don't hesitate to send an email to [email protected].