Performance Analysis Suite provides the performance best practice compliance checking for Maximo or TPAe based applications. With the new command line interface and report generation introduced sicne version 1.1.0, it can be integrated into Maximo or TPAe based applications to achieve "continuous compliance checking".
The integration can provide:
Continuous performance compliance checking for Maixmo and TPAe based applications.
Performance Analysis Suite is periodically launched by cron task instances configured in Maximo or TPAe based applications. Users can control how often the checking should be performance. The recommended frequency is once per day.
The reports of performance best practice compliance checking is preserved for later reference, along with the data collected from the environment during the compliance checking. The reports and the data collected and preserved can be sent to product support for further analysis upon requested.
Users can control how long to the past the history should be kept. Default is 50 results.
(Optional) Email notification can be enabled to notify upon the identification of violation of the performance best practice.
(Optional) Work orders can be generated automatically upon the identification of violation of the performance best practice, assigned to the designated owners.
(Optional) When work orders are to be generated, duplicate work orders do not get generated for the same kind of violation.
Here we provides a sample cron task implementation for you to easily setup such integration in your Maximo or TPAe based application environment. Following are the instruction for setting up such integration:
Initialize the crontask instance
Download the sample cron task implementation here. This implementation provides basic functionality mentioned here. Of course, you can further extend it based on your own needs.
Copy the cron task class to the maximo ear package and stop the WAS sevrer. Add the class into businessobjects.jar with the command like "jar -uvf businessobjects.jar custom\perfanalyst\*.class" and restart the WAS server (Formally, you should rebuild the ear package with the new added class).
Go To->System Configuration->Platform Configuration->Cron Task Setup->New Cron Task Definition to create a new cron task like this:
Specify a proper schedule to run this cron task (we recommend to run it once per day). As for the cron task parameters, only 2 parameters are required: "PerfAnalyst working directory" and the "Selected environment". Naturally, working directory is where you extracted Performance Analysis Suite on the server where the cron task instance runs (note: The working dir should not contains blanks for some JRuby bug.) and the environment name is the one you created for your environment. We also recommend to limit this cron task instance to only run on a specific JVM instance (see here for how to control it).
(Optional) If you wish to receive an email notification whenever there's violation to the performance best practice compliance checking identified, specified the email address in "Notify email" (multiple addresses allowed and are separated by comma). The default is admin user's email address.
(Optional) It is also possible have this cron task instance to generate a work order whenever there's violation to the performance best practice compliance checking identified.
When work order generation is enabled, you could create a result set inbox in start center to view all the work order related with some owner or description as your please.
In the generated work order, the violation report is attached as the attachment.
Click the attachments directly to view the violation report (in order to view doclinks, please follow the steps later to properly set it up):
Maximo won't manage documents through database but forwardly using a file path or URL (doclink) to link with the document. In order to access the generated reports by PerfAnalyst inside Maximo directly, we should config the doclink related properties of Maximo system properties and setup a http server to access the specific document by http protocol remotely.
For details, please see Setting up Attached Documents for Maximo 7.1. The following are the general steps (Windows, Linux or AIX are similar, just pathname difference):
Creating Attachment Directories: create a doclinks directory and some sub directories on the machine storing the document files. For example: C:\DOCLINKS. This directory should be put as the cron task parameter "Output base dir".
Configurate Http Server for Doclink:
1. Open the httpd.conf file for the IBM HTTP Server. (Backup httpd.conf)
Under C:\Program Files\IBM\HTTPServer\conf
2. Find ‘DocumentRoot’ and change like below
3. Find "# This should be changed to whatever you set DocumentRoot to" and change like below
4. Save that file and restart the HTTP Server
5. Verify that the HTTP Server is configured correctly:
Create a test file text.txt on C:\DOCLINKS\test.txt, then access it in browser: http://[server_name or IP]/test.txt
Using the servername from the httpd.conf file.
Or if you don't want to set a document root dir for the Http Server for some reason, you can specify a accessible dir as following:
Alias /doclinks "C:\doclinks"
IndexOptions NameWidth=25 Charset=UTF-8
Allow from all
Config system properties
1. Login to Maximo, and go to => System Configuration => Platform Configuration => System Properties
2. Check that the following Property Names have the listed values. If not, update them;
Property: mxe.doclink.doctypes.defpath Global Value: C:\DOCLINKS
Property: mxe.doclink.path01 Global Value: C:\DOCLINKS = http://<servername or IP> or Global Value: C:\doclinks= http://<servername or IP>/doclinks, if you don't set the document root for the http server but use a specified accessible dir.
Property: mxe.adminEmail Global Value: an valid email
Property: mail.smtp.host Global Value: smtp server name
3. Restart App server or Click ‘Live Refresh’