StoRM GridHTTPs configuration guide

Important

From StoRM v1.11.7 the GridHTTPs server is deprecated. Install and configure the storm-webdav service instead.

The EMI3 GridHTTPs is the component responsible to provide:

• HTTP(s) file-transfer capabilities: it’s possible to GET/PUT data via HTTP protocol but this is authorized only if a valid SRM prepare-to-get or SRM prepare-to-put has been successfully done before;
• a WebDAV interface to the StoRM endpoint that conceals the details of the SRM protocol and allows users to mount remote Grid storage as a volume on their own desktops;
• a mapping-service used by Backend that convert a real file path to a valid file-transfer URL.

YAIM configuration variables

All the GridHTTPs specific variables can be found in the following file:

  /opt/glite/yaim/examples/siteinfo/services/se_storm_gridhttps

Please copy it in your CONFDIR/services directory and edit as your needs. You have to set at least these mandatory variables:

• STORM_BACKEND_HOST

and check the other variables to evaluate if you like the default set or if you want to change those settings. Table 1 summaries YAIM variables for StoRM GridHTTPs component.

##Advanced service configuration

The GridHTTPs component relies on a single configuration file that contains all the configurable parameters. This file is:

/etc/storm/gridhttps-server/server.ini

containing a list of:

key = value

pairs that can be used to configure the GridHTTPs server. In case a parameter is modified, the GridHTTPs service has to be restarted in order to read the new value.

###server.ini

EMI3 StoRM GridHTTPs server no longer needs Tomcat, cause it is now a web component residing in an embedded Jetty server. About Jetty server and its connectors configuration you can manage the following variables:

GridHTTPs’ log file is configurable:

GridHTTPs interacts with StoRM Backend to configure itself in bootstrap phase, to check user’s authorization access to resources, to perform SRM operation, to set checksum value on a file, etc. So it needs to know information about BE location and ports:

GridHTTPs works with SURLs so it needs to know a valid SRM endpoint:

GridHTTPs manage file transfers and file creation. So it computes checksum during transfers. The computed checksum type is adler32. This capability can be disabled.

##GridHTTPs Logging

GridHTTPs’ log files are located in /var/log/storm/ directory. They are the followings:

• storm-gridhttps-server.log For managed requests This is the main log file of StoRM GridHTTPs. All the information about the WebDAV, HTTP file-transfer and mapping requests, error or warning are logged here depending on the log level. At the INFO level, the GridHTTPs logs, for each operation, who have request the operation (DN and FQANs if not anonymous), on which file(s) (SURLs) and the operation result. At DEBUG level, much more information are printed regarding the status of many StoRM internal component, depending on the request type. DEBUG level has to be used carefully only for troubleshooting operation. If ERROR or FATAL level are used, the only event logged in the file are due to error condition.

• storm-backend.stdout This file contains the standard out of the GridHTTPs process. Usually it does not contains any useful information.

• storm-backend.stderr This file contains the event logged as ERROR or FATAL conditions. This event logs are presents both in the storm-gridhttps-server.log file and here.

The logging level of these files can be specified editing the configuration file logback.xml located in /etc/storm/gridhttps-server/ directory modifying the level value of:

  <logger name="it.grid.storm" level="INFO">
    <appender-ref ref="PROCESS" />
  </logger>

The supported logging levels are: FATAL, ERROR, WARN, INFO, DEBUG and TRACE.

The suggest logging level for production endpoint is INFO. In case the log level is modified, there’s no need to restart GridHTTPs service.