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.  manifest.v3 package dependencies

    Posted Thu October 15, 2015 11:57 AM

    hi,

    query1: in my package dependencies do i mention about WmPublic(Package), .(version)??

    query2,

    1. i’ve couple of package dependency entries in manifest.v3.
    2. on IS, i’ve edited and removed one of the line under package dependency xml block.
    3. from IS admin, package mgmt, reloaded the package.
    4. query: package fails to activate. since IS still looking for the second missing package (which i deleted in step 2 from manifest.v3 file)

    any help is appreciated

    thanks & regards
    ajay kumar kasam


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


  • 2.  RE: manifest.v3 package dependencies

    Posted Thu October 15, 2015 04:43 PM

    A1: it’s optional to mention dependency. Only based on your own need, you can decide to do so.
    A2: only edit it via developer or designer, never directly edit the manifest file.


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


  • 3.  RE: manifest.v3 package dependencies

    Posted Thu October 15, 2015 05:32 PM

    I personally do not mention WmPublic as a package dependencies on my custom package as this package will always exists and I am sure that no one will delete it as it has all core utils out of box provided by SAG.

    I suggest to update the package dependencies for your custom packages so that the dependent package must load first.

    But its a best practice :slight_smile:

    Any questions?


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


  • 4.  RE: manifest.v3 package dependencies

    Posted Mon October 19, 2015 01:54 PM

    Ajay,

    1. You don’t have to mention WmPublic as a dependent package for your custom package. This would be a dependent package for any custom package that you create, hence you don’t have to mention this.
    2. Do you see manifest.v3.bak file? If so, delete that file and reload the pacakge
    3. If you still have got problem, you messed up the structure of manifest.v3 file. Compare this file with any other manifest file from a loaded package with dependency.

    Regards
    Senthil


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


  • 5.  RE: manifest.v3 package dependencies

    Posted Wed October 21, 2015 03:00 PM

    Hi Ajay,

    can you share the manifest-file before and after the change as well as the error message from server-log?

    Regards,
    Holger


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