WCP12c - BAM Integration

I have uploaded to my GitHub the WebCenter Portal Extension -  BAM Dashboard Task Flow which helps to integrate with Oracle BAM Dashboards.

https://github.com/DanielMerchan/WebCenterExtensions



Summary of steps about how to use it (more detailed in GitHub)

Summary - Installation:
  • The project produces an ADF JAR Library that you can deploy within the WebCenter Portal Shared-Library extend.spaces.webapp or in a separate Shared-Library referenced by extend.spaces.webapp weblogic.xml
  • It requires to create an ADF Connection in WebCenter Portal using the Enterprise Manager (BAM Connection).
 

Usage:
  • Add BAM Dashboard Task Flow into WCP Resource Catalog.
  • Add BAM Dashboard Task Flow into a WCP Portal Page.
  • Configure BAM Dashboard Task Flow Input Parameters. (A BAM Dashboard Proxy Page URL looks like http://wcp12c:7004/bam/composer/faces/proxypage?DashboardParameters=%28ProcessSelection%3D%5BALL%5D%3B%29&dashboard=ProcessHealth&project=ProcessAnalytics_v2) The importan part is DashboardParameters=%28ProcessSelection%3D%5BALL%5D%3B%29&dashboard=ProcessHealth&project=ProcessAnalytics_v2 The rest is built by using the BAM Connection name configured.
    • BAM Connection Name: Provide the ADF Connection Name created for BAM. (E.g. BAMConnection) E.g.: BAMConnection
    • Dashboard: Name of the BAM Dashboard to embed. It corresponds to the URL parameter dashboard E.g.: ProcessHealth
    • Dashboard Parameters (Optional): URL Parameters of the Dashboard. It corresponds to the URL parameter DashboardParameters E.g.: ProcessSelection%3D[ALL]%3B
    • Project: BAM Project the dashboard belongs. It matches to the URL parameter project. E.g.: ProcessAnalytics_v2
  • Configure Display Options:
    • Strecht Content: True
  • Configure Content Style:
    • Give a minimum height. E.g.: 800px

Comments

Post a Comment

Popular posts from this blog

OJET: Inter-Module communication in TypeScript Template

Image
In this post I bring another example on how to Communicate Modules using the Oracle JET - TypeScript Template based on the Oracle JET Cookbook: InterModule Communication From now and so on will create multiple examples using TypeScript for those who are not familiar with it and wants to turn the Cookbook examples into TypeScript :). The example ( ojet-typescript-list-detail ) can be found as usual in my GitHub repository: https://github.com/DanielMerchan/ojet-examples This example is a bit different compared to the Cookbook example where the modules are not running at the same time within a Module. This example is built as described in the following images: Customers module acts as the Wrapper Module. It coordinates when to load the list and detail modules. Customers module makes use also of signals npm module for communication between Customers-List, Customers-Detail. Explanation of the Example customers.js is the coordinator responsible module for: initiali
Read more

OJET: Build and Deploy in an Application Server

Image
There are some other sources where an Oracle JET Application is packaged and deployed as a WAR in Oracle WebLogic Application Server (Arda Eralp) https://blogs.oracle.com/ardaeralp/deploy-oracle-jet-application-to-weblogic-server (Andrejus Baranovski's) http://andrejusb.blogspot.com/2016/07/serving-oracle-jet-application-from.html They may look bit old or maybe because they call directly grunt tasks by using the grunt-cli . In this post I will update a bit these posts in Oracle JET 6.1.0 and the usage of ojet build (instead of calling the grunt tasks) for also building the corresponding WAR file. The example can be found in my GIT repository: https://github.com/DanielMerchan/ojet-examples Let's start... Install grunt-war module in your Oracle JET Application. npm install grunt-war --save-dev Create a war.js (or call it whatever you want) in /scripts/grunt/config folder under your souce files. This is a sample code inside of it, check https://www.npmjs.com/packag
Read more

OJET: Select All options using only Checkboxset

Image
This is an example on how to select all other options by using another oj-checkboxset. GitHub: ojet-checkbockset-select-all The idea is to keep track of the selection and make use of the on-value-changed as described in the following code. self.colorOptions = ko.observableArray([ { id: "blueopt", value: "blue", color: "Blue" }, { id: "greenopt", value: "green", color: "Green" }, { id: "redopt", value: "red", color: "Red" }, { id: "limeopt", value: "lime", color: "Lime" }, { id: "aquaopt", value: "aqua", color: "Aqua" }, ]); self.selectAll = ko.observableArray([]); self.currentColor = ko.observableArray(["red"]); self.selectAllOptionChanged = (event) => { const newSelection = event.detail.value; if (newSelection.indexOf('all')
Read more