JD Edwards EnterpriseOne Tools 8.98 Performance … … · JD Edwards EnterpriseOne Tools 8.98...

JD Edwards EnterpriseOne Tools 8.98Performance Monitor Guide

September 2008

JD Edwards EnterpriseOne Tools 8.98 Performance Monitor GuideSKU E1_TOOLS898TPF-B 0908

Copyright © 2003–2008, Oracle and/or its affiliates. All rights reserved.

Trademark NoticeOracle is a registered trademark of Oracle Corporation and/or its affiliates. Other namesmay be trademarks of theirrespective owners.

License Restrictions Warranty/Consequential Damages DisclaimerThis software and related documentation are provided under a license agreement containing restrictions on use anddisclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreementor allowed by law, youmay not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute,exhibit, perform, publish or display any part, in any form, or by anymeans. Reverse engineering, disassembly, ordecompilation of this software, unless required by law for interoperability, is prohibited.Subject to patent protection under one or more of the following U.S. patents: 5,781,908; 5,828,376; 5,950,010;5,960,204; 5,987,497; 5,995,972; 5,987,497; and 6,223,345. Other patents pending.

Warranty DisclaimerThe information contained herein is subject to change without notice and is not warranted to be error-free. If you findany errors, please report them to us in writing.

Restricted Rights NoticeIf this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of theU.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS

Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are“commercial computer software” or “commercial technical data” pursuant to the applicable Federal Acquisition Regulationand agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shallbe subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicableby the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer SoftwareLicense (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

Hazardous Applications NoticeThis software is developed for general use in a variety of informationmanagement applications. It is not developedor intended for use in any inherently dangerous applications, including applications whichmay create a riskof personal injury. If you use this software in dangerous applications, then you shall be responsible to take allappropriate fail-safe, backup, redundancy and other measures to ensure the safe use of this software. OracleCorporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerousapplications.

Third Party Content, Products, and Services DisclaimerThis software and documentationmay provide access to or information on content, products and services from thirdparties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kindwith respect to third party content, products and services. Oracle Corporation and its affiliates will not be responsiblefor any loss, costs, or damages incurred due to your access to or use of third party content, products or services.

Contains GNU libgmp library; Copyright © 1991 Free Software Foundation, Inc. This library is free software whichcan bemodified and redistributed under the terms of the GNULibrary General Public License.Includes Adobe® PDFLibrary, Copyright 1993-2001 Adobe Systems, Inc. and DL Interface, Copyright 1999-2008Datalogics Inc. All rights reserved. Adobe® is a trademark of Adobe Systems Incorporated.Portions of this program contain information proprietary toMicrosoft Corporation. Copyright 1985-1999MicrosoftCorporation.Portions of this program contain information proprietary to Tenberry Software, Inc. Copyright 1992-1995 TenberrySoftware, Inc.Portions of this program contain information proprietary to Premia Corporation. Copyright 1993 PremiaCorporation.This product includes code licensed fromRSAData Security. All rights reserved.This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit(http://www.openssl.org/).This product includes cryptographic software written by Eric Young ([email protected]).This product includes software written by TimHudson ([email protected]). All rights reserved.This product includes the Sentry Spelling-Checker Engine, Copyright 1993Wintertree Software Inc. All rightsreserved.

Open Source DisclosureOracle takes no responsibility for its use or distribution of any open source or shareware software or documentationand disclaims any and all liability or damages resulting from use of said software or documentation. The followingopen source software may be used in Oracle’s JD Edwards EnterpriseOne products and the following disclaimersare provided:This product includes software developed by the Apache Software Foundation (http://www.apache.org/). Copyright(c) 1999-2000 The Apache Software Foundation. All rights reserved. THIS SOFTWARE IS PROVIDED “ASIS’’ ANDANYEXPRESSEDOR IMPLIEDWARRANTIES, INCLUDING, BUTNOTLIMITEDTO, THEIMPLIEDWARRANTIESOFMERCHANTABILITYANDFITNESS FORAPARTICULARPURPOSEAREDISCLAIMED. INNOEVENT SHALL THEAPACHE SOFTWAREFOUNDATIONOR ITSCONTRIBUTORSBE LIABLE FORANYDIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, ORCONSEQUENTIALDAMAGES (INCLUDING, BUTNOTLIMITEDTO, PROCUREMENTOF SUBSTITUTEGOODSORSERVICES; LOSSOFUSE, DATA, OR PROFITS; ORBUSINESS INTERRUPTION)HOWEVERCAUSEDANDONANYTHEORYOFLIABILITY,WHETHER INCONTRACT, STRICT LIABILITY, OR TORT(INCLUDINGNEGLIGENCEOROTHERWISE) ARISING INANYWAYOUTOFTHEUSEOFTHISSOFTWARE, EVEN IFADVISEDOFTHE POSSIBILITYOF SUCHDAMAGE.

Contents

General PrefaceAbout This Documentation Preface ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ixJD Edwards EnterpriseOne Application Prerequisites.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ixApplication Fundamentals.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ixDocumentation Updates and Downloading Documentation.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .x

Obtaining Documentation Updates.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . .xDownloading Documentation.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . .x

Additional Resources.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xTypographical Conventions and Visual Cues.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xi

Typographical Conventions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . .xiiVisual Cues.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . .xiiCountry, Region, and Industry Identifiers.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .xiiiCurrency Codes.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .xiv

Comments and Suggestions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xivCommon Fields Used in Implementation Guides.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiv

PrefaceJD Edwards EnterpriseOne Performance Monitor Preface.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xviiJD Edwards EnterpriseOne Performance Monitor Workbench Companion Documentation. . . . . . . . . . . . . . . .xvii

Chapter 1Getting Started with JD Edwards EnterpriseOne Performance Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . .1JD Edwards EnterpriseOne Performance Monitor Overview... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1JD Edwards EnterpriseOne Performance Monitor Implementation.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

JD Edwards EnterpriseOne Performance Monitor Implementation Steps. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . .1

Chapter 2Understanding JD Edwards EnterpriseOne Performance Monitor.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3JD Edwards EnterpriseOne Performance Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3JD Edwards EnterpriseOne Performance Monitor Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

The Monitored System... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . .6The Monitoring System... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . .7

Implementing the Production Monitoring System... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Copyright © 2003–2008, Oracle and/or its affiliates. All rights reserved. v

Contents

JD Edwards EnterpriseOne Performance Monitor Instrumentation.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Understanding PMUs... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . .8Understanding Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . .9

Performance Integration with Third-Party Systems.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9JD Edwards EnterpriseOne Performance Monitor Data.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10Scope of JD Edwards EnterpriseOne Performance Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Chapter 3Setting Up JD Edwards EnterpriseOne Performance Monitor... .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11Configuring JD Edwards EnterpriseOne Performance Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11Enabling the Required Elements on the Monitoring System... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Setting Up JD Edwards EnterpriseOne Performance Monitor Database. . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .11Setting Up the Web Server for the Monitoring System... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .13Configuring JAS.INI file on the Monitoring Server.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .14

Enabling the Required Elements on the Monitored System.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17Setting Up the Database of the Monitored System.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .17Specifying the Monitor URL... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .18Setting Up the Web Server of the Monitored System... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .18Configuring JAS.INI file on the Monitored Server (JD Edwards EnterpriseOne JAS Server). . . . . . . . . . . .18Setting Up the Application Server.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .19Configuring JDE.INI file on the Monitored Server (JD Edwards EnterpriseOne ApplicationServer). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .20

Chapter 4Administering JD Edwards EnterpriseOne Performance Monitor.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23Understanding JD Edwards EnterpriseOne Performance Monitor Administration.. . . . . . . . . . . . . . . . . . . . . . . . . . . .23

JD Edwards EnterpriseOne Performance Monitor Administration.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .23Forms Used for JD Edwards EnterpriseOne Performance Monitor Administration.. . . . . . . . . . . . . . .. . . . . . . .24

Setting Global System Options.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Setting System Definition Defaults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Modifying System Definitions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27Viewing Agent Definitions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28Setting Agent Filter Options... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29Scheduling the Reaper Program.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Chapter 5Monitoring System Performance.... . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . .31

vi Copyright © 2003–2008, Oracle and/or its affiliates. All rights reserved.

Contents

System JD Edwards EnterpriseOne Performance Monitoring.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Monitoring System Performance.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .31Forms Used to Modify System Performance.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .32

Viewing Open PMUs... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Monitoring Individual User Performance.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33Viewing Open PMU Trees.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Chapter 6Analyzing Historical Performance Data..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35Historical Performance Data.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Historical Performance Data.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .35Forms Used to Analyze Historical Performance Data.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .35

Viewing Completed PMUs... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35Entering Search Criteria.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .36Working with Completed PMUs... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .36Completed PMU Status... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .38

Chapter 7Evaluating JD Edwards EnterpriseOne Performance Monitor Meta-Data. . . . . . . . . . . . . . . . . . . . . . .39Understanding JD Edwards EnterpriseOne Performance Monitor Meta-Data Definitions. . . . . . . . . . . . . . . . . . . .39

Forms Used to Evaluate JD Edwards EnterpriseOne Performance Monitor Meta-Data. . . . . . . . . .. . . . . . . .41Revising Metric Definitions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42Revising Event Definitions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43Revising Context Definitions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44Revising PMU Definitions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Appendix APMU Definition Reference..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47PMU 100 C Call Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47PMU 101 Java Call Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48PMU 200 JDB/JDBj DML APIs.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49PMU 201 SQL DML APIs... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50PMU 300 Execute Form... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51PMU 301 Event Rules.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52PMU 302 Fetch Process.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53PMU 303 OK Process.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53PMU 304 Asynch OK Process.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

Copyright © 2003–2008, Oracle and/or its affiliates. All rights reserved. vii

Contents

Appendix BUnderstanding JD Edwards EnterpriseOne Performance Monitor Architecture.. . . . . . . . . . . . . .57JD Edwards EnterpriseOne Performance Monitor Architecture Components.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

JD Edwards EnterpriseOne Application Server.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .57JD Edwards EnterpriseOne JAVA Application Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .58JD Edwards EnterpriseOne Monitoring Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .58Data Flow... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .59

Glossary of JD Edwards EnterpriseOne Terms.... . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . .61

Index ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77

viii Copyright © 2003–2008, Oracle and/or its affiliates. All rights reserved.

About This Documentation Preface

JD Edwards EnterpriseOne implementation guides provide you with the information that you need to implement anduse JD Edwards EnterpriseOne applications from Oracle.

This preface discusses:

• JD Edwards EnterpriseOne application prerequisites.• Application fundamentals.• Documentation updates and downloading documentation.• Additional resources.• Typographical conventions and visual cues.• Comments and suggestions.• Common fields in implementation guides.

Note. Implementation guides document only elements, such as fields and check boxes, that require additionalexplanation. If an element is not documented with the process or task in which it is used, then either it requires noadditional explanation or it is documented with common fields for the section, chapter, implementation guide, orproduct line. Fields that are common to all JD Edwards EnterpriseOne applications are defined in this preface.

JD Edwards EnterpriseOne Application PrerequisitesTo benefit fully from the information that is covered in these books, you should have a basic understanding ofhow to use JD Edwards EnterpriseOne applications.

You might also want to complete at least one introductory training course, if applicable.

You should be familiar with navigating the system and adding, updating, and deleting information by using JDEdwards EnterpriseOne menus, forms, or windows. You should also be comfortable using the World WideWeb and the Microsoft Windows or Windows NT graphical user interface.

These books do not review navigation and other basics. They present the information that you need to use thesystem and implement your JD Edwards EnterpriseOne applications most effectively.

Application FundamentalsEach application implementation guide provides implementation and processing information for your JDEdwards EnterpriseOne applications.

For some applications, additional, essential information describing the setup and design of your systemappears in a companion volume of documentation called the application fundamentals implementation guide.Most product lines have a version of the application fundamentals implementation guide. The preface of eachimplementation guide identifies the application fundamentals implementation guides that are associatedwith that implementation guide.

Copyright © 2003–2008, Oracle and/or its affiliates. All rights reserved. ix

General Preface

The application fundamentals implementation guide consists of important topics that apply to many or all JDEdwards EnterpriseOne applications. Whether you are implementing a single application, some combinationof applications within the product line, or the entire product line, you should be familiar with the contentsof the appropriate application fundamentals implementation guides. They provide the starting points forfundamental implementation tasks.

Documentation Updates and Downloading DocumentationThis section discusses how to:

• Obtain documentation updates.

• Download documentation.

Obtaining Documentation UpdatesYou can find updates and additional documentation for this release, as well as previous releases, on Oracle’sPeopleSoft Customer Connection website. Through the Documentation section of Oracle’s PeopleSoftCustomer Connection, you can download files to add to your Implementation Guides Library. You’ll finda variety of useful and timely materials, including updates to the full line of JD Edwards EnterpriseOnedocumentation that is delivered on your implementation guides CD-ROM.

Important! Before you upgrade, you must check Oracle’s PeopleSoft Customer Connection for updates to theupgrade instructions. Oracle continually posts updates as the upgrade process is refined.

See AlsoOracle’s PeopleSoft Customer Connection, http://www.oracle.com/support/support_peoplesoft.html

Downloading DocumentationIn addition to the complete line of documentation that is delivered on your implementation guide CD-ROM,Oracle makes JD Edwards EnterpriseOne documentation available to you via Oracle’s website. You candownload PDF versions of JD Edwards EnterpriseOne documentation online via the Oracle TechnologyNetwork. Oracle makes these PDF files available online for each major release shortly after the softwareis shipped.

See Oracle Technology Network, http://www.oracle.com/technology/documentation/psftent.html

Additional ResourcesThe following resources are located on Oracle’s PeopleSoft Customer Connection website:

Resource Navigation

Application maintenance information Updates + Fixes

Business process diagrams Support, Documentation, Business Process Maps

x Copyright © 2003–2008, Oracle and/or its affiliates. All rights reserved.

General Preface

Resource Navigation

Interactive Services Repository Support, Documentation, Interactive Services Repository

Hardware and software requirements Implement, Optimize + Upgrade; Implementation Guide;Implementation Documentation and Software; Hardwareand Software Requirements

Installation guides Implement, Optimize + Upgrade; Implementation Guide;Implementation Documentation and Software; InstallationGuides and Notes

Integration information Implement, Optimize + Upgrade; Implementation Guide;Implementation Documentation and Software; Pre-BuiltIntegrations for PeopleSoft Enterprise and JD EdwardsEnterpriseOne Applications

Minimum technical requirements (MTRs) Implement, Optimize + Upgrade; Implementation Guide;Supported Platforms

Documentation updates Support, Documentation, Documentation Updates

Implementation guides support policy Support, Support Policy

Prerelease notes Support, Documentation, Documentation Updates,Category, Release Notes

Product release roadmap Support, Roadmaps + Schedules

Release notes Support, Documentation, Documentation Updates,Category, Release Notes

Release value proposition Support, Documentation, Documentation Updates,Category, Release Value Proposition

Statement of direction Support, Documentation, Documentation Updates,Category, Statement of Direction

Troubleshooting information Support, Troubleshooting

Upgrade documentation Support, Documentation, Upgrade Documentation andScripts

Typographical Conventions and Visual CuesThis section discusses:

• Typographical conventions.• Visual cues.• Country, region, and industry identifiers.• Currency codes.

Copyright © 2003–2008, Oracle and/or its affiliates. All rights reserved. xi

General Preface

Typographical ConventionsThis table contains the typographical conventions that are used in implementation guides:

Typographical Convention or Visual Cue Description

Bold Indicates PeopleCode function names, business functionnames, event names, system function names, methodnames, language constructs, and PeopleCode reservedwords that must be included literally in the function call.

Italics Indicates field values, emphasis, and JD EdwardsEnterpriseOne or other book-length publication titles.In PeopleCode syntax, italic items are placeholders forarguments that your program must supply.

We also use italics when we refer to words as words orletters as letters, as in the following: Enter the letterO.

KEY+KEY Indicates a key combination action. For example, a plussign (+) between keys means that you must hold downthe first key while you press the second key. For ALT+W,hold down the ALT key while you press the W key.

Monospace font Indicates a PeopleCode program or other code example.

“ ” (quotation marks) Indicate chapter titles in cross-references and words thatare used differently from their intended meanings.

. . . (ellipses) Indicate that the preceding item or series can be repeatedany number of times in PeopleCode syntax.

{ } (curly braces) Indicate a choice between two options in PeopleCodesyntax. Options are separated by a pipe ( | ).

[ ] (square brackets) Indicate optional items in PeopleCode syntax.

& (ampersand) When placed before a parameter in PeopleCode syntax,an ampersand indicates that the parameter is an alreadyinstantiated object.

Ampersands also precede all PeopleCode variables.

Visual CuesImplementation guides contain the following visual cues.

xii Copyright © 2003–2008, Oracle and/or its affiliates. All rights reserved.

General Preface

NotesNotes indicate information that you should pay particular attention to as you work with the JD EdwardsEnterpriseOne system.

Note. Example of a note.

If the note is preceded by Important!, the note is crucial and includes information that concerns what you mustdo for the system to function properly.

Important! Example of an important note.

WarningsWarnings indicate crucial configuration considerations. Pay close attention to warning messages.

Warning! Example of a warning.

Cross-ReferencesImplementation guides provide cross-references either under the heading “See Also” or on a separate linepreceded by the word See. Cross-references lead to other documentation that is pertinent to the immediatelypreceding documentation.

Country, Region, and Industry IdentifiersInformation that applies only to a specific country, region, or industry is preceded by a standard identifier inparentheses. This identifier typically appears at the beginning of a section heading, but it may also appearat the beginning of a note or other text.

Example of a country-specific heading: “(FRA) Hiring an Employee”

Example of a region-specific heading: “(Latin America) Setting Up Depreciation”

Country IdentifiersCountries are identified with the International Organization for Standardization (ISO) country code.

Region IdentifiersRegions are identified by the region name. The following region identifiers may appear in implementationguides:

• Asia Pacific• Europe• Latin America• North America

Industry IdentifiersIndustries are identified by the industry name or by an abbreviation for that industry. The following industryidentifiers may appear in implementation guides:

• USF (U.S. Federal)

Copyright © 2003–2008, Oracle and/or its affiliates. All rights reserved. xiii

General Preface

• E&G (Education and Government)

Currency CodesMonetary amounts are identified by the ISO currency code.

Comments and SuggestionsYour comments are important to us. We encourage you to tell us what you like, or what you would like tosee changed about implementation guides and other Oracle reference and training materials. Please sendyour suggestions to your product line documentation manager at Oracle Corporation, 500 Oracle Parkway,Redwood Shores, CA 94065, U.S.A. Or email us at [email protected].

While we cannot guarantee to answer every email message, we will pay careful attention to your commentsand suggestions.

Common Fields Used in Implementation GuidesAddress Book Number Enter a unique number that identifies the master record for the entity. An

address book number can be the identifier for a customer, supplier, company,employee, applicant, participant, tenant, location, and so on. Depending onthe application, the field on the form might refer to the address book numberas the customer number, supplier number, or company number, employeeor applicant ID, participant number, and so on.

As If Currency Code Enter the three-character code to specify the currency that you want to useto view transaction amounts. This code enables you to view the transactionamounts as if they were entered in the specified currency rather than theforeign or domestic currency that was used when the transaction was originallyentered.

Batch Number Displays a number that identifies a group of transactions to be processed bythe system. On entry forms, you can assign the batch number or the systemcan assign it through the Next Numbers program (P0002).

Batch Date Enter the date in which a batch is created. If you leave this field blank, thesystem supplies the system date as the batch date.

Batch Status Displays a code from user-defined code (UDC) table 98/IC that indicates theposting status of a batch. Values are:Blank: Batch is unposted and pending approval.A: The batch is approved for posting, has no errors and is in balance, buthas not yet been posted.D: The batch posted successfully.E: The batch is in error. You must correct the batch before it can post.

xiv Copyright © 2003–2008, Oracle and/or its affiliates. All rights reserved.

General Preface

P: The system is in the process of posting the batch. The batch is unavailableuntil the posting process is complete. If errors occur during the post, thebatch status changes to E.U: The batch is temporarily unavailable because someone is working withit, or the batch appears to be in use because a power failure occurred whilethe batch was open.

Branch/Plant Enter a code that identifies a separate entity as a warehouse location, job,project, work center, branch, or plant in which distribution and manufacturingactivities occur. In some systems, this is called a business unit.

Business Unit Enter the alphanumeric code that identifies a separate entity within abusiness for which you want to track costs. In some systems, this is called abranch/plant.

Category Code Enter the code that represents a specific category code. Category codes areuser-defined codes that you customize to handle the tracking and reportingrequirements of your organization.

Company Enter a code that identifies a specific organization, fund, or other reportingentity. The company code must already exist in the F0010 table and mustidentify a reporting entity that has a complete balance sheet.

Currency Code Enter the three-character code that represents the currency of the transaction.JD Edwards EnterpriseOne provides currency codes that are recognized bythe International Organization for Standardization (ISO). The system storescurrency codes in the F0013 table.

Document Company Enter the company number associated with the document. This number, usedin conjunction with the document number, document type, and general ledgerdate, uniquely identifies an original document.If you assign next numbers by company and fiscal year, the system uses thedocument company to retrieve the correct next number for that company.If two or more original documents have the same document number anddocument type, you can use the document company to display the documentthat you want.

Document Number Displays a number that identifies the original document, which can be avoucher, invoice, journal entry, or time sheet, and so on. On entry forms, youcan assign the original document number or the system can assign it throughthe Next Numbers program.

Document Type Enter the two-character UDC, from UDC table 00/DT, that identifies theorigin and purpose of the transaction, such as a voucher, invoice, journalentry, or time sheet. JD Edwards EnterpriseOne reserves these prefixesfor the document types indicated:P: Accounts payable documents.R: Accounts receivable documents.T: Time and pay documents.I: Inventory documents.O: Purchase order documents.S: Sales order documents.

Copyright © 2003–2008, Oracle and/or its affiliates. All rights reserved. xv

General Preface

Effective Date Enter the date on which an address, item, transaction, or record becomesactive. The meaning of this field differs, depending on the program. Forexample, the effective date can represent any of these dates:

• The date on which a change of address becomes effective.• The date on which a lease becomes effective.• The date on which a price becomes effective.• The date on which the currency exchange rate becomes effective.• The date on which a tax rate becomes effective.

Fiscal Period and FiscalYear

Enter a number that identifies the general ledger period and year. For manyprograms, you can leave these fields blank to use the current fiscal period andyear defined in the Company Names & Number program (P0010).

G/L Date (general ledgerdate)

Enter the date that identifies the financial period to which a transaction will beposted. The system compares the date that you enter on the transaction to thefiscal date pattern assigned to the company to retrieve the appropriate fiscalperiod number and year, as well as to perform date validations.

xvi Copyright © 2003–2008, Oracle and/or its affiliates. All rights reserved.

JD Edwards EnterpriseOne PerformanceMonitor Preface

This preface discusses Oracle’s JD Edwards EnterpriseOne Performance Monitor companion documentation.

JD Edwards EnterpriseOne Performance MonitorWorkbench Companion Documentation

Additional, essential information describing the setup and design of JD Edwards EnterpriseOne Tools residesin companion documentation. The companion documentation consists of important topics that apply to JDEdwards EnterpriseOne Performance Monitor as well as other JD Edwards EnterpriseOne Tools. You shouldbe familiar with the contents of these companion guides:

• JD Edwards EnterpriseOne Tools Release 8.98 Reference Guide for <platform>

• JD Edwards EnterpriseOne Applications Release 9.0 <install_or_upgrade> Guide for <database> on<platform>

Customers must conform to the supported platforms for the release as detailed in the JD EdwardsEnterpriseOne minimum technical requirements. In addition, JD Edwards EnterpriseOne may integrate,interface, or work in conjunction with other Oracle products. Refer to the cross-reference material in theProgram Documentation at http://oracle.com/contracts/index.html for Program prerequisites and versioncross-reference documents to assure compatibility of various Oracle products.

Copyright © 2003–2008, Oracle and/or its affiliates. All rights reserved. xvii

Preface

xviii Copyright © 2003–2008, Oracle and/or its affiliates. All rights reserved.

CHAPTER 1

Getting Started with JD Edwards EnterpriseOnePerformance Monitor

This chapter discusses:

• JD Edwards EnterpriseOne Performance Monitor Overview

• JD Edwards EnterpriseOne Performance Monitor Implementation

JD Edwards EnterpriseOne Performance Monitor OverviewOracle’s JD Edwards EnterpriseOne Performance Monitor enables you to view real-time and historicalperformance data of your JD Edwards systems. JD Edwards EnterpriseOne Performance Monitor provides theinformation that you need to solve immediate performance issues and analyze trends in system performance.

By default, JD Edwards EnterpriseOne Performance Monitor is disabled on a new JD Edwards EnterpriseOneinstallation. To enable JD Edwards EnterpriseOne Performance Monitor, follow the configuration instructionsin this guide.

When you have a JD Edwards application environment running and you have set up JD Edwards EnterpriseOnePerformance Monitor, you can begin to capture and analyze JD Edwards EnterpriseOne performance data.

JD Edwards EnterpriseOne Performance MonitorImplementation

This section provides an overview of the steps that are required to implement JD Edwards EnterpriseOnePerformance Monitor.

In the planning phase of your implementation, take advantage of all JD Edwards sources of information,including the installation guides and troubleshooting information. A complete list of these resources appears inthe preface in About This Documentation with information about where to find the most current version of each.

JD Edwards EnterpriseOne Performance MonitorImplementation StepsThis table lists the steps for JD Edwards EnterpriseOne Performance Monitor implementation.

Copyright © 2003–2008, Oracle and/or its affiliates. All rights reserved. 1

Getting Started with JD Edwards EnterpriseOne Performance Monitor Chapter 1

Step Reference

1. Install EnterpriseOne. JD Edwards EnterpriseOne installation documentationfor your platform.

2. Install one or more EnterpriseOne applications. JD Edwards EnterpriseOne installation documentation foryour applications.

2 Copyright © 2003–2008, Oracle and/or its affiliates. All rights reserved.

CHAPTER 2

Understanding JD Edwards EnterpriseOnePerformance Monitor

This chapter discusses:

• JD Edwards EnterpriseOne Performance Monitor.

• JD Edwards EnterpriseOne Performance Monitor elements.

• Implementation options.

• JD Edwards EnterpriseOne Performance Monitor instrumentation.

• JD Edwards EnterpriseOne Performance Monitor integration with third-party systems.

• JD Edwards EnterpriseOne Performance Monitor data.

• Scope of JD Edwards EnterpriseOne Performance Monitor.

JD Edwards EnterpriseOne Performance MonitorJD Edwards EnterpriseOne Performance Monitor helps system administrators monitor JD EdwardsEnterpriseOne performance data and, if wanted, share the data with third-party monitoring tools. JD EdwardsEnterpriseOne Performance Monitor is a diagnostic utility for monitoring the performance of the mainelements of your JD Edwards EnterpriseOne system, such as web servers, application servers, and processscheduler servers. You can monitor real-time performance and analyze historical data.

JD Edwards EnterpriseOne Performance Monitor reports durations and key metrics of JD EdwardsEnterpriseOne runtime execution, such as SQL statements and business functions.

Note. JD Edwards EnterpriseOne Performance Monitor enables you to isolate and identify the causes ofperformance issues; however, it does not provide automatic solutions to performance issues.

JD Edwards EnterpriseOne Performance Monitor OutputThe metrics provided by JD Edwards EnterpriseOne Performance Monitor enable system administrators to:

• Monitor real-time system performance.• Identify poorly performing tiers, hosts, domains, servers, application code, and SQL statements in anEnterpriseOne environment.

• Identify performance trends.• Address and isolate performance bottlenecks.


Understanding JD Edwards EnterpriseOne Performance Monitor Chapter 2

JD Edwards EnterpriseOne Performance Monitor ElementsThis diagram illustrates the main elements of JD Edwards EnterpriseOne Performance Monitor:


Chapter 2 Understanding JD Edwards EnterpriseOne Performance Monitor

Database Host

Archivetable

Historytable

Currenttable

Config.table

APPHOST - Monitored System

Application Server

Archive batch process:- Moves/removes data from Current/Historytables to Archive table.

Reaper batch process:- Moves/removes timed out data fromCurrent table to the History table.

AppServer C process (C-Agent):-Sends performance data through JDENetmessage to the PerfMon Java Adapter on theMonitoring Server-Receives Agent configuration changes.

User Interface

WEBHOST – Monitored System

Java Application Server

JAS Runtime Engine:

- Retrieves performance data from thedatabase and displays it in EOne PerfMonUser interface per user request.

- Changes configuration in database andsends notification to the PPMI Server per userrequest.

WEBHOST – Monitoring System

Monitoring Server

PerfMon Java Adapter:- Receives performance data from C-Agentsand converts the data to HTTP format beforehanding it to the Monitor Server.- Sends new Agent configuration to C-Agentson the APPHOst.

Monitor Server:- Receives data from Java Agents in HTTPformat and inserts the data in database.- Returns Agent configuration to all registeredAgents.- Sends performance data to all registered(third party) proxy clients.

2

1

84

6

4

Arrow Format Description1 JdeNet C processes (C-Agents) on the APPHOST send performance data to the PerfMon Java Adapter.2 HTTP PerfMon Java Adapter sends the performance data to the Monitor Server using PerfMon Java Agents.3 HTTP JAS Runtime Engine sends performance data to the Monitor Server using PerfMon Java Agents.4 JDBj Monitor Server inserts performance data in the database in current and history tables.5 HTTP Administrator initiates Agent Configuration change through the PerfMon User Interface.6 JDBj JAS Runtime Engine updates the Agent configuration in the database.7 HTTP JAS Runtime Engine notifies the Monitor Server from Agent Configuration change in the database.8 JDBj Monitor Server reads the new Agent configuration form database.9 HTTP Monitor Server sends the new Agent configuration to all Java Agents.10 JdeNet PerfMon Java Adapter sends the new Agent configuration to all C-Agents on the APPHOST.11 JDB Archive batch process archives/removes performance data in the database.12 JDB Reaper batch process moves timed out data from current table to the history table.13 JDBj JAS Runtime Engine reads the data from database and displays it in HTML format to the User Interface.

5

7 93

9

12

1313

10

11

JD Edwards EnterpriseOne Performance Monitor Elements

For a detail explanation of the diagram, see Appendix B.



A monitoring system can monitor one or more JD Edwards EnterpriseOne application systems. However,the monitored system can be monitored by just one monitoring system.

You can configure a self-monitoring system for development and testing.

The Monitored SystemThe monitored system comprises these main elements:

• JD Edwards EnterpriseOne application database.• JD Edwards EnterpriseOne application server.• JD Edwards EnterpriseOne web server.

Note. An application server is also known as a business logic server in some materials. However, in this guide,only the term application server appears.

JD Edwards EnterpriseOne Performance Monitor agents reside on each main element of the monitored system.Agents run on the servers to gather and report performance information. An agent is a small piece of codeoperating from within an existing process. It collects performance data and uses a dedicated thread to send thedata to the monitoring system. Agent threads report data to the monitoring system’s monitor servlet, which inturn reports performance data to the PSPPMSRV server processes in the monitoring system’s application server.

Two types of agents exist:

• Process instrumentation agents that report data about the specific server activities.• Domain resource agents that report resource usage statistics about the process and server, such as CPU usage.

JD Edwards EnterpriseOne Application DatabaseThis database is installed with the installation of the JD Edwards EnterpriseOne system. This database hasall the tables to store performance data for EnterpriseOne. The default installation installs both JD EdwardsEnterpriseOne application tables and JD Edwards EnterpriseOne Performance Monitor tables within the samedatabase. JD Edwards EnterpriseOne users can use the Object Configuration Management (OCM) settings touse a separate database for Performance Data. Separating performance data and production data into separatedatabases should enhance the performance of the JD Edwards EnterpriseOne Servers.

Application ServerThe JD Edwards EnterpriseOne application server, also known as the JD Edwards EnterpriseOne EnterpriseServer, contains the CallObject Kernel processes used to run business functions on the application server.Each CallObject Kernel process, or each CallObject thread, in the case of multi-threaded CallObjects, uses aC-Agent to collect and send the performance data to the JD Edwards EnterpriseOne Performance MonitorJava Adapter on the monitoring server.

The C-Agent is a small piece of code that operates within an existing CallObject process or thread. TheC-Agent uses the JD Edwards EnterpriseOne JDENet communication protocol to send the performance data tothe monitoring server. C-Agents report data to the PerfMon Java Adapter, which in turn sends the data tothe Monitor servlet. The monitoring system’s monitor servlet then sends performance data to the monitoringsystem’s Data Collator Servlet.

Note. JD Edwards EnterpriseOne Performance Monitor does not monitor the performance of the RDBMSor the server on which it runs.



Web ServerThe JD Edwards EnterpriseOne web server, also known as the JD Edwards EnterpriseOne JAS (Javaapplication server), contains Java components of the JD Edwards EnterpriseOne web server. The JD EdwardsEnterpriseOne Java components have been instrumented to send performance data to the monitoring server.Each component of the JAS Server uses a Java Agent to collect and send the performance data to the monitorservlet on the monitoring server.

A Java Agent is a small piece of code operating from within an existing JVM process. It collects data and usesa dedicated thread to send the data to the monitoring system. Java Agents report data to the Monitor servletwhich in turn sends XML formatted performance data to the Monitoring System’s Data Collator servlet.

The Monitoring SystemThe monitoring system includes these elements:

• JD Edwards EnterpriseOne Performance Monitor Java Adapter.• JD Edwards EnterpriseOne Monitor Servlet.• JD Edwards EnterpriseOne Performance Monitor Integration (PPMI) Servlet.• JD Edwards EnterpriseOne Data Collator Servlet.

JD Edwards EnterpriseOne Performance Monitor Java AdapterJD Edwards EnterpriseOne Performance Monitor Java Adapter is the bridge between the JD EdwardsEnterpriseOne application server and the monitoring server. C-Agents on the application server (CallObjectKernel processes/threads) collect and send the performance data to the Java Adapter using the JDENetcommunication protocol. For each C-Agent on the application server, a Java Agent is created within theJD Edwards EnterpriseOne PerfMon Java Adapter process. Based on the type of the message sent by theC-Agent, the Java Agent calls into the appropriate Java Agent API. From this point on, the performancedata is processed the same way as if a Java Agent running on the JD Edwards EnterpriseOne web serversent the data. This architecture allows the same components on the monitoring server (Monitor, PPMI,and Data Collator servlets) to manage Agents and process performance data regardless of the origin of thedata: application server or web server.

See Chapter 2, "Understanding JD Edwards EnterpriseOne Performance Monitor," Implementing theProduction Monitoring System, page 8.

JD Edwards EnterpriseOne PPMI ServletThe PPMI servlet registers and manages PPMI clients. The Data Collator is an integrated PPMI client forJD Edwards EnterpriseOne monitoring server. Any third-party solution can register to the PPMI servlet andreceive JD Edwards EnterpriseOne performance data.

The PPMI servlet also receives the Agent configuration notifications sent by the JD Edwards EnterpriseOneweb server. Administrators can change the Agent configuration for one or all the registered Agents and notifyall the Agents of the changes. The JD Edwards EnterpriseOne web server sends an Agent notification messageto the PPMI servlet, which in turn, notifies the Monitor servlet. The Monitor servlet reads the new Agentconfiguration for the appropriate Agents from the database and sends the configuration back to Agents. Notethat each time an Agent sends the performance data to the Monitor Servlet the Agent configuration is sentback to the Agent as the response. The PPMI servlet also adds a new record in the database for each Agentregistered with the monitoring system.



JD Edwards EnterpriseOne Monitor ServletThe Monitor servlet receives the performance data from Agents and sends it to the Data Collators. For eachmessage sent by an Agent, the Monitor servlet sends back the Agent configuration. This way, the Agents arealways up-to-date of any configuration changes. Note that administrators can change the Agent configurationsfrom the JD Edwards EnterpriseOne PerfMon User Interface.

JD Edwards EnterpriseOne Data Collator ServletThe Data Collator servlet registers itself with the PPMI servlet as a PPMI client. By registering with the PPMI,the Data Collator will receive the performance data sent by the Monitor servlet. Note that the PPMI servletnotifies the Monitor servlet of all newly registered clients. The Data Collator’s main function is to write theperformance data to the JD Edwards EnterpriseOne PerfMon database. Two main database tables are used tocontain the performance data: Current Transaction table and History Transaction table. The Data Collatorwrites the performance data for a running transaction to the current transaction table until the transaction ends.The Data Collator then writes the End Transaction data to the History Transaction table and removes allrecords related to this transaction from the Current Transaction table.

Implementing the Production Monitoring SystemIn a production environment, you should configure the JD Edwards EnterpriseOne monitoring systemseparate from the production monitored systems. Any JD Edwards EnterpriseOne system database that isdelivered with JD Edwards EnterpriseOne installation contains the appropriate database definitions to storeall JD Edwards EnterpriseOne Performance Monitor data. With the separate monitoring system, you canmonitor a single JD Edwards EnterpriseOne system, or you can configure it to monitor multiple JD EdwardsEnterpriseOne systems.

Note. JD Edwards EnterpriseOne Performance Monitor can monitor any JD Edwards EnterpriseOne systemrunning on 8.95 or greater. Always consult JD Edwards EnterpriseOne Release Notes and guides to becomeaware of any exceptions or unsupported features between release levels.

JD Edwards EnterpriseOne Performance MonitorInstrumentation

This section explains the terminology that is associated with JD Edwards EnterpriseOne PerformanceMonitor instrumentation. Instrumentation refers to the modifications that are made to internal JD EdwardsEnterpriseOne programming code that enable the system to report performance data to a monitor. Selectedareas of JD Edwards EnterpriseOne runtime source code have been instrumented. When the system runsinstrumented code, it generates time-stamped performance metrics that are relevant to that section of code.Agents running on the monitored system send the performance data to JD Edwards EnterpriseOne PerformanceMonitor. Instrumentation generates performance measurement units (PMUs) and events.

Understanding PMUsA PMU is a unit of measure that reflects the execution of a section of code. The system starts and stops aPMU at specific locations in the code, and the system may update a PMU anytime between the start and stoptimes. JD Edwards EnterpriseOne has defined a set of PMU types, and each type of PMU corresponds tothe instrumentation at a specific code location such as a SQL Execute in the application server or a JDBjrequest in the web server.



Each PMU includes:

• PMU Type.• Instance identifier (a unique identifier for a specific PMU instance).

• Start time.• Stop time.• Status.• Metrics (such as number of SQL fetches or buffer size used in a Jolt response).

Open PMUs are those that are currently being processed. These are PMUs for which a "stop" transaction hasnot yet been received. Completed PMUs are those for which a "stop" transaction has been received. PMUscan assume a parent-child relationship. Child PMUs start within a parent PMU. Child PMUs are linked totheir parent by the parent instance ID.

You can view PMUs within a tree structure that reveals the hierarchy of parent-child PMUs and indicates theprocessing times at each level.

Understanding EventsEvents are not implemented for the 8.95 release of JD Edwards EnterpriseOne Performance Monitor.

Events are notifications containing performance metrics that are different from PMUs in that they are nothierarchical and they do not have durations. Events relate to resource usage, such as CPU usage or memoryallocation. JD Edwards EnterpriseOne has defined a set of event types, and each type of event is reported at aspecific location in the instrumented code.

Each event has:

• Type.• Instance identifier (a unique identifier for a specific event instance).• Timestamp.• Severity.• Metrics (such as CPU usage and memory allocation).

See Chapter 7, "Evaluating JD Edwards EnterpriseOne Performance Monitor Meta-Data," Revising EventDefinitions, page 43.

Performance Integration with Third-Party SystemsUsing web service technology, performance data that is generated by JD Edwards EnterpriseOne PerformanceMonitor can be shared with third-party performance-monitoring tools by way of JD Edwards EnterpriseOnePerformance Monitor Integration (PPMI) API. The PPMI API uses the Simple Object Access Protocol (SOAP).

Note. The PPMI API protocol is not documented in guides. It is used only in products that are developed byJD Edwards EnterpriseOne system and performance management integration partners. You can use the PPMIAPI only if you are licensed through JD Edwards.



JD Edwards EnterpriseOne Performance Monitor DataAfter JD Edwards EnterpriseOne Performance Monitor is configured to retrieve and store data in theperformance database tables, you can view the performance data using a variety of JD Edwards EnterpriseOneapplications that:

• Provide a summary of performance data.

• Present raw performance data.

You can access all of the forms that are related to JD Edwards EnterpriseOne Performance Monitor using theJD Edwards EnterpriseOne Performance Monitor menu. Some performance information appears in grids,while other performance information appears in charts. You have the option to view chart information in gridsfor sorting and downloading to Microsoft Excel.

Scope of JD Edwards EnterpriseOne Performance MonitorJD Edwards EnterpriseOne Performance Monitor provides performance metrics for:

• JD Edwards EnterpriseOne application server components- Business function processing- Database operations (insert, delete, update, select).

• JD Edwards EnterpriseOne WEB Server (also known as JAS) components.- Business function processing- Database operations (insert, delete, update, select)- JD Edwards EnterpriseOne application events.


CHAPTER 3

Setting Up JD Edwards EnterpriseOnePerformance Monitor

This chapter provides an overview of the configuration of JD Edwards EnterpriseOne Performance Monitor anddiscusses how to:

• Enable the required elements on the monitoring system.

• Enable the required elements on the monitored system.

Configuring JD Edwards EnterpriseOne Performance MonitorConfiguring JD Edwards EnterpriseOne Performance Monitor involves enabling the required elements onthe monitored system and the monitoring system.

When you install the JD Edwards EnterpriseOne System and transfer the appropriate files to the web serverand application server, all of the required elements are in place. You do not need to install additional modulesfor JD Edwards EnterpriseOne Performance Monitor.

Enabling the Required Elements on the Monitoring SystemThis section covers the configuration of your monitoring system, which includes:

• Setting up JD Edwards EnterpriseOne Performance Monitor database.• Setting up the web server for the monitoring system.• Configuring JAS.INI file on the monitoring server.

Setting Up JD Edwards EnterpriseOne PerformanceMonitor DatabaseThe monitoring database requires the use of at least the JD Edwards EnterpriseOne System database for theproduction monitoring system. Set up this database up using the instructions in the JD Edwards EnterpriseOneInstallation Guide. To improve performance of the monitored server, you may want to map the PerfMondatabase tables to a database other than the production database. These tables would need to be mapped:


Setting Up JD Edwards EnterpriseOne Performance Monitor Chapter 3

Table Server

F95900 PM System Definitions (PSPMSYSDEFN)

F95900D PM System Definition Languages (PSPMSYSDEFN_LAN)

F95901 PM System Defaults (PSPMSYSDEFAULTS)

F95902 PS System Version (PSPMSYSVERSION)

F95903 PM Table Map (PSPMTABLEMAP)

F95904 PMGlobal Administration (PSPMMONITORGBL)

F95905 PMMonitor Clustering (PSPMMONINST)

F95906 PM Frequent Users (PSPMOPRDEFN)

F95907 PM Trace Names (PSPMPERFTACE)

F95908 PM Frequent Components (PSPMPNLGRPDEFN)

F95909 PMAgent Definition (PSPMAGENT)

F95910 PMAgent Filters (PSPMAGENTFILTER)

F95911 PMArchive Parms (PSPMARCHRUNCNTL)

F95912 PM Collator Instances (PSPMCOLLINST)

F959310 PM Event Set (PSPMEVENTSET)

F959310D PM Event Set Language (PSPMEVENTSET_LN)

F959311 PM Event Definition (PSPMEVENTDEFVN)

F959311D PM Event Definition Language (PSPMEVENT_LNG)

F959320 PM Transaction Set (PSPMTRANSSET)

F959320D PM Transaction Set Language (PSPMTRANSSET_LN)

F959321 PM Transaction Definition (PSPMTRANSDEFN)

F959321D PM Transaction Definition Language (PSPMTRANS_LAN)

F959331 PMMetric Definition (PSPMMETRICDEFN)

F9593311 PMMetric Definition UDCDisplay (n/a)

F959331D PMMetric Definition Language (PSPMMETRIC_LNG)

F959332 PMMetric Value (PSPMMETRICVALUE)

F959332D PMMetric Value Language (PSPMMETRICVALUE_LN)


Chapter 3 Setting Up JD Edwards EnterpriseOne Performance Monitor

Table Server

F959341 PM Context Definition (PSPMCONTEXTDEFN)

F959341D PMContext Definition Language (PSPMCONTEXTDEFN_LNG)

F95951 PM Event History (PSPMEVENTHIST)

F95952 PM Event Archive (PSPMEVENTARCH)

F95953 PM Event Clone (PSPMEVENTHISTCL)

F95960 PM Transaction Current (PSPMTRANSCURR)

F95961 PM Transaction History (PSPMTRANSHIST)

F95962 PM Transaction Archive (PSPMTRANSARCH)

F95963 PM Transaction Clone (PSPMTRANSHISTCL)

Setting Up the Web Server for the Monitoring SystemThe JD Edwards EnterpriseOne Transaction Server (RTE) Installer program installs all of the elements thatJD Edwards EnterpriseOne Performance Monitor requires on the web server. No additional installationsare required.

JD Edwards EnterpriseOne Performance Monitor servlets that run on the web server of the monitoringsystem are:

• Monitor servlet.• PPMI servlet.• Data Collator servlet.

When you start the WEB Server on the monitoring server, different components of the Server start in this order:

1. The JD Edwards EnterpriseOne PerfMon Java Adapter is started and waits for incoming messagesfrom JD Edwards EnterpriseOne application servers.

2. The Data Collator is started.3. The Data Collator sends a registration request to the PPMI servlet.4. PPMI servlet registers the Data Collator.5. Data Collator waits to receive performance data from Monitor servlet.6. JD Edwards EnterpriseOne JAS Server Agents register with the Monitor servlet.7. JD Edwards EnterpriseOne CallObject processes on the application server (C-Agents) send the AgentInitialization request to the JD Edwards EnterpriseOne Java Adapter.

8. JD Edwards EnterpriseOne Java Adapter registers the C-Agents with the Monitor servlet.9. JAS Server Agents send performance data to the Monitor servlet.10. C-Agents send performance data to the JD Edwards EnterpriseOne Java Adapter.11. JD Edwards EnterpriseOne Java Adapter sends performance data to the Monitor servlet.



12. Monitor servlet sends performance data to the Data Collator.13. Data Collator writes performance data to the database.

Note. Make note of the URL of the web server for the monitoring system. On the monitored system, youneed to specify the appropriate URL to which performance data is sent.

Configuring JAS.INI file on the Monitoring ServerThe JD Edwards EnterpriseOne Transaction Server installer installs the PerfMon components on theMonitoring System. The following sections refer to the JD Edwards EnterpriseOne Transaction Server InstallDirectory by JD Edwards EnterpriseOneTransInstallDir.

The JAS.INI file on the monitoring server is located in EnterpriseOneTransInstallDir/cfg/jas.ini. This .ini filehas some settings in common with the Java Application servers’s (JAS) JAS.INI file.

These settings in the jas.ini file on the monitoring server are in addition to these common settings.

[JDENET_KERNEL_DEF2]The [JDENET_KERNEL_DEF2] section defines the JD Edwards EnterpriseOne PerfMon Java Adaptercomponent of the monitoring server. You do not need to change any settings for this section and it is correctlyconfigured after the install.

# Name of PerfMon Java adapter kernel.

#

krnlName=E1PerfMon Adapter

#

# Class of PerfMon Java adapter kernel to be loaded; contains dispatch methods.

#

processClassName=com.JD Edwards.pt.e1.ppm.E1PmAdapter.E1PmDispatchMessageV1

#

# Start of message range for this kernel

#

startMessageRange=11000

#

# End of message range for this kernel

#

endMessageRange=11100

#

# Maximum number of threads that this kernel will run.

#

maxNumberOfThread=1

[JDENET]In order for the EnterpriseOne PerfMon Java Adapter to start correctly on the monitoring server, these settingsneed to be set in the [JDENET] section. Note that the value of the variable MaxKernelRanges should be 2.



#

# Maximum number of dedicated kernel types

#

maxKernelRanges=2

#

# JAS Server JDENET Listening port. This is the port on which the JDENet Listener⇒will

# listen for the performance data coming from E1 application server. Note that the

# value of this setting should be equal to the E1 application server JDE.INI file⇒setting

# for:

# [PERFMON_JAVA_ADAPTER_1]

# javaAdapterPort=6545

serviceNameListen=6545

[PERFMON]This section defines the settings for JD Edwards EnterpriseOne Performance Monitor servlets on the Server.

# This is the URL of the monitor Servlet.

# ~MONITOR_HOST_NAME~ is the name of the machine where you installed the

# E1 monitoring server.

# ~MONITOR_LISTEN_PORT~ is the port number on which the Monitor Servlet will

# be listening.

# E1 Transaction Server installer will update this setting in the jas.ini file⇒with the

# correct host name and port number.

monitorUrl=http://~MONITOR_HOST_NAME~:~MONITOR_LISTEN_PORT~/ppm/monitor

# A String used to distinguish the host and port of the machines where different⇒Agents

# are running. Please use the same host name and port number used in the previous⇒setting.



hostPort=~MONITOR_HOST_NAME~:~MONITOR_LISTEN_PORT~

#

# Transactions will be timed out by the Monitor Server if the “End Transaction” is⇒not

# received this number of seconds after the Start Transactoin.

#

transactionTimeout=60

#

# not currently being used.

#



sampler=60

#

# PPMI_HOST_NAME is the name of the machine where the monitoring server

# is running on.

# PPMI_LISTEN_PORT is the port number on which the monitoring server

# is listening.

#

ppmiUrl=http://~PPMI_HOST_NAME~:~PPMI_LISTEN_PORT~/ppm/ppmi

#

# Maximum number of threads that will be used by Java adapter.

# You can use one thread per CallObject process/thread on the application server.

# For example, if there are 5 CallObject processes on the application server and⇒each one

# is configured to have 4 threads then you can set this setting to 20.

#

#

dispatchMaxThread=20

#

# if true, then users can snoop monitor servlet’s status.

# Some HRML pages can be used to view the status of different PerfMon Servlets and

# E1PmJavaAdapter process. In order to activate the access to those pages you⇒should,

# set this flag to true.

#

PPMConsole=false

#

# Maximum size (megabytes) of memory used by Monitor servlet queues.

# You can increase this setting if error messages appear on the monitoring server

# complaining about transferring data between different components of the

# monitoring server.

#

PPMMonitorBufferSize=50

#

# Interval (in minutes) until a partially filled batch is flushed by the Monitor⇒servlet.

# The batch is flushed if it is filled before this time.

PPMSyncInterval=1



[PERFCOL]# URL of PPMI to register with.#ppmiUrl=http://~PPMI_HOST_NAME~:~PPMI_LISTEN_PORT~/ppm/ppmi

## Location of Collator servlet.# COLLATOR_HOST_NAME is the name of the machine where the Monitoring System# is installed.# COLLATOR_PORT_NUMBER is the port number on which the monitoring server# is listening.#collatorUrl=http://~COLLATOR_HOST_NAME~:~COLLATOR_LISTEN_PORT~/ppm/Collator

## Group of streaming performance data to be associated with the collator.# This is a string to distinguish different data collators. Different data coll# running on different monitoring systems can have their own groups.#GROUP=group1

## Number of elements (for example, transaction start or end) the Monitor servle# sends to PPMI clients.#BATCHSIZ=1000

## Number of Collator threads to start that will listen to one group.#NumCollThreads=1

Enabling the Required Elements on the Monitored SystemThis section discusses enabling the required elements on the monitored system which is the system for whichyou intend to collect performance data. A monitored system requires these items to be in place:

• JD Edwards EnterpriseOne application server.• JD Edwards EnterpriseOne web server (also known as JD Edwards EnterpriseOne JAS Server).• Valid monitor servlet URL value.

Setting Up the Database of the Monitored SystemAs long as your JD Edwards EnterpriseOne application server is running against your JD EdwardsEnterpriseOne database, no further database configuration is required for JD Edwards EnterpriseOnePerformance Monitor.



Specifying the Monitor URLThe monitor URL identifies the Monitor servlet. The monitor URL value must reflect the URL of the monitorservlet that is running on the monitoring system. The readme.txt generated by the installer contains thecorrect value for the URL. The agents on the monitored system check the monitor URL value periodically.When the monitor URL value is set to NONE, JD Edwards EnterpriseOne Performance Monitor componentson the monitored system are disabled.

Setting Up the Web Server of the Monitored SystemNo additional installation procedure is required. When JD Edwards EnterpriseOne Performance Monitoris turned on (by providing the monitor URL or by setting the flag in the JAS.INI file), agents on the JDEdwards EnterpriseOne web server automatically become active and begin relaying performance data tothe monitoring system.

Configuring JAS.INI file on the Monitored Server (JDEdwards EnterpriseOne JAS Server)The JAS.INI file on the monitored web server requires new settings for PerfMon. If these settingsdo not exist, you need to add them. The JAS.INI file on the monitored web server is located in:E1JASInstallDir/WebClinet.war/WEB-INF/jas.ini. The following line must exist in the [SERVERCOMPONENTS] section in the jas.ini file on the Monitored Server: com.jdedwards.jas.PerfMonInitThe following section is added to the JAS.INI file to define the settings for JD Edwards EnterpriseOnePerformance Monitor:

[PERFMON]The settings that you need to set after the install are in brackets ({}). For the other settings you can use thedefault installed values and change them later if needed.


# The readme.txt file generated by the installer contains the correct value for⇒url_value.

{monitorUrl}=--Add the URL value from the readme.txt generated by the installer--


# are running. Please use the same host name and port number used in the previous⇒setting.



{hostPort}=--Add the HOST:PORT from the readme.txt generated by the installer--

#

# Transactions will be timed out by the Monitor Server if the “End Transaction” is⇒not

# received this number of seconds after the Start Transactoin.

#




#


#

sampler=60

#

# Please use the host name and port number from the readme.txt generated by the

# installer.

#

ppmiUrl=http://~PPMI_HOST_NAME~:~PPMI_LISTEN_PORT~/ppm/ppmi

#

# if true, then users can snoop monitor servlet’s status.

#

PPMConsole=false

#

# Maximum size (megabytes) of memory used by Monitor servlet queues.

#

PPMMonitorBufferSize=50

#

# Interval (in minutes) until a partially filled batch is flushed by the

# Monitor servlet.

#

PPMSyncInterval=1

#

# Number of Java Agents to initialize at the startup of the JAS Server. Agent

# initialization is a time consuming process. This many Agents are initialized at⇒the startup

# and the groups of Agents will be initialized if more Agents are needed. If this⇒setting is

# missing from the JAS.INI file the default value of 100 will be used by the⇒system.

ClientCachePerfSize=100

Setting Up the Application ServerPerformance data is gathered for CallObject Kernel processes running on the monitored application server.No installation or configuration procedures are required. When the monitored system is enabled, agents inevery instrumented server process automatically become active and begin relaying performance data tothe monitoring system.

Ensure that the agentActive setting in the [PERFMON] section of the JDE.INI file is set to true (enabled).By default, it is set to false (disabled). If the agentActive setting is commented out or set to anything otherthan true, then the agents are disabled for this server.



Configuring JDE.INI file on the Monitored Server (JDEdwards EnterpriseOne Application Server)PerfMon requires new settings in the JDE.INI file on the monitored Server.

[PERFMON]The settings that you need to set after the install are in brackets ({}). The other settings you can use the defaultinstalled values and change them later if needed.

# flag to enable/disable JD Edwards EnterpriseOne Performance Monitor Agents on⇒the application Server. If⇒set

# to anything other than true no performance data will be sent from the⇒application Server to

# the Monitor Server.

#

agentActive = true


# The readme.txt file generated by the installer contains the correct value for⇒url_value.

{monitorUrl}=--Add the URL value from the readme.txt generated by the installer--


# are running. Please use the host name and port number of the JD Edwards⇒EnterpriseOne application server.

{hostPort}=~E1AppServer_HOST_NAME~:~E1AppServer_LISTEN_PORT~

#

# JDENET mressages will be timed out by the Appliation Server if the response is⇒not

# received before this number of seconds.

#

jdenetTimeout=120

# PerfMon Transactions will be timed out by the Monitor Server if the “End⇒Transaction”

# is not received this number of seconds after the Start Transactoin.

#



#

sampler=60

#

# Default filter mask (Standby) for Agents.

# valid values are:

# Standby 1 No performance data is collected.

# standard 4 Minimum amount of performance data is collected.



# verbose 5 More performance data is collected.

# debug 6 Maximum amount of performance data is collected.

#

filterMask = 1

[PERFMON_JAVA_ADAPTER_1]

#

# Please use the host name of the monitoring server provided in the readme.txt⇒generated

# by the installer.

#

{javaAdapterhost} = -- use the host name of the monitoring System --

#

# Port on which the E1JavaAdapter is listening. Should be the same as the

# [JDENET] serviceNameListen value used by the Monitoring system.

{javaAdapterPort} = -- use the same value as the serviceNameListen in the [JDENET]

secion in the JAS.INI file on the Monitoring System.


CHAPTER 4

Administering JD Edwards EnterpriseOnePerformance Monitor

This chapter provides an overview of JD Edwards EnterpriseOne Performance Monitor administration and discusseshow to:

• Set global system options.

• Set system definition defaults.

• Modify system definitions.

• View agent definitions.

• Set agent filter options.

• Schedule the reaper program.

Understanding JD Edwards EnterpriseOne PerformanceMonitor Administration

This section discusses JD Edwards EnterpriseOne Performance Monitor administration and lists the formsused for JD Edwards EnterpriseOne Performance Monitor administration.

JD Edwards EnterpriseOne Performance Monitor AdministrationJD Edwards EnterpriseOne Performance Monitor administration includes:

• Specifying global settings.

• Viewing performance definitions such as those related to systems, agents, metrics, and so on.

• Setting system defaults.

• Scheduling batch programs that maintain performance data.


Administering JD Edwards EnterpriseOne Performance Monitor Chapter 4

Forms Used for JD Edwards EnterpriseOne PerformanceMonitor Administration

Form Name FormID Navigation UsageGlobal Administration -Global AdministrationRevisions

W95900A JD Edwards EnterpriseOneMenus, JD EdwardsEnterpriseOneLifecycleTools, SystemAdministration Tools, JDEdwards EnterpriseOnePerformance Monitor,Administration, GlobalAdministration

View and modify globaladministration settings, suchas the PPMI URL value.

System Defaults - SystemDefault Revisions

W95900B JD Edwards EnterpriseOneMenus, JD EdwardsEnterpriseOneLifecycleTools, SystemAdministration Tools, JDEdwards EnterpriseOnePerformance Monitor,Administration, SystemDefaults

Set global system defaultsfor all monitored systems.

System Definitions - WorkWith System Definitions

W9500C JD Edwards EnterpriseOneMenus, JD EdwardsEnterpriseOneLifecycleTools, SystemAdministration Tools, JDEdwards EnterpriseOnePerformance Monitor,Administration, SystemDefinitions

View and select systemdefinition that is associatedwith each of the systems thatare being monitored.

System Definitions - SystemDefinition Revisions

W95900D From the System Definitions- WorkWith SystemDefinitions form, click Find.

View and modify the systemdefinition that is associatedwith each of the systemsthat are being monitored.For example, you can setarchive, PMU timeout, andagent buffer size.

Agent Definitions - WorkWith Agent Definitions

W9500E JD Edwards EnterpriseOneMenus, JD EdwardsEnterpriseOneLifecycleTools, SystemAdministration Tools, JDEdwards EnterpriseOnePerformance Monitor,Administration, AgentDefinitions

View and select thedefinitions of the agents thatare running on the monitoredsystem’s application server,and web server.

Agent Definitions - AgentDefinition Revisions

W95900F From the Agent Definitions -Agent Definition Revisionsform, click Find.

Make active or inactive theagent that you selected.


Chapter 4 Administering JD Edwards EnterpriseOne Performance Monitor

Page Name Definition Name Navigation UsageAgent Filters - WorkWithAgent Filters

W9500J JD Edwards EnterpriseOneMenus, JD EdwardsEnterpriseOneLifecycleTools, SystemAdministration Tools, JDEdwards EnterpriseOnePerformance Monitor,Administration, Agent Filters

Search for the filter levels forthe agents that are runningon the monitored system.

Agent Filters - Agent FilterRevisions

W95900G From the Agent Filters -WorkWith Agent Filtersform, click Find.

Set the filter levels for theagents.

Submit Job - WorkWithBatch Versions - AvailableVersions

W98305WA JD Edwards EnterpriseOneMenus, Submit Job.

Enter R95900 in the BatchApplication field and clickFind. Select the Reaper andclick Select.

Submit Job - WorkWithBatch Versions - AvailableVersions

W98305WA From the Submit Job - WorkWith Batch Versions -Available Versions, searchfor and select a batchapplication, and click Select.

Select Data Selection, DataSequencing, or both, andclick Submit.

Setting Global System OptionsAccess the Global Administration - Global Administration Revisions form.

URL Displays the URL.

User User ID used to access the PPMI servlet.

Password Password used to access the PPMI servlet.

Maximum Rows Limits the amount of data that can be inserted into the JD EdwardsEnterpriseOne Performance Monitor tables.

Last Updated User ID Specifies the last user to update the record.

Last Updated Date/Time Specifies the Utime when the record was last updated.

Setting System Definition DefaultsAccess the System Defaults - System Default Revisions form.

The System Defaults form enables you to set default values for all of the monitored systems. When a newsystems register with the monitoring system for the first time, the system adopts the default values thatyou have set.



Using the System Defaults form enables you to set global values for each monitored system rather thanmodifying the values for each system separately.

Archive Nothing, DeleteData, Archive Data

Choose an archive mode. The archive mode specifies how the archive programshould process the performance data stored in the monitoring database.

Allow Performance Trace Enables authorized users connected to this monitored system to start a specificperformance trace.

Agent Heartbeat Interval(sec)

Indicates the interval at which agents that do not have any performance datato report or that are in standby mode connect to the monitor servlet to benotified of any configuration changes. If agents post data to the monitoringsystem before this interval expires, they will be notified of any configurationchanges and the timer will be reset. The lower the number, the greater theresponsiveness of the agents to configuration changes, but the greater thenetwork traffic. This value cannot be set to zero.

PMU Timeout (days) Indicates the interval in which an open PMU is considered timed out. PMUtimeouts are measured in days. The PMU timeout value cannot be set to zero.After the specified interval, the system assumes that a PMU that has notcompleted encountered an error and should no longer be considered open. Thereaper program moves timed out PMUs from the current PMU tables to thehistory PMU tables and sets the status to Reaper Timed Out.

Agent PMU Sample Rate(1/X)

Enables you to reduce the amount of PMU data generated by monitoring just1 of every N server trips. Sampling does not affect PMUs initiated in aperformance trace.

Agent Buffering Interval(sec)

Specifies the rate (in seconds) at which an agent sends performance data tothe monitoring system. This value cannot be set to zero. A smaller intervaldecreases the delay between the time when the monitored system generatesperformance data and the time it is displayed on the monitoring system. Largerintervals enable more efficient transmission of performance data across thenetwork because the system can consolidate the data into packets. The largerthe interval, the greater the Agent Max Buffer size should be set.

Agent Max Buffer Size(bytes)

Determines the maximum size of the buffer containing performance data.This enables you to cap the amount of data being stored by the agent on themonitored system and the amount of data sent across your network. If thislimit is reached, the agent automatically discards new performance data untilthe current data has been posted to the monitor servlet. The agent posts analarm to the monitoring if the buffer size threshold is exceeded. The minimummust be 10240 bytes (10 KB).

Agent Filter Level Select a filter level stored in the system default table applied to monitoringsystem when no specific definition is applied. Each PMU definition has afilter level set to one of the following: standard, verbose, or debug. Markinga PMU as standard, verbose, or debug will tell JD Edwards EnterpriseOnePerformance Monitor system whether or not the PMU metrics should becaptured based on what level JD Edwards EnterpriseOne Performance Monitoris capturing data at. JD Edwards EnterpriseOne Performance Monitor filterlevel can be one of the following: standby (no metric data captured), standard(only standard PMUs captured), verbose (standard and verbose PMUscaptured), or debug (all PMUs captured).



Modifying System DefinitionsAccess the System Definitions - System Definition Revisions form.

A system refers to a particular monitored system. System definitions are created automatically when the firstagent of a monitored system registers with the monitoring system. The database name and GUID (a JDEdwards EnterpriseOne value used to uniquely identify a JD Edwards system) are provided by the agentduring its registration process.

This section describes the properties and configuration options for each monitored system.

System ID Identifies each monitored system. JD Edwards automatically generates thisvalue incrementally. System definitions are created automatically when thefirst agent of a monitored system registers with the monitoring system.

Database Name Identifies the name assigned to the database during installation, such asHPDEVORAP or HP9000. - - - FORM SPECIFIC HELP - - - The nameof the database running on the monitored system. The monitoring systemautomatically inserts this value when it recognizes and creates a monitoredsystem.

Description Identifies the description for JD Edwards EnterpriseOne Performance Monitorusage. - - - FORM SPECIFIC HELP - - - A description of the monitoringsystem to assist recognition. The default value is the database name.

UID Identifies the unique identifier for JD Edwards EnterpriseOne PerformanceMonitor defined systems. The monitoring system automatically inserts thisvalue when it recognizes and creates a monitored system.

Archive Mode Displays the archive mode you set specifies how the archive program shouldprocess the performance data stored in the monitoring database.

Allow User Trace Enables authorized users connected to this monitored system to start a specificperformance trace.

Agent Heartbeat Interval(sec)

Indicates the interval at which agents that do not have any performance datato report or that are in standby mode connect to the monitor servlet to benotified of any configuration changes. If agents post data to the monitoringsystem before this interval expires, they will be notified of any configurationchanges and the timer will be reset. The lower the number, the greater theresponsiveness of the agents to configuration changes, but the greater thenetwork traffic. This value cannot be set to zero.

PMU Timeout (days) Indicates the interval in which an open PMU is considered timed out. PMUtimeouts are measured in days. The PMU timeout value cannot be set to zero.After the specified interval, the system assumes that a PMU that has notcompleted encountered an error and should no longer be considered open. Thereaper program moves timed out PMUs from the current PMU tables to thehistory PMU tables and sets the status to Reaper Timed Out.

Agent Buffering Interval(sec)

Specifies the rate (in seconds) at which an agent sends performance datato the monitoring system.This value cannot be set to zero.A smaller interval decreases the delay between the time when the monitoredsystem generates performance data and the time it is displayed on the



monitoring system. Larger intervals enable more efficient transmission ofperformance data across the network because the system can consolidate thedata into packets. The larger the interval, the greater the Agent Max Buffersize should be set.

Agent PMU Sample Rate(1/X)

Enables you to reduce the amount of PMU data generated by monitoring just1 of every N server trips. Sampling does not affect PMUs initiated in aperformance trace.

Agent Max Buffer Size(bytes)

Determines the maximum size of the buffer containing performance data.This enables you to cap the amount of data being stored by the agent on themonitored system and the amount of data sent across your network. If thislimit is reached, the agent automatically discards new performance data untilthe current data has been posted to the monitor servlet. The agent posts analarm to the monitoring if the buffer size threshold is exceeded. The minimummust be 10240 bytes (10 KB).

Last Updated User ID Specifies the last user to update the record.

Last Updated Date/Time Specifies the Utime when the record was last updated.

Viewing Agent DefinitionsAccess the Agent Definitions - Agent Definition Revisions form.

Agent definitions enable you to view the details about the agents in monitored systems.

System ID Identifies each monitored system. JD Edwards EnterpriseOne automaticallygenerates this value incrementally. System definitions are createdautomatically when the first agent of a monitored system registers with themonitoring system.

Database Name Identifies the name of the database running on the monitored system. Themonitoring system automatically inserts this value when it recognizes andcreates a monitored system.

Agent ID Identifies an agent within a domain. This is automatically generated by themonitor the first time an agent registers.

Domain Monitor Displays as Yes or No. If yes, then this agent is responsible for sendingresource events for its host and domain to the monitor at the specified samplingrate for the monitored system.

Domain Name Identifies the name of the domain in which an agent operates.

Domain Type Indicates whether the domain is an application server, a web server, or aProcess Scheduler server domain.

Domain Host/Port Identifies the name or IP address of the server on which the domain residesincluding the port number to which the domain listens for requests.

Domain Directory Specifies the directory in which the domain is installed on the server.

Server Instance Specifies the collator server instance number.



Agent Inactive Select this box to make the agent inactive. If selected, the agent’s events andPMUs do not appear in JD Edwards EnterpriseOne Performance Monitorforms showing current information. You can still view information aboutevents and PMUs sent by inactive agents using the forms that display historicalinformation.

Setting Agent Filter OptionsAgent Filters - Agent Filter Revisions form.

Agent filters determine the amount of performance data that is generated and sent to the monitoringsystem. Depending on the situation, different levels of performance data may be needed to assist in yourperformance-related decisions. The levels range from no information to extremely detailed information.

Each type of PMU and event is associated with a filter level, which is the lowest level at which the systemgenerates performance data for that PMU or event.

System ID Identifies each monitored system. The JD Edwards EnterpriseOne systemautomatically generates this value incrementally. System definitions arecreated automatically when the first agent of a monitored system registerswith the monitoring system.

Database Name Identifies the name assigned to the database during installation, such asHPDEVORAP or HP9000. - - - FORM SPECIFIC HELP - - - The nameof the database running on the monitored system. The monitoring systemautomatically inserts this value when it recognizes and creates a monitoredsystem.

Description Identifies the description for JD Edwards EnterpriseOne Performance Monitorusage. - - - FORM SPECIFIC HELP - - - A description of the monitoringsystem to assist recognition. The default value is the database name

Last Update User ID Specifies the last user to update the record.

Last Update Date/Time Specifies the Utime when the record was last updated.

Scheduling the Reaper ProgramThe reaper process (R95900/XJDE0001) maintains the tables JD Edwards EnterpriseOne PerformanceMonitor uses to store performance data for current, real-time processing. It should be scheduled to run (viascheduler) periodically based on the filter level you are capturing data at and the load your enterprise is under.Performance of JD Edwards EnterpriseOne Performance Monitor will degrade if the tables JD EdwardsEnterpriseOne Performance Monitor uses to store performance data for current, real-time processing arenot maintained by the reaper process.

When JD Edwards EnterpriseOne Performance Monitor gets notified that a PMU has finished (it receives aSTOP for an open PMU), it:

• Flags the corresponding start and update rows in the current PMU table F95960 for deletion.• Inserts a row for the completed PMU in the F95961 table.



When the reaper program (R95900/XJDE0001) runs, it:

• Deletes all rows in current PMU table (F95960) that are flagged for deletion.

• Sets the status to timed out for expired PMUs in the current table.

Warning! If you do not schedule the reaper program to run often enough, the F95960 table will grow verylarge over time, and it may contain many old, open PMUs.


CHAPTER 5

Monitoring System Performance

This chapter provides an overview of system JD Edwards EnterpriseOne Performance Monitoring and discusses how to:

• Use the system performance home form.• View open PMUs.• View open PMU trees.• Monitor Individual User Performance.

System JD Edwards EnterpriseOne Performance MonitoringThis section contains an overview of monitoring system performance and lists the forms that are used tomonitor system performance.

Monitoring System PerformanceThe activities that are related to monitoring system performance are primarily for viewing and analyzing themost recent performance data that is received from agents in a monitored system.

Note. The information that is presented in the System Performance forms is as current as the last form refresh.

Note. The standard deviation is a statistic that tells you how tightly all the values that are used to compute theaverage are clustered around the average. Large standard deviations warn that the averages appearing in thechart are not a reliable indicator of response times that are experienced by individual users.


Monitoring System Performance Chapter 5

Forms Used to Modify System PerformanceForm Name FormID Navigation Usage

System Performance - WorkWith System Performance

W95910J JD Edwards EnterpriseOneMenus, JD EdwardsEnterpriseOneLifecycleTools, SystemAdministration Tools, JDEdwards EnterpriseOnePerformance Monitor,SystemMonitor, SystemPerformance

Search for performance datato analyze.

System Performance -System Performance

W95910E From the SystemPerformance - WorkWithSystem Performance form,select an item and clickSelect.

View performance indicesand daily averages. You canalso view open PMUs andcompleted PMUs by clickingthe corresponding links.

Open PMUs - Open PMUs W95910D JD Edwards EnterpriseOneMenus, JD EdwardsEnterpriseOneLifecycleTools, SystemAdministration Tools, JDEdwards EnterpriseOnePerformance Monitor,SystemMonitor, OpenPMUs.

Search for open PMUs.

Open PMU Trees - OpenPMU Trees

W95910G JD Edwards EnterpriseOneMenus, JD EdwardsEnterpriseOneLifecycleTools, SystemAdministration Tools, JDEdwards EnterpriseOnePerformance Monitor,SystemMonitor, OpenPMU Trees.

Search for open PMU trees.

Open PMU Trees - OpenPMU Trees Revision form.

W95910H From the PMU Trees -Open PMU Trees form,select an open PMU Treeand click Select.

View and modify openPMU Trees.

User Level Trace W95900M From the Agent FilterRevisions form, click theTools menu, then click UserLevel Trace.

Enter a user from whom youwant to collect data.

Viewing Open PMUsAccess the Open PMUs - Open PMUs form.


Chapter 5 Monitoring System Performance

An open PMU is a PMU that started but has not finished prior to an agent reporting performance metrics tothe monitor. Information regarding open PMUs are stored in the F95960 table. When the PMU finishes, thecollator flags the PMU for deletion and inserts a matching row into the F95961 table, which stores completedPMU data.

If an end user is reporting that a JD Edwards EnterpriseOne form is slow, use the Open PMU form to seewhere the request has stalled. Search for that user’s ID to see the current state of that user’s open PMUs.

Before you view current PMU details, you need to enter search criteria. If you do not specify criteria, the formdisplays all of the open PMUs for the selected system.

User ID Specifies the code that identifies a user profile.

PMU Set Categorizes meta-data transaction definitions into a set. Currently, onlyone definition set exists, and it is reserved for JD Edwards EnterpriseOnedevelopment.

PMU ID Specifies the identifier for a particular PMU you can monitor.

Performance Trace Identifies the name of the trace used to capture performance data that a usercan start and stop to capture specific results.

Context 1, 2, 3 Specifies values (1-3) that are common to the entire user request or a specifictier. PMU metrics contain data specific to an individual PMU.



Duration >=sec Identifies the duration in milliseconds that a single transaction took tocomplete.

Duration < (sec) Identifies the duration in milliseconds that a single transaction took tocomplete.

Note. Some of the metrics for various PMUs do not have values until the PMU finishes, so in some cases,metrics may appear with no values.

Monitoring Individual User PerformanceYou can monitor individual users’ system performance using the UserLevel Trace Application. You set theperformance data according to the user override of JD Edwards EnterpriseOne Performance Monitoring level.You can override JD Edwards EnterpriseOne Performance Monitoring level for one user at a time, howeveryou cannot override JD Edwards EnterpriseOne Performance Monitoring level for multiple users.

Access the User Level Trace form.


Standard, Verbose, Debug Select a filter value to view only the information returned of a specific filterlevel. Each meta-data definition has a filter level set to one of the following:Standard, verbose, or debug.


Monitoring System Performance Chapter 5

Viewing Open PMU TreesAccess the Open PMU Trees - Open PMU Trees form.

Every user request generates a set of PMUs that you can display as a tree. The PMU with the top instance ID isthe root of the tree and PMUs with no children are the leaves. A node represents each PMU or child PMU.Clicking a node reveals its detail, or the Select button on the parent nodes reveals its details.

A search may return multiple PMU trees. For example, if a user ID is shared across multiple users, or a singleuser has initiated multiple browser sessions, then more than one user request may be currently processing, andtherefore more than one PMU tree open.

The data that is related to open PMUs is dynamic because the system is currently processing the PMU.Therefore, the composition of trees, and even their presence, is likely to change each time you click Refresh.

Note. For each PMU in the tree, the duration value represents the period of time that has elapsed since themonitoring system received the start timestamp for each PMU. In some cases, the display may indicate that achild PMU is "older" than its parent. For example, if the application server sent PMU information before theweb server sent PMU information, the child PMUs that are running on the application server will display asmaller duration than the associated parent PMUs that are running on the web server.



CHAPTER 6

Analyzing Historical Performance Data

This chapter provides an overview of historical performance data and discusses how to view completed PMUs.

Historical Performance DataThis section provides an overview of historical performance data and lists the forms used to analyze historicalperformance data.

Historical Performance DataThe system stores historical data from the moment a PMU finishes processing or an event occurs. When thearchive program runs (R95900/XJDE0002), it either deletes the historical data or moves it to the archive tables.

Analyzing historical data can help you:

• Identify trends.By comparing historical data, you can spot upward and downward performance trends.

• Investigate past user complaints.For example, a user may complain that performance was slow during the previous week. You searchhistorical performance data to find the PMUs that were generated by the user at a specific time a week ago.

Forms Used to Analyze Historical Performance DataForm Name FormID Navigation Usage

Completed PMUs -Completed PMUs

W95920D JD Edwards EnterpriseOneMenus, JD EdwardsEnterpriseOneLifecycleTools, SystemAdministration Tools, JDEdwards EnterpriseOnePerformance Monitor,History, Completed PMUs

Enables you to search forand display completedPMUs.

Viewing Completed PMUsAccess the Completed PMUs - Completed PMUs form.


Analyzing Historical Performance Data Chapter 6

Entering Search CriteriaBefore you can view frinformation about completed PMUs, you need to enter criteria so that you can locate theappropriate completed PMUs.


PMU Set Categorizes meta-data transaction definitions into a set. Currently, onlyone definition set exists, and it is reserved for JD Edwards EnterpriseOnedevelopment.

PMU ID Specifies the identifier for a particular PMU you can monitor.


Context 1,2,3 Specifies values (1-3) that are common to the entire user request or a specifictier. PMU metrics contain data specific to an individual PMU.



Duration >= (ms) Identifies the duration in milliseconds that a single transaction took tocomplete.

Duration < (ms) Identifies the duration in milliseconds that a single transaction took tocomplete.

From Date/Time Identifies the date and time the monitor started the request. This is relatedto the duration of a PMU.

To Date/Time Identifies the date and time the monitor started the request. This is relatedto the duration of a PMU.

Working with Completed PMUsAt the bottom of the Completed PMUs - Completed PMUs form, the grid contains the information that isrelated to the PMUs that are retrieved by your search criteria.

You can access the Completed PMUs - PMU Details - C Call Object details form from a variety of JD EdwardsEnterpriseOne Performance Monitor forms, such as the Completed PMUs - Completed PMUs form and theOpen PMUs - Open PMUs form. You can also access it readily from trees. To access the form, you click thelink that is created from the PMU name.

You can access the PMU details form from a variety of JD Edwards EnterpriseOne Performance Monitorforms, such as the Completed PMUs form and the Open PMUs form. You can also access it readily from trees.To access the form, you click the link that is created from the PMU name.

The PMU Details form indicates:

• PMU ID and the PMU definition set to which it belongs.• Identification information.


Chapter 6 Analyzing Historical Performance Data

• Durations information, including metric values.• Context information.• Additional data.

The information that appears on the PMU Details form varies depending on the type of PMU that is displayed.All metrics are formatted according to information from the metric definition.

Completed PMUs

PMU Describes a unit of measure that reflects the execution of a section of code.

Duration (ms) Identifies the duration in milliseconds that a single transaction took tocomplete.

Tree View Displays completed PMUs in a tree view. Useful to show the hierarchy ofnested PMUs. Node description will be the concatenated PMU Label (alternatelanguage if applicable) and PMU duration. Only PMUs that are completedwill show. Only top level parents will be displayed at the first level underthe root. Children of the parents can be expanded. The PMU selected on thecalling form will be set to bold in the tree. The PMU will be shown in thehierarchical context it was created from. Therefore, the selected PMU can beat the parent level or the child level. All nodes can be selected and PMU Detail(W95920F) will be called to show all available information.

PMU Status Specifies the status the PMU of the PMU.


Monitor Start Identifies the date and time the monitor started the request. This is relatedto the duration of a PMU.

Context 1, 2, 3 Specifies values (1-3) that are common to the entire user request or a specifictier. PMU metrics contain data specific to an individual PMU.

Agent ID Identifies an agent within a domain. This is automatically generated by themonitor the first time an agent registers with it.


ContextThe Context tab reveals the context definition and value that is associated with each PMU in the grid. To viewthe details of the contexts in a PMU, examine the context and PMU definitions.

This Description column shows data for the additional description value that is part of the incoming PMU. Thedescription stores large character values and generally stores information that exceeds the 128–character limitof Metric 7 and the 254–character limit of the contexts.

MetricsThe Metrics tab presents the metric values for all of the metrics that are defined for each PMU in the grid.

Metric information appears in a raw format. The values reflect exactly what is stored in the database.


Analyzing Historical Performance Data Chapter 6

Additional DataThe Additional Data tab enables you to view textual information about the data being captured by the PMU.

Agent DetailsThe Agent details tab presents information about the agent from which the PMU was executed.

IdentificationThe Identification tab enables you to view specific identifications associated with the PMUs.

Completed PMU StatusA completed PMU can be assigned one of these statuses:

Status Description

Success The PMU finished successfully.

Failed The PMU finished unsuccessfully.

Abort Instrumentation code terminated a PMU due to an unexpectedcondition.

Unknown Assigned in situations when an agent closes a child PMU if thetop-level PMU closes out of sequence.

Timeout Instrumentation code timed out the PMU.

Reaper Timeout Long running PMU closed by the Reaper.

Admin Timeout An administrator manually closed the PMU. This is not currentlyimplemented.


CHAPTER 7

Evaluating JD Edwards EnterpriseOnePerformance Monitor Meta-Data

This chapter discusses JD Edwards EnterpriseOne Performance Monitor meta-data definitions and describes how to:

• Revise Metric definitions.

• Revise Event definitions

• Revise Context definitions.

• Revise PMU definitions.

Understanding JD Edwards EnterpriseOne PerformanceMonitor Meta-Data Definitions

JD Edwards EnterpriseOne Performance Monitor uses these meta-data definitions:

• Metrics.• Event Definitions.

• Contexts.• PMUs.

MetricsJD Edwards EnterpriseOne Performance Monitor agents send PMUs and events to the monitor. Each PMU andevent contains one or more metrics. Each metric has a unique identifier. Metric definitions are the buildingblocks for creating PMUs and events. PMUs and events comprise up to six numeric values and one stringmetric value. One metric definition can appear in multiple event and PMU definitions.

EventsEvents are not implemented for the 8.95 release of JD Edwards EnterpriseOne Performance Monitor. You canview and add them, however they are not functional.

Events are notifications containing performance metrics that are different from PMUs in that they are nothierarchical, and they do not have durations. JD Edwards EnterpriseOne has defined a set of event types, andeach type of event is reported at a specific location in the instrumented code.

Each event has:

• Type.• Instance identifier (a unique identifier for a specific event instance).


Evaluating JD Edwards EnterpriseOne Performance Monitor Meta-Data Chapter 7

• Timestamp.• Severity.• Metrics (such as CPU usage and memory allocation).

Event definitions group as many as seven metrics to measure the intended performance data. Some events donot have metrics.

ContextsA context definition applies only to PMU definitions. Contexts provide additional information so that PMUperformance data can be displayed and searched more effectively. For example, a context definition enablesyou to group and sort numeric values, such as an execute count, by form name. Contexts enable the system toassign the data to various elements such as forms, components, service calls, applications, business functions,event rules, and so on. Without contexts, you have only numeric data in no understandable grouping.

PMU metrics contain data that is specific to that PMU. Context values, on the other hand, are common tothe entire user request or a specific tier. The system uses contexts to "flatten" a PMU tree. For example, youdo not have to navigate up from a SQL PMU to an event rule PMU to see what application generated thatSQL statement.

PMUsA PMU is a unit of measure that reflects the execution of a section of code. The system starts and stops aPMU at specific code locations, and the system may update a PMU anytime between the start and stoptimes. JD Edwards EnterpriseOne has defined a set of PMU types, and each type of PMU corresponds to theinstrumentation at a specific code location, such as a SQL Execute in application or a business function call onthe JD Edwards EnterpriseOne server.

Each PMU includes:

• PMU Type.• Instance identifier (a unique identifier for a specific PMU instance).• Start time.• Stop time.• Status.• Metrics (such as number of SQL fetches).

A PMU represents a section of code that is bracketed by calls to an internal instrumentation API that signal thestart and stop of that logical unit of code.

PMU definitions group as many as seven metrics to measure the intended performance data. Some PMUs donot have metrics.


Chapter 7 Evaluating JD Edwards EnterpriseOne Performance Monitor Meta-Data

Forms Used to Evaluate JD Edwards EnterpriseOnePerformance Monitor Meta-Data

Form Name FormID Navigation UsageMetric Definitions - WorkWith Metric Definitions

W95905A JD Edwards EnterpriseOneMenus, JD EdwardsEnterpriseOneLifecycleTools, SystemAdministration Tools, JDEdwards EnterpriseOnePerformance Monitor,Administration, Meta-Data,Metric Definitions

Search for metricdefinitions.

Metric Definitions - MetricDefinition Revisions

W95905C OnMetric Definitions- WorkWith MetricDefinitions, after retrievingmetric definitions, select ametric definition you want torevise and click Select.

View and modify metricdefinitions and opt to displaythe metric value alone, orwith its label.

Metric Definitions - MetricReference

W95905E OnMetric Definitions -Metric Definition Revisions,click Metric References.

Review metric references.

Context Definitions - WorkWith Context Definitions

W95905D JD Edwards EnterpriseOneMenus, JD EdwardsEnterpriseOneLifecycleTools, SystemAdministration Tools, JDEdwards EnterpriseOnePerformance Monitor,Administration, Meta-Data,Context Definitions

Search for ContextDefinitions.

Context Definitions- Context DefinitionRevisions

W95905F On Context Definitions- WorkWith ContextDefinitions, after retrievingcontext definitions, select acontext definition you wantto revise and click Select.

View and modify contextdefinitions and accessthe Context Definitions -Context Reference form.

Context Definitions -Context Reference

W95905E On the Context Definitions- Context DefinitionRevisions form, clickContext Reference.

View reference data forContext Definitions.

PMUDefinitions - WorkWith PMUDefinitions

W95905J JD Edwards EnterpriseOneMenus, JD EdwardsEnterpriseOneLifecycleTools, SystemAdministration Tools, JDEdwards EnterpriseOnePerformance Monitor,Administration, Meta-Data,PMUDefinitions

Search for and select PMUDefinitions.



Page Name Definition Name Navigation UsagePMUDefinitions - PMUDefinition Revisions

W95905G On PMUDefinitions - WorkWith PMUDefinitions, afterretrieving PMU definitions,select a PMU definitionyou want to revise andclick Select.

View and revise PMUDefinitions.

Event Definitions - WorkWith Event Definitions

W95905K JD Edwards EnterpriseOneMenus, JD EdwardsEnterpriseOneLifecycleTools, SystemAdministration Tools, JDEdwards EnterpriseOnePerformance Monitor,Administration, Meta-Data,Event Definitions

Search for and select EventDefinitions.

Event Definitions - EventDefinition Revisions

W95905M On Event Definitions - WorkWith Event Definitions, afterretrieving Event definitions,select an Event definitionand click Select.

View and revise EventDefinitions.

Revising Metric DefinitionsThis section discusses the attributes of a metric definition.

Access the Metric Definitions - Metric Definition Revisions form.

Note. Only JD Edwards EnterpriseOne should modify metric definitions. Modifying metric definitions atyour site could cause unexpected results.

Metric ID Identifies Metric meta-data definitions.

Metric Type Indicates the type of metric meta-data definition (Counter, Gauge, NumID,StrID).

• Counter: A counter metric is designed to enable sums of values from aspecific time range to be calculated.

Examples are bytes printed and records written. The values can also beaveraged, maximums and minimums can be calculated, and other kinds ofstatistical calculations can be performed

• Gauge: A gauge metric is designed to be used instead of a counter when it isnot meaningful to calculate sum values that are recorded within a time range.

Calculations that are performed on gauge metrics include: average, standarddeviation, median, maximum value, and minimum value. For example, theamount of memory that is used on a server is a gauge metric type. If youmeasure the amount of memory that is used over 20 transactions in atime range, the sum of the memory that is used is not necessarily useful.However, the average, median, and standard deviation provide insightinto usage per transaction.



• Numeric Identifier: A numeric identifier is a numeric value that is used asan identifier, not as a measurement value.Creating sums and averages, or manipulating these values in any arithmeticway is not meaningful. For example, message numbers and error codes arenumeric identifier metric types.

• String: Used with metric definition attributes that need to be represented astext, not a numeric value.Arithmetic operations are not performed on string metric types. Forexample, descriptive attributes, such as site path, file name, and so on, arestring metric types.

Metric Label Identifies the description for JD Edwards EnterpriseOne Performance Monitorusage. - - - FORM SPECIFIC HELP - - - Displays a more detailed descriptionof the purpose of the metric.

Description Identifies the description for JD Edwards EnterpriseOne Performance Monitorusage. - - - FORM SPECIFIC HELP - - - Displays a more detailed descriptionof the purpose of the metric.

Metric Multiplier Identifies the multiplier used for metric definition meta-data.

Display Metric as anInteger

Indicates where metric meta-data definition is an integer or double value.This is a Yes/No flag.

Metric Display Enables you to determine what appears on the forms displaying a metric. Theseoptions are mutually exclusive. Select Display Value to display the actualvalue. Select Display Label to display the label describing the metric value. Ifusing Display Label select the UDC you wish to use as Display Labels.

Metric References Calls References (W95905E). Shows all the places this metric is used withinPMU and Event Definitions.

Revising Event DefinitionsThis section discusses the attributes of an Event definition. Events are not implemented for the 8.95 release ofJD Edwards EnterpriseOne Performance Monitor. You can view and add them, however they are not functional.

Access the Event Definitions - Event Definition Revisions form.

Event Definition Set Categorizes meta-data event definitions into a set. Currently, only onedefinition set exists, and it is reserved for JD Edwards EnterpriseOnedevelopment.

Set Description

Event ID Identifies a particular event you can monitor.

Event Label Identifies the label for Event meta-data definitions.

Event Description Describes JD Edwards EnterpriseOne Performance Monitor usage. - - - FORMSPECIFIC HELP - - - Displays a more detailed description of the purposeof the Event.



Additional Label Identifies the label for PMU additional data.


Context Tab

Context ID 1–3 Identifies context values 1–3.

Display Content 1–3 Flag to indicate whether or not context value 1 should be displayed whenshowing PMU data.

Metric Tab

Metric ID 1–7 Identifies meta-data for definitions 1–7 used for giving context to metricvalues.

Display Metric 1–7 Flag to indicates whether or not context value 1 should be displayed whenshowing PMU data.

Revising Context DefinitionsThis section discusses the attributes of a context definition.

Access the Context Definitions - Context Definition Revisions form.

Context Identifier Identifies Context meta-data definitions.

Context Label Identifies the context label appears on any form that displays a context todescribe the value.

Description Displays a more detailed description of the purpose of the context.

Context Reference Calls References (W95905E). Shows all the places this metric is used withinPMU and Event Definitions

Revising PMU DefinitionsThis section describes the attributes of PMU definition.

Access the PMU Definitions - PMU Definition Revisions form.

PMU Definition Set Categorizes metadata event definitions into a set. Currently, only one definitionset exists, and it is reserved for JD Edwards EnterpriseOne development.

Set Description Describes a definition set.



PMU ID Identifies a particular PMU that you can monitor.

PMU Label Identifies the label for PMU additional data.

PMU Description Describes a PMU metadata definition.

Additional Data Label Identifies the label for PMU additional data.


Contexts 1, 2, 3 Identifier to context value 1 through 3.

Display Content 1, 2, 3 Flag to indicate whether or not context value should be displayed whenshowing PMU data.

Metric ID 1, 2, 3, 4, 5, 6, 7 Identifies metric values 1, 2, 3, 4, 5, 6, 7.

Display Metric ID Flag to indicate whether or not metric value should be displayed whenshowing PMU data.


APPENDIX A

PMU Definition Reference

This appendix contains the structure of each PMU that is defined in the JD Edwards EnterpriseOne system.

Note. Currently, only one PMU set definition exists; set 2.

PMU 100 C Call ObjectPMU 100 has these identification attributes.

Attribute Value

ID 100

Label C Call Object

Description Measure total execution time when jdeCallObject is called.

Filter LevelPMU 100 has a filter level of Standard.

Contexts

Context Value Description

1 BSFN Information Application/Form/BSFN/BSFNVersion/Previous BSFN

2 Login Information Host/Port/User/Environment/Role

3 Other Information Module/BSFN Library/PID /Thread

Metrics

Metric Value Description

1 BSFN Level Business Function Level injdeCallObject

2 BLC Specs Retrieval Time in ms Total retrieval time for BLC specs

3 DSTemplate Spec Retrieval Time Total retrieval time for DSTemplatespecs


PMU Definition Reference Appendix A


4 Call BSFN Retry Number Of Retry to Call BSFN

5 Not Used Not Used

6 Not Used Not Used

7 Additional Information BSFN Author/Overridelocation/Commit Mode

Additional LabelCall Object Error/Server Status.

PMU 101 Java Call ObjectPMU 101 has these identification attributes.

Attribute Value

ID 101

Label Java Call Object

Description Java Call Object Execution Time


Contexts


1 BSFN Information Application/Form/BSFN/BSFNVersion/Previous BSFN

2 Login Information Host/Port/User/Environment/Role

3 Other Information Module/BSFN Library/PID /Thread

Metrics


1 BSFN DS Flattening Time Java Call Object BSFN DS FlatteningTime


Appendix A PMU Definition Reference


2 BSFN Inflating Time Java Call Object BSFN DS InflatingTime

3 BSFN Plug-in Execution Time Total Execution Time For BusinessFunction Plug-in

4 Serialized Object Time Retrieval time for DSTMPL&JDEBLC serialized object time

5 Retry Total Number Of Retry

6 Additional Information BSFN Author/Overridelocation/Commit Mode

7 Not Used Not Used

Additional LabelCallObject/BSFN Error List

PMU 200 JDB/JDBj DML APIsPMU 200 has these identification attributes.

Attribute Value

ID 200

Label JDB/JDBj DMLAPIs

Description E1PM_JDB_DML_DEBUG

Filter LevelPMU 102 has a filter level of Debug.

Contexts


1 Object Object Name

2 Data Source Data Source Name



Metrics


1 DB Request DB request Type

2 Commit Mode DB transaction mode

3 Return Code Function return code

4 Number of Records Number of Returned Records(Commit/Rollback Excluded)

5 Not Used Not Used

6 Not Used Not Used

7 Transaction ID Transaction ID

Additional LabelJDB/JDBj

PMU 201 SQL DML APIsPMU 201 has these identification attributes.

Attribute Value

ID 201

Label SQL DMLAPIs

Description E1PM_SQL_DML_DEBUG

Filter LevelPMU 106 has a filter level of Debug.

Contexts


1 Database Name Database Name

2 Host Name Database Host Name

3 Database Type Database Type



Metrics


1 Transaction Mode Size of HTML Response in bytes.

2 Not Used Not Used

3 Not Used Not Used

4 Not Used Not Used

5 Not Used Not Used

6 Not Used Not Used

7 Transaction ID Transaction ID

Additional LabelJDB/JDBj

PMU 300 Execute FormPMU 108 has these identification attributes.

Attribute Value

ID 300

Label Execute Form

Description User Session logout, expiration, timeout, or error


Contexts


1 User/Environment/Role User, Environment, and Role

2 Application Name Application Name

3 Form Name Form Name



Metrics


1 Reason Reason for session termination.

2 Response Code HTTP Response Code.

7 User ID User ID of user logging on.

Additional LabelN/A

PMU 301 Event RulesPMU 301 has these identification attributes.

Attribute Value

ID 301

Label Event Rules

Description Event Rules

Filter LevelPMU 109 has a filter level of Verbose.

Contexts


1 Event Name Web server Session ID.

2 Object ID Client IP Address.

Metrics


1 Grid Row Grid Row

2 Grid Column Grid Column

Additional LabelN/A



PMU 302 Fetch ProcessPMU 113 has these identification attributes.

Attribute Value

ID 302

Label Fetch Process

Description Fetch Process

Filter LevelPMU 113 has a filter level of Verbose.

Contexts


1 Business View Business View

Metrics


1 Bypass Signon? Boolean - logging in with a guest ID?

Additional LabelN/A

PMU 303 OK ProcessPMU 303 has these identification attributes.

Attribute Value

ID 303

Label OK Button

Description OK Button Process




Contexts


1 TP Usage Transaction Processing Usage

Metrics


0 Not Used Not Used

Additional LabelN/A

PMU 304 Asynch OK ProcessPMU 304 has these identification attributes.

Attribute Value

ID 304

Label Asynch OK Process

Description Asynch OK Button Process


Contexts


1 User/Environment/Role User, Environment, and Role

2 Application Name Application Name

3 Form Name Form Name

Metrics


1 Queue Elements Queue Elements

2 Not Used Not Used




3 Not Used Not Used

4 Not Used Not Used

5 Not Used Not Used

6 Not Used Not Used

7 TP Usage Transaction Processing Usage

Additional LabelN/A


APPENDIX B

Understanding JD Edwards EnterpriseOnePerformance Monitor Architecture

This appendix discusses JD Edwards EnterpriseOne Performance Monitor Architecture.

JD Edwards EnterpriseOne Performance MonitorArchitecture Components

This section discusses the major components of JD Edwards EnterpriseOne Performance Monitor Architecture,which are:

• JD Edwards EnterpriseOne application server.• JD Edwards EnterpriseOne web server (also known as JAS, Java application server)• JD Edwards EnterpriseOne monitoring server• User interface• Database host• Data Flow

JD Edwards EnterpriseOne Application ServerThis section discusses the components of the application server.

AppServer C-AgentAll instrumented C processes on the JD Edwards EnterpriseOne application server are linked to the JDEdwards EnterpriseOne PerfMon DLL to call into instrumentation API’s. Instrumentation API’s sendperformance data to the PerfMon Java Adapter on the Monitoring Server using JD Edwards EnterpriseOneProprietary JDENT communication protocol.

Archive Batch ProcessThis component is a batch process scheduled to periodically move data from current and history table toarchive tables and also can be configured to remove data from all tables to manage disk space. This processuses JD Edwards EnterpriseOne proprietary JDB API’s to access and modify database tables.

Reaper Batch ProcessThis component is a batch process scheduled to periodically move data from current tables to history tablesfor completed transactions and also to delete flagged rows in current tables. This process uses JD EdwardsEnterpriseOne proprietary JDB API’s to access and modify database tables.


Understanding JD Edwards EnterpriseOne Performance Monitor Architecture Appendix B

JD Edwards EnterpriseOne JAVA Application ServerThis section discusses the components of the JAS server.

JAS Runtime EngineThis component is used to display HTML pages for JD Edwards EnterpriseOne PerfMon User Interface.Retrieves meta-data from database and creates HTML Pages to send back to user browser over HTTP. It alsochanges Agent configuration in the database and sends a notification to the PPMI Servlet so the changes canget to the Agents. Jas runtime engine uses JD Edwards EnterpriseOne proprietary JDBj API’s to access andmodify database tables.

JD Edwards EnterpriseOne Monitoring ServerEnterprise One Monitoring Server uses the same components as the Enterprise solution which are: PPMIServlet, Monitor Servlet and Data Collator. Changes have been made to these components for integrationwith JD Edwards EnterpriseOne environment. For example these components have been changed to use JDEdwards EnterpriseOne JDBj mechanism for database operations. No changes have been made in the way 3rdpart solutions will register and retrieve data from the Monitoring Server. One new component (JD EdwardsEnterpriseOne PerfMon Java Adapter) has been added to act as a bridge between JD Edwards EnterpriseOneapplication server and Monitor Server. This adapter receives the performance data from the Enterprise Server(through JDENet messages) and converts them to HTTP and sends them to the Monitor Servlet by calling intoexisting PerfMon Java API’s.

PerfMon Java AdapterPerfMon Java Adapter acts as a bridge between JD Edwards EnterpriseOne application server and theMonitoring Server. C processes on the application Server (also known as C-Agents) send the performancedata to the PerfMon Java Adapter using the JD Edwards EnterpriseOne JDENet protocol. PerfMon JavaAdapter calls into Java API’s and passes the performance data to the monitor Servlet which runs on theMonitor Server. Note that the Java API’s called by the PerfMon Java Adapter are the same API’s that arecalled in JAS Runtime Engine instrumented code.

Monitor ServletThe Monitor Servlet receives the registration notification from all the Agents and updates the database withthe registration information. It also receives the performance data from all the Agents in the environmentand hands the data to all registered PPMI clients. In JD Edwards EnterpriseOne solution the “out of the box”PPMI client for performance data is the JD Edwards EnterpriseOne data collator whish is another componentof the Monitor Server. Each time the Monitor Server receives the performance data from an Agent, it sendsback the Agent configuration as the response to the Agents. This is how the Agents will be notified from anyAgent configuration changes. The Monitor Servlet uses the JD Edwards EnterpriseOne proprietary JDBj API’sto access and modify database tables.

Data Collator ServletThe Data Collator registers itself to the PPMI Servlet as a PPMI Client Proxy to show interest in receivingperformance data for JD Edwards EnterpriseOne environment. By receiving performance data from theMonitor Servlet, the data collator will update the database accordingly: If the data is indicating the end of anopen transaction, then the data collator will add the data to the history table and remove all the correspondingdata for this transaction from the current table. Otherwise the data is added to the current table. The DataCollator uses the JD Edwards EnterpriseOne proprietary JDBj API’s to access and modify database tables.


Appendix B Understanding JD Edwards EnterpriseOne Performance Monitor Architecture

PPMI ServletThe PPMI Servlet manages PPMI clients. PPMI Client is a component that registers to the PPMI Servlet toreceive JD Edwards EnterpriseOne performance data. When a client registers, the PPMI Servlet will notify theMonitor Servlet of the newly registered client and the Monitor Servlet will make sure that the performance datawill be sent to the client. In JD Edwards EnterpriseOne Performance Monitor architecture, the JD EdwardsEnterpriseOne Data Collator is the default PPMI client for the system. The PPMI Servlet also receives theAgent configuration change messages from the JD Edwards EnterpriseOne JAS Server. This happens when aJD Edwards EnterpriseOne administrator changes the configuration for a group pf Agents using the JDEdwards EnterpriseOne PerfMon User Interface. By receiving the notification, the PPMI Servlet reads the newAgent configuration from the database and updates the Agent configuration in the memory. This configurationin the memory is the one that is sent back to all the Agents by the Monitor Servlet. The PPMI Servlet uses theJD Edwards EnterpriseOne proprietary JDBj API’s to access and modify database tables.

Data FlowThis section describes how data flows through JD Edwards EnterpriseOne Performance Monitor.

Sending Performance Data to Monitor ServerArrows 1

On the JD Edwards EnterpriseOne application server the C-Agent calls into C instrumentation API to send theperformance data to the JD Edwards EnterpriseOne PerfMon Java Adapter on the Monitoring Server.

Arrow 2

On the Monitoring Server the Java Adapter calls into Java Agent API’s to send the performance data tothe Monitor Servlet component of the Monitoring Server. The Java Agent API’s use a separate thread perAgent to communicate with the Monitoring Server.

Arrow 3

The JAS Runtime Engine calls into Java Agent API’s to send the performance data to the Monitor Servletcomponent of the Monitoring Server. The Java Agent API’s use a separate thread per Agent to communicatewith the Monitoring Server.

Saving performance Data in databaseArrow 4

Inside the Monitor Server, the Monitor Servlet receives the performance data from Java Agents in HTTPformat and converts the data to XML before sending it to the Data Collator. The data collator componentof the Monitor Server calls into JD Edwards EnterpriseOne JDBj API’s to save performance data to the JDEdwards EnterpriseOne PerfMon database.

Sending configuration changes to the AgentsArrows 5,6,7,8 and 9

The administrator uses the JD Edwards EnterpriseOne PerfMon User Interface to change Agent configurationfor a group of Agents. (arrow number 5).

The JAS Runtime engine changes the Agent configuration data in JD Edwards EnterpriseOne PerfMondatabase (arrow number 6).

The JAS Runtime engine sends a notification message (in HTTP format) to the PPMI Servlet component ofthe Monitor Server (Arrow number 7).


Understanding JD Edwards EnterpriseOne Performance Monitor Architecture Appendix B

The PPMI Servlet reads the new Agent configuration from PerfMon database (arrow number 8).

The PPMI Server updates the Agent configuration data in the memory, where it will be accessed by theMonitor Servlet. The Monitor Servlets sends the new Agent configuration to all the Agents the next time itcommunicates with the Agents (arrow number 19).

On the JAS Server no additional work is needed. The PerfMon Java Adaptor sends a JDENet messagecontaining the new Agent configuration to all the C-Agents processes on the AppServer (arrow number 10).The Java Adapter manages a C-Agent process table where it keeps the host name and port number (amongothers) of all the C-Agent processes registered to the Java Adapter.

Archiving data in databaseArrow 11

A scheduled batch process will archive data in the database. The Archive batch process can be scheduled torun periodically to either move the performance data from database tables to the Archive tables or to removethem from Archive tables to free disk space on the database host. This batch process uses the EnterpriseOneproprietary JDB API’s to access data in the database.

Reaping data in databaseArrow 15

A scheduled batch process will move timed out data from current tables to history tables. This batch processuses the EnterpriseOne proprietary JDB API’s to access data in the database.


Glossary of JD Edwards EnterpriseOne Terms

Accessor Methods/Assessors Java methods to “get” and “set” the elements of a value object or other source file.

activity rule The criteria by which an object progresses from one given point to the next in a flow.

add mode A condition of a form that enables users to input data.

Advanced Planning Agent(APAg)

A JD Edwards EnterpriseOne tool that can be used to extract, transform, and loadenterprise data. APAg supports access to data sources in the form of rational databases,flat file format, and other data or message encoding, such as XML.

alternate currency A currency that is different from the domestic currency (when dealing with adomestic-only transaction) or the domestic and foreign currency of a transaction.

In JD Edwards EnterpriseOne Financial Management, alternate currency processingenables you to enter receipts and payments in a currency other than the one in whichthey were issued.

Application Server Software that provides the business logic for an application program in a distributedenvironment. The servers can be Oracle Application Server (OAS) or WebSphereApplication Server (WAS).

as if processing A process that enables you to view currency amounts as if they were entered in acurrency different from the domestic and foreign currency of the transaction.

as of processing A process that is run as of a specific point in time to summarize transactions up to thatdate. For example, you can run various JD Edwards EnterpriseOne reports as of aspecific date to determine balances and amounts of accounts, units, and so on as ofthat date.

Auto Commit Transaction A database connection through which all database operations are immediately writtento the database.

back-to-back process A process in JD Edwards EnterpriseOne Supply Management that contains the samekeys that are used in another process.

batch processing A process of transferring records from a third-party system to JD EdwardsEnterpriseOne.

In JD Edwards EnterpriseOne Financial Management, batch processing enablesyou to transfer invoices and vouchers that are entered in a system other than JDEdwards EnterpriseOne to JD Edwards EnterpriseOne Accounts Receivable and JDEdwards EnterpriseOne Accounts Payable, respectively. In addition, you can transferaddress book information, including customer and supplier records, to JD EdwardsEnterpriseOne.

batch server A server that is designated for running batch processing requests. A batch servertypically does not contain a database nor does it run interactive applications.

batch-of-one immediate A transaction method that enables a client application to perform work on a clientworkstation, then submit the work all at once to a server application for furtherprocessing. As a batch process is running on the server, the client application cancontinue performing other tasks.

See also direct connect and store-and-forward.

best practices Non-mandatory guidelines that help the developer make better design decisions.


Glossary

BPEL Abbreviation for Business Process Execution Language, a standard web servicesorchestration language, which enables you to assemble discrete services into anend-to-end process flow.

BPEL PM Abbreviation for Business Process Execution Language Process Manager, acomprehensive infrastructure for creating, deploying, and managing BPEL businessprocesses.

Build Configuration File Configurable settings in a text file that are used by a build program to generate ANTscripts. ANT is a software tool used for automating build processes. These scriptsbuild published business services.

build engineer An actor that is responsible for building, mastering, and packaging artifacts. Somebuild engineers are responsible for building application artifacts, and some areresponsible for building foundation artifacts.

Build Program AWIN32 executable that reads build configuration files and generates an ANT scriptfor building published business services.

business analyst An actor that determines if and why an EnterpriseOne business service needs tobe developed.

business function A named set of user-created, reusable business rules and logs that can be calledthrough event rules. Business functions can run a transaction or a subset of atransaction (check inventory, issue work orders, and so on). Business functions alsocontain the application programming interfaces (APIs) that enable them to be calledfrom a form, a database trigger, or a non-JD Edwards EnterpriseOne application.Business functions can be combined with other business functions, forms, event rules,and other components to make up an application. Business functions can be createdthrough event rules or third-generation languages, such as C. Examples of businessfunctions include Credit Check and Item Availability.

business function event rule See named event rule (NER).

business service EnterpriseOne business logic written in Java. A business service is a collection ofone or more artifacts. Unless specified otherwise, a business service implies both apublished business service and business service.

business service artifacts Source files, descriptors, and so on that are managed for business service developmentand are needed for the business service build process.

business service class method Amethod that accesses resources provided by the business service framework.

business service configurationfiles

Configuration files include, but are not limited to, interop.ini, JDBj.ini, andjdelog.properties.

business service cross reference A key and value data pair used during orchestration. Collectively refers to both thecode and the key cross reference in theWSG/XPI based system.

business service cross-referenceutilities

Utility services installed in a BPEL/ESB environment that are used to access JDEdwards EnterpriseOne orchestration cross-reference data.

business service developmentenvironment

A framework needed by an integration developer to develop and manage businessservices.

business services developmenttool

Otherwise known as JDeveloper.

business service EnterpriseOneobject

A collection of artifacts managed by EnterpriseOne LCM tools. Named andrepresented within EnterpriseOne LCM similarly to other EnterpriseOne objects liketables, views, forms, and so on.


Glossary

business service framework Parts of the business service foundation that are specifically for supporting businessservice development.

business service payload An object that is passed between an enterprise server and a business services server.The business service payload contains the input to the business service when passed tothe business services server. The business service payload contains the results from thebusiness service when passed to the Enterprise Server. In the case of notifications, thereturn business service payload contains the acknowledgement.

business service property Key value data pairs used to control the behavior or functionality of business services.

Business Service PropertyAdmin Tool

An EnterpriseOne application for developers and administrators to manage businessservice property records.

business service propertybusiness service group

A classification for business service property at the business service level. Thisis generally a business service name. A business service level contains one or morebusiness service property groups. Each business service property group may containzero or more business service property records.

business service propertycategorization

Away to categorize business service properties. These properties are categorizedby business service.

business service property key A unique name that identifies the business service property globally in the system.

business service propertyutilities

A utility API used in business service development to access EnterpriseOne businessservice property data.

business service property value A value for a business service property.

business service repository A source management system, for example ClearCase, where business service artifactsand build files are stored. Or, a physical directory in network.

business services server The physical machine where the business services are located. Business services arerun on an application server instance.

business services source file orbusiness service class

One type of business service artifact. A text file with the .java file type written to becompiled by a Java compiler.

business service value objecttemplate

The structural representation of a business service value object used in a C-businessfunction.

Business Service Value ObjectTemplate Utility

A utility used to create a business service value object template from a businessservice value object.

business services server artifact The object to be deployed to the business services server.

business view Ameans for selecting specific columns from one or more JD Edwards EnterpriseOneapplication tables whose data is used in an application or report. A business viewdoes not select specific rows, nor does it contain any actual data. It is strictly a viewthrough which you can manipulate data.

central objects merge A process that blends a customer’s modifications to the objects in a current releasewith objects in a new release.

central server A server that has been designated to contain the originally installed version of thesoftware (central objects) for deployment to client computers. In a typical JDEdwards EnterpriseOne installation, the software is loaded on to one machine—thecentral server. Then, copies of the software are pushed out or downloaded to variousworkstations attached to it. That way, if the software is altered or corrupted through itsuse on workstations, an original set of objects (central objects) is always availableon the central server.


Glossary

charts Tables of information in JD Edwards EnterpriseOne that appear on forms in thesoftware.

check-in repository A repository for developers to check in and check out business service artifacts. Thereare multiple check-in repositories. Each can be used for a different purpose (forexample, development, production, testing, and so on).

connector Component-based interoperability model that enables third-party applications andJD Edwards EnterpriseOne to share logic and data. The JD Edwards EnterpriseOneconnector architecture includes Java and COM connectors.

contra/clearing account A general ledger account in JD Edwards EnterpriseOne Financial Management thatis used by the system to offset (balance) journal entries. For example, you can use acontra/clearing account to balance the entries created by allocations in JD EdwardsEnterpriseOne Financial Management.

Control TableWorkbench An application that, during the InstallationWorkbench processing, runs the batchapplications for the planned merges that update the data dictionary, user-definedcodes, menus, and user override tables.

control tables merge A process that blends a customer’s modifications to the control tables with the data thataccompanies a new release.

correlation data The data used to tie HTTP responses with requests that consist of business servicename and method.

cost assignment The process in JD Edwards EnterpriseOne Advanced Cost Accounting of tracing orallocating resources to activities or cost objects.

cost component In JD Edwards EnterpriseOneManufacturing, an element of an item’s cost (forexample, material, labor, or overhead).

credentials A valid set of JD Edwards EnterpriseOne username/password/environment/role,EnterpriseOne session, or EnterpriseOne token.

cross-reference utility services Utility services installed in a BPEL/ESB environment that access EnterpriseOnecross-reference data.

cross segment edit A logic statement that establishes the relationship between configured item segments.Cross segment edits are used to prevent ordering of configurations that cannot beproduced.

currency restatement The process of converting amounts from one currency into another currency, generallyfor reporting purposes. You can use the currency restatement process, for example,when many currencies must be restated into a single currency for consolidatedreporting.

cXML A protocol used to facilitate communication between business documents andprocurement applications, and between e-commerce hubs and suppliers.

database credentials A valid database username/password.

database server A server in a local area network that maintains a database and performs searchesfor client computers.

Data SourceWorkbench An application that, during the InstallationWorkbench process, copies all data sourcesthat are defined in the installation plan from the Data Source Master and Table andData Source Sizing tables in the Planner data source to the system-release number datasource. It also updates the Data Source Plan detail record to reflect completion.

date pattern A calendar that represents the beginning date for the fiscal year and the ending date foreach period in that year in standard and 52-period accounting.


Glossary

denominated-in currency The company currency in which financial reports are based.

deployment artifacts Artifacts that are needed for the deployment process, such as servers, ports, and such.

deployment server A server that is used to install, maintain, and distribute software to one or moreenterprise servers and client workstations.

detail information Information that relates to individual lines in JD Edwards EnterpriseOne transactions(for example, voucher pay items and sales order detail lines).

direct connect A transaction method in which a client application communicates interactively anddirectly with a server application.

See also batch-of-one immediate and store-and-forward.

Do Not Translate (DNT) A type of data source that must exist on the iSeries because of BLOB restrictions.

dual pricing The process of providing prices for goods and services in two currencies.

duplicate published businessservices authorization records

Two published business services authorization records with the same useridentification information and published business services identification information.

embedded application serverinstance

An OC4J instance started by and running wholly within JDeveloper.

edit code A code that indicates how a specific value for a report or a form should appear or beformatted. The default edit codes that pertain to reporting require particular attentionbecause they account for a substantial amount of information.

edit mode A condition of a form that enables users to change data.

edit rule Amethod used for formatting and validating user entries against a predefined ruleor set of rules.

Electronic Data Interchange(EDI)

An interoperability model that enables paperless computer-to-computer exchange ofbusiness transactions between JD Edwards EnterpriseOne and third-party systems.Companies that use EDI must have translator software to convert data from the EDIstandard format to the formats of their computer systems.

embedded event rule An event rule that is specific to a particular table or application. Examples includeform-to-form calls, hiding a field based on a processing option value, and calling abusiness function. Contrast with the business function event rule.

EmployeeWork Center A central location for sending and receiving all JD Edwards EnterpriseOne messages(system and user generated), regardless of the originating application or user. Eachuser has a mailbox that contains workflow and other messages, including ActiveMessages.

enterprise server A server that contains the database and the logic for JD Edwards EnterpriseOne.

Enterprise Service Bus (ESB) Middleware infrastructure products or technologies based on web services standardsthat enable a service-oriented architecture using an event-driven and XML-basedmessaging framework (the bus).

EnterpriseOne administrator An actor responsible for the EnterpriseOne administration system.

EnterpriseOne credentials A user ID, password, environment, and role used to validate a user of EnterpriseOne.

EnterpriseOne object A reusable piece of code that is used to build applications. Object types include tables,forms, business functions, data dictionary items, batch processes, business views,event rules, versions, data structures, and media objects.


Glossary

EnterpriseOne developmentclient

Historically called “fat client,” a collection of installed EnterpriseOne componentsrequired to develop EnterpriseOne artifacts, including the Microsoft Windows clientand design tools.

EnterpriseOne extension A JDeveloper component (plug-in) specific to EnterpriseOne. A JDeveloper wizardis a specific example of an extension.

EnterpriseOne process A software process that enables JD Edwards EnterpriseOne clients and serversto handle processing requests and run transactions. A client runs one process,and servers can have multiple instances of a process. JD Edwards EnterpriseOneprocesses can also be dedicated to specific tasks (for example, workflow messagesand data replication) to ensure that critical processes don’t have to wait if the serveris particularly busy.

EnterpriseOne resource Any EnterpriseOne table, metadata, business function, dictionary information, or otherinformation restricted to authorized users.

EnvironmentWorkbench An application that, during the InstallationWorkbench process, copies theenvironment information and Object Configuration Manager tables for eachenvironment from the Planner data source to the system-release number data source. Italso updates the Environment Plan detail record to reflect completion.

escalation monitor A batch process that monitors pending requests or activities and restarts or forwardsthem to the next step or user after they have been inactive for a specified amount oftime.

event rule A logic statement that instructs the system to perform one or more operations basedon an activity that can occur in a specific application, such as entering a form orexiting a field.

explicit transaction Transaction used by a business service developer to explicitly control the type (auto ormanual) and the scope of transaction boundaries within a business service.

exposed method or value object Published business service source files or parts of published business service sourcefiles that are part of the published interface. These are part of the contract with thecustomer.

facility An entity within a business for which you want to track costs. For example, a facilitymight be a warehouse location, job, project, work center, or branch/plant. A facility issometimes referred to as a “business unit.”

fast path A command prompt that enables the user to move quickly among menus andapplications by using specific commands.

file server A server that stores files to be accessed by other computers on the network. Unlikea disk server, which appears to the user as a remote disk drive, a file server is asophisticated device that not only stores files, but also manages them and maintainsorder as network users request files and make changes to these files.

final mode The report processing mode of a processing mode of a program that updates orcreates data records.

foundation A framework that must be accessible for execution of business services at runtime.This includes, but is not limited to, the Java Connector and JDBj.

FTP server A server that responds to requests for files via file transfer protocol.

header information Information at the beginning of a table or form. Header information is used to identifyor provide control information for the group of records that follows.

HTTP Adapter A generic set of services that are used to do the basic HTTP operations, such as GET,POST, PUT, DELETE, TRACE, HEAD, and OPTIONS with the provided URL.


Glossary

instantiate A Java term meaning “to create.” When a class is instantiated, a new instance iscreated.

integration developer The user of the system who develops, runs, and debugs the EnterpriseOne businessservices. The integration developer uses the EnterpriseOne business services todevelop these components.

integration point (IP) The business logic in previous implementations of EnterpriseOne that exposes adocument level interface. This type of logic used to be called XBPs. In EnterpriseOne8.11, IPs are implemented in Web Services Gateway powered by webMethods.

integration server A server that facilitates interaction between diverse operating systems and applicationsacross internal and external networked computer systems.

integrity test A process used to supplement a company’s internal balancing procedures by locatingand reporting balancing problems and data inconsistencies.

interface table See Z table.

internal method or value object Business service source files or parts of business service source files that are not part ofthe published interface. These could be private or protected methods. These could bevalue objects not used in published methods.

interoperability model Amethod for third-party systems to connect to or access JD Edwards EnterpriseOne.

in-your-face-error In JD Edwards EnterpriseOne, a form-level property which, when enabled, causes thetext of application errors to appear on the form.

IServer service This internet server service resides on the web server and is used to speed up deliveryof the Java class files from the database to the client.

jargon An alternative data dictionary item description that JD Edwards EnterpriseOne appearsbased on the product code of the current object.

Java application server A component-based server that resides in the middle-tier of a server-centricarchitecture. This server provides middleware services for security and statemaintenance, along with data access and persistence.

JDBNET A database driver that enables heterogeneous servers to access each other’s data.

JDEBASE DatabaseMiddleware

A JD Edwards EnterpriseOne proprietary database middleware package that providesplatform-independent APIs, along with client-to-server access.

JDECallObject An API used by business functions to invoke other business functions.

jde.ini A JD Edwards EnterpriseOne file (or member for iSeries) that provides the runtimesettings required for JD Edwards EnterpriseOne initialization. Specific versions of thefile or member must reside on every machine running JD Edwards EnterpriseOne.This includes workstations and servers.

JDEIPC Communications programming tools used by server code to regulate access to thesame data in multiprocess environments, communicate and coordinate betweenprocesses, and create new processes.

jde.log The main diagnostic log file of JD Edwards EnterpriseOne. This file is always locatedin the root directory on the primary drive and contains status and error messages fromthe startup and operation of JD Edwards EnterpriseOne.

JDENET A JD Edwards EnterpriseOne proprietary communications middleware package. Thispackage is a peer-to-peer, message-based, socket-based, multiprocess communicationsmiddleware solution. It handles client-to-server and server-to-server communicationsfor all JD Edwards EnterpriseOne supported platforms.

JDeveloper Project An artifact that JDeveloper uses to categorize and compile source files.


Glossary

JDeveloperWorkspace An artifact that JDeveloper uses to organize project files. It contains one or moreproject files.

JMSQueue A Java Messaging service queue used for point-to-point messaging.

listener service A listener that listens for XMLmessages over HTTP.

local repository A developer’s local development environment that is used to store business serviceartifacts.

local standalone BPEL/ESBserver

A standalone BPEL/ESB server that is not installed within an application server.

LocationWorkbench An application that, during the InstallationWorkbench process, copies all locationsthat are defined in the installation plan from the Location Master table in the Plannerdata source to the system data source.

logic server A server in a distributed network that provides the business logic for an applicationprogram. In a typical configuration, pristine objects are replicated on to the logicserver from the central server. The logic server, in conjunction with workstations,actually performs the processing required when JD Edwards EnterpriseOne softwareruns.

MailMergeWorkbench An application that merges Microsoft Word 6.0 (or higher) word-processingdocuments with JD Edwards EnterpriseOne records to automatically print businessdocuments. You can use MailMergeWorkbench to print documents, such as formletters about verification of employment.

Manual Commit transaction A database connection where all database operations delay writing to the databaseuntil a call to commit is made.

master business function (MBF) An interactive master file that serves as a central location for adding, changing, andupdating information in a database. Master business functions pass informationbetween data entry forms and the appropriate tables. These master functions provide acommon set of functions that contain all of the necessary default and editing rules forrelated programs. MBFs contain logic that ensures the integrity of adding, updating,and deleting information from databases.

master table See published table.

matching document A document associated with an original document to complete or change a transaction.For example, in JD Edwards EnterpriseOne Financial Management, a receipt is thematching document of an invoice, and a payment is the matching document of avoucher.

media storage object Files that use one of the following naming conventions that are not organized intotable format: Gxxx, xxxGT, or GTxxx.

message center A central location for sending and receiving all JD Edwards EnterpriseOne messages(system and user generated), regardless of the originating application or user.

messaging adapter An interoperability model that enables third-party systems to connect to JD EdwardsEnterpriseOne to exchange information through the use of messaging queues.

messaging server A server that handles messages that are sent for use by other programs using amessaging API. Messaging servers typically employ a middleware program to performtheir functions.

Middle-Tier BPEL/ESB Server A BPEL/ESB server that is installed within an application server.

Monitoring Application An EnterpriseOne tool provided for an administrator to get statistical information forvarious EntepriseOne servers, reset statistics, and set notifications.


Glossary

named event rule (NER) Encapsulated, reusable business logic created using event rules, rather that Cprogramming. NERs are also called business function event rules. NERs can be reusedin multiple places by multiple programs. This modularity lends itself to streamlining,reusability of code, and less work.

nota fiscal In Brazil, a legal document that must accompany all commercial transactions for taxpurposes and that must contain information required by tax regulations.

nota fiscal factura In Brazil, a nota fiscal with invoice information.

See also nota fiscal.

Object ConfigurationManager(OCM)

In JD Edwards EnterpriseOne, the object request broker and control center forthe runtime environment. OCM keeps track of the runtime locations for businessfunctions, data, and batch applications. When one of these objects is called, OCMdirects access to it using defaults and overrides for a given environment and user.

Object Librarian A repository of all versions, applications, and business functions reusable in buildingapplications. Object Librarian provides check-out and check-in capabilities fordevelopers, and it controls the creation, modification, and use of JD EdwardsEnterpriseOne objects. Object Librarian supports multiple environments (such asproduction and development) and enables objects to be easily moved from oneenvironment to another.

Object Librarian merge A process that blends any modifications to the Object Librarian in a previous releaseinto the Object Librarian in a new release.

Open Data Access (ODA) An interoperability model that enables you to use SQL statements to extract JDEdwards EnterpriseOne data for summarization and report generation.

Output Stream Access (OSA) An interoperability model that enables you to set up an interface for JD EdwardsEnterpriseOne to pass data to another software package, such as Microsoft Excel,for processing.

package JD Edwards EnterpriseOne objects are installed to workstations in packages from thedeployment server. A package can be compared to a bill of material or kit that indicatesthe necessary objects for that workstation and where on the deployment server theinstallation program can find them. It is point-in-time snapshot of the central objectson the deployment server.

package build A software application that facilitates the deployment of software changes and newapplications to existing users. Additionally, in JD Edwards EnterpriseOne, a packagebuild can be a compiled version of the software. When you upgrade your version of theERP software, for example, you are said to take a package build.

Consider the following context: “Also, do not transfer business functions into theproduction path code until you are ready to deploy, because a global build of businessfunctions done during a package build will automatically include the new functions.”The process of creating a package build is often referred to, as it is in this example,simply as “a package build.”

package location The directory structure location for the package and its set of replicated objects.This is usually \\deployment server\release\path_code\package\package name. Thesubdirectories under this path are where the replicated objects for the package areplaced. This is also referred to as where the package is built or stored.

PackageWorkbench An application that, during the InstallationWorkbench process, transfers the packageinformation tables from the Planner data source to the system-release number datasource. It also updates the Package Plan detail record to reflect completion.

Pathcode Directory The specific portion of the file system on the EnterpriseOne development client whereEnterpriseOne development artifacts are stored.


Glossary

patterns General repeatable solutions to a commonly occurring problem in software design. Forbusiness service development, the focus is on the object relationships and interactions.For orchestrations, the focus is on the integration patterns (for example, synchronousand asynchronous request/response, publish, notify, and receive/reply).

planning family Ameans of grouping end items whose similarity of design and manufacture facilitatesbeing planned in aggregate.

preference profile The ability to define default values for specified fields for a user-defined hierarchy ofitems, item groups, customers, and customer groups.

print server The interface between a printer and a network that enables network clients to connectto the printer and send their print jobs to it. A print server can be a computer, separatehardware device, or even hardware that resides inside of the printer itself.

pristine environment A JD Edwards EnterpriseOne environment used to test unaltered objects with JDEdwards EnterpriseOne demonstration data or for training classes. You must have thisenvironment so that you can compare pristine objects that you modify.

processing option A data structure that enables users to supply parameters that regulate the running ofa batch program or report. For example, you can use processing options to specifydefault values for certain fields, to determine how information appears or is printed,to specify date ranges, to supply runtime values that regulate program execution,and so on.

production environment A JD Edwards EnterpriseOne environment in which users operate EnterpriseOnesoftware.

production-grade file server A file server that has been quality assurance tested and commercialized and that isusually provided in conjunction with user support services.

Production Published BusinessServicesWeb Service

Published business services web service deployed to a production application server.

program temporary fix (PTF) A representation of changes to JD Edwards EnterpriseOne software that yourorganization receives on magnetic tapes or disks.

project In JD Edwards EnterpriseOne, a virtual container for objects being developed inObject Management Workbench.

promotion path The designated path for advancing objects or projects in a workflow. The followingis the normal promotion cycle (path):

11>21>26>28>38>01

In this path, 11 equals new project pending review, 21 equals programming, 26 equalsQA test/review, 28 equals QA test/review complete, 38 equals in production, 01 equalscomplete. During the normal project promotion cycle, developers check objects outof and into the development path code and then promote them to the prototype pathcode. The objects are then moved to the productions path code before declaringthem complete.

proxy server A server that acts as a barrier between a workstation and the internet so that theenterprise can ensure security, administrative control, and caching service.

published business service EnterpriseOne service level logic and interface. A classification of a publishedbusiness service indicating the intention to be exposed to external (non-EnterpriseOne)systems.

published business serviceidentification information

Information about a published business service used to determine relevantauthorization records. Published business services + method name, published businessservices, or *ALL.


Glossary

published business serviceweb service

Published business services components packaged as J2EEWeb Service (namely, aJ2EE EAR file that contains business service classes, business service foundation,configuration files, and web service artifacts).

published table Also called a master table, this is the central copy to be replicated to other machines.Residing on the publisher machine, the F98DRPUB table identifies all of the publishedtables and their associated publishers in the enterprise.

publisher The server that is responsible for the published table. The F98DRPUB table identifiesall of the published tables and their associated publishers in the enterprise.

pull replication One of the JD Edwards EnterpriseOne methods for replicating data to individualworkstations. Such machines are set up as pull subscribers using JD EdwardsEnterpriseOne data replication tools. The only time that pull subscribers are notified ofchanges, updates, and deletions is when they request such information. The requestis in the form of a message that is sent, usually at startup, from the pull subscriber tothe server machine that stores the F98DRPCN table.

QBE An abbreviation for query by example. In JD Edwards EnterpriseOne, the QBE line isthe top line on a detail area that is used for filtering data.

real-time event Amessage triggered from EnterpriseOne application logic that is intended for externalsystems to consume.

refresh A function used to modify JD Edwards EnterpriseOne software, or subset of it, suchas a table or business data, so that it functions at a new release or cumulative updatelevel, such as B73.2 or B73.2.1.

replication server A server that is responsible for replicating central objects to client machines.

Rt-Addressing Unique data identifying a browser session that initiates the business services callrequest host/port user session.

rules Mandatory guidelines that are not enforced by tooling, but must be followed in order toaccomplish the desired results and to meet specified standards.

quote order In JD Edwards Procurement and Subcontract Management, a request from a supplierfor item and price information from which you can create a purchase order.

In JD Edwards Sales Order Management, item and price information for a customerwho has not yet committed to a sales order.

secure by default A security model that assumes that a user does not have permission to execute anobject unless there is a specific record indicating such permissions.

Secure Socket Layer (SSL) A security protocol that provides communication privacy. SSL enables client andserver applications to communicate in a way that is designed to prevent eavesdropping,tampering, and message forgery.

SEI implementation A Java class that implements the methods that declare in a Service Endpoint Interface(SEI).

selection Found on JD Edwards EnterpriseOne menus, a selection represents functions that youcan access from a menu. To make a selection, type the associated number in theSelection field and press Enter.

serialize The process of converting an object or data into a format for storage or transmissionacross a network connection link with the ability to reconstruct the original data orobjects when needed.

ServerWorkbench An application that, during the InstallationWorkbench process, copies the serverconfiguration files from the Planner data source to the system-release number


Glossary

data source. The application also updates the Server Plan detail record to reflectcompletion.

Service Endpoint Interface(SEI)

A Java interface that declares the methods that a client can invoke on the service.

SOA Abbreviation for Service Oriented Architecture.

softcoding A coding technique that enables an administrator to manipulate site-specific variablesthat affect the execution of a given process.

source repository A repository for HTTP adapter and listener service development environment artifacts.

spot rate An exchange rate entered at the transaction level. This rate overrides the exchange ratethat is set up between two currencies.

Specification merge Amerge that comprises three merges: Object Librarian merge, Versions List merge,and Central Objects merge. The merges blend customer modifications with data thataccompanies a new release.

specification A complete description of a JD Edwards EnterpriseOne object. Each object has its ownspecification, or name, which is used to build applications.

Specification Table MergeWorkbench

An application that, during the InstallationWorkbench process, runs the batchapplications that update the specification tables.

SSL Certificate A special message signed by a certificate authority that contains the name of a user andthat user’s public key in such a way that anyone can "verify" that the message wassigned by no one other than the certification authority and thereby develop trust inthe user’s public key.

store-and-forward The mode of processing that enables users who are disconnected from a server to entertransactions and then later connect to the server to upload those transactions.

subscriber table Table F98DRSUB, which is stored on the publisher server with the F98DRPUB tableand identifies all of the subscriber machines for each published table.

superclass An inheritance concept of the Java language where a class is an instance of something,but is also more specific. “Tree” might be the superclass of “Oak” and “Elm,” forexample.

supplemental data Any type of information that is not maintained in a master file. Supplemental data isusually additional information about employees, applicants, requisitions, and jobs(such as an employee’s job skills, degrees, or foreign languages spoken). You can trackvirtually any type of information that your organization needs.

For example, in addition to the data in the standard master tables (the Address BookMaster, Customer Master, and Supplier Master tables), you can maintain otherkinds of data in separate, generic databases. These generic databases enable astandard approach to entering and maintaining supplemental data across JD EdwardsEnterpriseOne systems.

table access management(TAM)

The JD Edwards EnterpriseOne component that handles the storage and retrievalof use-defined data. TAM stores information, such as data dictionary definitions;application and report specifications; event rules; table definitions; business functioninput parameters and library information; and data structure definitions for runningapplications, reports, and business functions.

Table ConversionWorkbench An interoperability model that enables the exchange of information between JDEdwards EnterpriseOne and third-party systems using non-JD Edwards EnterpriseOnetables.


Glossary

table conversion An interoperability model that enables the exchange of information between JDEdwards EnterpriseOne and third-party systems using non-JD Edwards EnterpriseOnetables.

table event rules Logic that is attached to database triggers that runs whenever the action specified bythe trigger occurs against the table. Although JD Edwards EnterpriseOne enablesevent rules to be attached to application events, this functionality is applicationspecific. Table event rules provide embedded logic at the table level.

terminal server A server that enables terminals, microcomputers, and other devices to connect to anetwork or host computer or to devices attached to that particular computer.

three-tier processing The task of entering, reviewing and approving, and posting batches of transactions inJD Edwards EnterpriseOne.

three-way voucher match In JD Edwards Procurement and Subcontract Management, the process of comparingreceipt information to supplier’s invoices to create vouchers. In a three-way match,you use the receipt records to create vouchers.

transaction processing (TP)monitor

Amonitor that controls data transfer between local and remote terminals and theapplications that originated them. TP monitors also protect data integrity in thedistributed environment and may include programs that validate data and formatterminal screens.

transaction processing method Amethod related to the management of a manual commit transaction boundary (forexample, start, commit, rollback, and cancel).

transaction set An electronic business transaction (electronic data interchange standard document)made up of segments.

trigger One of several events specific to data dictionary items. You can attach logic to a datadictionary item that the system processes automatically when the event occurs.

triggering event A specific workflow event that requires special action or has defined consequencesor resulting actions.

two-way authentication An authentication mechanism in which both client and server authenticate themselvesby providing the SSL certificates to each other.

two-way voucher match In JD Edwards Procurement and Subcontract Management, the process of comparingpurchase order detail lines to the suppliers’ invoices to create vouchers. You do notrecord receipt information.

user identification information User ID, role, or *public.

User Overrides merge Adds new user override records into a customer’s user override table.

value object A specific type of source file that holds input or output data, much like a data structurepasses data. Value objects can be exposed (used in a published business service) orinternal, and input or output. They are comprised of simple and complex elements andaccessories to those elements.

variance In JD Edwards Capital Asset Management, the difference between revenue generatedby a piece of equipment and costs incurred by the equipment.

In JD Edwards EnterpriseOne Project Costing and JD Edwards EnterpriseOneManufacturing, the difference between two methods of costing the same item (forexample, the difference between the frozen standard cost and the current cost isan engineering variance). Frozen standard costs come from the Cost Componentstable, and the current costs are calculated using the current bill of material, routing,and overhead rates.


Glossary

versioning a published businessservice

Adding additional functionality/interfaces to the published business services withoutmodifying the existing functionality/interfaces.

Version List merge The Versions List merge preserves any non-XJDE and non-ZJDE versionspecifications for objects that are valid in the new release, as well as their processingoptions data.

visual assist Forms that can be invoked from a control via a trigger to assist the user in determiningwhat data belongs in the control.

vocabulary override An alternate description for a data dictionary item that appears on a specific JDEdwards EnterpriseOne form or report.

wchar_t An internal type of a wide character. It is used for writing portable programs forinternational markets.

web application server Aweb server that enables web applications to exchange data with the back-endsystems and databases used in eBusiness transactions.

web server A server that sends information as requested by a browser, using the TCP/IP set ofprotocols. A web server can do more than just coordination of requests from browsers;it can do anything a normal server can do, such as house applications or data. Anycomputer can be turned into a web server by installing server software and connectingthe machine to the internet.

Web Service DescriptionLanguage (WSDL)

An XML format for describing network services.

Web Service InspectionLanguage (WSIL)

An XML format for assisting in the inspection of a site for available services and a setof rules for how inspection-related information should be made.

web service proxy foundation Foundation classes for web service proxy that must be included in a business serviceserver artifact for web service consumption onWAS.

web service softcoding record An XML document that contains values that are used to configure a web service proxy.This document identifies the endpoint and conditionally includes security information.

web service softcoding template An XML document that provides the structure for a soft coded record.

Where clause The portion of a database operation that specifies which records the database operationwill affect.

Windows terminal server Amultiuser server that enables terminals and minimally configured computers todisplayWindows applications even if they are not capable of runningWindowssoftware themselves. All client processing is performed centrally at theWindowsterminal server and only display, keystroke, and mouse commands are transmitted overthe network to the client terminal device.

wizard A type of JDeveloper extension used to walk the user through a series of steps.

workbench A program that enables users to access a group of related programs from a single entrypoint. Typically, the programs that you access from a workbench are used to completea large business process. For example, you use the JD Edwards EnterpriseOnePayroll Cycle Workbench (P07210) to access all of the programs that the system usesto process payroll, print payments, create payroll reports, create journal entries,and update payroll history. Examples of JD Edwards EnterpriseOne workbenchesinclude Service Management Workbench (P90CD020), Line SchedulingWorkbench(P3153), PlanningWorkbench (P13700), Auditor’s Workbench (P09E115), andPayroll Cycle Workbench.

work day calendar In JD Edwards EnterpriseOneManufacturing, a calendar that is used in planningfunctions that consecutively lists only working days so that component and work orderscheduling can be done based on the actual number of work days available. A work


Glossary

day calendar is sometimes referred to as planning calendar, manufacturing calendar, orshop floor calendar.

workflow The automation of a business process, in whole or in part, during which documents,information, or tasks are passed from one participant to another for action, accordingto a set of procedural rules.

workgroup server A server that usually contains subsets of data replicated from a master network server.A workgroup server does not perform application or batch processing.

XAPI events A service that uses system calls to capture JD Edwards EnterpriseOne transactionsas they occur and then calls third-party software, end users, and other JD EdwardsEnterpriseOne systems that have requested notification when the specifiedtransactions occur to return a response.

XMLCallObject An interoperability capability that enables you to call business functions.

XMLDispatch An interoperability capability that provides a single point of entry for all XMLdocuments coming into JD Edwards EnterpriseOne for responses.

XMLList An interoperability capability that enables you to request and receive JD EdwardsEnterpriseOne database information in chunks.

XML Service An interoperability capability that enables you to request events from one JD EdwardsEnterpriseOne system and receive a response from another JD Edwards EnterpriseOnesystem.

XMLTransaction An interoperability capability that enables you to use a predefined transaction type tosend information to or request information from JD Edwards EnterpriseOne. XMLtransaction uses interface table functionality.

XMLTransaction Service(XTS)

Transforms an XML document that is not in the JD Edwards EnterpriseOne formatinto an XML document that can be processed by JD Edwards EnterpriseOne. XTSthen transforms the response back to the request originator XML format.

Z event A service that uses interface table functionality to capture JD Edwards EnterpriseOnetransactions and provide notification to third-party software, end users, and other JDEdwards EnterpriseOne systems that have requested to be notified when certaintransactions occur.

Z table Aworking table where non-JD Edwards EnterpriseOne information can be stored andthen processed into JD Edwards EnterpriseOne. Z tables also can be used to retrieveJD Edwards EnterpriseOne data. Z tables are also known as interface tables.

Z transaction Third-party data that is properly formatted in interface tables for updating to theJD Edwards EnterpriseOne database.


Glossary


Index

Aadditional documentation xAgent Definitions form 28Agent Filters form 29agentsconnecting to monitors 13domain resource agents 6monitoring definitions 28process instrumentation agents 6setting buffer sizes 28setting event sampling rates 27setting filtering 29understanding 6understanding monitor URLs 18

Application Engine programsPSPM_ARCHIVE 27, 35reaper program 27See Also reaper program

application fundamentals ixapplication server domainsmonitored system elements 6

application serversmonitoring system elements 8setting up for monitored systems 19

archivingsetting archive mode 27understanding performance historydata 35

authenticationunderstanding PMU 113 53

Bbufferssetting for performance data 28

Cchartsmonitoring performance data 10, 31

comments, submitting xivcommon fields xivCompleted PMUs form 35contact information xivcontextsPMU 100 47

PMU 101 48PMU 102 49PMU 106 50PMU 108 51PMU 109 52PMU 113 53PMU 114 53PMU 115 54understanding 40understanding definitions 44

counter metrics 42cross-references xiiiCustomer Connection website x

Ddatabasessetting up for monitored systems 17setting up monitoring databases 11understanding JD Edwards applicationdatabases 6understanding monitoring systemdatabases 7

deviation, standard, See standard deviationdocumentationdownloading xrelated xupdates x

domain resource agents 6domainsapplication server 6See Also application servers

domain resource agents 6identifying for agents 28identifying for PMU requests 37

downloading documentation x

Eeventsunderstanding 9

Ffilteringsetting for agents 29setting for PMUs 45, 47


Index

Ggauge metrics 42Global Administration form 25gridsmonitoring performance data 10

Iimplementation guidesordering x

instrumentationprocess instrumentation agents 6understanding 8understanding PMUs 40

JJD Edwards EnterpriseOneevents 9, 11See Also events

PMUs 8See Also PMUs

system database (PTSYS) 7, 11JD Edwards EnterpriseOne PerformanceMonitoradministering 23agents 6See Also agents

analyzing historical performancedata 35configuring 11elements 4instrumentation 8See Also instrumentation

metadata 39See Also metadata

monitored systems 6See Also monitored systems

monitoring data 10monitoring system performance 31monitoring systems 7See Also monitoring systems

performance metrics coverage 10setting global system options 25setting up 11sharing performance data with third-partysystems 9understanding 3

JD Edwards EnterpriseOne PerformanceMonitor Integration (PPMI), See PPMI

JD Edwards Multi-Platform Installerprogram 13

Llabelsviewing for contexts 44viewing for metrics 43, 45viewing for PMUs 45, 47

Mmetadatacontexts 44See Also contexts

metrics 42See Also metrics

PMUs 44See Also PMUs

understanding 39metricsmodifying definitions 42PMU 100 47PMU 101 48PMU 102 49PMU 106 50PMU 108 51PMU 109 52PMU 113 53PMU 114 53PMU 115 54selecting for PMUs 45understanding 39understanding definitions 42

monitor servletsidentifying 18

monitored systemsdefining 27enabling required elements 17setting up application servers 19setting up databases 17setting up Process Scheduler servers 20setting up web servers 18specifying monitor URLs 18understanding 5, 6understanding application servers 6understanding databases 6understanding web server 7

monitoring systemsenabling required elements 11setting archive mode 27


Index

setting up monitoring databases 11setting up web servers 13understanding 5, 7understanding application servers 8understanding databases 7understanding Process Schedulerservers 8

Multi-Platform Installer program 13

Nnotes xiiinotificationsevents 9See Also events

notifying monitor servlets ofconfiguration changes 28

numeric identifier metrics 43

OOpen PMU Trees form 34Open PMUs form 32

PPeopleCode, typographicalconventions xiiperformance measurement units (PMUs),See PMUsPerformance Trace Consolelaunching 27

PMUsentering search criteria 36monitoring completed 35, 36monitoring open PMU trees 34monitoring open PMUs 32monitoring within tree context 38PMU 100 47PMU 101 48PMU 102 49PMU 106 50PMU 108 51PMU 109 52PMU 113 53PMU 114 53PMU 115 54setting sampling rates 28setting timeouts 27understanding 8, 40understanding completed PMUstatus 38

understanding definitions 44PPMIspecifying passwords 25specifying user IDs 25understanding 9

PPMI servletsaccessing 25

prerequisites ixprocess instrumentation agents 6Process Scheduler serversmonitoring systems 8setting up for monitored systems 20

production monitoring systemsusing the PTSYS database 11

PSPM_ARCHIVE program 27, 35PSPM_REAPER program, See reaperprogramPSPPMSRV processesregistering servlets 13using PMUs 29

PTSYS database 7, 11

Rreaper programReaper Timeout status 38scheduling 29understanding PMU timeouts 27

refreshes, formSystem Performance formsinformation 31

registrationagents 28servlets 13

related documentation x

SsamplingPMUs with enabled sampling 47setting for agent events 27setting for agent PMUs 28

searchesPMUs 36

serversapplication 6See Also application servers

web 7See Also web servers

servletsrunning on web servers 13


Index

Simple Object Access Protocol (SOAP) 9SOAP 9standard deviationunderstanding 31

statusmonitoring for PMUs 37understanding for completed PMUs 38

string metrics 43suggestions, submitting xivSystem Definitions form 27

Ttablesmaintaining performance data tables 29moving timed-out PMUs 27

third-party systems, sharing performancedata 9timeoutssetting for PMUs 27understanding PMU timeoutstatuses 38

tracingenabling for monitored systems 27

trees, PMU 34, 38typographical conventions xii

UURLsspecifying monitor URLs 18

usersidentifying for PMUs 37monitoring for PMU trees 34

Vvisual cues xii

Wwarnings xiiiweb serversmonitored system elements 7setting up for monitored systems 18setting up for monitoring systems 13


JD Edwards EnterpriseOne Tools 8.98 Performance … … · JD Edwards EnterpriseOne Tools 8.98...

Documents

Transcript of JD Edwards EnterpriseOne Tools 8.98 Performance … … · JD Edwards EnterpriseOne Tools 8.98...