Oracle Analytics Cloud and Server

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

OBIEE 12c to OAS 2025 migration - security issues

Accepted answer
80
Views
6
Comments

Hello,

I'm trying to import in OAS 2025 a bar file exported from OBIEE 12c.
The bar file contains whole application, including RPD, catalog and authorization.
I tried via the console as well as via importarchive.sh

My problem is: after importing, all default OAS roles are missing, including BIServiceAdministrator.

As a result, after the bar import, user weblogic does not have access to the most console functionality.
For example, I am not able to access "Roles and Permissions" and fix the situation.

What should be done to migrate my bar file to OAS 2025 and retain the default OAS roles?

Thanks,

Alex

Best Answer

Answers

  • Gianni Ceresa
    edited Apr 24, 2025 12:14PM

    Hi,

    When you import your BAR, you can decide to not override the security, and you then manually do a "merge" between your custom 12c security and the default OAS 2025 security. This allows you to maintain all the default roles and policies, and to be able to inherit what needed in your own security.

    Or, just recreate all you need: you maybe don't have access through DV, but you still have access to FMW EM, where you can create roles and assign policies. And you can also do that via WLST if you extract the default security from OAS 2025 before to override everything with your BAR.

  • AM_1
    AM_1 Rank 4 - Community Specialist

    Gianni,
    Thanks for your prompt response!
    Unfortunately, I can't get a response from EM.
    Even right after clean installation
    myserver:9500/console works fine,
    but when I try
    myserver:9500/em and enter weblogic credentials, the page freezes for several minutes and then I'm getting a timeout error.

    Can you point me the scripts for WLST ?

  • AM_1
    AM_1 Rank 4 - Community Specialist

    Thank you Sumanth!
    I will try this.

  • Follow https://support.oracle.com/epmos/faces/DocContentDisplay?id=1423893.1 to enable the discovery cache for EM, then your login will work. I usually use the method of adding the few config lines to the file and restart the AdminServer.

    It's a known thing that EM is "painful" to login into because of timeouts.

  • There isn't a written set of WLST commands to create the default security model, you would generally build it by exporting the default security (or if you have a script that does read the security model and generate all the WLST commands to recreate it).

    And I don't have the default OAS 2025 security model around, still didn't need to migrate somebody to it so far…