how to add runtime in ibm mobilefirst 7.1 in remote server - ibm-mobilefirst

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

Related

How to add Runtime environment in mobile first 7.1?

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.

Deploy a war file on a different version of MobileFirst Server

I deployed a war file in a WAS server and when I opened the MobileFirst console it says:
"No runtime environment deployed in this server."
When I checked the logs it says that the mobileFirst version which I generated the war file is 7.1.0 and my server in which I'm going to deploy it is v7.0.0. I want to deploy my war file on our server which is v7.0.0 since that's the one that has a license.
I'm thinking to generate a war file with v7.0.0 on my current environment which is v7.1.0 but I can't figure out how. Anyone?
You cannot create a 7.0.0 .war file when developing using 7.1.0.
7.1 generates 7.1
7.0 generates 7.0
You can deploy 7.0 .war file in 7.1 server
Not the opposite.

MobileFirst 7.1 - How to use CLI for current installed Liberty Core with MobileFirst server

I recently installed Liberty Core server, created a new Profile, installed MobileFirst Platform Server and deployed a MobileFirst runtime environment with the Server Configuration Tool in MacBook.
Instead of installing in default directory(Application/ibm/*) I choose to install under custom directory (Users/username/LibertyCore).
I started the server manually installed adapters and *.wlapp from worklight console.
Instead of doing this manual deployment I want to do it from command line? My understanding is I have to use MFP command line utility.
I installed MFP CLI utility then parsed to the App Project folder to build and deploy to currently installed Liberty Core server I see issue with MFP PUSH it says server is not started though server is running.
So when I do MFP Info I found that CLI is pointing to completely different set up. How can I make CLI to point to currently installed Liberty Server.
Note that you can run "mfp help" to see all available CLI commands.
There is the command "mfp server". Using this command you can add additional server definitions: "mfp server add". Run the command and follow the on-screen instructions to add a server definition for your remote server...
Once you've added it, you can use "mfp push your-remote-server-name" to push the artifacts to the remote server.

Worklight Server error syncAdaptersFromDB

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

Worklight Server - Failed to deploy adapter 'LinkAccount.adapter'.

From the previous problematic and devastation in installation worklight server into our websphere, IBM Worklight 6.1 - Project fails to initialize because the project database schema is from version N/A , we discover new problem after that catastrophic event. First we got this error message
Error 500: javax.servlet.
ServletException: Worklight Console initialization failed.Logged Exception: java.lang.RuntimeException: FWLSE4010E: The project 'xxxx' failed to initialize, because the project WAR file is not supported by the server from version 6.1.0.00.20131126-0630. Use the migration tool to upgrade the project WAR file. [project xxxx]
Then we use the migration tool to ugrade follow from this guideline --> http://pic.dhe.ibm.com/infocenter/wrklight/v6r1m0/topic/com.ibm.worklight.deploy.doc/devenv/r_migrating_old_wl_project_to_new_wl_server.html
We managed to deployed the war file.
Next we want to deploy the adaptor, we encounter this error message
Failed to deploy adapter 'LinkAccount.adapter'. The 'adapter' version '6.1.0.00.20131219-1900' is different than the version of the Worklight project '6.0.0'. Use Worklight Studio '6.0.0' to build and deploy the application.
When we check the version at the console (Worklight Server), the project war version is 6.0.0. Both Studio and Server is in the same version 6.1 but need to do the migration process which downgrade the project into 6.0.0.
Do missing something during the installation of Worklight server?
Our Worklight Studio (eclipse)
Worklight Server version
Remove the worklight console application from WAS (Websphere application server)
Stop WAS.
Redeploy war file that containing worklight console
Start WAS
You need to rebuild the .wlapp and .adapter files in your studio version that have a same version with worklight server.
Install Worklight Studio 6.1
Deploy Worklight Server 6.1
Build your project in Worklight Studio 6.1 (adapters, app)
Deploy generated .war file in the server
Deploiy generated .adapter and .wlap in the server
Build everything with the new version and deploy the new artifacts in the same version.
If you are running on your application server several instances of Worklight Server, make sure you deploy to the correct one.
Delete the contents in your project bin folder.
Build and deploy all the adapters.
Build and deploy the application.
open worklight console