Each and every day, we strive to create the very best product possible – not just for our clients and those who judge our work but, more importantly, for ourselves. We are all perfectionists in our own right; after all, each project we undertake is a testament to our own ability.
One source of creative inspiration that I find myself drawn to time and time again is Top Chef on Bravo. For those that have not watched; the series features aspiring chefs who compete for their shot at culinary stardom and the chance to earn the title of “Top Chef.” Each episode holds two challenges for the chefs. The first is a Quickfire test of their basic abilities and the second is a more involved elimination challenge designed to test the versatility and inventiveness of the chefs as they take on unique culinary trials such as working with unusual and exotic foods or catering for a range of demanding clients. The challenges not only test their skills in the kitchen, but also uncover if they have the customer service, management and teamwork abilities required to be the Top Chef. The competing chefs live and breathe the high-pressure lifestyle that comes with being a master chef and each week someone is asked to “pack up their knives” and go home.
The real questions for the judge are:
Did the Chef’s dish WORK? In other words, did their thinking and execution work?
When we talk about integration we don’t have to look back and dwell about those questions because we provide the tools to not only put the ingredients together but to ensure that they were executed as planned. Today starts a series about moving forward knowing what you did worked as expected and confirming your integration worked.
Exploring the Data Validation Option commands with PowerShell, Part One
Running the DVOCmd RunTests command from PowerShell
The Data Validation Option (DVO) lets you test and validate whether moved or transformed data is complete and accurate. DVO requires the Informatica PowerCenter. Informatica has training that is either instructor-led, or OnDemand. You can see an OnDemand preview for the Data Validation Option at:
DVO has a built-in command line utility called DVOCmd. You can use DVOCmd with either the Windows command line shell or the PowerShell Console. DVOCmd can schedule the execution of tests.
I have worked with PowerShell for years. Every version of Windows has a command line shell window. The command line shell window has not changed. Anyone with a background in UNIX or LINUX is familiar with the concepts of a command line shell. The Windows command line shell is adequate but not as full-featured as a UNIX command shell. Many people would prefer to click on the user interface rather than type esoteric commands, even if the command line may execute faster.
PowerShell is a recent improvement on the Windows Command Line shell window. The scripting language of PowerShell is based on C# and the object model is based on the Microsoft .NET Framework.
PowerShell Version 2.0 is built into Windows 7, Windows Server 2008 Release 2, and later releases of the Windows operating systems. You can also install PowerShell 2.0 on earlier editions of Windows.
You can start the PowerShell console by using the Search box on the Start menu.
For this example, I have created a table pair with two joined tables. To run this table pair from a command line, I add a simple External ID in the Table Pair Editor. The External ID is “A1234″. I save the table pair, and then create a test.
With joined tables, I can run a Value test. I select the columns that I used for the join in the table pair. PowerShell runs every test for that table pair.
I use “sl”, which is an abbreviation for the Set-Location cmdlet. The cmdlet is a lightweight command that is used by PowerShell. The Set-Location command is sort of equivalent to the “cd” command in the Command Line shell. Set-Location sets the working location to C:\Program Files (x86)\Informatica9.1.0\DVO.
You can run the DVOCmd commands only from the DVO directory. The Informatica location may be different. The file name is based on the version of Informatica PowerCenter installed.
If the current directory is not part of the environment path, you may need to add “.\” to the beginning of the script command. PowerShell does not load commands from the current location by default. PowerShell has more security options than the command line shell, which is another discussion.
In DVOCmd, to run the tests for a table pair, the syntax is:
Most of these arguments are optional.
After the test has been run you can verify if the test was a success or failure.
If you prefer, you can send the output to a log file. I have added the command to send the information to the Run.log in another directory.
You can open the log file to verify that the tests were successful.
And for desert you ask?
No meal can be fully integrated without dessert. So our next blog will feature more ways to understand and ensure that as you move and transform data that the results you expect are delivered.