I am planning to migrate an existing worklight 6.1 application to mobilefirst 7.1.Currently three versions of application are running.
I am following this as my reference :
http://www.ibm.com/support/knowledgecenter/SSHS8R_7.1.0/com.ibm.worklight.upgrade.doc/devenv/c_upgrade_to_srvr_in_production_env.html
But I am going to do some process change in this process because I have a fresh server for mobilefirst 7.1.
As in mobilefirst 7.1, there are many changes in workligth db in compare to worklight 6.1, I will create a configuration first on mf server using server configuration tool. Then I will create a runtime environment for my application with lates mobilefirst 7.1 war.
But while doing that if I give reference of older database(worklight 6.1) as database in server configuration tool for migration , are all version which are currently running on worklight will run without error on mobilefirst 7.1?
Should I keep contextroot of mf runtime same as worklight (previous) ?
All I want is older versions to be up and running after this deployment.
I will enable mf server on same Domain/IP which is configured with worklight 6.1 server.
But while doing that if I give reference of older database(worklight 6.1) as database, are all version which are currently running on worklight will run without error on mobilefirst 7.1?
Not sure what you mean here... You can't have a 7.1 server with a 6.1 database.
What you can have is an application server (liberty, was, tomcat, ...) that runs TWO MobileFirst war files: that of 6.1 and that of 7.1, so that existing 6.1-based apps will continue working as-is, and 7.1 new clients will connect to the new server...
When you have the two servers running, you can then start "migrating" users by blocking the 6.1 app in the MobileFirst Console to the 7.1 version of the app.
If you need further assistance with this, you should open a PMR. Stack Overflow is not the place for this type of question, plus you may need official support, which, again, that's what a PMR is for.
Related
Hi I recently updated MobileFirst Version from 7 to 8 and the application working perfectly on MobileFirst Development Kit Server (with Android, iOS, Browser Environment).
But after I have deploy to on premise MobileFirst Server version 8. What happened is the only environment or platform that visible on server is iOS as you can see in screenshot below.I have successful deploy all 3 platform but the other two platform not visible
We couldn't find any information on IBM knowledge Center website
Thank you.
This happens if, during installation of IBM MobileFirst Platform Server 8.0 ( using Installation Manager), you select the option "Install IBM MobileFirst Platform Foundation for iOS" in the General settings panel. If this option is chosen, iOS will be the only platform visible in the MobileFirst Operations Console.
Once the choice has been made during installation, you cannot reset it later. You will have to uninstall and re-install , and choose not to select "for iOS" option. Keep the default option (No) as-is in the Install IBM MobileFirst Platform Foundation for iOS section of the General settings panel.
Details on each step during installation, can be found in this link.
After applying latest iFix( 8.0.0.0-MFPF-IF201708031112) to the IBM MobileFirst Server 8.0.0 and cordova-mfp-plugin( v8.0.2017072706), MFPF Runtime still shows the older version no (8.0.2017070506). Due to the mismatch of the server runtime version and mfp plugin version we were not able to connect to the server and obtain accessToken in our mobile application.
Below is the version info log captured from server messages.log file.
[8/9/17 10:26:02:750 EDT] 00000025 com.ibm.mfp.server.core.internal.logging.ServerInfoLog I
MFP version: 8.0.0.00-20170803-1112
MFPF runtime version: 8.0.2017070506
Running on server: Liberty, version:8.5.5.8. Running on premise
Running OS: Windows Server 2012 R2, version: 6.3
Java: IBM Corporation, version: 1.7.0
DB name: DB2/NT64, DB version: SQL10058
Application Log:
08-08 20:48:40.935 19080-19112/com.xxxxx E/null: >> Failed to connect to MobileFirst Server{"status":400,"statusText":"Bad Request","responseText":"{\"server_version\":\"8.0.2017070506\", **"errorCode\":\"PROTOCOL_MISMATCH_ERROR\",\"errorMsg\":**"There is a mismatch between the SDK versions used for this application. If you upgraded the SDK, please create a new application version.\"}","errorMsg":"There is a mismatch between the SDK versions used for this application. If you upgraded the SDK, please create a new application version.","errorCode":"PROTOCOL_MISMATCH_ERROR"}
08-08 20:48:40.950 19080-19112/com.xxxxx E/null: Fatal error - Client was unable to connect to MFP Server
The most likely cause of the issue is this -
you had application registrations when your server was at an iFix level prior to February 2017. There were Dynamic app authenticity feature related changes in the February build (details here), which does not apply directly to earlier application registrations. Owing to which due to this it is ending up with "Protocol Mistmatch Error".
In order to resolve the issue, increment your application registration version in MFP Operations Console & in your client application. Rebuild the client application and it should connect to the server successfully.
how to add runtime in ibm mobilefirst 7.1 in remote server ?
As of now I have remote server where already one runtime exist, I have deployed a .wlapp and .adapter file in console and I am testing this on a device and its working fine as mentioned in IBM MobileFirst Platform 7.1 - No runtime environment deployed in this server
Question is how can i add(deploy) another runtime ?
Assuming you have another MobileFirst project, you need to use the IBM Configuration Tool in order to deploy the second .war file. It's basically following the same steps you did for the first .war file, only deploying a different (.war) file...
You can also deploy manually: http://www.ibm.com/support/knowledgecenter/en/SSHS8R_7.1.0/com.ibm.worklight.deploy.doc/admin/c_manually_configuring_app_server.html
I know that there is a separation of the lifecycle of the MFP Studio and MFP Server. What happens if the development team updated the Studio with a fix? In other words, is it supported to deploy a runtime for example v6.3.0.00.20150214-1702 to a MFP Server v6.3.0.00.20141127-1357?
The scenario you've described it a supported scenario. The MFP Server should be able to host a .war file generated from a newer MFP Studio build of the same major version (6.3, and I believe support from this scenario exists starting 6.1 or 6.2).
Of course, if you encounter a problem you should probably open a PMR on that. :)
We've just upgraded our Worklight server to 6.0.0.20140208-1639, and we're now frequently getting in the Websphere standard out log the error:
DeployService W com.worklight.integration.services.impl.DeployServiceImpl syncAdaptersFromDB FWLSE0082W: Failed to deploy adapter. This may be due to a JavaScript error in your adapter implementation (archive: 'C:\Windows\TEMP\HelloWorld6506022860570731839.adapter'). [project worklightEMS]
com.worklight.gadgets.bean.InvalidDeployableException: The 'adapter' version 'null' is different than the version of Worklight Server '6.0.0'.
Use Worklight Studio '6.0.0' to build and deploy the application.
at com.worklight.integration.services.impl.DeployServiceImpl.syncAdaptersFromDB(DeployServiceImpl.java:167)
at com.worklight.integration.services.impl.DeployServiceImpl.access$000(DeployServiceImpl.java:73)
at com.worklight.integration.services.impl.DeployServiceImpl$ClusterSyncAdaptersTransaction.run(DeployServiceImpl.java:513)
at com.worklight.integration.services.impl.DeployServiceImpl$ClusterSyncAdaptersTransaction.run(DeployServiceImpl.java:502)
at com.worklight.core.util.RssBrokerUtils.doInTransaction(RssBrokerUtils.java:132)
at com.worklight.integration.services.impl.DeployServiceImpl.syncAdaptersFromDBTransaction(DeployServiceImpl.java:499)
at com.worklight.gadgets.bean.ClusterDataSynchronizationTask.step(ClusterDataSynchronizationTask.java:42)
at com.worklight.core.tasks.TaskThread.run(TaskThread.java:111)
There is no "HelloWorld" adapter in c:\Windows\TEMP and we can't find any reference to this in the WL project that was deployed to the server. We rebuilt the WAR and deployed to the server using the same patch release.
Any idea why this error is being triggered and what we can do to stop it?
The following are pretty much the issue as yours:
Issues of migrating Worklight from v6.0 to v6.1
IBM Worklight 6.0 - Adapter disappears after it is deployed
IBM Worklight - Project built on 6.1 will not deploy on 6.1 server, says I need to use 6.0
IBM Worklight 6.0.0.1 - Error deploying adapters to server
Worklight Server - Failed to deploy adapter 'LinkAccount.adapter'.
I recommend to review all answers to the above questions.
You can then try to (or/and anything else that will be suggested above):
Rebuild all artifacts (.wlapp, .adapter) with the new Worklight Studio build
Make sure the updated Worklight Server version is installed in the application server
Deploy the freshly generated .war file by Worklight Studio
Deploy all artifacts