Skip to main content

IMPORTANT - Product End of Life Statement - IMPORTANT

Request RE, Survey, and Calendar 1.5 Support Ending December 31, 2020
Contact Kinetic Data Support with Questions
Kinetic Community

BMC BladeLogic Command Run

Uses the BladeLogic web services to run a CLI Command on a BladeLogic App Server.


By downloading this file, you acknowledge that you agree to our Terms of Service

Detailed Description

bladelogic.jpgThis handler uses the BMC BladeLogic web services to run a CLI Command on a BladeLogic App Server using SOAP calls. After authenticating with username, password, and app server location, the handler starts making SOAP calls to configure the CLI tunnel. It starts by making a login call with the BladeLogic username and password. It then takes the session id from the response (to help authenticate all future requests) and then assumes the role that was specified in the info values. After all the authentication is finished, the CLI command is sent with the name space, command name, and any non-empty arguments. Finally the response string from the command will be returned from the SOAP response.


Name Description
Name Space The name space of the CLI command.
Command Name The name of the CLI command.
Command Argument 1 Command argument 1.
Command Argument 2 Command argument 2.
Command Argument 3 Command argument 3.
Command Argument 4 Command argument 4.
Command Argument 5 Command argument 5.

Sample Configuration

Parameter Example Configuration
Name Space NSHScriptJob
Command Name getDBKeyByGroupAndName
Command Argument 1 /Task Jobs
Command Argument 2 Sample_Script
Command Argument 3  
Command Argument 4  
Command Argument 5  


Name Description
CLI Response This returns the response string from the CLI command.

Change Log

Version Date Description
1 2014-07-11 Initial Version