Managing Multiple Apps with the Same Name in NSL



By: dguest

April 9, 2008 7:28 am

Reads: 161

Comments:0

Rating:0

Problem

A Forum reader recently asked:

“How can I manage 2 different applications with the same executable name? Is there any way to create two application definitions for the same executable name?”

And here is the response from David Guest …

Solution

You can create two scripts and then call them from a single script. Let’s assume that your application is called TestApp.exe, and it has two different versions.

1. Create a script for the first version and get it working.

2. Cut and paste the script into a generic script called “TestApp-Version1″.

3. Create the second script for the second application and test it.

4. Cut and paste it into a generic script called “TestApp-Version2″.

5. Get a script to work out what it is going to do, and which application is being run. Do this first by getting the MD5 hash of each application (a utility for this is at http://www.winmd5.com). As an example, the WinMD5 application which you can get from the web site has
the following MD5 hash: “944a1e869969dd8a4b64ca5e6ebc209a”

6. When you have the MD% hash for each application you can write a short script as follows:

#Application definition to determine which of 2 similar applications is 
being run
GetMD5 ?MD5Hash
If ?MD5Hash eq "944a1e869969dd8a4b64ca5e6ebc209a"
     Include "TestApp-Version1"
     EndScript
Else
     If ?MD5Hash eq "944a1e869969dd8a4b64ca5e6ebcfffc"
         Include "TestApp-Version2"
         EndScript
     Else
         MessageBox "This application is not supported"
     EndIf
EndIf
# End of Script

VN:F [1.9.22_1171]
Rating: 0.0/5 (0 votes cast)

Tags: ,
Categories: Uncategorized

Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment.  It just worked for at least one person, and perhaps it will be useful for you too.  Be sure to test in a non-production environment.

Comment