Showing posts from July, 2020


Some applications can expose REST services using either path parameters or query parameters.   For example Oracle Fusion applications provides REST API's using both path parameters and query parameters.  Path Parameter Sample:  https://fusion-host-name:443/hcmRestApi/resources/latest/userAccounts/ { UserGUID } When you provide this URL in OIC relative URL path , OIC will create a parameter called UserGUID with type as String.  You can use this parameter variable to pass dynamic values during runtime.  Query Parameter Sample:  https://idcs-host-name/admin/v1/Users? filter =userName+sw+%22vijaya%22 https://oracle-fusion-hostname/hcmRestApi/resources/latest/emps? q =PersonNumber=112233 In this scenario , we cant provide URL with ?  in OIC rest end point.   We can provide value till ? mark.  In the above examples, query parameters are filter and q strings.    While creating REST invoke , select add query parameters and provide Query parameters as filter and q.  We can provide values t

OIC - Invoke Oracle Fusion ESS Scheduler Job for Job Set

You may come across a scenario where in you may need to submit multiple ESS jobs or BIP Jobs  in parallel or in sequence.  In that case ,  you need to create a job set comprising multiple ESS jobs.  Oracle provide following SOAP services to invoke ESS jobs.  ERP Integration service  https://<fa-host-name>/fscmService/ErpIntegrationService ESS Webservice  https://<fa-host-name>/ess/esswebservice We can use ESS Webservice to invoke a Job Set or Individual Job Definition.  These are the sample payloads for invoking Job Definition or a Job Set.  JOB_DEFINITION_PAYLOAD <soapenv:Envelope xmlns:sch="" xmlns:soapenv="" xmlns:typ="">    <soapenv:Header>       <wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="" xmlns:wsu=&quo