You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: data-platform/analytical-data-platform-lakehouse/workload-architecture-documents/obia-with-odi-migration-to-oci/wad/wad.md
|Author Author|[email protected]| Initial Author (to be removed for customer) | Oracle |
44
44
45
45
## Document Purpose
46
46
@@ -50,7 +50,7 @@ This document provides a high-level solution definition for the Oracle solution
50
50
51
51
# Business Context
52
52
53
-
(WAD Template) is using OBIA version 11g which they want to migrate to OCI and leverage where possible the advantages of a cloud native solution. It is important to know which version of OBIA (WAD Template) is using. The recommended version to deploy on OCI is OBIA 11.1.1.10.3 PS3. This version is certified with OAC and ADW. It is possible to use OBIA version 11.1.1.0.2 on OCI but only DBCS and OAC can be used as cloud products. Other components are on- premise applications. It would be best if the source application is running on OCI as well, but that is not a fixed requirement. It is important to check which version customer is using and what the latest certification matrix is and what current support guidelines are. Version 11.1.1.10.3 is still in support. An upgrade to the 11.1.1.10.3 version from 11.1.1.10.2 or earlier will be mainly a technology upgrade from 11g to 12c but due to the change of technology and the level of customisations in ODI this will require more or less effort.
53
+
(ExampleCustomer) is using OBIA version 11g which they want to migrate to OCI and leverage where possible the advantages of a cloud native solution. It is important to know which version of OBIA (ExampleCustomer) is using. The recommended version to deploy on OCI is OBIA 11.1.1.10.3 PS3. This version is certified with OAC and ADW. It is possible to use OBIA version 11.1.1.0.2 on OCI but only DBCS and OAC can be used as cloud products. Other components are on- premise applications. It would be best if the source application is running on OCI as well, but that is not a fixed requirement. It is important to check which version customer is using and what the latest certification matrix is and what current support guidelines are. Version 11.1.1.10.3 is still in support. An upgrade to the 11.1.1.10.3 version from 11.1.1.10.2 or earlier will be mainly a technology upgrade from 11g to 12c but due to the change of technology and the level of customisations in ODI this will require more or less effort.
54
54
55
55
Success criteria:
56
56
@@ -62,7 +62,7 @@ Success criteria:
62
62
63
63
## Workload Business Value
64
64
65
-
(WAD Template) is running a recent installation of OBIA 11g. with support and security risks. Modernising this Data Warehouse and Analytics solution will help (WAD Template) to be ready for the future again. Migrating to OCI and using ADW, OAC and ODI creates an as much as possible cloud native solution and leverages the existing OBIEE, ODI and Database knowledge in a modern setting while preserving previously made investments in Data Warehouse, extractions and analytics.
65
+
(ExampleCustomer) is running a recent installation of OBIA 11g. with support and security risks. Modernising this Data Warehouse and Analytics solution will help (ExampleCustomer) to be ready for the future again. Migrating to OCI and using ADW, OAC and ODI creates an as much as possible cloud native solution and leverages the existing OBIEE, ODI and Database knowledge in a modern setting while preserving previously made investments in Data Warehouse, extractions and analytics.
66
66
67
67
After the migration the OBIA installation will continue as a custom data warehouse and analytics solution based on the cloud native successors of the migrated stack.
68
68
@@ -193,7 +193,7 @@ You can use a OCI Bastion service to provide secure access to your resources. Th
193
193
194
194
### VCN and Subnets
195
195
196
-
For security reasons the the Data Warehouse and Analytics components are positioned in a separate VCN. Spoke VCNs are not accessible from the internet. All components are placed in private subnets. The subnets where OAC, ADW and the Linux developer instance are in can be configured to be accessible from customers network or accessed through the Bastion Service in the Hub VCN. VCN's require to have CIDR ranges that are not overlapping with other VCN's and are also not overlapping with IP ranges used in (WAD Template) network.
196
+
For security reasons the the Data Warehouse and Analytics components are positioned in a separate VCN. Spoke VCNs are not accessible from the internet. All components are placed in private subnets. The subnets where OAC, ADW and the Linux developer instance are in can be configured to be accessible from customers network or accessed through the Bastion Service in the Hub VCN. VCN's require to have CIDR ranges that are not overlapping with other VCN's and are also not overlapping with IP ranges used in (ExampleCustomer) network.
197
197
198
198
### Network Firewall
199
199
@@ -307,11 +307,11 @@ For departmental groups:
307
307
-\<prefix\>-\<compartment\>-\<purpose\>-admins
308
308
-\<prefix\>-\<compartment\>-\<purpose\>-users
309
309
310
-
The value for \<prefix\> or the full names **must be agreed** with (WAD Template).
310
+
The value for \<prefix\> or the full names **must be agreed** with (ExampleCustomer).
311
311
312
312
### Security and Identity Management
313
313
314
-
This chapter covers the Security and Identity Management definitions and resources which will be implemented for (WAD Template).
314
+
This chapter covers the Security and Identity Management definitions and resources which will be implemented for (ExampleCustomer).
315
315
316
316
#### Universal Security and Identity and Access Management Principles
0 commit comments