I've fairly recently started working with Java (most of my recent experience is in .NET). As part of that effort, I have been doing some comparison between Jetty and Tomcat.
One feature of Tomcat that I think would be useful in our environment is the built in management console that allows an administrator to deploy/undeploy/restart/etc the various applications deployed to the server.
Is there a similar capability available for Jetty? If not, is there a preferred way to manage application servers?
Thanks for your input.
Any JMX console should work, including JConsole and JVisualVM.
Related
I know how to create a web service in C++ Builder/Delphi. But, I don't know how to publish it on my web site. I'm using a web hosting service, not my own personal web server. For example,
I usually use the first option "Stand-alone VCL application". Can this one be published on the web site? What are the differences between those types anyway?
Standalone VCL and console applications are mainly for debugging purposes. You use them when you develop your service because this way it is much faster. You can debug your code and use the WebApp debugger that comes with delphi.
If you want to deploy in production use either ISAPI or CGI. ISAPI is a dll that gets loaded by Apache or IIS (most common but there are other web servers that support it). Usually it was faster then CGI because it loaded once and ran inside the host process, the web server itself, but because it is a DLL that meant that if crashed, it could bring down the whole web server.
CGI on the other hand is a standalone executable. It was used a lot on linux where forking a process is cheap and fast. Every request used its own instance of CGI executable. But since then, projects like fast CGI and others made this a lot faster and more appealing. This also goes for ISAPI. Since then, there are ways to isolate ISAPIs into its own sandboxed processes.
As for hosting. Both are 32 or 64 bit Windows processes. So you need a Windows platform to run them. Mostly that will be Apache or IIS. This is not the best option for hosting because hosting is mostly done on Linux. This is the reason why PHP is still so popular. It runs on Linux and 99% hosting environments support it. So if your hosting is not Windows based and does not support CGI or ISAPI then you are out of luck.
What is to stop you using a WAMP server (or similar) to run single-user business database applications day-to-day?
I read everywhere that WAMP and the like are intended for the development of web apps, but why can't they be used to deploy desktop apps - what're the downsides?
Personally I think WAMP/MAMP/LAMP are great applications that CAN be used for production servers.
I have started doing this myself as I do not have the complete knowledge in server administration on the linux end and my PHP applications are not compatible with IIS.
If you are a small operation than it should save you time then go for it.
If your business grows and you can afford to put on staff to manage dedicated servers with the Apache, PHP ect all installed separately then I also recommend this.
The main difference I can see is that WAMP probably wont be as scalable as the preferred setup. The binaries are all integrated and sometimes I have had issues trying to figure out which php.ini file the system is using.
WAMP is just as secure as any other server as long as you know how to do so, is provides a UI layer which cost CPU time but like I said if you are only serving small web sites/apps than this should be just fine.
My other recommendation is to install it on a Server (Windows 2008 RS or 20012) Windows servers are more reliable and powerful than the Windows User version. Just remember to turn off IIS and any other roles not used by the Windows Server.
Make sure you your WAMP folder backed up regularly!
Good luck
I haven't found one yet. I guess the speed won't be as good as a 'pure' setup, but it sounds like that isn't an issue.
I run an epos web app for a photo studio no problem at all!
WAMP usually stands for Windows, Apache, Mysql, PHP or whatever your particular choice for P is. It describes a stack meant for specifically for deploying/developing web applications and is a rough equivalent to LAMP. Most things that would be considered desktop applications wouldn't use a webserver and more than likely would not be written in PHP.
The issue is not so much one of downsides as it is Apples and Oranges: Desktop applications are usually built with a less web centric stack.
Actually i used with wamp for many purposes; I used it with VB.NET apps, PHP, etc...but I think if you want to use it for deployment, you should start by configuring it to do so.
For example, for PHP deactivation errors display in php.ini, start listening on all allow all in httpd.conf, activating safe mode, setting a password for MySQL; and many other options that have to be configured.
I personally prefer because it is a quick and lightweight tool.
I am new on web services development and I will be using the app engine.
I would like to know if it is possible to debug locally a web service (at localhost:8888/) and debug at the same time the web app that will be using the service.
The App Engine SDK ships with a local server implementation that you typically debug on. You'd debug the web app in your browser.
http://code.google.com/appengine/docs/python/tools/devserver.html
Yes, you can debug both client and server.
However I assume that client and server are separate code bases - in this case you would have two IDE projects open each running it's own debug session.
Since you are new to GAE, I would advice to use one of rich IDE's available out there. For example, I can mention Eclipse or IntelliJ which make it very easy to debug and find issues in GAE apps.
Here are some links:
Intellij GAE support
Eclypse GAE plugin
I have to develop ATL app that is meant to run as service most the time, however we need to deploy it as user application in few environments
I believe that the answer is no, but I could easily be wrong - in either case however this probably isn't the approach I would take. Personally in your situation I would either:
Develop 2 apps, a service and a user application, or
Develop a console application and use the Windows Server 2003 resource kit to run it as a service.
See here for instructions on how to run any Application as a Windows service (I'm sure there are better guides out there, but I'm struggling to find them at the moment)
I need to deploy an old style .asmx asp.net web service (not WCF) on a windows 7 machine for test reasons. However it seems that just deploying it on a virtual directory or new web site on IIS won't cut like it used to back in xp.
What should I do? I need to test the service locally prior to deploying it, and so far it's giving me a hard time.
Any help will be greatly appreciated
Thanks
Deploying to a Virtual Directory should work just like it did in XP...with one minor change.
The default behavior in IIS7 is to use 'Integrated' Managed Pipeline Mode for your Application Pools. More than likely, you just need to change that to 'Classic' Managed Pipeline Mode (or switch your Web Service over to use the built-in 'Classic ASP.NET' App Pool).