Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-3202

Missing documentation of .jbossclirc file for CLI (management-cli-guide)

    XMLWordPrintable

Details

    Description

      https://access.stage.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-7.0.beta/management-cli-guide

      EAP distribution contain runtime configuration file for jboss-cli - $JBOSS_HOME/bin/.jbossclirc which can be used to to initialize the environment when a new session is launched.

      https://developer.jboss.org/wiki/CommandLineEnvironmentVariables

      List of available commands is the same like for cli disconnected from the server.

      [pkremens@dhcp-10-40-5-180 bin] $ cat .jbossclirc | grep -v \#
help --commands
[pkremens@dhcp-10-40-5-180 bin] $ ./jboss-cli.sh 
Commands available in the current context:
batch                  connect                echo                   embed-host-controller  help                   if                     patch                  quit                   unset                  
clear                  connection-info        echo-dmr               embed-server           history                module                 pwd                    set                    version

      Attachments

        Issue Links

          blocks

          Tracker - Issue tracking a bug fix or improvement in another component JBEAP-4962 EAP7 Management CLI Guide issues tracker

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-4951 Update the default variable value in .jbossclirc file

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Verified

          Activity

            People

              dmichael@redhat.com David Michael (Inactive)
              pkremens@redhat.com Petr Kremensky (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: