1 Reply Latest reply on Feb 24, 2014 9:06 PM by Keith Babo

    one Input multiple external references Scenario in BPMN ?

    Mauro Araujo Newbie

      Hi, is possible to have something like this in SY  ?

      The objective here is obtain a XML

      That The 1st input (service Input) is going to Equipment  Then we do some validations and the result goes to feed the Input Of MeterData (The input now is  the result of the first one)

      Meterdata Out  passes in Gateway and Feed the input of the next Service .... if something wrong or not valid an exception is throwed and the procces finished. 


      Service Input -> Equipment*->MeterDataService*->ObjectsProces*->InterfaceUtils *->ServiceInput responce


      (*The inputs here are Xml Lists  and not simple boolean or flag  responses, result of the previous executed service )

      each reference is a diferent wsdl and the input depends of the previous.

      Does SY  + BPM can handle This ?

      How I do the mapping of In/out of each service in BPM , I use SY task or onother ?

      Is there any example i can get some guidance , if not possible what are the alternatives(Bean  , BPEL  ... ).




      Thank You For your Help

        • 1. Re: one Input multiple external references Scenario in BPMN ?
          Keith Babo Master

          It is definitely possible to orchestrate all of these services with BPM.  All you need to do is map the result of each invocation into a process variable inside your BPMN 2 process.  For creating the response, you can: (1) add some logic to create the reply in an onExit in the final SY service task in your workflow, or (2) add a final task to the workflow which creates the response.


          You will have to experiment a bit with the content model for your invocations to determine the best way to pass around the "XML lists".  You might want to transform them to Java objects or you can always just leave them as XML.


          Your best bet is to take an existing quickstart like bpm-service and modify it a bit to implement some of the behavior needed in your target application.  That will give you a feel for how mapping between the process and service invocation works.