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.
Related
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
What new features are included as compared to worklight version 6.2 in MobileFirst for hybrid application? I searched a lot on google and IBM site I dont find any new things which are new in 7.1.0 for hybrid application. Can any one suggest new things which are included for hybrid app.
The biggest addition in MobileFirst Platform Foundation 7.0 was Java adapters, enabling you to write JAX-RS applications thus creating flows not possible with JavaScript adapters.
The biggest additions in MobileFirst Platform Foundation 7.1 are the introduction of the OAuth 2.0 security model and as consequence the session-independent mode in the MobileFirst Server. Also introduced were Cordova applications (as opposed to MobileFirst Studio-managed Hybrid apps), allowing more room for applicative wizardry not possible with Hybrid apps.
For an exhaustive list of changes, see the changelogs:
7.0: http://www.ibm.com/support/knowledgecenter/SSHS8R_7.0.0/com.ibm.worklight.getstart.doc/start/c_release_notes.html?lang=en
7.1: http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.getstart.doc/start/c_release_notes.html?lang=en
How to use Java 8 for MobileFirst / Worklight mobile applications? I have always encountered articles that it wouldn't work with Java 8. Any one had luck in using it with Java 8?
At this time, MobileFirst does not support Java8. We're actively working on this and we should be able to announce support "soon". Be aware that there are several different aspects to your issue -
Developer environment; CLI and Studio, and embedded Liberty server
MobileFirst Server, of many different flavors; Liberty, WAS, Tomcat, etc.
Suggest you ask your question again in a week or so, and I should be able to provide a more specific answer.
I am asked to upgrade IBM WebSphere application server 8.0 to 8.5.5 on linux environment. Could you please give me a step by step guide for this migration?
thanks,
Kumar
The simplest method (assuming your WebSphere instances have enough spare CPU/disk/etc) is to build a second WebSphere cell at the new level and migrate applications across one at a time. Access to the application servers should be controlled by either a web server (using the WAS plugin) or an IP sprayer product and which version of app server used should be controlled in that layer. Updating in place has many pitfalls and can be difficult to recover from if something goes wrong which can lead to extended down time for your applications.
My team is working on the migration of a hybrid app from Tibco Silver Mobile(TSM) platform to IBM MobileFirst Platform.
I have a JAX-RS webservice developed using Weblogic IDE which is currently hosted on TSM server. This webservice does a security check for all the incoming back-end requests and pass the request to the back-end if it is from a valid source.
When the app will be migrated from TSM to MobileFirst platform the TSM server will be moved out of the scene. I am looking for some alternate options for hosting this JAX-RS webservice. I don't want to make any changes to the webservice since it is a tested and proven code used in the TSM based solution.
I understand from the IBM MobileFirst Platform 7.0 documentation that JAX-RS support is now available on the MobileFirst Server and JAX-RS specification based Java adapters can be developed and deployed to the server.
Can I deploy the above mentioned webservice .WAR file as such to MobileFirst Server, without making any customizations?
If yes, what is the procedure for deploying the webservice (.WAR) to MobileFirst Server?
If no, what are the alternate options that can be considered?
As indicated in the comments above:
MFP Server is actually a Java EE application deployed to a supported Java EE application server, WebSphere Liberty or full WebSphere ND being the normal options, though TomCat is also supported.
In principle your own JAX/RS WAR file can be deployed to these same servers, the details will depend upon exactly what Java EE features you exploit and you will need to understand those Java EE servers' administration model. MFP itself is not affected by this, and you need no MFP knowledge to do it. You just need to understand the chosen Java EE server. Personally I would start with WebSphere Liberty.
A further question would be whether it is better to isolate your JAX/RS and Mobile First servers into their own Java EE server instances. It can be easier to manage and scale if you keep things separate, but technically there should be no interference if you do co-locate them. It is pretty trivial to spin up a dedicated Liberty server.
A more interesting question is whether there is value in actually exploiting the MFP Adapter capability to create JAX/RS services. In effect it's your familiar JAX/RS programming model but packaged slightly differently, deployed as a MFP adapter, and with the option explicitly to exploit the MFP security model and easily call other MFP adapters.
Personally, if I were coming to a project with no existing JAX/RS services and have commited to MFP and its security model then I would do my JAX/RS in the MFP Adapters.