Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table 3-1 Category Details table

HeaderDescription
Status

Indicates the highest severity error (if any) encountered by one of the category’s components, as follows:

Image Modified Red. Indicates that at least one of the category’s components encountered a high severity error.

Image Modified Orange. Indicates that at least one of the category’s components encountered a medium severity error.

Image Modified Yellow. Indicates that at least one of the category’s components encountered a low severity error.

Image Modified Green. Indicates that none of the category’s components encountered errors.

Image Modified Indicates components configured to experience downtime in the defined time frame. Errors for this component are ignored.

Image Modified Indicates problematic components that have been acknowledged and are currently being handled. These components, and the errors resulting from them, are excluded from their category’s total and are grouped together in this category. For more information, see Defining problematic components as acknowledged.

Category

Indicates a group per technology, such as:

  • Agents
  • FocalPoints
  • Warehouse processes
  • License Limitation Metrics
  • Licenses
  • Action items
Total componentsIndicates the total number of components in the selected category.
Errors

The color-coded stacked bar indicates the number of underlying components that have an error. Only red (high) and orange (medium) severity errors are shown.

Click on the icon on the header to switch between the following display methods:

  1. Show relative-sized colored toolbar according to the number of components that have problems.
  2. Show full-sized colored toolbar.
  3. Show the number of components that have problems.

About the Main area in the Dashboard tab

...

Table 3-2 FocalPoints or Agents table headings

HeaderDescription
Status

Indicates the highest severity error (if any) encountered by the component, as follows:

Image Modified Red. Indicates that the component encountered a high severity error.

Image Modified Orange. Indicates that the component encountered a medium severity error.

Image Modified Yellow. Indicates that the component encountered a low severity error.

Image Modified Green. Indicates that no component encountered errors.

Image Modified Indicates components configured to experience downtime in the defined time frame. Errors for this component are ignored.

Node

Name of the node.

ServerName of the server on which the FocalPoint or Agent is running.
AgentName of the FocalPoint or Agent.
DescriptionA short description of the current status for the selected FocalPoint or Agent.
CriticalityDisplays the related instance(s) criticality setting.

 

About the Events table

The Events table lists all the Precise events for the selected FocalPoint or Agent. Each row corresponds to an event. You can control the way data is displayed in the table. See “About sorting data” on page 184.

...

Table 3-3 Events table headings

HeaderDescription
Level

Indicates severity:

  • Red stop sign indicates that a critical alarm has been raised.
  • Yellow warning sign indicates a near-critical alarm has been raised.
DateDisplays the date and time the event occurred.
MessageA short description of the current status.
IDThe ID (identification number) for the specific event.

 

About the Warehouse processes category related table

...

Table 3-4 Warehouse processes table headings

HeaderDescription
Status

Indicates the highest severity error (if any) encountered by the component, as follows:

Image Modified Red. Indicates that the component encountered a high severity error.

Image Modified Orange. Indicates that the component encountered a medium severity error.

Image Modified Yellow. Indicates that the component encountered a low severity error.

Image Modified Green. Indicates that no component encountered errors.

Image Modified Indicates components configured to experience downtime in the defined time frame. Errors for this component are ignored.

Node

Name of the node.

InstanceName of the instance.
ServerName of the server on which the instance is installed.
ProductName of the product.
ProcessName of the process.
Last RunThe date of the last run for this process.
CriticalityDisplays the related instance(s) criticality setting.

 

About the Licenses category related table

...

Table 3-5 Licenses table headings

HeaderDescription
StatusIndicates the licenses installed and the status for each.
ServerName of the server on which the FocalPoint or Agent is running.
AgentName of the FocalPoint or Agent.
FeatureA description of the license feature.
Licensing Status

One of the following statuses:

  • Not Licensed. The feature is installed, but the current license file does not include a product key for the feature.
  • Licensed. The feature has a license.
  • Expired. The feature was licensed, but its license has expired. This status usually appears when a feature is included in a trial license with an expiration date.
  • License Expires in <x> Days. The feature has a license, but the license will expire soon. This status appears when the expiration date occurs within the next 14 days.
Expiration DateExpiration date for the currently installed license for a feature.

To use the Precise product suite, you need the appropriate license file. All product keys are saved in a single license file managed by Precise FocalPoint. The Precise license file contains information about the product features that you are licensed to use. It also contains data about your information system environment, including CPU, model, server name, or IP addresses of the servers where the products run.

...

Table 3-6 License Limitation Metrics

LabelDescription
statusIndicates the License Limitation Metrics status for the installed technology/CPUs.
TechnologyTechnology to which the License Limitation Metrics applies.
Amount InstalledThe number of instances of the relevant technology/CPUs that are installed.
Amount of Applied LicensesThe limitation of the number of instances of the relevant technology/CPUs.

 

About the Action Items category related table

...

Table 3-7 Action Items table headings

HeaderDescription
IconThe icons display the criticality of the Action Item related instance, whether high, medium, or low.
StatusIndicates the status of an Action Item.
IDThe Action Item ID number.
Node

Name of the node.

InstanceName of the instance.
ServerName of the server on which the FocalPoint or Agent is running.
Originthe origin of an Action Item.
StatusIndicates the status of an action item, whether done, failed, pending, blocking, or executable.
Update timeThe date of the last run for this process.
CriticalityDisplays the criticality of the Action Item related instance, whether high, medium, or low.

 

Anchor
Agents
Agents
About the Agents tab

...

The current status of an agent can be any of the following statuses:

IconDescription
Image Modified
The agent is starting up.
Image Modified
The agent is running.
Image Modified
The agent is stopped.
Image Modified
The agent is running but has encountered a problem. See the agent log files for details, verify the agent (using the Verify button), or contact Precise Technical Support.
Image Modified

The agent is in failed status. This occurs in case the agent has problems. For example, in case it has crashed at least three times in an hour. See the agent log files for details, verify the agent (using the Verify button), or contact Precise Technical Support.

Info

Once the agent is in failed status it keeps returning this status even if the original problem is fixed. To recover the agent from this status, fix the original problem, then start the agent using AdminPoint>Agents tab.


Image Modified
Precise FocalPoint cannot retrieve the current agent status. See the Precise FocalPoint logs and the agent log files for details. See Viewing a log file from the Agents tab.

You can control the way data is displayed in the table. See “About sorting data” on page 184.

...

Table 3-8 Selecting agents

SelectAction
An individual agentClick a specific row in the table.
An arbitrary set of agentsClick the first agent row, hold down the <Ctrl> key, and then click all other required agent rows.
A consecutive group of agentsClick the first agent row, hold down the <Shift> key, and then click the last agent row.

 

Anchor
ManagingAgents
ManagingAgents
Managing agents

...

Table 3-9 Additional columns

TechnologyColumn nameDescription
OracleDatabase IDThe ID of the database.
WebWeb server typeThe type of the Web server.
WebServer-side installed indicationAn indication if the server-side is installed.
WebClient-side installed indicationAn indication if the client-side is installed.
J2EEJ2EE typeThe J2EE type.

You can control the way data is displayed in the table. See “About sorting data” on page 184.

...

Table 3-10 Display Instances & Clusters buttons

EntityButtonDescription
InstanceAdd InstanceAdd a new instance. For more information about the installation, see the Precise Installation guide.
InstanceEdit

Edit the selected instance. If the instance is part of a cluster, the edit button is disabled and editing is done by selecting the cluster and clicking Edit. For more information about the installation, see the Precise Installation Guide.

InstanceDelete

Delete the selected instance from the Display Instances & Clusters table and invoke the uninstall process for the instance. For more information about the installation, see the Precise Installation Guide.

InstanceSet AppTierAssign the instance to an AppTier. See Setting AppTiers.
InstanceCustomize Columns

Customize the columns for one or more instances. See Customizing column headers and their values for instances.

ClusterAdd Cluster

Add a new cluster. This can only be performed for J2EE, Web, and Oracle. For more information about adding a new cluster, see the Precise Installation Guide.

ClusterEdit

For J2EE and Web , this button opens the Add Servers window within the cluster installation. For Oracle , this button opens the Add New Oracle Cluster window.

ClusterAdvanced Edit

This button opens the Instance Properties window in the Install Web Cluster process from within you can click Advanced to change the properties. This button is only enabled for Web technology.

ClusterSet AppTierAssign the cluster to an AppTier. See Setting AppTiers.

 

Anchor
SettingAppTiers
SettingAppTiers
Setting AppTiers

...

  1. In AdminPoint, select Setup>Updates.
  2. In the screen that appears, select one of the following display modes from the drop-down menu(s) above the table.
    • Server Status. This mode displays all servers that the update selected in the “For” drop-down menu should be applied to, and the current application status. The Server Status table displays the following information:

      HeaderDescription
      Update IDName of the update.
      ServerName of the server.
      StatusAn icon that indicates whether the update was applied successfully or with errors.
      Application Type
      Indicates how the update was applied to the server. The application types include:
      • Applied (Directly). The update was applied directly on the selected server.
      • Applied (Upon Installation). The update was automatically applied on the server when the server was installed.
      • Applied (Indirectly). The changes and functionalities provided by the update were applied on the selected server when a newer update containing these functionalities was applied to it.
      • Update Required. The update should be applied on the selected server.
      • Update Required (Priority). The updated must be applied on the selected server before it is applied on other servers in the same framework.
        A FocalPoint is installed on the selected server. Within each node, the servers with FocalPoints installed on them must be updated before the other servers. Therefore, the update must be applied on the selected (FocalPoint) server before it is applied on other servers in the same node.

        Info

        Because there can be multiple nodes in a Precise installation, there can be multiple servers with this status. This status only refers to servers in the same node. You can update a server (without a FocalPoint) in a different node before updating the selected server, if the servers with FocalPoints installed on them in the other node have already been updated.


      • Pending Prerequisites. The update cannot be applied until all prerequisites are fulfilled. A list of prerequisites can be found per update on https://precise.secure.force.com.
      • Pending Server-Update Version Upgrade. The server version is not supported by the update. The server version must be upgraded before the update can be applied.
      Applied OnThe date and time that the update was applied on the server.
      NodeName of Framework node that the selected server is part of.
      Installed AgentsList of all agents that are currently installed on the server.


    • Update Status. This mode displays all updates currently loaded and their status for all relevant servers. The table displays the following information:

      HeaderDescription
      Update IDName of the update.
      ServerName of the server.
      StatusAn icon that indicates whether the update was applied successfully (insert icon) or with errors (insert icon).
      Application Types

      Indicates how the update was applied to the server. The application types include:

      • Applied (Directly). The update was applied directly on the selected server.
      • Applied (Upon Installation). The update was automatically applied on the server when the server was installed.
      • Applied (Indirectly). The changes and functionalities provided by the update were applied on the selected server when a newer update containing these functionalities was applied to it.
      • Update Required. The update should be applied on the selected server.
      • Update Required (Priority). The updated must be applied on the selected server before it is applied on other servers in the same framework.
      • A FocalPoint is installed on the selected server. Within each node, the servers with FocalPoints installed on them must be updated before the other servers. Therefore, the update must be applied on the selected (FocalPoint) server before it is applied on other servers in the same node.

        Info

        Because there can be multiple nodes in a Precise installation, there can be multiple servers with this status. This status only refers to servers in the same node. You can update a server (without a FocalPoint) in a different node before updating the selected server, if the servers with FocalPoints installed on them in the other node have already been updated.


      • Pending Prerequisites. The update cannot be applied until all prerequisites are fulfilled. A list of prerequisites can be found per update at https://precise.secure.force.com.
      • Pending Server-Update Version Upgrade. The server version is not supported by the update. The server version must be upgraded before the update can be applied.
      Applied OnThe date and time that the update was applied on the server.
      NodeName of framework node that the selected server is part of.
      ProductName of the Precise components that are affected by the update.


You can control the way data is displayed in the table. See “About sorting data” and "About filtering data" on page 184.

...

Using the Status combo at the top of the view you can select to view only pending action items, failed action items, or completed action items:

HeaderDescription
ID

The action items resource identification number; this ID number may be used more than once. For example, there may be several messages with the same Action ID for different instances.

ServerThe name of the server where the action item was produced.
TechnologyThe technology type of the monitored instance. Exists only for action items which have a value in the instance column.
InstanceName of the specific instance that is being monitored (if relevant).
Action ItemThe title of the action item. After clicking an action item, the action item's full text is displayed lower on the screen. You can also view the action item's full text in the tooltip of this column.
OrderThe order of Precise installation action items should be performed as specified - in ascending order. The specified order is necessary because of dependencies between action items.
StatusThis is an icon which indicates the status of Precise installation action items. The action item status can be one of the following: completed, failed, or pending. In the case of a failed status, the tooltip describes the reason for failure.
BlockingThe icon indicates whether the start of the related agent is being blocked, until the action item has completed.
OriginThis the source of the action item. The source can be any of the following: install, uninstall, update, or verification.
Executable

A check mark indicates the action item is executable. An executable action item can be handled automatically by selecting the action items and clicking Execute. To execute the action item, additional user input (such as: user and password) may be required.

NodeName of Framework node.
Update TimeDate and time when the action items were produced or last updated due to failure, execution or marked as done.
Required FieldsThis column displays the name of fields requiring user input before automatic execution of the action item.

 

About icons for action items

The legend for the action items table is:

IconDescription
Image Modified
The action item was completed successfully.
Image Modified
Invocation of the action item failed. See this icon’s tooltip for the failure reason.
Image Modified
The action item was not yet performed.
Image Modified
The action item's related agent cannot be started until the action item is performed.
Image Modified
The action item can be automatically executed by Precise. Click execute to instruct Precise to execute it for you.

  

Displaying Dependencies on/off

...

Table 3-11 Display Applications table displayed columns

Column nameDescription
ApplicationName of the application. In the Agents table, AdminPoint displays all of the applications that an instance belongs to, according to the AppTiers it is part of.
NodeName of the node.
AppTiersName of the AppTiers.
TechnologiesName of the technologies within the application.
SmartLink ApplicationIf available, the name of the SmartLink application.
ProductSee Customizing custom columns in the environment.
TypeSee Customizing custom columns in the environment.
LocationSee Customizing custom columns in the environment.
TagSee Customizing custom columns in the environment.
CommentSee Customizing custom columns in the environment.

 

Managing applications

Using the applications command buttons, you can perform the following actions on one or more applications in the Display applications table:

...

Through the Warehouse tab, you can view and manage PMDB statuses and processes. See “About the PMDB” on page 68.

 

Precise. Performance intelligence from click to storage. Learn more > >

...


IDERA Website | Products | Buy | Support | Community | About Us | Resources | Legal