How to determine which change is using a certain workflow

When there is an active instance using a certain workflow process, it can't be disabled. To see which work order is using a certain workflow, go to the Workflow Administration application. It lists al active process and allows to stop them.

Comparing TADDM performance on different platforms

Introduction

This document compares the running time of running discovery in TADDM 7.1.2 on a virtual environment (VMware ESX) and a non-virtual environment. This is not an comprehensive test, and should not take as TADDM performance result, but just as a comparison study of the TADDM Server in different platforms.

Platforms

Virtual environment

Linux RedHat Enterprise Server Release 5
2 vCPU
3600 MB
VMware ESX, with just 1 VM running

Non-virtual Windows environment

Windows 2003 SP2
2 CPUs
3200 MB
TADDM 7.1.2 and DB2 collocated in one server

Non-virtual Linux environment

Linux RedHat Enterprise Server Release 5
2 CPUs
3200 MB
TADDM 7.1.2 and DB2 collocated in one server

Two server, non-virtual environment

TADDM Server in the Windows environment above
DB2 Server in a separate machine, same specification as the server above

Target environment

37 Computer Systems, consisting of Windows, AIX, HP-UX, Solaris and Linux machines.
Number of components found: 315 (3 Server Equivalents)

Running time

Running time	Virtual environment	Windows environment	Linux environment	Two-server environment
Level 3 Discovery	30 min 47 sec	8 min 49 sec	28 min 37 sec	6 min 4 sec
Level 3 Discovery without WebSphereCellSensor	10 min 36 sec	7 min 43 sec	6 min 16 sec	5 min 8 sec
Level 2 Discovery	10 min 15 sec	5 min 6 sec	7 min 34 sec	4 min 4 sec
100 MB IDML bulk load (250,000 CIs)	13 hours 9 min	5 hours 52 min	13 hours 55 min	22 hours 19 min
Level 3 Rediscovery after bulk load	30 min 4 sec	6 min 47 sec	16 min 25 sec	6 min 24 sec

Conclusions

• Even in a small scale, the discovery process in a Virtual environment is almost 4 times slower than in a non-virtual environment
• Although the run time for other activities don't show significant difference, the discovery process in a Virtual environment is just prohibitive.
• Except for bulk loading, a two-server environment had the best performance in all tests.
  

Bringing Microsoft Active Directory manager information into Tivoli Process Automation Engine

• Go to TPAE, DB Config, select PERSON table and add the following attributes
  
  • supervisor_dn as aln(511);
  
  
  • person_dn as aln(511).

• Still in the DB Config, define the following relationship in the PERSON table:

• Go to TPAE, Cron Task Setup, select LDAPSYNC and create a user mapping like the following:
  

<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE ldapsync SYSTEM "ldapuser.dtd">
<ldapsync>
<user>
<basedn>...</basedn>
<filter>(objectClass=user) </filter>
<scope>subtree</scope>
<attributes>
<attribute>sAMAccountName</attribute>
<attribute>givenName</attribute>
<attribute>displayName</attribute>
<attribute>memberOf</attribute>
<attribute>sn</attribute>
<attribute>manager</attribute>
<attribute>distinguishedName</attribute>
</attributes>
<datamap>
<table name="MAXUSER">
<keycolumn name="USERID" type="UPPER">sAMAccountName</keycolumn>
<column name="LOGINID" type="ALN">sAMAccountName</column>
<column name="PERSONID" type="UPPER">sAMAccountName</column>
<column name="STATUS" type="UPPER">{ACTIVE}</column>
<column name="TYPE" type="UPPER">{PRIMARY}</column>
<column name="QUERYWITHSITE" type="YORN">{1}</column>
<column name="FORCEEXPIRATION" type="YORN">{0}</column>
<column name="FAILEDLOGINS" type="YORN">{0}</column>
<column name="PASSWORD" type="CRYPTO">{0}</column>
<column name="MAXUSERID" type="INTEGER">{:uniqueid}</column>
<column name="SYSUSER" type="YORN">{0}</column>
<column name="INACTIVESITES" type="YORN">{0}</column>
<column name="SCREENREADER" type="YORN">{0}</column>
</table>
<table name="PERSON">
<keycolumn name="PERSONID" type="UPPER">sAMAccountName</keycolumn>
<column name="FIRSTNAME" type="ALN">givenName</column>
<column name="LASTNAME" type="ALN">sn</column>
<column name="STATUS" type="UPPER">{ACTIVE}</column>
<column name="TRANSEMAILELECTION" type="UPPER">{NEVER}</column>
<column name="STATUSDATE" type="ALN">{:sysdate}</column>
<column name="ACCEPTINGWFMAIL" type="YORN">{1}</column>
<column name="LOCTOSERVREQ" type="YORN">{1}</column>
<column name="PERSONUID" type="INTEGER">{:uniqueid}</column>
<column name="HASLD" type="YORN">{0}</column>
<column name="LANGCODE" type="UPPER">{en}</column>
<column name="PERSON_DN" type="UPPER">distinguishedName</column>
<column name="SUPERVISOR_DN" type="UPPER">manager</column>
</table>
</datamap>
</user>
</ldapsync>

• Go to Action application and define the following Action:

• Go to Escalation application and define the following Escalation:

DB2 on Rails

I'm starting again with the IBM_DB adapter gem, available at: http://rubyforge.org/projects/rubyibm/

• gem install ibm_db
• rails newapp
• cd newapp
• ruby script/console
• >> gem 'ibm_db'
  
• ruby script/generate model person
• in the file db/migrate/*_create_person.rb, define the following:

class CreatePeople < ActiveRecord::Migration
def self.up
create_table :people do |t|
t.column :firstname, :string
t.column :lastname, :string
t.column :phone, :stringgg
end
end

def self.down
drop_table :people
end
end

• rake db:migrate