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. :)
Related
After installing MobileFirst Platform , It give No run time is there.
My configuration was given below:
1. WebSphere Application Server 8.5
2. Oracle 11g Enterprise edition
3. Mobile-first platform 7.1
Please help me to create Run-time in Mobile first Console.
From where I will download sample war file (for ex: project.war) for creating run-time environment.
You have only mentioned "after installing IBM MobileFirst" and not exactly the steps followed. Configuring IBM MobileFirst Platform has two phases:
a) Installing the application binaries into the filesystem using Installation Manager.
b) Deploying MFP admin services and runtime in to an Application server using Server configuration tool or ANT scripts. The runtime war file needs to be created using IBM MFP Studio.
If you have not performed phase 2 or only installed admin services and not the runtime, go through the information in these links:
Using server configuration tool
Using ANT scripts to deploy
To get you started with various MFP 7.1 projects , you refer and use any of the sample applications available at MFP 7.1 Getting started tutorials.
Once you have any of these sample projects loaded or a new project created in MFP studio, you can build the server side artefacts (adapters, application wlapps and runtime war) within the MFP studio or using ANT scripts:
Refer this link for further details and steps- Deploy projects.
I have a MFP 7.1 server with one runtime currently deployed for use.
Will the application binaries already installed on phones still work after applying the fixpacks?
Or do i have to plan to upgrade the runtime and deploy a new application binary?
The fix pack you apply will typically be to the MobileFirst Studio or the Server runtime. If you've applied it to MobileFirst Studio & rebuilt your app, then this must be redistributed to the end users to gain advantage of any fixes that are part of this fix pack.
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 just upgrade my current mobilefirst studio to latest version. After the Update i can't able to open the my projects.It's showing the following error when tried to open the project.
"Migrating the ProjectName project from version 7.0.0.00.20150610-1353
to version 7.1.0.00.20150807-0630 has failed because There is no
available migration path. Use the latest MobileFirst Studio or the
latest "IBM MobileFirst Studio Upgrader" from IBM Fix Central site
http://www.ibm.com/support/fixcentral/ "
This question is useless without providing a project that demonstrates the failure in upgrade in MobileFirst Studio.
As such, the only alternative I can offer is for you to create a new project in MobileFirst Studio, and copy over into it your web resources to the corresponding folders: the JavaScript, CSS and HTML, as well any custom classes you may have implemented.
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