Page History
...
Table 3-1 Category Details table
Header | Description |
---|---|
Status | Indicates the highest severity error (if any) encountered by one of the category’s components, as follows: Red. Indicates that at least one of the category’s components encountered a high severity error. Orange. Indicates that at least one of the category’s components encountered a medium severity error. Yellow. Indicates that at least one of the category’s components encountered a low severity error. Green. Indicates that none of the category’s components encountered errors. Indicates components configured to experience downtime in the defined time frame. Errors for this component are ignored. 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:
|
Total components | Indicates 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:
|
About the Main area in the Dashboard tab
...
Table 3-2 FocalPoints or Agents table headings
Header | Description |
---|---|
Status | Indicates the highest severity error (if any) encountered by the component, as follows: Red. Indicates that the component encountered a high severity error. Orange. Indicates that the component encountered a medium severity error. Yellow. Indicates that the component encountered a low severity error. Green. Indicates that no component encountered errors. Indicates components configured to experience downtime in the defined time frame. Errors for this component are ignored. |
Node | Name of the node. |
Server | Name of the server on which the FocalPoint or Agent is running. |
Agent | Name of the FocalPoint or Agent. |
Description | A short description of the current status for the selected FocalPoint or Agent. |
Criticality | Displays 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
Header | Description |
---|---|
Level | Indicates severity:
|
Date | Displays the date and time the event occurred. |
Message | A short description of the current status. |
ID | The ID (identification number) for the specific event. |
About the Warehouse processes category related table
...
Table 3-4 Warehouse processes table headings
Header | Description |
---|---|
Status | Indicates the highest severity error (if any) encountered by the component, as follows: Red. Indicates that the component encountered a high severity error. Orange. Indicates that the component encountered a medium severity error. Yellow. Indicates that the component encountered a low severity error. Green. Indicates that no component encountered errors. Indicates components configured to experience downtime in the defined time frame. Errors for this component are ignored. |
Node | Name of the node. |
Instance | Name of the instance. |
Server | Name of the server on which the instance is installed. |
Product | Name of the product. |
Process | Name of the process. |
Last Run | The date of the last run for this process. |
Criticality | Displays the related instance(s) criticality setting. |
About the Licenses category related table
...
Table 3-5 Licenses table headings
Header | Description |
---|---|
Status | Indicates the licenses installed and the status for each. |
Server | Name of the server on which the FocalPoint or Agent is running. |
Agent | Name of the FocalPoint or Agent. |
Feature | A description of the license feature. |
Licensing Status | One of the following statuses:
|
Expiration Date | Expiration 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
Label | Description |
---|---|
status | Indicates the License Limitation Metrics status for the installed technology/CPUs. |
Technology | Technology to which the License Limitation Metrics applies. |
Amount Installed | The number of instances of the relevant technology/CPUs that are installed. |
Amount of Applied Licenses | The 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
Header | Description |
---|---|
Icon | The icons display the criticality of the Action Item related instance, whether high, medium, or low. |
Status | Indicates the status of an Action Item. |
ID | The Action Item ID number. |
Node | Name of the node. |
Instance | Name of the instance. |
Server | Name of the server on which the FocalPoint or Agent is running. |
Origin | the origin of an Action Item. |
Status | Indicates the status of an action item, whether done, failed, pending, blocking, or executable. |
Update time | The date of the last run for this process. |
Criticality | Displays the criticality of the Action Item related instance, whether high, medium, or low. |
Anchor | ||||
---|---|---|---|---|
|
...
The current status of an agent can be any of the following statuses:
Icon | Description | ||
---|---|---|---|
The agent is starting up. | |||
The agent is running. | |||
The agent is stopped. | |||
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. | |||
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.
| |||
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
Select | Action |
---|---|
An individual agent | Click a specific row in the table. |
An arbitrary set of agents | Click the first agent row, hold down the <Ctrl> key, and then click all other required agent rows. |
A consecutive group of agents | Click the first agent row, hold down the <Shift> key, and then click the last agent row. |
Anchor | ||||
---|---|---|---|---|
|
...
Table 3-9 Additional columns
Technology | Column name | Description |
---|---|---|
Oracle | Database ID | The ID of the database. |
Web | Web server type | The type of the Web server. |
Web | Server-side installed indication | An indication if the server-side is installed. |
Web | Client-side installed indication | An indication if the client-side is installed. |
J2EE | J2EE type | The 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
Entity | Button | Description |
---|---|---|
Instance | Add Instance | Add a new instance. For more information about the installation, see the Precise Installation guide. |
Instance | Edit | 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. |
Instance | Delete | 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. |
Instance | Set AppTier | Assign the instance to an AppTier. See Setting AppTiers. |
Instance | Customize Columns | Customize the columns for one or more instances. See Customizing column headers and their values for instances. |
Cluster | Add 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. |
Cluster | Edit | 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. |
Cluster | Advanced 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. |
Cluster | Set AppTier | Assign the cluster to an AppTier. See Setting AppTiers. |
Anchor | ||||
---|---|---|---|---|
|
...
- In AdminPoint, select Setup>Updates.
- 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:
Header Description Update ID Name of the update. Server Name of the server. Status An 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 On The date and time that the update was applied on the server. Node Name of Framework node that the selected server is part of. Installed Agents List 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:
Header Description Update ID Name of the update. Server Name of the server. Status An 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 On The date and time that the update was applied on the server. Node Name of framework node that the selected server is part of. Product Name 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:
Header | Description |
---|---|
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. |
Server | The name of the server where the action item was produced. |
Technology | The technology type of the monitored instance. Exists only for action items which have a value in the instance column. |
Instance | Name of the specific instance that is being monitored (if relevant). |
Action Item | The 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. |
Order | The 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. |
Status | This 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. |
Blocking | The icon indicates whether the start of the related agent is being blocked, until the action item has completed. |
Origin | This 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. |
Node | Name of Framework node. |
Update Time | Date and time when the action items were produced or last updated due to failure, execution or marked as done. |
Required Fields | This 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:
Icon | Description |
---|---|
The action item was completed successfully. | |
Invocation of the action item failed. See this icon’s tooltip for the failure reason. | |
The action item was not yet performed. | |
The action item's related agent cannot be started until the action item is performed. | |
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 name | Description |
---|---|
Application | Name 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. |
Node | Name of the node. |
AppTiers | Name of the AppTiers. |
Technologies | Name of the technologies within the application. |
SmartLink Application | If available, the name of the SmartLink application. |
Product | See Customizing custom columns in the environment. |
Type | See Customizing custom columns in the environment. |
Location | See Customizing custom columns in the environment. |
Tag | See Customizing custom columns in the environment. |
Comment | See 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