Home

User Manual

1. Jimys J2EE Is Monitoring Your System User Manual jimys_usermanual1 0 13 doc 20 10 05 User Manual Document Versions Version Reference Evolution Cause Date 1 0 0 UM1 0 0 Creation 11 08 2005 1 0 1 UM1 0 1 Complete 12 08 2005 1 0 2 UM1 0 2 Complete 17 08 2005 1 0 3 UM1 0 3 Correction 22 08 2005 1 0 4 UM1 0 4 Correction 23 08 2005 1 0 5 UM1 0 5 Correction 25 08 2005 1 0 6 UM1 0 6 Modification 29 08 2005 1 0 7 UM1 0 7 Complete 31 08 2005 1 0 8 UM1 0 8 Complete 01 09 2005 1 0 9 UM1 0 9 Complete 03 09 2005 1 0 10 UM1 0 10 Complete 03 09 2005 1 0 11 UM1 0 11 Correction 05 09 2005 1 0 12 UM1 0 12 Correction 06 09 2005 1 0 13 jimys usermanual1 0 13 Update for delivery 20 10 2005 jimvs usermanual1 0 13 doc 20 10 05 User Manual Table of Contents 1 INTRODUC TON MEE 1 2 ABOUT JIMXU i d p b 2 2 IN EE 2 NI A EEN 2 2 3 WHAT ARE THE ADVANTAGES TO USE JIMVS H 2 24 WHO MAVUSE E 2 20 NEIE EE 3 gt S AMIS SOURCES sie ne eee ene nee ee ene enn eee eS er ee ee eee eee ee 4 3 1 INTRODUC TION E 4 32 e Eegen TEE 4 Se UN SI ee FOLDE ee EE 6 l oe TO 6 3932 Gompile JIMVSJ ZEE saisies ni ie a aa ea Senai agn 6 EEN 7 9 4 JIMVOPROBES FOLDER a g a ia a tice ud tau nte ui busca Dc sdawul uu esee d aaa 7 S MEE 2 7 Sr CE 1016 8 a S EET Omm 7 343 Compiling the SOURCES secessit 9 4 GETTIN
2. jimvs usermanual1 0 13 doc Il 20 10 05 User Manual 1 Introduction This document describes the User Manual of the Jimvs tool The goal is to lead the user through the installation process to ensure the svstem is installed correctly It explains also how the different functionalities are used jimys_usermanual1 0 13 doc 1 20 10 05 User Manual 2 About Jimvs 2 1 What s Jimvs 2 Jimvs is a monitoring tool for the J2EE applications that aims to facilitate the operator s life It offers an advanced error detection feature through a alarms generation mechanism and a global view of the managed system status a tracking activity of the managed nodes through some graphical charts 2 2 Why Jimys Such tools are more and more required because the systems become very complex Humans meet huge difficulties to take care of all the components at the same time And when you deploy your application on a J2EE cluster the requirement is far more critical There are a very large number of events to examine that are generated at different levels system JVM J2EE application and on several nodes for a cluster configuration 2 3 What are the advantages to use Jimys Jimys tackles these issues the relevant informations for the supervision are gathered in a single graphical interface for the whole managed system the data are updated on the fly When a fault occurs the operator is notified The time of inter
3. fidji dc frec bull fr domain instance probe ujf mbean joramjmx Joram tvpe Destination name sal ifidji dc frec bull fr domain instance probe ujf mbean joramjmx Joram type Destination name sal fidji dc frec bull fr domain instance probe ujf mbean memo Chart 0 Select a probe fidji dc frec bull fr domain instance probe ujf mbean cpu Select Probe Chart 1 Select a probe fidji dc frec bull fr domain instance probe ujf mbean cpu Select Probe Chart 2 Select a probe fidji dc frec bull fr domain instance probe ujf mbean network fidji dc frec bull fr jonas jonas probe ujf mbeanzjonasjmx jonas 2eeType EntityBean name MyEr fidji dc frec bull fr jonas jonas probe ujf mbean jonas mx jonas 2eeType 2EEServer name jona fidji dc frec bull fr jonas jonas probe ujf mbean jonas mx jonas 2eeType DBCDataSource name fidji dc frec bull fr jonas jonas probe ujf mbean jonas mx jonas j2eeType TAResource name Ts fidji dc frec bull fr jonas jonas probe ujf mbean jonas mx jonas 2eeType StatefulSessionBean ni fidji dc frec bull fr jonas jonas probe ujf mbean jonas mx jonas j2eeType StatelessSessionBean fidji dc frec bull fr jonas jonas probe ujf mbean jonas mx jonas 2eeType StatelessSessionBean ag let re ga hater de Jones fd PER TYPE pan else fidji dc frec bull fr jonas jonas probe ujf mbean jonas mx jonas type Cache host
4. Jimys needs 2 topics and 1 queue to work correctly The name of them must be defined in the property files mediator properties and engine properties See the JOnAS documentation to configure the JMS topics and queue in JOnAS 4 3 Database Installation Jimys can be use in combination with for example a MySQL or PostgreSQL database e MySQL o Please refer to the MySQL installation manual at http www mvsal org e PostgreSQL o Please refer to the PostgreSQL installation manual at http www postgresal org 4 4 JimysJ2EE Installation 1 Extract jimvsJ2EE on vour disk 2 Make ant make dist with the build xml to create the distribution 3 Next step is the configuration 4 5 Installing the Jimvs probes module jimys_usermanual1 0 13 doc 10 20 10 05 User Manual Define a central machine where vou want to put all the libraries and mlet config file This machine needs to have a running http server Vou can use a JOnAS server which does the monitoring for this purpose Put the mletXY xml file on the HTTP server in a way that it is accessible through http host 9000 mletXY xml Put all the libraries which are referenced by the mlet file to the same place or to the url which is specified in the mlet file Copy the jimysProbes folder on all the machines which should be monitored You can delete the lib folder if you want to save disk space The only jars you absolutely need are dist bootJimvs ja
5. Begin time Disch 12 08 2005 Show Chart jimys_usermanual1 0 13 doc 42 20 10 05 User Manual 4 Enter the time to start with the monitoring If the field is empty the monitoring will start at the time the Show Chart button has been pressed Show Charts Begin time 14 19 17 12 08 2005 Show Chart 5 The user is redirected to the chart page that shows the different charts Monitor a Rule in a chart Main Charts Chart 1 4 More Parameters 11 56 00 11 56 30 11 57 00 11 57 30 11 58 00 11 58 30 samoa dc frec bull fr domain instance probe ujf mbean cpu fidji dc frec bull fr domain instance probe uf mbean cpu tonga domain instance probe ujf mbean cpu More Parameters 11 56 00 11 56 30 11 57 00 11 57 30 11 58 00 11 58 30 fidji de frec bull fr domain instance probe ujf mbean memorv samoa dc frec bull fr domain instance probe uji mbean memorv To remove an attribute from a chart it is only necessary to select the Remove Attribute button of an attribute Rulename cpul Attributename CPULoad Remove Attribute 7 4 4 2 Charts If the rules and the attributes have been selected then the chart is shown on this page This page is refreshed every 8 seconds automatically to get the latest state of the attributes jimys_usermanual1 0 13 doc 43 20 10 05 User Manual 7 4 5 Live Cluster check Ea Jimys Be Configuration
6. Select a rule net 7 Select Rule jimys usermanual1 0 13 doc 41 20 10 05 User Manual 2 Select an attribute of that rule Monitor a Rule in a chart Monitor a Rule in a chart Main Charts Select a rule fs1 Select Rule Select a rule fsl Select Rule Select an attribute Bee PEEP eee eee EEE eee Pee etree eee eer eee eee eee eee Add Attribute Isdbi average io in ms LOAD sda4 average io in ms LOAD sdal average io in ms LOAD sdb average io in ms LOAD sda3 average io in ms LOAD sdb average io in ms LOAD sda5 average io in ms LOAD sda average io in ms LOAD sda average iol LOAD 5 Out Chart 3 Select a rule fsi sl Select Rule Add Attribute Chart 1 Select a rule fs1 7 Select Rule Chart 2 Select a rule fs1 Select Rule Chart 3 Select a rule fs1 Select Rule 3 Other rules can be added to another chart Monitor a Rule in a chart Main Charts Chart 0 Select a rule cpui 7 Select Rule Select an attribute CPULoad Add Attribute EEI Attributename CPULoad Remove Attribute Chart 1 Select a rule memi Select Rule Select an attribute Memory 7 Add Attribute Rulename mem1 Attributename Memory Remove Attribute Chart 2 Select a rule net2 Select Rule Chart 3 Select a rule net2 7 Select Rule Show Charts
7. 8 20 10 05 User Manual 3 4 3 Compiling the sources There is an ant build script in the root of the directorv The different targets are clean o removes the compiled files and also the distribution jar files compile o compiles the sources jar o produces the JimvsProbes jar in the dist folder bootJar o produces the BootJimvs jar in the dist folder startProbes o Starts an MBeanServer and deploys all the probes defined in the mletXY xml specified in the monitoringXY properties file Consult the build properties file to change the path to the monitoringXY properties file Client o Starts a client thread which connects to a pump to retrieve the data This application illustrates how to connect to the pumps and retrieve the data You can extend this class in order to use the information collected by the pump Consult the build properties file to change the host and port to connect to jimvs usermanual1 0 13 doc 9 20 10 05 User Manual 4 Getting started 4 1 Environment The following tools and software are necessarv to run Jimvs correctiv e Host running JimysJ2EE o Linux Kernel 2 4 o Java Virtual Machine 1 4 8 o Apache Ant 1 6 2 o JONAS 4 6 o MySQL 3 2354 or PostgreSQL 7 4 or another JDBC compliant product e Clusternodes o Linux Kernel 2 4 4 2 JOnAS Installation Please refer to the JOnAS installation manual at hitp jonas objectweb org 4 2 1 Java Messaging Service configuration
8. 8 Mediator g E Rule Engine D Monitoring Cluster Status Monitor a Rule e Monitor a Probe in a chart e Monitor a Rule in a chart Live Cluster Check m Cleanup Database Cartography The live cluster check helps to get a real time check of the health of the cluster Live Cluster Check Connected to e samoa dc frec bull fr e fidji dc frec bull fr Live Cluster Check samoa dc frec bull fr Time Probe Identifier Status 1124277640407 samoa dc frec bull fr domain instance probe ujf mbean cpu 1124277640407 samoa dc frec bull fr domain instance probe ujf mbean network 1124277640408 samoa dc frec bull fr domain instance probe ujf mbean memory 1124277640408 samoa dc frec bull fr domain instance probe ujf mbean fileSystem 1124277640409 samoa dc frec bull fr domain instance probe ujf mbean log 1124277640410 samoa dc frec bull fr jonas jonas probe ujf mbean jonasjmx 1124277640411 samoa dc frec bull fr domain instance probe ujf mbean joram mx fidji dc frec bull fr Time Probe Identifier 1124277551654 fidji dc frec bull fr domain instance probe ujf mbean cpu 1124277551654 fidji dc frec bull fr domain instance probe ujf mbean network 1124277551655 fidji dc frec bull fr domain instance probe ujf mbean memory 1124277551655 fidji dc frec bull fr domain instance probe ujf mbean filesystem 1124277551659 fidji dc frec bull fr domain instance probe ujf mbean log 1124277551661 fidji
9. ADEngineEJB o This module contains everything which is necessary to work with the rule engine e MediatorEJB o This module corresponds to the mediator e DBCommunication o This module does the database access and contains the business logic EJB and hibernate e VisualizeJimys o This corresponds to the graphical user interface struts application e DroolsRAR o This is the resource adapter with the Drools rule engine e JimysCommons o This contains all the files that are shared between the modules e bin o Contains all installation and run scripts 3 3 2 Compile JimysJ2EE To compile JimysJ2EE use the build xml in the JimvsJ2EE s root folder These are the main targets e make dist o Using this target the complete distribution is build and ready to be deployed with the scripts This target builds the different modules and copies them with their libraries and configuration files into the distribution folder dist e clean_all o This cleans all class folders from the different modules and erases the output directory e update dist o Use this target if you have changed a configuration file and don t want to rebuild the complete project The configuration file is copied in the distribution folder and is ready to use e build all o This target builds the different modules in the output folder The build xml contains other targets which are not explained in detail These targets are for the different modules and can be used for example to
10. User Manual this list vou also have to specifv the probe specific properties which will be org objectweb jimys monitoredSystem probe NEW NAME 5 2 4 Probe specific configuration Each probe has specific properties which must be defined Some are mandatory some are arbitrary Mandatory e name o the object name of the probe in the mbeanserver This is the same name specified for the mbean in the mlet file e attributes o the list of attributes which are collected by the pump This is a list of attribute names which is available through the mbean interface of the mbean probe The different attributes are separated by a 5 e sampleTime o this is the time the pump waits to collect the attributes for the next time Arbitrary e init o Some probes must be initialized to work correctly For example the jonasjmx probe must be initialized to receive the correct url of the mbeanserver of jonas After initialization the probe is able to connect to the other mbean server and collect the data You have to look at the mbean interface of the probe to see how many attributes you must specify in the init property The init method of the probe mbean interface has only java lang String parameters The number of parameters depends on the probe Each parameter is separated by a jimvs usermanual1 0 13 doc 19 20 10 05 User Manual 5 2 5 The different probes In general All the possible attributes of the probe
11. compile precompile the jsp jimvs usermanual1 0 13 doc 6 20 10 05 3 3 3 User Manual Scripts installRun sh o The installRun script installs the different packages libraries and configuration files in JOnAS After the installation JOnAS starts and Jimys is deployed install sh o Installs the different packages libraries and configuration files in JOnAS javaCheck sh run sh o Starts JOnAS and deploys Jimys stop sh o Stops JOnAS uninstall sh o Remove the different packages libraries and configuration files from JONAS 3 4 JimysProbes folder 3 4 1 3 4 2 Folders dist o contains the libraries of the jimys probes This folder normally contains only 2 jars conf o contains the configuration files of the probes and the JMX server lib o contains all the necessary libraries in order to compile the distribution jars from the sources libMini o contains the minimum of libraries in order to be able to run the probes These libraries are the mx4j libs and also the xml implementation libraries Attention You must also have the lib BootJimvs jar in the dist directory to start the probes Important files startProbes sh o startup script to start the probe module You can modify this script in order to take advantage of a different configuration monitorXY properties build xml o The ant script to build the binaries from the sources The target bootJar produces the binary BootJimys jar The target
12. deprecated because you should use the jonasjmx probe which is based on the genericjmx probe Log o This probe analyses the monolog output and can be used in parallel of the jonasjmx probe This probe must be initialised The probe registers a jmx listener in monolog which runs in a second mbeanserver Cartography o This probe analyses the hardware of the system The data sent by this probe is constant as long as you do not have any hot pluggable architecture Therefore the sample rate should be very high This probe is based on the lewys probes and works only on linux systems Preferable kernel 2 4 x 9 Please ask BULL SA for additional information jimys_usermanual1 0 13 doc 20 20 10 05 User Manual e Sunjvm o This probe analyses the sunjvm This probe is deprecated because you should use the genericjmx probe This probe permits to monitor the specific mbeans inside a jvm 1 5 e Genericjmx o This probe is a generic probe which allows probing attributes of mbeans deployed on other mbeanservers In order to have multiple instances of the genericjmx probe you must have different configuration files See next chapter Furthermore you must specify a different name in the mlet file but always the same code That means you can have 2 entries in the mlet file which have as code GenericJmx but 2 different object names This probe must be initialised The first parameter of the init method specifies the mbeanserver ur
13. detail about which component produces an error Jimys Probe status of the Cluster Cluster jimys nok EI ujf mbean joram mx ok ujf mbean log ok ujf mbean cpu alert ujf mbean network ok uf mbean memorv component error 7 3 ujf mbean fileSystem component error EJOnAS j Jonas ok Jonas ok uf mbeanzjonasjmx ok ok Now the administrator can react on the problem jimys usermanual1 0 13 doc 97 20 10 05 User Manual 7 4 3 Monitor a Probe in a chart EP Administration Ee Jimys Ge Configuration l 8 Mediator I Rule Engine Ge Monitoring e show All Data e Cluster Status i Monitor a Probe in a chart e Monitor a Rule in a chart oe Live Cluster Check e Cleanup Database 9 Carto graphy 7 4 3 1 Main It is possible to have 4 different charts to monitor attributes of the different probes The following steps are necessary to monitor a probe attribute 1 Choose a chart and select a probe Monitor a Probe in a chart Monitor a Probe in a chart Chart 0 Select a probe fidji dc frec bull fr domain instance probe ujf mbean2cpu nn ifidji dc frec bull fr domain instance probe ujf mbean cpu fidji dc frec bull fr domain instance probe ujf mbean fileSvstem fidji dc frec bull fr domain instance probe ujf mbean joram mx Joram type Destination name C Edit dc frac bul fr damai instance probe lif irihenti jaramiri fora Eyne S Dextiabun afia jor
14. is a lightweight application and can run in parallel of some other java processes The distribution contains the following files and folders jimvsJ2EE build xml bin installRun sh install sh javaCheck sh run sh stop sh uninstall sh ADEngineEJB etc conf lib SIC MediatorEJB etc conf lib SIC JimysCommons SIC DBCommunication etc conf lib SIC VisualizeJimys jimys usermanual1 0 13 doc 4 20 10 05 User Manual WEB INF 4 resources 4 lib SIC DroolsRar etc lib SIC jimvsProbes startProbes sh build xml dist BootJimys jar JimysProbes jar conf config xml logging properties mlet xml mletHardware xml mletJonas xml mletJonasHardware xml monitor properties monitorHardware properties monitorJonas properties monitorJonasHardware properties probes joramProbeConfig xml probeconfig 414 xml lib 3 party libraries libMini mx4j jar mx4j jmx jar mx4j remote jar mx4j tools jar xercesImpl jar xml apis jar jimvs usermanual1 0 13 doc 5 20 10 05 User Manual 3 3 JimysJ2EE folder 3 3 1 Modules The following are the different modules being part of the distribution The different folders contain subfolders with their libraries deployement descriptor sources and configuration files The structure of the different folders can change in order to the needs of the modules e
15. jar produces the binary distribution JimvsProbes jar of the probes and the pump This jar is designed to be on a central place http jimvs usermanual1 0 13 doc 7 20 10 05 User Manual server and is downloaded dvnamicallv bv the probe module when this one starts This has the advantage that you only need to replace the jar on a single place The url is in the monitorXY properties which points to the mletXY xml The real url is coded in the mletXY xml file which is also placed on the central place Please consult chapter 4 5 for installation instructions or the JMX specification e Config xml o Configuration file of the mx4j server You can modify the port which is opened for the jmx server e Logging properties o Config file of the logger e mletXY xml o These files define the mlet configuration This file is intented to be stored somewhere on a web server But it is not mandatory This file defines all the MBeans which are loaded by the JMX server For example the mletJonas xml defines only the probes MBeans which are able to monitor jonas parameters like log jonas and joram You can also use the mletJonasHardware xmi and decide only to start the jonas probes But the specific libraries for the hardware probes will also be downloaded by the probe module In this file you define where the libraries are located codebase Normally this is a url which points to a web server url but you can also let the url point to
16. localhost path fidji dc frec bull fr jonas jonas probe ujf mbean jonas mx jonas type Cache host localhost path fidji dc frec bull fr jonas jonas probe ujf mbean jonas mx jonas type Cache host localhost path fidji dc frec bull fr jonas jonas probe ujf mbean jonas mx jonas type Cache host localhost path fidji dc frec bull fr domain instance probe ujf mbean cpu Select Probe Chart 3 Select a probe fidji dc frec bull fr domain instance probe ujf mbean cpu Select Probe jimvs usermanual1 0 13 doc 98 20 10 05 User Manual 2 Then select an attribute of that probe Monitor a Probe in a chart Select a probe fidji dc frec bull fr domain instance probe ujf mbean cpu Select Probe Select an attribute CPULoad Add Attribute Chart 1 Select a probe fidji dc frec bull fr domain instance probe ujf mbean cpu Select Probe Chart 2 Select a probe fidji dc frec bull fr domain instance probe ujf mbean cpu Select Probe Chart 3 Select a probe fidji dc frec bull fr domain instance probe ujf mbean cpu Select Probe 3 If necessary other attributes can be added to the same chart Monitor a Probe in a chart Main Chart 0 Select a probe fidji dc frec bull fr domain instance probe ujf mbean cpu Select Probe Select an attribute CPULoad si Add Attribute Probename fid
17. o Description the password to access the topic o Value anonymous 3 Engine queue e engine java naming factory initial o Description Java naming factory o Value com sun jndi rmi registrv RegistrvContextFactorv e engine java naming provider url o Description naming provider url o Value rmi localhost 1099 e engine mdb queue name o Description the name of the queue the engine binds to o Value queue e engine mdb queue connection factory o Description the connection factory for the queue o Value JQCF 4 Available pumps Here it is here possible to specify a list of know hosts where a pump is running With the help of this list it is not necessary to specify each host to connect but Jimys will show a selectable list to the user with the hosts e mediator pumpX o Description this indicates a host with a pump X is a number ascending from O to the number of hosts u Example mediator pumpO hostAB 1999 mediator pump1 hostCD 1999 o Value hostname port jimvs usermanual1 0 13 doc 14 20 10 05 User Manual 5 Cluster check These properties are used to make a live cluster check This check will return the health of the whole cluster e mediator attribute livecheck name o Description the attribute name of the pump MBean to receive the heartbeat o Value HeartBeat 6 Registered probes Attribute of the pump MBean to receive a list of the registered probes e mediator attribute registered probes name o
18. the file system That means you don t need to download the libraries dynamically from a webserver but you can also copy them somewhere on the file system This reduces the network load on startup e monitorXY properties o This file defines the mlet url and also which probes are started Furthermore it defines some parameters of each probe Attention this file is specified in the startup script startProbes sh This is one of the most important files for the probe module For the different svntax please look in chapter 4 5 for a detailed explanation of this file e joramProbeConfig xml o Configuration of the joram probe The syntax of this file is similar to the Jonas probe e probeconfig 414 xml o Configuration of the jonasjmx probe The syntax of this file is similar to the Jonas probe Remark The XY in the name of the monitoringXY properties and mletXY xml files is an alias for the different example files in the conf directory When XY is replaced by Jonas you use the jonas monitoring files Using the Hardware files let you monitor the hardware architecture Using the files where XY is replaced by nothing mlet xml you have all the available probes But be prepared to see some errors when using these files because some monitored resources are not running See the Java specification of JMX This probe has been developed by BULL SA This probe has been developed by BULL SA jimvs usermanual1 0 13 doc
19. the rules nn nnn nnne nnne nnn nnn nns 26 0 STAR STOP JIM a a M 27 6 1 USING THE GRIF KE 27 G2 MANUAU a irid i aa 27 621 Deplov ING ele ler Oe n ME m m m 27 6 2 2 Start the pump and orobes ccc cccccececaseaseeeeeeeeeeeceeeaeeeceeeeeeeeesesauaaaseeeeeeeeeees 27 6 2 3 Undeploy the application nn nnnnn men nnnn nanna nanna nanna n ann nn 27 7 USING THE WEB USER INTERFACE ccccceeeceeesesceeeessseeeeeeeeeeeeenseeeeneeeeeseeeeoeees 28 7 1 INTRODUCTION E 28 jimys_usermanual1 0 13 doc Il 20 10 05 User Manual Hee ETING CONNECT ED EE 28 7 3 CONFIGURATION MENU ME 28 Tl E e EE 28 rec MEE lu 1 de Le et e 1 EE 28 TMi MEE CC nd 29 7 3 1 3 Detail configurati serseri aren n 30 7 3 1 4 Mediator configuration ss nnnnnnnznnznnnnenznnnznnnnzzznna 31 Doce WAIN EE ege 32 Tore Fire ANC E 32 7 3 2 2 Activate Deactivate Rule seen 32 L323 SHOW CODIOQUEAL ON Lu isir 33 7 4 MONITORING MENU EE 34 rq Snow allat a eR E E 34 AD EE IUS Ec tesa ie lie d a ai da 35 7 4 3 Monitor a Probe in a chart en m Im Imm meme meer nre 38 7 4 3 1 a EE 38 E CCP Eu ee 40 TAA Monitor a H le nacharas n EE 41 1 4 4 1 WIGI ME 41 lg D AM RRERRRRR 43 SEMEN lt 1 IU i e e ERR 44 7 4 6 CGeanupdatabase eene nennen nenne nnns nsns nnne nnns nna as 45 Lo 0o EE 46 Se MERC te E i 47
20. ujf mbeanzjonasjmx jonas type Cache host localhost path jonasAdmin spareNotFoundEntries 500 samoa dc frec bull fr jonas jonas probe ujf mbean jonas mx jonas type Cache host localhost path jonasAdmin accessCount 1178 samoa dc frec bull fr domain instance probe ujf mbean cpu CPULoad 16 samoa dc frec bull fr jonas jonas probe ujf mbean jonas mx jonas type Cache host localhost path jonasAdmin hitsCount 1012 samoa dc frec bull fr jonas jonas probe ujf mbeanzjonasjmx jonas type Cache host localhost path jonasAdmin spareNotFoundEntries 500 samoa dc frec bull fr jonas jonas probe ujf mbean jonas mx jonas type Cache host localhost path jonasAdmin accessCount 1178 4 To change the level of the messages that should appear it is necessary to change the level and validate advice alert Warning notification note not specified monitoring cancel Afterwards it is necessary to select the host in the tree and the messages with the selected level will be displayed jimys_usermanual1 0 13 doc 36 20 10 05 5 Inacase of an error on a host the following state is shown Jimys Probe status of the Cluster e Cluster jimys nok The administrator sees that the cluster has a problem Selecting the cluster node he sees more information about the host that has a problem Jimys Probe status of the Cluster Fl Cluster jimys nok BL e nok Selecting the host he sees even more
21. Description the JMX attribute name to get the list of all the registed probes o Value RegisteredProbes 7 Change probe sample time e mediator attribute get probe sample time name o Description the name of the JMX attribute to get a probe sample time o Value getProbeSampleTime e mediator attribute set probe sample time name o Description the name of the JMX attribute to set a probe sample time o Value setProbeSampleTime 5 1 3 The DBManager The dbmanager properties file contains the configuration of the DBManager 1 database connection e database local home o Description name of the local stateful session bean home o Value DBManagerHome L e database remote home o Description name of the remote stateful local session bean home o Value DBManagerHome e database java naming factory initial o Description Java naming factory o Value com sun jndi rmi registry RegistryContextFactory e database java naming provider url o Description naming provider url o Value rmi localhost 1099 jimvs usermanual1 0 13 doc 15 20 10 05 User Manual 2 engine connection e engine web session name o Description The name of the home of the engine stateless session bean o Value EngineWebEJBHome e engine time session name o Description The name of the stateless session bean home used to initialize the timer to fire the rules o Value RuleFireTimerEJBHome e engine java naming factory initial o Description Java naming
22. G STARTED E 10 4 1 REEGELE 10 42 JONAS ER e EE 10 4 2 1 Java Messaging Service configuration sen ennnnnnnnnnnnnnnznznnnnzznznnzzna 10 4 3 DATABASE INSTALLATION EE 10 4 4 JIMYSJ2EE INSTALLATION cesses eene nn nnne nnn n nns nn ann n nnn ne nnn nnns 10 4 5 INSTALLING THE JIMYS PROBES MODULE sssusnnnnnnrenssrsrnnrrrrrrernssnrnrnrrrrrrrerersnrnrnrrenn 10 5 CONFIGURATION GUIDE sisuiciies iesu rra Uc REDE pee GE RV FEE RUADe aae tas sive in REECEa ba Duns iaa mnis cuc UEDE 12 S1 CONFIGURE JIMY SIZES 12 5 1 1 The Analysis Decision Engine essere 12 5 12 The Mediator PM 13 gka he DIB NAINA ON ian a a hadas nuni sas densi uU Ea OE 15 5 2 CONFIGURE THE JIMYS PROBE MODULE NEEN 17 S21 ER rulle Seege Idee 18 52 2 Admin configurator KE 18 5 2 3 List of the deployed porobes nn nnnennn nanna nn nanna nennen nnne nnns 18 5 2 4 Probe Specific configuration nr nara nara rna nnn nn 19 52 59 Thiedijlerent OCS eege eege 20 5 2 6 Configuration file of the GenericJmx probe sssseeennnnnnnnnnzzzznnananzznnznznzzzzznznza 22 G 22 5 4 CONFIGURE THE HIBERNATE misteri ein rta e e iii 23 Ge 02 24 597 elo elio Qalli e a a eter Pe E 24 052 Beliried BEE 24 599 Wite your OWMTUOS serii 25 5 5 4 Validate
23. MDBConnector mdb new MDBConnector mdb addProbeAttribute cpu CPULoad Integer cpu getAttributeByKey CPULoad toString mdb sendResult ALERT Your CPU is Integer cpu getAttributeByKey CPULoad intValue _LevelHelper ALERT cpu alarm 80 r1 mdb null 7 3 2 3 Show configuration This page shows the configuration of the Analysis Decision Engine It is not possible to change the configuration at runtime Rule Engine Activate Deactivate Rule Show Config database topic connection factory JTCF clustername jimys databas e java na ming provider url rmi localhost 3099 A EE DBManagerHome engine rar conne ction SAMPLERAR databas e topic conne ction password anonymo us databas e jav a naming factory initial com sun jndi rmi registry RegistryContextFactory datab as e topic co nnection username anonymous database topic name dbtopic This page does not list the parameter that can be found under Fire Rules jimys_usermanual1 0 13 doc 33 20 10 05 User Manual 7 4 Monitoring menu 7 4 1 Showa all data EB Administration Eva Jimys Be Configuration P e Mediator 6 Rule Engine Ge Monitoring amp Show All Data e Cluster Status e Monitor a Rule jem Monitor a Probe in a chart e Monitor a Rule in a chart e Live Cluster Check e Carto graphy Consulting the page Show All the user sees all messages in the database Show All Data
24. SamplingPeriod 10000 gt polls descriptor logdateformat dd MM yyyy HH mm ss logtimeformat HH mm ss gt poll name joramDestination gt lt discriminator gt Joram type Destination lt discriminator gt lt attribute list gt lt attribute gt attribute name NbMsgsDeliverSinceCreation attribute name attribute attribute attribute name NbMsgsReceiveSinceCreation attribute name attribute attribute attribute name NbMsgsSendToDMQSinceCreation attribute name attribute attribute list polls polls descriptor probe config Remarks e The attributes of the elements probe tasks and polls descriptor are not used by JimysProbes They are only there to be compatible with the J2EE probe e he element poll defines the name of the mbean to monitor You can use regular expressions like j2eeType JDBCDataSource This means that all the mbeans matching this expression will be pulled to collect the information e The attribute elements define which attributes of the mbean are pulled e You can have multiple poll elements which define different mbeans in the same mbeanserver to pull Like the sample configuration file of the jonasjmx probe 5 3 This probe was developed by BULL SA Please ask BULL SA for further information This probe was developed by BULL SA jimvs usermanual1 0 13 doc 22 20 10 05 User Manual 5 4 Configure the Hiber
25. Show All Detailed Result Time Stamp Result Message Level 1123834984862 Your RxNetworkLoad is 24 monitoring Filesystem to db not_specified 1123834985348 Your Memory is 98 monitoring Jonas Mbean received note 1123834985640 Jonas Mbean received note 1123834985653 Jonas Mbean received note 1123834985719 Jonas Mbean received note 1123834985731 Jonas Mbean received note 1123834985561 Jonas Mbean received note 1123834985825 Jonas Mbean received note 1123834985666 Jonas Mbean received note 1123834985745 Jonas Mbean received note 1123834985838 Jonas Mbean received note Jonas Mbean received note 1123834986066 Jonas Mbean received note 1123834986444 Jonas Mbean received note 1123834986524 Jonas Mbean received note 1123834986605 Jonas Mbean received note 1123834986666 Jonas Mbean received note 1123834986918 Jonas Mbean received note After selecting a timestamp the user is redirected to the Detailed Result and sees the detail of the message Show All Data Show All Show Result Detail Probeldentifier Attribute Name Attribute Value fidji dc frec bull fr domain instance probe ujf mbean network RxNetworkLoad 24 Here are the different probe attributes listed which belong to the message The probe identifier contains the hostname domain and instance to know exactly from which node of the cluster the event came jimys_usermanual1 0 13 doc 94 20 10 05 7 4 2 Cluster status Under cluster status it is possible to check the
26. ancel 1123835006682 fidji dc frec bull fr CPU gt 10 and hitsCount gt 2 alert Cancel 1123835006725 fidji dc frec bull fr CPU gt 10 and hitsCount gt 2 alert Cancel 1123835006666 fidji dc frec bull fr CPU gt 10 and hitsCount gt 2 alert Cancel 1123835009013 fidji dc frec bull fr CPU gt 10 and hitsCount gt 2 alert Cancel 1123835009064 fidji dc frec bull fr CPU gt 10 and hitsCount gt 2 alert Cancel 1123835009083 fidii dc frec bull fr CPU gt 10 and hitsCount gt 2 alert Cancel Selecting the timestamp of an alert the detail is shown on Show Alarm Detail page An alert can also been cancelled by selecting Cancel Show Alarms Show Alarm Detail Time Stamp Result Message Level Action 1123834994751 fidji de frec bull fr CPU gt 10 and hitsCount gt 2 alert Cancel 1123834999738 fidji dc frec bull fr CPU gt 10 and hitsCount gt 2 alert Cancel 1123835000329 fidji dc frec bull fr CPU gt 10 and hitsCount gt 2 alert Cancel The level of the alert is set to cancelled and not shown anv more on this page To view the alert detail it is necessary to consult Monitoring gt Show All Data jimys_usermanual1 0 13 doc 46 20 10 05 e Show Alarm Detail Alarms Show Alarms Show Alarm Detail Probeldentifier Attribute Name Attribute Value fidji dc frec bull fr domain instance probe ujf mbean cpu CPULoad 31 fidji de frec bull fr j jonas jonas probe ujf mbean jonasJmx j jonas type Cache hos
27. can be used MDBConnector o The connector helps to write the result of a rule in the database PumpCheckHelper o This helper checks if the pumps are still sending their data ClusterStatusHelper o This helper defines a method to check the whole cluster status and write it in the database if a change has occurred at runtime CartographyHelper o The CartographyHelper is used to extract the cartography from a cartography event and to write the data in the database LevelHelper o The LevelHelper has a set of define levels which are used to assign an alarm level to an entry in the database jimys_usermanual1 0 13 doc 25 20 10 05 User Manual Following events can be used To get more details please consult the External Specification in the chapter about interesting parameters to observe AbstractProbe Cpu Memory Network JonasMBean Joram Cjdbc Filesystem JonasLog Admin The following is what a rule should look like rule name rulesetname_ruleName gt Eaeh amp ulenhasea rulananie aad at teast one parameter The convention for the rulenarae 4gatis psed ia 5rslesetname rulename The ondittastis optional More conditions are possible The expression in the condition clause must be a boolean expression The cansequentecisceguired The consequence defines what to do when the conditiansr arestgdfilledoAs sbomnia the example thisruleowil whteiamessage to the console and add an entry in the database by using the MDBCon
28. db topic connection password mediator mdb topic connection factory mediator mdb topic connection username mediator connect pump engine java naming factory initial engine mdb queue name mediator pumps engine mdb queue connection factory mediator attribute livecheck name mediator java naming factory initial mediator java naming provider url engine java naming provider url mediator mdb topic name mediator attribute set probe sample Ume name mediator pump2 PumpConnectorHome_L anonymous JTCF anonymous m ujf mbean org objectweb jimys pump com sun jndi rmi registry RegistryContextFactory queue 3 JQCF HeartBeat com sun jndi rmi registry RegistryContextFactory rmi localhost 3099 rmi localhost 3099 topic 0 setProbeSampleTime fidji dc frec bull fr 1999 In this page it is possible to consult the configuration of the mediator which corresponds to the mediator properties file jimys usermanual1 0 13 doc 20 10 05 7 3 2 Rule Engine Ei Administration Onas Ge Jimys o Ge Configuration JOnAS Administration l 0 Mediator i e Rule Engine ne Weeer ch limys Configuration e Show All Data Rule Engine e Cluster Status Fire Rules Activate Deactivate Rule Show Config 7 TO Monitor a Rule Name Value oe Monitor a Probe in a chart i e Monitor a Rule in a chart e Live Cluster Check we Cleanup Database Fire rule after 1o events Modify jo ms Modify Rule f
29. dc frec bull fr domain instance probe ujf mbean cartography 1124277551661 fidji dc frec bull fr jonas jonas probe ujf mbean jonas mx 1124277551662 fidji dc frec bull fr domain instance probe ujf mbean joramjmx Connected to Not connected to a pump Live Cluster Check Your are not connected to a pump You need to be connected to at least one pump jimys_usermanual1 0 13 doc 44 20 10 05 User Manual Otherwise it is not possible to get a live cluster status 7 4 6 Cleanup database a Administration EA Jimys EB Configuration 7 6 Mediator 6 Rule Engine Ge Monitoring 6 Show All Data I e Cluster Status Le Monitor a Rue e Monitor a Probe in a chart i 8 Monitor a Rule in a chart S e Live Cluster Check Cleanup Database amp Alarms NT Cartography This page helps to clean up the database Cleanup Database Cleanup Database Cleanup entire database Are you sure that you wan t do cleanup the database This action cannot be undo Yes Cleanup a specific time period time format dd MM yyyy hh mm ss lif blank then start from day 0 To 13 20 11 17 08 2005 Clean The database can be cleaned up totally or only a specific time period can be erased e Total cleanup Cleanup entire database Are you sure that you wan t do cleanup the database This action cannot be undo Yes By selecting Yes the tables in the database are deleted e Time pe
30. e the sample time of the different probes and to show the actual configuration of the mediator jimvs usermanual1 0 13 doc 28 20 10 05 User Manual 7 3 1 2 Main In this page it is possible to see which pumps are connected to connect to new ones or to disconnect from pumps e Connected to Here are the pumps listed where the mediator is connected to Mediator Main Detailed configuration Mediator configuration Connected to Select pumps to disconnect from s amoa dc frec bull fr fidji dc frec bull fr Check if you wanna disconnect from all Disconnect Or the following if no connection can be found Mediator Main Detailed configuration Mediator configuration Connected to Your are not connected to a pump e Check the host s to connect to Check the hostis to connect to samoa dc frec bull fr fidji dc frec bull fr tonga dc frec bull fr Check if you wanna connect to all Connect Here it is possible to connect to the different pumps which have been specified in the mediator properties file jimvs usermanual1 0 13 doc 29 20 10 05 e Connect to host port Connect If a new host has been added at runtime in the cluster and should monitor it it is not necessary to stop Jimys At runtime it is possible to add new hosts to monitor by specifying the hostname and port where the probes run e Disconnect from host Disconnect Ente
31. eactivated at runtime Each rule which is listed here gets an activator and needs an entry in the file with the rules e engine rule rulesetName ruleName o Description indicates that the rule ruleName in the ruleset rulesetName is activable deactivable at runtime o Value true or false 5 1 2 The Mediator The configuration is done in the mediator properties file 1 Main configuration e mediator connect pump o Description the JMX object name of the pump which runs on the nodes o Value imvs mbean org objectweb jimvs monitoredSvstem pump e Mediator pump connect local home o Description the local stateful session bean home which is used by the mediator to connect to the different pumps For each pump a new session is created o Value PumpConnectHome L 2 Parser topic e mediator java naming factory initial o Description Java naming factory o Value com sun jndi rmi registrv RegistrvContextFactorv e mediator java naming provider ur o Description naming provider url o Value rmi ocalhost 1099 e mediator mdb topic name o Description the name of the topic the parser subscribes to jimvs usermanual1 0 13 doc 13 20 10 05 User Manual o Value topic e mediator mdb topic connection factory o Description the connection factory of the topic o Value JTCF e mediator mdb topic connection username o Description the username to access the topic o Value anonymous e mediator mdb topic connection password
32. factory o Value com sun jndi rmi registrv RegistrvContextFactorv e engine java naming provider url o Description naming provider url o Value rmi localhost 1099 3 mediator connection e mediator web session name o Description name of the mediator stateful session bean home o Value MediatorWebEJBHome e mediator java naming factory initial o Description Java naming factory o Value com sun jndi rmi registrv RegistrvContextFactorv e mediator java naming provider url o Description naming provider url o Value rmi localhost 1099 jimys_usermanual1 0 13 doc 16 20 10 05 User Manual 5 2 Configure the Jimvs probe module We will only explain the mletXY xml file and monitorXY properties file The config xml file can be modified according the mx4j documentation And the orobeconfig 414 xml configuration file of the jonas probe mletXY xml In this file you define all the MBeans which are deployed on the client machines monitored machines This file is intended to be accessible through a http url But you can also copy it to the file system One entry defines one MBean mlet code mbeanImplementationClassName name mbeanName archive libs vou need to download codebase urlWhereTheLibsAreLocated gt code o Theclass you name here is instantiated by the MBean server name o The Object name of the MBean With this name you are able to access the MBean archive o A list of jar files wh
33. ich are mandatory in order to instantiate the MBean That means if you instantiate a class in the MBean implementation specified by code this class must be in one of the archives defined here codebase o The url where the MBean server is able to download the jar files specified in the archive attribute Remarks Do not bother that the file is not a valid xml file No root node is specified You can define also mbeans here which are not used afterwards by the probe module It is possible to have a large mlet xml where all the possible mbeans are defined but in the monitor properties you specify which one are used by the pump Attention when you specify mbeans here the mbean server will instantiate them So it is possible that you receive some errors on start up For example when you specify the CJDBC mbean this probe will immediately try to establish a connection to the cjdbc server But when no server is running you will see an error This error will not cause any trouble for the other mbeans monitorXY properties This probe was developed by BULL SA Please ask BULL SA For additional information jimvs usermanual1 0 13 doc 17 20 10 05 User Manual We will explain how vou configure the JimvsProbes and which possibilities you have Global configuration of the MBean server e mlet file o defines the url where the mlet file is found This has to be a valid URL It can be on the file svstem or on a web se
34. ire timer interval Le Cartography 7 3 2 1 Fire Rules This page shows the configuration parameters of the Analysis Decision Engine that can be changed at runtime Rule Engine Fire Rules Activate Deactivate Rule Show Config Fire rule after po events Modifv Rule fire timer interval l me Modify If the parameters are changed at runtime the changes will be lost when restarting the system if they have not been added in the engine properties file 7 3 2 2 Activate Deactivate Rule This page contains the rules which can be activated and deactivated Rule Engine Fire Rules Activate Deactivate Rule rl cpu alarm 80 Active Deactivate r Deactive Active Deactivate Active Deactivate Deactive Active Deactivate n A KH lt ty E m n E D du i IT did r1 cpu trans Active Deactivate rl joram Activate Deactive rl cartl Active Deactivate rl cjdbcl Activate l Deactive 7 rl mem Active j Deactivate rl fsl Active Deactivate jimys usermanual1 0 13 doc 32 20 10 05 User Manual To see the detailed information of a rule it is only necessary to click on the name of the rule and the detail is shown to the user P Rulename rl cpu alarm 80 e Condition s Condition r1 cpu alarm 80 isActive Condition Integer cpu getAttributeByKey CPULoad intValue gt 80 Consequence Consequence
35. ji dc frec bull fr domain instance probe ujf mbean cpu Attributename CPULoad f Remove Attribute 1 Select a probe fidji dc frec bull fr domain instance probe ujf mbean cpu Select Probe Select an attribute cPULoad sl Add Attribute Probename samoa dc frec bull fr domain instance probe ujf mbean cpu Attributename CPULoad Remove Attribute Probename tonga domain instance probe ujf mbean cpu Attributename CPULoad Remove Attribute Chart 2 Select a probe fidji dc frec bull fr domain instance probe ujf mbean cpu Select Probe Chart 3 Select a probe fidji dc frec bull fr domain instance probe ujf mbean cpu Select Probe Show Charts Begin time 11 54 05 12 08 2005 Show Chart jimvs usermanual1 0 13 doc 39 20 10 05 4 Enter the begin time to start monitoring If the field is empty the monitoring starts at the time the Show Chart button has been pressed Show Charts Begin time 11 54 05 12 08 2005 Show Chart 5 The user is redirected to the charts page that will show the different charts Monitor a Probe in a chart Main Charts Chartl 4 More Parameters 11 5 20 11 57 30 11 57 40 11 57 50 11 58 00 11 58 10 11 58 20 11 58 30 oF nmn ou P ul On co Lab 11 57 20 11 57 30 11 57 40 11 5 50 11 56 00 11 56 10 11 58 20 11 58 30 11 58 40 samoa dc frec bull fr domain instance probe ujf mbean cpu CPULoad tonga domain insta
36. l of the mbeanserver to connect to The second parameter is the location of the configuration file and the third parameter is the name of the probe which must be different from the other probes A good example of using the genericjmx probe is the joram probe e Jonasjmx o This probe collects the data from a jonas instance This probe must be initialized If you want to monitor multiple jonas instances on the same machine you must specify in the mlet file 2 elements of this probe with different names You must also change the first and third parameters of the init method The configuration file may stay the same if you want to retrieve the same data e GenericLogFile o This probe collects the different events alert warning info produced by any application which writes a log file The log file must have different levels of messages and associate a timestamp to each event in the log file For exotic log files it is probably necessary to customize the GenericLogFile e Joram o Please consult the example of the joram probe which uses the GenericJmx probe jimys_usermanual1 0 13 doc 21 20 10 05 User Manual 5 2 6 Configuration file of the GenericJmx probe The svntax of the configuration file is identical to the contiguration of the Jonas probe Here is a small example lt xml version 1 0 encoding UTF 8 gt lt probe config gt lt probe tasks dateFormat yyyy_MM_dd_HH_ mm defaultRefreshPeriod 300000 default
37. nate The configuration of hibernate in Jimvs is done using 2 files hibernate cfg xml Hibernate configuration mapping hbm xml Database mapping file hibernate cfg xml Different properties must be specified in this configuration file All the information is related to the configuration of hibernate and the database No mapping information should be specified in this file e session factory name o The JNDI name of the session factory which is used to bind it in the JNDI tree e connection datasource o The JNDI datasource name This name is the datasource name of the database configured in JOnAS Default jdbc 1 e Dialect o The SQL dialect to use Please see the hibernate documentation for a complete list of valid values For example org hibernate dialect PostgreSQLDialect e show sql o Show the executed SQL strings at runtime e mapping resource o The mapping file name to use mapping hbm xml The mapping of all the java beans is done in this file You should not modify this file But it depends on how the database analyzes the SQL string The tables are created by the cmp2 beans the first time Now it is possible that the database interprets the SQL string case sensitive So it is possible that you have to see the table names after creation with a database tool and change the table names in the mapping hbm xmi file jimys_usermanual1 0 13 doc 23 20 10 05 User Manual 5 5 Rules The definition of the
38. nce probe uji mbean cpu CPULoad To remove an attribute from a chart it is only necessary to select the Remove Attribute button of an attribute kal tw a GI ka Sc Ala FALLI IK LILL l Probename fidji dc frec bull fr damain instance probe ujf mbean cpu Attributename CPULoad Remove Attribute 7 4 3 2 Charts If the probes and attributes have been selected then the chart is shown on this page This page is refreshed every 8 seconds automatically to get the latest states of the attributes jimvs usermanual1 0 13 doc 40 20 10 05 User Manual 7 4 4 Monitor a Rule in a chart g Administration Ea jimvs Ge Configuration Mediator 6 Rule Engine De Monitoring 6 show All Data Cluster Status e Monitor a Rule 6 Monitor a Probe in a chart 6 Monitor a Rule in a chart Live Cluster Check Cleanup Database Le Cartographv 7 4 4 1 Main It is possible to have 4 different charts to monitor the result of the different rules The following steps are necessarv to monitor a rule 1 Chose a chart and select a rule Monitor a Rule in a chart Monitor a Rule in a chart Chart 0 Chart 0 Select a rule Select a rule netz Select Rule Select Rule Chart 1 Select a rule net2 Select Rule Chart 2 Select a rule net2 Select Rule Chart 3 Select a rule net Select Rule Select Rule Select Rule Chart 3
39. nector lt java condition gt 5 5 4 Validate the rules lt java consequence gt The sSsteneoontatnsoa tulebase Validat6pto heck if theorute fikowkt the rules does MDB have any semamic emew IMemsures not tlhat the rules are doing the right thiig addProbe cpu mdb sendResult Your Cpu load is over 90 5 LevelHelper Alert cpul r1 java consequence ru be jimvs usermanual1 0 13 doc 26 20 10 05 User Manual 6 Start Stop Jimvs 6 1 Using the scripts The easiest wav to start stop Jimvs is to use the scripts that are in the jimvsJ2EE folder 6 2 Manuallv 6 2 1 Deplov the application To deplov Jimvs from scratch the following steps are necessarv Copy contents of jimysJ2EE dist apps to SJONAS BASE apps Copy contents of jimvsJ2EE dist conf to SJONAS BASE conf Copy contents of jimysJ2EE dist lib to SJONAS ROOT lib ext Copy contents of jimysJ2EE dist rars to SJONAS BASE rars Start JOnAS with jonas start Deploy Mediator jonas admin a Mediator ear Deploy the Rule Engine jonas admin a DroolsRAR rar Deploy ADEngine jonas admin a ADEngine ear Deploy DBManager jonas admin a DBManager ear PC ek skr 6 2 2 Start the pump and probes Use the scripts to start the pump and probes 6 2 3 Undeploy the application To undeploy Jimys e With JOnAS continuing to run 1 Undeploy Mediator jonas admin r Mediator ear 2 Undeploy the Rule Engine jonas admin r DroolsRAR
40. og content application level with either a generic JMX probe or a generic log probe Moreover a heartbeat mechanism checks both whether the managed system is alive and whether the probes are alive The processing module of Jimys relies on an original architecture based on Drools engine rules Through the inference motor Jimys allows to define high level rules for the filtering aggregating correlation of the events and even to implement some automatic behaviours that interact with the managed system supervision loop The centralized part of Jimys is a J2EE application on top of JOnAS The rules engine Drools is accessed through a RAR connector and the alarms are stored in a database such as MySQL jimys_usermanual1 0 13 doc 3 20 10 05 User Manual 3 Jimys sources 3 1 Introduction Jimys is delivered as a package with the different modules and configuration files The configuration has to be customized 3 2 Folder structure There are 2 main folders which contain the sources and binaries of the 2 main applications e he Analysis decision system module the User interface module and Storage module which are located in the folder JimysJ2EE This should be deployed on a standalone machine which monitors the other machines This is a heavy application which needs good hardware e he Probe module is located in the folder jimvsProbes This application should be deployed on the monitored machines This
41. r and the libs in the libMini folder You can also delete the source and build directory 5 Now the configuration of the probe module If you used in step 2 for example mletJonas xml please use now also the monitorJonas properties But it is not mandatory 6 Adapt the different urls in the monitorXY properties in order to match your network settings jonas port protocol and file system settings the absolute path to the probe jmx configuration files 7 Adapt the startProbes sh script in order to take the right monitorXY properties file as argument 8 Launch the startupProbes sh script and you hopefully see no errors Remarks The default port for the JMX server is 1999 f you try to monitor a JOnAS server or another JMX server this server needs to run before the probes are started Please be sure to have defined the JAVA HOME environment variable jimvs usermanual1 0 13 doc 11 20 10 05 User Manual 5 Configuration guide 5 1 Configure JimysJ2EE 5 1 1 The Analysis Decision Engine The engine properties file contains different properties which must be configured Different properties must be the same as specified during the configuration of JOnAS to work correctly Here are the configuration properties 1 Main configuration e clustername o Description the name of the cluster to monitor o Value jimvs e engine conf fire rule after o Description defines after how many recei
42. r the hostname to disconnect from 7 3 1 3 Detail configuration To see the sample time of the different pumps it is necessary to being connected to at least one host When not connected to any hosts Mediator Detailed configuration Mediator configuration Connected to Your are not connected to a pump If connected to some hosts Mediator Main Detailed configuration Mediator configuration Connected to a fidji de frec bullfr jimys_usermanual1 0 13 doc 30 20 10 05 User Manual After selecting a host the page will displav the different sample times that can be changed Mediator Main Detailed configuration Mediator configuration samoa dc frec bull fr Probe Name Current Sample Time New Sample Time ujf mbean network 3000 Change ujf mbean jonasjmx 5000 KI Change ujf mbean log 3000 D 1L e Change uf mbeanzjoramjmx 5500 MI Change ujf mbean memorv 3500 Change ujf mbean cpu 3800 Change ujf mbean fileSystem It is only possible to change one parameter at once 7 3 1 4 Mediator configuration Mediator Main Detailed configuration Mediator configuration mediator pump1 tonga dc frec bull fr 1999 mediator attribute get probe sample time name getProbeSampleTime mediator attribute registered probes name RegisteredProbes mediator pumpO samoa dc frec bull fr 1999 mediator pump connector local home mediator m
43. rar 3 Undeploy ADEngine jonas admin r ADEngine ear 4 Undeplov DBManager jonas admin r DBManager ear e With JOnAS stopping 1 jonas stop jimvs usermanual1 0 13 doc 27 20 10 05 User Manual 7 Using the Web User Interface 7 1 Introduction The Web User Interface is base on the JOnAS web interface jonasAdmin 7 2 Getting connected To connect to the Web User Interface use a web browser that supports Frames and CSS URL http host to connect to port VisualizeJimys To login use the username and password specified in the jonas properties Username jonas Password jonas 7 3 Configuration menu 7 3 14 Mediator 7 3 1 1 Introduction This configuration menu is used to connect disconnect to the different pumps of the cluster EB Administration SN Jimys Be Configuration Mediator JOnAS Administration e Rule Engine se Monitoring e Show All Data e Cluster Status OMonitora Rule connectada ss i e Monitor a Probe in a chart Select pumps to disconnect from Monitor a Rule in a chart e EE EE T samoa dc frec bull fr La Cieno Database fidji dc frec bull fr Alarms Check if you wanna disconnect from all Disconnect Se Cartography Check the host s to connect to tonga dc frec bull fr Check if you wanna connect to all Connect Connect to host port Connect Disconnect from host Disconnect It is also possible to chang
44. riod Cleanup a specific time period time format dd MM yyyy hh mm ss From if blank then start from day 0 To 13 20 11 17 08 2005 Clean It is necessary to indicate the beginning and ending of the period jimys_usermanual1 0 13 doc 45 20 10 05 User Manual 7 5 Alarms Administration Ea jimvs a Configuration x Mediator p e Rule Engine Be Monitoring Show All Data e Cluster Status 8 Monitor a Rule a e Monitor a Probe in a chart e Monitor a Rule in a chart l i Live Cluster Check e e Cleanup Database id Cartographv e Show Alarms This page shows all the alerts in the database Show Alarms Show Alarm Detail Time Stamp Result Message Level 1123834987438 fidji dc frec bull fr CPU gt 10 and hitsCount gt 2 alert Cancel 1123834994751 fidji dc frec bull fr CPU gt 10 and hitsCount gt 2 alert Cancel 1123834999738 fidji dc frec bull fr CPU gt 10 and hitsCount gt 2 alert Cancel 1123835000329 fidji dc frec bull fr CPU gt 10 and hitsCount gt 2 alert Cancel 1123835000339 fidji dc frec bull fr CPU gt 10 and hitsCount gt 2 alert Cancel fidji dc frec bull fr CPU gt 10 and hitsCount gt 2 alert Cancel 1123835001882 fidji dc frec bull fr CPU gt 10 and hitsCount gt 2 alert Cancel 1123835001904 fidji dc frec bull fr CPU gt 10 and hitsCount gt 2 alert Cancel 1123835006651 fidji de frec bull fr CPU gt 10 and hitsCount gt 2 alert C
45. rules is done in the rules dri file 5 5 1 Application data Application Data is data in the rule engine that is used by all the rules This data is not checked against a rule when it is inserted into the working memory The following data is necessary for the engine e pumps o tocheck the pump health at runtime e status o tocheck the clusterstatus at runtime The following data is optional e type of RuleActivator o This data is used to enable activation or deactivation of a rule The value must be an instance of RuleActivator The value should have the same name as the rule name This is the convention used If a ruleactivator is defined then it is necessary to define the same rule in the mediator properties file When data is not defined here then it will not be possible to use the activator 5 5 2 Defined rules The system has some defined rules These rules can be used or modified Each of these rules can be activated deactivated at runtime To handle this they all need a ruleactivator object Following rules are defined e pumpChecker o This rule checks every 40 seconds if the registered pumps are alive e checkProbesPumps o The rule checks the health of the whole cluster The rule is fired after having received an heartbeat from a pump e ri cpu alarm 80 o This rule generates an alarm if it receives a Cpu event and the CPULoad attribute is higher than 80 e ri CDU o This rule writes an entry in the database if it receive
46. rver e mlet name o defines the object name of the mlet bean in the MBean server when it is deployed This property may stay like this no need to change e mx4j config o the url where the configuration file of the mx4j server is stored Remark From now on we will not repeat the prefix org objectweb jimys monitoredSystem for each property 5 2 1 Pump configuration e pump name o the object name of the pump mbean in the mbeanserver e pump compress o enable disable the compression on the pump Enabling the compression reduces the amount of data send over the network but increases the cpu load on both sides When you use a client or the mediator of JimysJ2EE you must also enable the decompression to be able to see the data e pump sampletime o Specify the sample rate of the pump This is the time between two messages sent from the pump to the client mediator This parameter is arbitrary if not specified the sample rate is 5 seconds 5 2 2 Admin configuration e admin name o the object name of the admin mbean in the mbeanserver 5 2 3 List of the deployed probes e probes o the list of the probes which will be registered in the pump Do not confuse with the mbeans which will be deployed on the mbeanserver These are specified in the mlet file Each name of the list is separated by a 57 The names specified may be extended and customized But when you specify a new name in jimys usermanual1 0 13 doc 18 20 10 05
47. s a Cpu event and checks the attribute CPULoad e ri memi o This rule writes an entry in the database if it receives a Memory event e ri neti o This rule writes an entry in the database if it receives a Net event and checks the attribute RxNetworkLoad jimys_usermanual1 0 13 doc 24 20 10 05 User Manual ri fsi o This rule writes an entry in the database if it receives a FileSvstem event ri Ui o This rule writes an entry in the database if it receives a JonasLog event ri cjdbci o This rule writes an entry in the database if it receives a Cjdbc event ri jonasi o This rule writes an entry in the database if it receives a JonasMBean event ri joram1 o This rule writes an entry in the database if it receives a Joram event ri carti o This rule writes the actual cartography in the database ri cpu trans o This rule write an alert in the database if it receives from the same host a Cpu event and a JonasMBean event where the CPULoad is higher than or equal to 10 and the JonasMBean hitsCount of the cache is higher than or equal to 2000 killer o This rule retracts every object that is longer than 60 seconds in the working memory 5 5 3 Write your own rules To write your own rules it is necessary to understand the methodology adapted by the rule engine vendor to write the rules and how the rule engine works Please consult first the documentation about Drools at www drools org To write the different rules different helper
48. s which may be monitored must be in the interface of the probe mbean If you want to add a new attribute you have to add the method of in the interface Cpu o This probe can monitor the load of the CPU We chose not to use the CPU probe of the lewys probes because we had some problems to calculate the load This probe only works on linux OS The load is calculated by taking two snapshots of the data in the proc file system proc stat for a given time between the snapshots The load is calculated data2 data1 time2 time1 100 Network o This probe analyses the network traffic Rx Tx The load is calculated the same way than the cpu The probe is based on the lewys probes Memory o This probe calculates the memory usage of the system The probe is based on the lewys probes Filesystem o This probe calculates the IO load of the file system The probe is based on the lewys probes Cjdbc o This probe collects information of the cjdbc Attention this probe must be initialized The probe is based on the lewys probes Apache o This probe collects the log of the apache web server This probe needs to be initialised in order to be able to find the log file Attention this probe opens the file and reads the whole file If you have a large log file you may encounter performance problems Jonas o This probe is a wrapper around the j2ee probe developed by BULL SA This probe needs to be initialised Attention this probe in jimys is
49. state of the cluster Z iB Administration EX Jimys Be Configuration v Mediator 6 Rule Engine C Monitoring 6 Show All Data q e Monitor a Rule Monitor a Probe in a chart oe Monitor a Rule in a chart v6 Live Cluster Check E Cleanup Database e Cartography To get real time values it is necessary to be connected to the different cluster nodes otherwise old data from the database is shown Cluster Status The following steps are necessarv to get the status 1 Enterthe name of the cluster Cluster Status 2 Select the branch of the tree to have a more detailed view Jimys Probe status of the Cluster e Cluster jimys ok jimys_usermanual1 0 13 doc 35 20 10 05 3 Select a hostname to see more detailed information about a specific host Jimys Probe status of the Cluster ujf mbean joram mx ok ujf mbean memory ok E uf mbean filesvstem ok Ej JOnAS jonas ok Fl jonas ok ujf mbean jonas mx ok ok The detailed information ujf mbean memory ok ujf mbean filesvstem ok EJOnAS Ejonas ok jonas ok ujf mbean jonasJmx ok ok Probeldentifier Attribute Name Attribute Value samoa dc frec bull fr domain instance probe ujf mbean cpu CPULoad 16 samoa dc frec bull fr jonas jonas probe ujf mbean jonas mx jonas type Cache host localhost path jonasAdmin hitsCount 1012 samoa dc frec bull fr jonas jonas probe
50. t localhost path jonasAdmin hitsCount 2551 fidji dc frec bull fr j jonas jonas probe ujf mbeanzjonasjmx ji jonas tvpe Cache l host localhost path jonasAdmin spareNotFoundEntries 500 fidji dc frec bull fr jonas jonas probe ujf mbean jonas mx jonas type Cache host localhost path jonasAdmin accessCount 2854 7 6 Cartographv EB Administration E Jimys e Configuration Mediator e Rule Engine E e Monitoring 8 Show All Data P amp Cluster Status e Monitor a Rule Monitor a Probe in a chart Ed Monitor a Rule in a chart ux e Live Cluster Check Le Cleanup Database e Cartographv To show the cartographv it is necessarv to be connected to at least one pump Cartography Cartography Your are not connected to a node you need to be connected to at least to 1 pump Select a host to get his cartography No Cartography for host found Cartography Cartography Select a host to get his cartography samoa dc frec bull fr 6 fidji de frec bull fr Get No Cartography for host found jimys_usermanual1 0 13 doc 47 20 10 05 Choosing a host and selecting Get the cartographv of that host is shown to the user Cartography Cartography dentifier Value idji dc frec bull fr domain instance probe ujf mbean cartography_C ice 1166 Type Host bridge PCI device 1166 rverWorks CNB20HE Type kima mini iri ve xull fr domain instance probe ujf mbean cartography Con
51. troller Tec pull fr dom in instanc H robe ijf mb f frec bull fr domain instance probe ujf mbean cartography_Controller_Se jimys_usermanual1 0 13 doc 48 20 10 05
52. ved events the rules are fired o Value 10 e engine conf fire interval o Description defines in milliseconds after how many milliseconds the rules are fired If the value is O then the timer is inactive o Value 0 e engine rar connection o Description this parameter indicates the JNDI name of the resource adapter for the rule engine o Value JimvsDrools e engine conf use listener o Description Setting this property to true the system informs the user when an object has been asserted retracted from the rule engine and counts the events into the working memory o Value false 2 Database topic connection e database java naming factory initial o Description Java naming factory o Value com sun jndi rmi registrv RegistryContextFactory e database java naming provider url o Description naming provider url o Value rmi localhost 1099 e database remote home o Description Remote home of the DBManager o Value DBManagerHome jimys_usermanual1 0 13 doc 12 20 10 05 User Manual e database topic name o Description the jms topic the DBManager subscribes o Value dbtopic e database topic connection factory o Description the name of the topic connection factory o Value JTCF e database connection username o Description topic username o Value anonymous e database connection password o Description topic password o Value anonymous 3 Rules The following properties specify the rules which can be activated or d
53. vention is reduced and since the MI TR Mean Time To Repair is reduced the MTBF is improved Moreover Jimys is based on a rules engine that leverages its flexibility Such tool allows to automatically sort and analyse the huge amount of events that may be raised by the system in order to provide the administrator with only the relevant information It also allows customizing the error detection rules in order to adapt them at your administration policies Even the actions can be enhanced to implement in addition of the alarm generation for example a mail sending or a reconfiguration task on the managed system 2 4 Who may use Jimys All the users who have to deal with complex monitoring tasks for example to supervise a clustered J2EE application to supervise a set of standalone J2EE applications jimvs usermanual1 0 13 doc 2 20 10 05 User Manual 2 5 Inside Jimvs Jimvs provides both the probes infrastructure enabling the retrieving and the gathering of the events on the managed nodes and a centralized analysis decision module being able to process these events on the fly and yields alarms or status for the operator A lot of probes are already available to supervise different levels on the managed nodes system level with a CPU probe a memory probe a network probe and a disk probe JVM level with a JDK 1 5 probe J2EE level with a JMX probe polling the JOnAS s MBeans or a JOnAS log s probe retrieving the l

User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents