-
Bug
-
Resolution: Obsolete
-
Major
-
None
-
7.0.0.GA
-
None
https://access.stage.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0/configuration-guide/
Apart from interactive and non-interactive mode (JBEAP-5018), CLI can also be used programmatically via CLI public api. We should reflect this in product documentation.
CLI public api upstream documentation and example:
- https://developer.jboss.org/wiki/JBossAS7Command-linePublicAPI
User can use any JVM-based scripting language using a simplified wrapper class for the CLI API - org.jboss.as.cli.scriptsupport.CLI see comments
- https://developer.jboss.org/wiki/AdvancedCLIScriptingWithGroovyRhinoJythonEtc
If user wants to connect to a remote JBoss EAP instance without installing the server on his local machine, he can use the CLI remote client jar. It is called jboss-cli-client.jar and it is located in <JBOSS_HOME>/bin/client (also available as Maven dependency)
- https://developer.jboss.org/wiki/UsingTheCLIRemoteClientJar
Some other resources I found:
- http://www.mastertheboss.com/jboss-server/jboss-script/discover-wildfly-jboss-resources-from-java-code
- blocks
-
JBEAP-4962 EAP7 Management CLI Guide issues tracker
- Closed