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
| Name Surname |[email protected]| Account Cloud Engineer | example |
28
28
29
29
## Document Purpose
@@ -68,7 +68,7 @@ This is a living document, additional sections will be added as the engagement p
68
68
69
69
Organizations use on-premises deployments of E-Business Suite (EBS) for a wide range of functionalities, including Financials, Order Management, Procurement, Manufacturing and Logistics. These implementations are often customized to seamlessly integrate with other applications to meet business requirements. So it’s counterproductive to re-architect software from scratch. OCI has the flexibility to support everything Organizations are currently doing with EBS.
70
70
71
-
Most On-Premises EBS deployments can be migrated to run on Oracle Cloud Infrastructure (OCI) without requiring significant configuration, integration, or business process changes, and result in an implementation that is more flexible, more reliable, higher performance, and lower cost than either On-Premises or other Cloud vendors. Running EBS on Oracle Cloud enables you to:
71
+
Most On-Premises EBS deployments can be migrated to run on OCI without requiring significant configuration, integration, or business process changes, and result in an implementation that is more flexible, more reliable, higher performance, and lower cost than either On-Premises or other Cloud vendors. Running EBS on Oracle Cloud enables you to:
72
72
73
73
- Increase business agility
74
74
- Better manage growth
@@ -99,7 +99,7 @@ Currently Customer's EBS workload is a multi node deployment of EBS release 12.2
99
99
- Two nodes EBS farm (Deployed to WebLogic Clusters of Managed Servers) hosting web, forms and concurrent managers and
100
100
- A single external facing node hosting web functionality to support iSupplier portal.
101
101
102
-
Two client connection routes, internal via a WAN and externally via the internet. Both routes employ https which is terminated on a load-balancer. The internal farm employs a shared application tier home.
102
+
Two client connection routes, internal via a WAN and externally via the internet. Both routes employ https which is terminated on a load-balancer. The internal application cluster employs a shared application tier home.
103
103
104
104
The reporting elements of the solution are provided using Oracle Business Intelligence Enterprise Edition 'X' together with Oracle Apex 'X' for access to archived legacy data.
105
105
@@ -139,8 +139,6 @@ In addition to these requirements, the [CIS Oracle Cloud Infrastructure Foundati
139
139
140
140
Current EBS workload has four environments:
141
141
142
-
Current EBS workload has four environments:
143
-
144
142
-**Production**
145
143
- EBS Application Version: **12.2**
146
144
- Oracle Database Version: **19c**
@@ -159,18 +157,23 @@ Current EBS workload has four environments:
159
157
- Number of Application Node: Single Application Node including Web, Forms and Concurrent Managers Instances
160
158
- 1 Single Instance of EBS is running on DMZ zone, catering for external end-users
161
159
- Number of Database Node: Single node Oracle Restart
162
-
-**DR**
160
+
-**Disaster Recovery (DR)**
163
161
- This is a copy of Production environment which is kept in synch with Production environment using following synchronization methods:
164
162
- EBS application tier are kept in synch with Production using rsync job scheduled via crontab
165
163
166
164
- The EBS database repository is synchronized with DR using Oracle Data Guard Solution
167
-
168
-
#### Environment Sizing
165
+
166
+
167
+
#### Environment Sizing
169
168
170
169
*Guide:*
171
170
172
171
*A section describing the Current EBS workload of the Customer: Sizing Details, Current On-Premise BoM*
173
172
173
+
*Example:*
174
+
175
+
Partner will capture current EBS workload sizing here.
176
+
174
177
### High Availability and Disaster Recovery Requirements
175
178
176
179
*Guide:*
@@ -235,11 +238,11 @@ The Customer has both internal and external endpoints of their EBS workload.
235
238
236
239
**Internal Users:**
237
240
238
-
Users access EBS using URL https://`<Internal LB URL:port>`. The connection flows via external/internal firewall to the Load Balancer in DMZ. Load Balancer terminates the SSL and passes the request on port 8010 to EBS internal servers 'X', 'Y'. The internal EBS servers communicate with EBS RAC Database on Linux VMs 'A', 'B' using port 1531 and validate the user request.
241
+
Users access EBS using URL https://`<Internal LB URL:port>`. The connection flows via external/internal firewall to the Load Balancer in DMZ. Load Balancer terminates the Secure Socket Layer (SSL) and passes the request on port 8010 to EBS internal servers. The internal EBS servers communicate with EBS RAC Database on Linux VMs using Database listener port 1531 and validate the user request.
239
242
240
243
**External Users:**
241
244
242
-
External users access EBS using URL https://`<External LB URL:port>`. The connection flows via external/internal firewall to the Load Balancer in DMZ. Load Balancer terminates the SSL and passes the request on port 8010 to EBS external server 'X'.
245
+
External users access EBS using URL https://`<External LB URL:port>`. The connection flows via external/internal firewall to the Load Balancer in DMZ. Load Balancer terminates the SSL and passes the request on port 8010 to EBS external server.
243
246
244
247
### Workload Monitoring Requirements
245
248
@@ -438,6 +441,8 @@ Abbreviations per resource type are listed below. This list may not be complete.
438
441
439
442
#### Security and Identity Management
440
443
444
+
*Guide:*
445
+
441
446
This chapter covers the Security and Identity Management definitions and resources which will be implemented for Customer.
442
447
443
448
##### Universal Security and Identity and Access Management Principles
@@ -640,7 +645,7 @@ Deployment architecture for the 'Hub and Spoke Topology' is illustrated below:
640
645
{width="90%" height="90%"}
641
646
642
647
643
-
Deployment architecture including 'Tenancy - A' and Tenancy - B' are illustrated in the design below:
648
+
Deployment architecture including two tenancy: 'Tenancy - A' and Tenancy - B' are illustrated in the design below:
644
649
645
650

646
651
@@ -656,7 +661,7 @@ Deployment architecture including 'Tenancy - A' and Tenancy - B' are illustrated
656
661
657
662
*Example:*
658
663
659
-
Proposed plan is to move EBS Application server (\_12.2) in the compute VM shapes on the latest OS and kernel version (which is supported). On-Premises RAC Database (**19c**) will be migrated to a VM-DB RAC system based on a Multi-tenant Architecture.
664
+
Proposed plan is to move EBS Application server (\_12.2) in the compute VM shapes on the latest OS and kernel version (which is supported). On-Premises RAC Database (**19c**) will be migrated to a VM-DB RAC system based on a multitenant architecture.
660
665
661
666
Oracle Cloud Infrastructure Web Application Firewall (WAF) helps you make your endpoints more secure by monitoring and filtering out potentially malicious traffic. It is a cloud-based, Payment Card Industry (PCI) compliant, global security service that protects applications from malicious and unwanted internet traffic.
662
667
@@ -669,6 +674,15 @@ Oracle Cloud Infrastructure Web Application Firewall (WAF) helps you make your e
669
674
*Example:*
670
675
671
676
Oracle Maximum Availability Architecture (MAA) is Oracle's best practice blueprint based on proven Oracle high availability technologies and recommendations. The goal of MAA is to achieve the optimal high availability architecture at the lowest cost and complexity. Papers are published on the Oracle Technology Network [OTN](http://www.oracle.com/goto/maa).
677
+
To achieve maximum Oracle E-Business Suite database availability, Oracle recommends deploying EBS on an Oracle Database MAA foundation that includes the following technologies:
678
+
- Oracle Real Application Clusters (RAC)
679
+
- Oracle Data Guard
680
+
- Oracle Flashback Database
681
+
- Oracle Automatic Storage Management
682
+
- Oracle Recovery Manager and Oracle Secure Backup
683
+
- Oracle Online Upgrade Using Edition Based Redefinition
684
+
685
+
Please refer to the following reference paper for detail.
672
686
673
687
*Reference:*
674
688
@@ -701,11 +715,11 @@ The objective of the security architecture is to enable you to maintain your sec
701
715
Oracle has designed security into every aspect of our infrastructure to help our customers achieve better protection, isolation and control. We started by taking a unique design approach, separating the network and server environments. This way, if an attack occurs on a VM, we can contain that threat and prevent it from moving to other servers, resulting in better protection and lower risk for customers.
702
716
703
717
We also hyper-segment our physical network and backend infrastructure for secure isolation between customer instances and backend hosts. Additionally, we’ve implemented hardware-based root of trust, making sure each server is pristine each and every time it is provisioned.
704
-
718
+
Below diagram shows security posture of EBS in OCI.
For each customer’s VCN there is a range of defense in depth protections available spanning across **layers 3-7**.
722
+
For each customer’s VCN there is a range of defense in depth protections available spanning across **layers 3-7**.
709
723
710
724
**VCN (1):** A VCN provides isolation for your workload from any other workload on Oracle Cloud Infrastructure, including your other workloads in a different VCN.
711
725
@@ -739,7 +753,8 @@ __Note:__Please see generic OCI security guidelines in the [Annex](#security-gui
739
753
740
754
*Example:*
741
755
742
-
Customer will access EBS workload internally over the OCI backbone and EBS external endpoints will be secured by OCI Web Application Firewall (WAF).
756
+
Customer will access EBS workload internally over the OCI FastConnect connectivity solution and EBS external endpoints will be secured by OCI Web Application Firewall (WAF). FastConnect is a private, dedicated connectivity which improves security, it supports bandwidths from 1Gbps to 10Gbps.
757
+
An alternative option to FastConnect is Virtual Private Network (VPN). VPN could also be a back-up configuration if FastConnect is down.
743
758
744
759
### Workload Monitoring
745
760
@@ -749,7 +764,12 @@ Customer will access EBS workload internally over the OCI backbone and EBS exter
749
764
750
765
*Example:*
751
766
752
-
Customer will use OEM to monitor their EBS workload.
767
+
Customer will use OEM to monitor their EBS workload. Customer can also leverage OCI Stack Monitoring for EBS.
768
+
For detail please check the below blog article specified in reference section.
769
+
770
+
*Reference:*
771
+
772
+
[OCI Stack Monitoring for EBS](https://blogs.oracle.com/observability/post/oci-stack-monitoring)
753
773
754
774
### Regulations and Compliances
755
775
@@ -805,9 +825,21 @@ Automation is provided for a selection of deployment and management scenarios. T
805
825
806
826
### OCI Networking
807
827
828
+
*Guide:*
829
+
830
+
*A section describing OCI networking capabilities and features*
831
+
832
+
*Example:*
833
+
834
+
Oracle Cloud Infrastructure (OCI) networking and connectivity products and services enable customers to manage and scale their networks.
835
+
Please refer to the following article for a better understanding of OCI networking capabilities and how it can be leverages for Customer advantage.
-[OCI Networking Best Practices](https://www.ateam-oracle.com/post/oci-networking-best-practices-recommendations-and-tips---part-one---general-oci-networking)
841
+
-[Best practices for hybrid and multicloud OCI networking design](https://docs.oracle.com/en/solutions/oci-best-practices-networking/index.html#GUID-368122DF-8B74-4F38-A55F-23E47E04AEB2)
842
+
811
843
812
844
## Sizing and Bill of Materials
813
845
@@ -817,7 +849,7 @@ Automation is provided for a selection of deployment and management scenarios. T
817
849
818
850
*Example:*
819
851
820
-
OCI sizing of the EBS workload and its integrated Solution components are reflected in the diagram below:
852
+
A sample sizing of the EBS workload is reflected in the diagram below for reference purposes:
821
853
822
854

0 commit comments