# [wildfly-dev] Windows Batch Scripts

28 messages
12
Open this post in threaded view
|

## Re: [wildfly-dev] Windows Batch Scripts

 Well I think that if PowerShell will bring improvements to windows scripts, and that to this date we consider WildFly as an advanced application server, then is fine to make a requirement to have powershell installed. Jorge Solórzanohttp://www.jorsol.com On Wed, May 29, 2013 at 9:51 AM, James R. Perkins wrote: PowerShell is available as a separate download[1] for WinXP FWIW.  Not that we should force the use, but it is available. [1]: http://www.microsoft.com/en-us/download/details.aspx?id=7217 On 05/29/2013 08:35 AM, Jason Greene wrote: I think we should also move the .bat files into a separate WinXP directory (the only platform that JDK7 supports which doesn't have powershell) to avoid accidental clicking or execution. On May 29, 2013, at 10:28 AM, Brian Stansberry [hidden email] wrote:  No, all .bat scripts. The basic goal would be to make them as close in functionality to the .sh scripts as possible. On 5/29/13 10:21 AM, Spolti wrote:  We need rewrite all .sh script in psh? On 05/29/2013 11:29 AM, Brian Stansberry wrote:  We've planned for a while to create powershell variants for all our Windows scripts and to basically deprecate the old ones.[1] If someone wants to take that on, please contact Tomaz Cerar. He's unavailable for a couple weeks, so if you urgently want to take it on, let me know. [1] https://issues.jboss.org/browse/WFLY-676 On 5/27/13 6:59 AM, Spolti wrote:  :), Is the best way use powershell? Or we can put a dependency in standalone/domain.bacth, or something like that? On 05/27/2013 08:52 AM, Nicklas Karlsson wrote:  Only pre-installed on Windows7/Server 2008+ On Mon, May 27, 2013 at 2:45 PM, Spolti <[hidden email] [hidden email]> wrote: All windows versions have powershell instaled by default? On 05/27/2013 07:26 AM, Tristan Tarrant wrote:  Powershell ? On 05/24/2013 01:37 PM, Dimitris Andreadis wrote:  The problem with spaces in the path on Windows always surfaces   one way or another. I think  we need better automated testing for the scripts. I agree with Stan, switching to .exe is a bad idea. On 17/05/2013 14:29, [hidden email]   [hidden email] wrote:  On 5/16/2013 9:51 PM, James R. Perkins wrote:  Hello All, There was an issue found with the Windows batch scripts if   the JBOSS_HOME path had a space  or a ) in it. I created a fix and PR to fix the issue [1]. If anyone has any good or better ideas on how to make this   cleaner please let me know. We  are toying with the idea of just using an EXE instead of   batch scripts, but any input from  someone with more Windows batch scripting experience than me   is welcome.  Whatever you do, don't turn it into an EXE. For better or   worse, customers have always  relied on being able to hack the batch script. I think you'd   get a lot of pushback.  [1]: https://github.com/wildfly/wildfly/pull/4520 -- James R. Perkins JBoss by Red Hat  _______________________________________________ wildfly-dev mailing list [hidden email] [hidden email] https://lists.jboss.org/mailman/listinfo/wildfly-dev  _______________________________________________ wildfly-dev mailing list [hidden email] [hidden email] https://lists.jboss.org/mailman/listinfo/wildfly-dev   -- Regards, ______________________________________ Filippe Costa Spolti Linux User n°515639 - http://counter.li.org/ [hidden email] [hidden email] +55 34 9679-2388 "Be yourself" _______________________________________________ wildfly-dev mailing list [hidden email] [hidden email] https://lists.jboss.org/mailman/listinfo/wildfly-dev -- Nicklas Karlsson, +358 40 5062266 Vaakunatie 10 as 7, 20780 Kaarina  -- Regards, ______________________________________ Filippe Costa Spolti Linux User n°515639 -http://counter.li.org/ [hidden email] +55 34 9679-2388 "Be yourself" _______________________________________________ wildfly-dev mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/wildfly-dev  -- Brian Stansberry Principal Software Engineer JBoss by Red Hat _______________________________________________ wildfly-dev mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/wildfly-dev  -- Jason T. Greene WildFly Lead / JBoss EAP Platform Architect JBoss, a division of Red Hat _______________________________________________ wildfly-dev mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/wildfly-dev  -- James R. Perkins JBoss by Red Hat _______________________________________________ wildfly-dev mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/wildfly-dev _______________________________________________ wildfly-dev mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/wildfly-dev
Open this post in threaded view
|

## Re: [wildfly-dev] Windows Batch Scripts

 +1 I don't think downloading PowerShell is too much to ask.  If you are crazy enough to use WinXP, you shouldn't be surprised that you have to add something to make it work. On 5/29/2013 12:12 PM, Jorge Solórzano wrote: Well I think that if PowerShell will bring improvements to windows scripts, and that to this date we consider WildFly as an advanced application server, then is fine to make a requirement to have powershell installed. Jorge Solórzano http://www.jorsol.com On Wed, May 29, 2013 at 9:51 AM, James R. Perkins wrote: PowerShell is available as a separate download[1] for WinXP FWIW.  Not that we should force the use, but it is available. [1]: http://www.microsoft.com/en-us/download/details.aspx?id=7217 On 05/29/2013 08:35 AM, Jason Greene wrote: I think we should also move the .bat files into a separate WinXP directory (the only platform that JDK7 supports which doesn't have powershell) to avoid accidental clicking or execution. On May 29, 2013, at 10:28 AM, Brian Stansberry [hidden email] wrote:  No, all .bat scripts. The basic goal would be to make them as close in functionality to the .sh scripts as possible. On 5/29/13 10:21 AM, Spolti wrote:  We need rewrite all .sh script in psh? On 05/29/2013 11:29 AM, Brian Stansberry wrote:  We've planned for a while to create powershell variants for all our Windows scripts and to basically deprecate the old ones.[1] If someone wants to take that on, please contact Tomaz Cerar. He's unavailable for a couple weeks, so if you urgently want to take it on, let me know. [1] https://issues.jboss.org/browse/WFLY-676 On 5/27/13 6:59 AM, Spolti wrote:  :), Is the best way use powershell? Or we can put a dependency in standalone/domain.bacth, or something like that? On 05/27/2013 08:52 AM, Nicklas Karlsson wrote:  Only pre-installed on Windows7/Server 2008+ On Mon, May 27, 2013 at 2:45 PM, Spolti <[hidden email] [hidden email]> wrote: All windows versions have powershell instaled by default? On 05/27/2013 07:26 AM, Tristan Tarrant wrote:  Powershell ? On 05/24/2013 01:37 PM, Dimitris Andreadis wrote:  The problem with spaces in the path on Windows always surfaces   one way or another. I think  we need better automated testing for the scripts. I agree with Stan, switching to .exe is a bad idea. On 17/05/2013 14:29, [hidden email]   [hidden email] wrote:  On 5/16/2013 9:51 PM, James R. Perkins wrote:  Hello All, There was an issue found with the Windows batch scripts if   the JBOSS_HOME path had a space  or a ) in it. I created a fix and PR to fix the issue [1]. If anyone has any good or better ideas on how to make this   cleaner please let me know. We  are toying with the idea of just using an EXE instead of   batch scripts, but any input from  someone with more Windows batch scripting experience than me   is welcome.  Whatever you do, don't turn it into an EXE. For better or   worse, customers have always  relied on being able to hack the batch script. I think you'd   get a lot of pushback.  [1]: https://github.com/wildfly/wildfly/pull/4520 -- James R. Perkins JBoss by Red Hat  _______________________________________________ wildfly-dev mailing list [hidden email] [hidden email] https://lists.jboss.org/mailman/listinfo/wildfly-dev  _______________________________________________ wildfly-dev mailing list [hidden email] [hidden email] https://lists.jboss.org/mailman/listinfo/wildfly-dev   -- Regards, ______________________________________ Filippe Costa Spolti Linux User n°515639 - http://counter.li.org/ [hidden email] [hidden email] +55 34 9679-2388 "Be yourself" _______________________________________________ wildfly-dev mailing list [hidden email] [hidden email] https://lists.jboss.org/mailman/listinfo/wildfly-dev -- Nicklas Karlsson, +358 40 5062266 Vaakunatie 10 as 7, 20780 Kaarina  -- Regards, ______________________________________ Filippe Costa Spolti Linux User n°515639 -http://counter.li.org/ [hidden email] +55 34 9679-2388 "Be yourself" _______________________________________________ wildfly-dev mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/wildfly-dev  -- Brian Stansberry Principal Software Engineer JBoss by Red Hat _______________________________________________ wildfly-dev mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/wildfly-dev  -- Jason T. Greene WildFly Lead / JBoss EAP Platform Architect JBoss, a division of Red Hat _______________________________________________ wildfly-dev mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/wildfly-dev  -- James R. Perkins JBoss by Red Hat _______________________________________________ wildfly-dev mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/wildfly-dev _______________________________________________ wildfly-dev mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/wildfly-dev  _______________________________________________ wildfly-dev mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/wildfly-dev
Open this post in threaded view
|

## Re: [wildfly-dev] Windows Batch Scripts

Open this post in threaded view
|

## Re: [wildfly-dev] Windows Batch Scripts

Open this post in threaded view
|

## Re: [wildfly-dev] Windows Batch Scripts

 >Yes, WFLY-676 has the wrong title. It should be "Preserve James Perkins' Sanity". Remember also to change the type to "Enhancement" in that case ;-) But on the topic, is this related to https://issues.jboss.org/browse/WFLY-223 ? Or is the whole native connector/prunsrv JBossWeb-related? What is the correct way of starting WF as a windows service (and are there batch scripts that need to be converted there)? _______________________________________________ wildfly-dev mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/wildfly-dev
Open this post in threaded view
|

## Re: [wildfly-dev] Windows Batch Scripts

 On 5/29/13 11:39 PM, Nicklas Karlsson wrote: >> Yes, WFLY-676 has the wrong title. It should be "Preserve James Perkins' Sanity". > > Remember also to change the type to "Enhancement" in that case ;-) > > But on the topic, is this related to > https://issues.jboss.org/browse/WFLY-223 ? I don't see WFLY-676 and WFLY-223 as being part of the same task. > Or is the whole native > connector/prunsrv JBossWeb-related? No. prunmgr.exe and prunsrv.exe are general usage executables from Apache Commons.[1] > What is the correct way of > starting WF as a windows service (and are there batch scripts that > need to be converted there)? > AIUI, to install as a service, it's prunsrv.exe install path\to\[standalone|domain].bat I confess I haven't tried this. I've never seen any other Windows startup scripts besides standalone/domain.bat. [1] http://commons.apache.org/daemon/procrun.html-- Brian Stansberry Principal Software Engineer JBoss by Red Hat _______________________________________________ wildfly-dev mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/wildfly-dev
Open this post in threaded view
|

## Re: [wildfly-dev] Windows Batch Scripts

 On Fri, 2013-05-31 at 11:53 -0500, Brian Stansberry wrote: > AIUI, to install as a service, it's > > prunsrv.exe install path\to\[standalone|domain].bat If only it was that simple. The one I have for EAP 6 (I'd assume it would work for WilfFly too) is: prunsrv.exe install JBossEAP6 --DisplayName="JBoss EAP 6" --LogLevel=INFO --LogPath="%JBOSS_HOME%\standalone\log" --LogPrefix=service --StdOutput=auto --StdError=auto --StartMode=exe --StartImage=cmd.exe --StartPath="%JBOSS_HOME%\bin" ++StartParams="/c \"set NOPAUSE=Y ^^^&^^^& standalone.bat\"" --StopMode=exe --StopImage=cmd.exe --StopPath="%JBOSS_HOME%\bin"  ++StopParams="/c jboss-cli.bat --controller=localhost:9999 --connect --command=:shutdown" That's just the simplified version which doesn't deal with domain mode, needing credentials because it's running as a different user and so on :( > I confess I haven't tried this. I've never seen any other Windows > startup scripts besides standalone/domain.bat. https://bugzilla.redhat.com/show_bug.cgi?id=900708 has the current iteration of a script to set this up that various people have been working on for EAP 6, and assuming it works for WF as-is, could probably be added. -- James "Doc" Livingston JBoss Support Engineering Group _______________________________________________ wildfly-dev mailing list [hidden email] https://lists.jboss.org/mailman/listinfo/wildfly-dev