Trigger BICC Extract from an OIC integration

Business Requirement and Challenges

Oracle BICC is a powerful tool allowing extraction of full or incremental data from SaaS public ViewObjects for subsequent loads to target BI and other systems.

If we want OIC to orchestrate the extraction and uploading the result to target instance, there should be an option to initiate the extract request by an OIC integration.

The documentation of BICC provides the documentation on describes the endpoint and sample payload that can be used to achieve SOAP API (oracle.com).

However – the straightforward import of SOAP endpoint and invoking in an OIC integration – does not work.

Here are the challenges we faced:

• The WSDL described in the documentation (https://servername.fa.us2.oraclecloud.com/bi/ess/esswebservice?wsdl) can not be directly imported to OIC because of internal references.
• Once the issue above was resolved by Oracle Support Note we faced next issue “Fault String : A required header representing a Message Addressing Property is not present”

Solution

• Following the Oracle Support note above, perform the following:
  1. Download the WSDL from your env by going to the following URL: /bi/ess/esswebservice?WSDL
  2. Download the definitions by going to the following URL: /bi/ess/esswebservice?WSDL=ESSWebServiceAbstract.wsdl
  3. Take the content of definitions element from the 2nd file and merge it to the first WSDL that you downloaded
     
  4. Save the merged file to something like bi-ess-full.wsdl (make sure it ends with wsdl)
  5. Zip the file to something like this: bi-ess-full.zip (do not use MacOS compress – it will add manifest that will prevent OIC parsing)
  6. Upload the Zip file above to OIC SOAP connection:
     
  7. Set security for the connection by specifying User/Password token
• In the OIC integration, define custom SOAP headers to allow calling ESSWEBSERVICE:
  1. Download XSD schema of custom SOAP Headers from the url: https://www.w3.org/2006/03/addressing/ws-addr.xsd
  2. Define MessageId and Action custom SOAP headers by using the schema above:
     
  3. Map the parameters and headers:
     
• Receive the ESS Job request id and poll for its completion
• Download the BICC generated file from UCM and proceed with the orchestration logic.