IBM Worklight - Server configuration from application? - ibm-mobilefirst

we are devloping an application using IBM worklight.
we have a requirement that the worklight server may be deployed in other location(that is ip will be changing).
can the app be configured to communicate to the other server through some settings page with out being reinstalled ?

Yes and No.
The official response is that this is not a supported configuration. IBM Worklight will not support this if done.
Technically, you have 2 options:
Use the Worklight Settings page (enabled by default in application-descriptor.xml; Android and iOS only)
In iOS it is external to the app, accessible via Preferences.app
In Android it is accessible via the Options Menu (which is not present starting API Level 13 or so)
This feature is not meant for end-user consumption; you must enter URLs manually. This is not encouraged for anything other than testing
This feature is not customizable
Create your own app-level settings page and follow this: Re-route/Divert some WL.Client Adapter Invocation traffic to WL Server through different URL (for PCI payment and security requirements)?
Again, this is not encouraged. There will not be support provided if this path is chosen
If you feel this is important to your customer, you can submit an RFE and explain your use case for future consideration by Worklight product designers.

Related

Capabilities of Airwatch's Workspace ONE Web browser

My company is evaluating using Airwatch for Mobile Device Management. We have some webapps (PWA / using Service Workers) we use internally. In other posts I read that the administrators may limit the use of the devices' default browsers Safari and Chrome and only allow Airwatch's Workspace ONE Web browser for internal web pages.
Now, my questions are: Does the Workspace ONE Web browser support Progressive Web Apps with service workers?
And additionally, is this browser based on another one, so I'm able to check easily what Workspace ONE Web is capable of (caniuse)?
I would recommend that you review the capabilities directly from VMware. Starting here: https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/9.7/vmware-airwatch-guides-97/GUID-AW97-Features_Matrix.html
PWA's may function differently on Workspace ONE - Web if there are specific controls implemented that could impede the PWA functionality, like local storage. However, you'll likely be able to determine if this is a risk to your project by reading the documentation.

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

How to deploy a local eclipse worklight project in cloud server?

I developed an android based hybrid app in the IBM MFP-7.0., My app is fetching the data from the Java service which is running in Tomcat Server. Here the app adapters are running in my local system MFP server to get the data from the Java service, So that I can only run the app in my local system android emulator. Now, we want to deploy the app in the cloud so that we can give this app to our users. Can some body help me how to run our MFP app in the cloud? Is it required to place eclipse in the cloud to run my MFP server like the way I am running in my local system?
Thanks in advance.
It looks to me like your understanding is completely lacking in this subject matter. Also note that this question has got nothing to do with programming.
You need a host machine. On this server you will run an application server (Tomcat, WebSphere Full profile, WebSphere Liberty profile - either single or a farm, depending on your required network topology and security & scalability needs).
On this application server you deploy MobileFirst
You will also need a database
This host machine needs to be accessible (with appropriate security) to the public Internet so that it could serve apps installed in end-users' devices
The application needs to be configured to send requests to the server (or to any front-side server like a Load Balancer, again, depending on your topology)
The generated application needs to be submitted to an App Store so that users could download and install it on their devices
I suggest that you will do some reading before asking any question. Since you're using IBM MobileFirst, start by reading the user documentation: http://www-01.ibm.com/support/knowledgecenter/SSNJXP/welcome.html

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/

IBM Worklight 6.2. Configure security roles per runtime environment (.war project)

When you access to worklight console you have the list of runtime environments deployed (.war projects). Then you can enter to each environment and operate with the applications, adapters, analytics, etc.
Reading the documentation I found there are several roles you can configure to operate with the worklight console.
The question is if it is possible to configure those roles per runtime environment, or any other way to define different group of users that will have permission to access to each runtime environment.
If it is not, would it be supported to install more than one Worklight console in the same WAS server? This way we could define different roles for each console.
Concerning the question about deploying several Worklight consoles in the same WAS server, the response is yes. You have to use of course different context roots for the different Worklight consoles/Worklight admin services and specify a different value for the JNDI property ibm.worklight.admin.environmentid. The Worklight runtime must have the same ibm.worklight.admin.environmentid that the one used for the console that handles this runtime.
There is no differentiation between runtimes (in either Worklight Foundation 6.2 or MobileFirst Platform Foundation 6.3).
After logging-in (to the Management console), the role the user is applied with will be the one used for any interaction with any runtime.
You may submit an enhancement request: https://developer.ibm.com/mobilefirstplatform/help/