There are no specific licensing options for making content public, and the July release of OAC is introducing, in LA the ability to make content publicly available.

In addition, the access token tab and the mcp connect tab are not visible by default as of the July OAC release - they are only visible if the developer options is enabled.

@Muhammad Shoaib - yes, you'll need a webtier to act as a layer to redirect incoming traffic on the public API endpoints to the internal endpoints that are mapped as seen in that bi_vh.conf file.

Apologies for the confusion - in OAS, since that is all configured by our customers, we cannot pre-configure the WLS webtier. As such, we provide the best practice Enterprise Deployment Guide and that includes how to expose the APIs per the config link I sent earlier. Mike

I think the answer to your question is that it's the same process as in OAS 2025. The OAS APIs require configuration of the webtier to expose the endpoints per the documentation links https://docs.oracle.com/en/middleware/bi/analytics-server/oasri/index.html Specifically the bi_vh.conf documented here shows how to do that…

The OAS APIs require configuration of the webtier to expose the endpoints per the documentation links https://docs.oracle.com/en/middleware/bi/analytics-server/oasri/index.html Specifically the bi_vh.conf documented here shows how to do that configuration:…

Hi Jitendra - thanks for your suggestion. I'd be interested to learn more about the types of integration you have worked on - it sounds mostly at the data level? Have you been embedding FAIDP workbooks into APEX as well? Thanks Mike

Hi, thanks for your question. Yes. it is read only. You may want to consider using the OAC MCP Server. This YT video provides an overveiw. Regards Mike

Have you considered the Oracle Analytics MCP server?

Please also test checking the style option in safe domains. Thanks Mike

Please could you log an SR with Support. Thanks.

IDCS / IAM won't send a login page to an iframe for security reasons so you see this error. If you have federated logins between SaaS and OAC then you could try the three-legged OAuth setting.…

Please could you log this as an idea in the ideas lab - it's something we'd like to implement for the REST API. Currently, you'd need to use the SOAP APIs: https://docs.oracle.com/en/cloud/paas/analytics-cloud/acsdv/c_xmlviewservice_service.html…

You need to include the embedding code for analytics within an iframe for React as the knockout binding used by JET won't work with the vdom in React - something like this.. import React from "react"; import ReactDOM from "react-dom";class App extends React.Component { render() { return <iframe id='OACembed'…

Thanks for your question and I'm glad to hear it works well for you. However, this is currently not planned for classic. Regards Mike

Hi, thanks for your question, I'm afriad that this isn't available in OAS 2025. Mike

Hi Hasan - thanks for your question. The embedding feature is based around a consumer experience which is why when your users create a filter it is being lost on page refresh. Depoending on your use case, it is possible to programmatically create filters and pass parameters to the embedded canvas that could form the basis…

Thanks for logging this idea! Regards Mike

Thanks for logging this request. Mike

Yes, it did ! https://docs.oracle.com/en/cloud/paas/analytics-cloud/acapi/op-20210901-catalog-type-id-actions-changeownership-post.html