HP Matrix Operating Environment Software manual See also system

Page 73

server

1.

Physical server:

 

 

Hardware that can run one or more operating systems, including a partitionable complex.

 

 

Also, hardware that can run an instance of the vPars monitor. Server hardware includes one

 

 

or more cabinets containing all the available processing cores, memory, I/O, and power

 

 

and cooling components. HP Integrity servers include two types of server hardware:

 

 

standalone servers and cell-based servers.

 

2.

Virtual server:

 

 

A software-based virtual environment that can run an operating system. A virtual server

 

 

includes a subset of the server hardware resources, including cores, memory, and I/O.

 

 

Virtual servers may be virtual partitions under vPars or virtual machines under Integrity VM

 

 

.

 

3.

Systems Insight Manager uses the term “server” for any standalone server, nPartition, or

 

 

virtual server that is running an instance of an operating system or an instance of the vPars

 

 

monitor.

 

See also system.

Serviceguard

A monitored workload associated with a Serviceguard cluster and a particular Serviceguard

workload

package within the cluster. The workload (and the utilization data reported) follows the package

 

it is associated with as it moves between the nodes of the cluster.

SSL

Secure Sockets Layer. Protocol for validating identity and for creating an encrypted connection

 

between a server and a Web browser.

system

1.

A server, nPartition, virtual partition, or virtual machine that is running an instance of an

 

 

operating system.

 

2.

Entities on the network that communicate through TCP/IP or IPX. To manage a system, some

 

 

type of management protocol (for example, SNMP, DMI, or WBEM) must be present on the

 

 

system. Examples of systems include servers, workstations, desktops, portables, routers,

 

 

switches, hubs, and gateways.

 

See also server.

template

An HP-supplied or user-defined set of rules, properties, or metadata that describe an object in a

 

computing network.

 

In Application Discovery, templates specify the data collection and matching rules to be

 

 

used to define and discover an application.

 

When referring to a logical server, a template is the collection of information that defines

 

 

the logical server and its attributes. A template logical server has no actual resources

 

 

associated with it.

unmatched process

A process that Application Discovery can discover that does not match existing templates or

 

packages that Application Discovery is using for discovery and monitoring. Unmatched processes

 

might include custom and third-party applications.

virtual machine

A software entity provided by HP Integrity Virtual Machines, VMware ESX, or Microsoft Virtual

 

Server. This technology allows a single server or (with Integrity Virtual machines) nPartition to act

 

as a VM Host for multiple individual virtual machines, each running its own instance of an

 

operating system (referred to as a guest OS). Virtual machines are managed systems in HP Matrix

 

Operating Environment.

virtual partition

A software partition of a server, or of a single nPartition, where each virtual partition can run its

 

own instance of an operating system. A virtual partition cannot span an nPartition boundary.

 

See also nPartition, virtual machine.

visibility

Application Discovery makes it possible for you to control the amount of data appearing on user

 

interface screens by letting you determine what applications, packages, or hosts will be visible

 

in the user interface or not. Currently, visibility settings are global in nature, which means they

 

apply to all screens in Application Discovery and are not specific to a particular user or job role.

VM Host

A server running software such as HP Integrity Virtual Machines, VMware ESX, or Microsoft

 

Virtual Server, that provides multiple virtual machines, each running its own instance of an

 

operating system.

73

Image 73
Contents Application Discovery 7.2 User Guide Page Contents Support and other resources TroubleshootingConfiguring the Wbem provider password Glossary Index Error messages Completing certificate exchangeDocumentation feedback Key to event attributesPage Introduction Features of Application DiscoveryIntroduction Application Discovery components Components and conceptsHow discovery works Refining Application DiscoveryUnderstand your current discovery state Discovery ratioRefine discovery by checking agent state Understanding application templatesRefine discovery by creating application templates Warm-up ratioUnderstanding server resource consumption How memory usage is calculatedUsed mem Page Using System Insight Manager to start the agent Procedures and examplesStarting the agent from the command line Starting Application DiscoveryUsing System Insight Manager to stop the AD agent Reconfigure a running agent from the command lineStopping the agent from the command line Checking agent stateWorking with data views Adjusting the user interfaceExplanation of agent states Set screen data refresh intervalSet color theme Change the data viewSet number of table rows Sort data in view tablesOther controls available from right-clicking on a view table Filter data in view tablesSet visibility for hosts on Application Discovery screens Navigate between viewsSet visibility for matched applications Set visibility for packages on Application Discovery screens Modifying the maximum size of an event listSetting data polling interval Setting event attributesIntroduction to event settings in Application Discovery Setting alert location Setting event severityManaging application templates Find an application templateChange 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 Aggregation rule fields and their descriptions Create an application template ruleCreate a process aggregation rule Managing application templates Procedures and examples Managing application templates Check unmatched processes to find application candidates How to remove types from the aggregation ruleUnderstanding the tables that show unmatched processes Filling in the aggregation rule fields using table data Filling in the system scope 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 Subscription service How to contact HPSupport and other resources Information to collect before contacting HPRelated information HP authorized resellersDocuments ResourcesComputer 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 attributesAdditional event types specific to Application Discovery Event severity typesEvent viewing locations Error messages seen when trying to log Error messagesPage Completing certificate exchange Completing certificate exchange from the command lineIntroduction 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.