Difference between revisions of "DHN Installation:Post-installation configuration"
From Gcube Wiki
Manuelesimi (Talk | contribs) |
Manuelesimi (Talk | contribs) (→HNMService) |
||
| Line 1: | Line 1: | ||
| − | |||
== Configuration files == | == Configuration files == | ||
| Line 14: | Line 13: | ||
* ''DHNProfileUpdateIntervalInMillis'' | * ''DHNProfileUpdateIntervalInMillis'' | ||
** the DHN profile is updated accordingly to this interval. The interval is specified as milliseconds. | ** 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 [[DHN-coordinates|here]] | ||
| + | * | ||
== Scripts == | == Scripts == | ||
Scripts that have to be run that take care of post installation activities: | Scripts that have to be run that take care of post installation activities: | ||
Revision as of 09:12, 30 March 2007
Configuration files
Configuration files that have to be edited after the installation:
HNMService
JNDI file
The HNMService performs a 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
Scripts
Scripts that have to be run that take care of post installation activities:
