en.help.task-appdeployruby.html Maven / Gradle / Ivy
To Deploy a Ruby Application
- In the navigation tree, select the Applications node.
The Applications page opens.
- In the Deployed Applications table, click the Deploy button.
The Deploy Applications or Modules page opens.
- Specify the location of the application to deploy.
- If the application is an archive file that resides on or is
accessible from the client machine, select the option Packaged File to Be Uploaded
to the Server.
The client machine is the host on which you are viewing the Administration
Console through a browser.
Click Browse to browse to the file, or type the full path
to the file.
- If the application is an archive file that resides on the server machine,
or is an unpackaged application from an exploded directory, select the option Local
Packaged File or Directory That Is Accessible From the GlassFish Server.
The server machine is the host that is running the domain administration server
(DAS).
Click Browse Files to browse to a file, or Browse Folders to
browse to a directory. Alternatively, type the full path name to the file
or directory. It is common to deploy a JRuby application from a directory.
- From the Type drop-down list, select Ruby Application.
If you specified either a Packaged File to Be Uploaded to the Server
or a Local Packaged File That Is Accessible From the GlassFish Server, the
application type is detected automatically. If you specified a Directory That Is Accessible From
the GlassFish Server, you must specify the type manually.
- In the Application Name field, retain the default name, which is the directory
name or the prefix of the file name, or type another name.
The default name appears if you chose to upload a file. The
application name must be unique.
- In the Context Root field, type a string that identifies the Ruby application.
In the URL of the Ruby application, the context root immediately follows the
port number (http://host:port/context-root/...). The context root must start with a forward slash, for
example, /hello.
- Select the Status Enabled checkbox to enable the application.
This option is selected by default. If this option is disabled, the application
is unavailable.
- Select the Force Redeploy checkbox to force redeployment if the application is already
deployed.
If this option is not selected, an attempt to deploy an application that
is already deployed results in an error. This option is disabled by default.
- In the JRuby Home field, type the path to the directory where the
JRuby container is installed.
The default location is as-install/jruby. If you specify a value for this
field, the application value overrides the JRuby Home value set for the Ruby
container.
- In the Initial Pool Size field, type the initial number of JRuby runtimes
to start.
The value must be greater than or equal to the value in the
Minimum Pool Size field and less than or equal to the value in
the Maximum Pool Size field. The default value is 1. If you
specify a value for this field, the application value overrides the Initial Pool
Size value set for the Ruby container.
- In the Minimum Pool Size field, type the minimum number of JRuby runtimes
in the pool.
The value must be less than or equal to the value in the
Initial Pool Size field and less than or equal to the value in
the Maximum Pool Size field. The default value is 1. If you
specify a value for this field, the application value overrides the Minimum Pool
Size value set for the Ruby container.
- In the Maximum Pool Size field, type the maximum number of JRuby runtimes
in the pool.
The value must be greater than or equal to the value in the
Minimum Pool Size field and greater than or equal to the value in
the Initial Pool Size field. The default value is 1. If you
specify a value for this field, the application value overrides the Maximum Pool
Size value set for the Ruby container.
- From the Framework drop-down list, select the framework on which the application is
to be deployed.
Available choices are rails, merb, sinatra, and auto-detection. The default is auto-detection.
Setting this property to a value other than auto-detection bypasses the normal, and potentially
lengthy, auto-detection process and forces deployment on the specified framework. If the deployed
application is not written for the specified framework, errors result.
- From the Rack Environment drop-down list, select the environment in which the JRuby
framework, such as Rails or Merb, runs.
Available choices are production, development, and test. The default is development.
- From the MT-Safe drop-down list, select the thread-safe setting for the framework in
which the application will run.
This property affects applications started using an auto-detected user-provided startup script. Available choices are:
- true
Specifies that the framework is thread-safe and therefore does not need a pool created for it.
- false
Specifies that the application starts with a pool of application instances, and each instance of the application is accessed by one thread at a time.
- default
The GlassFish Server tries to detect thread safety automatically. This value is the default.
This property only affects frameworks being launched where the thread safety cannot be
automatically determined. Setting this value to true does not cause an auto-detected Rails
2.1.x application to be launched in thread-safe mode, nor can it be used
to force a thread-safe framework to start in pooled mode.
- From the Virtual Servers drop-down list, select the virtual server to be associated
with this application.
- In the Description field, type a description for this application.
- Click OK.
See Also