IBM Worklight 6.2 - decode proguard obfuscated trace - ibm-mobilefirst

Is it possible to use IBM Worklight Log and Analytics feature to upload and decode obfuscated crash reports (e.g. ProGuard or the iOS alternative) to the Worklight Server?

Android ProGuard is currently not supported in Worklight (5.x - 6.2.0.x) applications, so in that respect this option is not available regardless. I am not familiar with an iOS equivalent to ProGuard.
AFAIK the Worklight Operational Analytics platform does not provide the ability to decode uploaded logs. You can however control what exactly you'd like to upload.

Related

Prevent jailbroken/rooted devices from accessing MFP 7.1

I am trying to understand how the MobileFirst Platform could prevent Jailbroken/rooted devices from accessing its resources.
Does MobileFirst Platform provide this type of security.?
How can we implement it as I could not find any resource to walk us through it?
Thanks.
MobileFirst Platform Foundation does not, in itself, provide any facility to prevent jailbroken / rooted devices from accessing resources. However, you can use MaaS360 or Trusteer to provide this kind of protection as desired.
There's a tech note here that gives an overview of mobile OS features that can be used by various versions of MobileFirst Platform Foundation and Worklight.

how to Manage app and data on a device (Block, Wipe and others) in ibm mobilefirst 8.0

How to Manage app and data on a device (Block, Wipe and others) in ibm mobilefirst 8.0?
Following options are available in Mobilefirst 7.1:
Managing app distribution (using the Application Center)
Managing app versions (using the Operations Console)
Managing app access (using the Operations Console)
Managing usage, performance, warnings and errors (using the Analytics Console)
Managing data access
I suggest that you will take a tour of the MobileFirst Operations Console in MobileFirst Foundation 8.0. See here: https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/8.0/product-overview/components/console/
Managing data access / Managing app access
I assume you are referring to "remote disable". This is available from the application screen in the console. Select the desired registered application from the sidebar navigation and under the Management tab you will see a Application Access title.
Managing usage, performance, warnings and errors (using the Analytics Console)
Unsurprisingly, this is available from the Analytics console as before.
Learn more about Analytics console here: https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/8.0/analytics/console/
Managing app distribution (using the Application Center)
This has not changed and it not related to MobileFirst Foundation 8.0. You do this through the AppCenter console as before. AppCenter did not change between 7.1 and 8.0.
Managing app versions
In previous versions you would have upped the version value in application-descriptor.xml. In v8.0 instead whenever you want to release a new point release, i.e. 1.1 or 2.0 etc, you need to register another app versions, either using the MobileFirst CLI or directly via the console.
I suggest that you will start getting familiar with the product...
Product overview: https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/8.0/product-overview/
Upgrading/Migrating: https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/8.0/upgrading/
Application development: https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/8.0/application-development/

How to Client Side and Server Side integration of IBM TeaLeaf

I have to implement TeaLeaf analytics for our application so i am doing sample POc for android and iphone environment for hybrids application. Anyone please advice me how can i implement the TeaLeaf stuff in my POC.
Below that activity i did,
create sample app version project and add android/iphone environment
application-descriptor.xml i added IBM teaLeaf SDK
what else i have do? i was searching google and following ibm knowledge center also there is not much clarity for tutorial and how can i test in development environment.
below that link i referred :
http://www.ibm.com/support/knowledgecenter/SSHS8R_6.3.0/com.ibm.worklight.integ.doc/integ/t_tealeaf_client.html
If I understand your question correctly, it seems like you're attempting to create a connection between IBM MobileFirst Platform 6.3.0 and IBM Tealeaf. I work on integrations of IBM Tealeaf On-Cloud with client e-commerce platforms and it seems like you might be dealing with IBM Tealeaf On-Premise.
That being said, my understanding of the process for the On-Cloud implementation is that there are a few libraries you need to make sure are being included on pages you'd like Tealeaf to observe:
Tealeaf.js (distributed by IBM)
Sizzle.js
JQuery, if the page uses it ... also note that if the site uses JQuery, you need to provision from IBM the JQuery flavor of Tealeaf.js instead of the W3C flavor.
Hammer.js
Pako.js (again this assumes the On-Cloud version of Tealeaf, as this is a library for compressing data a being sent to IBM cloud-service collectors. In the On-Premise version my understanding is that this data is written to a file that is saved to the local hardware.)
How the libraries are included is something you'd decide when working with the client's server and development team - every organization has their preferences. Generally though they'd be inserted on pages that need to be monitored and the Tealeaf.js config would be edited to specify the endpoint of the collector for the regional data center on which space was provisioned for the client (in the US, either in Dallas or Washington DC.)
As for the On-Premise implementation of Tealeaf, you can jump in to the documentation here: http://www.ibm.com/support/knowledgecenter/SS2MBL/tealeaf_product_family_welcome.html

Push notification does not work on mobilefirst platform 7.1 server

We have develop a cross platform app with mobilefirst studio 7.0 and test it on production environment.
It was fine before we upgrade our project with mobilefirst studio 7.1.0.00-201510120-1525 and test it on clean staging server (7.1.0.0 20151012-1525).
It seems that the push notification functionality dedicated on mobilefirst 7.0 did not work properly on production server of mobilefirst platform version 7.1. The source code and configuration file of our mobilefirst push notifcation adapter and configuration files are here.
Inorder to fix the issue, we refer to official push notification tutorial which was documented here.
Surprisingly, although the source project in official tutorial looks fine on development server, it still not work on production server either.
We have test this project using iphone5s with ios 8.4 and HTC 816h phone with android 4.4.2, both of them fail to register push notification service after we login to the HybridEventSource sample application and tap the “Subscribe Notification” button.
The Mobilefirst server logs down internal server error message during the registration process of client devices.
I am wondering how to let the push notification mechanism work again on mobilefirst 7.1?
Either a valid push notification sample code of mobilefirst 7.1 or any fix pack which we do not know is welcomed.
Since we did not authenticate users via mobilefirst server, and devices were connected through vpn to server,
we prefer to have a solution which does not depends on particular mobilefirst server side authentication mechanism.
The server log message generated during this test is in this file.
The log file generated while we run EventSourceNotification app as xcode project is in this file.
For detail system log from ios device, please refer to device log file
And the Log message generated by HTC 816h android 4.4.2 phone is here
Information about our server environment:
Operating system : centos 5.8 linux
Java development kit : Oracle jdk 1.8 update 65 x86-64
Application server : Apache tomcat server 7.0.63
Worklight environment database : oracle database 11g.
Apple push notification service certificate : sandbox version
Well that's kinda suspicious, isn't it?
Since we did not authenticate users via mobilefirst server, and devices were connected through vpn to server, we prefer to have a solution which does not depends on particular mobilefirst server side authentication mechanism.
You are using the push mechanism provided by MFPF but you do not want to go through MFPF? You are required to go through MFPF if you want to use the push mechanism provided by MFPF... What did you mean by the above?
That said, did your DBA examine mf7-1-EventSourceNotifications-catalina.out.log? There are quite a few Oracle-related exceptions there that you should look at.
If you are still unable to resolve it I suggest to open a PMR instead so that the development team will be able to further investigate.

Worklight 6.2: Is it possible to decommission the device using any WL API

Worklight 6.2: Is it possible to decommission the devices using any Worklight API apart from Licence Tracking in Worklight Server?
Not sure how an API would be of help here.
Anyway, the only available feature that allows you to disable a specific device, is the License Tracking feature you have mentioned in your question.
Feel free to submit feature requests: https://developer.ibm.com/mobilefirstplatform/help/