Performing Functions by Using a Command Line

Use the apm_init command to initialize the APM ETL processes. Manual steps are also required after you run this command. See Enabling and Initializing the APM ETL for complete information about the initialization process.

The syntax of the command is: apm_init(.sh|.bat) [-fvdh -–hostAlias]

Options are:

Use the emi_init command to initialize the EMI framework (provided as part of SAS Environment Manager Extended Monitoring), or to enable the ACM ETL, APM ETL, or solution kits ETL. Issue this command as part of the process of initializing and enabling the components of SAS Environment Manager Service Management Architecture. See Initializing and Enabling the Service Management Architecture for more information about using this command.

The syntax of the command is: emi_init(.sh|.bat) [-dfhiksv] [(—–enable|—–disable) <ACM,APM,KITS,ALL)] [—–vafeed <ON|OFF>] [—–resetDB —–resetFlags]

Options are:

The APM ETL processes are specified to run at 1 AM. Use the master_apm_etl command if you want to run the processes manually or at another time. The command runs the processes to extract the information from the SAS logs and load it into the SAS Environment Manager Data Mart. You can use a scheduler to issue the command at a specified time to run the ETL processes at a time other than the default. You can also issue the command yourself to run the processes immediately. However, because the SAS logs roll over at midnight, whenever the ETL processes run after midnight, they always use the same data that was collected during the previous 24 hours.

Although you can run the ETL process at any time, the stored process reports expire at midnight. When you display a report, it uses data from the SAS Environment Manager Data Mart, and then the report is cached. When you display the report again, the cached report is displayed. After midnight, the cached report expires and the report is generated again when you select it. Suppose you display a report that uses data from the APM ETL, and then run the master_apm_etl command. If you then display the report again, the report will still use the cached data, rather than the data that the ETL process just loaded.

The syntax of the command is: master_apm_init(.sh|.bat) [-dhv -–evdebug <0–3>]

Options are:

The ACM ETL processes are specified to run at 12 midnight. Use the master_acm_etl command if you want to run the processes manually or at another time. The command runs the processes to extract the ACM data and load it into the SAS Environment Manager Data Mart. You can use a scheduler to issue the command at a specified time to run the ETL processes at a time other than the default. You can also issue the command yourself to run the processes immediately.

Although you can run the ETL process at any time, the stored process reports expire at midnight. When you display a report, it uses data from the SAS Environment Manager Data Mart, and then the report is cached. When you display the report again, the cached report is displayed. After midnight, the cached report expires and the report is generated again when you select it. Suppose you display a report that uses data from the ACM ETL, and then run the master_acm_etl command. If you then display the report again, the report will still use the cached data, rather than the data that the ETL process just loaded.

The syntax of the command is: master_acm_init(.sh|.bat) [-dhv -–evdebug <0–3>]

Options are:

The solution kit ETL processes that load data collected by the installed solution kits run at 2 AM. Use the master_kits_etl command if you want to run the processes manually or at another time. The command runs the processes to extract the solution kit data and load it into the SAS Environment Manager Data Mart. You can use a scheduler to issue the command at a specified time to run the ETL processes at a time other than the default. You can also issue the command yourself to run the processes immediately.

Although you can run the ETL process at any time, the stored process reports expire at midnight. When you display a report, it uses data from the SAS Environment Manager Data Mart, and then the report is cached. When you display the report again, the cached report is displayed. After midnight, the cached report expires and the report is generated again when you select it. Suppose you display a report that uses data from a solution kit, and then run the master_kits_etl command. If you then display the report again, the report will still use the cached data, rather than the data that the ETL process just loaded.

The syntax of the command is: master_kits_init(.sh|.bat) [-dhvx -–evdebug <0–3>]

Options are:

Use the validate command to validate the structure of the SAS Environment Manager framework and to find any errors or changes. This command runs during the initialization process to verify that the framework is correct before anything new is added. The command has four levels:

The syntax of the command is: validate(.sh|.bat) [-qvdh] [–l <1|2|3|4>] [-p| -–userPolicy <IGNORE|WARN|ERROR>]

Options are:

Use the agentClone command to create a machine-neutral archive (.tar) file of the SAS Environment Manager agent. You can then copy the file to a server (such as a SAS grid server) that is not part of the standard SAS environment installed by the SAS Deployment Wizard. The agent provides monitoring support for servers in a SAS grid.

The syntax of the command is: agentClone(.sh|.bat) [-vdh] [-t <Minimal|Select>] [–w <workingDir>] [tarfile]

Options are:

Use the create_event command to manually create a SAS Environment Manager event. After it is created, the event appears in the SAS Environment Manager Event Center.

The syntax of the command is: createEvent(.sh|.bat) [-vdh] [-f <file>] [–l <INFO|WARN|ERROR>] [–s <source>]

Options are:

Use the create_http_checks command to create an HTTP check service based on the definitions in the file httpChecks.json. This file contains all of the predefined HTTP check definitions, but not all of these definitions are created by default. To create one of the definitions:

To verify that the service has been created, sign on to SAS Environment Manager and select BrowseServices. The new HTTP check service is listed,

The syntax of the command is: create_http_checks(.sh|.bat) [-fxvdh] [-t <taskfile>]

Options are:

Solution kits provide customized metrics and reports to support specific SAS solutions and applications. Use the ev_kit_installer command to install new solution kits.

The syntax of the command is: ev_kit_installer(.sh|.bat) [-fvdh] [-k <kitname|ALL>]

Options are:

Use the runSASJob command to run a SAS program with the SAS autoexec and environment necessary for the program to access the SAS Environment Manager Data Mart and the EMI framework.

The syntax of the command is: runSASJob(.sh|.bat) [-bdhv] [––args <args>] [––autocall <autocall_dir>] [––autoexec <(BATCH|APM|KITS|STP) | <autoexec_file>] [––config <config_file>] [––evdebug <0–3>] [––log <log_results_file>] [––nodms] [––printfile <output_file>] [––work <saswork_dir>] [––workdir <working_dir>]

Options are: