Software Deployment

Ian,

Don't know if this helps, my company uses Radia to deploy software internally - something that I have no involvement with so not sure if this is right.

There is a 'HKLM\Software\Novadigm\Properties' key, under there is NVDARGPROVIDERNAME=<name of server>.

Also a 'NVDSOURCEDIR'=<UNCPATH>

This is on a client machine


Hope this helps,

Dunnpy

Thanks, Paul.

Close, but no cigar :-(

NVDARGPROVIDERNAME=radia
NVDSOURCEDIR=[path from which the client was installed]

I did find a DNS alias in the value for NVDARGRESOLUTIONMANAGER but connecting to that server, I found no MSIs.

Ian,

I'm fairly new to Radia from a packaging standpoint but know that the config files are stored in c:\Program Files\Hewlett-Packard (HPCAE if you are using version 7.8). Under there, go to CM\Agent\Lib and look for the file "args.xml". Look inside the file (I use Notepad) and look for:
RESOLUTIOMANAGER

It will give you the name of the Radia server that you machine will contact first.

Of course, what will happen then if you are in a large environment, is that the resolution manager machine might redirect to your closest RCS (Radia Configuration Server) but I don't know what to tell you for how to get that name.

On another note, there are log files that might help you too. In the Agent folder, there is a subfolder named Log. In there are the Radia logs.

The Connect_Manual.log contains information from when the user runs Radia for self service.
The Connect_Softare.log contains information from when Radia pushes applications down to the machine.

There are many more files in there but I usually sort them by date so I can tell which ones have been most recently updated and look in those first.

Hope that helps.
-Lewis

ORIGINAL: VBScab

I did find a DNS alias in the value for NVDARGRESOLUTIONMANAGER but connecting to that server, I found no MSIs.



The normal process is to use the Publisher to bring applications into the RCS. What Radia does is converts everything into it's own set of binary files. So from that standpoint, you won't see source files or MSIs on the RCS. What you will need to do is find out where the files were put prior to them being brought into Radia with the Publisher. Once I have my application all packaged and ready for Radia, I put the files onto the local hard drive where my Publisher software is installed (into a Temp folder). Then I use Publisher to bring everything into Radia which then converts it all into it's own set of binaries.

My guess is that unless you know where the source files are located prior to them being brought in with Publisher, you problably won't find them.

Of course, I'm pretty new to Radia so I could be wrong. ;)

Funny how things work out...

About 3 hours after reading Lewis's response (thanks, Lewis, BTW) I was approached by a member of the Production packaging team, who asked if I could take a look at some logs produced by a failed install. Obviously, I innocently opined that it would help enornously if I could get hold of the package, so I could check it against the log. He gave me all the information I needed.

And yes, the package in question was another jaw-dropper. This is going to be such fun!

You're welcome.

If you as an application packaging engineer are looking for a real challenge, Radia is definitely the way to go. Bringing packages into Radia can take a while as there are so many ways to make a Radia package.

Also, Radia error messages can be quite vague and cover a lot of problems (unlike MSI errors that are more specific). It might as well say "an error was found - exiting". LOL

FWIW - in the log files, each line will have 3 dashes (---). When you open the log file, look for an exclamation (!) in the dashes (e.g. --!) as that will mean there is an error on that line of the log file and might give you a clue as to what the problem is. If there is a question mark, (?), that means that there is a warning (like a path was not found but is not needed) and usually be ignored. Knowing that will help you track down errors with the install too.

Personally, I still put an MSI log file in the ZCREATE line so that I can troubleshoot the MSI install too.