HP UX Matrix Operating EnvIronment manual Separation rule fields and their descriptions, Session

Page 31

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.

User scope

How many users' processes can be associated with one instance of this application:

 

one – one user's processes per application.

 

Effect: A separate instance of this application will be shown for each different user who

 

runs this application. This effect is similar to that obtained by setting pid

 

scope=session.

 

any – any number of different users per application.

 

Effect: Number of users has no specific limiting effect on defining the application

 

described by this template. That is, only one instance is recognized, regardless of how

 

many users are running the application concurrently.

is pidtree

Shall child processes spawned by the parent be considered part of the parent application

 

instance or as a separate instance:

 

no – child processes are not considered part of the parent application instance. This is

 

the default value.

 

Effect: Child processes will be shown as separate application instances in Application

 

Discovery.

 

yes – child processes are considered part of the parent application instance.

 

Effect: Child processes will not be shown as separate application instances in Application

 

Discovery.

NOTE:

If you want to define a template based on ownership or how many instances are currently 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 template separation rule fields for tips on finding specific process attributes.

Managing application templates 31

Image 31
Contents Application Discovery 6.2 User Guide For managed nodes Table of Contents Support and other resources Configuring the Wbem provider password Glossary Index List of Figures Application visibility selector Sort indicatorPossible values for agent state List of TablesPage Introduction Features of Application DiscoveryPage Application Discovery components Components and conceptsDiscovery ratio Refining Application DiscoveryHow discovery works Understand your current discovery stateWarm-up ratio Refine discovery by checking agent stateHow memory usage is calculated Understanding application templatesRefine discovery by creating application templates Key to the graphic is as follows Understanding server resource consumptionPage Starting Application Discovery Procedures and examplesUsing HP SIM to start the agent Starting the agent from the command lineChecking agent state Reconfigure a running agent from the command lineUsing HP SIM 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 statesSet color theme Set general visibilitySet number of table rows Sort data in view tables Change the data viewFilter data in view tables Navigate between views Other controls available from right-clicking on a view tableSet visibility for matched applications Set visibility for hosts on Application Discovery screensModifying the maximum size of an event list Setting event attributesSetting data polling interval Introduction to event settings in Application DiscoverySetting alert location Setting event severityFind an application template Managing application templatesChange application template values Create a new template Key to application template values Constructing regular expressions Application identity Session Separation rule fields and their descriptionsAggregation rule fields and their descriptions Create an application template ruleCreate a process aggregation rule Managing application templates Example of a nested template aggregation rule 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 Prerequisites Create an application workload in Virtualization ManagerCreate Monitored Workload Definition screen reopens Backing up Application Discovery filesPage Errors in installation TroubleshootingApplications not visible in Application Discovery screens Data missing in Application Discovery screensData missing in Application Discovery screens Host not visible in Application Discovery screens Check that SSH is configured correctly on the managed node# cd /.ssh /* rootuserhomedirectory/.ssh Packages not visible in Application Discovery screens Application Discovery may not be correctly configuredCheck that the host is known to Application Discovery Check that the Application Discovery agent is running UI Unable to connect to servermessages Errors in Application Discovery user interface operationJava UI exception message displays To list the AD agent package installed on the machine, then Page Application Discovery resources Support and other resourcesContacting HP Related informationPage Page Options Amgrd= Logtrace InstallationAuthors Agentconfig Check agent state Event types Key to event attributesAdditional event types specific to Application Discovery Event severity typesEvent viewing locations Table C-1 Error messages seen when trying to log Error messagesPage Introduction Using HP SIM to complete certificate exchangeCompleting certificate exchange from the command line Completing certificate exchangeCompleting certificate exchange Credentials Configuring the Wbem provider passwordPage Agent GlossaryManaged SSL Wbem Index Admin/Config tabClear filter menu pick Group option Defining an application template rule AD Agents, 13