OBIEE 11g to OAS 2025 (8.2) – Legacy vs New Analytics Interface, Model Admin Tool, DV Compatibility

Question

After migrating from OBIEE 11g to Oracle Analytics Server (OAS) 2025 (version 8.2.0.0), we noticed that the default analytics interface—where all reports are accessed—still uses the legacy layout. The URL ends with: https://:/analytics/saw.dll?bieehome 1. Is there a way to access these reports through the new Analytics Interface instead of the legacy one? We would prefer to utilize the latest UI for a more modern user experience if possible. 2. What is the best practice post-migration: to continue using the legacy interface or switch to the new one? If switching to the new interface is recommended, could you explain why? Are there specific benefits in terms of performance, supportability, or user adoption? 3. Regarding the RPD: The migrated repository is still being opened and edited using the Model Administration Tool (MAT). Is MAT considered a legacy tool now that Oracle offers the Semantic Modeler? Would it be advisable to convert the RPD to a Semantic Model, and what implications should we be aware of? 4. Can reports migrated from OBIEE 11g be opened or visualized within the Data Visualization (DV) interface in OAS 2025? If yes, are there any limitations or preparation steps needed to make them compatible? 5. Is DV (Data Visualization) used the same as OBIEE Answers (for building reports/analyses) and then Redwood UI Pages same as OBIEE Dashboards for grouping reports, prompts, tabs We’d appreciate insights or recommendations from others who have completed a similar migration or have experience working with OAS 2025. Thanks in advance!

SteveF-Oracle · Accepted Answer

Hi @User_K47BL , Welcome to the Oracle Analytics community, we are glad you are here: I will give you some starters and others can chime in. 1. Is there a way to access these reports through the new Analytics Interface instead of the legacy one?We would prefer to utilize the latest UI for a more modern user experience if possible. The new interface ishttps://:/dv You can access your legacy content, but it will be opened in the /analtyics UI. 2. What is the best practice post-migration: to continue using the legacy interface or switch to the new one? If switching to the new interface is recommended, could you explain why? Are there specific benefits in terms of performance, supportability, or user adoption? This question may be more subjective, but you can create more modern dashboards, infographic style. You have control, as an author, how the consumer views the content. You can see the "Galleries" link in the top ribbon for some examples and ideas from the community (note: some/most of those are created with Oracle Analytics Cloud which will always be feature forward compared to the annual release of OAS). The modern home page also has options for augmented analytics such as auto insights, explain, and other built in machine learning features. Presentation flows. https://docs.oracle.com/en/middleware/bi/analytics-server/visualize-data.html 3. Regarding the RPD: The migrated repository is still being opened and edited using the Model Administration Tool (MAT). Is MAT considered a legacy tool now that Oracle offers the Semantic Modeler? Would it be advisable to convert the RPD to a Semantic Model, and what implications should we be aware of? You can use either, you can start with making sure all your data sources are supported with Semantic Modeler. https://docs.oracle.com/en/middleware/bi/analytics-server/datamodel-oas/plan-your-migration-model-administration-tool-semantic-modeler.html 4. Can reports migrated from OBIEE 11g be opened or visualized within the Data Visualization (DV) interface in OAS 2025? If yes, are there any limitations or preparation steps needed to make them compatible? Your classic dashboards/analysis will/can be listed on the home page, when you select them, they will be opened in the classic interface (/analytics) 5. Is DV (Data Visualization) used the same as OBIEE Answers (for building reports/analyses) and then Redwood UI Pages same as OBIEE Dashboards for grouping reports, prompts, tabs We’d appreciate insights or recommendations from others who have completed a similar migration or have experience working with OAS 2025. You can build Workbooks similar to Analysis in Answers, but the interface, and features are modernized and the workflow is different. There is a ton of information in the searchable documentation including tutorials, videos. The documentation is also indexed in the internet search engines. There is also an Analytics You Tube channel, so you can see some of the features in action. https://www.youtube.com/watch?v=LSLgmMzYp-E&list=PL6gBNP-Fr8KVcn8qhvoLdoWwVZ32Oyprb I will let other comment here on their migration experiences, I just wanted to get some information out to start. I do suggest if you have a specific question once you get started, to post them as separate threads. Thanks for being here!

Gianni Ceresa · Accepted Answer

1 and 2: it isn't about legacy vs new, it's DV vs "classic". Two different solutions, with different features. DV isn't designed as the full replacement of the other, it's a different approach to analytics. Therefore there isn't a best practice, or even a good practice between the two UIs. It depends on you, your usage of the product, your users.

3: Here as well there isn't a legacy and a new one. There are 2 different tools to do similar (very similar, more than DV vs "classic") things. What you should not do is keep jumping from one to the other. The Model Admin Tool is a very different way to build a RPD compared to Semantic Modeler, just because the UI is very different and allows for more freedom compared to the newer Semantic Modeler that force you more into a given workflow. First thing first is to verify if your RPD works in Semantic Modeler: you can import it, but a number of times the result was quite disappointing for me, with large pieces of the RPD missing and the import didn't really tell me anything about it. You really must approach that "migration" between Model Admin Tool and Semantic Modeler carefully, with a good set of test defined to make sure the result is valid. Semantic Modeler gives you native GIT integration and JSON-language instead of XML, up to you to decide if you need it now or not.

4: By "report" migrated from 11g, you mean Publisher reports? Or you mean "classic" dashboards and analyses?

5: This is a subjective topic. I agree with Steve answer on this above, while I also disagree because for me DV workbooks aren't at all like analyses and dashboard in "classic". Their design, the structure, the approach, the control you have on it has nothing to do. In DV you have 1 workbook that contains multiple canvas that contains multiple visualizations. Each visualization can be seen as the equivalent of an analysis in "classic", a canvas as the equivalent of a dashboard page, a workbook as the equivalent of a dashboard. In "classic" you have permissions on each of those, in DV you don't, you have less granularity from that point of view. This is just one aspect, there is a lot more going on. In my opinion DV and "classic" are for different kind of users, wanting to do different things with the product.