[
https://issues.jboss.org/browse/AS7-5781?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-5781:
---------------------------------------
Doing this would involve a thread under the control of a Host Controller scanning a
filesystem location and invoking commands to update the domain-wide configuration. This
has a couple implications:
1) The scanner could not be part of a subsystem, as it is in a standalone server. A Host
Controller does not install runtime services for subsystems. It only tracks their
configuration in order to provide that configuration to the servers under its control.
This would mean elevating the scanner notion into the core AS, which is a concern.
2) Only the master Host Controller would be able to be configured with such a scanner.
Only the master is allowed to make updates to the domain wide configuration.
The basic implementation difference between such a scanner and the one currently used for
standalone servers is the addition of configurations for which server-groups should be
affected by the scanner. The list of management operations generated by the scanner would
then need to include the relevant server-group-level operations. This would add a fair
amount of complexity, particularly around some of the edge cases, such as the user adding
a new server-group to the scanner's config when the HC is not running -- this would
require detecting the need to add the relevant deployments to the new server group upon
boot. Much more problematic is the case where a user *removes* a server group from the
scanner's config when the HC is not running.
Similar issues exist regarding interaction between this scanner and other administrative
clients, such as the web based admin console. What happens if an admin using the console
removes a scanner-controlled deployment from a particular server-group?
Filesystem deployment scanner for a managed domain
--------------------------------------------------
Key: AS7-5781
URL:
https://issues.jboss.org/browse/AS7-5781
Project: Application Server 7
Issue Type: Enhancement
Components: Domain Management
Affects Versions: 7.1.0.Final
Environment: Ubuntu 12.04 Os , JBOSS As 7.1.0 final
Reporter: hitesh yadav
Original Estimate: 1 day, 4 hours
Remaining Estimate: 1 day, 4 hours
Is there any folder or path at which if any .war is put, in such a way that when JBOSS AS
7.1.0 start in domain mode the .war file deploy in Master node and it's related slave
Node.
For Example......... In standalone mode if we put .war file in
/jboss-as-7.1.0.Final/standalone/deployments/ folder and start the JBOSS AS 7.1.0 in
standalone mode ,the .war deploy properly.......i want same thing domain mode, in
other-server-group .....
Means the requirement is that the .war file should put in one folder and when JBOSS AS
7.1.0 start in domain mode the .war file should deploy in other-server-group
.............
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira