worklight-server

i have created a XSLT for the WL.Server.invokeHttp which gets the data from the backend server in XML format and performing transformation successfully. this adapter is used to get the data from backend server. but while sending data to server in XML , as i am getting data in adapter as JSON , i need to transform it into XML using XSLT. is there any provision in ibm worklight adapters that i can perform XSLT transformation for input request just the way i can do it easily while getting response from backend server. Here i am explaining the return data ( i.e. response) for example, if i want to

I am facing issue with upgrading to Worklight 6.2. Please find the error below: ERROR: transport error 202: bind failed: Address already in use ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:750] FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197) Thanks in advance I guess you see this when starting your 6.2 server? It's because you have your 6.1 server still running. The clash on the dt_socket will cause

My problem is this: When in Development environment , everything is OK - the poller is working fine, the DB statuses changes, etc. When in Production environment , nothing appears in the log and nothing changes in the DB (I'm reading notifications from a DB table). Push Notifications eventSource: WL.Server.createEventSource({ name : 'PushEventSource', poll : { interval : 360, onPoll : 'sendNotifications' }, securityTest : 'mobileSecTest' }); mobileSecTest security test: <mobileSecurityTest name="mobileSecTest"> <testUser realm="LdapAdapterRealm"/> <testDeviceId provisioningType="none"/> <

I have a problem when deploying my Worklight project on the server . It shows the following Error Message : FWLSE3041E: 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. and when I tried to preview my application it showed this message : SRVE0777E: Exception thrown by application class 'com.worklight.core.auth.impl.AuthenticationFilter.verifyServletInitialized:420' I had the same issue using Worklight 6.2 CLI, but recreating the

I had an Ant build file working fine on Worklight v5.0.6. On porting to Worklight v6.0 I found out that there's a new mandatory attribute, worklightserverhost , for the app-builder task. <app-builder applicationFolder="path/to/proj" environments="mobilewebapp,android,iphone" nativeProjectPrefix="myproj" worklightserverhost="?Here?" outputFolder="where/to/put/it"/> I can find no documentation of the value to put here or its significance; my guess is that it is supposed to be the value that was formerly in application-descriptor.xml and is now taken from worklight.properties when building in

Two part question. Generic question about a server configuration feature, and then it's possible implications for what we'd like to do. The worklight properties file has entries publicWorklightHostname, publicWorklightPort, publicWorklightProtocol. Individual applications also specify much the same information in the application descriptor. It's clear that applications need the descriptor information to "find" the server. What purpose do the corresponding entries serve in worklight.properties? I believe that the two are supposed to match. We have a scenario where we need to deploy our adapters

In our project we are trying to figure our what the best process to connect to the server will be - especially when taking care of offline/online scenarios etc. Right now, for us, it seems that all three options to connect to the WL server are similar. Whatever option we use, we can call our Adapter Procedures perfectly and we receive Notification Messages that are set in the console. We are not sure about Direct Update - this is not working properly yet. Are there any important differences between these three ways of connecting to the WL server, or is basically the same connection procedure

I have an already running Worklight application. We are planning to move to another production cluster tomorrow but I want to get the old .wlapp that is already deployed on the first cluster. How can I get it? I could find a directory on the temp file of the WebSphere application server, but it is in an exploded form. When I zipped one of them and converted it to .wlapp, while the deployment was successfull, I had a Direct Update and the application failed to start... Is it the right path? When you build your application in Worklight Studio, the build produces .wlapp files and stores them in