deviceBridge™ User Guide

Transcription

Mobile Labs
deviceBridge™ User Guide
Copyright © 2016 Mobile Labs, LLC. All rights reserved. Confidential and Proprietary
i
Contents
1
About deviceBridge
1
2
Requirements
1
2.1
deviceConnect Appliance Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
2.2
deviceConnect Power Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
2.3
Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
2.4
Network Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
2.5
Trust Hardware Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3
2.6
deviceBridge Hardware Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4
2.7
Supported Mobile Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4
3
4
5
6
7
8
9
Getting Started
4
3.1
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4
3.2
Install deviceBridge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5
deviceBridge Applications
7
4.1
deviceBridge Application on Mac OS X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
4.2
deviceBridge Application on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15
deviceBridge Command Line Interface
21
5.1
21
deviceBridge Command Line Interface for OSX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration file
23
6.1
Configuration file contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24
6.2
Sample Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24
deviceBridge Maintenance and Management
25
7.1
25
deviceBridge logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mobile Labs Support
25
8.1
25
Upgrading deviceConnect Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Legal Notices
26
ii
Mobile Labs, LLC 7.1, April 2016
1 About deviceBridge
deviceBridge is an application that allows a user to connect remotely connected devices in deviceConnect™ to a user’s
local workstation, as if the device was connected by USB cable, giving users the ability to use remote devices to develop,
debug, and test native and web mobile applications.
2 Requirements
2.1 deviceConnect Appliance Specifications
Dimensions
Monitor Height
Cart Weight
Capacity
USB Hubs
Appliance Fans
Server
37 5/8" W x 39 1/8" H x 24" D
19.35"
216 lbs
48 devices
3 Datamation 16-Port USB Charge and Sync Hubs
3 intake fans, 3 exhaust fans
Apple Mac Mini running OS X 10.11.3
Intel i7 3.0 GHz processor, 16GB RAM, 1TB Hard Disk Drive
2.2 deviceConnect Power Requirements
International
Fans
Domestic Fans
Mac-mini
USB Hubs
Monitor
6.5 Watts, 230 Volts, 0.045 Amps (x6= 0.27 Amps)
5.5 Watts, 115 Volts, 0.08 Amps (x6= 0.48 Amps)
85 Watts, 230 Volts, 0.36 Amps
225 Watts, 230 Volts, 0.97 Amps (x3= 2.91 Amps), 3.6 Amps Max
28 Watts, 12 Volts, 2.3 Amps
2.3 Software Requirements
Various components will require different software. The deviceConnect UI is a browser based application and browser
based deviceViewer. These can run on many platforms and browsers. Mobile Labs Trust is a software download that
only runs on Windows. Below are the software requirements needed to use deviceConnect.
2.3.1 deviceConnect Management
Browsers
OS X
Windows
IE 8 or greater, Edge, Firefox, Chrome, Safari
10.8 or greater
Windows 7 or greater
Note
Xcode 6.0 on a Macintosh running OS X 10.9 is required to provision the deviceControl applications for use and
optionally to incorporate the Trust instrumentation library to your iOS application. You will need an Apple Developer or
Enterprise account to provision and instrument applications.
1 / 26
2.3.2 deviceViewer Browser
Browsers
OS X
Windows
IE 10 or greater, Edge, Firefox, Chrome, Safari 6.1.5 or greater
10.8 or greater
2.3.3 Mobile Labs Trust
Windows
.NET
HP
4.0
QuickTest Professional (QTP) 11 or Unified Functional Tester (UFT) 11.5X - 12.5X
(required for automation)
Note
QTP version 11 requires patch QTPTEA_00002. This patch must be requested through HP Support. Contact your
QTP system administrator to initiate a support request to receive this patch.
2.3.4 deviceBridge
Browsers
OS X
Windows
Xcode
Firefox, Chrome, Safari 6.1.5 or greater
OS X 10.10.4 or greater
Version 6 or greater
2.3.5 deviceConnect Command Line Interface (CLI)
.NET
Framework
Mono
Windows
OS X
4.0
3.2.4.9 (http://www.mono-project.com/Mono:OS X)
10.8 and greater
Note
Mono is only required for Mac OS X.
2.4 Network Requirements
deviceConnect was designed and built to be installed behind corporate firewalls. Therefore, there are some network
requirements for deviceConnect.
Tip
Mobile Labs recommends being connected by Ethernet cable rather than WiFi for controlling devices. Each device
connection will utilize around 3 Mbps bandwidth.
2 / 26
2.4.1 Static IP Address
Because deviceConnect contains a server, a static IP address must be assigned to the server allowing users to access the
server.
Tip
A DNS entry for the IP address can make getting to the server easier for users.
nect.company.com.
For example: devicecon-
2.4.2 Ports
The internal network is used for communication from a web browser and Mobile Labs Trust to the deviceConnect server.
The following ports must be open for communication to the server:
80
10160
22
This port is used to access the deviceConnect web UI.
This port is used by Mobile Labs Trust to communicate to the server for device control and
automation.
SSH port to remotely manage the server. This is optional as the server can be managed
directly with the mouse and keyboard.
2.4.3 WiFi or Cellular
deviceConnect does not share the network connection with the devices, therefore it is necessary to give the devices WiFi
or Cellular connections. This is required because it’s important for applications to use the same connection mechanisms
they normally make for testing, without being interfered by the deviceConnect communication that comes over the USB
connection.
2.5 Trust Hardware Configuration
2.5.1 Recommended Configuration
The following lists show the recommended and minimum requirements for using Mobile Labs Trust. If you are using
HP Unified Functional Testing, these requirements are in addition to the minimum requirements for using UFT.
Computer /
Processor
Memory
Color Settings
Graphics Card
Intel® Core™ i7
6GB
32 bit
1GB
2.5.2 Minimum Configuration
The following is the minimum configuration of hardware supported.
Computer /
Processor
Memory
Color Settings
Graphics Card
Intel® Core™ i5
4GB
32 bit
256MB
3 / 26
2.6 deviceBridge Hardware Configuration
2.6.1 Recommended Configuration
The following lists show the recommended and minimum requirements for using deviceBridge. If you are using any
other development and testing software, these requirements are in addition to the minimum requirements for such
software.
Computer /
Processor
Memory
Disk
2.2GHz Quad-core Intel Core i7
16GB 1600MHz DDR3L SDRAM
500 MB available disk space
2.6.2 Minimum Configuration
The following is the minimum configuration of hardware supported.
Computer /
Processor
Memory
Disk Space
1.6GHz dual-core Intel Core i5 processor
2.5GHz 4GB of 1600MHz DDR3 memory
250 MB available disk space
2.7 Supported Mobile Platforms
Apple iOS
Android
Amazon™
devices running versions 6.0 - 9.3
phones or tablets running versions 2.3, 4 - 6.0
Phones and Tablets running Android versions 2.3, 4 - 6.0
Note
Android devices running on a x86 processor or using 64bit JNI libraries are currently not supported. If 64bit JNI
libraries are used, the application is installed as a 32bit application.
3 Getting Started
deviceBridge is a licensed add-on to deviceConnect. Before deviceBridge can be used the license file in deviceConnect must be updated to enable deviceBridge services. Contact your account representative to purchase and enable
deviceBridge.
3.1 Prerequisites
In order to use deviceBridge for Android devices, you must have the following installed on your computer:
• JAVA
• Android SDK
Note
If your have installed Android Studio, you already have the Android SDK
4 / 26
3.2 Install deviceBridge
deviceBridge is an application that must be installed in order to bridge a device to the user’s local workstation. Follow
these steps to install deviceBridge:
1. In the deviceConnect user menu, click the Download deviceBridge to download the files.
2. Extract the files from the dcb.zip file
3.2.1 OS X Installation
1. Extract the deviceBridge-OSX.zip file
2. Copy or move the deviceBridge.app file to the Applications folder to make it easy to access
Note
The first time the app is run, it will prompt the user for username and password for an account with administrative
privileges, and install necessary background components (dcb and dcbControl) and update system configuration as
needed. This installation process is repeated whenever there is a new version of deviceBridge with new versions of
those components. When the installation process is complete, the user is prompted to restart Xcode, iTunes, etc.
3.2.2 Windows Installation
1. Extract the deviceBridge-x86.msi or deviceBridge-x64.msi installer file from the dcb download file
a. For a 32-bit Windows machine, use deviceBridge-x86.msi
b. For a 64-bit Windows machine, use deviceBridge-x64.msi
2. Click Run on the Open File - Security Warning “Do you want to run this file” window
3. Click Next on the Mobile Labs deviceBridge SetUp Wizard
5 / 26
4. Click Yes for user account control windows
a. If prompted, enter computer admin account user name
b. If prompted, enter computer admin account password
c. Click Finish to complete the deviceBridge Setup Wizard
6 / 26
Note
Windows .NET Framework 4.0 must be installed prior to installing deviceBridge.
4 deviceBridge Applications
4.1 deviceBridge Application on Mac OS X
4.1.1 Launch Application
To launch the deviceBridge app:
1. Open the deviceBridge.app that was downloaded and installed to the Applications folder.
2. Click open on the warning deviceBridge.app is an application downloaded from the Internet. Are you sure you
want to open it?’ dialog
3. Click continue on the deviceBridge Component Updates Required dialog
a. Enter computer admin account Username
b. Enter computer admin account Password
c. Click Install Helper
7 / 26
4. Click OK on deviceBridge Updates Complete dialog
5. Restart Xcode or iTunes or any other iOS testing tools
When deviceBridge is launched deviceBridge notifications will appear in the OS X notification center for various activities like devices being connected or disconnected. These notifications can be configured in the OS X notifications
system settings.
8 / 26
4.1.2 OS X Permission Requirements for Android deviceConnect
In order to connect to Android devices, deviceBridge will need to use a copy of the adb application in the Android SDK.
On launch, it will ask you to specify the location of the installation directory.
You can close the Android SDK Configuration window if you do not want to use deviceBridge with Android Devices.
Otherwise, once you have installed Android SDK to your local machine,
1. Click the Choose button
2. If Android SDK is installed, the Finder window will automatically open to platform-tools
9 / 26
3. Choose adb and click Choose
Note
Choose the Do not ask me again checkbox to stop the Android SDK Configuration windows from appearing if you do
not wish to use Android devices with deviceBridge.
4.1.3 Configuration
Use the configuration window to connect servers, devices and change Android SDK Configurations. To launch the
configuration window, click on the deviceBridge icon in the menu bar and choose deviceBridge Configuration. In the
window, when a device or a server are configured, information about the server or device is displayed. For a server, you
can change the login information by clicking the "Change login. . . " button. Click on the "View in deviceConnect" link
to launch deviceConnect and bring up the device list or device details page.
10 / 26
Add Server
To add a server to deviceBridge:
1. Click the + button
2. Choose Add Server. . .
3. Enter deviceConnect host
4. Edit the Server Name field. By default it will update to the host entry.
5. Enter your deviceConnect username
6. Enter your deviceConnect password
7. Click Add
Once the server has been added it will immediately be connected.
Add Devices
To add devices to deviceBrige:
1. Click the + button
2. Choose Add Device. . .
3. Select one or more devices to connect
4. Click Add
Tip
Double click to instantly add a device and close the window
Note
The add devices window will appear after entering a new server in the configuration window.
11 / 26
Warning
For iOS devices using Xcode may require that the symbol files need to be copied into Xcode. This can
be an issue over a network as any interruptions will require that the download start over. If this problem is
experienced, it might be best to copy the files directly from the deviceConnect server to your computer. The
path of the symbol files on the server and your computer are ~/Library/Developer/Xcode/iOS\
DeviceSupport
Remove Servers and Devices
To remove a server and devices from being connected to the computer with deviceBridge:
1. Select the server or device in the list
2. Click the - button
3. Click Remove button on confirmation window
Note
Removing a server will also remove all of the associated devices.
Android SDK Configuration
Android SDK configurations can be changed from the deviceBridge Configuration window.
1. Click the settings button
2. Choose Android SDK Configuration. . .
3. Make needed changes and click Choose
Export Configuration
The deviceBridge configuration details can be exported to a file so they can be saved and loaded at another time.
2. Choose Export Configuration. . .
12 / 26
3. Enter in a file name and location
4. Click the export button
Note
The file contents are exported in a JSON file format.
Import Configuration
deviceBridge configurations can be imported making it easier to connect to servers and devices instead of adding each
server and device one by one.
2. Choose Import Configuration. . .
3. Choose a file to import
4. Click Import
The servers and devices will then be connected with deviceBridge.
4.1.4 Status
Use the status window to view the status of connected servers and devices. To launch the status window, click on the
deviceBridge icon in the menu bar. The servers and devices will appear in the window and display their connected state
to deviceConnect.
4.1.5 Save Logs
In the event that you are experiencing an issue, support may ask for the deviceBridge logs.
1. Select Save Logs. . . in the deviceBrige menu
13 / 26
2. Choose a file name and location
3. Click Save
The logs contain the following files:
• ~/.dcbridgerc
• /var/log/system.log*
• /usr/local/var/dcb/*
• /Library/Logs/com.mobilelabsinc.*
• /Library/Logs/DiagnosticReports/dcb*
• /Library/Logs/DiagnosticReports/deviceBridge*
• /Library/Logs/DiagnosticReports/com.mobilelabsinc.*
• /Library/Application Support/CrashReporter/dcb*
• /Library/Application Support/CrashReporter/deviceBridge*
• /Library/Application Support/CrashReporter/com.mobilelabsinc.*
• /Library/Preferences/SystemConfiguration/*.plist
4.1.6 User Guide
The user guide can be opened and viewed by selecting deviceBridge User Guide from the deviceBridge application
menu.
4.1.7 About deviceBridge
Choosing About deviceBridge will pop open a new window displaying the deviceBridge version and copyright.
14 / 26
4.1.8 Quit deviceBridge
When you choose the Quit deviceBridge option in the deviceBridge menu, the application will close and disconnect the
servers and devices from the computer. The existing configuration is retained so that when the application is launched
the same servers and devices will be retained.
4.2 deviceBridge Application on Windows
4.2.1 Launch Application
To launch the deviceBridge app:
1. Click on Mobile Labs > deviceBridge in the Windows Start Menu
Notifications will appear in the Windows notification area, at the far right of the taskbar, for various activities like,
devices being connected or disconnected.
15 / 26
Tip
Right-click for the options to pin to your taskbar or Start menu
Note
In order to connect to Android devices, deviceBridge will need to use a copy of the adb application in the Android SDK.
On launch, it will ask you to specify the location of the Android SDK platform-tools directory. If you wish to change
the location later, you can choose Android SDK Configuration in the Options menu of the deviceBridge Configuration
window.
Note
Non-administrator Windows accounts can run deviceBridge after it has been installed by a user with administrative
privileges. deviceBridge cannot be run by multiple users simultaneously on a client workstation.
4.2.2 Configuration
Use the configuration window to connect servers and devices. To launch the configuration window, right click on
the deviceBridge icon in the notification area and choose deviceBridge Configuration. In the window, when a device
or a server are configured, information about the server or device is displayed. For a server, you can change the
login information by clicking the "Change login. . . " button. Click on the "View in deviceConnect" link to launch
deviceConnect and bring up the device list or device details page.
16 / 26
Add Server
To add a server to deviceBridge:
1. Click the Add Server. . . button
2. Enter deviceConnect Host
3. If needed, edit the Server Name field. By default it will update to the host entry.
4. Enter your deviceConnect User Account
5. Enter your deviceConnect Password
6. Click OK
Once the server has been added it will immediately be connected.
Add Devices
To add devices to deviceBrige:
1. Click the Add Devices. . . button
17 / 26
2. Select one or more devices to connect
3. Click OK
Tip
Double click to instantly add a device and close the window
Note
The add devices window will appear after entering a new server in the configuration window.
Remove Servers and Devices
To remove a server and devices from being connected to the computer with deviceBridge:
1. Select the server or device in the list
2. Click the Remove button
3. Click the OK button on confirmation window
Note
Removing a server will also remove all of the associated devices.
Export Configuration
The deviceBridge configuration details can be exported to a file so they can be saved and loaded at another time.
1. Click the File drop-down menu
2. Choose Export Configuration. . . or Ctrl+E
3. Enter in a file name and location
4. Click the Save button
Note
The file contents are exported in a JSON file format.
18 / 26
Import Configuration
deviceBridge configurations can be imported making it easier to connect to servers and devices instead of adding each
server and device one by one.
1. Click the File drop-down menu
2. Choose Import Configuration. . . or Ctrl+I
3. Choose a file to import
4. Click the Open button
The servers and devices will then be connected with deviceBridge.
4.2.3 Status
Use the status window to view the status of connected servers and devices. To launch the status window, click on
the deviceBridge icon in the notification area. The servers and devices will appear in the window and display their
connected state to deviceConnect.
4.2.4 Save Logs
In the event that you are experiencing an issue, support may ask for the deviceBridge logs.
1. Select Save Logs. . . in the deviceBrige menu
19 / 26
+
. Choose a file name and location . Click Save
The logs contain the following files:
• com.mobilelabsinc.deviceBridge.log
• com.mobilelabsinc.deviceBridge.0.log, com.mobilelabsinc.deviceBridge.1.log, com.mobilelabsinc.deviceBridge.2.log,
...
• dcb.log
• dcb.config
• System Information.txt
Note
The 0.log, 1.log, 2.log files are older versions of the com.mobilelabsinc.deviceBridge log. A new log is started each
day (or when the log becomes too big), and older files’ numbers are rotated. A maximum of five such logs are stored.
4.2.5 User Guide
The user guide can be opened and viewed by selecting deviceBridge User Guide from the deviceBridge application
menu.
4.2.6 About deviceBridge
Choosing About deviceBridge will pop open a new window displaying the deviceBridge version and copyright.
20 / 26
4.2.7 Quit deviceBridge
When you choose the Exit deviceBridge option in the deviceBridge menu, the application will close and disconnect the
servers and devices from the computer. The existing configuration is retained so that when the application is launched
the same servers and devices will be retained.
5 deviceBridge Command Line Interface
5.1 deviceBridge Command Line Interface for OSX
deviceBridge comes with a Command Line Interface that can be used to connect and disconnect devices that are housed
in deviceConnect.
5.1.1 Installing the binary as a CLI
The deviceBridge application contains a binary file that can be installed to be used as a Command Line Interface.
To install the deviceBridge binary:
1. Follow the steps to install the deviceBridge application.
2. The dcb binary file MUST be copied from /Applications/deviceBridge.app/Contents/MacOS/
to /usr/local/bin/
3. Open Terminal application and execute the following command to make the file executable
sudo chmod +x /usr/local/bin/dcb
Note
the CLI and the GUI cannot be run at the same time as only one deviceBridge instance can be running.
21 / 26
5.1.2 Running a command
Running a command is as simple as calling "dcb" in a Terminal window. Running the command "dcb" will display the
options that can be used
dcb
The result of the command would be:
deviceConnect Bridge 7.0.0.0
Copyright (c) 2016 Mobile Labs, LLC. All rights reserved.
Usage: dcb [global-options] command [options] args...
Commands:
help - Provides help on a given command.
install - Install dcb as a launchd service (requires root).
uninstall - Uninstall dcb launchd service (requires root).
Global options:
--config - Path to a configuration file.
--debug - Enable debugging output.
Note
The install and uninstall commands will require using "sudo" to run the command.
Examples of some common commands:
dcb
sudo
sudo
sudo
sudo
dcb
dcb
dcb
dcb
install
--debug true install
--config other_config_file install
uninstall
Note
The help command in conjunction with another command will provide more information about the command. For
instance sudo dcb help install will provide more information about the install command.
5.1.3 Connect to a device
To start and connect to devices with deviceBridge, run the following command in a Terminal Window:
sudo dcb install
Once you have the device connected, you can connect to the device with the deviceControl application in the web based
deviceViewer. You should be able to access the desired devices in your development apps such as Xcode, Instruments,
and iTunes.
Tip
Start deviceBridge before opening a connection to the web viewer or other tools that you would like to use.
Note
Since this operation restarts usbmuxd, applications which you intend to use with deviceBridge may need to be
restarted afterwards.
22 / 26
Note
Xcode takes a long time for a device to appear within the UI due to the amount of device queries it performs. iTunes/Instruments do not take as long.
5.1.4 Disconnect a device
The following command will stop deviceBrige and disconnect the device
sudo dcb uninstall
This will release the devices from deviceConnect as long as there are no other sessions to the device such as the
deviceViewer
Note
If you do not run this command, the device will stay retained or will connect again as soon as a network connection is
established to deviceConnect.
5.1.5 Swapping devices
When you start deviceBridge with "sudo dcb install", the configuration file is copied to the following location: /usr/local/var/dcb/config.json. The deviceBridge process is then started using the .json file. See the Configuration File section
of this document to learn more. In order to change devices during usage
To swap out a device:
1. Edit the contents of /usr/local/var/dcb/config.json. This will require use of sudo, because that file will be owned
by root.
2. To cause the server to re-read /usr/local/var/dcb/config.json, the user sends a SIGHUP signal to the process.
sudo kill -HUP NNNN
Simply replace NNNN with the Process ID of the dcb process. If you do not have the Process ID, the following
can be used:
sudo killall -HUP dcb
Note
The .dcbridgerc configuration file is not changed. It is recommended that you update this file if you want your changes
to be permanent.
Note
If the properties of a server or device are changed, then dcb will treat that as removal of the existing object followed
by insertion of a new object with the new properties. For example, if the "name" field of a device is changed, dcb will
disconnect from that device and then re-connect. As another example, if the "token" field for a server is changed, dcb
will disconnect from that server and all associated devices, then reconnect to the server and its devices.
6 Configuration file
The configuration file is the file that stores the configuration of the servers and devices to run deviceBridge. The
configuration file is stored on OS X as the following file:
$HOME/.dcbridgerc
23 / 26
6.1 Configuration file contents
In order to easily build a deviceBridge configuration file, use the deviceBridge application. The deviceBridge configuration file is automatically generated and updated as you use the application.
The configuration file is a file that contains the configuration in JSON format. The servers entry is a JSON Array of the
following objects.
Object
isHttpsWeb
host
name
token
user
linkedDevices
Description
Boolean: Determines if the deviceConnect web interface is accessed via
HTTPS.
String: The IP or DNS name of the deviceConnect server
String: A name of the deviceConnect server that is meaningful to the user
String: The API token of the deviceConnect user
String: The username for the deviceConnect user
JSON Array: A json schema of the devices to connect via deviceBridge
Each linkedDevices contains the following information in the servers section has the following items:
Object
id
os
name
vendorUniqueIdentifier
Description
GUID: The deviceConnect ID of the device. This can be found in the
URL of the browser for the device details page of this device.
String: iOS or Android
String: The name of the device in deviceConnect
String: The vendor unique identifier in deviceConnect. For iOS this is
the UDID of the device. For Android this is the serial number.
Note
Android is not yet supported.
6.2 Sample Configuration
{
"servers" : [
{
"isHttpsWeb" : false,
"linkedDevices" : [
{
"id" : "c933508d-9927-4803-93e4-2171435c7464",
"os" : "iOS",
"name" : "IPHONE5",
"vendorUniqueIdentifier" : "14af9f6fc2f30e284a8464d43594fb16976e2e56"
}
],
"host" : "10.0.1.100",
"name" : "10.0.1.100",
"token" : "ceba3df1-b9d1-415f-a704-be29a3838899",
"user" : "[email protected]"
}
]
}
24 / 26
7 deviceBridge Maintenance and Management
7.1 deviceBridge logs
Sometimes it is necessary to looks at the deviceBridge logs to review the actions of the system. The deviceBridge
system logs the output to the following logs:
7.1.1 OS X
/Library/Logs/com.mobilelabsinc.dcb.log
/var/log/system.log
The first log file mentioned above contains only the deviceBridge log information. The second log mentioned above
contains all of the logs of the computer system including the deviceBridge logs. The deviceBridge log file is rotated to
have a maximum file size of 5MB with a total log file size of 20MB. The extneded logs will have sequential numbers
and are g-zipped, as well as logs that are older than 14 days will be removed.
7.1.2 Windows
%APPDATA%\Local\Mobile Labs\deviceBridge\dcb
%APPDATA%\Local\Mobile Labs\deviceBridge\System Information
The first log file mentioned above contains only the deviceBridge log information. The second log mentioned above
contains all of the logs of the computer system including the deviceBridge logs.
8 Mobile Labs Support
We work hard to make our products easy to use and trouble-free, but if you have questions or issues with any of our
products, please contact us! We are easy to reach and always at-hand if needed.
We strive to be easy to do business with, to keep our promises, and to put our customers first. Our global support team
is available whenever you need them to keep your Mobile Labs products running at their peak.
If you have a question or issue, you can quickly open a Support Ticket with our customer support team at http://support.mobilelabsinc.com
Our team will be notified immediately and a support ticket will be automatically opened in our tracking system. You
can expect a prompt reply with an answer or next steps to resolve your issue.
If you need immediate assistance after hours, you can reach us at +1-888-975-2066. Simply leave a phone number
where you can be reached, and a Mobile Labs support manager will return your call.
For more information about Mobile Labs support or for general questions and/or concerns, please call our main number,
404-214-5804. You can also reach us by email: [email protected].
THANK YOU for being a Mobile Labs customer!
8.1 Upgrading deviceConnect Server
Mobile Labs reminds you to consult with Mobile Labs Support before applying any upgrades or making any modifications to your deviceConnect server(s). The deviceConnect servers are configured especially for deviceConnect
functions, are optimized for security and performance, and are therefore sensitive to OS X software levels and file structure. Modifications to the Mac OS X system, including Apple-supplied upgrades, can cause a deviceConnect outage
and could necessitate a lengthy repair or replacement process. In particular, please do not accept prompts to download
or apply upgrades to the operating system. The deviceConnect server is not configured to support general user-land use;
logins to the Mac OS should only occur at the suggestion of our Support personnel. Please consult with Mobile Labs
Support before making any changes as we want you to always have 100 per cent availability.
25 / 26
9 Legal Notices
Confidential and Proprietary
The information contained in this document is confidential and proprietary to Mobile Labs, LLC. No part of this guide
may be distributed or disclosed in any form to any third party without written permission of Mobile Labs, LLC.
Disclaimers
The information contained herein is subject to change without notice.
Mobile Labs shall not be liable for technical or editorial errors or omissions contained herein.
Copyrights
Copyright © 2016 Mobile Labs, LLC. All rights reserved.
Trademarks
Mobile Labs is a trademark of Mobile Labs, LLC.
deviceConnect is a trademark of Mobile Labs, LLC.
deviceBridge is a trademark of Mobile Labs, LLC.
Mobile Labs Trust is a trademark of Mobile Labs, LLC.
iOS is a trademark or registered trademark of Cisco in the U.S. and other countries and is used under license.
App Store is a service mark of Apple Inc.
Xcode is a registered trademark of Apple Inc.
iTunes is a registered trademark of Apple Inc.
Android is a trademark of Google Inc.
Amazon, Kindle, Fire and all related logos are trademarks of Amazon.com, Inc. or its affiliates.
Microsoft, Windows, Windows XP are U.S registered trademarks of Microsoft Corporation in the United States and
other countries.
HP Unified Functional Testing is a registered trademark of Hewlett-Packard Development Company. HP and the names
of any other HP products referenced herein are trademarks and/or service marks or registered trademarks and/or service
marks of Hewlett-Packard Development Company, L.P., and/or its subsidiaries.
26 / 26

deviceBridge™ User Guide

Transcription

Similar documents

Silego Technology - Globalpress Electronics Summit

Mohawk College Student Feedback on Teaching INFO BA635

CATALINA ISLAND MARINE INSTITUTE

Preschool Deluxe Action Train Table with Lid

pamphlet - Muddy Paws

I`m helping to end MS by participating in the 2016 Jayman BUILT MS

leonard ho spearman technology building

Firehouse hosts Great Big Home Show

The Board of Directors of Qatar Fuel (WOQOD) is pleased to invite