This chapter contains the following topics:
Section 3.1, "Configuring JD Edwards EnterpriseOne Performance Monitor"
Section 3.2, "Enabling the Required Elements on the Monitoring System"
Section 3.3, "Enabling the Required Elements on the Monitored System"
Configuring JD Edwards EnterpriseOne Performance Monitor involves enabling the required elements on the monitored system and the monitoring system.
When you install the JD Edwards EnterpriseOne System and transfer the appropriate files to the web server and application server, all of the required elements are in place. You do not need to install additional modules for JD Edwards EnterpriseOne Performance Monitor.
This 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.
The monitoring database requires the use of at least the JD Edwards EnterpriseOne System database for the production monitoring system. Set up this database up using the instructions in the JD Edwards EnterpriseOne Installation Guide. To improve performance of the monitored server, you may want to map the PerfMon database tables to a database other than the production database. These tables would need to be mapped:
| 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 | PM Global Administration (PSPMMONITORGBL) |
| F95905 | PM Monitor Clustering (PSPMMONINST) |
| F95906 | PM Frequent Users (PSPMOPRDEFN) |
| F95907 | PM Trace Names (PSPMPERFTACE) |
| F95908 | PM Frequent Components (PSPMPNLGRPDEFN) |
| F95909 | PM Agent Definition (PSPMAGENT) |
| F95910 | PM Agent Filters (PSPMAGENTFILTER) |
| F95911 | PM Archive 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 | PM Metric Definition (PSPMMETRICDEFN) |
| F9593311 | PM Metric Definition UDC Display (n/a) |
| F959331D | PM Metric Definition Language (PSPMMETRIC_LNG) |
| F959332 | PM Metric Value (PSPMMETRICVALUE) |
| F959332D | PM Metric Value Language (PSPMMETRICVALUE_LN) |
| F959341 | PM Context Definition (PSPMCONTEXTDEFN) |
| F959341D | PM Context 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) |
The JD Edwards EnterpriseOne Transaction Server (RTE) Installer program installs all of the elements that JD Edwards EnterpriseOne Performance Monitor requires on the web server. No additional installations are required.
JD Edwards EnterpriseOne Performance Monitor servlets that run on the web server of the monitoring system 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:
The JD Edwards EnterpriseOne PerfMon Java Adapter is started and waits for incoming messages from JD Edwards EnterpriseOne application servers.
The Data Collator is started.
The Data Collator sends a registration request to the PPMI servlet.
PPMI servlet registers the Data Collator.
Data Collator waits to receive performance data from Monitor servlet.
JD Edwards EnterpriseOne JAS Server Agents register with the Monitor servlet.
JD Edwards EnterpriseOne CallObject processes on the application server (C-Agents) send the Agent Initialization request to the JD Edwards EnterpriseOne Java Adapter.
JD Edwards EnterpriseOne Java Adapter registers the C-Agents with the Monitor servlet.
JAS Server Agents send performance data to the Monitor servlet.
C-Agents send performance data to the JD Edwards EnterpriseOne Java Adapter.
JD Edwards EnterpriseOne Java Adapter sends performance data to the Monitor servlet.
Monitor servlet sends performance data to the Data Collator.
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, you need to specify the appropriate URL to which performance data is sent.The JD Edwards EnterpriseOne Transaction Server installer installs the PerfMon components on the Monitoring System. The following sections refer to the JD Edwards EnterpriseOne Transaction Server Install Directory by JD Edwards EnterpriseOneTransInstallDir.
The JAS.INI file on the monitoring server is located in EnterpriseOneTransInstallDir/cfg/jas.ini. This .ini file has 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.
The [JDENET_KERNEL_DEF2] section defines the JD Edwards EnterpriseOne PerfMon Java Adapter component of the monitoring server. You do not need to change any settings for this section and it is correctly configured 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
In order for the EnterpriseOne PerfMon Java Adapter to start correctly on the monitoring server, these settings need 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
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. # E1 Transaction Server installer will update this setting in the jas.ini file⇒ with the # correct host name and port number. 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
# 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 collators # running on different monitoring systems can have their own groups. # GROUP=group1 # # Number of elements (for example, transaction start or end) the Monitor servlet # sends to PPMI clients. # # BATCHSIZ=1000 # # Number of Collator threads to start that will listen to one group. # NumCollThreads=1
This section discusses enabling the required elements on the monitored system which is the system for which you 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.
As long as your JD Edwards EnterpriseOne application server is running against your JD Edwards EnterpriseOne database, no further database configuration is required for JD Edwards EnterpriseOne Performance Monitor.
The monitor URL identifies the Monitor servlet. The monitor URL value must reflect the URL of the monitor servlet that is running on the monitoring system. The readme.txt generated by the installer contains the correct 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 components on the monitored system are disabled.
No additional installation procedure is required. When JD Edwards EnterpriseOne Performance Monitor is turned on (by providing the monitor URL or by setting the flag in the JAS.INI file), agents on the JD Edwards EnterpriseOne web server automatically become active and begin relaying performance data to the monitoring system.
The JAS.INI file on the monitored web server requires new settings for PerfMon. If these settings do 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 [SERVER COMPONENTS] section in the jas.ini file on the Monitored Server: com.jdedwards.jas.PerfMonInit The following section is added to the JAS.INI file to define the settings for JD Edwards EnterpriseOne Performance Monitor.
The settings that you need to set after the install are in brackets ({}). For the other settings you can use the default installed values and change them later if needed.
# This is the URL of the monitor Servlet.
# 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--
# 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.
# E1 Transaction Server installer will update this setting in the jas.ini file⇒
with the
# correct host name and port number.
{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.
#
transactionTimeout=60
#
# not currently being used.
#
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
Performance 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 in every instrumented server process automatically become active and begin relaying performance data to the 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 other than true, then the agents are disabled for this server.
PerfMon requires new settings in the JDE.INI file on the monitored Server.
The settings that you need to set after the install are in brackets ({}). The other settings you can use the default installed 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
# This is the URL of the monitor Servlet.
# 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--
# A String used to distinguish the host and port of the machines where different⇒
Agents
# 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.
#
transactionTimeout=60
# not currently being used.
#
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.