Skip navigation
Toggle Sidebar

Project Documentation

Installation Instructions

  1. Download the latest plugin distribution from Project Downloads
  2. Stop your Hyperic server
  3. Put the gigaspaces-0.1.0.jar to $HYPERIC_HOME/hq-engine/server/default/deploy/hq.ear/hq-plugins/
  4. Start the server
  5. Ensure all your Gigaspaces instances are running otherwise HQ agents will not detect them. Ensure either GSM or Lookup service instance is running. The plugin uses JINI lookup infrastrucutre to find active GS instances.
  6. Stop your HQ Agents
  7. Ensure your HQ Agent use the same JVM version as your Gigaspaces product. HQ Agent is bundled with JRE 1.4 by default. So you either need to use Gigaspaces for JDK 1.4, or upgrade HQ Agent's JRE to 1.5.
  8. Ensure user account used to run HQ Agent has read permission on Gigaspaces home directory and subdirectories.
  9. Copy gigaspaces-0.1.0.jar to $HQ_AGENT_HOME/pdk/plugins
  10. Start HQ Agents
  11. In several minutes detected Gigaspaces instances will appear in autoinventory as Gigaspace 6.0 servers.

FAQ

Q: Why don't you have feature X? I need it.  

A: Just post an issue ticket to the JIRA. I'll implement the improvement ASAP. 

Q: Hyperic did not autodetected my GS instances! Why?

A: Ensure Gigaspaces instances are running. ))) 

A: Ensure Gigaspaces & HQ Agents use the same JVM version. The plugin loads GS classes during runtime discovery. So if this can not be done, auto-discovery fails.

A: Ensure IP multicast works properly on your machine.  

A: You have deleted previously discovered Gigaspaces servers. In order to make them reappear you must delete and rediscover their host platform.

Q: My services (GSCs, JVMs, Spaces, PUs) are not detected! What can I do? 

A:  It is a known issue for Microsoft Vista. I don't know exact cause of the problem, but this does not happen neither on Windows XP nor on Linux.

A: Did not you deleted the services before? If so, rediscover whole platform to get them back.

A: Actually, they are detected. But you need wait for too long. HQ Agents run runtime discovery on startup and once for each 15 minutes by default. So you can either restart agents to enforce runtime scan, or change agent's runtime discovery interval.

   Put the following line into $HQ_AGENT/agent.properties file:

# Run runtime discovery each minute
autoinventory.defaultScan.interval.millis=60000

   ATTENTION! Auto-discovery is not a zero cost operation. Don't make it happend to frequently. Especially, on CPU bound systems.

Adaptavist Theme Builder Powered by Atlassian Confluence