If your new to or just need to learn more about AWS.. this is a great slide presentation I stumbled across

As of ITM 6.2.1, there is a perceived capability to now rename situations within the editor.

However, the rename is actually a new attribute called ‘Full Name’ and only changes the TEPS display name for the situation; the EIF will still send the original situation name.

IBM responds this is “working as designed” — a load of crap if you ask me and a “feature” that should not have been introduced at all if it were to be so counter-intuitive.

Here’s IBM’s response:

Problem(Abstract)
Situation names that are less than 32 characters in length do not populate the “Fullname” field when running the ‘tacmd viewsit -s ‘ command.

Symptom
tacmd viewsit shows null Fullname Field

Cause
The Fullname field is only populated when the original situation name is 32 characters or greater or if a situation name is changed.

Resolving the problem
When a situation is created with a name less than 32 characters in length, the situation name is stored in the “Name” column. At this point, the “Name” column serves two purposes: a unique ID for the situation and the situation display name. The “Fullname” column is blank.

If an existing situation name is changed, the “Name” column still serves as the unique ID and will not be updated to reflect the situation name change.

The new situation name is stored in the “Fullname” column, the new name now assumes the role of situation display name. The length of the new name does not matter, the new name must be stored in the “Fullname” column, since the “Name” column containing the unique ID cannot be changed.

The only time we should expect the “Full Name” field to be populated is when the original situation name is 32 characters or greater or when a situation name has changed from it’s original name (regardless of the length of the new situation name).

In a nutshell: use the ‘eventcreate‘

I had an issue with ITM Windows Agent creating events which I was then sending out email alerts via a UNIX script.

The simple problem was backslashes in windows paths where the “Take Action” notification script was literalizing characters which might be part of the EventLog Description

For example:

"c:\Damned these\nagging\slashes\argh"

became

c:\Damned these
agging\slashesrgh

Yes, simply quoting my string would have solved most of my problem, IT DID HOWEVER lead me to a handy windows command for testing, called ‘eventcreateid‘

Example : eventcreate /ID 101 /SO FooBar /D “Test Message for ITM” /T ERROR /L Application

Installing a LAMP stack: Linux – Apache, PHP, and MySQL on Fedora Core

Assuming you already have Linux and Yum installed.

1. Install Apache (httpd), PHP, MySQL (server and client), and the component that allows
php to talk to mysql.

 yum -y install httpd php mysql mysql-server php-mysql

2. Configure the new services to start automatically

  /sbin/chkconfig httpd on
  /sbin/chkconfig --add mysqld         [this is not required with FC4 and above]
  /sbin/chkconfig mysqld on

  /sbin/service httpd start
  /sbin/service mysqld start

3. IMPORTANT! Set up the mysql database root password. Without a password, ANY user on the box can login to mysql as database root. The mysql root account is a separate password from the machine root account.

 mysqladmin -u root password 'new-password'           [quotes are required]

4. Make additional security-related changes to mysql.

 mysql -u root -p

 mysql> DROP DATABASE test;                            [removes the test database]
 mysql> DELETE FROM mysql.user WHERE user = '';        [Removes anonymous access]
 mysql> FLUSH PRIVILEGES;

5. Following the above steps, the document root for Apache is /var/www/html/

Create a test PHP script (such as phpinfo.php) and place it in the document root. A useful
test script sample:

 <?php
    phpinfo();
 ?>

6. Create a database and database user for your data. You will use this database and user name
in your database connection string. The GRANT statement actually creates a new MySQL user account.

 mysql> CREATE DATABASE web_db;
 mysql> GRANT ALL PRIVILEGES ON web_db.* TO 'web_user'@'localhost' IDENTIFIED BY 'thepassword';

I was experimenting with WAMP on my laptop, not a big deal in itself, but when I rebooted the Apache server failed to start.

Event logs showed something else had already been binded to port 80.

Quick Fix was to determine which PID had it by running the following:
netstat -ano
From there you can use task manager, determine the conflicting process, kill the PID.

(If you had CYGWIN installed)
netstat -ano | grep :80
ps -Wef | grep <pid> # To determine the process
kill -9 <pid>

DOWNLOAD:  

The ‘um_cleanup’ script that comes with ITM6 Universal Agent I’m convinced was written by an intern or co-op who just learned the basics of scripting.

I “rewrote” the whole darn thing with the following comments and syntax:

um_cleanup_jds.ksh -h
USAGE: um_cleanup_jds.ksh [UA|CMS|CNPS|ALL]


ITM 6.2 FP1 contains several new and changed T/EC class changes, ranging from new classes, new slots, and only ONE new slot (omnux_value replacing kux_value).

**I have not seen an ITM event containing kux_value nor omnux_value, but to be safe, I added the old ‘kux_value’ slot to the kux.baroc file.

TOTAL: 22 baroc files

Reference: http://help.mosso.com/article.php?id=180

Your script is calling for the “REMOTE_ADDR” and receives the IP of a server in front of one of our back-end servers. The web facing server is then passing the scripts output without giving the expected REMOTE_ADDR of the visitor. In order for your scripts to recognize that they are on a cluster and log the correct IP of your visitors, you will need to replace and add the code below.

For PHP:
Locate any lines of code that are similar to this snippet of code,
$_SERVER['REMOTE_ADDR'];
And replace it with this snippet of code,
$_SERVER['HTTP_X_CLUSTER_CLIENT_IP'];

For ASP:
Locate any lines of code that are similar to this snipper of code,
Request.ServerVariables(“REMOTE_ADDR”)
And replace it with this snipper of code,
Request.ServerVariables(“HTTP_X_CLUSTER_CLIENT_IP”)

My fix for this required a unix shell (if you’re on a Windows look at installing cygwin on your system.

# Ftp your web content down to your local system

$ for file in `find <path_to_files> -exec grep -l REMOTE_ADDR {} \;`; do base=`basename $file`; sed ‘s/REMOTE_ADDR/HTTP_X_CLUSTER_CLIENT_IP/g’ $file > /tmp/$base; grep HTTP_X_CLUSTER_CLIENT_IP /tmp/$base >/dev/null 2>&1 && grep REMOTE_ADDR $file && echo “Updated $base” && mv
/tmp/$base $file; done

# Then simply upload the changed files to your system.

Not all of them mind you, but some important ones none-the-less:

• KFW_STARTJVM=N
• KFW_USE_EMBEDDED=Y
• KFW_EWAS_SERVER_PID_FILE=C:\IBM\ITM\CNPSJ\profiles\ITMProfile\logs\ITMServer\ITMServer.pid
• KFW_EWAS_STARTSERVER_SCRIPT=C:\IBM\ITM\CNPSJ\profiles\ITMProfile\bin\startServer.bat
• KFW_EWAS_STOPSERVER_SCRIPT=C:\IBM\ITM\CNPSJ\profiles\ITMProfile\bin\stopServer.bat

I verified the following by modifying all the variables in my %CANDLEHOME%\CNB\kfwenv file where numerical values like ports and max where incremented by one, and the string vlaues had _XXX_ inserted

The modified kfwenv was backed up, then I reconfigured the TEPS and ran a diff on both files, and the above variables are the resulting default values.