OIM AD Connector Patching

I need to apply a connector patch for AD connector. I know the patch id also. Please let me know the steps for downloading this patch and applying it to the existing connector.
Edited by: 955932 on Oct 10, 2012 11:10 PM

You must have Oracle customer support identifier to login oracle support for patch download
If you have support identifier and knowing the patch ID, login into the Oracle support :
http://support.oracle.com
Finally download it from Patches section
readme will be having all the required step for patch installation.

Similar Messages

Applying OIM Connector Patches

I currently have OIM 9.1 with connector version 9.0.4.1 and what to apply connector patch 7017816 to correct an issue with the AD password sync loop issue. Are there any special instructions somewhere on how to apply the patch? If I attempt to install the patch following the connector instructions on a initial install the patch breaks several adapters causing them to no longer compile.

I have seen similar issues on rare instances but neither I nor Oracle OIM support has ever been able to figure out what is causing it.
What I usually do is to delete the generated source code and then ask for a recompile in the design client This causes the source code to be regenerated which hopefully will resolve your problem.
Hope this helps
/M

AD Connector Patch 11.1.1.5.0A (AD connector patch 14190610)

hi all,
I am having OIM 11gR2 (11.1.2.0).
I have a confusion about applying patch for AD connector 11.1.1.5.0.
I need to know that in the Patch download zip file (AD connector patch 14190610) there are many folders that are same as available in AD connector 11.1.5.0, in the read me file for this patch there is no mentioning of what to do with the rest of the folders, its only saying
*"1)On the Target where connector server is Installed.*
*Unzip the content of the bundle ActiveDirectory.Connector-1.1.0.6380.zip to the folder where Connector server is installed."*
on the connector download page
http://www.oracle.com/technetwork/middleware/id-mgmt/downloads/connectors-101674.html
for AD connector mentioned is that
*"Please apply AD connector patch 14190610 after downloading from MOS (My Oracle Support) if you are using this connector against OIM 11.1.2.0 or above."*
So it means that its a patch only not the full connector so then what is the use of the rest of the folders (configuration, dataset, owglue, resources,upgrade, xml) provided in that patch zip file other then the "bundle ActiveDirectory.Connector-1.1.0.6380.zip"
Do we need to run the "Upgrade Connector" after the installation of Connector 11.1.1.5.0 ?
any comments
Thanks...

Hi,
Even I couldn't find one, so I guess there isn't one. So, what I did was install new connector server in the same windows box running on different port and switched the OIM configuration to use it. My environment is running fine after this change.
Regards,
Sunny

OIM Database Connectors version upgrade

Hi,
I need to upgrade the OIM DB User Management Connector from release 9.0.4.1 to 9.0.4.4. and the OIM Database Application Table Connector from release 9.0.4.1 to 9.1.0.1. Any one knows which patches should be applied for these upgrades? I can't find any documentation regarding this.
Thank you.
Regards.

First of all have a look at the read me which comes along with the connector patch and see if the upgrade you are trying to achieve is supported or not. For example:
The *4 Deploying the Patch Set* section in the latest release *9.0.4.5* of the DB User Management Connector clearly says the following:
Note:
Direct upgrade to release 9.0.4.5 from release 9.0.4.3 or earlier releases is not supported.
Same applies to DB App Tables Connector as well. See and confirm it by yourself because I don't have those versions of the connector.
Thanks
Sunny

Windows 2000 connector Patch issue (Patch ID: 8318738)

Hi,
We have applied the latest Windows 2000 connector Patch on our DEV environment.
While trying to provision the Windows resource (the user’s home network shared folder), effectively there is some permissions issue that is encountered while executing in the DLL and it effectively causes some page fault that prompts the OS to kill the process and the OC4J instance is restarted.
FYI..
10/01/11 01:26:17 Running GETUSERANDPERMISSIONS
10/01/11 01:26:17 Target Class = com.thortech.xl.util.adapters.tcUtilStringOperations
10/01/11 01:26:17 Running GETGRANTUSERPERMISSIONS
10/01/11 01:26:17 Target Class = com.thortech.xl.util.adapters.tcUtilStringOperations
10/01/11 01:26:17 Running GETPERMCOMMANDANDFOLDERPATH
10/01/11 01:26:17 Target Class = com.thortech.xl.util.adapters.tcUtilStringOperations
10/01/11 01:26:17 Running GETFULLGRANTUSERSHARECOMMAND
10/01/11 01:26:17 Target Class = com.thortech.xl.util.adapters.tcUtilStringOperations
10/01/11 01:26:17 Running EXECUTEGRANTUSERFOLDERPERMISSIONSCOMMAND
10/01/11 01:26:17 Target Class = com.thortech.xl.integration.WindowsNT40.tcUtilWindowsNT40
Entering method runRemoteCommand
szAdminName is =:OIMADMIN
szDomainName is =:dev.abc.com
szCommand is =:cmd /c cacls %home%\user70065 /E /P User70065:C 2>C:\WINDOWS\system32\windowsConnectorError.txt
temp is \\hou016.dev.abc.com\root\cimv2
connecting to server
# An unexpected error has been detected by HotSpot Virtual Machine:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x695befe7, pid=2212, tid=4184
# Java VM: Java HotSpot(TM) Server VM (1.5.0_06-b05 mixed mode)
# Problematic frame:
# C [tcWindowsNT40.dll+0x1efe7]
# An error report file with more information is saved as hs_err_pid2212.log
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
10/01/11 01:26:20 Start process
WARNING: Code-source D:\product\OASDev_2\j2ee\halOIM\applications\Xellerate\soap.jar (from manifest of /D:/product/OASDev_2/j2ee/halOIM/applications/Xellerate/xlGenConnector.jar) has the same filename but is not identical to /D:/product/OASDev_2/webservices/lib/soap.jar (from <code-source> (ignore manifest Class-Path) in META-INF/boot.xml in D:\product\OASDev_2\j2ee\home\oc4j.jar). If it contains different versions of the same classes, it will be masked as the latter is already visible in the search path of loader Xellerate.root:0.0.0.
WARNING: Code-source D:\product\OASDev_2\j2ee\halOIM\applications\Xellerate\http_client.jar (from manifest of /D:/product/OASDev_2/j2ee/halOIM/applications/Xellerate/xlGenConnector.jar) has the same filename but is not identical to /D:/product/OASDev_2/j2ee/home/lib/http_client.jar (from <code-source> (ignore manifest Class-Path) in META-INF/boot.xml in D:\product\OASDev_2\j2ee\home\oc4j.jar). If it contains different versions of the same classes, it will be masked as the latter is already visible in the search path of loader Xellerate.root:0.0.0.
WARNING: Code-source D:\product\OASDev_2\j2ee\halOIM\applications\Xellerate\xlWebApp\WEB-INF\lib\share.jar (from WEB-INF/lib/ directory in D:\product\OASDev_2\j2ee\halOIM\applications\Xellerate\xlWebApp\WEB-INF\lib) has the same filename but is not identical to /D:/product/OASDev_2/jlib/share.jar (from <code-source> in /D:/product/OASDev_2/j2ee/halOIM/config/server.xml). If it contains different versions of the same classes, it will be masked as the latter is already visible in the search path of loader Xellerate.web.xlWebApp:0.0.0.
10/01/11 01:26:38
GMS: address is HOUOIM602V:4079
WARNING: Code-source D:\product\OASDev_2\j2ee\halOIM\applications\Xellerate\xlScheduler\WEB-INF\lib\xlScheduler.jar (from WEB-INF/lib/ directory in D:\product\OASDev_2\j2ee\halOIM\applications\Xellerate\xlScheduler\WEB-INF\lib) has the same filename but is not identical to /D:/product/OASDev_2/j2ee/halOIM/applications/Xellerate/xlScheduler.jar (from manifest of /D:/product/OASDev_2/j2ee/halOIM/applications/Xellerate/xlDataObjectBeans.jar). If it contains different versions of the same classes, it will be masked as the latter is already visible in the search path of loader Xellerate.web.xlScheduler:0.0.0.
10/01/11 01:26:42 Loading xalan.jar for XPathAPI.
10/01/11 01:26:43 Nexaweb Technologies Inc.(C)2000-2004. All Rights Reserved.
10/01/11 01:26:43 Nexaweb Technologies Inc.
10/01/11 01:26:43 10 Canal Park
10/01/11 01:26:43 Cambridge, MA 02141
Any one of you faced a similar issue if you also happend to apply this patch? Please suggest if you interpret any other issue from the logs.
Thanks in advance.

Guys,
Any Help on this Issue?

OIM AD connector- Groups added natively in AD getting deleted

We are facing this issue with the OIM Ad connector- 11.1.1.5.0. The scenario is :
1. OIM user get created
2. OIM provisions user to AD and adds user to 2 groups ( 1 and 2)
3. AD Administrator logs into the AD directly and adds 3 groups to the user ( Group3,Group4 and Group5)
4. OIM admin goes to the resources tab and adds Group6 to the user from within OIM AD resource
Shouldn't we see that the user account on AD be a member of group1,group2,group3,group4,group5 and group6. This is the expected behavior
What we are seeing on the account is that only group1,group2 and group6 are visible.
I understand the the groups - Group3,Group4 and Group5 will not be visible on the resource form unless we do a recon but OIM should not be DELETING groups added natively on AD
Any help on this issue will be appreciated

Thanks everyone. I do agree that the behavior should be such that all 6 groups should be visible on the user on the target (AD) system. However, we are seeing that the groups added natively within AD are getting deleted and OIM is "truing up" the user account with the groups that are added within the process form , i.e. the scenario described above. OIM is actually deleting the groups that were added manually on AD.
If I do trigger a target recon, then I can see that all the groups are reflected on the user within OIM. However running this task every hour or rather every time I need to add an entitlement on a user is not a feasible solution,would you agree?. Also this is a limitation that cannot be placed on a helpdesk person. Rather , if this is the only solution , it should be a functionality of the connector.
Please note that the connector deployed is v11.1.1.5.0 and NOT the 9.1.1.7. The 9.x connector did behave as expected , i.e it did not delete any groups. However the new ICF based connector is deleting groups. Is there a setting within the connector configuration to turn on/off this functionality?
This is what I see in the connector server logs
<VERBOSE>: Class-> ActiveDirectoryUtils, Method -> GetDnFromPath, Message -> Exiting the method. Returning the value = CN=TEST6,CN=Users,DC=OIM,DC=Test,DC=com
<VERBOSE>: Class-> CustomAttributeHandlers, Method -> UpdateDeFromCa_OpAtt_Groups, Message -> DirectoryEntry path = LDAP://xx.xx.xx.xxx/CN=Print,DC=OIM,DC=Test,DC=com. Removing: CN=TEST6,CN=Users,DC=OIM,DC=Test,DC=com from the property: member
"PRINT" is the group that was added natively on AD.

OIM GTC Connector

Hi All,
I have a requirement where I need to provision and reconcile into multiple flat files and metadata in each of them may differ.
So I was planning to create custom GTC connector each for provisioning and reconciliation respectively.
Can anyone please suggest me the best possible solution for this.
Is Oracle planning to launch a connector for flat file in near future which can help in such scenarios?

I have tried using default GTC connector for reconciliation (without trusted source reconciliation). I have three fields in the file UserName,FirstName,LastName and have mapped them to account profile for OIM, a reconciliation rule has been created which looks for equality of User Id in both OIM and flat file. The User ID is present in both flat file and OIM and is same.
I have done configuration on both OIM 9100 and also on OIM 9101.
It is working in OIM 9100 but not on 9101 and giving me null pointer exception. Any idea why it is not working on 9101.
When I have a new entry in flat file that exists in OIM the connector link the two and creates the resource form. But when I try to update/delete any existing value in flat file it is showing me a strange behaviour.
For update it links the same profile again to different resource form (basically it link the account using "one entity match found" however it should be "one process match found")and for delete it is not working. I am assuming that it is not able to call process tasks.
Can anyone tell me why it is doing so. My reconciliation rule is working fine.

OIM DBUM connector error

Hi All,
I have instlalled the OIM DBUM connector for Oracle databse. I have provided all the parametrs except connectionproperties column while configuring the itresource for the connector.when trying to run the schedulers OOTB to populate lookups synchronized with target iam getting the following error.please help me out.
oracle.iam.connectors.icfcommon.exceptions.OIMException: Thor.API.Exceptions.tcAPIException: Row index out of bounds
thanks.

Hi Ketan,
I have installed DBUM *11.1.1.6* on OIM *11.1.1.5* locally.
in the connector guide i followed below steps.
1. Sec:2.2.1 Installing the Connector in Oracle Identity Manager
2. Sec:2.3 Postinstallation
Section 2.3.1, "Postinstallation on Oracle Identity Manager"
Section 2.3.1.1, "Configuring the Target System As a Trusted Source"-notdone
Section 2.3.1.2, "Changing to the Required Input Locale" -----left it with default values
Section 2.3.1.3, "Clearing Content Related to Connector Resource Bundles from the
Server Cache"
Section 2.3.1.4, "Creating the Administrator Account on Oracle Database Vault"-----not done
Section 2.3.1.5, "Setting up the Lookup Definition for Connection Pooling"---not done
Section 2.3.1.6, "Enabling Logging for Oracle Identity Manager"
Section 2.3.2 Configuring the IT Resource for the Target System
In this we have a parameter text field called Connection Properties ----I left it blank and dont know what needs to be filled.
Remaining parameters are set
Database Name-IP of DB machine
DB Type
JDBC Driver
JDBC URL
Login Password
Login User
I could see connector installation success message. But when I am trying to run the scheduled jobs configured to populate the lookups , getting the above mentioned error.
Thanks.
Section 2.3.2, "Configuring the IT Resource for the Target System"
Section 2.3.3, "Configuring the Connector to Support Multiple Versions of the
Target System"------------------->not done
Edited by: Powerlad on Sep 2, 2012 11:55 PM

Documentation for OIM AD Connector

Hi,
Can any one suggest any documentation for OIM AD Connector which gives steps to develop adapters and so on

OIM Connector Guide for AD - > http://download.oracle.com/docs/cd/E10150_01/doc.904/e10158/toc.htm
OIM Connector Framework Guide -> http://download.oracle.com/docs/cd/E10150_01/doc.904/e10178/toc.htm
Maynot have a great deal of details, but something to start off with.
Rgds, Ajay

OIM - OID11g Connector Logging

Hi All,
I have updated the logging.xml as below to enable the logging for OIM -OID Connector 11.1.1.5.0 but I can't see anything in the file (File is created but it has no logs):
<log_handler name='oid-handler' level='TRACE:32' class='oracle.core.ojdl.logging.ODLHandlerFactory'>
<property name='logreader:' value='off'/>
<property name='path' value='/u01/oracle/iam_middleware/user_projects/domains/IAMdomain/oidconnector.log'/>
<property name='format' value='ODL-Text'/>
<property name='useThreadName' value='true'/>
<property name='locale' value='en'/>
<property name='maxFileSize' value='5242880'/>
<property name='maxLogSize' value='52428800'/>
<property name='encoding' value='UTF-8'/>
</log_handler>
<logger name="OIMCP.OID" level="TRACE:32" useParentHandlers="false">
<handler name="oid-handler"/>
<handler name="console-handler"/>
</logger>
Please help.
Thanks
Sunny

Firstly I would normally manage OIM 11g logging through Oracle Enterprise Manager rather than directly in a logging.xml file, with log information appearing in the OIM server diagnostic log rather than a dedicated log file as you have done. That is not to say what you are doing is wrong (I cannot comment as I have never managed OIM 11g logging in this way.)
The other thing that may be wrong is the logger you are using. You have logger OIMCP.OID. For my OIM11g OID connector logging I am using the standard logger of XL_INTG.OID.

OIM PoepleSoft Connector

Hi All,
I am installing OIM - PeopleSoft connector for Employee Reeconciliation. As part of Target System Configuration for Full Reconciliation(Trusted Source) i performed all the steps specified in Connector documentation on Target System. Summary of the steps is Full publish of Person Data in PeopleSoft as xml files and feeding these xml as initial data load to OIM. After running the process scheduler for Data Publish of PERSON_BASIC_FULLSYNC message i dont see any xml files being generated. Rather it only gives me one log file and a .trc file. The log file says the process has ran successfully. But no expected out.
Any one who previously performed these steps successfully please share your experience and pointer would be appreciated
PeopleSoft HRMS 8.8
People Tools : 8.9.26
OIM 11g.
Connector : 9.1.1.6
Connector Documnetation Followed : http://download.oracle.com/docs/cd/E11223_01/doc.910/e11205/deploy.htm#BIHFHICC
Regards,
Ashok

i'm face the same problem, have u soloved this problem . can u share me with it ?

OIM Siebel Connector Real-Time

Hi All
I am using the direct provisioning for the OIM Siebel Connector.
Can I make this provisioning process to be a real time without human intervention ?
At the current time, I am adding an LDAP resource and Siebel resource to each user manually to start the provisioning process. Is there anyway to automate this process to remove the human intervention ?
Thanks

You can create a schedule task to initiate provisioning through APIs
Or
Use Access Policy. Whenever user will get created into OIM, he will get Siebel Resource

OIM server crashes while Importing OIM AD connector config XML files

while installing OIM connector for Microsoft Active directory on the 2nd step of installation "Import of Connector XML Files (Using Deployment Manager)" Installation fails and OIM server crashes... my OIM server version is 11.1.1.3.0 and Connector is ActiveDirectory 9.1.1.5.0
Here is oim_server1-diagnostic log file
[2012-01-10T17:23:10.450+05:00] [oim_server1] [ERROR] [] [XELLERATE.ADAPTERS] [tid: [ACTIVE].ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: XELSYSADM] [ecid: 0000JJ7ZjsLFW7WFLz3V8A1F31xJ00006f,0] [APP: oim#11.1.1.3.0] [dcid: 80666d38c1d0770e:-122ffcd8:134c75e0aa6:-7ffd-00000000000001e9] Class/Method: tcAdpUtils/compileAdapter encounter some problems: Could not compile adapter : adpADCSMOVEGROUP
[2012-01-10T17:23:10.465+05:00] [oim_server1] [ERROR] [] [XELLERATE.ADAPTERS] [tid: [ACTIVE].ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: XELSYSADM] [ecid: 0000JJ7ZjsLFW7WFLz3V8A1F31xJ00006f,0] [APP: oim#11.1.1.3.0] [dcid: 80666d38c1d0770e:-122ffcd8:134c75e0aa6:-7ffd-00000000000001e9] Class/Method: tcAdpUtils/compileAdapter encounter some problems: Compile failed on Tue Jan 10 17:23:10 UZT 2012[[
error: Exception thrown while constructing Processor object: null
----------------SOURCE FILE
1: /* Copyright (c) 2001 - 2007, Oracle Corporation. All rights reserved.
2: */
3: package com.thortech.xl.adapterGlue.ScheduleItemEvents;
4: import com.thortech.xl.dataobj.*;
5: //import com.thortech.xl.adapterGlue.*;
6: //import com.thortech.xl.dataobj.tcDataSet;
7: import java.io.IOException;
8: import java.util.*;
9: import java.io.FileWriter;
10: import java.io.File;
11: import java.sql.Timestamp;
12: import java.text.DateFormat;
13: import com.thortech.xl.dataobj.util.tcAdapterTaskException;
14: import com.thortech.xl.dataobj.util.*;
15: import com.thortech.xl.dataobj.util.tcJarEntryClassLoader;
16: import com.thortech.xl.remotemanager.*;
17: import java.rmi.*;
18: import java.net.URL;
19: import java.lang.reflect.Constructor;
20: import java.lang.reflect.Method;
21: import java.lang.reflect.Modifier;
22: import java.lang.reflect.InvocationTargetException;
23: import java.lang.reflect.Field;
24: import java.net.*;
25:
26: public class adpADCSMOVEGROUP extends com.thortech.xl.adapterfactory.events.tcAdpEvent {
27: public adpADCSMOVEGROUP() {
28: super();
29: setEventName("ADCS Move Group");
30: }
31:
32: Hashtable ihTaskRetVals = new Hashtable();
33:
34: // Adapter Variables
35: String OrgName; // Organization Name
36: String sConfigurationLookUp; // ADParameterLookUp
37: long ADServer; // AD Server
38: String ObjectGUID; // ObjectGUID
39:
40: //Persistant Objects
41: Object ADconsObj;
42: Class clsAD;
43:
44: //Variables needed for class loader
45: String sURL;
46: URL url1;
47: URL[] aURL;
48: ClassLoader moURLClassLoader;
49: Class moTargetClass;
50: Object[] maoConstructorArgs;
51: Class[] masConParamTypes;
52: Constructor moCons;
53:
54: protected void implementation() throws Exception {
55:
56: try {
57:
58: if (! initAdapter("ADCS Move Group"))
59: return;
60:
61: // Run Time Variables
62: OrgName = getRunTimeValue("OrgName").toString();
63: sConfigurationLookUp = getRunTimeValue("sConfigurationLookUp").toString();
64: ADServer = ((Long)getRunTimeValue("ADServer")).longValue();
65: ObjectGUID = getRunTimeValue("ObjectGUID").toString();
66:
67: //Initialize persistant object "AD"
68: clsAD = Class.forName("com.thortech.xl.integration.ActiveDirectory.tcUtilADTasks");
69: maoConstructorArgs = new Object[]{getITAttrVal(ADServer, "Server Address"), getITAttrVal(ADServer, "Root Context"), getITAttrVal(ADServer, "Admin FQDN"), getITAttrVal(ADServer, "Admin Password"), getITAttrVal(ADServer, "Use SSL"), getITAttrVal(ADServer, "Port Number"), getITAttrVal(ADServer, "Invert Display Name"), "yes", sConfigurationLookUp, getDataBase()};
70: masConParamTypes = new Class[]{String.class, String.class, String.class, String.class, String.class, String.class, String.class, String.class, String.class, Class.forName("com.thortech.xl.dataaccess.tcDataProvider")};
71: moCons = clsAD.getConstructor(masConParamTypes);
72: ADconsObj = moCons.newInstance(maoConstructorArgs);
73:
74:
75: // Execute Tasks and store results in Hashtable...
76:
77: ihTaskRetVals.put("MOVEGROUP", MOVEGROUP());
78: // Output mapping for Task MOVEGROUP
79: setAdpRetVal(ihTaskRetVals.get("MOVEGROUP"), "String");
80:
81:
82: finalizeAdapter();
83:
84: } catch (tcAdapterTaskException e) {
85: e.printStackTrace();
86: updateSchItem("R", e.getMessage(), e.getReason());
87: return;
88: } catch (Exception e) {
89: e.printStackTrace();
90: updateSchItem("R", e.getMessage(), getReason("", e));
91: return;
92: }
93:
94: }
95:
96: // *** Move Group ***
97: private Object MOVEGROUP() throws Exception {
98: Object oRetVal = "";
99:
100: Object objCons;
101: String sTaskName = "Move Group";
102: try {
103:
104: System.out.println("Running Move Group");
105:
106: //This method uses persistent object "AD"
107:
108: // Initialize method
109: Class[] moMethodParmTypes = new Class[] {String.class, String.class, Class.forName("com.thortech.xl.dataaccess.tcDataProvider")};
110: Object[] moMethodParams = new Object[] {OrgName, ObjectGUID, getDataBase()};
111: Method moMethod = clsAD.getMethod("moveGroup", moMethodParmTypes);
112:
113: // Check for static method
114: if (Modifier.isStatic(moMethod.getModifiers()))
115: ADconsObj = null;
116:
117: // Invoke method
118: oRetVal = moMethod.invoke(ADconsObj, moMethodParams);
119:
120: } catch (Exception e) {
121: e.printStackTrace();
122: if (e instanceof InvocationTargetException) {
123: Throwable t = ((InvocationTargetException)e).getTargetException();
124: throw new tcAdapterTaskException("adpADCSMOVEGROUP", "Move Group", t.getMessage(), "", "");
125: } else {
126: throw new tcAdapterTaskException("adpADCSMOVEGROUP", "Move Group", e.getMessage(), "", "");
127: }
128: }
129: return returnVal(oRetVal);
130: }
131: }
----------------COMMAND LINE javac -classpath C:\Oracle\MIDDLE~1\WLSERV~1.3\server\ext\jdbc\oracle\11g\ojdbc6dms.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\user-patch.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\soa-startup.jar;;C:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_oepe1033\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\patch_ocp353\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Oracle\MIDDLE~1\JDK160~1\lib\tools.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;C:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.3.0.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;C:\Oracle\MIDDLE~1\modules\ORGAPA~1.1/lib/ant-all.jar;C:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\oracle.soa.common.adapters_11.1.1\oracle.soa.common.adapters.jar;C:\Oracle\MIDDLE~1\ORACLE~1\soa\modules\commons-cli-1.1.jar;C:\Oracle\MIDDLE~1\ORACLE~1\soa\modules\oracle.soa.mgmt_11.1.1\soa-infra-mgmt.jar;C:\Oracle\Middleware\Oracle_IDM1\oam\agent\modules\oracle.oam.wlsagent_11.1.1\oam-wlsagent.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.xdk_11.1.0\xsu12.jar;C:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules.xquery_10.3.1.0.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\db2jcc4.jar;C:\Oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\soa-infra;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\fabric-url-handler_11.1.1.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\quartz-all-1.6.5.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\oracle.soa.fabric_11.1.1\oracle.soa.fabric.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\oracle.soa.adapter_11.1.1\oracle.soa.adapter.jar;C:\Oracle\Middleware\Oracle_SOA1\soa\modules\oracle.soa.b2b_11.1.1\oracle.soa.b2b.jar;C:\Oracle\Middleware\Oracle_IDM1\server\lib\oim-manifest.jar;C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrf.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\common\derby\lib\derbyclient.jar;C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\xqrl.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-async.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-auth-client.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-auth-server.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-authz-service.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-configmbeans.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-context.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-entitymgr.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-kernel.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-pluginframework.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-utils.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-platform-workflowservice.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\iam-toplinksession.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlAdapterUtilities.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlAPI.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlAttestation.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlAuditor.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlAuthentication.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlBackOfficeBeans.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlBackofficeClient.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlCache.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlCrypto.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlDataObjectBeans.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlDataObjects.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlDDM.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlGenConnector.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xliGCProviders.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlInputPreprocessor.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlLogger.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlRemoteManager.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlRequestPreview.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlScheduler.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlUtils.jar;C:\Oracle\Middleware\Oracle_IDM1\server\apps\oim.ear\APP-INF\lib\xlVO.jar -d C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\\oracle\oim\adapters C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\\oracle\oim\adapters\adpADCSMOVEGROUP.java
[2012-01-10T17:23:14.075+05:00] [oim_server1] [NOTIFICATION] [] [oracle.iam.configservice.impl] [tid: [ACTIVE].ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: XELSYSADM] [ecid: 0000JJ7ZjsLFW7WFLz3V8A1F31xJ00006f,0] [APP: oim#11.1.1.3.0] [dcid: 80666d38c1d0770e:-122ffcd8:134c75e0aa6:-7ffd-00000000000001e9] Inside PostImport method of UserManagementPostImportForDm
[2012-01-10T17:23:14.450+05:00] [oim_server1] [ERROR] [] [oracle.iam.configservice.impl] [tid: [ACTIVE].ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: XELSYSADM] [ecid: 0000JJ7ZjsLFW7WFLz3V8A1F31xJ00006f,0] [APP: oim#11.1.1.3.0] [dcid: 80666d38c1d0770e:-122ffcd8:134c75e0aa6:-7ffd-00000000000001e9] The attribute ObjectGUID does not exist!
[2012-01-10T17:23:15.075+05:00] [oim_server1] [NOTIFICATION] [IAM-0080013] [oracle.iam.platform.kernel.impl] [tid: [ACTIVE].ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: XELSYSADM] [ecid: 0000JJ7ZjsLFW7WFLz3V8A1F31xJ00006f,0] [APP: oim#11.1.1.3.0] [dcid: 80666d38c1d0770e:-122ffcd8:134c75e0aa6:-7ffd-00000000000001e9] [arg: 30] [arg: 0] [arg: oracle.iam.platform.entitymgr.vo.EntityMetadata] [arg: MODIFY] Kernel executing default validation with process id, event id, entity and operation 30.0.oracle.iam.platform.entitymgr.vo.EntityMetadata.MODIFY
[2012-01-10T17:23:15.090+05:00] [oim_server1] [NOTIFICATION] [IAM-0080014] [oracle.iam.platform.kernel.impl] [tid: [ACTIVE].ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: XELSYSADM] [ecid: 0000JJ7ZjsLFW7WFLz3V8A1F31xJ00006f,0] [APP: oim#11.1.1.3.0] [dcid: 80666d38c1d0770e:-122ffcd8:134c75e0aa6:-7ffd-00000000000001e9] [arg: 30] [arg: 30] [arg: oracle.iam.platform.entitymgr.vo.EntityMetadata] [arg: MODIFY] [arg: /file/User.xml] Kernel executing default action handler with process id, event id, entity and operation 30.30.oracle.iam.platform.entitymgr.vo.EntityMetadata.MODIFY.entityId=/file/User.xml

There are different log handlers and loggers with different properties what are XELLRATE.DDM's properties
here is the logging.xml file
<?xml version="1.0" encoding="UTF-8"?>
<logging_configuration>
<log_handlers>
<log_handler name='console-handler' class='oracle.core.ojdl.logging.ConsoleHandler' formatter='oracle.core.ojdl.weblogic.ConsoleFormatter' level='WARNING:32'/>
<log_handler name='odl-handler' class='oracle.core.ojdl.logging.ODLHandlerFactory' filter='oracle.dfw.incident.IncidentDetectionLogFilter'>
<property name='path' value='${domain.home}/servers/${weblogic.Name}/logs/${weblogic.Name}-diagnostic.log'/>
<property name='maxFileSize' value='10485760'/>
<property name='maxLogSize' value='104857600'/>
<property name='encoding' value='UTF-8'/>
<property name='useThreadName' value='true'/>
<property name='supplementalAttributes' value='J2EE_APP.name,J2EE_MODULE.name,WEBSERVICE.name,WEBSERVICE_PORT.name,composite_instance_id,component_instance_id,composite_name,component_name'/>
</log_handler>
<log_handler name='wls-domain' class='oracle.core.ojdl.weblogic.DomainLogHandler' level="WARNING"/>
<log_handler name='owsm-message-handler' class='oracle.core.ojdl.logging.ODLHandlerFactory'>
<property name='path' value='${domain.home}/servers/${weblogic.Name}/logs/owsm/msglogging'/>
<property name='maxFileSize' value='10485760'/>
<property name='maxLogSize' value='104857600'/>
<property name='encoding' value='UTF-8'/>
<property name='supplementalAttributes' value='J2EE_APP.name,J2EE_MODULE.name,WEBSERVICE.name,WEBSERVICE_PORT.name'/>
</log_handler>
<log_handler name='em-log-handler' level='NOTIFICATION:32' class='oracle.core.ojdl.logging.ODLHandlerFactory' filter='oracle.dfw.incident.IncidentDetectionLogFilter'>
<property name='path' value='${domain.home}/servers/${weblogic.Name}/sysman/log/emoms.log'/>
<property name='format' value='ODL-Text'/>
<property name='useThreadName' value='true'/>
<property name='maxFileSize' value='5242880'/>
<property name='maxLogSize' value='52428800'/>
<property name='encoding' value='UTF-8'/>
</log_handler>
<log_handler name='em-trc-handler' level='TRACE:32' class='oracle.core.ojdl.logging.ODLHandlerFactory'>
<property name='logreader:' value='off'/>
<property name='path' value='${domain.home}/servers/${weblogic.Name}/sysman/log/emoms.trc'/>
<property name='format' value='ODL-Text'/>
<property name='useThreadName' value='true'/>
<property name='locale' value='en'/>
<property name='maxFileSize' value='5242880'/>
<property name='maxLogSize' value='52428800'/>
<property name='encoding' value='UTF-8'/>
</log_handler>
</log_handlers>
<loggers>
<logger name="" level="WARNING:1">
<handler name="odl-handler"/>
<handler name="wls-domain"/>
<handler name="console-handler"/>
</logger>
<logger name="oracle" level="NOTIFICATION:1"/>
<logger name="oracle.adf"/>
<logger name="oracle.adf.desktopintegration"/>
<logger name="oracle.adf.faces"/>
<logger name="oracle.adf.controller"/>
<logger name="oracle.adfinternal"/>
<logger name="oracle.adfinternal.controller"/>
<logger name="oracle.jbo"/>
<logger name="oracle.adfdt"/>
<logger name="oracle.adfdtinternal"/>
<logger name="oracle.bam"/>
<logger name="oracle.bam.common"/>
<logger name="oracle.bam.system"/>
<logger name="oracle.bam.middleware"/>
<logger name="oracle.bam.adc.security"/>
<logger name="oracle.bam.common.security"/>
<logger name="oracle.bam.adc.ejb.BamAdcServerBean"/>
<logger name="oracle.bam.reportcache.ejb.ReportCacheServerBean"/>
<logger name="oracle.bam.eventengine.ejb.EventEngineServerBean"/>
<logger name="oracle.bam.ems.ejb.EMSServerBean"/>
<logger name="oracle.bam.adc.api"/>
<logger name="oracle.bam.adc"/>
<logger name="oracle.bam.eventengine"/>
<logger name="oracle.bam.ems"/>
<logger name="oracle.bam.webservices"/>
<logger name="oracle.bam.web"/>
<logger name="oracle.bam.reportcache"/>
<logger name="oracle.bpm"/>
<logger name="oracle.bpm.analytics"/>
<logger name="oracle.integration"/>
<logger name="oracle.integration.platform.blocks.cluster"/>
<logger name="oracle.integration.platform.blocks.deploy.coordinator"/>
<logger name="oracle.integration.platform.blocks.event.saq"/>
<logger name="oracle.integration.platform.blocks.java"/>
<logger name="oracle.integration.platform.faultpolicy"/>
<logger name="oracle.integration.platform.testfwk"/>
<logger name="oracle.soa"/>
<logger name="oracle.soa.adapter"/>
<logger name="oracle.soa.b2b"/>
<logger name="oracle.soa.b2b.apptransport"/>
<logger name="oracle.soa.b2b.engine"/>
<logger name="oracle.soa.b2b.repository"/>
<logger name="oracle.soa.b2b.transport"/>
<logger name="oracle.soa.b2b.ui"/>
<logger name="oracle.soa.bpel"/>
<logger name="oracle.soa.bpel.console"/>
<logger name="oracle.soa.bpel.engine"/>
<logger name="oracle.soa.bpel.engine.activation"/>
<logger name="oracle.soa.bpel.engine.agents"/>
<logger name="oracle.soa.bpel.engine.bpel"/>
<logger name="oracle.soa.bpel.engine.compiler"/>
<logger name="oracle.soa.bpel.engine.data"/>
<logger name="oracle.soa.bpel.engine.delivery"/>
<logger name="oracle.soa.bpel.engine.deployment"/>
<logger name="oracle.soa.bpel.engine.dispatch"/>
<logger name="oracle.soa.bpel.engine.sensor"/>
<logger name="oracle.soa.bpel.engine.translation"/>
<logger name="oracle.soa.bpel.engine.ws"/>
<logger name="oracle.soa.bpel.engine.xml"/>
<logger name="oracle.soa.bpel.entity"/>
<logger name="oracle.soa.bpel.jpa"/>
<logger name="oracle.soa.bpel.system"/>
<logger name="oracle.soa.dvm"/>
<logger name="oracle.soa.management.facade.api"/>
<logger name="oracle.soa.mediator"/>
<logger name="oracle.soa.mediator.common"/>
<logger name="oracle.soa.mediator.common.cache"/>
<logger name="oracle.soa.mediator.common.error"/>
<logger name="oracle.soa.mediator.common.error.recovery"/>
<logger name="oracle.soa.mediator.common.message"/>
<logger name="oracle.soa.mediator.dispatch"/>
<logger name="oracle.soa.mediator.dispatch.resequencer.toplink"/>
<logger name="oracle.soa.mediator.filter"/>
<logger name="oracle.soa.mediator.instance"/>
<logger name="oracle.soa.mediator.management"/>
<logger name="oracle.soa.mediator.metadata"/>
<logger name="oracle.soa.mediator.monitor"/>
<logger name="oracle.soa.mediator.resequencer"/>
<logger name="oracle.soa.mediator.resequencer.besteffort"/>
<logger name="oracle.soa.mediator.resequencer.fifo"/>
<logger name="oracle.soa.mediator.resequencer.standard"/>
<logger name="oracle.soa.mediator.service"/>
<logger name="oracle.soa.mediator.serviceEngine"/>
<logger name="oracle.soa.mediator.transformation"/>
<logger name="oracle.soa.mediator.utils"/>
<logger name="oracle.soa.mediator.validation"/>
<logger name="oracle.soa.scheduler"/>
<logger name="oracle.soa.services.common"/>
<logger name="oracle.soa.services.identity"/>
<logger name="oracle.soa.services.notification"/>
<logger name="oracle.soa.services.rules"/>
<logger name="oracle.soa.services.rules.obrtrace"/>
<logger name="oracle.soa.services.workflow"/>
<logger name="oracle.soa.services.workflow.common"/>
<logger name="oracle.soa.services.workflow.evidence"/>
<logger name="oracle.soa.services.workflow.metadata"/>
<logger name="oracle.soa.services.workflow.persistency"/>
<logger name="oracle.soa.services.workflow.query"/>
<logger name="oracle.soa.services.workflow.report"/>
<logger name="oracle.soa.services.workflow.runtimeconfig"/>
<logger name="oracle.soa.services.workflow.soa"/>
<logger name="oracle.soa.services.workflow.task"/>
<logger name="oracle.soa.services.workflow.task.dispatch"/>
<logger name="oracle.soa.services.workflow.task.routing"/>
<logger name="oracle.soa.services.workflow.user"/>
<logger name="oracle.soa.services.workflow.verification"/>
<logger name="oracle.soa.services.workflow.worklist"/>
<logger name="oracle.soa.services.workflow.performance"/>
<logger name="oracle.soa.services.cmds"/>
<logger name="oracle.soa.wsif"/>
<logger name="oracle.soa.xref"/>
<logger name="oracle.sdp"/>
<logger name="oracle.sdpinternal"/>
<logger name="oracle.sdp.owlcs.customer"/>
<logger name="oracle.sdp.owlcs.config"/>
<logger name="oracle.sdp.owlcs.timer"/>
<logger name="oracle.sdp.messaging"/>
<logger name="oracle.sdp.messaging.client"/>
<logger name="oracle.sdp.messaging.driver"/>
<logger name="oracle.sdp.messaging.engine"/>
<logger name="oracle.sdp.messaging.parlayx"/>
<logger name="oracle.sdp.messaging.server"/>
<logger name="oracle.wsm"/>
<logger name="oracle.wsm.msg.logging" level="NOTIFICATION:1" useParentHandlers="false">
<handler name="owsm-message-handler"/>
<handler name="wls-domain"/>
</logger>
<logger name='oracle.sysman' level='NOTIFICATION:32' useParentHandlers='false'>
<handler name='em-log-handler'/>
<handler name='em-trc-handler'/>
</logger>
</loggers>
</logging_configuration>

ODSEE Connector Patch ID request

Hello Everyone
We are using LDAP connector 11.1.1.6 version in OIM 11.2.2. The target is SunOne and we are using it in ODSEE format.
Now, we are seeing a problem where even if the user is disabled in target and if we run 'LDAP Trusted Reconciliation' the user is not getting disabled in OIM. All the required attributes - enabledAttribute, enabledValue, disabledValue and enabledWhenNoAttribute are all set correctly.
After a research, my colleague told me that there is a patch for this bug. Can someone tell me the bug number or patch number of this solution or any other info which is helpful to me?
Thanking You in advance.
Sandeep

Not very sure but just check whether latest BP fixes your issue.
Bundle Patch Number : 11.1.2.2.5
My Oracle Support Patch Number : Patch:19718347 (Release Date: 20-Jan-2015). This is a Suite Bundle Patch with OIM OPatch Version # 19787058.
~J
Please mark the response as helpful or correct when appropriate to make it easier for others to find it

OIM 11g: Connector based on SEND / EXPECT or scripting

Hello
I have a system that I need to integrate into OIM 11g. (11.1.1.5.2) The application has a scripting engine to perform all user management functions. For example, on the system itself you would run the following from the command line:
account create 'bsmith'
account password 'password'
account permission 'login'
account group default 'enduser'
account description 'Bob Smith'
account firstname 'Bob'
account lastname 'Smith'
The account repository is a custom format, and I cannot provisioning directly to it via the DB tables, or flat file etc etc. The system, however, is running on a standard UNIX platform, so I have access to SSH into the box and issue the commands.
Question: What is the best way to implement a connector to an application that only uses a scripting engine for account management? Is there an OOTB connector that can use UNIX send/expect? What about executing a shell script with inputs for the variables needed? Can I use the standard SSH connector, and override the 'user add' command?
Thank you.

Following are the the list of mappings. The ones wth similar names are easy to guess. Notice that USR_COUNTRY is missing in the list. I have requested Oracle to log a bug for this and for any other missing fields. If accepted this should be available in the next patch.
(Mapping between user definition qualifiers on data object manager form and actual USR fields)
=== Process Definition ===
Name -> pkg_name
Type -> pkg_type
=== Object Definition ===
Object Name -> obj_name
Object Type -> obj_type
Object Target Type -> obj_order_for
=== Organization Definition ===
Organization Name -> act_name
Organization ID -> act_key
Organization Type -> act_cust_type
Organization Status -> act_status
Organization Parent ID -> parent_key
+ Organization UDFs
=== User Definition ===
User Key -> usr_key
Request Key -> req_key
Identity -> usr_fss
User Login -> usr_login
Role -> usr_emp_type
Password -> usr_password
First Name -> usr_first_name
Middle Initial -> usr_middle_name
Last Name -> usr_last_name
Disabled -> usr_disabled
Type -> usr_type
User Status -> usr_status
Manager -> usr_manager_key
Organization -> act_key
Start Date -> usr_start_date
End Date -> usr_end_date
Provisioning Date -> usr_provisoning_date
Deprovisioning Date -> usr_deprovisioning_date
Provisioned Date -> usr_provisioned_date
Deprovisioned Date -> usr_deprovisioned_date
Email Address -> usr_email
Email -> usr_email
+ User UDFs

OIM AD Connector Patching

Similar Messages

Maybe you are looking for