Oracle Access Manager - Multi Data Center

OAM Multi-Data Center configuration
(and OIM Multi Data Cener configuration)
MDC or Multi-Data Center configuration is supported in 11gR2 PS2 and PS3. It uses T2P tools and utilities to create OAM configurations in each Data Center, one being Master and other its clone. Policies need to be in synch between the two Data Centers.
Chapter 7  Using Multi-Data Center in 11.1.2.2
Chapter 17.1 Introducing Multi-Data Center in 11.1.2.3

MDC is supported in 3 configurations
  • Active - Active             Both Data Center are active and provide services to users
  • Active - Hot Standby    Both Data center are active but user requests are not sent to the Hot standby site
  • Active - Passive            Both Data Center are running but only Active site is servicing user requests while the Passive site services are not started. The services in the Passive site can be started in a reasonable amount of time in case the Primary Data Center goes down.
Weblogic domains do not span across multi-data centers. Weblogic domains are set up in one data center only, typically OAM deployments are clustered with two or more nodes in a cluster under a Weblogic domain.
Across two geographically apart Data Center, the OAM in the second Data Center is a clone of the first. You can configure the two Data Center OAMs in either Active-Active, Active-Passive or Active-Hot Standby. 


Oracle Identity Management 11gR2PS3 Multi Data Center Deployment Guide
OAM 11.1.2.3 Implementing Multi-Data Center with Oracle Access Management





Comments

  1. atif xhaikhDecember 4, 2019 at 4:09 AM

    This is highly informatics, crisp and clear. I think that everything has been described in systematic manner so that reader could get maximum information and learn many things.
    servidor cloud CPanel brasil

    ReplyDelete

Post a Comment

Popular posts from this blog

VMware fix for Invalid manifest and ova file import failed errors

Image
Recently we got a OVA file for a virtual machine. The vendor instructions were to import the ova file in vmware Workstation, Player for Windows/Linux, Fusion for Mac, and VirtualBox as well.  The instructions were to take the available package and launch the VM with VMware workstation. The package contained  Module.mf, Module.ovf and Module-disk.vmdk and a Module.ova file. The .mf and .ovf file were 2 KB each whereas the vmdk was several gigs. The package also contained a Module.ova file which was several gigs as well. OVF           Open Virtualization Format MF             Manifest file VMDK       Virtual Machine Disk OVA           Open Virtualization Appliance The ovf file is a xml file that contains metadata for the ovf package The mf file contains the SHA1 hash codes of all files in the package The vmdk file is the disk image of the virtual machine,  VMware Workstation or VirtualBox. (vmdk format was originally developed by VMware and is an open format now). All of
Read more

SOAPUI - import certificate

Image
Note: SoapUI has two versions, one is open source and second Professional version. The open source can be download here . (confirmed link 12/19/2018). SSL Handshake issue:   There is an Issue in SoapUI version 5.3.0 (and 5.2.0 version) with SSL handshake error. It was resolved by updating below in vmoptions file ( refer here ). However, the error that shows up while trying to load wsdl is "Error loading WSDL" as below The fix is to Enable TLS 1.2 protocol for SOAP/REST calls in SoapUI, by ammending the vmoptions file to add the directive for TLS as (-Dsoapui.https.protocols=TLSv1.2). Refer here . Update: Version 5.5.0 does not have this issue. If you are on 5.3.0 better upgrade to 5.5.0 which is available now (Feb 2019). I had above issue as well as another issue reaching to https endpoint. Upgrade to 5.5.0 resolved issue. Select "Check for updates" under the Help menu and you will get option for upgrade. Select upgrade current version and accept all defaul
Read more

Session Timeout in Oracle Access Manager

Image
Session Timeout in Oracle Access Manager (OAM) The session lifetime and Idle timeout entries control how long a user's session is valid. In OAM, a user session is an object which represents an authenticated user. This object is stored in the server memory and if Database session persistence is enabled, this object is stored or available in the database. Each session is unique and is identified by both a userid and Session ID (session identifier), see screenshot below "OAM User Session Management".  A valid session means a user has been authenticated with OAM. A session can have following three states: 1) active 2) inactive 3) expired When a session is created it is in active state and is available as an object in the OAM. After a set time - idle timeout, the session moves or transitions to inactive state. And finally after the Session Lifetime time, the session is marked as expired. Expired sessions are removed from server memory. Read more about Session Lifetime
Read more