GlassFish is an enterprise ready container. That is great if you need all the features that an enterprise might use. If you need these features, then great. If not, then not so great. Sometimes less is more, but since I have to learn GlassFish, I will endeavor forward.
This article will provide information and links that talk about the configuration of GlassFish.
Creating a Windows Service
During the installation of GlassFish you can specify a domain to be created. At that time you can also give an option for creating an Operating System service.
In Windows this means creating a Windows Services which starts and runs GlassFish. You can also do this from the command line using asadmin.bat and the create-service command.
Here is an example of the installer trying to create the operating system service (i.e. Windows Service). Interestingly I specified a name with spaces which the command didn’t like which forces me to rerun the command from the command line. Here is the service information from the Services control panel.
The default ports for GlassFish are 4848 for the administration portal, 8080 for the HTTP listener, and 8181 for the HTTPS listener. Feel free to change them if need be. For now we are sticking with the default ports.
default-config vs. server-config
The default-config configuration is a special configuration that acts as a template for creating named configurations. Clusters and instances cannot refer to the default-config configuration. The default-config configuration can only be copied to create configurations.
The server-config configuration is automatically created for the domain administration server (DAS) when the domain is created.
Getting to the minimal configuration
Stay tuned! We will talk about reducing the footprint of GlassFish to get to what we consider the bare minimum.