Launching the console via command line

The BMC Client Management console can also be launched via the command line. In this case it can be opened directly for a specific device and at a specific functionality, such as remote control for device X.


Related topics

Installing silently

Downloading-and-installing-the-BMC-Helix-Client-Management-console

Launching-the-web-console-for-device-access

Launching-operational-rules-and-software-deployments-through-XML

Launching-patch-deployments-and-assigning-monitoring-policies-through-XML

Prerequisite

The console jar file is located at  %APPDATA%/\BMC Software\Client Management\Web Start and java is located in the bin folder. You must first install the web start package to use the command line to launch the console. For more information about installing the web start package, see  Downloading and installing the BMC Helix Client Management console .

To launch the console on the dashboard or on a specific node of a device by using command line

  1. Open a terminal window.

  2. Do one of the following:

      • To open the console on the dashboard, enter the following command.NumaraFootprintsAssetCore.jar  -u myusername -p mypassword -s 1610

        To open the console on a device/functionality, you must enter the values for -u, -p, and -s . If you do not enter these values, you will be prompted to enter your login credentials.

      • To open the console directly on a specific node of a device on your network, use -n or -i with a context. Refer to the following examples:
        • To view the inventories of a device:
          java -jar../../../NumaraFootPrintsAssetCore.jar -u <login> -p <password> -s <server>:<port> -i <deviceid> -inv
        • To open a remote control session on a device:
          java -jar../../../NumaraFootPrintsAssetCore.jar -u <login> -p <password> -s <server>:<port> -i <deviceid> -rcd

        • To restart a device:
          java -jar../../../NumaraFootPrintsAssetCore.jar -u <login> -p <password> -s <server>:<port> -i <deviceid> -restart

          If the device does not exist or you do not have sufficient rights to access it, an error message is displayed and the console opens on the dashboard.

        • To communicate with the agent in the secure mode by using SSL:

          java -jar../../../NumaraFootPrintsAssetCore.jar -u <login> -p <password> -s<server>:<port> -ssl 2

          If the certificate is not located at the default path

          java -jar../../../NumaraFootPrintsAssetCore.jar -u <login> -p <password> -s<server>:<port> -ssl 2 -certpath C:\_Platform\12.8\console\certs

    The hierarchy is displayed in the left panel of the console in Device Groups > Your Device Group. A device can exist under several nodes, however, when you open the console by using command line, the device opens in one of the two nodes: Device Topology and Device Groups. When you use the command line to open the console, the console opens on the device node that is first returned by the search mechanism, which is, by default, a node existing in Device Groups. If the console that you are trying to open is not a member of any group, the console opens on a device in Device Topology. If the search command line option is defined, the console opens on the device shown directly under the Search node.

    Refer to the following table for a list of commands and contexts that you can use to open the console.

Option

Description

Commands

-u

Specifies the username of the BMC Client Management user

-p

Specifies the password of the BMC Client Management user

-s

Specifies the server:port number to communicate with the agent

-ssl

Defines if the agent communication is secured via SSL. The possible values are integers between 0 and 3:

  • 0 - Agent accepts both secure and non-secure communication, however it sends only non-secure communication.
  • 1 - Agent accepts both secure and non-secure communication, however it sends only secure communication.
  • 2 - Agent only communicates in secure mode, that is, it only sends and receives secure communication. This is the preferred mode.
  • 3 - Agent only communicates in secure mode, but all participants (agents, consoles) must have SSL certificates and perform mutual authentication.

-cert

Specifies the SSL certificate to be used in case of SSL=3

-certpath

Specifies the directory where certificates are located. It is required when the certificates are not located at the default path, which is ${CONSOLE_MAIN_DIR}/certs/.

-n

Specifies the device name

-i

Specifies the device ID

Context

-search

Opens the Search node

-ConfigSummary, -inv

Opens the Inventory node

-op

Opens the Assigned Operational Rules node

-RemoteControl, -rc

Opens the Remote Control node

-rcd

Opens a remote control session

-da

Opens the Direct Access node

-FileSystem

Opens the File System node

-Registry

Opens the Registry node

-Services

Opens the Services node

-Events

Opens the Windows Events node

-Processes

Opens the Process Management node

-Ping

Pings the remote device

-Reboot

Reboots the remote device

-Restart

Restarts the agent

-Shutdown

Shuts down the remote device

-WakeUp

Wakes up the remote device

-FileTransfer

Transfers the files between remote device and local device