<%@ include file="/sdk/oemTop.jspf" %> <%@ include file="/oemNoscript.jspf" %> <%@ taglib uri="http://xmlns.oracle.com/uix/ui" prefix="uix" %> <%@ taglib uri="http://xmlns.oracle.com/oem/jsp/tag" prefix="oem" %> <%@ page import="oracle.cabo.ui.UIConstants" %> <%@ page import="oracle.sysman.dbTarget.db.bsln.model.BSLNConstants" %> <%@ page import="oracle.sysman.dbTarget.db.bsln.ctlr.BaselineConstants" %> <%-- JavaBean references --%> <%-- JavaScript functions --%> <%@ include file="/enablePPR.jspf" %> <%@ include file="/oemTitle.jspf" %> <%@ include file="/database/global.jspf" %> <% boolean preferred = BSLNConstants.STATUS_PREFERRED.equals(pageBean.getThreshold().getSetting().getMetric().getStatus()); %> <%-- == Warning message that statistics are required for this == page. --%> <%-- == Last updated date --%> <%-- == Non-preferred metric message area. --%> <%-- == The editThresholds form is the form submitted to make a change to the == threshold settings. It has a different action than the one that loaded == this page. --%> <%-- == Critical threshold parameter --%> <%-- == Warning threshold parameter --%> <%-- == Occurrences threshold parameter --%> <%-- == The updateDisplay form is submitted via the Update Display button. == It does nothing more than transfer the editThresholds form values for == a refresh, but we use a different form for apply/clear settings events == because they are for different actions. --%> <%@ include file="metricCalendar.jspf" %>