Hydra Server: Operation

Starting & Stopping the Service

The Hydra service is controlled through the standard Tomcat scripts.
service tomcat5 [stop|start|restart|status]
There are no other controls necessary. All the standard Tomcat options may be used and references found in the standard locations.

Service Information

Service Endpoints

A Hydra service presents a number of service endpoints. A Hydra service configured to have three key stores on a machine called "example01.net" will expose:

Logging and Logs

A Hydra service logs information to several places.

The tomcat-specific logging is sent to the standard log files:

The keystore-specfic logging is sent to:
Where "n" is the keystore instance.

The trustmanager Authentication logging is sent to:

Logging levels

The logging levels may be set for the tomcat logging in the standard manner. This is not part of Hydra and is not discussed here.

The keystore-specific logging levels are set in the file:
Where "n" is the keystore instance. A restart of the overall Hydra service is needed to effect the changes.

The trustmanager authentication-specific logging levels are set in the file:
A restart of the overall Hydra service is needed to effect the changes.

The logging syntax follows the standard log4j style.

-- JohnWhite - 06-Jul-2012

This topic: EMI > WebHome > EmiProjectStructure > EmiProductTeams > GLiteSecurity > EMIHydraDocumentation > HydraServerOperation
Topic revision: r2 - 2012-07-09 - JohnWhite
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback