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.



#Automation


#Applicationintegration
#webMethods
#Integration
 View Only
  • 1.  trigger output

    Posted 07/23/07 01:37 PM

    Hi to all
    The trigger out put is diplaying in server log how can see the output in the result panel of the developer screen


    #Universal-Messaging-Broker
    #webMethods
    #broker
    #Integration-Server-and-ESB


  • 2.  RE: trigger output

    Posted 07/23/07 06:27 PM

    You would benefit greatly from some basic training in Integration Server development.

    Asking a multitude of beginner level questions on a technical discussion forum is not an efficient way to learn any technology including Integration Server.

    After you have spent some quality time with the product documentation (including the PDF’s in the wm_home\Developer\doc\guides folder), please do feel free to ask clarifying questions.

    Mark


    #Integration-Server-and-ESB
    #Universal-Messaging-Broker
    #webMethods
    #broker


  • 3.  RE: trigger output

    Posted 10/11/07 11:14 PM

    OK, I have the solution.

    When You running/testing any service Developer forces to create a new session (or use the same owned) and to assign thread on the server - this session and thread are working for Developer and therefore You see the result of invocation.

    When trigger invokes any service then he for a while is the owner of different new session + thread. This trigger, session or thread have no idea of user using Developer and wanting look at the result.

    Solution (but for development enviroment only):
    Create two Java services in the same folder (class de facto), and in this class create (Shared->Source edit box) instance member: IData pipeline.

    java service tool.latched:setDocument

    • input [document] document
    synchronized (_instance) {
    try {
    _instance.pipeline = IDataUtil.deepClone(pipeline);
    } catch (java.io.IOException e) {
    throw new ServiceException(e);
    }
    }

    java service tool.latched:getDocument

    • output [document] document
    IDataUtil.append(_instance.pipeline, pipeline);

    the same class “latched” “Shared->Source”

    IData pipeline; // it's better to create regular instance member and  use "_instance" static member, but not create any other static members

    In triggering service invoke also tool.latched:setDocument mapping the trigger document to “document”.
    From Developer invoke tool.latched:getDocument.

    Works fine, doesn’t it ?


    #broker
    #webMethods
    #Integration-Server-and-ESB
    #Universal-Messaging-Broker


  • 4.  RE: trigger output

    Posted 10/11/07 11:27 PM

    Wouldn’t invoking savePipeline from the trigger service, then running restorePipeline from Developer achieve the same result?


    #webMethods
    #Universal-Messaging-Broker
    #Integration-Server-and-ESB
    #broker


  • 5.  RE: trigger output

    Posted 10/12/07 07:25 AM

    Yes of course, even better, because of its “$name” selector/key, it was my tiredness (2 AM in the night), and thanks.


    #webMethods
    #broker
    #Universal-Messaging-Broker
    #Integration-Server-and-ESB