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

TAM For E-Business

Lets talk about Links and Junctions :
WebSEAL is a proxy that is located between the Internet and the internal back-end servers. In the following figure, the browser requests a Web page using the URL https:///Junction1/index.html. WebSEAL uses the junction name Junction1 to identify the back-end server and sends a request for http://ServerA/index.html.

The Problem :
Webpage contains links to other webpages, and resources which are accessed using the URLs. These Hyperlinks are send to back-end servers using webseal, but these URLs might not be validated as they dont contain the junctions.
Link Types:  There are 3 link types we come across ITIM/ ITAM : Relative, server relative and Absolute.

Relative links do not contain the name of the server or the name of the current directory. When the browser receives a relative link, the link appears to be located on the WebSEAL server. Relative links are correctly interpreted as links to other pages in the same directory on the same server.
For example, assume that this line appears in http://serverA/index.html: About this site
The browser retrieved this page from https://webseal/Junction1/index.html. This URL is correctly interpreted as pointing to https://webseal/Junction1/ about.html. This request would go back to WebSEAL and WebSEAL would know to request http://serverA/about.html.
•    Server-relative links do not contain the name of the server, but they do contain the name of the directory.
For example, assume that this line appears in http://serverA/index.html: Contact information
The browser retrieved this page from https://webseal/Junction1/index.html. This URL is interpreted as pointing to /contact.html on the same server. However, from the browser’s perspective the server is WebSEAL. If WebSEAL did not change the HTML, the browser would attempt to retrieve https://webseal/contact.html instead of the correct URL, which is https://webseal/Junction1/contact.html.
•    Absolute links contain the name of the server and the directory. For example, assume that this line appears in http://serverA/index.html:
Copyright Information
If WebSEAL did not change the HTML, the browser would attempt to connect directly to ServerA, bypassing WebSEAL. A correctly configured firewall would only allow connections to ServerA from WebSEAL.



ReF: Junctions and Links.pdf IBM White paper