ibm-mobilefirst

Not sure whether the same issue has been raised before (I tried to comment but was unable to do so - see link below) Anyway, I've just upgraded my development environment to MobileFirst Studio 7.1 and I'm having an issue with the adapters we created in 7.0. The adapters deploy without error but when I try to call WL.Client.invokeProcedure from my browser (I'm just testing as a web app at the moment) I get an error 500 in the browser console. I've tested the adapters using the "Run As ... > Call MobileFirst Adapter" menu option, and they work so this is only related to accessing the adapters

I have seen some questions about dynamic adapter configuration at run-time how to pass domain,port number,username and password from user input to worklight http adapter With a Worklight Adapter can I change the domain and port for a procedure at runtime? but my question is about adapter configuration after deploy on WL server 5.0.6 from external - not at runtime from code. Our scenario is that in our enterprise development and testing process requires the QA and Testing team to change the destination host and port for the adapters from mockup-backend to testing-backend to production-backend

I want to distribute my Worklight App via the App Store. The problem is, users will have to point to different Worklight Servers depending on what company they belong to, but I don't want my users to have visibility to the Worklight Server URL or have the ability to change it themselves (meaning I want to set worklightSettings in the application-descriptor.xml to false so "Custom Server URL" does not appear in the settings). So my idea is to initially point all my users to a default Worklight Server (in which they would only connect to the first time the start the app) which would be

When deploying the BPM project in a development environment, everything works. However, when trying to move the project to the WAS application server, the adapter deployment fails (.war and .wlapp deployment passes successfully): Failed to deploy adapter 'BPMAdapter.adapter'. : Procedure 'getRest' in adapter 'BPMAdapter' requires security test 'BPMAdapter-securityTest' which is not defined in authenticationConfig.xml. We've verified the security test exists in authenticationConfig.xml, here's the portion of the tests, so it is, in fact present: <securityTests> <customSecurityTest name=

I am using IBM Worklight 6.0.0 and testing on iOS 7 device. I have the following js error: Cannot register to event source callback with an existing alias: 'myPush'. The alias is already in use for event source 'PushEventSource'. On device, when I login, logout then login again. (error appear the second time) On the client side, my code is: if (WL.Client.Push){ WL.Client.Push.onReadyToSubscribe = function(){ WL.Logger.debug("onReadyToSubscribe"); WL.Client.Push.registerEventSourceCallback( "myPush", "PushAdapter", "PushEventSource", pushNotificationReceived); if (isPushSubscribed() == false) {

I am getting JVM Heap space error in Worklight when tried to deploy Android Application. Failed to deploy the application to Worklight server: InputStream error: java.lang.OutOfMemoryError: Java heap space How to fix this issue. Any Help is appreciated. Idan Adar Not exactly a Worklight issue, but rather an Eclipse issue. See possible solutions at: How to increase Java Heap Size in Eclipse How to increase application heap size in Eclipse? java.lang.OutOfMemoryError: Java heap space Increase JVM max heap size for Eclipse For me the error related to the Heap size of the server, not the heap size

I've developed a hybrid application using Worklight 6.1 + Dojo 1.8. The application tests out fine using Chrome "Common & Android". When I deploy the device to my Nexus-7 Tablet running 4.3 all of my views appear together, and the dojo widget are simply text content. I reviewd a previous post titled : " Worklight mobile app doesn't load dojo mobile widgets on android 4.x devices " I'm experiencing the same situation, and I also, have followed the steps mentioned in several posting found across the Web. •Make sure to have all dojo required files under www folder... •Uncheck "Provide Library