Person Form Customization in ITIM

In ITIM , it is very easy to customize various forms like person add.
Steps:
Login to itim console
Navigate to Configure System -> design forms
You may have to accept running the script, as this is java. If you dont let the script run, or let the browser stop it , then you might not be able to customize the person page.

Now go to Person , double click on it.
You will see person again , if you have made another custom person class, you will be able to see it there as well. Once you double click person, you will see the tabs on the right. Each tab has different attributes. Each tab in here appears as a separate tab in create person.
To create a new tab, go to Form Menu --> TAB menu ->  add Tab.

You will then need to rename the tab by tab menu -> rename tab

Once the person form is created, simply double click the attribute you want from the attribute list on the right. Any attribute you dont want to show up in the user create menu , can be selected and deleted using delete key. this will send the attribute back in the attribute list. You WILL NOT BE ABLE TO DELETE ANY ATTRIBUTE, so dont worry and play around.

You can give default value to the selected attribute by selecting Properties in right hand corner of the window.

Once done , save form and exit.

All set for Pulse 2012

I have finally got my Pulse 2012 pass with me , and with the hotel booked, looking forward to interact with whole lot of people I know. Try to understand where the technology is flying and where the people are working ...
Will keep a log of Pulse updated .

User Modify in TAM LDAP using pdadmin

To create the user using pdadmin :

user create deepakg83 uid=deepakg83,cn=users,o=myorg,c=us deepakg83 wsadmin wsadmin PasswordForwsadmin


Substitute myorg with valid LDAP entry in your ldap
This will create deepakg83 for TAI++ configuration . 

We can directly set the validity of a user to true using pdadmin . It is achieved with ease once you log into pdadmin and run the following command :
pdadmin sec_master > user modify deepakg83 account-valid yes

Creating WebSeal Junctions from Command line

Ever wondered how easy it is to make webseal junctions from mere command line, it is possibly easier than making it from WAS TAM integrated console.
Login to Webseal machin :
pdadmin> login
Enter user name:
Enter password :
-----
The first thing i recommend you to list the servers available in your webseal
pdadmin sec_master> server list

You will get a list of servers ... find the entry that looks like :
default-webseald-server01

This is possibly your webseal name , this is used at many instances and should be kept safe .

Now lets make the webseal junction :

server task default-webseald-server01 create -t ssl -b supply -c iv_creds -h wasPortalServer01 -p 20004 /junctionname01

Where wasPortalServer01 is the backend server which will be authenticated by webseal and junctionname01 is the junction that will be created.
If you now have to load balance the two servers on same junction name , DO NOT run the following command:
server task default-webseald-server01 create -t ssl -b supply -c iv_creds -h wasPortalServer02 -p 20004 /junctionname01
This will be ERROR ...

Use this command instead :
server task default-webseald-server01 add  -h wasPortalServer02  -p 20004 /junctionname01


This will create a junction which will be TAI++ enabled 
 

ITIM DB2

Connecting to itim db2 is easy , but most of us forget to profile db.

Login to itim db2 server as root

Then profile the db :

# . /home/db2admin/sqllib/db2profile
db2 connect to user itimuser using

Easy as it gets :)

if u want to run select commands, put db2 "Select * from abc where d = 'gupta'"

GLPCTL088E Unable to run the command on directory server instance ''

GLPCTL088E Unable to run the command on directory server instance '' If u got an error like this running ibmslapd -k command ,do check if there is -k or .k

The correct syntax is :  /location/ibmslapd -k

Tivoli General Rules

The way things have come up in recent past have changed.
modus operandi tends to include most if not all of the following:

•    It is reactive, not proactive.
•     Resources may be healthy while customer service levels are not acceptable.
•     Events describe problems, not corrective actions.
•     Events flow into the Operations room at an incredibly high rate, and “event storms” have performance impact on systems.

•    Fixes are typically manual and inefficient.
•     Problems cannot be prioritized because impacts are unknown.
•    Most problems cannot be detected; more than 50% of all problems are reported through the help desk.
•   Organizational boundaries breed incompatible tools, making end-to-end management and integration very difficult.
•    Lack of vision and strategic direction increases costs.

ReF: IBM Redbooks: Tivoli Monitoring