The AE JMX agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host facilitates using MBeans in SAP NetWeaver.
The statusThis represents the condition of a task (such as active, blocked, generating). of the J2EE Engine can be queried via JMX. The output information is also displayed in the Visual Administrator under Server -> Services -> Monitoring.
All the Visual Administrator's functions are provided via MBeans and can also be used in AE.
Limitation: AE cannot use JMX operations or attributes that use SAP-specific classes (for example, com.sapmarkets.bam.applicationAn application is a software which helps a user to fulfill specific tasks. In the context of ARA see also: Application entity..User) or complex data structures such as lists, maps, or arrays.
The AE MBean Browser in the JXM jobAn Automation Engine object type for a process that runs on a target system. displays a maximum of 300 MBeans. A search filter facilitates the search for particular MBeans (right-click the tree structure -> apply filter...).
For example: The number of unsuccessful loginAn Automation Engine object type that stores account credentials used by agents on target systems. attempt should be queried. The first illustration shows this value below the node Security -> Aggregated Data. Therefore, you can filter for "*Security/Aggregated Data/UnsuccessfulLogonAttemptsCount*" in the MBean Browser. Exactly one MBean is returned in the AE environmentAn Environment consists of Deployment Targets which represent your endpoints. Different environments are used for different phases in the software delivery cycle, for example Development, QA, Staging, Production. An environment is typically set up once and used by several applications..
Here you can select one of the following attributes: "Value", "MaxValue" or "MinValue". An AE job can be scheduled that queries the number of error messages periodically.
The Visual Administrator also configures, starts and stops services. As it also uses JMX MBeans, this functionPre-defined run book template in the Automation Engine. One single step only, e.g. Start Windows Service, Copy file,… is available via the agent.
Services are listed in the Visual Administrator under Server -> Services:
For example: The Telnet service should be started or stopped.
You can filter "*SAP_J2EEServicePerNode*" in order to have all services displayed in the MBean Browser. The returned MBeans correspond to the corresponding services.
All services have a "start" and "stop" method. Select the entry "telnet" from the tree structure. Then select the method "stop". Click OK to generate an AE job that stops the Telnet service:
The modification is immediately visible in the Visual Administrator:
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |