1. To launch
the console in interactive mode:
console.exe -graphwithdate] [model]
If [-graphwithdate] is specified the current
date is added in the footer of real-time charts.
If [model] is specified, it will be opened
directly.
[model] can also contain the path to a model
file:
console.exe "c:\program files\sysload\console\model.wks"
or it can be the path to a Console Object
saved on the Management Server:
console.exe "//mgtserver/wks/model"
2. To
generate HTML Report(s) corresponding to the specified model(s):
console.exe -h model1[,model2,...] -batchticket batch.tic
[-output outputdir]
If [-output] is specified then the HTML
Reports are generated in the 'outputdir' directory.
3. To print
the specified model(s):
console.exe -p model1[,model2,...] -batchticket batch.tic
4. To
generate a set of HTML Reports described in the report.ini file:
console.exe -hr report.ini -batchticket batch.tic [-output outputdir]
If [-output] is specified then the HTML
Reports are generated in the 'outputdir' directory.
5. To print
a set of models described in the report.ini file:
console.exe -pr report.ini -batchticket batch.tic
6. To save
the result of a row or column data extraction to a text file:
console.exe -e model.ext file.txt -batchticket batch.tic
To save the result of a column data
extraction to an Excel file:
console.exe -e model_colum.ext file.xls -batchticket batch.tic
This does not apply to row data extractions.
7. To save
the result of an alert report to a text file:
console.exe -e model.erp file.txt -batchticket batch.tic
To save the result of an alert report to an
CSV file:
console.exe -e model.erp file.csv -batchticket batch.tic
To save the result of an alert report to an
Excel file:
console.exe -e model.erp file.xls -batchticket batch.tic
8. To export
the Monitored Objects and Groups from a Management Server in XML format:
console.exe -export agents -outputfile agents.xml -batchticket batch.tic
You must be connected as an Administrator to
just one Management Server.
9. To import
a list of Monitored Objects and Groups from an XML file to a Management Server:
console.exe -import agents.xml [-output output.txt] -batchticket batch.tic
You must be connected as an Administrator to
the Management Server.
10. To
propagate access rights from Groups to Monitored Objets:
console.exe -propagate_rights -batchticket batch.tic
You must be connected as an Administrator to
the Management Server.
11. To
launch a batch processing on Monitored Objects:
console.exe -agentrequest -inputfile input.sldar -outputfile result.txt -batchticket batch.tic
12. To
obtain a report on the prerequisites of Monitored Objects for SP Portal:
console.exe -agtcomp spportal -output report.txt -batchticket batch.tic
To obtain a report on the prerequisites of
Monitored Objects for AES:
console.exe -agtcomp aes -output report.txt -batchticket batch.tic
You must be connected as an Administrator to
the Management Server.
13. To apply
the Enterprise Events:
console.exe -applyevents [-force] [-outputfile report.txt] -batchticket batch.tic
This will only apply Enterprise Events with
at least one Monitored Object marked as "To Update".
If -force option is specified all the
Enterprise Events will be applied on all the attached Monitored Objects.
To apply the Enterprise Events of a specific
model:
console.exe -applyevents -modelname model [-force] [-outputfile report.txt] -batchticket batch.tic
This will only apply Events of the 'model'
Enterprise model on the Monitored Objects marked as "To Update".
If -force option is specified all the Events
of the 'model' Enterprise model will be applied on all the attached Monitored
Objects.
To apply the Enterprise Events on specific
Monitored Objects:
console.exe -applyevents -monitoredobj monitoredobj1[,monitoredobj2,...] [-force] [-outputfile report.txt]
-batchticket batch.tic
This will only apply Enterprise Events with
at least one of the specified Monitored Objects marked as "To
Update".
If -force option is specified all the
Enterprise Events attached to specified Monitored Objects will be applied.
The Monitored Objects are defined whereas by
their label whereas by the string « mgtserver;type;name;instance ».
console.exe -applyevents -monitoredobj group1[,group2,...] [-force] [-outputfile report.txt] -batchticket batch.tic
This will only apply Enterprise Events with
at least one of the Monitored Objects of specified Groups marked as "To
Update".
If -force option is specified all the
Enterprise Events attached to Monitored Objects of specified Groups will be
applied.
The Groups are defined by the string «
//mgtserver/class.type/name ».
14. To apply
the Enterprise Entities:
console.exe -applyentities [-force] [-outputfile report.txt] -batchticket batch.tic
This will only apply Enterprise Entities
with at least one Monitored Object marked as "To Update".
If -force option is specified all the
Enterprise Entities will be applied on all the attached Monitored Objects.
To apply the Enterprise Entities of a
specific model:
console.exe -applyentities -modelname model [-force] [-outputfile report.txt] -batchticket batch.tic
This will only apply Entities of the 'model'
Enterprise model on the Monitored Objects marked as "To Update".
If -force option is specified all the
Entities of the 'model' Enterprise model will be applied on all the attached
Monitored Objects.
To apply the Enterprise Entities on specific
Monitored Objects:
console.exe -applyentities -monitoredobj monitoredobj1[,monitoredobj2,...] [-force] [-outputfile report.txt]
-batchticket batch.tic
This will only apply Enterprise Entities
with at least one of the specified Monitored Objects marked as "To
Update".
If -force option is specified all the
Enterprise Entities attached to specified Monitored Objects will be applied.
The Monitored Objects are defined whereas by
their label whereas by the string « mgtserver;type;name;instance ».
console.exe -applyentities -monitoredobj group1[,group2,...] [-force] [-outputfile report.txt] -batchticket batch.tic
This will only apply Enterprise Entities
with at least one of the Monitored Objects of specified Groups marked as
"To Update".
If -force option is specified all the
Enterprise Entities attached to Monitored Objects of specified Groups will be
applied.
The Groups are defined by the string «
//mgtserver/class.type/name ».
15. To apply
the Enterprise Diagnostic Metrics:
console.exe -applymetrics [-force] [-outputfile report.txt] -batchticket batch.tic
This will only apply Enterprise Diagnostic
Metrics with at least one Monitored Object marked as "To Update".
If -force option is specified all the
Enterprise Diagnostic Metrics will be applied on all the attached Monitored
Objects.
To apply the Enterprise Diagnostic Metrics
of a specific model:
console.exe -applymetrics -modelname model [-force] [-outputfile report.txt] -batchticket batch.tic
This will only apply Diagnostic Metrics of
the 'model' Enterprise model on the Monitored Objects marked as "To
Update".
If -force option is specified all the
Enterprise Diagnostic Metrics of the 'model' Enterprise model will be applied
on all the attached Monitored Objects.
To apply the Enterprise Diagnostic Metrics
on specific Monitored Objects:
console.exe -applymetrics -monitoredobj monitoredobj1[,monitoredobj2,...] [-force] [-outputfile report.txt]
-batchticket batch.tic
This will only apply Enterprise Diagnostic
Metrics with at least one of the specified Monitored Objects marked as "To
Update".
If -force option is specified all the
Enterprise Diagnostic Metrics attached to specified Monitored Objects will be
applied.
The Monitored Objects are defined whereas by
their label whereas by the string « mgtserver;type;name;instance ».
console.exe -applymetrics -monitoredobj group1[,group2,...] [-force] [-outputfile report.txt] -batchticket batch.tic
This will only apply Enterprise Diagnostic
Metrics with at least one of the Monitored Objects of specified Groups marked
as "To Update".
If -force option is specified all the
Enterprise Diagnostic Metrics attached to Monitored Objects of specified Groups
will be applied.
The Groups are defined by the string «
//mgtserver/class.type/name ».
16. To
reconstruct Enterprise Entities:
console.exe -reconstructentities -inputfile input.xml [-outputfile result.txt] -batchticket batch.tic
This option allows to reconstruct Enterprise
Entities from a xml File.
Only models specified in this file will be
impacted.
Entities will be created, updated or marked
for deletion.
Deployment will be necessary for impacted
MOs.
17. To
replace Monitored Objects in Workspaces, Dashboards :
console.exe -coreplacemo -inputfile input.xml [-outputfile result.txt] -batchticket batch.tic
This option allows to replace MO by another
in Workspaces, Dashboards.
18. To
display this help window:
console.exe -?
Batch
Ticket:
The console batch commands need a batch
ticket for authentication.
The batch ticket can be generated from the
'Environment' menu of the graphical console interface.