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
Related
I have a set of applications that have been developed by IBM using MobileFirst so it uses Worklight servers and adapters within the application.
I have been requested to investigate the possibilities of taking a hybrid mobile application developed on worklight and trying to migrate it onto something like IBM's BlueMix.
I was hoping someone could provide me with some insight as to how much work may be involved or if this task is even possible?
Thanks in advance.
Assuming you are using MobileFirst Platform Foundation 7.1, you can run your MobileFirst Server on IBM Containers, a technology powered by IBM Bluemix... you can read more about it here: https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/7.1/ibm-containers/
You can start by evaluating it: https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/7.1/ibm-containers/evaluate/
And later, assuming you are an IBM MobileFirst Platform customer, migrate your existing project and applications to it: https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/7.1/ibm-containers/run/
You will also want to experiment with MobileFirst Foundation 8.0 beta: https://mobilefirstplatform.ibmcloud.com/beta/
v8.0 beta also provides an all-new approach for running on Bluemix: https://mobilefirstplatform.ibmcloud.com/tutorials/en/foundation/8.0/ibm-containers/using-mobile-foundation/
Using 8.0 will require some migration effort, but it'll be worth it. :)
You could migrate your adapters and the app integrated with the MFP SDk as is and move it to Bluemix using MFP 7.1 on containers. The effort is minimal - say 2 days. Based on your comments above, If you want to ditch all that and remove worklight out of the equation all altogether, you will have to hand roll all that functionality that worklight was providing to you and of course maintain it yourself. Then this ceases to be a worklight question :) and the effort is certainly more than couple of days.
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/
I tried the integration of these products based on this article and I hit the same problem already documented in the article.
"invocation of javascript function 'getRSSFeeds' has failed: Could not initialize class com.ibm.websphere.objectgrid.ObjectGridManagerFactory
FWLSE0101E: Caused by: [project ExtremeScaleInWorklight]java.lang.NoClassDefFoundError: Could not initialize class com.ibm.websphere.objectgrid.ObjectGridManagerFactory"
It seems that it is caused by a Java class collision of log4j.
My solution was to create a separate Liberty server and install the WXS client for Liberty. This solved the problem, but then I cannot use the WL Development Server anymore which turns the development less efficient.
What is the best way to develop this kind of solution?
I have seen this integration of products on several slides, but I can't find an official guide on how to achieve this. Is there any?
Have You tries to get the IBM WebSphere eXtremeSCale Liberty profile developer tools 8.6 also installed in your WL Development Server ?
SO WXS has two components Client ( libraries) and Serer side components. They can be housed in the same JVM -- for tests, in production this does not really make sense. Serer side hosts storing of objects and enforcing the 'grid management' policies that you may employ using the xml confg files.
perhaps you can use IBM WebSphere eXtremeSCale Liberty profile developer tools 8.6 also installed in your WL Development Server and include then in the classpath.
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.
Can we build commercial apps using the IBM Worklight free Developer Edition?
I searched the IBM official site and I sensed that we have to buy the license to develop commercial apps. But, can someone please clarify it?
Legally speaking: No, you cannot.
Non-Production Limitation
The Program can only be deployed as part of the Licensee's internal
development and test environment for internal non-production
activities, including but not limited to testing, performance tuning,
fault diagnosis, internal benchmarking, staging, quality assurance
activity and/or developing internally used additions or extensions to
the Program using published application programming interfaces.
Licensee is not authorized to use any part of the Program for any
other purposes without acquiring the appropriate production
entitlements.
Technically speaking: you could create an application that does not utilize Worklight features that in order to use them in a production environment, you'd have to buy the Consumer or Enterprise Edition of IBM Worklight.
By doing so you will lose:
The ability to install Worklight Server on an application server
The ability to utilize Worklight Adapters for backend connectivity, that rely on Worklight Server
The ability to secure your application using numerous built-in security features (application authenticity, device provisioning, ...)
The ability to manage your applications (notify, disable, ...)
The ability to remotely update (Direct Update) your applications
The ability to leverage Worklight's unified Push Notifications
The ability to see operational analytics
... and the list goes on.
Instead, you will have to rely on AJAX requests and spend time on (re-)implementing various aspects required for an application (but that's also of course depending on the scope and purpose of the application).
Also see:
https://stackoverflow.com/questions/17030963/ibm-worklight-license-is-worklight-free-to-use/17031953#17031953
IBM Worklight - Limitations of Worklight Studio for Developers
For any inquiries about Worklight I would suggest to contact IBM:
https://www14.software.ibm.com/webapp/iwm/web/signup.do?source=raq&S_TACT=109HE02W&lang=en_US