-
Enhancement
-
Resolution: Done
-
Major
-
None
-
None
Currently, additions tot he deployment scanners are limited to locally running servers. This is due to a lack of API allowing accurate discovery of what folders need to be added for remote servers, specifically no way for as.core classes to discover what the remote server home is, what the remote configuration folder is, etc. There is a lack of api here, and that will need to be fixed before this issue can work.
Remember: If a remote server is not running with its management ports exposed, do not attempt to add the scanners, as the management connections will fail.
- relates to
-
JBIDE-17180 Disable custom deployment settings for remote servers without management port exposed
- Closed
-
JBIDE-13263 Workspace metadata deployment does not work for AS 6
- Closed
-
JBIDE-17181 Unhandled loop exception in JMX view using wf8, expose management port
- Closed
-
JBIDE-18912 Custom deploy dir with remote server using filesystem operations does not work
- Open
-
JBIDE-13444 deployment scanner additions should be called from behavior
- Closed