IBM MobileFirst Platform 7.1 - No runtime environment deployed in this server - ibm-mobilefirst

I have installed IBM Mobile First Server on a VM. As a part of Mobile First installation, I installed Application Center, IBM DB2 , WAS Liberty Core as well and Mobile First Studio on my local machine. I am able to view the Mobile First console on http://localhost:9083/console and providing the required credentials.I uploaded a war file by using the Server Configuration Tool. Restarted Application Server. Tried with different war files.
My issue is when I open my mobile first console I'm getting
No runtime environment deployed in this server
Here you can find my messages.log and server.xml files https://www.dropbox.com/s/ftb3bb71wyuarrl/share.zip?dl=0

You've changed the following:
<httpEndpoint id="defaultHttpEndpoint"
httpPort="9083"
httpsPort="9446" host="*" >
But kept this:
<jndiEntry jndiName="ibm.worklight.admin.jmx.port" value='"9443"'/>
And in the log, it mentions:
[9/24/15 8:29:06:429 CDT] 0000005b
com.worklight.common.util.jmx.LibertyRuntimeMBeanHandler I
Impossible to establish a REST connection to :
service:jmx:rest://localhost:9443/IBMJMXConnectorREST
In your previous question on the same topic it was identified that you have some VM network problems with the ports 9080 and 9443. So, try changing "9443" to align with the actual HTTPS port you're using, 9446.

Related

Worklight access remote adapter from different server mobilewebapp

I have few adapters deployed in remote uat server.
I want to access them n develop mobile web app in my local worklight server.
Im using IBM Mobilefirst 7.1.0
I tried setting host and contxt path of uat server in mobilewebapp build settings and run the app in my local server. But query call is throwing 404 error.
Can anyone help me in accessing remote adapters in local server.
It would've been easier to help you had you provided information such as where are you setting that connection info and what are you setting... since you're getting 404, this would typically mean that you have incorrectly inputted the connection info.
In MobileFirst Studio, right-click on the application folder and select Run As -> Remote Target and Build Settings. There you need to input the server address:
Host: https://your-server-ip-address:port-number
Context root: /myproj (typically the project name, unless you've specified otherwise in the server.xml of the remote application server).

IBM Worklight 6.2 App - Remote Server communication failure

I am developing a hybrid app in Worklight 6.2. I have a WorkLight Server installed Red Hat Linux 6 base as remote server.
I have give the servers ip address, port number and context root as"/worklight" in the "build settings and deploy target".
Then i added my adapter file and wlapp file into the remote servers "app" folder. I haven't made any changes in the server.xml file.
Now when i call the procedure from my app i am getting "[IPADDRESS:PORT/worklight/apps/services/api/MyApp/ipad/query] failure. state: 404, response: The server was unable to process the request from the application. Please try again later."
What am i missing and What changes do i have to make to make the request to work.?
The steps you are describing are not clear.
Make sure you are following the steps as provided in the IBM Worklight Knowledge Center.
First make sure the Worklight Server deployment to the application server was done correctly
You can verify this then by loading the Worklight Console (there will be no deployed projects)
Then follow the Worklight project (.war, .wlapp, .adapter) deployment to the Worklight Server instructions
You can verify this then by loading the Worklight Console (there will be 1 deployed application)

How to set up IBM work light server on my machine

Hello Folks,
We are recently working on IBM worklight and what we want to try is:
We have two machine, one we want to set as server and other one is for my developer to build the app.
Currently we have installed Apache Tomcat server on the machine which we want to make as server. We even have IBM Worklight installed on it. Now What I want to achieve is to deploy the app from other machine to this server. But I am not able to set up the things properly.
Things done so far:
Installed Apache Tomcat server software on a machine (server)
Installed IBM Installation Manager
I am not getting how will I set up the Worklight Server on this machine. Can anyone provide some information?
You cannot directly deploy from Worklight Studio (the Eclipse plug-in) to a remote Worklight Server.
The steps you need to take are:
Setup your application for a remote server, via the Build Settings and Deploy Target window
Build the app
Take the .wlapp/.adapter file and deploy it to the remote Worklight Server via it's Worklight Console
If you have done any server-related changes (authenticationConfig.xml, Java code, ...) you will need to first deploy the project's .war file to the application server that hosts the remote Worklight Server, and then the .wlapp.

IBM Worklight 6.1.0.1 - Server Configuration Tool issues

My configuration is:
OS: RHEL 5.7
IBM DB2 10.1
WAS8.5
WL6.1.0.1 (last fix pack installed)
When reading the WL6.1 Information Center, it is said that you can deploy several Worklight projects (that is, several project WAR files) to an application server just as you would deploy any JEE application: each deployed project must have a unique name and a unique context path.
This exactly what I am trying to do using the Server Configuration Tool located under the directory '/opt/IBM/Worklight/shortcuts/'.
When deploying the first WAR file under a WebSphere Application server profile, the Server Configuration Tool works perfectly and creates/deploys an EAR file named 'IBM_Worklight_Console.ear', in which the WAR file is included. However, when using the Server Configuration Tool to deploy a new WAR file under the same WebSphere Application server profile, the Server Configuration Tool creates the same EAR file named 'IBM_Worklight_Console.ear' with the new WAR file included. But obviously it overwrites the first Worklight Server configuration, preventing to deploy several Worklight projects to the websphere application server profile as it is supposed to do.
What could be the problem?
The Worklight documentation, section "Configuring multiple IBM Worklight projects", says that for multiple Worklight project WAR files in WebSphere Application Server, each must have a different id. In the Worklight Server Configuration Tool, you enter this id in the "Application server configuration" panel, in the "Deployment id" field. Once you choose a different id for each, they will be able to coexist. (At most one of the ids can be left empty.)

IBM Worklight - How to connect to another Worklight Server located in another machine in the same network?

I have setup Worklight Studio in my local Machine and developed a sample application. I need to deploy that application to a Worklight Server set up in another PC in the same network (LAN).
You already have a server in your local machine - Worklight Studio contains an internal Worklight Server. But that doesn't matter...
If you are using Worklight 5.x:
Open application-descriptor.xml
Find the worklightServerRootURL element
Change its value to that of the remote Worklight Server, for example: http://myotherserver:8080
Right-click on the application folder and choose: Run As >> Build All and Deploy
Take the *-all.wlapp and/or *.adapter files from the bin folder and deploy them via Worklight Console that resides in the other server machine.
If you are using Worklight 6.0:
Right-click on the application folder and choose: Run As >> Build for Remote Server
Enter the details of the other server machine (host, port, context root)
Take the *-all.wlapp and/or *.adapter files from the bin folder and deploy them via Worklight Console that resides in the other server machine.
The above assumes that the remote server(s) are configured to accept the applications and/or adapters you will deploy (that is, that you have deployed the .war file of the project; your scenario was not very detailed so my explanations were somewhat lexing).