Monday, January 27, 2014

Modify OIM11gR2 Session Timeout

Version: Oracle Identity Manager 11g R2
Description: This guide will show you how to increase or decrease session timeout  for the Identity Self Service and Identity System Administration pages.

Thursday, January 23, 2014

OIM Diagnostic Dashboard

Version: Oracle Identity Manager 11g R2
Description: This guide will show how to install the Oracle Identity Diagnostic Dashboard. The Oracle Identity Manager Diagnostic Dashboard is a standalone web application that allows you to validate your OIM installation and  configurations. Several validations include provisioning and reconciliation for some connectors , database connectivity, and target system SSL trust verification. Refer to "Working with the Diagnostic Dashboard" section in "Oracle® Fusion Middleware Administrator's Guide for Oracle Identity Manager" for more information.

Saturday, January 11, 2014

Cloning a Connector

Version: Oracle Identity Manager 11g R2
Description: Oracle Identity Manager has a built-in utility that allows you to clone a connector. This utility generates an XML file containing all the artifacts of the initial state of a connector. If you've made modifications to a connector such as adding new reconciliation and process form fields, they will
not be included. After generating the XML, use the "Import Deployment Manager" to import the XML to your OIM instance. ODSEE/OUD/LDAPV3 Connector, which is part of OID-11.1.1.6.0 connector bundle, is used an example.

Side Notes:
There is a minor issue with the clone utility. The scheduled jobs of the cloned connector will override the scheduled jobs of the original connector. A work around is to modify the XML and change the value of the name attribute in each of the Job tag.

You may run into a case where importing the cloned connector fails. The "Import Deployment Manager" does not have rollbacks, which means changes are made even on failures. If you receive an error, you can re-import the XML since the  "Import Deployment Manager" overrides the existing changes (Process forms are the exception).

Tuesday, January 7, 2014

BI Publisher 11.1.1.6.0 Software Installation

Prerequisites:  Linux environment setup and Oracle Database 11g

Description: This guide will show you how to install BI Publisher 11.1.1.6.0 on a Linux 64 bit environment. Here is an overview of the "Software Only" type installation path:
  1. Install Java. 
  2. Install WebLogic 10.3.6.
  3. Create BI Publisher schemas with Repository Creation Utility 11.1.1.6.0.
  4. Install BI Publisher.
  5. Configure BI Publisher.
Downloads: You can download BI Publisher 11.1.1.6.0 here. The others can be downloaded from Oracle Software Delivery Cloud. You may use a different version of Java as long as the Business Intelligence Suite 11.1.1.6.0 certification matrix is fulfilled.
  1. Java (jdk-7u45-linux-x64.gz)
  2. WebLogic 10.3.6 (V29856-01.zip)
  3. RCU 11.1.1.1.6.0 (V29674-01.zip)
  4. BI Publisher
    • bi_linux_x86_111160_64_disk1_1of2.zip
    • bi_linux_x86_111160_64_disk1_2of2.zip
    • bi_linux_x86_111160_64_disk2_1of2.zip
    • bi_linux_x86_111160_64_disk2_2of2.zip
    • bi_linux_x86_111160_64_disk3.zip
References:  BI Publisher Documentation Library

Monday, January 6, 2014

Bundle Patching OIM 11.1.2.1.x to 11.1.2.1.3

Description:  This guide will show you how to patch Oracle Identity Manager 11g R2 to Bundle Patch 3 (BP3 Patch: 17532765). The bundle patch requires you to apply the patch using OPatch, fill out "patch_oim_wls.profile" file, and run patch_oim_wls.sh script. You can download the patch at My Oracle Support. Read the README given in the patch for a detailed version of the entire process and additional post patching steps.

Tuesday, December 24, 2013

Flat File Connector: Packaging the Connector

Description: Create a flat file connector installer package. The package should contain all the artifacts and metadata for the flat file connector (E.g. IT Resource, Process Form, Resource Object, Adapters, etc). On a new OIM environment, you will be able to install the flat file connector. After connector installation, modify the IT Resources to point to your target system accordingly.

Monday, December 23, 2013

Flat File Connector: Scheduled Tasks and Jobs

Description: To create a scheduled task in Oracle Identity Manager, you need to create an xml of the task and push that xml into the metadata store (MDS) using weblogic import utility or deployment manager. (The xml to be imported may need to be adjusted when using one or the other) After purging the cache, you will be able to create a scheduled job of the type. 

To import the metadata into MDS using weblogic import utility:

1. Modify the weblogic.properties file located in "MW_HOME/Oracle_IDM1/server/bin" directory. Given below is an example. The metadata_file parameter is not used for importing; it mentioned for completeness. The absolute path of my xml file is "/home/oracle/importMetadata/flatfile/metadata/FFLookupRecon.xml".

# Weblogic Server Name on which OIM application is running 

wls_servername=oim_server1

# If you are importing or exporting any out of box event handlers, value is oim. 
# For rest of the out of box metadata, value is OIMMetadata. 
# If you are importing or exporting any custom data, always use application name as OIMMetadata.

application_name=OIMMetadata

# Directory location from which XML file should be imported.
# Lets say I want to import User.xml and it is in the location /scratc/asmaram/temp/oim/file/User.xml, 
# I should give from location value as /scratc/asmaram/temp/oim. Make sure no other files exist 
# in this folder or in its sub folders. Import utility tries to recursively import all the files under the 
# from location folder. This property is only used by weblogicImportMetadata.sh

metadata_from_loc=/home/oracle/importMetadata/flatfile

# Directory location to which XML file should be exported to

metadata_to_loc=

# For example /file/User.xml to export user entity definition. You can specify multiple xml files as comma separated values.
# This property is only used by weblogicExportMetadata.sh and weblogicDeleteMetadata.sh scripts

metadata_files=/metadata/FFLookupRecon.xml

2. Execute weblogicImportMetadata.sh file located in MW_HOME/Oracle_IDM1/server/bin" directory. When running the script, you will be prompted to enter weblogic username, password, and admin server URL.

3. Purge the cache. You will be prompted to enter the administrator credential for OIM and the OIM service URL.

cd  /home/oracle/Oracle/Middleware/Oracle_IDM1/server/bin
./PurgeCache.sh ALL



To import metadata into MDS using deployment manager:

1. Login to the OIM console, go to the Advanced section, and click Import Deployment Manager File under System Management. 


2. Select xml to import.