HPE Software Products: Mobile Center
Share |

ALM Integration with Mobile Center - Incorrect Login - SolutionOpen in a New Window

Hi,

I thought it worth posting this as it wasn't that intuitive imo.  To use the ALM Integration with Mobile Center, which allows the selection of the device from the test set, it is necessary to have the right version of ALM and perform the configuration from the help.  The COMMUNITY_SECURITY_PASSPHRASE for Mobile Center must be set to the same as in ALM.  There is one of those notes there.... but the section begins with an If, and talks about Single Sign-On tokens.  I ignored because of not using SSO...... this was wrong.  Set the value in Mobile Center to the same value as in ALM.

Paul

 

WEBVIEW is not available for hybrid appOpen in a New Window

I am trying to test an hybrid app (cordova, crosswalk build) in a real android device. I am using Appium in order to use selenium. I am able to launch the app in the device but its not possible to switch to the WEBVIEW, the reason is only one context is available that is NATIVE_APP.

But I can debug the app using chrome remore debug & can inspect the elements.

Here is the capabilities I am setting. 

capabilities.setCapability("platformName", "Android");
capabilities.setCapability("uuid", "3300f358d02c5297");
capabilities.setCapability("userName", "user");
capabilities.setCapability("password", "pass");
capabilities.setCapability("appPackage", "package");
capabilities.setCapability("appActivity","activity");
AndroidDriver driver = new AndroidDriver(new URL("mobile center url"), capabilities);

Without the WEBVIEW its really hard to inspect the elements. Can anyone tell me what can be the reason of not getting the WEBVIEW context?

 

Error 2049Open in a New Window

I get the error message 2049 " unexpected error from HPE Mobile Center" after wich i make in "open application in HPE Mobile Center" settings. I would like to know what is this error.

 

Mobile center connection with win 10 mobileOpen in a New Window

We need to automate a win10 miobile app which interacts with win10 PC (in which mobile connector is installed), using UFT and mobile center. Does mobile center provide support for the same  (win10 mobile app)? [Note: Same has been achived for combination of android and win10 PC, using UFT and mobile center]

 

New Release - Mobile Center 2.2 with immediate effect!Open in a New Window

Ease of use and flexibility are the core themes for this latest release of Mobile Center 2.2. From developers to test automation engineers, mobile app administrators and business/application owners, MC 2.2 has made their respective tasks easier. Some of the new features of interest to customers include video/camera sensor simulation, support of LDAP/Active Directory for ease of management, quick ad hoc, exploratory testing on the go and most importantly, 4 new licensing options to cater to every customers’ needs. Read on here to learn more about what’s new in MC2.2.

Lastly, save the date and come join us in one of these webinars:

  • Feb 2nd: Supporting the Idea Economy in the world of finance

This is a re-run of Discover London session. Prospective customers will be interested to learn how WorldPay support the idea economy and achieved high return on investment through its use of HPE UFT and Mobile Center. Check out link here.

 

Configure MC server to run on privileged port (Linux)Open in a New Window

 

In Linux OS the usage of ports less than 8080 restricted to root user.

The MC is not running as a root. You can easily configure MC to run there on port 8080 or 8443.

But if there is a need to run it on 80 or 443, we can try the following workaround:

1.       Install MC server with 443 port

2.       Run the following command (as root):            

                     setcap CAP_NET_BIND_SERVICE=+eip /usr/sbin/nginx

3.       Start the service

This will allows MC to run on priveleged port (like 80 or 443).

 

 

Connecting Windows Phone - WP-start-hpmc.batOpen in a New Window

I'm using HPE Mobile Phone 2.01 through a connector. I connected Android devices without problems.

This time I'm trying to connect a Windows Phone (8.1 update 2).

I've registered the phone (with the sdk that comes with Visual Studio 2015) and when I connected the phone to the PC the phone is recognized as a new storage unit.

When I connect the phone and execute WP-start-hpmc.bat (with admin priviledges) the phone appears in the Devices section but blurred and with state: disconnected.

As I execute the command WP-start-hpmc.bat the log indicates this:

 

Ejecutando (\\BT-NB-LEMI\ROOT\CIMV2:Win32_Process.Handle="6980")->terminate()
Ejecución correcta del método.
Parámetros de salida:
instance of __PARAMETERS
{
ReturnValue = 0;
};
Ejecutando (\\BT-NB-LEMI\ROOT\CIMV2:Win32_Process.Handle="5576")->terminate()
Ejecución correcta del método.
Parámetros de salida:
instance of __PARAMETERS
{
ReturnValue = 0;
};
nginx: [error] OpenEvent("Global\ngx_reload_6980") failed (2: FormatMessage() error:(15100))
"C:\Program Files\HPE Mobile Center Connector\connector\wrapper\/../jre/bin/java.exe" -Xmx30m -Djna_tmpdir="C:\Program Files\HPE Mobile Center Connector\connector\wrapper\/tmp" -Djava.net.preferIPv4Stack=true -jar "C:\Program Files\HPE Mobile Center Connector\connector\wrapper\/wrapper.jar" -c "C:\Program Files\HPE Mobile Center Connector\connector\wrapper\/wrapper.conf"
YAJSW: yajsw-beta-12.04
OS : Windows 8.1/6.3/amd64
JVM : Azul Systems, Inc./1.7.0_76/C:\Program Files\HPE Mobile Center Connector\connector\jre/64
ene 18, 2017 6:17:44 PM org.apache.commons.vfs2.VfsLog info
INFORMACIËN: Using "C:\Users\LEONAR~1.MIR\AppData\Local\Temp\vfs_cache" as temporary files store.
wrapper|YAJSW: yajsw-beta-12.04
wrapper|OS : Windows 8.1/6.3/amd64
wrapper|JVM : Azul Systems, Inc./1.7.0_76/C:\Program Files\HPE Mobile Center Connector\connector\jre/64
wrapper|create script: C:\Program Files\HPE Mobile Center Connector\connector/wrapper/killRelatedProcesses.groovy
-D{}: {}
io.netty.leakDetection.level
simple
-D{}: {}
io.netty.leakDetection.maxRecords
4
java.nio.ByteBuffer.cleaner: {}
available
java.nio.Buffer.address: {}
available
Platform: Windows
Java version: {}
7
-Dio.netty.noUnsafe: {}
false
sun.misc.Unsafe: {}
unavailable
-Dio.netty.noJavassist: {}
false
Javassist: unavailable
You don't have Javassist in your class path or you don't have enough permission to load dynamically generated classes. Please check the configuration for better performance.
-Dio.netty.tmpdir: {} (java.io.tmpdir)
C:\Users\LEONAR~1.MIR\AppData\Local\Temp
-Dio.netty.bitMode: {} (sun.arch.data.model)
64
-Dio.netty.noPreferDirect: {}
true
Your platform does not provide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to avoid potential system unstability.
wrapper|create script: C:\Program Files\HPE Mobile Center Connector\connector/wrapper/restartRelatedService.groovy
wrapper|create script: C:\Program Files\HPE Mobile Center Connector\connector/wrapper/startRelatedService.groovy
wrapper|create script: C:\Program Files\HPE Mobile Center Connector\connector/wrapper/stopRelatedServices.groovy
wrapper|start from Thread main
wrapper|set state IDLE->STARTING
checkRemainConc C:\Program Files\HPE Mobile Center Connector\connector/wrapper/startRelatedService.groovy 5
wrapper|starting Process
wrapper|starting controller
wrapper|executed script: C:\Program Files\HPE Mobile Center Connector\connector/wrapper/startRelatedService.groovy 5
wrapper|binding to port 15003
-Dio.netty.initialSeedUniquifier: 0x3f3227399ba44943 (took 1 ms)
-Dio.netty.allocator.type: {}
unpooled
-Dio.netty.threadLocalDirectBufferSize: {}
65536
-Dio.netty.maxThreadLocalCharBufferSize: {}
16384
Loopback interface: {} ({}, {})
lo
Software Loopback Interface 1
127.0.0.1
{}: {} (non-existent)
\proc\sys\net\core\somaxconn
200
wrapper|Controller State: UNKNOWN -> WAITING
wrapper|binding successfull
wrapper|controller started
wrapper|working dir C:\Program Files\HPE Mobile Center Connector\connector\jetty
system.env 56
env result 58
wrapper|spawning wrapped process
wrapper|is running: false pid=(-1<=0)
wrapper|exec: "C:\Program Files\HPE Mobile Center Connector\connector\jre\bin\java.exe" -classpath "C:\Program Files\HPE Mobile Center Connector\connector\wrapper\wrapperApp.jar;C:\Program Files\HPE Mobile Center Connector\connector\jetty\start.jar;C:\Program Files\HPE Mobile Center Connector\connector\jetty\start.jar" -XX:MaxPermSize=128m -XX:+UseParallelGC -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=HPHeapDump.txt "-Dconsole.home=C:\Program Files\HPE Mobile Center Connector\connector" "-Djetty.home=C:\Program Files\HPE Mobile Center Connector\connector/jetty" "-Djetty.base=C:\Program Files\HPE Mobile Center Connector\connector/jetty" "-Djetty.pid=C:\Program Files\HPE Mobile Center Connector\connector/jetty/jetty.pid" "-Djetty.state=C:\Program Files\HPE Mobile Center Connector\connector/jetty/jetty.state" "-Djetty.logs=C:\Program Files\HPE Mobile Center Connector\connector/log" "-Dpath=C:\Program Files\HPE Mobile Center Connector\connector/conf" -Dfile.encoding=UTF-8 -Djava.net.preferIPv4Stack=true -Xms512m -Xmx512m "-DJETTY_HOME=C:\Program Files\HPE Mobile Center Connector\connector/jetty" "-DJAVA_HOME=C:\Program Files\HPE Mobile Center Connector\connector/jre" "-DCONSOLE_HOME=C:\Program Files\HPE Mobile Center Connector\connector" -Dwrapper.port=15003 -Dwrapper.key=-8519700503074142639 -Dwrapper.teeName=-8519700503074142639$1484774264934 "-Dwrapper.tmp.path=C:\Program Files\HPE Mobile Center Connector\connector\wrapper\/tmp" "-Djna_tmpdir=C:\Program Files\HPE Mobile Center Connector\connector\wrapper\/tmp" "-Dwrapper.config=C:\Program Files\HPE Mobile Center Connector\connector\wrapper\wrapper.conf" org.rzo.yajsw.app.WrapperJVMMain
wrapper|waiting for termination of process
wrapper|created jva.pid file C:\Program Files\HPE Mobile Center Connector\connector\wrapper\app.pid
wrapper|started process with pid 2820
wrapper|set state STARTING->RUNNING
wrapper|GetExitCodeProcess returned 259
wrapper|getExitCode -2 processINFO==null=false
wrapper|is running: true 2820 -2
wrapper|waitFor -1
wrapper|GetExitCodeProcess returned 259
wrapper|getExitCode -2 processINFO==null=false
wrapper|is running: true 2820 -2
wrapper|1waitFor
wrapper|2waitFor
wrapper|GetExitCodeProcess returned 259
wrapper|getExitCode -2 processINFO==null=false
wrapper|is running: true 2820 -2
wrapper|WaitForSingleObject +
2820/0|[INFO] StandardFileSystemManager - Using "C:\Users\LEONAR~1.MIR\AppData\Local\Temp\vfs_cache" as temporary files store.
2820/0|APP user name=leonardo.miro
2820/0|APP working dir=C:\Program Files\HPE Mobile Center Connector\connector\jetty
2820/0|APP java version=1.7.0_76
2820/0|APP class path=C:\Program Files\HPE Mobile Center Connector\connector\wrapper\wrapperApp.jar;C:\Program Files\HPE Mobile Center Connector\connector\jetty\start.jar;C:\Program Files\HPE Mobile Center Connector\connector\jetty\start.jar
2820/0|APP library path=C:\Program Files\HPE Mobile Center Connector\connector\jre\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program Files\HPE Mobile Center Connector\connector\jre\bin;C:\Program Files\HPE Mobile Center Connector\connector\openssl\bin;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\HP\Virtual User Generator\strawberry-perl\perl\bin;C:\Program Files (x86)\Skype\Phone\;C:\Users\leonardo.miro\.dnx\bin;C:\Program Files\Microsoft DNX\Dnvm\;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\Program Files\Microsoft SQL Server\120\Tools\Binn\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;.
2820/0|Application args: no args
2820/0|mainClass/jar/script: null/start.jar/null
2820/0|external stop false
2820/0|args:
2820/0|--lib=C:\Program Files\HPE Mobile Center Connector\connector/conf
2820/0|terminated WrapperManager.init()
2820/0|connecting to port 15003
2820/0|WrapperManager: channel connected, sending key
-D{}: {}
io.netty.buffer.bytebuf.checkAccessible
true
2820/0|Controller State: WAITING -> ESTABLISHED
-Dio.netty.recycler.maxCapacity.default: {}
262144
2820/0|Controller State: ESTABLISHED -> LOGGED_ON
2820/0|Correct key
2820/0|app already logged on -> rejecting new connection
2820/0|unexpected connection closed: /127.0.0.1:16056
2820/0|2017-01-18_18:17:48.865 INFO org.eclipse.jetty.util.log - Logging initialized @2704ms
2820/0|2017-01-18_18:17:48.912 WARN o.e.jetty.server.HomeBaseWarning - This instance of Jetty is not running from a separate {jetty.base} directory, this is not recommended. See documentation at http://www.eclipse.org/jetty/documentation/current/startup.html
2820/0|2017-01-18_18:17:49.225 INFO org.eclipse.jetty.server.Server - jetty-9.2.10.v20150310
2820/0|2017-01-18_18:17:49.256 INFO o.e.j.server.AbstractNCSARequestLog - Opened C:\Program Files\HPE Mobile Center Connector\connector\log\2017_01_18.access.log
2820/0|2017-01-18_18:17:49.256 INFO o.e.j.d.p.ScanningAppProvider - Deployment monitor [file:/C:/Program%20Files/HPE%20Mobile%20Center%20Connector/connector/jetty/webapps/] at interval 1
2820/0|app already logged on -> rejecting new connection
2820/0|unexpected connection closed: /127.0.0.1:16057
2820/0|SLF4J: Class path contains multiple SLF4J bindings.
2820/0|SLF4J: Found binding in [jar:file:/C:/Program%20Files/HPE%20Mobile%20Center%20Connector/connector/jetty/webapps/hp4m-connector/WEB-INF/lib/logback-classic-1.0.12.jar!/org/slf4j/impl/StaticLoggerBinder.class]
2820/0|SLF4J: Found binding in [jar:file:/C:/Program%20Files/HPE%20Mobile%20Center%20Connector/connector/jetty/lib/ext/logging/logback-classic-1.1.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
2820/0|SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2820/0|SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
2820/0|18:17:57,006 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.groovy]
2820/0|18:17:57,006 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml]
2820/0|18:17:57,006 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [file:/C:/Program%20Files/HPE%20Mobile%20Center%20Connector/connector/jetty/webapps/hp4m-connector/WEB-INF/classes/logback.xml]
2820/0|18:17:57,006 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs multiple times on the classpath.
2820/0|18:17:57,006 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [file:/C:/Program%20Files/HPE%20Mobile%20Center%20Connector/connector/jetty/webapps/hp4m-connector/WEB-INF/classes/logback.xml]
2820/0|18:17:57,006 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [file:/C:/Program%20Files/HPE%20Mobile%20Center%20Connector/connector/jetty/resources/logback.xml]
2820/0|18:17:57,162 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set
2820/0|18:17:57,178 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - Setting ReconfigureOnChangeFilter scanning period to 5 seconds
2820/0|18:17:57,178 |-INFO in ReconfigureOnChangeFilter{invocationCounter=0} - Will scan for changes in [[C:\Program Files\HPE Mobile Center Connector\connector\jetty\webapps\hp4m-connector\WEB-INF\classes\logback.xml]] every 5 seconds.
2820/0|18:17:57,178 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - Adding ReconfigureOnChangeFilter as a turbo filter
2820/0|18:17:57,178 |-INFO in ch.qos.logback.core.joran.util.ConfigurationWatchListUtil@7905e210 - Adding [file:/C:/Program%20Files/HPE%20Mobile%20Center%20Connector/connector/jetty/webapps/hp4m-connector/WEB-INF/classes/logbackInt.xml] to configuration watch list.
2820/0|18:17:57,193 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]
2820/0|18:17:57,193 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT]
2820/0|18:17:57,256 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]
2820/0|18:17:57,256 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [FILE]
2820/0|18:17:57,272 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
2820/0|18:17:57,303 |-INFO in ch.qos.logback.core.rolling.FixedWindowRollingPolicy@713cc682 - No compression will be used
2820/0|18:17:57,303 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - Active log file name: C:\Program Files\HPE Mobile Center Connector\connector/log/connector.log
2820/0|18:17:57,303 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - File property is set to [C:\Program Files\HPE Mobile Center Connector\connector/log/connector.log]
2820/0|18:17:57,303 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]
2820/0|18:17:57,303 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [DEVICE_HEALTH_FILE]
2820/0|18:17:57,318 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
2820/0|18:17:57,318 |-INFO in ch.qos.logback.core.rolling.FixedWindowRollingPolicy@4d0cbae2 - No compression will be used
2820/0|18:17:57,318 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[DEVICE_HEALTH_FILE] - Active log file name: C:\Program Files\HPE Mobile Center Connector\connector/log/device_health.log
2820/0|18:17:57,318 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[DEVICE_HEALTH_FILE] - File property is set to [C:\Program Files\HPE Mobile Center Connector\connector/log/device_health.log]
2820/0|18:17:57,318 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]
2820/0|18:17:57,318 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [ACCESS_LOGGER]
2820/0|18:17:57,318 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
2820/0|18:17:57,318 |-INFO in ch.qos.logback.core.rolling.FixedWindowRollingPolicy@7ec172f2 - No compression will be used
2820/0|18:17:57,318 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[ACCESS_LOGGER] - Active log file name: C:\Program Files\HPE Mobile Center Connector\connector/log/WSaccess.log
2820/0|18:17:57,318 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[ACCESS_LOGGER] - File property is set to [C:\Program Files\HPE Mobile Center Connector\connector/log/WSaccess.log]
2820/0|18:17:57,318 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.classic.sift.SiftingAppender]
2820/0|18:17:57,318 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [FILE-THREAD]
2820/0|18:17:57,334 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.sift.MDCBasedDiscriminator] for [discriminator] property
2820/0|18:17:57,334 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]
2820/0|18:17:57,334 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [DEVICE_CONNECTION_FILE]
2820/0|18:17:57,334 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
2820/0|18:17:57,334 |-INFO in ch.qos.logback.core.rolling.FixedWindowRollingPolicy@4e61aee1 - No compression will be used
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[DEVICE_CONNECTION_FILE] - Active log file name: C:\Program Files\HPE Mobile Center Connector\connector/log/device_connections.log
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[DEVICE_CONNECTION_FILE] - File property is set to [C:\Program Files\HPE Mobile Center Connector\connector/log/device_connections.log]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [VNCLAUNCHER]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.rolling.FixedWindowRollingPolicy@6f205dfa - No compression will be used
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[VNCLAUNCHER] - Active log file name: C:\Program Files\HPE Mobile Center Connector\connector/log/vncLauncher.log
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[VNCLAUNCHER] - File property is set to [C:\Program Files\HPE Mobile Center Connector\connector/log/vncLauncher.log]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [WEBSOCKIFY]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.rolling.FixedWindowRollingPolicy@35fa0115 - No compression will be used
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[WEBSOCKIFY] - Active log file name: C:\Program Files\HPE Mobile Center Connector\connector/log/websockify.log
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[WEBSOCKIFY] - File property is set to [C:\Program Files\HPE Mobile Center Connector\connector/log/websockify.log]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [AWS]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.rolling.FixedWindowRollingPolicy@305d2562 - No compression will be used
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[AWS] - Active log file name: C:\Program Files\HPE Mobile Center Connector\connector/log/aws.log
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[AWS] - File property is set to [C:\Program Files\HPE Mobile Center Connector\connector/log/aws.log]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.rolling.RollingFileAppender]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [WS_KEEPALIVE_LOGGER]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.rolling.FixedWindowRollingPolicy@33415dbc - No compression will be used
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[WS_KEEPALIVE_LOGGER] - Active log file name: C:\Program Files\HPE Mobile Center Connector\connector/log/connectorKeepAlive.log
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[WS_KEEPALIVE_LOGGER] - File property is set to [C:\Program Files\HPE Mobile Center Connector\connector/log/connectorKeepAlive.log]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [device] to INFO
2820/0|18:17:57,350 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [device] to false
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [DEVICE_CONNECTION_FILE] to Logger[device]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [deviceHealth] to INFO
2820/0|18:17:57,350 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [deviceHealth] to false
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [DEVICE_HEALTH_FILE] to Logger[deviceHealth]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [accessLogger] to INFO
2820/0|18:17:57,350 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [accessLogger] to false
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [ACCESS_LOGGER] to Logger[accessLogger]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [vncLauncher] to INFO
2820/0|18:17:57,350 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [vncLauncher] to false
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [VNCLAUNCHER] to Logger[vncLauncher]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [websockify] to INFO
2820/0|18:17:57,350 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [websockify] to false
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [WEBSOCKIFY] to Logger[websockify]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [aws] to INFO
2820/0|18:17:57,350 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting additivity of logger [aws] to false
2820/0|18:17:57,350 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [AWS] to Logger[aws]
2820/0|18:17:57,350 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [HPMC-WebSocket-KeepAlive] to INFO
2820/0|log4j:WARN No appenders could be found for logger (org.springframework.web.context.ContextLoader).
2820/0|log4j:WARN Please initialize the log4j system properly.
2820/0|log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

 

I checked and saw many problems, many of then maybe warnings. But I can't found what the real problem is.

If you cant give me a hint about this let me know.

 

HPMC Enabler - required resources (OS X)Open in a New Window

Hi. In the past I've been able to sign ipa files with HPMC Enabler, but with the necessary upgrade of OS X I started to have problems to do it.

Is it possible that HPMC Enabler works in OS X beyond OS X 10.8 or 10.9?

I'm trying to sign ipa files with HPMC Enabler in OS X 10.11 and OS X 10.12 and I keep receiving the same message in GUI version and command line tool: "Error:: Codesigning app failed".

I've even tried the signing with HPMC Enabler 1.52 p1 and HPMC Enabler 2.01, as both have the same required resources.

If you can give me any feedback or help about this, please let me know

 

Ionic App and Mobile Center Testing CapabilitiesOpen in a New Window

Hello all,

I am developing a hybrid app through Ionic V2 and I wanted to be sure that the Mobile Center's testing capabilities are compatible with the AngularJS/CSS/HTML that Ionic uses. I know the UTF feature is compatible with hybrid apps, but can anyone speak to any of the other testing or monitoring SaaS features? 

 

Connecting Mobile Center to UFT - Connection failed: Unsupported Mobile Center versionOpen in a New Window

Hi,
I'm evaluating UFT and Mobile Center as an option for our automation framework. I downloaded the Windows HPMC server trial which gave me the MC201_Windows_Server.iso. When I mount and install this it installs the MC 2.0.0 version rather than 2.0.1 If I try to connect to UFT Trial version (v12.54.3256.0), in UFT I see the error: "Connection failed: Unsupported Mobile Center Version." I'm assuming this would not be an issue with 2.0.1 MC server.
Connection failed: Unsupported Mobile Center version. It doesn't say which version is required unfortunately.  Any ideas on how I can proceed?

Thanks,

Matt

 

Mobile Center Installation fails -Postgre Database Installation errorOpen in a New Window

 Installation of MC fails...

2017-01-12 20_08_51-Program Manager.jpg

 

Object Spy does not recognize objects from an app just shows "Device"Open in a New Window

Hi,

I'm using Mobile Center 2.01 and UFT 12.54. I'm trying to make a script with an app, but when I use object spy to store the objects of the app it shows just "Device". The app was already installed in the device, but I have also tried to upload it from Mobile center (Not packaged).

The strange thing is that other apps already installed in the device are recognized ok.

I have tested the same app with 2 devices and it's the same behaviour.

The app is "Mi Vodafone" (https://play.google.com/store/apps/details?id=es.vodafone.mobile.mivodafone&hl=es)

Many thanks in advance

Irene

 

HP Mobile Center 2.01 installation failureOpen in a New Window

I am installing HP Mobile Center 2.01 on windows 10 machine.

After 56% installation completion, the system throws an error msg - Failed to install local psotgres database.

Repeated the installtion 4 times by cleaning up the previously created installtion folder. However it is aborting at the same step every time and hence not able to complete the installation. Please guide me to overcome this problem.

 

 

Cannot recognize the WebApplication objects on Mobile devices through Object repositoryOpen in a New Window

Hello,

We are using Mobile center 2.0.1 licensed version with UFT 12.54.
We have a Web application to be automated in mobile device  and for that we are using "Mobile Center browser".
In 2.0.1 ,After adding any object into object repository, it gets added as "Browser.Page.Object" but, the same objects doesnot get highlighted or recognised through Object repository or through Script.

In older versions of Mobile Center i.e 1.52 the same objects were getting identified as "Device.App.WebView.Page.Object".

In Mobile center 2.0.1 ,In our Object repository, we created the same heirarchy("Device.App.WebView.Page.Object") and found that the  objects which were not recognised earlier using the 2.0.1 are getting identified successfully.

We tried recording option of UFT and found that the objects which are added to local repository during recording are getting highlighted and recognised in Mobile device successfully though they are added with "Browser.Page.Object" hierarchy.

The Object identification issue is observed only when we added the objects manually into the object repository.
Can you provide the resoluition for the same.

 

 

 

Mobile Center 2.01 Object identification queries which needed to be addressed on priorityOpen in a New Window

I am using UFT 12.53 and HP Mobile Web browser, while spying an object through Object Spy the object properties are displayed with hierarachy Browser >> Page >> Object,.

In previous version of Mobile center same objects were getting identified by hierarchy Device>>Application>>MobileWebView>>Object. If i Spy any object in HP Mobile Web browser and check the browser Version it is displayed as Chrome.

We are testing a WebApplication on both Desktop browsers and Mobile browsers
Below are my questions,would request you to go through the same and provide your inputs :

1. So does that mean there wont be any device dependency while identifying any object through Object repository.

2. After 2.0.1 The scope of Device Id and Application identifier will be just to launch a device. Device ID and Application Identifier wont play any role in object identification when the object is added into the Object repository.
Am I right? Please confirm.

3. We are using BPT framework and we run scripts on multiple devices. While using MC 1.52  objects gets added into the object repository with  "Device>>Application>>Mobileview" hierarchy. So when we will upgrade mobile center to 2.0.1, at that time we dont need this hierarchy in our Object repository? Will it support both the heirarchy (Browser>>Page  and Device>>Application>>Mobileview)?

4. Can we use the same scripts and objects  created on Desktop chrome browser on Android Mobile center web browser and Android Chrome browser and iOS device safari browser?

 

Thanks,

Shardul 

 

penatration testing reportOpen in a New Window

I want to generate mobile app (windows/ ios/ android) penatration testing report. How can i get these reports?
is is possible to generate report using 15 day trial version ?

 

Updating HPMC License -Open in a New Window

I needed to update the license of HPMC and after doing it I was able to access HPMC site again but when I connect Android or IOS devices they keep the state "not available". I checked the logs and the connector log show multiple times this messsage:

 

[2016-12-21 16:41:50,162] [] [] [] [] [] [] [qtp1039825477-18] [INFO] [HPMC-Filters] Request Path= /connector/validateVersion (CLS=c.h.m.filter.AuthenticationFilter)

[2016-12-21 16:41:50,162] [] [] [] [] [] [] [qtp1039825477-18] [INFO] [HPMC-Filters] request come from: 127.0.0.1 (CLS=c.h.m.filter.AuthenticationFilter)

[2016-12-21 16:41:50,165] [] [] [] [] [] [] [qtp1039825477-18] [WARN] [c.h.m.s.impl.DatPropertiesService] cant read from property file from classpath, using filesystem path '' (CLS=c.h.m.s.i.AbstractPropertiesServiceImpl)

[2016-12-21 16:41:50,182] [] [] [] [] [] [] [qtp1039825477-13] [INFO] [HPMC-Filters] Request Path= /client/certificate/login (CLS=c.h.m.filter.AuthenticationFilter)

[2016-12-21 16:41:50,183] [] [] [] [] [] [] [qtp1039825477-13] [INFO] [HPMC-Filters] request come from: 127.0.0.1 (CLS=c.h.m.filter.AuthenticationFilter)

[2016-12-21 16:41:50,241] [] [] [] [] [] [] [qtp1039825477-13] [ERROR] [c.h.m.s.impl.CustomerServiceImpl] The certificate is not valid or expired ... (CLS=c.h.m.s.impl.CustomerServiceImpl)

 

Could be a problem with the license?

 

Please let me know

 

Details:

- Red Hat Enterprise 6.5

- Mobile Center 1.52 + Patch 1

 

Mobile Center Error Code 1009Open in a New Window

Im trying to execute a test script using MJobile center. After launching the Application on device error syats "Connection with the Application Losy 1009"

 

HPMC Enabler - extended log?Open in a New Window

I'm working with new ipas that I need to upload to HPMC. When I tried to sign them manually with HPMC Enabler command line (following the instructions in http://mobilecenter.hpe.com/Content/Package_HPMC_Enabler.htm) I found that the process fails because of an error in codesigning.

The thing is: I'm using the same provision profile and developer certificate that worked fine some time ago. I check the Keychain access seeing that the developer certificate is fine and also take a look at the provision profile in the apple developer site. Both seems to be correct.

How can I found more details of the HPMC Enabler process? is there some kind of extended log to enable in the signing process so I can have a better scope of the problem?

Let me know

 

Ps: I also tried the gui version of Enabler and obtained the same result.

 

Details:

- Red Hat Enterprise 6.5

- Mobile Center 1.52 + Patch 1

- HPMC Enabler 1.52p1

 

Clarity on Mobile Center 2.01 patch 1 install instructionsOpen in a New Window

Hi,

I have a Mobile Center 2.01 Server running on Windows, and a connector running on Linux (CentOS Essentials).

Please confirm that I have understood the install correctly:

1.  Download the Linux Connector patch and run the .bin on the Linux machine as root.  This ends with a message saying successful install.

2. Restart the Linux Connector and confirm that I can connect to and use Android devices.  Connector version (from the dat folder) is 2.01.01.00.421.

I don't need to patch anything server side.

3. Download the patched version of HPMC Enabler.  Run this to resign the iOS agent and launcher files.

4. Copy the agent and launcher files to the connector.

5. Restart the connector.  Test with an iOS device running the latest version of iOS.

That's it?

The Server version should be 2.01.2744.

Regards

Paul 

 

Contact Us

Vivit Worldwide
P.O. Box 18510
Boulder, CO 80308

Email: info@vivit-worldwide.org

Mission

Vivit's mission is to serve
the Hewlett Packard
Enterprise User
Community through
Advocacy, Community,
and Education.