Webcast: Maintaining a Baseline of Applications



1 comment

  • Andrew Cudzilo

    Best practices question:

    Currently we nest the Java PDQ Library package inside a package called "OurPackage" -- we do a few custom steps after the installer, and thus far this has worked nicely (you only need to swap in the new Java package each time updates come out to "OurPackage", not duplicate the custom steps each time to each Java package that gets imported per updates).

    However, my assumption is that with nested packages included in a schedule, the scheduler doesn't "know" when we've updated "OurPackage" with a newer Java binary -- right? Or does it? (inquisitive tone)

    How does the schedule know a package version (especially if its not brought in via auto-deployment).  Is there a UNIQUE ID that each package attached to a schedule gets -- is it attached to the package name/version string?

    So, in my example (and assumptions on the unique id) would the best practice be, once a java update comes out -- update "OurPackage" as needed -- and then remove and re-add "OurPackage" to the scheduler to force the scheduler to treat "OurPackage" as a new package -- hence guaranteeing that the actual java update goes out?

    Or would it just be easier to add our custom steps to each imported Java update package and just update the scheduler when Java updates come out (essentially removing the "OurPackage" nested package from the equation and putting custom steps in source package)?

    Thanks for your thoughts

    Comment actions Permalink

Please sign in to leave a comment.