Cambium Wireless Manager Client Setup Guide: System Release 4.2 and Later

Cambium
Wireless
Manager
Client Setup
Guide
System Release
4.2 and Later
Issue 1 November 2014

© 2014 Cambium Networks. All Rights Reserved.
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Cambium Networks assumes
no liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained
herein. Cambium reserves the right to make changes to any products described herein to improve reliability,
function, or design, and reserves the right to revise this document and to make changes from time to time in
content hereof with no obligation to notify any person of revisions or changes. Cambium does not assume any
liability arising out of the application or use of any product, software, or circuit described herein; neither does it
convey license under its patent rights or the rights of others. It is possible that this publication may contain
references to, or information about Cambium products (machines and programs), programming, or services that
are not announced in your country. Such references or information must not be construed to mean that Cambium
intends to announce such Cambium products, programming, or services in your country.
Copyrights
This document, Cambium products, and 3rd Party Software products described in this document may include or
describe copyrighted Cambium and other 3rd Party supplied computer programs stored in semiconductor
memories or other media. Laws in the United States and other countries preserve for Cambium, its licensors, and
other 3rd Party supplied software certain exclusive rights for copyrighted material, including the exclusive right to
copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly, any
copyrighted material of Cambium, its licensors, or the 3rd Party software supplied material contained in the
Cambium products described in this document may not be copied, reproduced, reverse engineered, distributed,
merged or modified in any manner without the express written permission of Cambium. Furthermore, the
purchase of Cambium products shall not be deemed to grant either directly or by implication, estoppel, or
otherwise, any license under the copyrights, patents or patent applications of Cambium or other 3rd Party supplied
software, except for the normal non‐exclusive, royalty free license to use that arises by operation of law in the sale
of a product.
Restrictions
Software and documentation are copyrighted materials. Making unauthorized copies is prohibited by law. No part
of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or
translated into any language or computer language, in any form or by any means, without prior written permission
of Cambium.
License Agreements
The software described in this document is the property of Cambium and its licensors. It is furnished by express
license agreement only and may be used only in accordance with the terms of such an agreement. See the legal
information and license agreement section of the user guide.

© 2014 Cambium Networks, Inc. All Rights Reserved.
Table of Contents
Accuracy...................................................................................................................................... 2
Copyrights ................................................................................................................................... 2
Restrictions ................................................................................................................................. 2
License Agreements.................................................................................................................... 2
1 About this Guide............................................................................................ 5
2 Wireless Manager Client Requirements.............................................................. 7
3 Configuring Proxy and File Association .............................................................. 9
3.1 Installing Java Virtual Machine ....................................................................................... 9
3.2 Configuring the Proxy on a WM Client ........................................................................... 9
3.3 Setting Proxy Information in the Java Control Panel.................................................... 10
3.4 Configuring jnlp File Association in Windows............................................................... 11
3.5 Set the Proxy Information in the Web Browser ........................................................... 14
4 Launching the WM Client ...............................................................................17
5 Troubleshooting the WM Client Launch ...........................................................21
5.1 Java Web Start is not installed in this machine. Please download Web Start. ............ 21
5.2 Launch of a Second Client on Same Machine Hangs at 20% ........................................ 24
5.3 The Operating System Does Not Recognize the jnlp File Type..................................... 25
5.4 Java exception: Missing required Permissions manifest attribute in main jar ............ 25
5.5 Transport Exception when communicating with server............................................... 26
5.6 Unable to launch the application ................................................................................. 27
5.7 JRE Will Not Install or Settings Are Not Accepted in Windows .................................... 30
Resources for Support ..........................................................................................31
Community Forum .................................................................................................................... 31
Technical Support ..................................................................................................................... 31
WM Release 4.2 and Later Issue 1
Client Setup Guide November 2014
1 About this Guide

This document is intended for network operators as they select a device on which to use the Wireless
Manager client application and appropriately configure it for that use. It assumes that the operator
 has already used the server selection and setup guide to deploy an appropriate server device
and the WM distribution tool to
− successfully install the software components
− assure that WM can access those through several accounts that the operator has
configured during the installation process.
 will be using the quick start guide after this to discover devices on the network and preview
WM basic functions.
Also, an FAQ addresses common questions that include the upgrade paths. All of these documents
can be found at http://www.cambiumnetworks.com/support/management‐tools/wireless‐manager/.
5
2 Wireless Manager Client Requirements

Wireless Manager is a client‐server application that uses a java thick‐client connection. The client
device is subject to the following hardware requirements:
Requirement type Supported
hardware class any modern desktop or laptop
storage 15 MB
link speed 1 Mbps
screen resolution 1024 x 768

The client device is also subject to the following software requirements:
Requirement type Software and version
operating system1 Windows 12
Windows 8
Windows 7 Professional
Windows Server 2008 R2 Enterprise
Red Hat Enterprise Linux 5.5 ES
Red Hat Enterprise Linux 6.x ES
browser If the client is on a If the client is on a

Linux OS device: Windows OS device:
◦ Mozilla Firefox ◦ Internet Explorer 6, 7, or 8
◦ Google Chrome
◦ Mozilla Firefox

Java 32‐bit JVM 1.6 or later2
NOTES:
1. MacOS is not supported. The following additional OSs are expected to
work but have not been tested with the client application:
 Windows versions other than those shown above
 CentOS 5.5 or 6.x
2. Use of an earlier JVM version can result in an OutOfMemory error.
7
3 Configuring Proxy and File Association

3.1 Installing Java Virtual Machine
Visit
http://www.oracle.com/technetwork/java/javase/downloads/java‐se‐jre‐7‐download‐432155.html
and download the 32‐bit (x86) version of Java Runtime Environment (JRE) appropriate for your
operating system. Install this software into the default directory that its distribution tool
recommends.
3.2 Configuring the Proxy on a WM Client

If the WM client does not need a proxy server to reach the Internet, this section may be skipped
entirely. If a Proxy Server is used to access the Internet, there are a few issues that must be
addressed before both client/server connection and the physical map in the client application can
properly operate. One of the following cases applies:
 Case 1, where the client and server are on separate machines
 Case 2, where server and client are on the same machine
After installation, Case 2 applies to most operators, as they will want to try to run the client on the
same machine as the server. This means that all these instructions must be followed, as the machine
is performing both client and server duties.
If a proxy is needed for Internet connectivity, this information must be entered in both the Java
Control Panel and the web browser.
9
Issue 1 WM Release 4.2 and Later
November 2014 Client Setup Guide
3.3 Setting Proxy Information in the Java Control Panel

Launch the Java Control Panel:
Windows ‐ StartSettingsControl PanelJava
Linux ‐ /usr/local/cambium/wm/jre/bin/jcontrol
Click Network Settings from the General tab.
Select Use proxy server and enter your proxy
information (what is shown is only an
example).
Often, you will need to specify that the proxy
not be used for local addresses, of which the
WM Server might be.
Check Bypass proxy server for local
addresses, then click Advanced.
10
Enter the IP address or IP mask that will match
the address(es) on your server. Your network
administrator will be able to help you with
this.
Remember this must be followed for each
client machine where a proxy will be used.
3.4 Configuring jnlp File Association in Windows

If you are configuring the server device to also be a client device
1. explore to the folder C:\Cambium\WM\server\conf.
2. right‐click the file WebNMS.jnlp.
3. select Open WithChoose Program.
4. tap or click Program Files (x86) or, if that folder is not present, Program Files.
5. select the Java folder.
6. select the latest JRE folder (for example, JRE7 if JRE6 and JRE7 are present).
7. select the bin folder.
8. highlight javaws.exe.
9. press or click Open.
If the client device is operating on Windows 8 or Windows 7 and is not also the server device, use the
remainder of this section for guidance on how to ensure that it calls the correct application to open
jnlp files. Perform the following steps:
1. If the client device is operating on Windows 8, perform the following steps:
a. Either
 swipe from the right edge of the screen, then tap Search.
 point your mouse cursor to the upper right corner of the screen, then move it down
and click Search.
b. Either
 in the text box, type Default Programs.
 tap or click Apps, then tap or click Default Programs.
11
If the client device is operating on Windows 7, perform the following steps:
a. Click Start.
b. In the search bar, enter Default Programs.
c. Click Associate a file type or protocol with a program.
2. In the list of registered file types that opens, tap or click to highlight the .jnlp line.
3. Click the Change program button.
4. In the list of programs
a. tap or click More options or Browse.
b. under Computer in the left panel, tap or double‐click Local Disk (C:).
c. tap or click Program Files (x86) or, if that folder is not present, Program Files.
d. select the Java folder.
e. select the latest JRE folder (for example, JRE7 if JRE6 and JRE7 are present).
f. select the bin folder.
12
g. Highlight javaws.exe.
h. Press or click Open.
Java Web Start will now open jnlp files.
If you want the jnlp file to automatically open and your browser is
 Mozilla Firefox, perform the following steps:
1. Open WM server launch web page in Firefox.
2. Click the Launch WM Client button to start the jnlp file download.
3. Check the check box for Do this automatically for files like this from now on as shown
below:
4. Click OK to launch the WM Client .
 Google Chrome, perform the following steps:
1. Open the WM server launch web page in Chrome.
2. Click the Launch WM Client button to start the jnlp file download.
3. When prompted with the warning This type of file can harm your
computer. Do you want to keep WebNMS.jnlp anyway?, click the
Keep button.
4. Click to check the Always open files of this type option as shown below:
5. Click WebNMS.jnlp to launch the WM client .
13
3.5 Set the Proxy Information in the Web Browser
When a Proxy Server is used, an
exception is usually specified so
that the WM Server can be
reached. The following example
explains how to do this in Mozilla
Firefox 33.0 in Windows. Other
web browsers will also have a
facility for this; your network
administrator should be able to
help with this setup.
In Firefox, select ToolsOptions.
Select the Network tab and click
Settings in the Connection section.
14
The HTTP Proxy information would
most likely already exist here. If it
does not, it would need to be
added, otherwise the web
browser would not be able to
reach the Internet.
At No Proxy for:, enter the IP
address or IP Mask that matches
the server IP. This will be the same
information as was entered in the
Java Control Panel, however the
format might be slightly different.
In this example, we used
10.0.0.0/8, which means the
computer will look not look to the
Proxy for any IP address matching
10.x.x.x.
Different web browsers will have a
similar method for adding
exceptions, but it might look
slightly different.

15
4 Launching the WM Client

After any necessary post‐installation tasks are completed, and the WM Service is started, the client
can be launched. Ensure the client computer meets the requirements as outlined under Wireless
Manager Client Requirements on Page 7.
1. Ensure that the WM server is running on its device.
2. From the client, launch a supported web browser.
3. Find the IP address of the WM Server.
4. Type and open this URL in the web browser:
http://WMServerIPAddress:9090. 1
5. If you do not see a page as pictured above, ensure that the WM Server is running, that the IP
address is correct, and that you have followed the information in Installing Java Virtual
Machine on Page 9.
6. Click the Web Start Client button. Depending on your browser, the next dialog box might
look slightly different. The goal is to open the WebNMS.jnlp file with Java. In the case
below, click OK.
1
9090 is the default apache port on which the WM server is running.
17
 If the option to open with Java is not available, ensure you have installed Java as noted
under Wireless Manager Client Requirements on Page 7.
 If you see the following error dialog, this indicates that exceptions were not set correctly on
the web browser’s proxy, or the Java cache must be purged. See Unable to launch the
application on Page 27.
If all is well, the WM client authentication dialog should appear. Enter the User ID and Password as
shown below , then click Connect.
The default User ID is root and the associated Password is public.
Upon successful authentication, the WM client opens.
18
19
5 Troubleshooting the WM Client Launch

This section applies to problems encountered after a new installation of WM on a device operating
on Windows or Linux/CentOS.
5.1 Java Web Start is not installed in this machine. Please

download Web Start.
When you click the Launch WM Client button in the Wireless Manager startup web page, the file
WebNMS.jnlp is automatically downloaded to your client device. However, if this error is returned
instead
perform the following steps:
1. Download and install JRE as directed in Installing Java Virtual Machine on Page 9.
2. If your web browser is
Microsoft Internet Explorer, perform the following steps:
a) Click the gear symbol ( ) in the upper right corner of the error window.
b) From the resulting drop‐down menu, select Compatibility View settings.
21
c) In the Compatibility View Settings dialog, add the server host to the compatibility
list as shown below.
d) Dismiss the dialog.
22
Mozilla Firefox on a Windows platform, perform the following steps:
a) Launch Mozilla Firefox.
b) Select ToolsOptions.
c) Select Applications.
d) Under Content Type, locate the entry for JNLP File.
note ............. If you do not see an entry for JNLP File, close the Options dialog, perform the steps
provided under Configuring jnlp File Association in Windows on Page 11, then restart this
procedure at Step 1.
e) Select the JNLP File entry.
f) Under Action, select the Use Other option (as shown above).
g) Click OK.
h) From the Select Helper Application dialog, click Browse, navigate to the directory
where the required client Java version is installed, and select the javaws executable
file.
i) Click OK to close the Select Helper Application dialog.
j) Click OK to close the Options dialog.
Mozilla Firefox on a Linux platform, perform the following steps:
a) Launch Mozilla Firefox.
b) In the URL text box, enter
http://WM_server_IP_address:port/conf/WebNMS.jnlp.
Example: http://10.222.35.129:9090/conf/WebNMS.jnlp
23
c) In the panel shown below, click the Browse button.
d) Browse to the jre/bin directory.
e) Click to highlight javaws.
f) Click the Open button.
5.2 Launch of a Second Client on Same Machine Hangs at 20%

When this occurs, errors may or may not be noted about not being able to load certain WebRenderer
libraries. This occurs as the physical map simultaneously loads for each client session.
24
A workaround is available to delay the physical map load until the map itself is launched:
1. Open the file ...server\conf \NmsPanels.conf for editing.
2. Change
<PANEL
className="com.motorola.wibb.ems.platform.client.ui.oakleaf
.PhysicalMapPanel" PANEL-KEY="PhysicalMapPanel" INIT-ON-
STARTUP="true" />
to
<PANEL
className="com.motorola.wibb.ems.platform.client.ui.oakleaf
.PhysicalMapPanel" PANEL-KEY="PhysicalMapPanel" INIT-ON-
STARTUP="false" />
3. Save and close the file.
4. Launch multiple client instances.
5. Stagger their physical map launches.
5.3 The Operating System Does Not Recognize the jnlp File Type
Perform the steps provided under Configuring jnlp File Association in Windows on Page 11.
5.4 Java exception: Missing required Permissions manifest

attribute in main jar
The error generated for this exception is Unable to launch the application. This
exception may be indicating a problem that has resulted from enhanced security that makes Java less
vulnerable to external exploits. In Java 7 Update 51 and later, users are not allowed to run
applications that are
 unsigned
 self‐signed (not signed by a trusted authority)
 missing permission attributes.
WM thus qualifies as an application for Java to block. However, Java allows operators to add a
blocked application to an exception list so that it will run with certain warnings. To add WM in this
way, perform the following steps:
1. Open the Java Control Panel (in Windows, click Start and then select Configure Java; in
Linux, launch the executable file /usr/local/cambium/wm/jre/bin/jcontrol).
2. Click the Security tab.
3. Click the Edit Site List button.
4. Click Add in the Exception Site List window.
25
5. Set the cursor in the text box under Location.
6. Type in the URL of the WM server and port.
Example: http://localhost:9090 or http://10.222.45.126:9090
where 10.222.45.126 is IP Address of WM server
7. Click OK to save the URL that you entered.
8. Click Continue in the Security Warning dialog.
5.5 Transport Exception when communicating with server.

If this error occurs
it may be indicating that the proxy is blocking client‐server communication. If you encounter this
error, perform the following steps:
1. Open a command prompt in the operating system.
2. Execute the command javaws –uninstall.
3. Open Java Control Panel.
26
4. Click the Network Settings button.
5. Configure the proxy server. (See Setting Proxy Information in the Java Control Panel on
Page 10.)
6. Click OK to apply the settings.
7. Launch the WM client.
5.6 Unable to launch the application

You will receive this error if any of the proxy information (Java or web browser) is incorrect. See
Installing Java Virtual Machine on Page 9.
If you have already configured the proxy information, you might need to flush Java’s file cache, so the
new file can be loaded:
27
From the Java Control Panel, select Settings from
the Temporary Internet Files section.

Click Delete Files, and delete both Applications and
Applets and Trace and Log Files.
Click OK.
Try to launch the Web Start Client again.
Another reason for which you may see this error from Java is that you have not configured the
application as an exception for Java to allow:
28
In this case, you may have first encountered the
Java confirmation pop‐up warning about the
possibility that future attempts may be blocked.
1. Access the Java Control Panel as follows:
 If the client device OS is Windows, open
Control Panel, then double‐click Java.
 If the client device OS is Linux, enter
/usr/local/cambium/wm/jre/bin/jcontrol
2. In the resulting Java Control Panel, click the
Security tab.
3. In the Exception Site List block of this tab, click
the button for Edit Site List....
4. In the Exception Site List dialog, click Add.
29
5. When this dialog transitions to provide a text
box under Location, type
http://ServerIPAddress:PortNumber
6. Click OK.
7. Back in the Java Control Panel, click OK.
8. Direct your browser once again to
http://ServerIPAddress:PortNumber
9. In the Wireless Manager login page, click the
button for Launch WM Client.
RESULT: The Wireless Manager Authentication
dialog opens for logging in.

This error may also result from a VPN, firewall, or antivirus connection. Where this is the case, it is necessary to
specifically bypass the WM‐launch URL from the offending application or temporarily disable the application for
the duration of the WM client session.
See also Java exception: Missing required Permissions manifest attribute in main jar on Page 25.
5.7 JRE Will Not Install or Settings Are Not Accepted in Windows
If you find this to be the case, attempt a direct client launch from the DOS utility as follows:
1. Open the Command Prompt accessory.
2. At the command prompt, enter
C:\Cambium\WM\jre\bin>javaws.exe http://localhost:9090/conf/WebNMS.jnlp
where this bin folder is in fact where the javaws.exe executable is stored in your
client device.
30
Resources for Support

Community Forum
The technical support Community Forum is part of the support web site and can be used for asking
questions directly to the support team. Questions and answers are accessible to all so that any
customer can benefit from the same dialogue. To access this forum, visit
http://community.cambiumnetworks.com/. This forum requires authentication for posting.
Technical Support
You can obtain support for Wireless Manager from any or all of the following sources:
 Wireless Manager user guide, administration guide, and release notes at
http://www.cambiumnetworks.com/support/management‐tools/wireless‐manager/.
 Cambium Networks support web page: https://support.cambiumnetworks.com/. This page
provides links to information on all products and tools, as well as access to customer support
materials and interactive support forums. These resources are restricted to registered users
and channel partners.
 the Community Forum. Visit http://forum.cambiumnetworks.com/. See Community Forum
on Page 31.
 direct contact with Cambium Networks Technical Support. This contact is available 7 days
a week, 24 hours a day. To find the appropriate phone number based on your country or
region, visit http://www.cambiumnetworks.com/support/contact‐support.
 a technical support case, which you can open at
http://www.cambiumnetworks.com/support/open‐a‐support‐case. The case captures basic
information about answers you are seeking or the problem that your network is
experiencing and provides this to the support team, who are available 7 days a week,
24 hours a day, and will respond. They will also provide a case number by which you and
they can continue to track progress on issues that require deeper investigation.
31

Cambium Wireless Manager Client Setup Guide: System Release 4.2 and Later

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Cambium Wireless Manager Client Setup Guide: System Release 4.2 and Later

Transféré par

Droits d'auteur :

Formats disponibles

Cambium

Issue 1 November 2014

1 About this Guide

2 Wireless Manager Client Requirements

Requirement type Supported

Requirement type Software and version

browser If the client is on a If the client is on a

3 Configuring Proxy and File Association

3.2 Configuring the Proxy on a WM Client

3.3 Setting Proxy Information in the Java Control Panel

3.4 Configuring jnlp File Association in Windows

3.5 Set the Proxy Information in the Web Browser

4 Launching the WM Client

5 Troubleshooting the WM Client Launch

5.1 Java Web Start is not installed in this machine. Please

5.2 Launch of a Second Client on Same Machine Hangs at 20%

5.4 Java exception: Missing required Permissions manifest

5.5 Transport Exception when communicating with server.

5.6 Unable to launch the application

Resources for Support

Vous aimerez peut-être aussi