Execute a command in a specific session.
This operation is only valid for sessions that are connected to live, interactive sessions. When this command is issued into an artificial AP session, for example, Event Traffic Control sessions, there is no meaning. A POST to such a session returns the HTTP status 405 (Method not allowed).
None
SessionCommand in schema SessionCommand.xsd
The request contains the command that is run in the session that is the target of this HTTP method. The command text can contain the set of AP @ key abbreviations. For more information, see the key abbreviation table in the appendix on customizing special CA Automation Point files in the CA Automation Point Administrator Guide. No ‘@E’ key is required at the end of the command.
By default, the command is synchronous. This means that the API waits until any X-state on a session is cleared and the command has been transmitted to the monitored host.
Within the Command document, optionally the command can be processed asynchronously.
Supply a user ID and password in the HTTP Basic Authentication format. The user ID must be a user account with the AP Remote Viewer FULL privilege on the session that is the target of this HTTP method.
Successful result for a synchronous command = 200 = Ok
The success of a synchronous command means that the command was transmitted to the monitored host.
Success for an asynchronous command = 202 = Accepted.
The success of an asynchronous command means that the command was accepted by the AP server for later transmission to the monitored host.
None
A command is simply executed. CA Automation Point cannot access any properties of a command after it has been executed.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|