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
Expand all | Collapse all

Accessing wm.server.triggers:getTriggerReport output

  • 1.  Accessing wm.server.triggers:getTriggerReport output

    Posted Thu September 06, 2007 09:07 AM

    I have a problem with accessing data returned by above service. Automatically generated code from Developer tool says, there is no output for that service, but when calling from Developer, i receive plenty of data (presented on


    #webMethods
    #Integration-Server-and-ESB
    #webMethods-General


  • 2.  RE: Accessing wm.server.triggers:getTriggerReport output

    Posted Thu September 06, 2007 11:52 AM

    Hi Kordian,

    did you try running the service in IS Admin?
    Packages > Management > WmRoot > Browse Services > wm.server.triggers:getTriggerReport

    In the output you will find the structured values.

    As this is an internal service, it has no public documentation and may change without notice. Therefor it has no output signature (in this case), but the objects exist in the output pipeline of the service.

    Regards,
    Holger


    #webMethods
    #webMethods-General
    #Integration-Server-and-ESB


  • 3.  RE: Accessing wm.server.triggers:getTriggerReport output

    Posted Fri September 07, 2007 02:33 PM

    Exactly! But I am not java geek unfortunately, so I need some help to access this data, a piece of code as an example. Could You help me?


    #Integration-Server-and-ESB
    #webMethods
    #webMethods-General


  • 4.  RE: Accessing wm.server.triggers:getTriggerReport output

    Posted Mon September 10, 2007 09:00 AM

    Hello,
    You probably do not have to be a java geek. A good general programmer is well enough. What I usually do is make a new document type and a new specification to match the input and output signatures of the WmRoot service. Then I create a wrapper service to those signatures and have it call the internal service. This way I can easily plug the wrapper service in my other services and document the it is based on unstable code. If need be I can also take further action to make it forward or backward compatible if used in other release versions. Good day.

    Yemi Bedu


    #webMethods
    #webMethods-General
    #Integration-Server-and-ESB