OSver

Field	Description
OSver	Operating system version to which the template applies. If this field is left blank,
	Application Discovery tries to match the template against all operating system versions
	for which it has information.
Architecture	Architecture to which the template applies. If this field is left blank, Application
	Discovery tries to match the template against all architectures for which it has
	information.

NOTE:

If you want to define a template based on where the processes that you want to collect into an application are running, you can check the “Unmatched processes” table on a particular host screen or the “Processes not matched by this template” table on a template editing screen to get this information. See Filling in the System Scope fields using table data for tips on finding specific process attributes for this purpose.

Separation rule fields and their descriptions

Field Description

Is visible? By default during initial discovery, Application Discovery sets objects recognized as packages to 'no' and objects recognized as templates to 'yes'.

This field designates whether or not the application shall be visible to users of the Application Discovery user interface:

•yes – show the application data associated with this object.

•no – hide the application data associated with this object.

NOTE: Visibility actually has no affect on template matching, but is included here as a convenience. It is a global setting that allows you to control data presentation in all Application Discovery screens. It is not stored as a user preference.

Pid scope	How many process identifiers (pids) are allowed in an application:
	• one — one pid per running application.
	Effect: Each new concurrent run of this application is shown as a separate instance from
	the others in Application Discovery.
	• session – any number of pids per application for the duration of one terminal group
	session.
	Effect: All associated pids are treated as one running application instance for that session.
	However, because sessions on HP-UX and Linux are maintained per user, this has the
	effect of delineating running applications per user. Thus, if you log in twice (two concurrent
	terminal windows), you can have two separate instances of this running application. This
	effect is similar to that obtained by setting user scope=one.
	• any – any number of pids per application.
	Effect: Pids have no specific effect on defining the application described by this template.

28 Procedures and examples

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.

HP Matrix Operating Environment Software Separation rule fields and their descriptions, OSver

Models: Matrix Operating Environment Software

Architecture

Separation rule fields and their descriptions

Pid scope

session.

• any – any number of pids per application.

Matrix Operating Environment Software specifications