Disaster recovery approach for Oracle Fusion Middleware Product Suite at Your Company.

(This is an example ,make changes as per your topology)

Table of Contents

1. Representation of products in both data centers ................................................................................. 3

2. Recovering Oracle packaged products using RCU ................................................................................ 4

2.1 OSB/SOA BPM 11.1.1.7 ................................................................................................................. 4

2.2 WebLogic Server 10.3.6 ................................................................................................................ 5

3. Custom Products/Applications if Any ................................................................................................... 6

4. Oracle Security Products ....................................................................................................................... 6

5. Oracle API GateWay[OAG] .................................................................................................................... 6

6. Other Dependencies ............................................................................................................................. 7

6.1 Binaries .......................................................................................................................................... 7

6.2 Instance Configurations ................................................................................................................ 7

7. External API Endpoint failover. ............................................................................................................. 7

7.1 Failover of soaAPI.yourserver.com ............................................................................................... 7

1. Representation of products in both data centers

Secondary SitePrimary Site

Applications

Database

Data ReplicationSAP DS

OEDQ

Informatica

OSB

SOA

BPM

OAG

X DataGuard Replication

SQL Server Mirroring

Uses local database and does not have

transaction data

SAP DS

OEDQ

Informatica

OSB

SOA

BPM

OAG

Oracle Database

SQL Server Database

Other Database

No Replication/Not ImplementedX

X

Uses Data Guard Secondary DB for transaction data

X

2. Recovering Oracle packaged products using RCU

Middleware

Domain Configuration

Middleware – tar copy

Domain Configuration - tar

copy

Data guard replication

Dehydration store Dehydration store

2.1 OSB/SOA BPM 11.1.1.7 SOA OSB has 3 areas to be restored. a. Binaries,

• Binaries are stored in the file system. DR instance is a replica of Production binaries

b. Configurations related to domain • DR instance is a replica of Production configurations • If while configuring the domains, virtual names are used (

soaosbhost1,soaosbhost2 etc) so no modifications are needed • /etc/hosts entries for virtual hostnames must match the IPs in DR

environment. These entries should be documented as a part of the appendix.

c. SOA OSB BPM uses 3 schemas stored in Oracle Database.

• MDS, BAM and SOA schema should be stored in Data Guard secondary DB in xxxxxxx Data center - [TODO:insert machine names]

• Connection strings in WebLogic Data sources should be made to point vips viz. dbvip1 and dbvip2 for DR

• Entries for those should be modified in /etc/hosts

2.2 WebLogic Server10.3.6

Middleware

Domain Configuration

Middleware – tar copy

Domain Configuration - tar

copy

Dehydration store Dehydration store – local to DR

WebLogic Server has 3 areas to be restored independently. a. Binaries,

• Binaries are stored in the file system. DR instance is a replica of Production binaries

b. Configurations related to domain • DR instance is a replica of Production configurations • If while configuring the domains, virtual names are used (

soaosbhost1,soaosbhost2 etc) so no modifications are needed • /etc/hosts entries for virtual hostnames must match the IPs in DR

environment. These entries should be documented as a part of the appendix.

c. If WebLogic Server uses schemas stored in Oracle Database for Identity management

• WEBLOGIC schema should be stored in DR database independent of production - xxxxxxx.xxxxxxx.xxxxx

• This is purely a security store has no transaction data. • Connection strings in WebLogic Data sources should be made to point VIPs

viz. dbvip1 and dbvip2 for DR

3. Custom Products/Applications if Any

Deployment in production Deployment in DR

Application Schema Application Schema

Data guard Failover

a. The custom Application Schemas should be replicated into the Secondary database in

Sacramento Data center via Data Guard b. Data sources for Applications in WebLogic should be modified to include new values. c. The schema should be pointing to virtual names such as dbscan.clearwire.local that

points to the SCAN IP of Oracle DB. d. Application should be started after those modifications are made to verify if instances

come up fine

4. Oracle Security Products

Currently there are no Security Products Implemented.

5. Oracle API Gateway [OAG]

Currently Oracle API Gateway is not implemented.

6. Other Dependencies

TODO: Team to identify dependencies and propose DR steps.

6.1 Binaries

6.2 Instance Configurations

7. External API Endpoint failover.

7.1 Failover of soaAPI.CLEARWIRE.com

TODO: Architecture Team to elaborate further.