[jboss-jira] [JBoss JIRA] (WFCORE-1386) Accept properties file in scripts for starting as a service
Marek Kopecký (Jira)
issues at jboss.org
Thu Mar 14 09:44:00 EDT 2019
[ https://issues.jboss.org/browse/WFCORE-1386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708368#comment-13708368 ]
Marek Kopecký commented on WFCORE-1386:
---------------------------------------
[~esantana]: It seems that your comment is not related with running WF as a service on Windows, WF currently contains ./docs/contrib/scripts/service/service.bat file for this and according to the help text for this file, it seems that this feature is not in WF:
{noformat}
WildFly Service Script for Windows
Usage:
service install <options> , where the options are:
/startup : Set the service to auto start
Not specifying sets the service to manual
/jbossuser <username> : JBoss username to use for the shutdown command.
/jbosspass <password> : Password for /jbossuser
/controller <host:port> : The host:port of the management interface.
default: localhost:9990
/host [<domainhost>] : Indicates that domain mode is to be used,
with an optional domain/host controller name.
default: master
Not specifying /host will install JBoss in
standalone mode.
Options to use when multiple services or different accounts are needed:
/name <servicename> : The name of the service
default: Wildfly
/display <displayname> : The display name of the service, use double
quotes to allow spaces.
Maximum 256 characters.
default: WildFly
/desc <description> : The description of the service, use double
quotes to allow spaces.
Maximum 1024 characters.
default: WildFly Application Server
/serviceuser <username> : Specifies the name of the account under which
the service should run.
Use an account name in the form of
DomainName\UserName
default: not used, the service runs as
Local System Account.
/servicepass <password> : password for /serviceuser
Advanced options:
/config <xmlfile> : The server-config to use
default: standalone.xml / domain.xml
/hostconfig <xmlfile> : domain mode only, the host config to use
default: host.xml
/base <directory> : The base directory for server/domain content
Must be specified as a fully qualified path
default: C:\Users\Administrator\playground\wildfly-17.0.0.Beta1-SNAPSHOT\standalone or
C:\Users\Administrator\playground\wildfly-17.0.0.Beta1-SNAPSHOT\domain
/loglevel <level> : The log level for the service: Error, Info,
Warn or Debug (Case insensitive)
default: INFO
/logpath <path> : Path of the log
default depends on domain or standalone mode
/base applies when /logpath is not set.
C:\Users\Administrator\playground\wildfly-17.0.0.Beta1-SNAPSHOT\domain\log
C:\Users\Administrator\playground\wildfly-17.0.0.Beta1-SNAPSHOT\standalone\log
/debug : run the service install in debug mode
Other commands:
service uninstall [/name <servicename>]
service start [/name <servicename>]
service stop [/name <servicename>]
service restart [/name <servicename>]
/name <servicename> : Name of the service: should not contain spaces
default: Wildfly
{noformat}
> Accept properties file in scripts for starting as a service
> -----------------------------------------------------------
>
> Key: WFCORE-1386
> URL: https://issues.jboss.org/browse/WFCORE-1386
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Scripts
> Affects Versions: 2.0.0.Beta1
> Environment: Microsoft Windows
> Reporter: Roman Syroeshko
> Priority: Major
>
> Currently $JBOSS_HOME\bin\service\service.bat does not allow passing properties file. We run WildFly in domain mode using the followed command.
> {code}
> domain.bat --properties=jboss.properties
> {code}
> Now, it's impossible to install WildFly as a service like that without hacking out-of-the-box files.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
More information about the jboss-jira
mailing list