I am using eclipse-jee-luna-SR2-win32 and MobileFirst Platform Foundation 6.3.0.0-MFPF-StudioP2-IF201504301455.
Have created a adapter and tried running it. Getting error:
No MBean found for MobileFirst project 'HelloWorld'. Possibly the
MobileFirst runtime web application for MobileFirst project
'HelloWorld' is not running. If it is running, use JConsole to inspect
the available MBeans. If it is not running, full error details are
available in the MobileFirst Development Server Eclipse Console view.
Possible solutions/workarounds:
Delete the MobileFirstServerConfig
Quit Eclipse
Navigate to your Eclipse workspace
Delete the MobileFirstServerConfig folder
Open Eclipse
Delete the workspace and start again
Delete the workspace
Restart Eclipse
Re-import the project
Try with Eclipse Kepler SR2 32bit/64bit or Eclipse Luna SR2 64bit
Same thing happened to me. Then, I realised I forgot to deploy my adapters.
Related
When I am trying to run the mobilefirst application on the mobilefirst development server,
A notepad is opening, with a warning stating, "The filename, directory name, or the volume label syntax is incorrect.
I am getting this error
[ERROR ] FWLSE3002E: The resource is not found.
FWLSE3041E: No MBean found for MobileFirst project 'Project'.Possibly the MobileFirst runtime web application for MobileFirst project 'Project' is not running. If it is running, use JConsole to inspect the available MBeans. If it is not running, full error details are available in the Worklight Development Server Eclipse Console view.
How can I overcome this, to check my application output?
Java 8 is not supported in MobileFirst Platform.
You need to downgrade to either Java 6 or 7 and try again. See if the issue then disappears.
Other than that, the only reason why this would happen in Windows is if ANYWHERE in the path of filename of ANYTHING there are special charatecters: http://www.tomshardware.com/answers/id-2030845/file-directory-volume-label-syntax-incorrect.html
To double-check:
Place the Eclipse folder in C:\
Call it the directory "eclipse"
Place the workspace next to it.
Call it "workspace"
Open Eclipse and create a new project and application
Call them "MyProject" and "MyApp"
The error should not happen.
I am trying Worklight 6.2 on this version of eclipse:
Version: Luna Release (4.4.0)
Build id: 20140612-0600
The eclipse is clean, clean workspace and just installed Worklight 6.2 - 6.2.0.00-20140719-1643.
When I build my project for deployment to the development server I get error:
Failed to deploy application 'MyApp' to Worklight Server: No MBean found for Worklight project 'SiriusProject'. Possibly the Worklight
runtime web application for Worklight project 'SiriusProject' is not running. If it is running, use JConsole to inspect the available
MBeans.
If i try to deploy my adapter I get this error:
Adapter deployment failed: No MBean found for Worklight project 'MyProject'. Possibly the Worklight runtime web application for Worklight
project 'MyProject' is not running. If it is running, use JConsole to inspect the available MBeans.
Early in the console output I see
A preview contributor threw an exception while updating the URL
NullPointerException. check logs.
But I dont know which logs it is asking me to check.
See if any of these suggestions help: How to Fix No MBean found for Worklight project?
Ex:
Run As--> 4 - Build Settings and Deploy Target , then Run As --> Run on Worklight Development Server
Create a new Worklight project and copy files
The answer was to use eclipse Kepler instead of Luna.
Delete WorklightServerConfig folder in workspace and rebuild your application.
Another option is to Switch your workspace.
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
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).
I created the new Worklight project and application in Worklight v5.0.6 and it's running fine in the Developer Edition.
After building the project and trying to deploy it to my application server I get this error message:
nested exception is java.lang.RuntimeException: Class 'com.worklight.core.auth.ext.RejectingLoginModule' defined in login module 'rejectAll' in the authentication configuration file doesn't exist."
See the answer here: Failed deploying application using Worklight Console: "Failed to deploy application <appName>.wlapp'. : ERROR
Make sure that you are using the same Worklight version in both WAS
(the Worklight Server you have installed on it) and Worklight Studio
(the Eclipse plug-in you use in order to, eventually, generate the .wlapp).
To find out the Worklight version you have installed in WAS,
load Worklight Console and click on the "About" link at the top-right corner. The version number is displayed there.
To find out the Worklight version you have installed in
Eclipse, go to the Help menu >> About >> click the Worklight icon.
The version number is displayed there.
Mismatched Worklight versions are not recommended to have, and can/will cause such errors.