Oracle Analytics Cloud and Server Idea Lab

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

OAS API

Needs Votes
141
Views
7
Comments

Organization Name

CSE Consorzio Servizi Bancari

Description

OAS API to run DataFlow from an external application. The goal is to centralize the schedule of new DataFlow thorugh an API.

Use Case and Business Need

The goal is to centralize the schedule of new DataFlow thorugh an API.

Original Idea Number: 901495af00

18
18 votes

Needs Votes · Last Updated

Comments

  • Michal Zima
    Michal Zima Rank 6 - Analytics Lead

    Official (published and documented) Oracle Analytics Server API is definitelly a must requirement.
    Not only for running DF, but also for manipulating DV Data Sets - like for example:

    • creating DS
    • re-uploading file DS
    • purging BI Server cache entries, connected with particular DS
    • changing definition of DS
      etc...
  • Mrudula
    Mrudula Rank 1 - Community Starter

    We have a similar requirement to invoke the dataflows from an external application like ODI. It would be much helpful if this enhancement is addressed by the development team.

  • User_0THLM
    User_0THLM Rank 1 - Community Starter

    It is indeed a very important requirement for us as well. We would need to have REST API end points (Preferably) and/or SOAP end points to handle DV related Artefacts especially to migrate DV workbooks, Datasets, Data Flows, Connections etc. Migrations can also ease out if there are provisions to do it programmatically.

    Many a times we need Data flow to run in an event-based manner. We would want to programmatically run the Data flow with our ETL loads or some other event-based activities. Access provisioning is also an impediment most of the times as Data flow does not currently support access provisioning and is very much at user level right now.

    Also, the API end points may also help us in managing the DV artefacts, like removing duplicated objects (Datasets, Data Flow, Workbooks, Connections, jobs etc.). We can also possibly perform better quota management.

  • BrandonH
    BrandonH Rank 4 - Community Specialist

    I would not support this. The maturity level of Data Flows within DV doesn't seem to be enterprise grade at this time. Utilizing them within and enterprise scheduling system would be a bad architecture choice compared to other products on the market for transforming data eg ODI.

  • Michal Zima
    Michal Zima Rank 6 - Analytics Lead

    @BrandonH It is not very much clear, what you would not support ? Just API for manipulating data flows or API for DV as such (for manipulating other DV objects as well - connections, data sets, workbooks….) ? I hope the first option is correct. You are right, that data flows are not at the same level of maturity as dedicated ETL tools (like ODI) and I don’t think it has such ambition. It could just help analytics user with limited knowledge or without access to dedicated ETL tool with simple data manipulations/transformation directly within Analytics suite.

  • BrandonH
    BrandonH Rank 4 - Community Specialist

    @Michal Zima My comment was specific to the OP's post / enhancement request (API for dataflows)