
Leading the Way: Payara Platform Community 7 Beta Now Fully Jakarta EE 11 Certified
We’re excited to announce that Payara Platform Community 7 Beta application server is now fully certified as Jakarta EE 11 […]
In the world of pre-configured Docker & Kubernetes containers and Microservices, it’s easy to forget that not everybody is rushing to jump on the bandwagon quite yet and are still using the more traditional application server setup. With that in mind, many people like it when their servers start themselves up automatically on boot so that you don’t have to manually log onto each server and start the instances yourself. Now while you can get by using a script and a task scheduler like cron or Task Scheduler (Windows wins on the more obvious naming front here!), you can actually install Payara Server as a service like Apache HTTP Server or SSH so you can control it with your OS-native services manager.
The asadmin command to do this is:
create-service [domain-or-instance-name]
If you don’t provide a domain or instance name, it will default to using domain1.
The command takes several additional options for configuring your service, and as alluded to in the previous sentence, you’re not restricted to installing only the DAS instance as a service. You can specify an instance name with a node name in which it resides to install it as a service too.
As with any asadmin command, you can run it with the –help option to get information about the available options. Since you’re here though, I’ll briefly describe each of the options:
Hope this helps!
Share:
We’re excited to announce that Payara Platform Community 7 Beta application server is now fully certified as Jakarta EE 11 […]
Managing Payara Server Just Got Smarter Imagine managing your Jakarta EE applications not just with Maven goals, but by […]
Welcome aboard the August 2025 issue of The Payara Monthly Catch! With summer in full swing, things may have felt […]
Tried using this functionality to start Payara on reboot on a linux system and got the following error hundreds of times: Starting GlassFish_lamtec-dev depends on plymouth and therefore on system facility ‘$all’ which can not be true!
Suggestions??
Hi!
That’s not an error I’ve ever seen before personally, but it looks like it’s indicating that there’s a dependency conflict in your boot services (init.d or equivalent).
I’d recommend raising this on our forum where we and others can better help you, as my only suggestion with what you’ve given me would be to scour the start-up service logs for where the conflict may be coming from.
Thanks,
Andrew
Hi,
Almost what i was looking for well it is what I was looking for but would be more help full if some example were provided.
Thanks