Page History
...
| Column | Description | ||
|---|---|---|---|
| Node | The specific Precise framework installation.
| ||
| Technology | The name of the technology that the process gathers data for. Processes that maintain the PMDB itself are listed, but the technology column remains empty. | ||
| Process | The process name is a logical name that describes the process function. For example, “Calculate Baselines.” Two types of processes gather PMDB data. One process type includes processes that are part of the PMDB FocalPoint and run on the PMDB server, such as the Summarize Data process. The other process type includes processes that are part of another product, such as the Schema Changes process in a Microsoft SQL Server instance that Precise for SQL Server monitors. These processes run on the product’s server and on the PMDB FocalPoint, which is in charge of scheduling them. See “Batch Batch processes in Precise” on page 75Precise. | ||
| Product | The name of the product the process runs for. | ||
| Last Run | The last time the process that is named in this row ran. | ||
| Next Scheduled Run | Time when the process that is named in this row is scheduled to run again. | ||
| Status | An icon indicating the current status of the process that is named in this row. |
...
You can manually configure these parameters according to the requirements of your environment. You can edit the default values or override them by defining instance-specific values. If a process does not include any configurable parameters, the Parameters button is disabled. See “About About configurable process parameters” on page 87parameters.
The following table lists all the processes that you can configure per monitored instance.
...
- In the Main area table, select the process whose parameters you want to configure.
- Click Parameters.
In the Parameters dialog box, perform one of the following actions:
To edit the default values for the selected technology Click Edit Default Values.
In the Default Values dialog box, specify the values and click OK.
Unless instance-specific values override these values, they apply to all monitored instances.
To edit the values for a specific instance Select an instance in the table. Click Edit.
In the Edit Instance dialog box, clear the Use Defaults check box. Specify the values to be used for this instance.
Click OK.
In the Parameters dialog box, click OK.
Info After you change the default of the Minimum In Oracle time to load parameter in the Load Data process, you must stop and then restart the Precise for Oracle FocalPoint. The next step is to restart the Collector agents.
Info Changing the “Load Data” value from “300” to “30” for Precise for J2EE can take up to ten minutes to take effect.
Info You can also configure the Precise for Web URL mapping rule for a domain in a system: “Treat "Treat pages with different titles as different pages”pages." Select to view the URL along with the various titles that belong to it. The collected data includes page URLs and page titles. When cleared, you can only differentiate between different URLs, not between page titles. In this case, the collected data includes the page URL and the first page title for any URL in the system.
...
- Select a process in the Main area table and click Scheduling.
- In the Scheduling dialog box, perform any of the following tasks:
- Clear the Run this process in the PMDB check box to disable the process. This action removes the process from the PMDB Scheduler, but you can still run the process manually. See Manually running a process.
- Change the time that the process is scheduled to run. Each process runs at a predefined interval by default: Every 15 minutes (slice), hourly, daily, or weekly. You cannot change this interval, but you can set the exact time that the process runs, for example every 2 hours, 15 minutes after the hour.
- Schedule the process per instance (only available for some processes). This mechanism lets you perform the following tasks:
- Disable a process for a specific instance by clearing the relevant check box in the first table column.
- Set the interval of an instance within the process. For example, if you set the Run Every... column to 2, the instance executes every 2 minutes (or other) run of the process.
- Click OK.
| Anchor | ||||
|---|---|---|---|---|
|
The following sections provide a description of all existing Precise batch processes. The following table lists all batch processes on the Warehouse workstation.
...
Most process are specific to one technology. The “Load Data” Load Data process that does not have a Technology value is shared by SmartLink and J2EE. All changes to this value affect the slice size not only in SmartLink tabs, but also in all J2EE instances in that environment.
...
- Go to AdminPoint>Warehouse>Processes.
- From the table, select the “Load Data” Load Data process with an empty Technology value. Click Parameters.
- Select the relevant environment and click Edit.
- Mark the “Use Defaults” Use Defaults check box to enable editing.
- From the drop-down menu, select the desired slice size.
Click OK>OK.
Info Changing the “Load Data” Load Data value from “300” to “30” may take up to ten 10 minutes to take affect in Precise for J2EE.
...
- Select an instance in the Main area table and click Processes.
- In the PMDB Processes dialog box, the top table lists all processes involved in loading information for this instance. Select the process you want to focus on, such as a process that failed during its last run (indicated by the status icon).
The last run of this process affects the bottom table populated with detailed information on the PMDB tables. If an error occurred, focus on the details in the Error Message column. - Investigate all relevant data. Then click Close.
...