Guide to JD Edwards templates - static.helpsystems.com · • Infor M3 (Movex) • Infor XA • Infor XE • Misys • Misys Midas Plus • SAP •Maxava •Quick/EDD • Vision Replication

Guide to JD Edwards templates

CopyrightCopyright Halcyon - A Division of HelpSystems. All rights reserved.

This document is intended as a guide to the JD Edwards monitoring templates available withHalcyon software products for IBM i, Windows, AIX and Linux.

This documentation contains Halcyon proprietary and confidential information and may not bedisclosed, used, or copied without the prior consent of Halcyon Software, or as set forth in theapplicable license agreement. Users are solely responsible for the proper use of the softwareand the application of the results obtained.

Although Halcyon Software has tested the software and reviewed the documentation, the solewarranty for the software may be found in the applicable license agreement between HalcyonSoftware and the user.

Publication Revision: May 2016

Overview Halcyon Templates are designed to provide the same level of monitoring across a number ofsimilar devices by applying a set of user-defined filters with a single-click. This greatly reducesset-up time and ensures all systems are covered by at least a basic level of monitoring.

Should you need to make a system-wide change at a later date, a single update covers allsystems using the template.

Halcyon IBM i Templates also are available for the following specialized environments:

• Infor M3 (Movex)

• Infor XA

• Infor XE

• Misys

• Misys Midas Plus

• SAP

• Maxava

• Quick/EDD

• Vision Replication

• Vision iTERA Availability

C H A P T E R

CHAPTER 1INSTALLATION

If you already use any of Halcyon's Level 1 to 4 software suites then followthese instructions to install templates to a customized environment on the IBM i.

If you do not currently use Halcyon's tools in your JD Edwards environment butwish to have more information, an on-line demonstration or a free trial thenplease see the list of contacts on the back page of this guide.

Installation of Customized EnvironmentFollow these instructions to install templates to a customized environment.

1 Install the Halcyon solution, using the appropriate installation guide.

2 Once successfully installed, log into the environment to which you wish to apply the customized template, for example, HALPROD/HALCYON.

3 From the command line run ENDMON and press F4. Follow the prompts to complete the ending of the monitors.

Note: The installation of the customized environment fails if the monitors are not stopped.

4 From the command line type CSTENV and press F4.

5 Type the required authorization code for the template you wish to apply and press Enter.

I n s t a l l a t i o n 1-1

Figure 1.1 Entering the customization code

Note: Each customized environment requires an authorization code.

Please contact [email protected] or your local Halcyon reseller for details on how to obtain this code.

The Customized environment is now installed.

6 From the main menu of your Halcyon solution, select option 5=Work withRules. The template rules applicable to the customized environment that youinstalled can be found in the listed queue and rule groups. Default actionschedules are installed and additionally, where appropriate, changes tosystem defaults may also be made.

1- 2 H a l c y o n T e m p l a t e s

C H A P T E R

CHAPTER 2JD EDWARDS CUSTOMIZATIONTEMPLATES

Oracle's JD Edwards EnterpriseOne® is an integrated applications suite ofcomprehensive enterprise resource planning software. Halcyon templates canbe applied to both JD Edwards EnterpriseOne and World® solutions.

In most cases, the templates supplied can be used immediately uponcompletion of installation, but there may be instances where you need tochange rule properties to match those of your own environment. This can bedone by taking option 2=Change against the rule and making the requiredchanges. Similarly, should you require multiple rules for different messagequeues or devices and so on you can use option 3=Copy against the rule andthen make the required amendments.

ActionsUnless otherwise specified, all template rules are implemented with a defaultaction schedule which sends an alert message to your local console (option10=Message Console from the main menu). Should you wish to amend thisoption, take option 2=Change against the action within the rule and make theamendments as required.

Note: Please refer to the user reference guide for your Halcyon solution for details of actions that may be applied to rules.

J D E d w a r d s c u s t o m i z a t i o n t e m p l a t e s 2-3

Message Queue Rules

QHST System History Log Message QueueThis rule group contains three JDE rules.

JDE: Profile JDE disabledThis rule checks for message CPF1393, signifying that the user profile JDE isdisabled, being received in message file QCPFMSG.This rule runs 24/7.

JDE: Profile JDEINSTAL disabledThis rule checks for message CPF1393, signifying that the user profileJDEINSTAL is disabled, being received in message file QCPFMSG.This ruleruns 24/7.

JDE: Profile JDEGRP disabledThis rule checks for message CPF1393, signifying that the user profile JDEGRP is disabled, being received in message file QCPFMSG.This rule runs 24/7.

QSYSOPR QSYSOPR Message QueueThis rule group contains two JDE rules.

JDE: All inquiry messagesRaises an alert for each inquiry message that is generated on the QSYSOPRmessage queue.

JDE: High severity messages >=90Raises an alert for each message generated on the QSYSOPR message queue with a severity level of 90 or greater.

Job Log Rules

ORACLEJDEThis rule group contains five job log rules which monitor a selection of batch job messages and critical SQL errors in QZDASOINIT jobs.

JDE: SLEEPER batch job messagesSleeper is a dedicated subsystem that runs only one job - the Sleeper job. Thisjob submits scheduled jobs and releases all the jobs that have been set forunattended release.


This rule checks for any messages relating to the jobs within the SLEEPER subsystem and raises an alert for any batch job issuing an inquiry message in message file QCPFMSG. This rule runs 24/7 and is suspended for 30 minutes on alert to allow you time to investigate the cause.

JDE: OPSBATCH batch job messagesOPSBATCH is widely used as the operations subsystem for batch processing.This rule checks for any messages relating to the jobs within the OPSBATCHsubsystem and raises an alert for any batch job issuing an inquiry message inmessage file QCPFMSG. This rule runs 24/7 and is suspended for 30 minuteson alert to allow you time to investigate the cause.

JDE: USRBATCH batch job messagesUSRBATCH is widely used as the user subsystem for batch processing. Thisrule checks for any messages relating to the jobs within the USRBATCHsubsystem and raises an alert for any batch job issuing an inquiry message inmessage file QCPFMSG. This rule runs 24/7 and is suspended for 30 minuteson alert to allow you time to investigate the cause.

JDE: QBATCH batch job messagesThe QBATCH subsystem handles all of the JD Edwards job batch processing.This rule checks for any messages relating to the jobs within the QBATCHsubsystem and raises an alert for any batch job issuing an inquiry message inmessage file QCPFMSG. This rule runs 24/7 and is suspended for 30 minuteson alert to allow you time to investigate the cause.

JDE: Critical SQL error in QZDASOINIT jobsQZDASOINIT is the job name for the database SQL server jobs. These jobs areused to serve SQL to the JD Edwards client applications and normally run insubsystem QUSRWRK. This rule checks for any messages relating to theQZDASOINIT jobs within the QBATCH subsystem and raises an alert for anybatch job issuing an inquiry message in message file QCPFMSG. This rule runs24/7 and is suspended for 30 minutes on alert to allow you time to investigatethe cause.

Output Queue Rules

JDEPRT01 Output Queue RulesThis rule group contains two JDE customization rules that can be used tomonitor JDE output queues. The rules within this group are run every 60seconds.


JDEPRT01 queue released with JDEPRT01 startedChecks that the output queue JDEPRT01 is in a status of released and isattached to writer JDEPRT01 which is started. The rule is suspended for 30minutes if an alert is generated.

JDEPRT01 printer in MSGWChecks that the status of the output queue JDEPRT01 is not in a status ofMSGW. The rule is suspended for 30 minutes if an alert is generated.

Device Rules

JDE RulesThis rule group contains two JDE customization rules that can be used tomonitor devices. The rules within this group are run every 60 seconds.

Ethernet lines activeChecks to ensure that all ethernet line connections are active and are varied on.The rule is suspended for 30 minutes if an alert is generated.

TAP01 not active/varied onChecks to ensure that the Tape Drive TAP01 is varied on. The device name canbe overridden if required using option 2=Change against the rule. The rule issuspended for 30 minutes if an alert is generated.

Job Queue Rules

JDEDAYQThis rule group contains two JDE customization rules that can be used tomonitor the daytime job queue. The rules within this group are run every 60seconds.

JDE Daytime queue released 0800 to 1800 hoursChecks to ensure that the job queue JDEDAYQ is in a released status betweenthe hours of 0800 and 1800 on a daily basis. The rule is suspended for 30minutes if an alert is generated.

JDE Daytime queue held 1801 to 0759 hoursChecks to ensure that the job queue JDEDAYQ is in a held status between thehours of 1801 and 0759 on a daily basis. The rule is suspended for 30 minutesif an alert is generated.


JDENIGHTQThis rule group contains two JDE customization rules that can be used tomonitor the nighttime job queue. The rules within this group are run every 60seconds.

JDE Night queue held 0800 to 1800 hoursChecks to ensure that the job queue JDENIGHTQ is in a held status betweenthe hours of 0800 and 1800 on a daily basis. The rule is suspended for 30minutes if an alert is generated.

Night queue released 1801 to 0759 hoursChecks to ensure that the job queue JDENIGHTQ is in a released statusbetween the hours of 1801 and 0759 on a daily basis. The rule is suspended for30 minutes if an alert is generated.

Performance Rules

Notes regarding the Performance Monitor rules contained in this template:

• Each JD Edwards installation has unique job/subsystem names. Halcyon recommends that these templates are reviewed and updated to suit your own environment

• The MERLIN subsystem is only active where the barcode application is in use - not all installations of JD Edwards may have this activated

• The GPS subsystem is only active where the dashboard view is in use - not all installations of J D Edwards may have this activated

• The SLEEPER* jobs are the automatic batch processing jobs in subsystem SLEEPER – you must update these job names to suit your own environment

• Throughout these templates; USRBATCH represents the user subsystem for batch processing and OPSBATCH represents the operations subsystem for batch processing – you may have more batch processing subsystems defined in your environment

• Long running and temporary storage checking rules should be reviewed and specific jobs that do not require monitoring should be added as omissions. You may want to add automation to these rules to hold or end the jobs found to be long running or using excessive temporary storage

JDE RulesThis rule group contains the following JDE customization rules that can be usedto monitor JDE application specific performance statistics.


JDE: ASP used >= 85.0% - 89.9%This rule checks that the percentage of ASP used is not greater than or equal tobetween 85 and 89.9% of the total available and acts as an early warning ofpossible issues. The rule runs 24/7 and if an alert is raised, the rule issuspended for 15 minutes to allow you time to investigate and resolve the issue.

JDE: ASP used >= 90%This rule checks that the percentage of ASP used is not greater than or equal to90% of the total available. The rule runs 24/7 and if an alert is raised, the rule issuspended for 15 minutes to allow you time to investigate and resolve the issue.

JDE: System CPU >= 95%This rule checks that the percentage of CPU used is not greater than or equal to 95% of the total available. The rule runs 24/7 and if an alert is raised, the rule is suspended for 15 minutes to allow you time to investigate and resolve the issue.

JDE: Response times > 2 secondsChecks that the average interactive response time during the previous 5Performance Monitor base processing periods does not exceed 2 seconds. Therule is suspended for 30 minutes if an alert is generated.

JDE: High Interactive CPUThis rule checks for any Interactive job using more than 2000000 seconds ofCPUTIME in any subsystem. The rule runs 24/7 and if an alert is raised, the ruleis suspended for 60 minutes to allow you time to investigate and resolve theissue.

JDE: Check Sleeper Jobs are activeThis rule checks that the Sleeper jobs (SLEEPER1 - SLEEPER 7 inclusive) insubsystem SLEEPER always have at least 1 or more batch jobs active at anyone time. The rule runs 24/7 and if an alert is raised, the rule is suspended for30 minutes to allow you time to investigate and resolve the issue.

JDE: Check Debug server is activeThis rule checks that the Debug Server (QB5ROUTER) job in subsystemQUSRWRK always has at least 1 or more batch jobs active at any one time.The rule runs 24/7 and if an alert is raised, the rule is suspended for 30 minutesto allow you time to investigate and resolve the issue.

JDE: Check QMSF is active This rule checks that the Mail Server Framework (QMSF) job in subsystemQSYSWRK always has at least 3 or more batch jobs active at any one time. Therule runs 24/7 and if an alert is raised, the rule is suspended for 30 minutes toallow you time to investigate and resolve the issue.


JDE: Check Database Server is activeThis rule checks that the Database Server (QZDASRVSD) job in subsystemQSERVER always has at least 1 or more batch jobs active at any one time. Therule runs 24/7 and if an alert is raised, the rule is suspended for 30 minutes toallow you time to investigate and resolve the issue.

JDE: Check Netserver is activeThis rule checks that the Net Server (QZLSSERVER) job in subsystemQSERVER always has at least 1 or more batch jobs active at any one time. Therule runs 24/7 and if an alert is raised, the rule is suspended for 30 minutes toallow you time to investigate and resolve the issue.

JDE: Long running jobs USRBATCHThis rule checks for any batch jobs in subsystem USRBATCH that have beenrunning for longer than 7 hours. The rule runs 24/7 and if an alert is raised, therule is suspended for 30 minutes to allow you time to investigate and resolve theissue.

JDE: Long running jobs OPSBATCHThis rule checks for any batch jobs in subsystem OPSBATCH that have beenrunning for longer than 7 hours. The rule runs 24/7 and if an alert is raised, therule is suspended for 30 minutes to allow you time to investigate and resolve theissue.

JDE: Long running jobs QBATCHThis rule checks for any batch jobs in subsystem QBATCH that have beenrunning for longer than 7 hours. The rule runs 24/7 and if an alert is raised, therule is suspended for 30 minutes to allow you time to investigate and resolve theissue.

JDE: Long running jobs MERLINThis rule checks for any batch jobs in subsystem MERLIN that have beenrunning for longer than 7 hours and raises an alert if any are found to be in thisstatus.

JDE: Batch jobs in HLD status (USRBATCH)This rule checks for any batch jobs in a status of HELD in subsystemUSRBATCH. The rule runs 24/7 and if an alert is raised the rule is suspendedfor 30 minutes to allow you time to investigate and resolve the issue.

JDE: Batch jobs in HLD status (OPSBATCH)This rule checks for any batch jobs in a status of HELD in subsystemOPSBATCH. The rule runs 24/7 and if an alert is raised the rule is suspendedfor 30 minutes to allow you time to investigate and resolve the issue.


JDE: Batch jobs in HLD status (QBATCH)This rule checks for any batch jobs in a status of HELD in subsystem QBATCH.The rule runs 24/7 and if an alert is raised the rule is suspended for 30 minutesto allow you time to investigate and resolve the issue.

JDE: Batch jobs in HLD status (SLEEPER)This rule checks for any batch jobs in a status of HELD in subsystemSLEEPER. The rule runs 24/7 and if an alert is raised the rule is suspended for30 minutes to allow you time to investigate and resolve the issue.

JDE: Temporary storage USRBATCHThis rule checks for any job using more than 40000MB of temporary storage insubsystem USRBATCH. The rule runs 24/7 and if an alert is raised, the rule issuspended for 30 minutes to allow you time to investigate and resolve the issue.

JDE: Temporary storage OPSBATCHThis rule checks for any job using more than 40000MB of temporary storage insubsystem OPSBATCH. The rule runs 24/7 and if an alert is raised, the rule issuspended for 30 minutes to allow you time to investigate and resolve the issue.

JDE: Temporary storage QBATCHThis rule checks for any job using more than 40000MB of temporary storage insubsystem QBATCH. The QBATCH subsystem handles all of the JD Edwardsjob batch processing. The rule runs 24/7 and if an alert is raised, the rule issuspended for 30 minutes to allow you time to investigate and resolve the issue.

JDE: Temporary storage MERLINThis rule checks for any job using more than 40000MB of temporary storage insubsystem MERLIN. The rule runs 24/7 and if an alert is raised, the rule issuspended for 30 minutes to allow you time to investigate and resolve the issue.

JDE: Temporary storage QUSRWRK QZDASOINIT jobThis rule checks for the QZDASOINIT job using more than 40000MB oftemporary storage in subsystem QUSRWRK. The rule runs 24/7 and if an alertis raised, the rule is suspended for 30 minutes to allow you time to investigateand resolve the issue.

JDE: Temporary storage interactive dayThis rule checks for any interactive job using more than 50000MB of temporarystorage in any subsystem during the daytime. The rule runs between 09:00 and18:00 every day of the week and if an alert is raised, the rule is suspended for30 minutes to allow you time to investigate and resolve the issue.

2- 1 0 H a l c y o n T e m p l a t e s

JDE: Temporary storage batchThis rule checks for any batch job using more than 70000MB of temporarystorage in any subsystem. The rule runs 24/7 and if an alert is raised, the rule issuspended for 30 minutes to allow you time to investigate and resolve the issue.

JDE: Temporary storage interactive nightThis rule checks for any interactive job using more than 80000MB of temporarystorage in any subsystem during the nighttime. The rule runs between 18.01and 08:59 every day of the week and if an alert is raised, the rule is suspendedfor 30 minutes to allow you time to investigate and resolve the issue.

JDE: MSGW & LCKW QINTER jobsThis rule checks for any jobs in subsystem QINTER (except subsystem monitorjobs) that are in a status of MSGW and LCKW. The rule runs 24/7 and if an alertis raised, the rule is suspended for 30 minutes to allow you time to investigateand resolve the issue.

JDE: MSGW & LCKW QUSRWRK QZDASOINIT jobs This rule checks for any QZDASOINIT batch jobs in subsystem QUSRWRK that are in a status of MSGW and LCKW. The rule runs 24/7 and if an alert is raised, the rule is suspended for 30 minutes to allow you time to investigate and resolve the issue.

JDE: Subsystem QSERVER activeThis rule checks that subsystem QSERVER is constantly active. TheQSERVER subsystem is used for server functions for network connectivity. Therule runs 24/7 and if an alert is raised, the rule is suspended for 30 minutes toallow you time to investigate and resolve the issue.

JDE: Subsystem QSYSWRK activeChecks that subsystem QSYSWRK is constantly active. The QSYSWRKsubsystem holds system-related jobs. Jobs in this subsystem are generally pre-startjobs. The rule is suspended for 30 minutes if an alert is generated.

JDE: Subsystem QBATCH activeChecks that subsystem QBATCH is constantly active. The QBATCH subsystemhandles all of the JD Edwards job batch processing. The rule is suspended for30 minutes if an alert is generated.

JDE: Subsystem QSPL activeChecks that subsystem QSPL is constantly active. The QSPL subsystem isused for spooled files. The rule is suspended for 30 minutes if an alert isgenerated.


JDE: Subsystem QINTER activeChecks that subsystem QINTER is constantly active. The QINTER subsystemservices the needs of interactive user. The rule is suspended for 30 minutes ifan alert is generated.

JDE: Subsystem QUSRWRK activeChecks that subsystem QUSRWRK is constantly active. The QUSRWRKsubsystem is for user work and is intended to be used when there canpotentially be a large number of user jobs. The rule is suspended for 30 minutesif an alert is generated.

JDE: Subsystem QHTTPSVR activeChecks that subsystem QHTTPSVR is constantly active. The QHTTPSVRsubsystem is used for running Web application server instance jobs. The rule issuspended for 30 minutes if an alert is generated.

JDE: Subsystem QCMN activeChecks that subsystem QCMN is constantly active. The QCMN subsystem isused for running communication jobs. The rule is suspended for 30 minutes ifan alert is generated.

JDE: Subsystem USRBATCH activeChecks that subsystem USRBATCH is constantly active. The USRBATCHsubsystem is used for running user batch jobs. The rule is suspended for 30minutes if an alert is generated.

JDE: Subsystem OPSBATCH activeChecks that subsystem OPSBATCH is constantly active. The OPSBATCHsubsystem is used for running operational batch jobs. The rule is suspended for30 minutes if an alert is generated.

JDE: Subsystem JDEB733 activeChecks that subsystem JDEB733 is constantly active. The JDEB733 subsystemhandles the database source. The rule is suspended for 30 minutes if an alert isgenerated.

JDE: Subsystem MERLIN activeChecks that subsystem MERLIN is constantly active. The MERLIN subsystemis only active where the barcode application is in use - not all installations of JD Edwards may have this activated. The rule is suspended for 30 minutes if analert is generated.


JDE: Subsystem SLEEPER activeChecks that subsystem SLEEPER is constantly active. SLEEPER is adedicated subsystem that runs only one job - the Sleeper job. This job submitsscheduled jobs and releases all the jobs that have been set for unattendedrelease. The rule is suspended for 30 minutes if an alert is generated.

JDE: Subsystem GPS activeChecks that subsystem GPS is constantly active. The GPS subsystem is onlyactive where the dashboard view is in use - not all installations of J D Edwardsmay have this activated. The rule is suspended for 30 minutes if an alert isgenerated.

User Rules

JDE RulesThis rule group contains a single JDE customization rule that can be used tomonitor the JDE user profile. The rule within this group is run every 60 seconds.

Ensure JDE user profile is enabledChecks that the user profile JDE is enabled at all times. The rule is suspendedfor 30 minutes if an alert is generated.

Inactivity Rules

JDE RulesThis rule group contains two JDE customization rules that can be used tomonitor types of JDE inactivity. The rules within this group are run every 60seconds.

JDE: QUSRWRK QZDASOINIT jobs in RUN > 5 minsChecks that the QZDASOINIT job is running efficiently in subsystemQUSRWRK. An alert is raised if the period of inactivity is equal to 5 minutes orlonger. The rule is suspended for 30 minutes if an alert is generated.

JDE: QUSRWRK QZDASOINIT jobs in LCKW > 5 minsChecks that there are no QZDASOINIT jobs subsystem QUSRWRK that havebeen in LCKW status for more than five minutes. The rule is suspended for 30minutes if an alert is generated.


Object Rules

JDE RulesThis rule group contains a single JDE customization rule that can be used tomonitor JDE objects. The rule within this group is run every 60 seconds.

Track data area JDFOBJ/QJDF existenceChecks that library object library QJDF exists within the JDFOBJ data area.This library contains the execution objects required by the initial sign-onprogram. This field is also used by JDE’s PTF procedures to know where toreplace the object code. The rule is suspended for 30 minutes if an alert isgenerated.

Audit Journal Rules

JDE RulesThis rule group contains three JDE customization rules that can be used tomonitor JDE audit journal activity. The rules within this group are constantly inforce.

JDE: Track changes to JDE user profileChecks audit journal entry type; CP (User profile changed, created or restored)for any changes made to the JDE user profile.

JDE: Track changes to JDEINSTAL user profileChecks audit journal entry type; CP (User profile changed, created or restored) for any changes made to the JDEINSTAL user profile.

JDE: Track changes to JDEGRP user profileChecks audit journal entry type; CP (User profile changed, created or restored) for any changes made to the JDEGRP user profile.

JDE: Secure JDFDTA libraryChecks audit journal entry type; CA (Authority changes) for any amendmentsmade to the JDEDTA library.

JDE: Secure JDFOBJ libraryChecks audit journal entry type; CA (Authority changes) for any amendmentsmade to the JDEDTA library.


JDE: Secure JDFSRC libraryChecks audit journal entry type; CA (Authority changes) for any amendmentsmade to the JDEDTA library.

JDE: Track changes to QJDF data areaChecks audit journal entry type; ZC (Object accessed (change)) for anyamendments made to the QJDF data area.

JDE: Programs changed to adopt QSECOFRChecks audit journal entry type; PA (Program changed to adopt authority) forany programs amended to adopt QSECOFR authority.

JDE: Secure QGPL user job descriptionsChecks audit journal entry type; ZC (Object accessed (change)) for anyamendments made to QGPL user job descriptions.

JDE: Secure application authorization listsChecks audit journal entry type; ZC (Object accessed (change)) for anyamendments made to the application authorization lists.

JDE: Secure programs J98INIT and J98INITAChecks audit journal entry type; ZC (Object accessed (change)) for anyamendments made to programs J98INIT and J98INITA.


C H A P T E R

CHAPTER 3JD EDWARDS ENTERPRISEONEWINDOWS MONITORING

JD Edwards EnterpriseOne can be run on various platforms. Using aspecialized Network Server Suite Windows template the following can also bemonitored:

Oracle JDE EnterpriseOne templateOracle's JD Edwards EnterpriseOne® is an integrated applications suite ofcomprehensive enterprise resource planning software.

The Oracle JDE EnterpriseOne Windows template contains the followingcomponents:

Performance Monitors - WMI

JDE: Binary Large Object Handler Process Active - Instance(ipcsrv) Trigger(Does Not Exist)ipcsrv.exe is the process responsible for passing Binary Large Objects (BLOBs)between other processes. This rule checks to ensure that the ipcsrv.exeprocess exists and is active. An alert is raised if the process is found not to existon the monitored system.

JDE: Execute Submitted Jobs Process Active - Instance(runbatch) Trigger(Does Not Exist)runbatch.exe is the job responsible for executing the submitted reports. Thisrule checks to ensure that the runbatch.exe process exists and is active. Analert is raised if the process is found not to exist on the monitored system.


JDE: Monitor Excessive Jobs on Print Queue - Instance(US Office) Counter(Jobs) Trigger(>10)This rule raises an alert if a monitored print queue has in excess of ten jobsqueued.

JDE: Network Listener Process Active - Instance(jdesnet_n) Trigger(Count < 3)jdesnet_n is a network listener listens for connection requests. Depending onthe jde.ini setting, zero, one, or more of these processes can runsimultaneously. This rule raises an alert if less than thee jdesnet_n processesare active on the monitored system.

Note: Please check your own configuration and amend the count accordingly.

JDE: Network Listener Process Count - Instance(jdesnet_n) Trigger(Count < 3)jdesnet_n is a network listener listens for connection requests. Depending onthe jde.ini setting, zero, one, or more of these processes can runsimultaneously. This rule raises an alert if less than thee instances of jdesnet_nprocesses are found on the monitored system.

Note: Please check your own configuration and amend the count accordingly.

JDE: Primary Process Active - Instance(jdesnet) Trigger(Does Not Exist)This rule raises an alert if the primary process jdesnet_n is not found in themonitored system.

JDE: Server Manager Agent Process Active - Instance(steagent) Trigger(Does Not Exist)steagent.exe returns the CPU and memory usage of the Management Agentprocess. This rule raises an alert if the process steagent.exe is not found in themonitored system.

JDE: Server Kernel Process Count - Instance(jdesnet_k) Trigger(Count < 4)jdesnet_k is the job responsible for coordination between the net and queues.This rule raises an alert if the number of instances of jdesnet_k is less than fouron the monitored system.

J D E d w a r d s E n t e r p r i s e O n e W i n d o w s m o n i t o r i n g 3-17

System Monitors - Log File

JDE: Agent Maintenance Log File - Log File(e:\jde_home\SCFHA\logs\stderr.log) Include(*) Exclude()Agent maintenance is used when issues arise through managing the instances,such as being unable to or create instances or binding issues. This rule checksthe JD Edwards agent maintenance error log file (stderr.log) and raises an alertif any entries are found.

JDE: Java Development Environment Logfile Critical Entries - Log File(C:\jde_home\logs\e1agent_0.log) Include(SEVERE;WARNING) Exclude()The JD Edwards Java Development and Runtime Environment log file containsevents related to:

• registering/installing E1 managed instances

• registering and managing IBM WebSphere and Oracle Application Server

• managing the configuration file(s) for E1 managed instances

• starting/stopping E1 servers and the J2EE servers

• performing tools release upgrades/downgrades for E1 servers

• discovering and sending log files to the management console for viewing.

SEVERE messages arise when a critical error has occurred from theperspective of the agent. Critical errors are non-recoverable errors and requireimmediate attention. WARNING messages denote an abnormal or unexpectedresult occurred that is recoverable, from the perspective of the agent.

This rule checks the Java Development Environment (e1agent_0.log) log file forany Severe and/or Warning messages and raises an alert if any entries arefound.

JDE: Java Runtime Environment Critical Entries - Log File(C:\jre_home\logs\e1agent_0.log) Include(SEVERE;WARNING) Exclude ()This rule performs the same function as the previous rule but for the JavaRuntime Environment. This rule checks the Java Runtime Environment(e1agent_0.log) log file for any Severe and/or Warning messages and raises analert if any entries are found.

JDE: Management Agent Log File - Log File(e:\jde_home\SCFHA\logs\e1agent_0.log) Include(*) Exclude()The Management Agent generates log messages at various log levels. This rulechecks the Management Agent (e1agent_0.log) log file and raises an alert if anyentries are found.


JDE: Performance Statistics Log File - Log File(e:\JDEdwards\E910\log\jde_xxxx.log) Include(*) Exclude()SnapShot is the Deployment Server running SQL. The SnapShot programmanages multiple instances of JD Edwards EnterpriseOne, DeploymentServers or Development Clients on a single machine.

This rule checks the Performance Statistics (jde_xxxx.log) log file and raises analert if any entries are found.

JDE: Snapshot Log File - Log File(e:\Snapshot.log) Include(ERR) Exclude()SnapShot is the Deployment Server running SQL. The SnapShot programmanages multiple instances of JD Edwards EnterpriseOne, DeploymentServers or Development Clients on a single machine. The phrase ‘ERR’indicates an error.

This rule checks the Snapshot (snapshot.log) log file and raises an alert if any‘ERR’ entries are found.

System Monitors - Service

JDE: 910 B9 Network Service - Service(JDE910 B9 Network) Status(<> ‘Started’)The JD Edwards Network Service provides the network connection between theJD Edwards EnterpriseOne workstation and the JD Edwards EnterpriseOneenterprise server. The JDE network service is required for any operations to runon the server. This rule checks to ensure that the JDE910 B9 (the E1 service aused to connect to the back-end database) Network Service is started andraises an alert if it is found to be in any other status.

JDE: 910 B9 Queue Service - Service(JDE910 B9 Queue Service) Status(<> ‘Started’)The JD Edwards Queue Service starts jobs (batch or server packageinstallations) on the JD Edwards EnterpriseOne enterprise server. This rulechecks to ensure that the JDE910 B9 (the E1 service a used to connect to theback-end database) Queue Service is started and raises an alert if it is found tobe in any other status.

JDE: JD Edwards EnterpriseOne Service - Service(SM Management Agent) Status(<> ‘Started’)SM Management Agent is the agent that does the monitoring and reports backto the ServerManager Console. This rule checks to ensure that the SMManagement Agent is started and raises an alert if it is found to be in any otherstatus.

J D E d w a r d s E n t e r p r i s e O n e W i n d o w s m o n i t o r i n g 3-19

JDE: Oracle Weblogic Service - Service(Oracle Weblogic wl_server NodeManager) Status(<> ‘Started’)The Oracle WebLogic service controls the processes running in Weblogic. TheWebLogic Server installation process installs Node Manager to run as anoperating system service. This rule checks to ensure that the Oracle WebLogicwl_server NodeManager is started and raises an alert if it is found to be in anyother status.

TCP Monitors - TCP/UDP Generic

JDE: Management Agent Port - Host(127.0.0.1) Port(14502) Timeout(5 Secs) Command(&CM) Result(<> ‘[Empty]’)The JD Edwards Management Agent provides the Remote Management Agentwith the ability to accept incoming sessions. This rule checks port 14502 on thehost device and raises an alert if the status returned is anything other than‘Empty’.

JDE: Management Console HTTP Port - Host(127.0.0.1) Port(8999) Timeout(5 Secs) Command(&CM) Result(<> ‘[Empty]’)The JD Edwards Management Console provides the Management HTTPConsole with the ability to accept incoming sessions. This rule checks port 8999on the host device and raises an alert if the status returned is anything otherthan ‘Empty’.

JDE: Management Server JMX Port - Host(127.0.0.1) Port(14501) Timeout(5 Secs) Command(&CM) Result(<> ‘[Empty]’)The JD Edwards Management Server JMX provides the Management ServerJMX with the ability to accept incoming sessions. This rule checks port 14501on the host device and raises an alert if the status returned is anything otherthan ‘Empty’.


C H A P T E R

CHAPTER 4JD EDWARDS ENTERPRISEONE AIXMONITORING

JD Edwards EnterpriseOne can be run on various platforms. Using aspecialized Network Server Suite AIX template the following can also bemonitored:


The Oracle JDE EnterpriseOne AIX template contains the followingcomponents:

Script Monitor

JDE: Monitor Overnight NIGHTOPR Batch Processes - Script(jdejobs nightopr ^([a-zA-Z0-9]+).*)This Script Monitor rule monitors for any jobs running under the overnightNIGHTOPR batch processes that are still running and raises an alertaccordingly if any are found.

File and Folder Monitor

JDE: Monitor changes in JDE.INI - File or Folder(JDE_BASE\JDE.INI) Include(*) Trigger(Exists)JDE.INI is the main configuration file for JD Edwards EnterpriseOneinstallations. This rule monitors for any changes in this file and raises an alert ifany modifications are recorded.

J D E d w a r d s E n t e r p r i s e O n e A I X m o n i t o r i n g 4-21

Log File Monitor

JDE: Monitor JDE LogFiles - LogFile(/var/log/jde/jde*) Expression(.+)This Log File Monitor rule checks a specific JD Edwards log file for any changes and raises an alert if any are found.

Note: Each log file to be monitored must be entered as a separate rule. Use the copy rule facility to save time.

Process Monitor

JDE: Execute Submitted Jobs Process Active - Type(Process By Name) Process(runbatch) Trigger(Does Not Exist) runbatch.exe is the job responsible for executing the submitted reports. ThisProcess Monitor rule checks that the runbatch job is active and an alert is raisedif it is found to not exist in the monitored system.

JDE: Kernel Processes Active - Type(Process By Name) Process(jde_k) Trigger(Does Not Exist)jdes_k is the job responsible for co‐ordination between the net and thequeues. This Process Monitor rule checks that the jde_k job is active and analert is raised if it is found to not exist in the monitored system.

JDE: Kernel Process Count - Type(Process By Name) Process(jde_k) Measure(NumberOfProcesses) Trigger(<4)jdes_k is the job responsible for co‐ordination between the net and thequeues. This Process Monitor rule checks that at least four instances of thejde_k job are active and an alert is raised if any less than this number are foundin the monitored system.

JDE: Network Listener Process Active - Type(Process By Name)Process(jde_n) Trigger(Does Not Exist)jde_n is a network listener that listens for connection requests. Depending onthe jde.ini setting, zero, one, or more of these processes can runsimultaneously. This Process Monitor rule checks that the jde_n job is activeand an alert is raised if it is found to not exist in the monitored system.

JDE: Network Listener Process Count - Type(Process By Name) Process(jde_n) Measure(NumberOfProcesses) Trigger(<3)jde_n is a network listener that listens for connection requests. Depending onthe jde.ini setting, zero, one, or more of these processes can runsimultaneously. This Process Monitor rule checks that at least three instancesof the jde_n job are active and an alert is raised if any less than this number arefound in the monitored system.


C H A P T E R

CHAPTER 5JD EDWARDS ENTERPRISEONE LINUXMONITORING

JD Edwards EnterpriseOne can be run on various platforms. Using aspecialized Network Server Suite Linux template the following can also bemonitored:


The Oracle JDE EnterpriseOne Linux template contains the followingcomponents:

Script Monitor

JDE: Monitor Overnight NIGHTOPR Batch Processes - Script(jdejobs nightopr ^([a-zA-Z0-9]+).*)This Script Monitor rule monitors for any jobs running under the overnightNIGHTOPR batch processes that are still running and raises an alertaccordingly if any are found.

File and Folder Monitor

JDE: Monitor changes in JDE.INI - File or Folder(JDE_BASE\JDE.INI) Include(*) Trigger(Exists)JDE.INI is the main configuration file for JD Edwards EnterpriseOneinstallations. This rule monitors for any changes in this file and raises an alert ifany modifications are recorded.

J D E d w a r d s E n t e r p r i s e O n e L i n u x m o n i t o r i n g 5-23

Log File Monitor

JDE: Monitor JDE LogFiles - LogFile(/var/log/jde/jde*) Expression(.+)This Log File Monitor rule checks a specific JD Edwards log file for any changes and raises an alert if any are found.

Note: Each log file to be monitored must be entered as a separate rule. Use the copy rule facility to save time.

Process Monitor

JDE: Execute Submitted Jobs Process Active - Type(Process By Name) Process(runbatch) Trigger(Does Not Exist) runbatch.exe is the job responsible for executing the submitted reports. ThisProcess Monitor rule checks that the runbatch job is active and an alert is raisedif it is found to not exist in the monitored system.

JDE: Kernel Processes Active - Type(Process By Name) Process(jde_k) Trigger(Does Not Exist)jdes_k is the job responsible for co‐ordination between the net and thequeues. This Process Monitor rule checks that the jde_k job is active and analert is raised if it is found to not exist in the monitored system.

JDE: Kernel Process Count - Type(Process By Name) Process(jde_k) Measure(NumberOfProcesses) Trigger(<4)jdes_k is the job responsible for co‐ordination between the net and thequeues. This Process Monitor rule checks that at least four instances of thejde_k job are active and an alert is raised if any less than this number are foundin the monitored system.

JDE: Network Listener Process Active - Type(Process By Name)Process(jde_n) Trigger(Does Not Exist)jde_n is a network listener that listens for connection requests. Depending onthe jde.ini setting, zero, one, or more of these processes can runsimultaneously. This Process Monitor rule checks that the jde_n job is activeand an alert is raised if it is found to not exist in the monitored system.

JDE: Network Listener Process Count - Type(Process By Name) Process(jde_n) Measure(NumberOfProcesses) Trigger(<3)jde_n is a network listener that listens for connection requests. Depending onthe jde.ini setting, zero, one, or more of these processes can runsimultaneously. This Process Monitor rule checks that at least three instancesof the jde_n job are active and an alert is raised if any less than this number arefound in the monitored system.


Learn MoreFor white papers, online product tours, datasheets, technical tips and manuals, please visit: http://www.helpsystems.com/halcyon

Contactwww.helpsystems.com

US: +1 952-933-0609

Outside the U.S.: +44 (0) 870 120 3148

TrademarksIBM®, iSeries®, Power/System i®, IBM i®, i5/OS® and AIX® are registered trademarks of International Business Machines Corporation in the United States and in other countries,

Windows® is a registered trademark of Microsoft Corporation.

Linux® is a registered trademark of Linus Torvalds.

JD Edwards®, EnterpriseOne® and World® are registered trademarks of Oracle and/or its affiliates.

All other trademarks are respective of their own companies.

http://www.halcyonsoftware.com/technical

http://www.halcyonsoftware.com/technical

Documents

Guide to JD Edwards templates - static.helpsystems.com · • Infor M3 (Movex) • Infor XA • Infor XE • Misys • Misys Midas Plus • SAP •Maxava •Quick/EDD • Vision Replication