Kintana Best Practices and Standards

ZDS

This page focuses on best practices and standards that can make your Kintana installation easier to manage.

Kintana Source Code Change Control. Requests are starting to fail at a step that used to behave perfectly. Almost the first thing you want to know is if anyone changed the source code and if so what was changed. This article describes a trigger you can add to your schema to track down those evil-doers who made those changes to your production image and forgot to update the change log ... you know who you are...

How To Secure Your Kintana System. Setting up a robust security access scheme is not as hard as it looks despite the formidable heft of the 140 page Security Model Guide and Reference manual. This paper presents a straighforward security model that's easy to implmement. Once you have the basics right it's easy to customize.

Kintana Command Script Coding Standards. How you write command scripts can make the difference between quickly diagnosing the cause of a problem and moving on, and getting into a long debugging session. This paper suggests coding standards and tools you can use to create reliable scripts...

Environment Name Standards. Environment names and descriptions you associate with physical servers can be whatever you choose. However using a consistent naming convention is strongly recommended...

Decision Naming Conventions. Making the right decision is a whole lot easier if you name your choices consistently.

Kintana™, 'Mercury IT Governance™', 'HP PPM (Project and Portfolio Management)™
are trademarks of Kintana, Mercury Interactive Corporation, and Hewlett Packard Corporation respectively.