Getting Started with Open Manage Network Manager
This chapter describes how to install and start Open Manage Network Manager for basic network monitoring and management. For more detailed descriptions of all this software’s features, consult its other manuals (the Open Manage Network Manager Installation Guide, Synergy User Guide, Common Services Guide and Java Client User Guide) or the online help.
If you want to find something but are unsure about which manual it is in, you can search all text in the Acrobat files in a single directory. You can also click on the blue cross-references to go to the target destination of cross-references in Acrobat, however for such electronic cross-references to the other documents to work, they must be in the same directory. Cross-document links do not work between documents for different versions of this software, but may provide an approximate location to consult.
If you are sure your hardware, software and network is correct and just want to get started immediately, go to Getting Started.
The Open Manage Network Manager portal delivers powerful solutions to network problems, and, in addition to the Open Manage Network Manager technology documented in the following pages, Open Manage Network Manager offers the following capabilities:
• Message Boards, Blogs, Wikis
• Shared Calendars
• Enterprise Chat / Messaging
• RSS Feeds
• Tagging, Ratings, Comments
Because many capabilities are only indirectly related to Open Manage Network Manager’s operation, this guide does not cover them comprehensively. The section Server describes how to set up some of these features.
Suggested mini-troubleshooting steps:
1. Refresh the browser. If that doesn’t work,
2. Stop and start the web server and/or application server. Command lines for this:
startappserver / stopappserver
For Windows, to start the web server manager: oware\synergy\tomcat-X.X.X\bin\startsynergy. For Linux.
/etc/init.d/synergy start / /etc/init.d/synergy stop
3. Clear the browser’s cache (Firefox in particular loves persistent old pages), then refresh.
4. Stop and start the browser.
5. If all else fails: Reboot the host and re-start the application server, web server and browser.
When troubleshooting (or contacting technical support), you may find pertinent information in logs located in the following directories:
You can also run getlogs from a command line. The getlogs script packages relevant logs. This script creates a logs.jar file in the root installation directory, and moves any existing copy of logs.jar to oware\temp. logs.jar compresses all logs necessary for troubleshooting. Read the jar yourself, or forward this jar to technical support to help troubleshoot.
System requirements depend on how you use the application and the operational environment. Your specific network and devices may require something different from the recommendations for typical installations.
Generally, base the minimum configuration of any system on its expected peak load. Your installation should spend 95% of its time idle and 5% of its time trying to keep pace with the resource demands.