Previously I had a different version of WAS (8.5.5.3) this morning I installed WAS (8.5.5.6) on my laptop. Also I reinstalled MFP Server to point to new WAS
I started using 'Server configuration tool' then but somehow the tool remembers the old path '/opt/ibm/Websphere/Liberty' and all other old settings
Even I tried removing 'runtime' and 'application' and recreated but still 'tool' picks up the same old details by default
Is there any way to clear the old details (or cache) of 'Server configuration tool' ?
Thanks
Sathish kumar
In the current versions of MFP, there is no link between the application server you selected in Install Manager to deploy Application Center, and the application server that is presented first by the Server Configuration Tool when you deploy an MFP Server. The Server Configuration Tool looks at the list of application servers installed with Install Manager and presents them in the order in which it did find them.
Related
Installing IBM MobileFirst Studio 7.0 using MFPF_7.0_ELP_UPD_IBM_MF_STUDIO.zip but due to local LAN security we are not able to get dependency from eclipse market place which are required and downloaded directly from download.eclipse.org org. Where can we download necessary requirements and use this as local repository?
You can try this .zip file, but I'm pretty sure it is the same: http://public.dhe.ibm.com/ibmdl/export/pub/software/products/en/MobileFirstPlatform/mobilefirst_studio_plugin_7.0.0.zip
When using the .zip file, you can also attempt the installation with the "Contact all update sites..." checkbox un-checked, before proceeding with the installation in Eclipse.
In general, the MFP Studio installation requires an outside Internet connection.
Find a location with a working connection, install. Make a copy of your Eclipse for future use.
Standard scenario for this setup is to have a central installation (with Internet connection). Then archive that specific installation, and then sneakernet it each of the disconnected workstations. You must do this for each type of workstation (Win/OSX/Linux) to be supported. No its not optimal, but does resolve the problem. Hope this helps.
You can check with your network administrator if they can allow your machine to access to the internet via a proxy server. If this is possible all you need is to configure the network connection in Eclipse to include your proxy server setting. You can see the detail here:
http://help.eclipse.org/luna/index.jsp?topic=%2Forg.eclipse.platform.doc.user%2Freference%2Fref-net-preferences.htm
I am trying to install and configure Worklight application center on liberty profile.
I have installed the worklight 6.2 using the installation manager. Along the installation process i have installed the appcenter as well.
The installation was successful. But when i try to access the console it giving me "Context root not found".
Also I have checked the server.xml of the liberty server. It contains the appcenterconsole.war and the applicationcenter.war mapped.
Does anyone experience this problem as well?
This might be the same problem as mentioned here: Worklight Development Server does not start
Please make sure you use Oracle Java, not IBM Java!
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 move the application from dev to producation,change the application-description.xml and worklight.properties files and generate a .war file,and then i add it to the tomcat,but when I start tomcat,it occur the follow error:
java.lang.ClassNotFoundException: Class org.hsqldb.jdbcDriver not found in Worklight platform or project
but even I add the hsql.jar to my application,it still the error,any help?
my worklight version is 5.0.5 and apache-tomcat-7.0.37 and mysql is 5.1.57
HSQL is the default database used when running the Worklight project in Eclipse.
When you move to Tomcat, you also need to edit in worklight.properties the database-related properties.
Since you mentioned MySQL, you need to uncomment the MySQL section in worklight.properties and edit it according to your setup.
Of course, also undeploy and re-deploy the updated .war file.
Additions:
HSQL is a filesystem-driven database, and is provided by Worklight to work out-of-the-box, when running in Eclipse.
When moving to Tomcat and installing Worklight in it, you must edit worklight.properties and set it up so that it will know how to talk with the datbase.
In your case, when using MySQL you must also include in Tomcat's \lib folder the MySQL connector/J file. You can get it from here: http://www.mysql.com/downloads/mirror.php?id=412178 (click on "No thanks, just start my download" at the bottom).
Note that in order to run Worklight on an Application Server (such as Tomcat, WebSphere or Liberty), you must use either the Consumer or Enterprise Edition of Worklight. This is required as otherwise you will not have the Worklight JEE .jar file as well as the SQL scripts to create the database tables. All of this is done via the IBM Installation Manager.
You cannot use Worklight on an Application Server using the Developer Edition.