Fusion Middleware Home is corrupted (Common Env Script missing or Not executable)!

While running the opatch apply or opatch lsinventory we got below error.

Error :

/app/oracle/middleware/Oracle_SOA1/OPatch/opatch
Fusion Middleware Home is corrupted (Common Env Script missing or Not executable)!
/app/oracle/middleware/Oracle_SOA1/jdk/bin/java is not a valid executable for this platform.
OPatch cannot proceed!


./opatch lsinventory -invPtrLoc ../oraInst.loc
Fusion Middleware Home is corrupted (Common Env Script missing or Not executable)!
/app/oracle/middleware/Oracle_SOA1/jdk/bin/java is not a valid executable for this platform. OPatch cannot proceed!
OPatch returns with error code = 1

Solution :

1. Keep a backup of existing commEnv.sh file 
2. Restore from backup valid commEnv.sh file

3.Change the file permission of commEnv.sh file
4. Execute the opatch commands again to confirm everything works fine.

Thanks,

Arihant

OIM 11G R2 PS3 Lab 11: Three ways to export OIM Metadata (MDS)

We can export complete OIM MDS in 3 different ways.

1) MDS Export  from Weblogic EM Console

2) MDS Export  from wlst.sh script

3) MDS Export  from weblogicExportMetadata.sh

---------------------------------------------------------------------------------------------------------------

1) MDS Export  from Weblogic EM Console

* Login to Weblogic EM console > Expand Identity and Access > OIM > oim

* Expand  Application Defined Mbean > oracle.mds.lcm > server :oim_server1

* Expand Application : OIMAPPMetadata > MDSAppRuntime > MDSAppRuntime  on right hand      side click on Operations tab >> Click on exportMetadata

* In to Location give path where you want to export (No need to create directory manually, It will automatically create the directory) > Click on docs

* Click on Add

* In this lab we are exporting complete MDS that we enter /**. If you want to export any specific file you can do that. Ex -/file/User.xml ( For export User.xml)

* After setting the to location and docs, click on Invoke

* Check the status after clicking Invoke. It should be operation executed successfully.

* Check the export in to location.

2) MDS Export  from wlst.sh script

 * Go to /app/oracle/middleware/oracle_common/common/bin/ location and run wlst.sh conmand
     Enter the below Parameters manually.

•  connect()
•  Weblogic 
•  Weblogic user password
• t3://localhost:7001 (Server URL with admin port)
• exportMetadata(application='OIMMetadata', server='oim_server1', toLocation='/tmp/mds1') (If you want to export the MDS in specific location you can set that in toLocation)   
• If you want to export any specific file run below command
• exportMetadata(application='OIMAppMetadata',server='oim_server1',toLocation='/tmp/export',docs='/db/oim-config.xml',applicationVersion='*')

* Check the successfully transferred messages at the end.

*  Check the export in to location.

3) MDS Export  from weblogicExportMetadata.sh

* Go to /app/oracle/middleware/Oracle_IDM1/server/bin location and edit weblogic.properties

* Enter below Parameter

application_name=OIMMetadata

metadata_to_loc=/tmp/mds2 

metadata_files=/**  

* From the same location set the OIM_ORACLE_HOME ,run weblogicExportMetadata.sh command and enter below parameters manually.

     export OIM_ORACLE_HOME=/app/oracle/middleware/Oracle_IDM1

•  connect()
•  Weblogic 
•  Weblogic user password
• t3://localhost:7001 (Server URL with admin port)

* Check the export in to location.

Regards,
Arihant Baid

OIM 11G R2 PS3 Lab 3: Oracle Unified Directory (OUD) 11g PS3 (11.1.2.3.0) Connector Installation, Provisioning and Reconciliation

High Level Steps

1) Install the OUD connector in OIM
2) Configure IT Resource
3) Create Form Designer
4) Create Application Instance
5) Run Catalog Synchronization Job
6) Run LDAP Connector OU Lookup Reconciliation
7) Create a user and Provisioned to OUD

Start

1) Install the OUD connector in OIM

* Copy OID connecter  from (OID/OUD/ODSEE all are in OID connector) Connector folder to ConnectorDefaultDirectory folder

* Login to sysadmin console

*  Click on Manage Connector

*  Click on Install

* Select ODESS/OUD/LDAP3 connector and click on Continue

* Click on Continue

*  Check the Installation Status : Successful and click on Exit

2) Configure IT Resource

* Click on IT Resource

* Search IT Resource Type as LDAP >> DSEE Server >> Edit

* Provide the below IT Resource Parameters

   Configuration Lookup=Lookup.LDAP.OUD.Configuration
   baseContexts=dc=oud,dc=com
   credentials=*********
    host=192.168.1.124
    port=389
   principal=cn=Directory Manager
   ssl=no

3) Create Form Designer

* Click on Sandbox

* Click on Create  Sandbox

* Give Sandbox name

* Click on Form Designer

* Click on Create

*  Select Resource as LDAP, Give Form Type name and click on Create

4) Create Application Instance

* Click on Application Instance

* Give Name, Select Resource Object, IT Resource, Select Form and click on Save

 * Select sandbox and click on Publish Sandbox

* Click on Yes

5) Run Catalog Synchronization Job

* Click on Scheduler

*
* Search for Catalog Synchronization Job and click on Run Now

6) Run LDAP Connector OU Lookup Reconciliation

 Note - Crate some OU's in OUD LDAP before you run OU Lookup Scheduler.

* Search for LDAP Connector OU Lookup Reconciliation job and click on Run Now

* Login to design console and check the Code and Decode value in Lookup.LDAP.Organization lookup. After running the above job it should bring the  organizationalUnit from LDAP.

7) Create a user and Provisioned to OUD

* Login to Identity console and click on Users from Manage Tab

* Click on Create

* Fill the user from details and click on Save

* Click on Request Accounts from Users Account tab

* Select OUD App >> Add Selected to Cart >> Next

* Check the Grant will be effective immediately upon request completion and update

* Select the Container DN from the lookup and click on update

* Click on Submit

* Refresh the User's Account tab and check the account status it should be Provisioned 

* Check the User in OUD LDAP

Regards,
Arihant Baid