Attached is a document that gives tips on debugging OE Mobile applications. Please let me know if you have any other tips that might help others debug their applications and I will add to the document.
[View:~/cfs-file.ashx/__key/communityserver-discussions-components-files/17/DebuggingTips.docx:550:0]
http://localhost:8980//rest// | To perform a READ operation (fill() method in the JSDO) to get all the records for the resource. |
http://localhost:8980/.static/mobile/ | To get the catalog for service. |
Hello,
The error about the credentials seems to be happening because the URL http://localhost:8980//.static/mobile/ has an a dot in "static".
The the URL without the dot is working on your environment since you can get the JSON response (with PostMan).
http://:8980/MobService/rest/MobService/> results response timeout error
To debug this, you would need to look at the log files for the AppServer broker to see if the request completes in a timely manner.
A possible issue could be that the database is not connected to the AppServer broker and the request to run the Business Entity fails.
I hope this helps.
Here are my first experiences and some tips for troubleshooting.
I had a few problems when creating a demo application according to the example found in "OpenEdge Development: Mobile Applications" manual. E.g., in the example JavaScript code (which is run on Load event) there is no definition for 'cMsg' variable. For that reason, the application opened as a blank page. I took me a while to figure out that you need to add 'var cMsg="ok";' at the beginning of the JavaScript code.
Another problem for me was that since I have several OpenEdge versions on my machine, I had changed the NameServer port of OE11.2. However, the application was searching the AppServer broker using the default port (5162). I found this out eventually by looking at the log file in $DLC\servers\tomcat\webapps\MyMobileService\WEB-INF\adapters\logs. The NameServer port is defined at least in \WEB-INF\adapters\runtime.props and oerm\WEB-INF\oerm.data\default.prop. Changing the port in those places, the application began to work.
yes it was NS port number which was creating issue.. thanks alot
thanks for the suggestion
it was NS port number which was creating an issue. now its working fine.
I found that although you can set the defaults from OpenEdge Management for the OE WebServer, that this does not get picked up when you publish your apps. The best thing to do is to change the runtime files for the services in the PDSOE project.
Hi,
Hi Shubas,
Welcome to OpenEdge. We are working on providing samples with instuctions to make this easier but they are not available yet. We have a demo that we have been using at the OE Mobile road shows that I have attached to this post. Please follow the directions closely to create your own project from the attached zip file. There is no documentation but hopefully you can run it and then follow the logic in a browser debugger.
Shelley
Hi Shelley,
Did you not forget to post "Appserver.zip" which is referenced in the doc?
/Thomas
Hi Thomas,
Yes I forgot it. I've added it to the original post. Thanks!
-Shelley
Hi Shelley,
Thank you very much.
I will try to create my own project from the attached zip files and will update you the progress .
Thanks again.
Shubas
Looking for receiving tips from Shelley live? Don't miss her talk on Debugging OpenEdge mobile apps during the EMEA PUG Challenge in Brussels: