Details
-
Suggestion
-
Resolution: Won't Fix
-
None
-
Windows (WinXP, Windows 7)
Description
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
At this moment it only seems to be possible to deploy to the default server instance (the DAS) of a particular Glassfish domain.
In reality it is often necessary to deploy the application to a separate server instance, and not the default DAS instance.
This implies the need to not only create, start, and stop a domain, but also the need to be able to:
create a node agent.
start a node agent.
stop a node agent.
create a server instance.
start a server instance.
stop a server instance.
deploy an application to a particular server instance.
The above functionality would drastically increase productivity and the means to check in an early fase whether the domain-nodeagent-sever instance setup is correct.
Kind regards,
EDH
Attachments
Issue Links
- relates to
-
JRACLOUD-20366 Deployment to Glassfish server instances
- Closed
-
JRASERVER-14604 Add support for Sun Glassfish application server
- Closed
- was cloned as
-
JRASERVER-36048 Deployment to Glassfish server instances
- Closed