IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  sequencing Package loading...

    Posted Tue February 27, 2007 11:22 PM

    We need to sequence the list of packages when the IS is restarted. Any ideas on how ?

    Note: The direction I am going – There is a service called “WmOmiIs/omi.wm.is.filter:setPackageList”. I am guessing this might do the trick. My problem is start with is the input and ouput parameters are hidden.

    Any ideas ??


    #webMethods
    #Flow-and-Java-services
    #Integration-Server-and-ESB


  • 2.  RE: sequencing Package loading...

    Posted Wed February 28, 2007 12:26 AM

    Use package dependencies to control the order of package loading.


    #Flow-and-Java-services
    #webMethods
    #Integration-Server-and-ESB


  • 3.  RE: sequencing Package loading...

    Posted Wed February 28, 2007 06:33 PM

    Rob, Could you point me to the right service ?


    #Integration-Server-and-ESB
    #webMethods
    #Flow-and-Java-services


  • 4.  RE: sequencing Package loading...

    Posted Wed February 28, 2007 08:18 PM

    It’s not a service. It’s a configuration of the packages. For example, if Package A must be loaded before Package B, then on the package Settings tab in the 'Package dependencies", you specify Package A as the the package and . as the version. The package loader will ensure that Package A loads before Package B.

    In the attached screen shot, WmART is guaranteed to be loaded before the AxAdapter package is loaded. One can chain these dependencies together but you’ll want to be cautious about two things: 1) circular dependencies; 2) putting dependencies in place when package loading order doesn’t matter–when a package is reloaded using Administrator, all package that are dependents are also reloaded. Thus, if you have general purpose package like MyPublic that has lots of common services used by lots of packages, you probably don’t want to add MyPublic as a dependency in all those packages. That’s because any reload of MyPublic will cause all dependent packages to reload–which might effectively be the same as an IS restart.

    [attach]188[/attach]
    pkg_dependent.JPG


    #Integration-Server-and-ESB
    #webMethods
    #Flow-and-Java-services


  • 5.  RE: sequencing Package loading...

    Posted Mon March 05, 2007 02:48 PM

    If you do not want to use package dependendies, you could create a startup service that calls pub.packages:enablePackage for every package and place them in the right order yourself.
    You then also have to create a shutdown service that disables every package (pub.packages:disablePackage) when the server shuts down.


    #Integration-Server-and-ESB
    #Flow-and-Java-services
    #webMethods