Categories
- All Categories
- 75 Oracle Analytics News
- 7 Oracle Analytics Videos
- 14K Oracle Analytics Forums
- 5.2K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 40 Oracle Analytics Trainings
- 59 Oracle Analytics Data Visualizations
- 2 Oracle Analytics Data Visualizations Challenge
- 3 Oracle Analytics Career
- 4 Oracle Analytics Industry
- Find Partners
- For Partners
Moving DV from OAS to OAC
Can someone from Oracle highlight the steps involved in moving the data visualizer on OAS to OAC while keeping the database on-premise?
Best Answers
-
In Oracle Analytics the data isn't stored inside the visualization, therefore you can move your DV objects using the documented processes (BAR export in OAS and BAR import in OAC) and you can then change the connection details in OAC to point to your on-premises databases if needed. Of course you will need to handle the, probably, extra networking setup required (add rules to firewalls to allow the connection, or a dedicated VPN or using the Remote Data Gateway).
Keeping it simple: OAS to OAC isn't any different than OAS to OAS for DV content, while your database connection depends on how you plan to establish such connection.
1 -
More than "migrate" users and groups, you have to create them in Oracle Cloud.
Because OAS doesn't allows you to have local users and groups, it does integrate with the cloud identity provider. That's a different topic (it's outside OAC, just like users and groups are outside OAS).
The whole security part could be tricky and will probably require you to recreate things etc. (OAC wasn't really happy with custom application roles last time I tried to get my own security inside).
It also depends a lot on how your current OAS security looks like (it can be simple or extremely complex: security is a very customized thing).
1 -
What sources are you using for your DV workbooks? If they do use subject areas, then you will have the RPD in both places.
You don't really have many choices anyway and it's quite easy: do you need to use your subject areas as sources in DV? Then you need to deploy your RPD in OAC as well, adapting all the connections to point to the required sources (connection strings for database can be different when being "local" or connecting from cloud).
If you keep developing things in your RPD, you will need to remember to deploy it again, every time, in OAC, or your changes will be just local.
Technically it is impossible to have "a single" RPD for both OAC and your local OAS.
You could "cheat" by creating an Oracle Analytics connection in OAC and point it to your local OAS, and build your DV workbooks only on datasets created through that connection. But it will be datasets, not your subject areas, you will be adding an extra layer that has to be maintained (if you rename something, or need to add new data, it will be take extra work).
Doing a separate move for DV and "classic" (dashboards etc.) means you need to do more work in the meantime, keeping the RPD in sync between OAC and your local OAS (as long as your DV worksbooks need to use the subject area as sources).
1
Answers
-
@Gianni Ceresa Thanks for your prompt response! That makes sense. We will also have to migrate users and groups that we used in OAS to OAC right? We are planning to use Fastconnect for making the connection to on-prem database.
0 -
To add..
Generally, speaking for OAC, you two options to connect from OAC to an on-premise datasource.- Connect to on-premise data sources over private access channel (preferred if datasource supported)
- Connect to on-premise data sources using Data Gateway
Some helpful blogs to give you an overview
1 -
Thanks @SteveF-Oracle! Any idea which of the above 2 categories, the Fast connect would fall into?
0 -
Private Access Channel requires VPN or FastConnect; whereas, Data Gateway does not.
I forgot to provide you the overview link ;-)1 -
Thank you both @Gianni Ceresa and @SteveF-Oracle
1 -
@Gianni Ceresa if you don't mind, I had one more question regarding the transition:- Can we keep the RPD on-premise or do we have to move the RPD to cloud as well? What are the pros and cons of the either option?
0 -
It's technically "impossible".
The RPD is deployed on the product: if you are using OAC the RPD is deployed inside OAC in the cloud.
But you can keep developing your RPD locally and then upload it to OAC. Or download it from OAC locally and you work on it locally (offline).
You should also consider, as long as your RPD is compatible (do you have only relational data sources? then it could be compatible) to use Semantic Modeler: you don't need the Admin tool (Moderl administration tool) installed locally but you can develop your RPD in your browser using the "new" (it's a few years old already) semantic modeler.
Keeping it simple, a typical OAC deployment is everything is in OAC in the cloud, and you just connect to your own database that can be anywhere: on-premises or cloud. But when you move to OAC you generally move everything "analytics" to cloud and use everything there (RPD, Publisher reports, DV workbooks, agents).
This is also because you can't really easily have DV in the cloud and the RPD on-premises: that would mean 2 different independent products, OAC and OAS. Do you really want to have to maintain 2 environments and all the sync issues (just think about security for example)?
0 -
@Gianni Ceresa Thank you for such detailed explanation! We are only planning to move DV workbooks to OAC in the first phase and keep dashboards and database on premise. In the second phase we will be moving dashboards and then finally the database. So given that we will have DV workbooks on OAC but dashboards on premise, where do you see our RPD should be hosted?
0
