In a previous post, we discussed changes made to OpenGeo Suite for OS X to make it more consistent with how people use Macs. For the OpenGeo Suite 4.0 release, we also revisited the Windows installers with a goal towards making production deployments easier.
Previous versions of OpenGeo Suite for Windows had very little control over which specific components you could install. It was an all or nothing approach. OpenGeo Suite 4.0 brings a fully customizable installer so you can install only the specific components you’re interested in. Want a production GeoServer with an Oracle backend? You no longer have to install a PostgreSQL server you don’t need.
We’ve taken this a step further by shipping a very lean GeoServer out of the box. If you need a supported extension such as WPS, Clustering, or Mapmeter then you can choose those extensions explicitly. Forget to install an extension? Don’t worry, you can now run the installer again and it will detect what you currently have installed and provide options to install any additional components or extensions into OpenGeo Suite.
Another improvement over previous OpenGeo Suite releases for Windows is the use of standard Windows services to control Jetty (which serves up GeoServer and related services such as GeoWebCache) and PostgreSQL. Since these are now standard system services, you can do things such as control whether services automatically start when the system boots up.
An added benefit of using system services is that OpenGeo Suite components now run as Windows System Service users instead of local users. This means your data is no longer tied to a specific user on the server but is instead available globally. This also means you no longer need to leave a user logged-in to keep OpenGeo Suite running.
Try OpenGeo Suite 4.0 for Windows today!
Download OpenGeo Suite 4.0 to see for yourself. We hope these changes will make it easier for you to get up and running on your Windows servers.