I am working on a project in IBM MobileFirst. My question is regarding Direct Update.
Is it possible to receive direct update if I build/deploy my application from one machine to Mobile and point the server that is in another machine (Production machine)?
If not what should I do to receive Direct Update from Production machine.
Thanks in advance.
Your application can point to any MobileFirst Server you want, as long as that server has the application's .wlapp file deployed on it in order to register the application there (assuming also the server is properly configured to serve that application (adapters, authenticationConfig.xml, etc).
You can then deployed updated .wlapp files to that server, and it'll serve Direct Updates to registered applications.
Related
I had a engineer design our .net application back in 2009, my guess is that it was coded using visual studio, and all I have is the installer application. We have been using it on our 1 or 2 local client machines very well for the past few years, but now I want to move this front end to the cloud. Instead of installing it as an application on our windows 7 machines.
It is a very simple application used in our small warehouse that keeps track of cargo/shipments etc. It uses Sql Server 2008 Express as a backend which is stored locally.
I know how to get the database in the cloud, their are many options for that, using Amazon or Azure, but how do i get the local client application to the cloud?
I dont have access to the visual studio code, i just have the runtime executable file..
I am sure there is no way to do this, and many of SO users will say i need to re-write the front end.
I have tried to contact the developer and they hav since closed down. Is their anyway i can run this in the cloud?
I welcome all options and solutions!
Thanks.
I believe you have two options for hosting this application:
If you are able to configure the database connection string, you could host the database in the cloud, and distribute the application to your end users. However, you've already stated that you know how to move the database, so I assume this isn't an option.
The only alternative is to run the entire application on a cloud server, and send the user interface to a client using terminal services. This makes it appear as if the application is running locally on the user's computer, while it is actually running on the server.
For an off-the-shelf solution to achieve this, you could consider using Microsoft's RemoteApp Azure service. I'm sure there are other similar offerings available.
I successfully deployed war file and wlapp, adapters via server configuration tool and worklight console respectively, I am not able to communicate with the remote server. But from development environment, i am able to communicate with the app server.
Help me someone who have ideas and knowledge on this. Thanks in advance.
If I understand you correctly, after deploying the .adapter and .wlapp to the remote, your app is unable to connect to the remote server.
To me then it sounds like you are not building the app correctly for the remote server. You need to right-click on the application folder and select Run As > Build Settings and Deploy Target, and make sure you are using the correct server values for the remote server. You then need to deploy the .war to the remote application server and when done with that - deploy the .adapter and .wlapp files.
When trying to connect from the newly generated app, it should successfully connect - to the remote server.
I am done with my Project and its time to Deploy things to the Websphere Server to host My Worklight Application based on Woklight 6.1.0.
Despite reading the following question, I still have a question.
IBM Worklight - How to connect to another Worklight Server located in another machine in the same network?
The Websphere Server on which i have to Deploy my .war, .wlapp and .adapter files is remote server and does not fall under my company's domain. I do not have access to IP address and port provided by clients, So to deploy the same my backup plan is to copy files to a laptop having open network access and use RDP of the Window Server IP to deploy
My issues are:
As Worklight behaves, while i do Run as --> Run on Worklight Development Server it overwrite file properties like worklight.properties,.plist and index.html for windows with details of its local IP address.
When i do, Run --> Build Settings and Deploy Target I build the application to work with different Worklight Server and fill details i.e. Server: http: //182.19.xx.x0:9xx0 and Context Path: /Advisor. After doing it i see a message stating "Rebuild your Application after every change" then i click on 'OK'.
I expected it to rebuild everything for me as per details i provided but nothing happens. Is there anything i am missing?
After you add your remote server details in the Build Settings and Deploy Target window, you are instructed to re-build the application. Worklight Studio will not do this for you.
Change deployment target
Click OK
Right-click on the application folder and select Run As > Build All Environment
Per the user documentation:
Important: This dialog is used only to specify configurations and
settings; clicking OK does not trigger a build. Any time that you make
a modification with this dialog, you must rebuild your application and
environments for your changes to take effect, using either the Run As
-> Run on Worklight Development Server or the Run As -> Build... menu commands.
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.
I have read the posts:
IBM Worklight 6.0 - worklightserverhost attribute and the app-builder Ant task
IBM Worklight - How to connect to another Worklight Server located in another machine in the same network?
IBM Worklight 6.0 - application-descriptor.xml
And I think I'm missing something because all them stop with the generation of the wlapp for other servers.
After generating and installing the wlapp it is needed to generate and apk/ipa or "Run As" over the environment to execute that application.
The problem I'm having is that the deployed application in the device points to the development server always and not to the other server I have used for generating the .wlapp files with the (Run As -> Build For Remote Server...).
I have tried deploying the application with the property "publicWorkLighHostname" changed in the worklight.properites but it has no effect.
How do I deploy an application to the device pointing to the desired server?
Thank you.
Run As >> Build All and Deploy / Build specific environment, points to the local development server
Build for Remote Server, points to a server of your choosing
If you perform a Build All and Deploy after a Build for Remote Server, this will overwrite the previous action and the artifacts will again point to the local development machine.
So do a Build for Remote Server. Worklight Studio knows where to put what so that the app will reach the server.