Monitor Java or Java EE or apache tomcat application servers

The goal of JavaMelody is to monitor Java or Java EE application servers in QA and production environments. It is not a tool to simulate requests from users, it is a tool to measure and calculate statistics on real operation of an application depending on the usage of the application by users.

JavaMelody is opensource (LGPL) and production ready: in production in an application of 25 person years. JavaMelody is easy to integrate in most applications and is lightweight (no profiling and no database).

JavaMelody is mainly based on statistics of requests and on evolution charts.

It allows to improve applications in QA and production and helps to:

DataStage Run-Time Error 13 Type Mismatch

For those who just want the fix the steps are as follows. I recommend backing up your registry before attempting any of these steps.

1. Close all instances of the datastage client applications.

2.Start->run

3. regedit.exe

Starting Your Software Automatically on Boot

The way Linux starts (and stops) all its subsystems is very simple and modular. Lets you define initialization order, runlevels etc

From BIOS to Subsystems

Lets review what happens when we boot Linux:

1. The BIOS or a bootloader (lilo, zlilo, grub, etc) loads Linux Kernel from disk to memory, with some parameters defined in the bootloader configuration. We can see this process watching the dots that appear in the screen. Kernel file stays in the /boot directory, and is accessed only at this moment.
2. In memory, Kernel code starts to run, detecting a series of vital devices, disk partitions etc.
3. On of the last things Kernel does is to mount the / (root) filesystem, that obrigatoriamente must contain the /etc, /sbin, /bin and /lib directories.
4. Immediately behind, calls the program called init (/sbin/init) and passes the control to him.
5. The init command will read his configuration file (/etc/inittab) which defines the system runlevel, and some Shell scripts to be run.
6. These scripts will continue the setup of system's minimal infrastructure, mounting other filesystems (according to /etc/fstab), activating swap space (virtual memory), etc.
7. The last step, and most interesting for you, is the execution of the special script called /etc/rc.d/rc, which initializes the subsystems according to a directory structure under /etc/rc.d. The name rc comes from run commands.

Cognos init.d startup script for Linux | Startup/shutdown script for Cognos applications on Unix

Cognos init.d startup script for Linux | Startup/shutdown script for Cognos applications on Unix


# vi /etc/init.d/cognos

past the below mentioned script in it.

#!/bin/sh
# chkconfig: 345 99 10
# description: cognos auto start-stop script.

export JAVA_HOME=/usr/java/jdk1.6.0_32
export JRE_HOME=/usr/java/jdk1.6.0_32/jre

RETVAL=0

case "$1" in
    start)
      /opt/ibm/cognos/c10_64/bin64/cogconfig.sh -s
      RETVAL=$?
  ;;
    stop)
      /opt/ibm/cognos/c10_64/bin64/cogconfig.sh -stop
      RETVAL=$?
 
  
      exit 1
  ;;
esac

exit $RETVAL


:wq!

#chmod a+x cognos
#chkconfig --add cognos
#chkconfig cognos on