Company Products/Technology Services News/Events Support Spacer Contact Partners Customers
English    日本語
Products Photo

Product Documentation for Wireless Operations Center

Documentation Home for Wireless Operations Center > Wireless Operations Center Guide

Wireless Operations Center GuidePreviousNextIndex

 


Installing an Upgrade

Upgrading to Version 2.0

Prerequisites

Upgrading on Windows

Upgrading on Linux

Deploying via Java Web Start

Reverting to the Older Installation

Upgrading to Version 2.0

When upgrading Devicescape Wireless Operations Center 2.0:

  • No conversion of repository data is required.
  • The upgrade from 1.0 (or 1.1) to 2.0 must be done across the entire deployment, for the server and for all client machines.
  • Conductor 1.0 clients cannot connect to later servers, and 2.0 clients cannot connect to earlier servers.
  • We recommend you upgrade the repository server first, so that you can upgrade and test the client installs as you go. The upgrade may be done without un-installing the previous version.

Prerequisites

The upgrade may require that you:

  • Upgrade the Java runtime on some computers.
  • Operations Center 2.0 requires Java J2SE version 1.5 or better (sometimes called "5.0")
  • Conductor 1.0 and 1.1 require at least a J2SE 1.4.2 runtime.
  • On Linux systems, the directory /opt/devicescape/ contains a subdirectory (for example, ./opcenter_2_0) for each version of the product you have installed, and a master link which selects the current version (for example ./opcenter, a link to ./opcenter_2_0). The active version can be changed by changing the link.
  • On Windows systems, the product name change from Instant802 Conductor means that the new version can simply be installed beside the old.
  • For safety, when upgrading the repository server, you should first take a backup of your repository data. All repository data is stored in the repository directory, so all you can simply create a snapshot of all the content in that directory.

    • For instance, on Linux: 

    cd /var/instant802/repository 
    zip /tmp/repositories.zip -r .
  • The Configure... option of the Repository Administration tool can be used to see where exactly your server stores repositories.
    Note
    Operations Center 2.0 requires a more recent Java version than 1.1; before starting the Operations Center upgrade, you should download and install a Sun Java J2SE runtime, version 1.5.0_01 or better.

Upgrading on Windows

To upgrade Devicescape Wireless Operations Center on Windows, where the repository service was run, you must first remove the previous repository serviced daemon before installing Devicescape Wireless Operations Center 2.0. To do this:

  1. Uninstall the Windows Repository Service component of the Devicescape Wireless Operations Center package, using the Add&Remove Programs from the control panel.
  2. To complete the upgrade, simply run the installer OpCenter_2_0.msi in the usual way.

    3. The Windows software management system will carry out the upgrade.

Upgrading on Linux

You must have root user permissions to execute the commands to upgrade Devicescape Wireless Operations Center.

To upgrade Devicescape Wireless Operations Center on Linux:

  1. Insert the CD into your CD-ROM drive on your development host.
  2. Bring up a terminal command line shell in which to run the installation.
  3. Run the install script by typing opcenter_2_0.sh at the command line.

    4. This will populate /opt/devicescape/opcenter_2_0, and update the symbolic link /opt/devicescape/opcenter

    It will also check that the relative links are correct: 

    /usr/bin/opcenter -> /opt/devicescape/opcenter/bin/opcenter 
    /etc/init.d/opcenter -> /opt/devicescape/opcenter/bin/init_d

    If there are any unknown files they are untouched and a warning appears.

  4. If this occurs, restore the links as specified above, after saving your local variations.
  5. On the repository server host, customize the init.d script /etc/init.d/opcenter for your environment.
  6. Specify the appropriate value for JAVA_HOME.
  7. Repeat the configuration you were using with the previous version to:
    • Extend the available memory in VM_ARGS
    • Increase the available file descriptors in the limit command
  8. Edit the init.d script using the path /opt/devicescape/opcenter/bin/init_d to make the changes.

    9. Your init.d script from the previous installation is preserved in /opt/instant802/conductor_1_0/init_d. Consult it to find appropriate values.

  9. Restart the repository server by running:
    • /etc/init.d/conductor stop (if the old server is still running)
    • /etc/init.d/opcenter start

      • The new version will start up using the same password and Starting Repository settings as were configured for the old repository.

      Note
      On a client installation, after running the installer, no further work is needed.
      Users can run /usr/bin/opcenter dashboard to start the updated dashboard.

Deploying via Java Web Start

With Operations Center 2.0, you can deploy a Web-accessible version of the Dashboard by taking advantage of Java Web Start. Clients with Java Web Start support (such as Windows Explorer users who have installed the Sun Java runtime) will be able to launch the Dashboard without having it installed on their system.

The Getting Started section includes information on how to configure the HTTP service in the repository, and how to start the Dashboard using Java Web Start.

Reverting to the Older Installation

Reverting Installed Software to Previous Versions

On Windows:

  1. Uninstall the Devicescape Wireless Operations Center 2.0 package using the Add or Remove Programs control panel.
  2. Re-install the Conductor 1.0 package if you removed it.

On Linux:

Change the symbolic link in /opt/devicescape: 

rm /opt/devicescape/conductor 
ln -s /opt/instant802/conductor_1_0 /opt/instant802/conductor

Reverting the Repository Server

To revert to the old repository server:

  1. Stop the repository server /etc/init.d/opcenter stop
  2. Follow the instructions in Reverting Installed Software to Previous Versions above, to reactivate the old software.
  3. Restore your repository directories and files to the backup you made before installing the 2.0 system.
  4. Remove all the files and subdirectories from the repository directory, and restore them from the backup.

    5. Repositories that have been activated and monitored with the 2.0 system cannot be opened by older software.

  5. If you have no backup, you will need to create a new empty repository and repopulate it using discovery.
  6. Restart the server /etc/init.d/conductor start to resume network monitoring with the older software.
Wireless Operations Center GuidePreviousNextIndex