You should create a RPM Group in a blpackage, add all dependencies and the main rpm in the group.

This will invoke the rpm -uiv command with list of all these rpms .

Try and let me know

Thanks,

ROhit

RPMs should be installed in a specific order.

If RPM X is needed by RPM Y, you need to install RPM X first, then RPM Y.

When you create an RPM group , the underlying command issues becomes

rpm -uiv <list of all rpms in the rpm group>

This lets the rpm command to automatically sequence dependencies for installation, But yes this needs all required dependencies to be in the list.

If you dont know all the dependencies at the time of package creation, than it is a problem

There are ways to do this:-

1. pre-fetch the information about rpm, use the rpm command line query options to get the list of dependencies and package all those.
2. What I will do personally is to make my life easy

• If its not a custom rpm, The best one and easiest one is to use something like YUM. For this you need to have your yum repository populated for a particualar Redhat/Suse distribution. This makes sure that the rpm you are trying to install is present in the repostory with all its dependencies.
• This is supported by the Patch functionality of BladeLogic, I will use patch Analysis and put one rpm in the include list and will go for install mode, the analysis result will show the rpm as missing and will return other dependencies automatically, I will use the patch deploy job. Remember the install mode.

I am not sure if many of  the gurus will agree with me or not

Thanks,

Rohit

When using an rpm group, the RPM order does not matter as the rpm command sorts it all out. And the easiest way is to use YUM. Export your redhat patch repository via nfs and setup a yum repo to point to that nfs mount on your target server (Google it, if you don’t know how to do those two steps), then just install packages via YUM. YUM will autoresolve dependencies.

The easiest way to do this in BBSA is to create a patch catalog.  Then create Patching Job, on the 2nd or 3rd tab of the wizard you set the job to 'install mode' instead of update mode.  then you specify the package you want to install in the 'includes'.  run the paj, this will tell you what dependencies need to be installed.  when you run remediation all of the property deps will be pushed to the target.

the benefit of this is that you can push out httpd to a bunch of hosts, and if they all require different dependencies, the Patching Job will work that out.

Yeah, forgot all about that feature. That is the product's way of doing the manual steps I listed. That's handy.