tirsdag 1. mars 2016

IBM APM versions

IBM Application Performance Management comes in four editions. There is a good explanation in the knowledge center on differences:
APM offerings 

If you need standard OS and application monitoring you can normally use the basic version which is IBM Monitoring. It also includes the "Realtime transactions agent" which listens for HTTP-traffic. This is something you will use on your webservers to analyze web-traffic and it's quite powerful. Not many other products has this capability in the price-range that IBM Monitoring is in.

The IBM Application Performance Management edition adds in transaction tracking and a really cool dependency analyzer which draw your application topology. It does not work for everything, but I've seen it work very well with WebSphere.

There are a few more agents in this version which is not in the IBM Monitoring package.

IBM Application Diagnostics is for environments with WebSphere and/or WebSpehre Liberty Profile. It provides deep-dive functionality for such environments and it's a great tool to have in place.

IBM Application Performance Management Advanced is IBM Application Diagnostics + IBM Application Performance Management.

Prepare your onprem RedHat Linux for IBM APM v8 server

To install APM v8 on an on-premise server you need to install 64-bit RedHat Linux and make sure you have the pre-reqs in place. You can consult the documentation here:

IBM APM 8.1.2 Knowledge Center guide

These are my steps to perform successful installation:

1. Make sure you use a 64-bit distribution of RedHat Linux. This guide is based on RedHat version 6.6
2. I provide it with 4 cores and 16GB memory along with a 100GB thin provisioning disk.

3. Follow the normal steps to install RedHat, but do a manual disk partitioning

 4. /opt is where data will be stored so this is where you want as much space as possible. You will also need some playground in /tmp to work with agent images later on. 4-5GB is normally sufficient. This is an example of my partition-layout. Make sure you use at least 4000MG (4GB) for Swap, otherwise the prereqchecker will be annoyed.
5. I prefer to install X-gui, but it's not a requirement for APM.

6. When it's done installing RedHat, install VMware tools or the device drivers you need to make it work. Also make sure your hostname is registered in dns or manually updates the hosts file. It must be able to ping itself by hostname. Set a static ip-address.

7.  Next step is to configure yum. It is not a prereq but it will make your life easier later on. If you like to update the RedHat operating system you can do it at this point.

Note: you must have kernel 2.6.16 or higher and there are known problems with 2.6.32-434 to 2.6.32-504.7.1. In this guide I use 2.6.32-573.12.1.el6.x86_64
If you are not sure type:
uname -r


8. Next we need to disable selinux.
vi /etc/selinux/config



change

SELINUX=enforcing

to SELINUX=disabled

save and exit. This change require a reboot, but let's perform the other steps first.

9. I prefer to turn off the Linux firewall while I'm installing until I'm sure that everything works. I can configure it and turn it back on later.

chkconfig iptables off   
chkconfig ip6tables off

10. You need to change ulimit so that the OS will allow more open files. To see what is the current setting type
ulimit -n (must be greater than 10000)
ulimit -u (must be 4096 or more)
 
I prefer to set these permanently by editing /etc/security/limits.conf
In the bottom of the file enter these two lines:

root    soft    nofile  32768
root    hard    nofile  32768

root    soft    core    unlimited

Save and exit the editor. A reboot is required to active the changes. Perform the next step before rebooting.

11.  Install additional packages in RedHat. If you have set up a yum-connection this should be pretty simple:
yum install ksh
yum install pam.i686
yum install sg3_utils
yum install libstdc++.x86_64
yum install libstdc++.i686

Some of the packages might have dependencies.

12. Reboot the server and perform the following steps when it comes up to make sure everything is OK:
sestatus (should be disabled)
service iptables status  (should not be running)
service ip6tables status  (should not be running)

You are ready to start installing APM.


 . 

mandag 3. mars 2014

First things first

This is supposed to be an easy introduction to get IBM Monitoring products up and running with the least effort possible. I will try to write in a way that you do not need any pre-knowledge with any of the products.

You will of course need IT knowledge, knowledge of operating systems, network and management in general. Consider that as a pre-req. Comments and additions are welcome.