HP Matrix Operating Environment Software manual Usr/sbin/biod

Page 27

NOTE:

Application Discovery (AD) interprets executable path strings differently than Global Workload Manager (gWLM).

Application Discovery looks at a process from the perspective of how it is named when it is running. Therefore, to successfully construct an application that Application Discovery recognizes, you must provide attributes (data strings) that describe the running process.

Also, when defining an application, keep in mind that Application Discovery looks across your entire network for likely matches, and not just on one particular managed node.

It might help to think of the difference between AD and gWLM this way:

•In AD, an executable and arg[0] are compared directly to one another to make a match.

•In gWLM, the inode of an executable and the inode of arg[0] are compared to one another to make a match.

The following examples demonstrate the different results that you can expect when using the same executable and arguments in Application Discovery as compared to Global Workload Manager (gWLM).

Table 3 An example comparison of match behavior in AD and gWLM for same executable path and arguments

Example inputs

AD

gWLM

Executable

Process arg[0]

 

 

 

/usr/sbin/biod

match

match

/usr/sbin/biod

biod

no match

match

 

./biod

no match

match

 

/usr/sbin/biod

match

not allowed

biod

biod

match

not allowed

 

./biod

match

not allowed

Application identity and system scope fields and their descriptions

Field

Description

Application identity

 

Name

Required. Unique name given to the template to represent the application.

Version

Required. Version number of the application this template matches.

Title

User-defined name for the template.

Description

User-defined summary describing the template.

System scope

 

OS

Operating system to which the template applies. If this field is left blank, Application

 

Discovery tries to match the template within all operating systems for which it has

 

information.

Managing application templates 27

Page 26 Page 28
Image 27
Page 26 Page 28
Contents Application Discovery 7.2 User Guide Page Contents Support and other resources TroubleshootingKey to event attributes Error messages Completing certificate exchangeConfiguring the Wbem provider password Glossary Index Documentation feedbackPage Introduction Features of Application DiscoveryIntroduction Application Discovery components Components and conceptsDiscovery ratio Refining Application DiscoveryHow discovery works Understand your current discovery stateWarm-up ratio Understanding application templatesRefine discovery by checking agent state Refine discovery by creating application templatesUnderstanding server resource consumption How memory usage is calculatedUsed mem Page Starting Application Discovery Procedures and examplesUsing System Insight Manager to start the agent Starting the agent from the command lineChecking agent state Reconfigure a running agent from the command lineUsing System Insight Manager to stop the AD agent Stopping the agent from the command lineSet screen data refresh interval Adjusting the user interfaceWorking with data views Explanation of agent statesSort data in view tables Change the data viewSet color theme Set number of table rowsOther controls available from right-clicking on a view table Filter data in view tablesNavigate between views Set visibility for hosts on Application Discovery screensSet visibility for matched applications Set visibility for packages on Application Discovery screens Modifying the maximum size of an event listSetting event attributes Setting data polling intervalIntroduction to event settings in Application Discovery Find an application template Setting event severitySetting alert location Managing application templatesChange application template values Create a new template Application identity and system scope fields Key to application template valuesUsr/sbin/biod OSver Separation rule fields and their descriptionsUser scope Create an application template rule Aggregation rule fields and their descriptionsCreate a process aggregation rule Managing application templates Procedures and examples Managing application templates How to remove types from the aggregation rule Check unmatched processes to find application candidatesUnderstanding the tables that show unmatched processes Filling in the system scope fields using table data Filling in the aggregation rule fields using table dataFilling in the template separation rule fields Create an application workload in HP Matrix OE visualization Backing up Application Discovery files Page Errors in installation TroubleshootingData missing in Application Discovery screens Applications not visible in Application Discovery screens Host not visible in Application Discovery screens Data missing in Application Discovery screens Packages not visible in Application Discovery screens Page Go to /var/opt/amgr/procmaps UI Unable to connect to servermessages Errors in Application Discovery user interface operationJava UI exception message displays To fix this error, do one of the following On the managed nodes, run the command Information to collect before contacting HP How to contact HPSubscription service Support and other resourcesResources HP authorized resellersRelated information DocumentsComputer output Typographic conventionsPage Documentation feedback Page Page Options AmgrdNodaemon InstallationAuthors Amx -c AgentconfigOpt/amgr/bin/agentconfig Agentconfig file Opt/amgr/bin/amgrd Event types Key to event attributesEvent severity types Additional event types specific to Application DiscoveryEvent viewing locations Error messages seen when trying to log Error messagesPage Completing certificate exchange from the command line Completing certificate exchangeIntroduction Completing certificate exchange Configuring the Wbem provider password Page Application GlossaryOperating system referred to as a guest OS See also system Wbem Index Agentwbemcleanup commandCmdline Path Pid scope Title
Related manuals
Manual 111 pages 21.04 Kb Manual 12 pages 7.25 Kb

Matrix Operating Environment Software specifications

HP Matrix Operating Environment (MOE) is an innovative software platform designed to deliver efficient management and orchestration of IT resources across physical, virtual, and cloud infrastructures. It provides a comprehensive solution for organizations that require a robust and flexible environment to manage their IT operations seamlessly.

One of the main features of HP MOE is its ability to optimize resource utilization by automating the provisioning and management of infrastructure components. This includes the ability to rapidly deploy servers, storage, and networking resources in a manner that meets the dynamic needs of modern businesses. This automation significantly reduces the time and effort required for manual configurations, enabling IT teams to focus on strategic initiatives rather than routine tasks.

The software offers a unified management interface that provides visibility into the entire IT environment. Users can monitor performance metrics, track resource allocation, and manage workflows through a single dashboard. This centralized control not only simplifies operations but also enhances decision-making capabilities by providing real-time insights into system health and performance.

Another critical characteristic of HP MOE is its support for both physical and virtual resources. The platform is designed to seamlessly integrate with existing infrastructure, making it easier for organizations to adopt virtualization and hybrid cloud strategies. Its compatibility with industry-standard hypervisors allows businesses to leverage their current investments while taking advantage of the benefits of virtualization.

HP MOE incorporates advanced technologies such as automation scripts, APIs, and tools for workload balancing. This technological backbone enables organizations to implement elasticity in their environments, allowing them to scale resources up or down based on demand. The software also supports a service-oriented architecture, facilitating integration with other enterprise applications and systems.

Security is a top priority in the design of HP MOE. The software provides robust security features that ensure data integrity and protect against unauthorized access. This includes role-based access controls, encryption, and compliance reporting, all of which contribute to a secure operating environment.

In summary, HP Matrix Operating Environment Software is a powerful solution that addresses the complexities of managing modern IT resources. Its key features include automation, unified management, support for physical and virtual environments, and strong security measures. With its ability to enhance efficiency and streamline operations, HP MOE is an essential tool for organizations looking to stay competitive in an increasingly digital landscape.
Top Page Image Contents