Get Involved. Join the Conversation.


    Arvind Mathivanan
    Using Dynamic Payloads for SOA Cloud ESS Job Set
    Topic posted September 11, 2019 by Arvind MathivananBronze Medal: 1,250+ Points, tagged Cloud, Integration, PaaS, SOACS 
    30 Views, 3 Comments
    Using Dynamic Payloads for SOA Cloud ESS Job Set

    We use ESS as part of our SOA Cloud implementation. We have a case where we need to pass dynamic values for one of the field for an ESS Job that is part of a Job Set. Say Order Number is a parameter that I need to dynamically pass for the Job. In the Job Set creation, this field will be null for the Job as it can pull all orders during the schedule. The issue I see is  If I call the Job individually, it allows dynamic values but If I call the Job Set through ESS Web-Service, Even if I pass an order number for the Job, it's ignoring the dynamic value for Order number and only passes the default payload (order number as null) in Job Set. Am I missing something? If this is the expected behavior of Job Set, how would I be able to achieve this scenario?



    • Kanchankumar Khedkar

      You should be able to pass parameters dynamically to ESS job even if you are executing jobs via web service. 

      <element name="submitESSJobRequest">
      <element name="jobPackageName" type="string"/>
      <element name="jobDefinitionName" type="string"/>
      <element maxOccurs="unbounded" minOccurs="0" name="paramList" type="string"/>

      You should be able to pass the parameters in paramList 




      You should send the parameters in exact the same sequence as defined on job. 

      Hope this helps.



      • Arvind Mathivanan

        Hi Kanchan,

        Thanks for your reply. Your answer is more for sending dynamic values for an ESS Job. That works perfectly fine through the web-service. But this doesn't work for a Job-Set. The request for Job Set would be as below:

                <![CDATA[<ns1:processRequest xmlns:ns1=""> 
                <![CDATA[<ns1:process xmlns:ns1="">

    • Arvind Mathivanan

      I see currently the payload field is getting automatically substituted by the server during execution. Below Doc has details but that should be rectified i feel.