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