Project war not created after running build all environments - ibm-mobilefirst

MobileFirst Studio 6.3
Windows 7.
Used HellWorld sample to verify scenario.
Selecting Run As -> Build All Env The project .war file is not created. The only way it seems to generate the project .war file via "Run As" is to deploy the application to the test server. (Run As -> Run on MF Dev Server)
What is the appropriate approach in studio to cause the .war to be generated?

The Build All command is related only to the .wlapp file(s).
Select "Run on MobileFirst Development Server" in order to actually have a runtime to run your application on.

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.

How to deploy MobileFirst CLI application to an android device?

I am using MobileFirst CLI 7.1. I want to deploy my MobileFirst CLI application to an android device. How can I do that?
In studio i use to get a projected generated when I right click > Build and depoly for all environments.
Also I want to know how can I target remote server. (In Studio we had an option to deploy to remote environment.)
Do we have any commands for achieving the above two?
In studio i use to get a projected generated when I right click > Build and depoly for all environments.
You need to have google's ADT tools installed and execute the commands from the command-line, or import the project into Google's Android Studio IDE.
Also I want to know how can I target remote server. (In Studio we had an option to deploy to remote environment.)
In the Studio you did not have the option to "deploy to a remote server". You had the option to configure the application to point to a remote server (the properties you can edit in the worklight.plist/wlclient.properties file).
This feature does not exist in the CLI. After building the project, in case you want it to point to a different server, edit the properties in said file(s) to point to the remote server.

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

IBM Worklight 6.1 - Server configuration procedure - defining the .war file

What is the war file that i should define in the "worklight server configuration description?"
After installing all components from installation manager go to:
Windows Start Menu -> IBM Worklight Server 6.1 -> Server Configuration Tool
In the new window that pops up go to Create a new WL server configuration. Enter a name and the next screen of this wizard ask for a worklight project war.
Is it a projects war file or something in the server installation folder?
I believe this section in the Configuration tool refers to the .war file of the Worklight project you have created using Worklight Studio.
In your Worklight project look inside the bin folder.
There you will find a .war file.
You can review the following training module to getting a better overview:
Moving from development environment to stand-alone QA and production servers
Also read through this Information Center topic:
Deploying the project WAR file

IBM Worklight 6.1 - Build and Deploy not available?

I have used Worklight 5 for Eclipse Juno multiple times and had great success when building hybrid apps for Android and iOS. However, I just recently installed a new version of Eclipse Juno on a new computer and later installed Android ADT and Worklight.
Eclipse works as normal for non-Worklight apps. When I create a Worklight 6.1 project and right-click the common folder, select "Run-As", I am not presented with any options to do just that. I am only seeing the options for "Preview and Run configurations" but should be seeing these mentioned options and "Build and Deploy".
Is there something corrupted in Worklight that I need to change to make these options re-appear? Are these options no longer used? If they are not used, how do I deploy a hybrid to Android, iOS, or any other platform?
In Worklight 6.1 they have re-swizzled the options a bit, but if you want the equivalent of "Build all and Deploy," select: "Run on Worklight Development Server." You need to select the App, not the common folder to get that option.
Since you say you've been using Worklight 5 and have now switched to Worklight 6.1.0, I suggest that you will review the following:
What's New in Worklight 6.0.0.0
What's New in Worklight 6.1.0.0
IBM Worklight training modules
The Run As > Build and Deploy action was renamed to Run As > Run on Worklight Development Server and additional actions were added as well. You will want to take some time to re-familiarize yourself with the production...
Tip: no need to re-build after every web resource change you make; just refresh your previewed app and the change will be there.
In the image:
Run on Worklight Development Server = build and deploy
Build Android Environment = build only, don't deploy
Run on Android Studio = if you've installed Android Studio, the built project will open there
Build Settings and Deploy Target = configurations for minification/concatenation/other as well as changing the server the app will be deployed to, etc.
If you do not see these actions, I think it'd be best if you will get a fresh copy of Eclipse Java EE (4.2.2 ("Juno" SR2) or 4.3.1 ("Kepler" SR1)) and re-install Worklight Developer Edition from the Eclipse Marketplace (or your Consumer/Enterprise Edition if you're a Business Partner/Customer).