Introduction

The PROCESSIT Diagnostics Report provides a 37-point system health status snapshot, designed to eliminate guesswork and provide current and accurate system information critical to the resolution of application issues.

The report, which is e-mail driven, can be run on an on-demand basis or as a scheduled process, and includes database, operating system, application server, and workflow processing health monitoring points.

Download the diagnostics report

Download file from ftp://ftp.readsoft-us.com/Software/Oracle/PROCESSIT/DiagRpt/diagrpt.zip

Extract content to a directory of your choice. It is recommended to place it on the PROCESSIT WebLogic server, but it is not required.

Configure the report

Edit the properties file diagrpt.properties in the <$DOMAINHOME>/diagrpt directory to specify environment specific values for server names, email settings and warning thresholds. The settings in this file must match your PROCESSIT environment. You can edit the file in most common basic text editors.

If you are running PROCESSIT based on a virtual appliance installation the default settings can be used, although you should change the company name, environment name, and mail recipient.

Each property value is set after the equation symbol for that property, for instance company.name=MY-COMPANY. They are listed later in this document.

Mail recipient

You can choose to comment out the mail parameters. The report is then written to disc.

DIAGNOSTICS PARAMETERS

• company.name : Your company name. Used in report description and headline. Any text string is valid.
• processit.environment.name : The name of the environment for description purposes. Any text string is valid.
• db.serverName : The host name of the SOA database server, for instance the ip address or soa.vm.net.
• db.portNumber : The SOA database server port number.
• db.sid : The SOA database server sid.
• db.username : Database user name.
• db.password : Password for database user.
• report.outputfile : The filename and filetype for the report diagnostics file. The filetype should be .html, so the convention is yourfilename.html.
• mail.server : smtp server
• mail.to :
• mail.from :
• mail.subject :
• wls.hostName : The host name of the WebLogic server. for instance the ip address or weblogic.
• wls.serverName : The server name for the WebLogic server, for instance adminserver.
• wls.port : The WebLogic server port number
• wls.username : The WebLogic user.
• wls.password : Password for the defined WebLogic user.

Warning and Critical Thresholds

You can define a warning and a critical threshold level for each surveyed property. If the level is reached or surpassed, the report indicates that the value needs further attention and that your system performance might be suffering.

Refer to troubleshooting for advice on how to proceed if you discover critical performance issues.

The properties file is preconfigured with default best-practice values.

• wls.jvm.maxheap.warning : 3000000000
• wls.jvm.maxheap.critical : 2000000000
• wls.jvm.heapusage.warning : 85
• wls.jvm.heapusage.critical : 90
• wls.jdbc.freeconnections.warning : 10
• wls.jdbc.freeconnections.critical : 2
• wls.jdbc.leakedconnections.warning : 1
• wls.jdbc.leakedconnections.critical : 10
• filesystem.minimumfree.warning : 10
• workflow.staletask.warning : 1
• workflow.staletask.critical : 1
• workflow.staleflow.warning : 1
• workflow.staleflow.critical : 1
• db.tablespaceused.warning : 90
• db.tablespaceused.critical : 95
• db.sessions.warning : 225
• db.sessions.critical : 175
• db.processes.warning : 150
• db.processes.critical : 125
• db.transactions.warning : 250
• db.transactions.critical : 200
• ping.warning : 300
• ping.critical : 100

Running the diagnostics report

1. Open the directory where you unzipped the report file.
2. Run diagrpt.sh. The console reply should be Email sent.

After running the report the first time, make sure to verify that the intended mail recipient did receive the mail containing the report.

Report scheduling

Automated Script Scheduling

Use the the script schedule_rpt.sh to schedule runs of the Diagnostics Report Job.

The script creates two jobs:

• run_rpt_with_email.sh scheduled daily at 5am/05:00 to run the report and send it as email attachment to the designated recipients.
• run_rpt_noemail scheduled.sh scheduled every 10 minutes to update the online report.

Manual Coding Scheduling

	su –
	crontab –e
	#Modify the line below, and copy it into the editor
	crontab -e @daily cd "<path_to_diagrpt>" ; ./diagrpt.sh;cd $OLD_PWD
	<ESC> wq!
	crontab -l
        	

Schedule Example A

	su -
	crontab –e
	@daily cd /home/oracle/Desktop/"PROCESSIT Diagnostics Report Generator"; ./diagrpt.sh cd $OLD_PWD
	crontab –l
	[root@processit ~]# crontab -l
	@daily cd /home/oracle/Desktop/"PROCESSIT Diagnostics Report Generator"; ./diagrpt.sh;cd $OLD_PWD
	[root@processit ~]#
				

Schedule Example B

	crontab –e
	@daily cd "/home/oracle/rs"; ./diagrpt.sh; cd $OLD_PWD
	crontab –l
	[root@processit ~]# crontab -l
	@daily cd "/home/oracle/rs"; ./diagrpt.sh; cd $OLD_PWD [root@processit ~]#
				

Troubleshooting

After the report is run, if some values exceed your standards or warnings are received, for troubleshooting and reporting issues, please refer to the PROCESSIT Troubleshooting Guide.