Difference between revisions of "DHN Installation:Post-installation configuration"
Manuelesimi (Talk | contribs) (→Configuration files) |
Manuelesimi (Talk | contribs) (→Java WS Core: Log4J) |
||
| Line 20: | Line 20: | ||
# Display any warnings generated by our code | # Display any warnings generated by our code | ||
log4j.category.org.globus=INFO | log4j.category.org.globus=INFO | ||
| − | <pre> | + | </pre> |
| Line 29: | Line 29: | ||
log4j.category.org.diligentproject.common.profile.impl=DEBUG | log4j.category.org.diligentproject.common.profile.impl=DEBUG | ||
</pre> | </pre> | ||
| − | |||
=== HNMService === | === HNMService === | ||
Revision as of 09:28, 30 March 2007
Configuration files
Configuration files that have to be edited after the installation:
Java WS Core: Log4J
The Log4J output should be redirected on the file system in order to simplify the debugging of what is happening on the DHN and the exchange of such information. The following configuration should be insert in the $GLOBUS_LOCATION/container-log4j.properties file:
log4j.appender.A1=org.apache.log4j.RollingFileAppender
log4j.appender.A1.file=container.log
log4j.appender.A1.MaxFileSize=10000KB
# Keep ten backup file
log4j.appender.A1.MaxBackupIndex=100
# A1 uses PatternLayout.
log4j.appender.A1.layout=org.apache.log4j.PatternLayout
log4j.appender.A1.layout.ConversionPattern=%d{ISO8601} %-5p %c{2} [%t,%M:%L] %m%n
# Display any warnings generated by our code
log4j.category.org.globus=INFO
We initially suggest also to enable a DEBUG log level for the HNMService and the Profile Management Library. In order to do that, add the following lines to the same file:
log4j.category.org.diligentproject.keeperservice.hnm.impl=DEBUG log4j.category.org.diligentproject.common.profile.impl=DEBUG
HNMService
JNDI file
The HNMService performs JNDI lookups for some static configuration parameters. Its JNDI file is located in $GLOBUS_LOCATION/etc/org_diligentproject_keeperservice_hnm/jndi-config.xml
The global resource HNMServiceConfiguration groups the configuration parameters. The following ones have to be changed accordingly to the suggestion reported:
- DHNProfileUpdateIntervalInMillis
- the DHN profile is updated accordingly to this interval. The interval is specified as milliseconds.
- latitude + longitude
- these two coordinates are used to correctly locate the DHN on the Google Map visualized by the Monitoring Portlet. To discover which are the coordinates for the DILIGENT partner DHNs see here
- country: two letter code of the country (e.g. IT)
- location: a freetext placeholder (e.g. Pisa)
- localFileSystem
- the partition on your file system that you want to share with the hosted services
- DHNType
- allowed values here are: Dynamic, Static and SelfCleaning. A static DHN is not used as target for the dynamic deployment, while a SelfCleaning is automatically cleaned every night (used just for demos). The default value is Dynamic.
There are other parameters in the resource and they have to be left with their default values.
Scripts
Scripts that have to be run that take care of post installation activities:
