How to ignite a software depot to Ignite-UX clients?

[Kent_30]

I'm new to Ignite-UX and I need your help on this situation:

I have an Ignite-UX server and around 20 Ignite-UX clients. They are all up and running.
I have an application and I want to install this software depot to all Ignite-UX clients (I don't want to do 'swinstall' on each client individually). The Ignite-UX document shows I need to create a bundle from my depot, make a config file, and add the config file to an index. I did all of those but then I got stuck here. What should I do next? I don't want to reboot and re-install the ignite-ux clients, which will re-install the OS (I think). I only want to just install my application (additionally to all the current clients).

Another concern I have is when bundling my depot, is there any change on my depot fileset? In other words, is there any difference comparing between installing via ignite-UX and 'swinstall'. For example, will 'swlist my_app_bundle' and 'swlist my_app_depot' return different results or not. If yes, how can I resolve this? I don't want any difference. I hope your inputs will help me out.

Your helps are highly appreciated.

Thanks,
--KV

[Florian Heigl (new acc)]

I don't think You can use Ignite to push out software after installation, this is done by another tool.

From what I read Your software is already bundled and happy to go, so the following should work:

in general, Your software is just handled by swinstall/swremove/swcopy, there also exists an Openview Software Distributor (SD-UX), which is able to target remote hosts.

This would look like the following:

for hostname in host1 host2 ...
do
swinstall -s igniteserver:/path/to/depot "software_name" @ $host:/
done

but, if You're not planning to spend big bucks, You could also change this to:

for hostname in host1 host2 ...
do
ssh $hostname "/usr/sbin/swinstall -s igniteserver:/path/to/depot "softwarename" @ / "
done

I think this will do what You need.
Be aware, that You have to create a depot in the ignite server. /var/spool/sw should already exist, if You want to re-use it, You can simply copy the software in:

swcopy -s /path/to/software "softwarename" @ /var/spool/sw


Good luck!

[Steven E. Protter]

You can set up software depots on the Ignite server for clients to pull off the Ignite server.

First you need to swcopy the depots into the nfs structure that includes the Ignite Core OS you already set up.

Here are some documentation possibilities:
http://www1.itrc.hp.com/service/james/dispDoc.do?docURL=%2Fservice%2Fcki%2FdocDisplay.do%3FdocLocale%3Den_US%26docId%3D200000064128974&aid=SEARCH_CKI&pil=1&serStr=Ignite+software+depots

http://www1.itrc.hp.com/service/james/dispDoc.do?docURL=%2Fservice%2Fcki%2FdocDisplay.do%3FdocLocale%3Den_US%26docId%3D200000070346469&aid=SEARCH_CKI&pil=10&serStr=Ignite+software+depots

http://www1.itrc.hp.com/service/james/dispDoc.do?docURL=%2Fservice%2Fcki%2FdocDisplay.do%3FdocLocale%3Den_US%26docId%3D200000078009422&aid=SEARCH_CKI&pil=15&serStr=Ignite+software+depots

These docs are a little large, but if they don't work post back and I'll actually open up a paper manual for you and key in a procedure.

SEP

[Kent_30]

Hi SEP,
No any link helps. Can you key down what I should do after 'swcopy'ing my depot to the ignite server? What should I do so that my ignite clients can recognize the depot and pull it down.

Thanks,
--KV

[Greg Vaidman]

If you don't want to reinstall and you already have the depot on your IUX server, you can do the following...

run "/usr/lib/sw/mx/setaccess " on all of your clients. you could also do this as part of the ignite build.

then, from the iux server, you can push the software: "swinstall -s @ ..."

you only have to do the "setaccess" command once on each server, and then you can push software from the IUX server whenever you want.

As to your other question re: difference between installing software via ignite and swinstall, the answer is - when you install a Software Distributor depot product, either onto an IUX golden image, as part of the IUX build of a server, or using swinstall outside of IUX entirely, the swlist output will be identical in the end.

regards,
greg