I have Worklight Server and Appcenter installed on RHEL 6.4 and am unable to find commands to start & stop these servers gracefully. Primarily, I would like to do this to apply patches, make changes to databases etc.. Any help is really appreciated.
It sounds to me like you are referring to installed instances of Worklight Server and Application Center in a QA/UAT/Production environment.
This means that your Worklight Server and Application Center instances are deployed to some application server (either WAS, WAS Liberty or Tomcat). So the way to start and stop these instances would be via the commands available by the the used application server. You should probably then consult with the user documentation of the used application server for the commands. For example for Liberty: http://www-01.ibm.com/support/knowledgecenter/was_beta_liberty/com.ibm.websphere.wlp.nd.multiplatform.doc/ae/twlp_admin_script.html
If you are in fact referring to the Worklight Development Server (Worklight Studio plug-in for Eclipse), there is no publically available way to stop the server from command line -- unless you are using the CLI tool to manage your development (working outside of Eclipse), there you do have a command for it.
Related
I need to run a node.js server application as a self-contained executable which should be a Windows service. There are several libraries creating either a self-contained executable or which implement a Windows service layer in node.js but do not create a self-contained executable which is a Windows service itself.
Requirements are:
node.js server app should be deployed as Windows service (self-contained, win-exe, no node installation on target machine)
Windows service should be able to use parameters for node.js server app (e.g. a TCP port number or node_env)
it would be great, if some files could be stored beside the service which are used within node.js server app (e.g. SSL certificates)
Does anyone know an open source tool, library or sth. else which does fulfill these requirements and which is maintained well (still supported / developed, no critical old open issues etc.)?
here is a brief what I am trying to achieve.
I am working with an application which is in WordPress and running on Apache and in one of the screen (page) it's require to use any already built module which has a large set of functionality built in .Net, that require an IIS support.
I am running WordPress application on Linux and not sure if Linux provide that flexibility to run both servers Apache and IIS at the same time.
Have gone through with some blogs but nothing yet, not sure even it's possible or not.
Any suggestion would be appreciated...
Not is possible run IIS over linux, you can use kestrel with netCore ,because IIS not is cross plataform, many applications that run "net framework" you can migrate to "net standard" , one option is install "docker windows machine iis" but only run in windows machines
I am looking for the best practices for deploying an ExtJS app on a RHEL server. I tried installing sencha CMD on the server so that I could do the application build there, but I kept getting a segmentation fault with the 64-bit version and nothing happened with the 32-bit version (both as a normal user and with sudo). I even tried ssh'ing in with a -X option to enable Xterm, but that did not work. I am thinking I am going to have to do an external build and then deploy the entire contents to the server.
Ultimately, I would be doing this through a Bamboo server (same as Jenkins). For testing purposes though, I am going to use Webstorm. Anything I should be aware of/watch out for? I am deploying the entire project directory structure.
Alright: I was able to do this as root. Interesting. I should now be able to set up my Bamboo process.
I am new to Azure. I am following this tutorial in setting up my .Net server for azure and ios client.
http://azure.microsoft.com/en-us/documentation/articles/mobile-services-dotnet-backend-ios-get-started/
I am testing my ios client on simulator. Can I run my .NET server on my location machine with put publish it to azure? If yes, how can I figure my client to talks to this location machine?
And in the tutorial, it creates a Database Table. If I run it locally, do I need to setup my location DB server?
Not on a mac (which you need for iOS development). With the .NET backend you can run the service locally on a Windows machine, but it will be running off of localhost.
For iOS development, you have two choices. If you use the JavaScript / node.js backend, where all of your development can be done in the Mac (you can configure the service via Git locally or directly in the portal). If you use the .NET backend (the link you mentioned), then you need the Mac for the client-side development, and a PC (or Windows running in the Mac on an emulator such as parallels) to develop the server (you need Visual Studio for that).
And regarding your question about the table, when you run it locally, it will use Entity Framework Code First (by default), so you don't need to create the table in your (local) database - it will create it automatically for you.
Wondering if I should stick with testing on my local IIS install or just use the Express version. Any reason why or why not?
generally, I would try to have the development / testing environment resemble your live environment as closely as possible.
so if you're using IIS in production, I'd recommend using it in development also.
I cannot tell you how many times I've seen web apps working perfectly on the development machine using IIS6, and crashing completely on IIS7.
I suggest this configuration:
IIS Express on the developer machine
same IIS as in production on a staging machine
IIS Express is the best choiche on your local computer because it's easy and fast to install and configure and doesn't require administrative rights to be installed.
It's completely integrated with Visual Studio and it has all the functionality of IIS.
And the configuration is in the source code repository so each developer can checkout the solution and is able to run it with minimal effort.
As sJhonny suggests is recommended to have an environment closer as possible to the production environment.
The best way is to have a staging server with the same software configuration of the production server, in your case with the same IIS complete version (it's enough a virtual machine).