|
Documentation Home for Wireless Operations Center > Wireless Operations Center Guide
Appendix A. Portable Installation
This appendix describes how to install the Operations Center software from the zip archive opcenter.zip. This can be done on any platform that supports Java 1.5.
Installing on Other Systems
What Gets Installed
Installing on Other Systems
To install Devicescape Wireless Operations Center on other Unix systems such as Solaris, HPUX, etc:
- Download or obtain the software (
opcenter.zip) and unzip it into your programs directory.
We recommend placing the software as follows:
For Unix: /opt/devicescape/opcenter/
- For Unix systems customizable startup scripts are found in the directory
./bin/ in the installation directory.
- To start the demonstration session, you can run:
sh <opcenter>/bin/demo.sh
where <opcenter> is the directory in which you have unpacked the software.
- The unix
.sh scripts expect two environment variables to be set:
OPCENTER_HOME (optional): The Path to the Operations Center Installation
The OPCENTER_HOME (optional) variable should be set in your environment to the full path of the directory into which you expanded the .zip archive.
If you placed the software in /opt/devicescape/opcenter there is no need to set this variable.
The scripts will fail, with messages, if this variable is not set correctly.
JAVA_HOME (required): The Path to the J2RE 1.5 Installation
The JAVA_HOME (required) variable must be set to the directory where you installed the JRE. This directory may resemble something such as:
/opt/jdkl.5.0_01/
The contents of the directory to refer to will include:
The scripts will fail, with messages, if this variable is not set correctly.
What Gets Installed
When you install Devicescape Wireless Operations Center a directory is created called "opcenter/" in the location you specify. The opcenter/ directory contains the following files:
Jar Files (lib/)
|
Directory
|
File
|
Description
|
|
lib/
|
dswoc.jar
|
Java package containing the Operations Center application.
The runnable Java Main class is
com.devicescape.repository.opcenter
Use the Windows batch files and UNIX shell scripts start dswoc.jar with various pre-configured client or server options.
|
| |
java-snmp.jar
|
SNMP protocol library
|
| |
activation.jar
mail.jar
|
Java libraries for mail and for Java Bean activation
|
Linux Shell Scripts for Starting the Application
The various applications and tools in the Devicescape Wireless Operations Center system are selected by supplying a mode argument to the Operations Center main class (/user/bin/opcenter.sh is the shell script that calls the Operations Center executable). Each mode argument can be followed by specific options applicable to that mode. There are four choices as shown below.
|
Scripts
|
Subcommands
|
Options
|
Description and Example
|
|
/usr/bin/opcenter
|
demo
|
-p or --port
|
Starts the Starts the standalone demo. For example:
user/bin/opcenter demo -s -x sample
starts the demo. If the -x option is included (as in above example) the monitoring subsystem will not be started as a part of running the demo.
|
|
admin
|
-h or --host
|
Starts the Repository Administration Tool. For example:
user/bin/opcenter admin -c -h bradfpc:1777
starts the Repository Administartion Tool at host "bradfpc" on port 1777
You can also use the following optional arguments for starting the Administration Tool:
- RepositoryName - The name of a repository to load directly upon launch, rather than waiting for a user request.
-days [Number] - Specifies the number of days worth of event history to download to the client when starting any of the client applications. |
|
dashboard
|
-c or --client
|
Starts the Dashboard running as a client. For example:
user/bin/opcenter dashboard -c -h bradfpc:1777
starts the Dashboard at host "bradfpc" on port 1777
|
|
/etc/init.d/opcenter
|
start
|
|
Starts the Repository Server. For example:
/etc/init.d/opcenter start
starts the server.
|
Internal Configuration Files (registry/)
The registry directory contains software configuration files. It also contains activation key files.
Documentation Files (docs/)
|
File or Directory
|
File or Directory
|
Description
|
|
docs/
|
help/
pdf/
|
The docs/ directory contains HTML and related files for the Online Help (docs/help) and PDF of the Online Help in "book" form (docs/pdf/opcenter.pdf)
If you are using a Microsoft Internet Explorer (IE) Web browser Version 6.x, the file docs/help/opcenterWW.chm should display properly in your IE Web browser. This gives you a three-pane Online Help window with Search capabilities and a TOC that lets you show/hide subtopics.
If you are using any other browser (for example, Netscape or Mozilla), open the file docs/help/getstart.help.html in a Web browser to view the Online Help. (This is the file that it is called from the Help > Overview menu item on the Operations Center UI.)
For more information about the capabilities and limitations of the Online Help, see About This Document.
|
Sample Files for the Demo Network Model (repository/sample/)
|
Directory
|
File
|
Description
|
|
repository/sample/
|
|
Directory containing a sample network description.
When you start and save new network surveys, a similar directory will be created with the name and path location you specify when you save it. (For example, C:lab/my_lab_network/)
|
| |
network.txt
|
Text file containing a full description of the network surveyed. The network.txt file lists the set of devices discovered and their SNMP attributes ( MAC address, IP Address, and MIB information) as well as Operations Center settings applied to the devices (such as location on the layout map or groupings).
|
| |
floorplan.jpg
|
Underlay graphic of a floor plan used as a location map for positioning devices in the layout.
|
| |
snap<Date>.txt
|
|
| |
log<Date>.txt
|
Several log files containing the recorded event history on the devices discovered so far. The log files are named by date; for example,
log-20031024-00.txt.
In the sample, the logs are a static set of files. For a live network where monitoring is continuous or resumed on a daily basis, new log files are added to storage automatically as new events are logged.
On the Operations Center UI, these messages are shown in the History "Event Table" and also contribute information used to represent the overall network model shown on the Dashboard.
|
| |
dat-<Date>00.txt
|
Several text files containing data about changes to managed variables ( MIB data). The data files are named by date; for example, dat-20031024-00.txt.
In the sample, the data files are a static set of files. For a live network where monitoring is continuous or resumed on a daily basis, new data files are added to storage automatically to reflect the current values of managed variables (which change continuously based on such factors as traffic flow through the access points).
On the Operations Center UI, this data is surfaced in the History graphs and MIB settings (Tools > Settings), and also contributes information used to represent the overall network model shown on the Dashboard.
|
Source Code for SNMP Protocol Library (src/)
|
Directory
|
File
|
Description
|
|
src/
|
java-snmp.zip
|
Zip file containing the source code for the SNMP protocol library. To work with the source code, extract the files from the zip.
|
| 
