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.
Related
I am not able to add application into Test Workbench which is built using MFP v8. I am getting an error message while uploading the application into the Test Workbench.
Error message:
: this application is not a supported IBM MobileFirst Platform one. Please consider using IBM Rational Test Workbench
Eclipse version Used:
Eclipse Java EE IDE for Web Developers.
Version: Luna Service Release 2 (4.4.2)
Build id: 20150219-0600
Plug-ins:
IBM MobileFirst Foundation Studio 8.0.0
IBM MobileFirst Platform TestWorkbench 8.7
Test Workbench is not supported for MFP 8.0. Hence the message:
"Error message: : this application is not a supported IBM MobileFirst Platform one. Please consider using IBM Rational Test Workbench"
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.
I need to use maximo anywhere so i have installed worklight server and worklight studio. from worklight studio when trying to deploy adapter on worklight i got this error in console :
Adapter deployment failed
Not Found; Error 404: com.ibm.ws.webcontainer.servlet.exception.NoTargetForURIException: No target servlet configured for uri : /console/api/adapters/upload
What can be the cause of this problem? Can you help me please?
The current suggestion is to upgrade the Studio installation to either the latest 5.0.6.2 iFix level, or to Worklight 6.0, as Worklight 5.0.6 is no longer a supported product level.
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
The following is my setup:
WebSphere Application Server v8.0 express Edition
IBM DB2 10.1 Server Edition
IBM Worklight Server Consumer Edition v6.0
Worklight Studio v6.0 Consumer edition Eclipse plug-in
JDK 1.7
To perform installation task i followed the IBM Worklight v6.0.0 infocenter "Installing & Configuring" section.
After Deploying app on the Application Server when i am accessing app using
localhost:9080/Hello/console it shows the error of "Worklight Project not initialized".
Thanks,
It would help if you edit your question and detail how did you install (deploy) Worklight on your copy of WAS. This will help in finding out any possible errors in your steps.
Please make sure that you follow the instructions as given in the IBM Worklight Information Center: Installing Worklight Server
In addition I've found this technote regarding WAS Liberty, which talks about the same error message: http://www-01.ibm.com/support/docview.wss?uid=swg1PM88638