|WikiProject Brands||(Rated Start-class, Mid-importance)|
|WikiProject Software / Computing||(Rated Start-class, Mid-importance)|
|WikiProject United States / Austin||(Rated Start-class, Low-importance)|
Was this article taken from the IBM puff website? I've read the whole thing, and I still don't have the slightest idea what the damn software actually does. Apart from "Managing stuff." What the hell does that mean?
You raise a very good issue. I worked in the Tivoli Marketing Communications department for a while after several years as a technical writer there. I was one of several people charged with developing and maintaining the messaging. I can tell you with some certainty that most of my marketing colleagues did not know what the software was supposed to do or how it worked. Here's a few more details that I hope will be meaningful to you.
The original idea for the product was conceived by Todd Smith. He was an IBM employee who saw a potential train-wreck on the horizon with all the variations of UNIX, which was quickly eliminating the portability of UNIX, the very purpose of its existence from its inception. IBM, of course, offered AIX, Sun offered SunOS and later Solaris, HP offered HPUX etc. I know that this was a problem because I worked at WalMart for about a year and they were dealing with this exact problem. They were running four different versions of UNIX on their network.
Todd's idea was to develop a framework that would be installed on any UNIX platform. It would then intercept requests from applications that run on UNIX, make them platform agnostic, and deliver them to the appropriate server and marshal the data in a way that was appropriate for the version of UNIX that particular server was running. Then when the server responded it would reverse the data flow and pass it back to the original client.
The idea was to charge very little for the framework, and to create applications that would automate IT processes (as mentioned by the original author of the Tivoli entry). A typical process that we tried to automate early on was software distribution. The idea for this particular application was that the IT administrator would build some kind of service pack to install an application or upgrade an existing application. When the software pack was ready, the administrator would notify all users to log out at the end of the day--but to not shut down their work station, because the application was being installed or upgraded. Overnight, Tivoli Software Distribution would deliver the software pack to every computer and if necessary restart it.
The original idea was to automate all IT processes like the one I gave in the example. The Storage Software that the author mentions was actually a re-branding of something called IBM ADSTAR which enabled IT administrators to manage data storage and do things like back-up and restore. Without a storage management system you have to create scripts that will run every so often that take all your data from one location and copy it to another location. Tivoli Storage manager makes it easier to do that (supposedly).
Tivoli Change and Configuration Management is supposed to make it easier for administrators to configure applications properly. Tivoli NetView is a re-branding of IBM NetView, which displays network topology and represents network nodes as either green (up) or red (down), so that they can narrow the location of problems on the network. Tivoli Enterprise Console (TEC) receives information about the health of a client/server application and display the information on a monitor. So if you're using Outlook, for example, and your client suddenly can't reach the server, TEC administrators would be aware of the problem and in some cases actually pre-empt it. It actually worked and it was a neat little application. Tivoli Monitoring was the engine that fed TEC event information, but could also be used independent of it. The value TEC added to Tivoli Monitoring was an event correlation engine that could understand the relationship of different events to each other.
I have no idea what Workload Scheduler does,as well as the other applications mentioned by the author.
In short, the whole idea was to abstract details and tasks out of any IT process.
If you have other questions about Tivoli, you can contact me at firstname.lastname@example.org.
- - Wow. That was a most excellent answer. Thanks Guy. Hopefully someone can work this info into the wiki page.
Background on Tivoli Systems, Inc missing
I feel that the page is missing some background info. A link for Tivoli Systems, Inc redirects to this page, however it provides no information on the background of the company prior to IBM acquisition. That it is an acquisition is implied only by the links in the See Also section. The List of mergers and acquisitions by IBM has more information on the acquisition than the page itself such as when it was acquired (1996). The talk page classifies this as related to Austin, TX, but I see no mention of the location of the company in the main article. Chaozu42 (talk) 20:59, 8 May 2013 (UTC)
Someone suggested in private that they wanted to change the article title. However, the current title doesn't seem to cause any problems or is inaccurate, unless one wanted this article to be about "Tivoli Systems, Inc." before "Tivoli Software". If anyone has a better title, please mention it here. Despatche (talk) 08:16, 7 October 2013 (UTC)