Upgrade Oracle Access Management OAM from 11gR1 to 11gR2PS3

Follow below steps for upgrading OAM Oracle Access Management, 11gR2 versions  (11.1.2.2.0, 11.1.2.1.0, 11.1.2.0)  to  11gR2PS3 (11.1.2.3.0)
Note: 11.1.1.x.x refers to 11gR1
and    11.1.2.x.x refers to 11gR2

 Steps before starting upgrade or rather these are planning steps before beginning any Oracle IAM installation
1) Check and go through the Certification matrix published for your version of software. The certification matrix provides vendor recommended software product with their version numbers supported which have been fully tested by Oracle.           LINK  http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html
2) Go through the System Requirements document to verify the requirements of the certification have been met for the products that you plan to install. Check/verify the minimum speficiations for disk space, memory, OS version etc.                              LINK  http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-requirements-100147.html
3) Ensure compatibility between your products that you plan to install. For example version of ldap or OID that is compatible with OIM version.
Fusion Middleware Interoperability and Compatibility Guide for Oracle Identity and Access Management
https://docs.oracle.com/cd/E52734_01/core/INTOP/toc.htm
Before you begin upgrading OAM, ensure you have checked the below tasks  LINK
https://docs.oracle.com/cd/E52734_01/core/IAMUP/common_tasks.htm#CHDCCEJI
Also ensure that you are using a Java Development Kit (JDK) version that is supported and certified with Oracle Identity and Access Management 11.1.2.3.0. LINK for jdk http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html

 Check following step
If you are upgrading Oracle Access Management 11g Release 2 (11.1.2.2.0) environments and/or if your Oracle Access Management 11g Release 2 (11.1.2.2.0) environment was upgraded from 11g Release 1, check if $DOMAIN_HOME/config/fmwconfig/upgrade.properties file exists. If it does, rename the file to some other name, before you start with the upgrade.

 Backing up the Existing Environment
To back up the existing environment, you must stop all the servers, and back up the following:
  (a) MW_HOME directory, including the Oracle Home directories inside Middleware Home
  (b) Domain Home directory
  (c) Database schemas
  (d) Oracle Access Manager schemas, MDS schemas, Audit schema and any other dependent schemas
Task No.
Tasks
1
Complete the pre-upgrade tasks before you start the upgrade process.  LINK https://docs.oracle.com/cd/E52734_01/core/IAMUP/upg_psone_oam.htm#CACDIFCI
2
Upgrade Oracle Home by upgrading Oracle WebLogic Server to 10.3.6 (if you are not using Oracle WebLogic Server 10.3.6), applying mandatory patches for Oracle Access Manager, and upgrading Oracle Access Manager binaries to 11.1.2.3.0.
3
Create Oracle Mobile Security Manager (OMSM) schema, if you wish to configure Oracle Mobile Security Suite post upgrade.
4
Upgrade the following schemas using the Patch Set Assistant:

    (a)  Oracle Access Manager (OAM) schema

    (b)  Oracle Platform Security Services (OPSS) schema

    (c)  Audit Services (IAU) schema



Note: When you select Oracle Access Manager (OAM) schema, the OPSS and IAU schemas are also selected
5
Upgrade Oracle Platform Security Services (OPSS). It is highly recommended that you perform this step.
6
If you are upgrading Oracle Access Management 11.1.2 to 11.1.2.3.0, you must copy the modified system or domain mbean configurations.  (copy domain mbean step is only for upgrading from 11.1.2.0.0 ie 11gR2 base version to 11gR2PS3)

If you are upgrading Oracle Access Management 11.1.2.1.0 or 11.1.2.2.0 to 11.1.2.3.0, skip this task.
i.e. skip Step 6 if you are currently in version 11.1.2.1.0, 11.1.2.2.0 and upgrading to 11.1.2.3.0
7
Restart the WebLogic Administration Server and the Access Manager Managed Server(s).
8
Undeploy the coherence#3.7.1.1 library.   https://docs.oracle.com/cd/E52734_01/core/IAMUP/upg_psone_oam.htm#CACGJDDE
9
Upgrade the system configuration of Oracle Access Management. This step is required for the 11.1.2.3.0 features to work.  LINK   https://docs.oracle.com/cd/E52734_01/core/IAMUP/upg_psone_oam.htm#CACECHFB

If you do not perform this step, the upgraded environment will still work, as compatibility mode is supported for Oracle Access Management 11.1.2.x.x upgrade.
10
Extend the Oracle Access Management domain to include Oracle Mobile Security Suite and Policy Manager. LINK https://docs.oracle.com/cd/E52734_01/core/IAMUP/upg_psone_oam.htm#CACCJDJH
11
Start the WebLogic Administration Server and the Oracle Access Management Access Manager (Access Manager) Managed Server(s).
12
Perform the required post-upgrade tasks.  https://docs.oracle.com/cd/E52734_01/core/IAMUP/upg_psone_oam.htm#CACDJFAG
13
Verify the Oracle Access Management upgrade.



Comments

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

Centrally Managed Users (CMU) - New Feature in Oracle Database 18c

Image
Centrally Managed Users (CMU) Centrally Managed Users or CMU is a new feature introduced since Oracle DB 18c which allows simplified database user management through integration with Microsoft Active Directory (AD). Beginning with Oracle Database release 18c, version 18.1 and later supports direct integration with Microsoft Active Directory (AD) using the new centrally managed users capability. CMU allows the Oracle database to perform user authentication and authorization directly against AD. Benefits of CMU With centrally managed users, users accessing the database can be centrally managed to improve an organization's security posture. An enterprise user (a user in Microsoft Active Directory) can be exclusively mapped to a database account, or many enterprise users (in an Microsoft Active Directory group) can be mapped to a shared account in the database. Microsoft Active Directory groups can also be mapped to a database global role, which provides users with additional privilege
Read more