Software Deployment

Haven't done that particular app, but I find that the best rule of thumb is when there are multiple separate installs, keep them separated even they came in the same box. Sometimes the multiple installs are bundled into their main install, I separate them out as well. The reasoning behind it:

• Being a separate install is a sign that the vendor licensed someone else's software and bundled it with their app. That vendor may not be the only one who has done that. If you bunch up the add-on with a single app, you will make things more difficult for yourself if you find yourself deploying another app that uses the same licensed add-on.
  
• Future releases may use the same add-on. If that happens, you'll reduce the install time by upgrading only the portion that has changed.
  
• It is possible to call an MSI from within a MSI, so the base application install can launch the add-on MSIs creating a "single" install. You can do the same from other app MSIs, and if they're already there it will just do a quick verify on the common plug-in instead of two applications existing with a sizable overlap/conflict. CA apps are a prime example. Once you strip out the CA Licensing Utility as a separate pre-req application, CA apps show great improvement in the "plays well with others" dept.
  
• You're dealing with Java, with is a commonly used element. If that add-in conflicts with something else, it's better to have a conflict with only the Java plug-in as opposed to the entire application.
  

Of course, that just my two cents. Your results may vary.

Yo,
I just got a bad boy called Winrunner Quicktest to do. This app has a lot of components but no msi. Will a Setup Capture be able to do this.
I know that u must not run a capture for a msi and create a transform. When I try and run the MSI it complains about having to run the setup.exe that luanches the MSI.

Any advise please

Sounds like InstallShield junk. Is there an ISS script associated with the MSI. There is a way to make this work but I do not have any real expericance with it. Basically, you must have the appropriate ISS script installed so the MSI thinks you have run the setup. I belief this is correct. Check the boards for more infor., sorry I could not be more help.

Regarding MSI and setup.exe: Check the AppDeploy Tips & Tricks section for "Getting Around MSI Packages That Require Setup.exe". That article includes a link to an InstallShield posting on the same topic.

Took VikingLoki's advice and got WinRunner going, what a piece of #*%!. Their installation not mine. Had to really finagle the installtion to get it captured. Had to use Event Viewer and PCUpdater to capture what this is thing was doing. Took me a day but I got. Now I am capturing the JAVA and Terminal Emulator pieces, alot simplier.

I have some problem with WinRunner. sometime there is some message like: "object is disable" , "object not found". some more following problem:

And finally in Update mode also operation is same and I unable to perform database checkpoint. If I write the function db_check(“list.cd1”,”dbvf1”); and Run the message is following:
“GUI Capture Failed.
For more information, See the test results.
Error: Cannot open file 'C:\Program Files\Mercury Interactive\WinRunner\tmp\noname2\chklist\list.cd1'.”
Continue/push.

Thank You
md. shaiful islam

ORIGINAL: cduplessis

I know that u must not run a capture for a msi and create a transform. When I try and run the MSI it complains about having to run the setup.exe that luanches the MSI.

Any advise please



It's a good rule of thumb to try and customise a vendor install with transform if you can. Sometimes this can be more trouble that it's worth though.. Remember that the vendor setup may cater for all sorts which you don't need to worry about - like installing / updating MSIEXEC, installation on different operating systems etc. Also there maybe loads of nasty custom actions which just won't work in your locked down environment.

Sure, spend some time with the vendor MSI but if you aren't getting anywhere and are only concerned with one standard OS build then don't be afraid to try a snapshot. You can always strip out all the Install Shield guff after (or even add it to your global exclusion list to save time in the future). Have a look at the Install Shield engine installer (usually called isscript.msi or ISScript8.Msi depending on version) to see what you can happily exclude from your snapshot.

You can always refer back to the vendor MSI and resulting installation to make you you are achieving the same results with your MSI.

Hope this helps,
Rob.

Hello!

Has anybody done WinRunner 8.0 packaging? App requires a re-boot for licensing. Need some tips on that. - Thanks

Guys,

I just did the WinRunner 8.0. This is not a good app to deal with. Very resource intensive. App needs a reboot to complete the setup. So I captured even after the reboot. Initially I had NTVDM Hard error when launched the shortcut. But I re-captured and this time I didn't get any errors. It needs a maintenence number and license host name for straight launch. For license server name, you need to have an environment variable called LSHOST=<servername>. Initially during the launch it will ask to choose the license option. I chose concurrent server license. Then it saved that info in Windows\wrun.ini file. I put that file also in the package. So users won't be asked any questions, and can launch the short cut stright away.
For regular users, we need to open few classes and folders with Mercury Interactive\Winrunner. I still have to do it.
Also, I have an issue with "PALDRV" service to start it automatically. I need to check the right registry settings and drop them in my package.
Otherwise my package looks good, and no errors when launched.

Thanks