Details

    • Type: Sub-task Sub-task
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.1.2, 4.0
    • Fix Version/s: 3.1.2_b14
    • Component/s: docs
    • Labels:
      None

      Description

      Much of the customizability of creating services is hidden inside the catch-all "serviceproperties" args but they aren't documented.

        Issue Links

          Activity

          Hide
          Paul Davies added a comment -

          The create-service(1) man page for GlassFish 3.1 describes the --servicepropies option as follows:

          --serviceproperties

          (Oracle Solaris systems only) Specifies a colon (:)-separated list of various properties that are specific to the service. For Oracle Solaris 10, if you specify net_privaddr, the service's processes will be able to bind to the privileged ports (<1024) on the platform. You can bind to ports< 1024 only if the owner of the service is superuser, otherwise, this is not allowed.

          This man page also describes the --name option, which enables users to specify the that they will use when administering the service through Oracle Solaris SMF commands or the service management features of the Windows operating system.

          Show
          Paul Davies added a comment - The create-service(1) man page for GlassFish 3.1 describes the --servicepropies option as follows: --serviceproperties (Oracle Solaris systems only) Specifies a colon (:)-separated list of various properties that are specific to the service. For Oracle Solaris 10, if you specify net_privaddr, the service's processes will be able to bind to the privileged ports (<1024) on the platform. You can bind to ports< 1024 only if the owner of the service is superuser, otherwise, this is not allowed. This man page also describes the --name option, which enables users to specify the that they will use when administering the service through Oracle Solaris SMF commands or the service management features of the Windows operating system.
          Hide
          Byron Nevins added a comment -

          Please see this bug for more details

          Show
          Byron Nevins added a comment - Please see this bug for more details
          Hide
          Byron Nevins added a comment -

          NOW the Doc is incomplete. Now the service properties can also be used in Linux and Windows.

          Take a look in these 2 template files:
          D:\glassfish3\glassfish\lib\install\templates\Domain-service-winsw.xml.template
          D:\glassfish3\glassfish\lib\install\templates\linux-service.template

          Any of those tokens can be replaced by setting the value as a service-property.

          E.g.

          --serviceproperties DISPLAY_NAME="whatever you want"

          Note that this is a new feature for 3.1.2 and 4.0. For released versions the doc is correct, it only applies to SMF.

          This feature was added because a user pointed out that it is impossible to specify a custom display name for a service...

          Show
          Byron Nevins added a comment - NOW the Doc is incomplete. Now the service properties can also be used in Linux and Windows. Take a look in these 2 template files: D:\glassfish3\glassfish\lib\install\templates\Domain-service-winsw.xml.template D:\glassfish3\glassfish\lib\install\templates\linux-service.template Any of those tokens can be replaced by setting the value as a service-property. E.g. --serviceproperties DISPLAY_NAME="whatever you want" Note that this is a new feature for 3.1.2 and 4.0. For released versions the doc is correct, it only applies to SMF. This feature was added because a user pointed out that it is impossible to specify a custom display name for a service...
          Hide
          Byron Nevins added a comment -

          Contents of the template file:

          <service>
          <id>%%%NAME%%%</id>
          <name>%%%DISPLAY_NAME%%%</name>
          <description>GlassFish Server</description>
          <executable>%%%AS_ADMIN_PATH%%%</executable>
          <logpath>%%%LOCATION%%%/%%%ENTITY_NAME%%%/bin</logpath>
          <logmode>reset</logmode>
          <depend>tcpip</depend>
          <startargument>%%%START_COMMAND%%%</startargument>
          <startargument>--verbose</startargument>
          %%%CREDENTIALS_START%%%%%%LOCATION_ARGS_START%%%<startargument>%%%ENTITY_NAME%%%</startargument>
          <stopargument>%%%STOP_COMMAND%%%</stopargument>
          %%%CREDENTIALS_STOP%%%%%%LOCATION_ARGS_STOP%%%<stopargument>%%%ENTITY_NAME%%%</stopargument>
          </service>

          ================================

          Actually now that I look at the template – DISPLAY_NAME is the one-and-only thing that a user should optionally set as a service-property in Windows.

          Show
          Byron Nevins added a comment - Contents of the template file: <service> <id>%%%NAME%%%</id> <name>%%%DISPLAY_NAME%%%</name> <description>GlassFish Server</description> <executable>%%%AS_ADMIN_PATH%%%</executable> <logpath>%%%LOCATION%%%/%%%ENTITY_NAME%%%/bin</logpath> <logmode>reset</logmode> <depend>tcpip</depend> <startargument>%%%START_COMMAND%%%</startargument> <startargument>--verbose</startargument> %%%CREDENTIALS_START%%%%%%LOCATION_ARGS_START%%%<startargument>%%%ENTITY_NAME%%%</startargument> <stopargument>%%%STOP_COMMAND%%%</stopargument> %%%CREDENTIALS_STOP%%%%%%LOCATION_ARGS_STOP%%%<stopargument>%%%ENTITY_NAME%%%</stopargument> </service> ================================ Actually now that I look at the template – DISPLAY_NAME is the one-and-only thing that a user should optionally set as a service-property in Windows.
          Hide
          Paul Davies added a comment -

          Fixed in revision 51521.

          Show
          Paul Davies added a comment - Fixed in revision 51521.

            People

            • Assignee:
              Paul Davies
              Reporter:
              Byron Nevins
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: