Readme

HPE Mobile Center

Software Version: 1.52

 

Publication date: March 2016

Software release: March 2016

 

Patch 1 for version 1.52 includes the following enhancements:

 

This Readme provides information about Mobile Center such as system requirements, integrations information, and known issues:

Note: For the most up-to-date information on Mobile Center, check out the Mobile Center online help.

 

How to install

Installing Mobile Center requires that you first install Mobile Center 1.52, and then upgrade to Patch 1.

Choose the installation procedure according to your current situation:

If you have ... Follow this procedure
No existing installation of Mobile Center/ Mobile Center 1.51 installed Install Mobile Center 1.52 and then upgrade to patch 1.
Mobile Center 1.52 installed Upgrade to patch 1

Patch installation

Mobile Center 1.52 Patch 1 should be installed on top of an existing installation of Mobile Center 1.52.

The following steps assume that you have Mobile Center 1.52 installed.

Note: To run the app packager upgrader on iOS apps, make sure to first copy the latest version of the Mobile Center packager service to your Mac Machine. Before upgrading Mobile Center, set up your Mac machine as described in Configure the app packager for iOS apps.

 

To upgrade Mobile Center on a Linux Machine:

  1. Download  Mobile Center 1.52 Patch 1.
  2. Log in as root.

  3. Run the following command:
    unzip MOBILE_00009.zip –d <Target directory Name>
  4. Change directory to the Target directory:
    cd <Target directory Name>
  5. Run the following command:
    unzip MOBILE_00009.zip
  6. Extract the Linux installer:
    unzip MOBILE_00009-linux.zip
  7. Run the installer script:
    ./install_hpmc_HF.sh
  8. When you upgrade to the patch, the installer recognizes that you may have apps on the server that require repackaging, and prompts you to run the app packager upgrader. If you choose not to, you can run it manually at a later stage. For details, see upgrading apps with the upgrader tool.

  9. Note: If your apps were packaged manually from the command line and then uploaded to Mobile Center, the upgrader will not be able to upgrade the apps. You will need to repackage your apps using the latest version of the HPMC Enabler (iOS) or the HP4M APK Infuser (Android) before uploading them to Mobile Center.

    1. Enter Y to run the app packager upgrader.
    2. Enter the following parameters:
    3. ip Mobile Center server IP address.
      port Mobile Center server port
      email Mobile Center user name
      type

      App type:
      android
      ios
      all

  10. When prompted, enter the password for the Mobile Center user.

    The upgrade process starts. At the end of process, a report is displayed listing apps that were successfully repackaged, as well as those apps that couldn't be repackaged.

  11. Start the server:
    service hpmc start

To upgrade Mobile Center on a Windows Machine:

  1. Make sure you have Mobile Center version 1.52 installed.
  2. Download the  Mobile Center 1.52 Patch 1 file, MOBILE_00009.zip , and extract the files to a temporary folder. Unzip the second MOBILE_00009.zip file.
  3. From the MOBILE_0009 folder, extract the contents of the appropriate setup file, for example, MOBILE_00009.x32-win-server.zip or MOBILE_00009.x64-win-server.zip, onto the machine.
  4. Run the setup file. When you begin the installation of version 1.52 Patch 1, the wizard will detect that this is an upgrade and prompt you accordingly.
  5. In the Packaging Upgrade screen, indicate whether you want to automatically run the packager at the end of the setup. If you choose not to, you can run it manually at the end of the setup. For details, see upgrading apps with the upgrader tool.
  6. If you choose to upgrade the apps, the next screen prompts you to specify the credentials for the Mobile Center server, and to select the operating systems of the apps you want to upgrade.
  7. When the installation is complete, a message is displayed that the server was installed. Click Done.
  8. To stop an installation in progress, click Cancel. The setup program will roll back all the changes.

Note:
After upgrade:

Standalone Connector

Connector and server installations must be of the same version, in order for the devices to communicate properly with the server. If you installed the connector for Mobile Center 1.52 as a standalone component on a different machine, run the connector installer for Mobile Center 1.52 patch 1 as follows:

Linux connector:

  1. Copy the MOBILE_00009.zip file to your Linux machine.

  2. Log in as root.
  3. Run the following command:
    unzip MOBILE_00009.zip –d <Target directory Name>
  4. Change directory to the Target directory:
    cd <Target directory Name>
  5. Run the following command:
    unzip MOBILE_00009.zip
  6. Extract the Linux installer:
    unzip MOBILE_00009-linux.zip
  7. Run the installation script for the connector:
    ./install_hpmc_connector_HF.sh
  8. Restart the service:
    service hpmc start

Windows connector:

  1. Go to the patch archive file, MOBILE_00009.zip, and extract the files to a temporary folder. Unzip the second MOBILE_00009.zip file to the default MOBILE_0009 folder.
  2. From the MOBILE_0009 folder, extract the contents of the appropriate setup file, for example, MOBILE_00009.x32-win-connector.zip or MOBILE_00009.x64-win-connector.zip, onto the machine.
  3. Run the setup file, following the instructions of the wizard.

Enable iOS 9.3 support

iOS 9.3 support is included in Mobile Center 1.52 Patch 1. (This is the same package for iOS 9.3 support that is available from HPLN).
  1. Place the 9.3 folder (included in the installation package) under the relevant folder on the server:

    Linux: /opt/hpmc/libimobiledevice/developer-images

    Windows: server\libimobiledevice\developer-images or connector\libimobiledevice\developer-images
  2. On Linux machines, run chown hpmc:hpmc 9.3/ to associate the folder with the Mobile Center installation.
  3. Unplug the device and wait 10 sec before plugging it back into the server or connector.

Once connected, the device will be launched with Mobile Center support for iOS 9.3.

 

Server requirements

The Mobile Center server can also be run on a virtual machine.*

Linux server

Computer Processor:

2x2 GHz or higher dual core processor (Quad core recommended)

Operating System:

Red Hat Enterprise Linux 6.5 minimal workstation x64

Red Hat Enterprise Linux 7.1 minimal workstation x64

CentOS 6.5 minimal installation

CentOS 6.6 minimal installation

Memory:

4 GB RAM

Mobile Center requires at least 1 GB RAM free (2 GB recommended)
.

Free Hard Disk Space:

Hard disk space: 20 GB

  • General Installation: 15 GB
    • Installation directory: (/opt/hpmc) 1 GB
    • Database directory: (/opt/postgres) 13500 MB

      Note: You may require more space depending on the number of apps or app uploads that you are performing. For example, if the app size is 20 MB, and you have uploaded the same app 100 times, the required size is 2 GB.

    • Third party directory: (/opt/hpmc_3rd_party) 500 MB
  • Temp directory: (/tmp/) 5 GB

An additional 1 GB of free disk space is required on the system disk (the disk upon which the operating system is installed).

Browser:

Chrome, Firefox, Internet Explorer 10, Internet Explorer 11, Microsoft Edge.

(Browsers supported on clients connecting to Mobile Center's Lab Management console).

Database:
(comes with the installation package)

PostgreSQL server Version 9.3  

Maximum number of connected devices per server:

55 devices

Windows server

Computer Processor:

2x2 GHz or higher dual core processor (Quad core recommended)

Operating System:

Windows 7 64-bit

Windows Server 2012 R2

Windows 8.1

Memory:

4GB RAM

Mobile Center requires at least 1 GB RAM free (2 GB recommended)
.

Free Hard Disk Space:

Hard disk space: 20GB

  • General installation: 15 GB
    • <Installation Directory>: 1.5 GB
    • <Database Installation Directory>: 13.5 GB

      Note: You may require more space depending on the number of apps or app uploads that you are performing. For example, if the app size is 20 MB, and you have uploaded the same app 100 times, the required size is 2 GB.

  • Temp directory: (\Temp) 5 GB

An additional 1 GB of free disk space is required on the system disk (the disk upon which the operating system is installed).

Browser:

Chrome, Firefox, Internet Explorer 10, Internet Explorer 11, Microsoft Edge.

(Browsers supported on clients connecting to Mobile Center's Lab Management console).

Database:
(comes with the installation package)

PostgreSQL server Version 9.3  

Maximum number of connected devices per server:

55 devices

*Hosted virtualization hypervisors are supported. Mobile Center has been certified with:

 

Supported devices

For the most up-to-date list of certified devices, see supported devices.

The following devices are supported by Mobile Center:

Android

Devices running on Android 4.1 OS and higher.

The following devices have been tested and verified with Mobile Center:

Smartphones
Manufacturer Model Model number
CoolpadCoolpad S69190L_C00
Google Nexus 5Nexus 5
Google Nexus 6Nexus 6
HTCOne SHTC One S
HTCOne M8HTC One_M8
HTCOne M9HTC One M9
HTCDesire D816HHTC D816H
HuaweiHuawei P8GRA-L09
Huawei

Huawei Ascend P7-L10 4G

Known limitation: USB debugging needs to be activated each time you reconnect the device to Mobile Center.

Huawei p7-l10
LenovoS90S90-A
LGG3 16 GBLG-D855
LGD405h L90LG-D405h
LG G Flex2LG-H955
LGG4 LG-H815
LGNexus 5XLG-H791
Meizu

Meizu MX4 Pro

  1. Reboot your Linux machine.
M462
MotorolaMoto G (2nd Generation)Moto G (2nd Gen.)
MotorolaMoto XMoto X
MotorolaNexus 6XT1100
OnePlusOnePlus OneA0001
OnePlusOnePlus TwoA2003
OppoOppo R7 R7 Plus TD-LTE
Samsung

Galaxy Ace 3

Note: When connecting the device to Mobile Center, the orientation should be set to portrait.

GT-S7275B
Samsung Galaxy NoteGT-N7000
Samsung Galaxy Note 2 GT-N7100
SamsungGalaxy Note 3 SM-N9005
SamsungGalaxy Note 4SM-N910C
SamsungGalaxy Note Edge N915FSM-N915F
SamsungGalaxy Note 5SM-N920C
Samsung Galaxy S4GT-19500
Samsung Galaxy S5SM-G900F
SamsungGalaxy S6SM-G 920F
SamsungGalaxy S6 EdgeSM-G925F
SamsungGalaxy S6 Edge +SM-G928F
Sony Xperia ZD6653
SonyXperia Z5E6653
XiaomiXiaomi MI 3MI 3W
XiaomiXiaomi MI 4MI 4W
XiaomiXiaomi Note2014616
XiaomiXiaomi Redmi Note2014915

 

Tablets
Manufacturer Model Model number
GoogleNexus 7Nexus 7
GoogleNexus 9 Nexus 9
GoogleNexus 10Nexus 10
HPHP Slate 7 extremeH Slate 7 extreme
HPHP Slate S8-7600US 8-Inch7600US
HuaweiHonor TabletT1-823L
LenovoLenovo TAB 2A7-10F
Samsung Galaxy Tab 2 7.0 GT-P3100
SamsungGalaxy Tab 2 10.1GT-P5100
Samsung Galaxy Tab 3 7.0 SM-T 210
SamsungGalaxy Tab 3 Lite 7.0SM- T110
SamsungGalaxy Tab 3 8.0 SM-T 310
SamsungGalaxy Tab 4 8.0SM T330
SamsungGalaxy Tab 4 10.1SM- T531
SamsungGalaxy Tab A 9.7SM- T555C
SoulycinSoulycin T800T800
SonyXperia Z3SGP611
TeclastTeclast P98P98
XiaomiMI PadA0101
XiaomiMi Pad 2Mi Pad 2 16 GB

 

iOS

Devices running on iOS 7.x OS and higher.

Certain iOS devices (iPhone 4, iPhone 4s, iPad Mini 1, and iPad 2) are only supported for replay—not record. When working with these devices, install apps manually before running them. For details, see Repackage apps for specific iOS devices .

The following devices have been tested and verified with Mobile Center:

Smartphones
Manufacturer Model Model number Comments
AppleiPhone 4A1332xReplay only
AppleiPhone 5A1429 
AppleiPhone 5cA1507 
AppleiPhone 5sA1457 
AppleiPhone 6A1586 
AppleiPhone 6+A1522 
AppleiPhone 6sMKT32LL/A 
AppleiPhone 6s+MKVG2LL/A 

 

Tablets & iPods
Manufacturer Model Model number Comments
AppleiPad AirA1474 
AppleiPad Air 2A1566 
AppleiPad mini 1 32GB Wi-Fi+4G MD544HB / AReplay only
AppleiPad mini 2 Retina 16GB Wi-Fi ME279HB/A 
AppleiPad mini 3 Wi-Fi 16GB GoldMGYE2CH/A 
AppleiPad mini 4 Wi-Fi 64GBMK722RK/A 
AppleiPad 2A1396Replay only
AppleiPad 3A1340 
AppleiPad 4 A1460 
AppleiPod Touch (5th Gen) A1421 

 

Emulators

(Android 4.1 and higher):

Google SDK

Genymotion

 

Connector requirements

When you install Mobile Center, both the server and the connector are installed. However, the connector is designed as a lightweight piece of software for connecting devices to Mobile Center, that can also be installed as a standalone component. You can install the connector on multiple machines in distributed locations, or on your testing-tool machine. The connector can be installed on a Windows or Linux machine. For details, see Install the connector on a Windows machine or Install the connector on a Linux machine.

Linux

Hardware:

  • 2 GB RAM
  • 2 GB disk space

Operating System:

  • Red Hat Enterprise Linux 6.5 minimal workstation x64
  • Red Hat Enterprise Linux 7.1 minimal workstation x64
  • CentOS 6.5 minimal installation
  • CentOS 6.6 minimal installation
Windows

Hardware:

  • 2 GB RAM
  • 2 GB disk space

Operating System:

  • Windows Server 2008 R2 SP1 64-bit
  • Windows Server 2012 R2
  • Windows 7 SP1 32-bit or 64-bit
  • Windows 8.1 64-bit
  • Windows 10

Every mobile device connected to Mobile Center requires 900mA - 1.5A per port, depending on the device. To optimize power consumption and provide better utilization of USB ports, we recommend using a USB hub with an independent power supply that can sustain power consumption.

 

Network requirements

The following ports are required:

Server:

HTTPS (8443)

HTTP (8080)

VNC (5900)

VNC SSL (5901)

Connector:

HTTPS (8443)

HTTP (8080)

VNC (5900)

VNC SSL (5901)

Devices: 
Remote access3389
5900
5901
Android-specific

5000
5001

iOS-specific

12345

 

Multi-language support

Note: Mobile Center server does not support non-English OS servers.

 

Integrations

For a complete list of products that integrate with Mobile Center, check out My Product Matrix.

 

Limitations

Installation

Windows. Virtual network cards must be disabled before installation. In Control Panel\Network and Internet\Network Connections, right-click the virtual connection and select Disable. Virtual connections can be reactivated after installation.

Windows Update. When updating the Mobile Center server from version 1.51 to version 1.52, the setup program will always indicate that the application repackaging was successful. The setup issues this message even if you chose not to repackage your apps, even if you had no apps to repackage, and even if the repackaging failed.

Multi-Language support

Mobile Center server does not support non-English OS servers.

Saving Filter Preferences

In Windows 8.1, if you are using Internet Explorer version 11.0.23 as a non-admin user:

These limitations result from Internet Explorer not allowing localStorage access. These limitations do not apply if you launch the browser as an administrator.

Uploading apps

The maximum file size that you can upload is 200MB.

Remote access

Record and Replay

Android:

iOS:

Testing tools - UFT

The following are additional limitations when using Unified Functional Testing (UFT) with Mobile Center:

Opening Mobile Center

After defining the connection information for Mobile Center in the Options dialog box, the remote access window opens every time a record or run session begins.

To prevent this window from opening when you are not testing mobile applications, select Do not record and run tests on mobile in the Mobile pane of the Record and Run settings dialog box.

Running tests

Device locking

When you run a test or component on a mobile device, the device remains locked by Mobile Center until the test or component is closed. This is true even if the test or component is no longer running.

Multiple devices

Unexpected issues may occur when you are running a test with a MobileWebView test object on multiple devices.

If so, remove the accessibilityid description property from the test object and run the test again.

Device filtering: Testing multiple devices

If you have multiple steps in your test that use the same device filtering criteria defined by description properties, and also have multiple devices connected to Mobile Center that match the filtering criteria, all relevant steps use the same device used by the first step in your test.

To use a different device in a specific step, modify the filter for that step.

Device filtering: Modifying your filter

If your device filter is defined by description properties, and you modify those properties before running the test a second time, the device remains locked from the first run, and the second test run will fail.

Unlock the device in Mobile Center before running the test a second time.

Device filtering: Multiple steps with different device filters

If your test has separate steps with different device filters for each step, where the device filters do not conflict (the same device matches each filter), and:

To use the same device, modify the filter so that the properties match in all relevant steps.

For example, if you have a single device connected that matches the filters in both of the following steps, the test will fail on the second step.

Device("osversion:=8.4","ostype:=iOS").App("name:=HP Mobile Web","identifier:=com.hp.HPMobileWebBrowserINJ").MobileEdit("nativeclass:=UITextField","mcindex:=0","ispassword:=False","class:=Input","accessibilityid:=url").Set "AAA"
Device("ostype:=iOS").App("name:=HP Mobile Web","identifier:=com.hp.HPMobileWebBrowserINJ").MobileEdit("nativeclass:=UITextField","mcindex:=0","ispassword:=False","class:=Input","accessibilityid:=url").Set "BBB"

Modify the steps as follows to run the test:

Device("ostype:=iOS").App("name:=HP Mobile Web","identifier:=com.hp.HPMobileWebBrowserINJ").MobileEdit("nativeclass:=UITextField","mcindex:=0","ispassword:=False","class:=Input","accessibilityid:=url").Set "AAA"
Device("ostype:=iOS").App("name:=HP Mobile Web","identifier:=com.hp.HPMobileWebBrowserINJ").MobileEdit("nativeclass:=UITextField","mcindex:=0","ispassword:=False","class:=Input","accessibilityid:=url").Set "BBB"

Spying and highlighting

Text recognition

Testing mobile devices does not support the Tesseract OCR text recognition engine.

Business Process Testing

Testing Android apps

The MobileView object is not recorded.

Instead, you can create it manually in the object repository and do the following:

Testing SAP Fiori apps

If your test was created for a desktop version of a Fiori application, you may need to modify the test to ensure it runs correctly on the mobile version.

Additionally, different resolutions on different devices may cause differences in an object's properties and behavior. You may need to manually edit the test script to support multiple devices.

Tip: Add an Exist statement to ensure that an object is completely loaded on a page in a Fiori mobile application before running steps on that object.

Specific objects and methods

SAPUIRadioGroup

The SAPUIRadioGroup test object is not supported for Fiori applications.

SAPUITextEdit / SAPUIButton

Sometimes, when using SAPUITextEdit and SAPUIButton objects, the test steps are recorded in the incorrect order.

If this happens, change the order of the steps manually.

SAPUITextEdit

The SAPUITextEdit test object html tag identification property now uses the parent DIV element (instead of the INPUT element).

You must update any:

  • Tests that include checkpoints, output values or GetROProperty("html tag") steps on the SAPUITextEdit test object.

  • SAPUITextEdit objects you have in your object repositories.

SAPUIDialog.Close

The SAPUIDialog.Close button works only when a dialog contains a X close button.

Standard checkpoints and output values

When inserting standard checkpoints and output values to an already recorded test, and running standard checkpoint and output value steps on Fiori mobile applications, the test object must be fully visible in the Mobile Center remote access window.

This is relevant when editing the test, and not when recording it.

Using the HP Mobile Web browser app

Object Spy

The Object Spy is not supported for mobile browsers.

Checkpoints and output values

Checkpoints and output values cannot be added via the remote access window and must be added manually when editing test steps for mobile browsers.

Invalid URLs

If a test step navigates to an invalid URL, both the address bar and page are displayed as blank.

Run Results Viewer

When tests are run on the HP Mobile Web app, CSS elements may be displayed erroneously in the Captured Data pane of the Run Results Viewer (not relevant for HTML report).

Running Web tests using the HP Mobile Web browser app

Using the Chrome emulator

Multiple tabs

Multiple tabs are not supported, as well as the Browser.OpenNewTab and Browser.CloseAllTabs methods.

Unsupported methods may cause unexpected behavior when run in the emulator.

Object Spy

The Object Spy and Highlight in Application (from the Object Spy) are not supported for the emulator.

Test objects added while recording using the emulator cannot later be highlighted from the object repository.

Checkpoints and output values

Checkpoints and output values cannot be added during recording and must be added manually when editing test steps.

Maintenance mode

Maintenance mode is not supported for the emulator.

Test objects

The WebFile object is not support in the emulator.

The following objects are not supported in the emulator when they are created with the role property:

Link, WebButton, WebList, WebMenu, WebTabStrip, WebTree.

Hybrid applications

The following features are not supported when testing hybrid applications:

Note: Some features not supported for mobile in general are supported when working with hybrid applications. For details, see Unsupported features.

Additional limitations:

Keyword View

In the Keyword View, you may not be able to use the Insert run-time object option in the Select Test Object dialog box to insert a .Object statement for a selected test object.

Workaround: Enter the .Object statement manually.

Text checkpoint and output value steps

When recording and running text checkpoint and output value steps, the test object must be fully visible in the remote access window.

Object identification properties

Do not add or remove object identification properties, as customization is not supported.

WebList steps

Sometimes, when recording a WebList test object step, steps are added for both MobileDropDown and WebList test objects.

This may cause the MobileDropDown step to fail. To avoid this, delete the extra MobileDropDown step.

Recording date and time

Sometimes, when recording the date and time on MobileWeb test objects, native application steps are added in addition to hybrid application steps. This may cause the step to fail during a run session.

Workaround: Delete the extra native application steps.

Run results

CSS elements may be displayed erroneously in the Captured Data pane of the Run Results Viewer (not relevant for HTML report).

Working with ALM

Asset Comparison tool

The Asset Comparison tool does not compare changes in the Record and Run Settings for Mobile tests.

Test object icons

Test object icons for Mobile objects are not displayed in the Test Plan module or for object repositories saved in ALM.

Using Proxy servers

Apache configuration example:

###forward basic authentication###
					ProxyRequests on
				AllowCONNECT 8108 8080 80 7002 443 8443

Localization

Commas as decimal points

Your localized operating system may use commas as decimal points. This is not supported by UFT, and you may need to manually fix recorded steps to use periods as decimal points instead.

It is recommended to always use the period character as a decimal point, regardless of the locale of your operating system.

Simulating events

Simulating events, such as an incoming phone call or SMS, is not supported.

Suggested characters

Steps that include Japanese/Chinese characters that were added from the suggested characters line above the keyboard may not run correctly.

Tests created in earlier versions of UFT

Tests created prior to UFT 12.51

For tests that were created on hybrid applications prior to UFT 12.51, only the text, isEnabled, and isFocused properties are supported for checkpoints and output values.

Additionally, you must do the following to enable your test or component to run properly:

  1. Select the Test was created prior to UFT 12.51... check box before running the test.

    For tests

    Select the File > Test Settings > Mobile Hybrid tab.

    Select the Test was created prior to UFT 12.51 and contains steps on a hybrid mobile app check box.

    For components

    Open the application area, and in the sidebar, select Additional Settings > Mobile Hybrid.

    In the Mobile pane, select the Test was created prior to UFT 12.51 and contains steps on a hybrid mobile app check box.

  2. Make sure that UFT re-installs or restarts the app before running steps on the app.

    You can:

Tests created in UFT 12.02 Patch 1 or earlier

When working with an object repository in a test created in UFT 12.02 Patch 1 or earlier, the following commands are not supported:

Instead, update the test object descriptions from the application (select the test object and click Update from Application).

Caution: If you are working with MobileLabel test objects that are part of a MobileList test object, updating the description from the application can cause your test to behave unexpectedly.

To update the description of a MobileLabel test object from the application, replace it with a MobileList test object.

In the relevant test steps, replace the steps containing MobileLabel.MakeVisible and MobileLabel.Tap with a single step containing MobileList.Select <index>.

For example, replace:

Device("Device").App("UICatalog").MobileLabel("ListViewActivity").MakeVisible
Device("Device").App("UICatalog").MobileLabel("ListViewActivity").Tap

with:

 Device("Device").App("UICatalog").MobileList("list").Select 5

Unsupported features

The UFT Mobile Add-in supports only recording and running steps on mobile applications.

The following UFT abilities are not supported, or are only partially supported, when working with mobile objects: 


Legal Notices

Warranty

The only warranties for Hewlett Packard Enterprise Development LP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HPE shall not be liable for technical or editorial errors or omissions contained herein.

The information contained herein is subject to change without notice.

Restricted Rights Legend

Confidential computer software. Valid license from HPE required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.

Copyright Notice

© Copyright 2016 Hewlett Packard Enterprise Development LP

Trademark Notices

Adobe® is a trademark of Adobe Systems Incorporated.

Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.

UNIX® is a registered trademark of The Open Group.

Red Hat® is a registered trademark of Red Hat, Inc. in the United States and other countries.

Apple and the Apple logo are trademarks of Apple Computer, Inc., registered in the U.S. and other countries.

iPad® is a trademark of Apple Inc.

iPhone® is a trademark of Apple Inc.

Google™ © 2012 Google Inc. All rights reserved. Google and the Google Logo are registered trademarks of Google Inc.


Send documentation feedback