I installed IBM Mobile First 8.0.0. I deployed Push service and the tables are also created. In the mobile first console the push service is showing as inactive. On inspecting the element in the chrome error window it points to GET URL returning 404. When i paste the URL in the browser and execute, it returns the live update adapter is not available and the database may be corrupted
Any help in this regard is highly appreciated
If you installed the MobileFirst DevKit, then this shouldn't happen since everything is built-in. Try reinstalling in this case.
If this is a production or test environment installation using the IBM Installation Manager and Configuration tool, then you may have specified an incorrect path of the push services .war file. You can confirm this by comparing the various paths that are defined in the application server's server.xml file.
Related
We've been finalizing NopCommerce .Net Core web app which has been running great on a test server. I'm now trying to transfer the app to our production server, which did not have .Net Core. I installed the latest .Net Core hosting bundle and rebooted the server. I also have Web Deploy running on both the host and the client. I exported the app from the test machine and imported it into a newly created IIS site. After setting up the bindings - and enabling stdoutlogging, I try to see what's working, and get indication that "An error occurred while starting the application". No indication what the error is. Logs is not being written to. The event viewer tells me that:
Application 'MACHINE/WEBROOT/APPHOST/NOPCOMMERCE' started process '6980' successfully and is listening on port '41573', which is a random port not binded to.
One interesting thing I noticed on the test server is a "user" called nopCommerce which has full rights to the nopCommerce folder in inetpub/wwwroot. However this user does not show when I look at local users and groups. I am not sure therefore what this "user" is and if/how I should create it. Based on some advice from somewhere I temporarily gave everyone full rights to the nopCommerce folder, but that didn't work either.
Can anybody please aim me in the right direction?
Problem was a bad setup - access rights to subfolders of nopCommerce was one, which I solved by giving the users group modify rights. This might be a bad idea and I will do some more research. The other fault was a bad database login in the connectionString.
Ultimately I had to learn that instead of starting the app via IIS, it can be run from the command-line, and then messages and errors will be displayed in the DOS box. What to run is determined from the
I still don't know where the nopCommerce user comes from on the staging server.
We have done the installation and configuration of MFP 7.1V with WAS 8.5.5.0 V successfully.Here we are able to access the operation and analytics console and able to add the application (.wlapp files) and adapter files and able to access those application in tab by instantiating an apk files in the tab.
But here the issue we are facing is we are not able to get the devices list in the operation console and analytics and devices tracking in the analytics console.
So essentially I guess the issue is that the applications fail to connect to the server at all. Please edit your question with the full client-side log with the errors.
Until then my suggest is to verify in the generate .plist/.properties file that you are indeed attempting to connect to the correct server. Verify the host, port and context-root values in the files.
I do not understand the purpose of the properties listed in worklight.properties:
publicWorkLightHostname
publicWorkLightProtocol
publicWorkLightPort
Those properties are set when you do in eclipse the Run As -> "Build settings and deploy target..."
Are they duplicated? Which one is the valid one? Are they used in different ways?
I have read the documentation in info center:
https://pic.dhe.ibm.com/infocenter/wrklight/v6r1m0/index.jsp?topic=%2Fcom.ibm.worklight.deploy.doc%2Fadmin%2Fr_configuring_the_ibm_worklight_server_location.html
But there is no mention to the "Build settings and...".
See this question and answer: worklight server configuration - separating adapters and server
The properties that are found in worklight.properties relate to the
Worklight Server. The properties you have mentioned:
publicWorklightHostname, publicWorklightPort, publicWorklightProtocol,
are required because the server itself needs to know what is its URL
to the outside world, so that it can embed it in redirects and such.
These are also required for the Mobile Web, Desktop Browser
environments and Worklight Console.
For example:
Create a new application and add the Mobile Web environment > Run on Worklight Development Server deploy. Open Worklight Console and click on "Get application URL". Copy the URL. Go to worklight.properties, change the publicWorklightPort to "100"; Go back to console, compare the previous URL with the current.
From Javier:
They are not used by the mobile apps. They are shipped with the .war and are used by the .war to provide information to the user like the web url, but the server does not use them for the execution of a mobile app.
I've added an analytics server (Linux, accessible from the http:///iwap/worklight/v1/index.html) to use with my Worklight 6 server, but, the "Analytics" tab is now displaying, but, is empty.
The changed the wl.analytics.url under the war configuration for "Environment entries for web modules" and restarted the app.
The Worklight V6 Information Center (under "Installing and configuring the IBM Websphere Analytics PLatform"|"Configuring Worklight Server for analytics") says to use the format "http://<>iwap/v1/events/_bulk, but, the description column in the "Environment entries for web modules" settings says to use "http:///iwap/v1/events/app_activities". I've tried both, both with same result, empty screen under the Analytics tab.
Not sure where to go at this point, any one set this up successfully?
The correct syntax is:
http://${iwap.server.path}/iwap/v1/events/_bulk
If the analytics tab is blank, its possible that your IWAP server is not currently running or is unreachable from your worklight server.
In truth, the analytics tab just acts as an iFrame. You can visit the analytics console using the URL:
http://${iwap.server.path}/iwap/worklight/v1/index.html
If you are unable to visit that link, then the issue is with your IWAP server. Make sure that the server is started using the command "service analytics start" on the IWAP machine.
The IP address you enter is the IP address of the analytics server you installed independently of the Worklight server. Have you done this?
Installing and Configuring the analytics platform
The analytics tab in the Worklight console simply shows an iframe, using a slightly modified URL from the one you entered in the configuration. If you entered
http://<>/iwap/v1/events/_bulk (this the correct URL)
The URL you can visit is
http://<>/iwap/worklight/v1/index.html
You said you can visit it directly. Can you view the network tab or console in Firebug or Chrome developer tools to see if the URL it is attempting to visit from the Worklight console is correct?
Afternoon All,
Here is my context:
I am setting up an existing worklight project with App Envs for IPhone, Android, and Mobile Web.
When using the Worklight Console to preview the apps, I get context root errors from the iPhone app only. (I get the Error: The Server was unable to process the request from the appl...)
When I open the browsers JS console, I see the problem is that the app is requesting the wrong context root. It is accessing the /worklight/ context, which is not there.
The contextroot that does work is the following:
http://localhost:8080/apps/services/api/[APPNAME]/iphone/init
The Context root that the iphone is trying to hit:
http://localhost:8080/worklight/apps/services/api/[APPNAME]/iphone/init
Here is the weird part. The context root is fine for the Android, and Mobile Web environments. Only the iPhone environment is having context root issues.
All three environments are sharing the same application-descriptor.xml file and same server.
Below are some file outputs.
Files below:
/server/conf/worklight.properties
publicWorkLightHostname=localhost
publicWorkLightProtocol=http
publicWorkLightPort=8080
publicWorkLightContext=/worklight/
/apps/[APPNAME]/application-descriptor.xml
<worklightServerRootURL>http://localhost:8080</worklightServerRootURL>
So a couple of questions.
1) When setting the context roots, what is the relationship between the client and server. Do the context roots have to match between the two? Is one a master and the other simply slaves from that and does not need settings?
2) (Somewhat unrelated) While debugging this issue I have come across zero documentation about how to go about "un-deploying" the server in the Eclipse dev ide. (un-deploy the server is right from IBM's documentation) I need to know how to redeploy the server when I make changes to the server settings (worklight.properties). I have seen references to cracking open the war manually, to just stopping and starting the server in the IDE.
Any help is greatly appreciated.
If you are using a context root, it must exist in both worklight.properties and application-descriptor.xml. make sure both match, then re-build and deploy and see if the problem persists.
When using the development edition of Worklight, your server is based on Jetty which is run within Eclipse (it is bundled with the Worklight Studio plug-in you have installed in Eclipse). You do not need to "undeploy" anything. Simply make the changes to worklight.properties and application-descriptor.xml and re-build your application. The changes will make their way to both the server and client.
Do note, though, that using a context root is mainly for when using application servers such as Tomcat, Liberty or WAS.