What is Oracle's vision for enabling organizations to implement the MUDE for OAC?
Background: In an on-premise OBIEE system, we license the software. Because we have a license, we can install OBIEE on our developer's machines, and they can work in the normal MUD 'Check out a Project' --- 'Publish to Network' environment.
Today: Under the covers, OAC is OBIEE 12.2.1.2.0. We are physically able to run in a MUD environment by installing OBIEE 12.2.1.2.0 on our developer's machines, with everything working exactly as it did for the on-prem. The repository is still good old OBIEE, and we have not run into any problems with refreshing the model in OAC from an OBIEE 12.2.1.2.0 repository developed in the developer machines. It seems to not care - works great.
But we want to make sure we are completely on the up-and-up, that we aren't doing anything "naughty". So the question: For an Oracle customer who pays for OAC on a subscription basis (i.e. no OBIEE "license" per-se), is it still permissible for that customer to work with the same MUD strategy as described above? Is it allowable to download, install, and run OBIEE 12.2.1.2.0 as a developer who is feeding the OAC system? If not, what is Oracle's vision for enabling multi-user repository development in OAC?