djbrightman1 Absent Member.
Absent Member.
1172 views

Verify bundle that is not directly related...

Hi
We have a bundle (several in fact!) that calls another bundle as an install action, prior to doing it's own thing.
(We often do this for large installers, to copy the install source locally prior to running a customised install e.g. license key)

Is there a way to force verify the called bundle?

e.g. we think the called bundle hasn't actually done what it set out to do, but ZCM seems to think it has completed, so we want to force it to run again

I've been looking at "zac bv <display name>" but reading around it seems to only work with files that the agent *thinks it has installed (i.e. those associated). In that case this relates to previous thread https://forums.novell.com/showthread.php/476176-Show-INSTALLED-bundles-%28not-just-associated-%29

Any ideas or experience?
Cheers
David
Labels (2)
0 Likes
8 Replies
nop19832 Absent Member.
Absent Member.

Re: Verify bundle that is not directly related...

djbrightman wrote:

>
> Hi
> We have a bundle (several in fact!) that calls another bundle as an
> install action, prior to doing it's own thing.
> (We often do this for large installers, to copy the install source
> locally prior to running a customised install e.g. license key)
>
> Is there a way to force verify the called bundle?
>
> e.g. we think the called bundle hasn't actually done what it set out
> to do, but ZCM seems to think it has completed, so we want to force
> it to run again
>
> I've been looking at "zac bv <display name>" but reading around it
> seems to only work with files that the agent *thinks it has installed
> (i.e. those associated). In that case this relates to previous
> thread
>

https://forums.novell.com/showthread.php/476176-Show-INSTALLED-bundles-%28not-just-associated-%29
>
> Any ideas or experience?
> Cheers
> David


Hi

Not sure this would help in your case... but we did some like this some
time ago. Let's say that we needed to be sure a file was in place
before installing af bundle, we would add aa action and a requirenment
to that, so if the files was not in place it would verify the bundle
(that did the download) and the file/folder was there it would just go
on an install the rest of the bundle.

--
Niels
I have always liked... Cowabunga!

If you find this post helpful, please show your appreciation by clicking
on the star below.
A member must be logged in before s/he can assign reputation points.

-- Niels I have always liked... Cowabunga! If you find this post helpful, please show your appreciation by clicking on the star below. A member must be logged in before s/he can assign reputation points.
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Verify bundle that is not directly related...

Verifying the main bundle should be sufficient.

I ran a simple test last night.

#1 - Create Bundle with an Install Directory Action. (Install_Dir_Bundle)
#2 - Create a Bundle which had an Install Action of "Install Bundle Action" for Install_Dir_Bundle followed by launching a program action for a file in that directory. (Chain_Bundle)
#3 - Installed and Ran "Chain_Bundle" which created and populated the directory as well as launched the application.
#4 - I then deleted the directory and verified "Chain_Bundle". The directory was re-created and re-populated and the application successfully launched again.



djbrightman;2350348 wrote:
Hi
We have a bundle (several in fact!) that calls another bundle as an install action, prior to doing it's own thing.
(We often do this for large installers, to copy the install source locally prior to running a customised install e.g. license key)

Is there a way to force verify the called bundle?

e.g. we think the called bundle hasn't actually done what it set out to do, but ZCM seems to think it has completed, so we want to force it to run again

I've been looking at "zac bv <display name>" but reading around it seems to only work with files that the agent *thinks it has installed (i.e. those associated). In that case this relates to previous thread https://forums.novell.com/showthread.php/476176-Show-INSTALLED-bundles-%28not-just-associated-%29

Any ideas or experience?
Cheers
David
0 Likes
djbrightman1 Absent Member.
Absent Member.

Re: Verify bundle that is not directly related...

Thanks for that.
I think we're going to give up on this particular instance. The source is just too big and is causing too many issues. We're going to revert to 'sneaker ware' for this app....! 😉

Cheers
David
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Verify bundle that is not directly related...

djbrightman;2350730 wrote:
Thanks for that.
I think we're going to give up on this particular instance. The source is just too big and is causing too many issues. We're going to revert to 'sneaker ware' for this app....! 😉

Cheers
David


Large Content is not usually in issue.
For Install Directory Actions, "Single Piece of Content" should always be checked.
It makes things far more efficient on many levels.
0 Likes
djbrightman1 Absent Member.
Absent Member.

Re: Verify bundle that is not directly related...

CRAIGDWILSON;2350771 wrote:
Large Content is not usually in issue.
For Install Directory Actions, "Single Piece of Content" should always be checked.
It makes things far more efficient on many levels.

Thanks, good advice. However this beastie is 3.5GB and we have a very distributed network with some pretty poor links! 😉
Cheers
David
0 Likes
nop19832 Absent Member.
Absent Member.

Re: Verify bundle that is not directly related...

djbrightman wrote:

>
> CRAIGDWILSON;2350771 Wrote:
> > Large Content is not usually in issue.
> > For Install Directory Actions, "Single Piece of Content" should
> > always be checked.
> > It makes things far more efficient on many levels.

> Thanks, good advice. However this beastie is 3.5GB and we have a very
> distributed network with some pretty poor links! 😉
> Cheers
> David


No remote located storage, you could store the data on before
distribution?

--
Niels
I have always liked... Cowabunga!

If you find this post helpful, please show your appreciation by clicking
on the star below.
A member must be logged in before s/he can assign reputation points.

-- Niels I have always liked... Cowabunga! If you find this post helpful, please show your appreciation by clicking on the star below. A member must be logged in before s/he can assign reputation points.
0 Likes
djbrightman1 Absent Member.
Absent Member.

Re: Verify bundle that is not directly related...

nop1983;2351371 wrote:

No remote located storage, you could store the data on before
distribution?


"we have a very distributed network with some pretty poor links"...

Sometimes "sneakerware" is just best! 😉
Cheers
David
0 Likes
Highlighted
nop19832 Absent Member.
Absent Member.

Re: Verify bundle that is not directly related...

djbrightman wrote:

>
> nop1983;2351371 Wrote:
> >
> > No remote located storage, you could store the data on before
> > distribution?

>
> "we have a very distributed network with some pretty poor links"...
>
> Sometimes "sneakerware" is just best! 😉
> Cheers
> David


Right... not easy then 😉

--
Niels
I have always liked... Cowabunga!

If you find this post helpful, please show your appreciation by clicking
on the star below.
A member must be logged in before s/he can assign reputation points.

-- Niels I have always liked... Cowabunga! If you find this post helpful, please show your appreciation by clicking on the star below. A member must be logged in before s/he can assign reputation points.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.