Integrating PCS, DOCS and BI Publisher using OSB/SOACS – Part 1

Introduction

In this 3 part blog series, I will be demonstrating on how to use PCS to invoke OSB (On-Prem or SOACS) services and upload a report/doc generated using BI Publisher to DOCS.  The following components are used in this demonstration:

  • Oracle Document Cloud Service (DOCS)
  • Process Cloud Service (PCS) with DOCS integration configured.
  • BI Publisher 12.2.1 with sample reports installed
  • SOACS with OSB or OSB On-Prem.

In this blog series, I will be covering the following topics:
Part 1 – Overview and Setup (Part 1) – cover the use case, configuration steps for PCS, BI Publisher and DOCS REST Services.
Part 2 – OSB Services Design (Part 2) – cover the OSB service design in details and what you need to look out for when you design your OSB services.
Part 3 – PCS Application Design and Testing (Part 3) – cover the PCS process design and how to test the sample project.

Use Case

We will use PCS to design a Salary Report request process, the process allows the user to submit a salary report request and generate a PDF report in BI Publisher.  We also need to create a report folder dynamically and attach the PDF report to the newly created folder in the same PCS process instance so that we can review and approve the generated report.

PCS_DOCS_BI_OSB_High-Level

PCS and DOCS Integration

We will need to configure PCS and DOCS integration in order for this demonstration to work, the instruction for PCS and DOCS configuration can be found here.

PCS_DOCS_BI_OSB_PCS-DOCS

We will use the default folder structure in this demonstration. However, you can also configure the folder structure (shown below) if it’s required.

PCS_DOCS_BI_OSB_PCS-DOCS Configuration in PCS

Once the PCS and DOCS integration has been configured, when a process is initiated, a process folder for that process instance will be created in DOCS.  We can then login to DOCS using the same username and password we used to configure PCS and DOCS integration to review the folder structure:

PCS_DOCS_BI_OSB_DOCS_FolderStructure

DOCS REST Services

DOCS exposes number of REST services to retrieve folder/item information and upload the file using multipart messages.  In this demonstration, we will use the following DOCS REST API to retrieve the folder ID and upload file:

Resource URI Method Description
/api/1.1/folders/items GET Get a collection of all items (folders and files) that user has access to, including folders that others have shared with that user. The type field indicates if an item is a folder or file.
/api/1.1/folders/{folder id} GET Get folder information (metadata) for the specified folder.
/api/1.1/folders/{folder id} POST Create a new subfolder in the specified destination folder.
/api/1.1/folders/{folder id}/items GET Get a collection of child items (folders and files) in the specified folder. The type field indicates if an item is a folder or file.
/api/1.1/files/data POST Upload a new file using a multipart request to specify destination and file information.

BI Publisher

BI Publisher exposes a web service called report service, which has an operation called runReport. This operation allows you to run a report with or without input parameters and return the generated report in base64 encoded data format.  A list of operations available in BI Report Service is here

In this demonstration, we will be using the sample report called SalaryReport without parameter, the generated report will be a PDF file in base64 encoded data format.

SOACS and OSB on-premise

If you are planning to use SOACS, you will need to expose the BI Publisher report service externally so it can be invoked by SOACS.  If you are using OSB on-premise to invoke the BI Publisher report service, you will need to expose the OSB service externally to allow PCS to invoke, and you will also need to import the SSL certificate from DOCS to your OSB managed server trust store.

Summary

In this first part of this blog series, we have covered the use case, basic integration configuration and setup required for the PCS, DOCS, BI Publisher and OSB.  In part 2 of the blog, we will examine OSB services design in detail.

Comments

  1. Derek,
    We have followed your article and successfully integrated the PCS with DOCs for our dynamic document routing PCS process. Thanks for sharing an excellent article and knowledge base.

    Cheers Navin

Add Your Comment