Friday, July 29, 2005
Yesterday, I was faced with the challenge of integrating RCS with Mercury Change Management. RCS is one of many available version control software on UNIX. As such Mercury ITG has out-of-the-box support for RCS. However, it is critical to understand the functioning of the actual software in order to integrate it with ITG. In order to understand the functioning of RCS, I searched the Net looking for tutorials. I found many, but none of them was specifically written keeping in mind Windows users. So, I decided to post what I did.
I had to post the article on my other site, as I originally created the document in MS Word and you know how difficult it is to get MS Word generated HTML to get accepted anywhere. Following the exact steps as given in the article, you can develop a good understanding of the product. The target of this article is to make you learn the basics of RCS on your own.
The article is available at: http://www13.brinkster.com/ranjeetrain/tutorials/
Linked below is the top-level design of the tool, as published on the Mercury site.
ITG center is based on a modular design. Modules have been desgined to serve different purposes. Some of the ITG center modules are: IT Governance Dashboard, Demand Management, Project Management, Financial Management, Change Management etc. Licences can be purchased for individual modules depending on the requirement. A graphics containng the technical design of ITG Center is available at mercury site.
ITG center is based on a 3-tier architecture. The client/presentation tier has two kind of front-ends. One is a standard thin-client (a webbrowser) interface meant for end-users and the other is a Java applet called Workbench meant for developers (called configurators). Middle tier is an Application Server that combines a web server and the core ITG Center engine. Data storage is handled with an Oracle database server. This 3-tier architecture provides for unlimited flexibility in installation and configuration for scalability. ITG center has no internal databases and depends entirely on a Oracle database server. That means increased licensing cost but at the same time that also means increased dependability and availability. It can work with an external web server allowing for increased dependability and availability while at the same time opening possibilities of integration with other existing applications.
It is an interesting tool. I am likely to work with it for some time. You may expect to hear more on this from me. So, stay tuned folks!
Friday, May 27, 2005
Keywords: Administration tip
These days I am involved into one of the most challenging projects of my career. It has been a tremendous learning experience. One very small but significant thing that I learnt today is - Don't attempt protecting the servers with a BIOS password. Well, this may sound strange as we always think adding a password to the BIOS adds one more level of security. Well not really. Any person who can gain physical access to the server can get rid of that password. Besides, adding the password to the BIOS means, you cannot boot the system remotely. Now this is a big setback. Rather you would like everyone to work on the server remotely and no one to have physical access to it.
There would be a lot of people who will think otherwise. Logic would be - No physical access, no software access. Well, that can work in smaller organizations with a few servers and one or two administrators. But in case of large organizations and dozens of admins, that approach is not practical. The bottomline is: If you want your servers to be accessed remotely, don't add a password to the BIOS.
Wednesday, May 25, 2005
- GFI MailEssentials
- SPAM Shredder
- Safe Express
Tuesday, May 24, 2005
Wednesday, April 06, 2005
Netscape Color map http://help.netscape.com/kb/consumer/19960513-14.html
Hope you enjoy the tools!
Today I was going through what I had posted earlier, and at places it felt like, I started blogging without providing a background. More so because this blog is on general software development issues. To make the content more context-friendly and to help search engines index these pages wisely, now onwards I will be adding categories to my posts. Hopefully, that will add some more value to the content for future visitors.
Monday, April 04, 2005
Last week I received an email from a colleague of mine who wanted help with a script that will give him a dump of all the fields in a form and related information such as its data type, default value and associated code etc. Last couple of days I had been busy trying to achieve the same. This morning has brought a relief when my boss forwarded me an email that he received from Stephanie Heit, Sales Manager, Teamstudio Europe.
The email was about a product they call Teamstudio Script Browser that TeamStudio calls a LotusScript Code Navigator. From the product page at teamstudio.com - "Teamstudio Script Browser is a tool to help you use and navigate the LotusScript code stored within an IBM Lotus Notes database in a way that has never before been possible."
Its a promising product. I still have to review it. I will give the report of the product later. For the time being check it out for yourself from this page.
Wednesday, March 30, 2005
Thursday, March 24, 2005
- When you are in real hurry, you can save a few seconds by typing your query directly in the address bar. Prepend "www.google.com/search?q=" to your query text. It will fetch the results directly. This, of course, uses all the defaults. If you want language selection and content filtering etc, better use the full syntax generated by the site.
- Use keywords rather than complete phrases. e.g. Festivals India is likely to fetch more precise results than "Indian festivals"
- Use exact error message if you are looking for its description and put it under double quote. e.g. "Router:Failed to connect to SMTP host". This is more likely to bring up relevent pages than queries based on keywords such as Router Error SMTP failure
- Google by default does an AND on the tokens in the query text, i.e. it will try to find pages with all the tokens in the query text. If you want to change that, use specific boolean operators.
- While submitting a complete phrase or sentence for search, google omits commonly used words. Use a plus symbol (+) to include them in the search.
- Sometimes you remember having seen a page on a particular site with specific information that you need now. Instead of visiting the site and going thru all the pages one by one, use google to do the job. Prepend your query text with "site:www.siteaddress.com". That syntax causes google to search for the query text only in the pages cached from that site. If Google has cached pages from that site, it will be hundreds times faster and precise than finding the information by manually searching that site yourself.
- You may use Google as a thesaurus. When uncertain about what a word might mean, you may ask Google to define terms/phrases for you. Use this URL: www.google.com/search?q=define:Your_Search_Term