With the intention to import many flat files in the future, I have created a stagingDR directory (with my initials included knowing that if I forget in the future, I know I created that) and within that directory I created another directory called Imports. This is where I will be dropping my data feed so OIM can acknowledge the file and import it.
I created the required steps to create a trusted Reconciliation and posted this on youtube back later 2012. I was just tired on following the Oracle documentation without them proof reading and making sure it works correctly. To counter this lazy approach that Oracle makes, I decided to make a video on this.
Most people you will come across understand that the java arguments -ms, -mx, PermSize, MaxPermSize etc. need to be set in order for there to be sufficient java memory allocation for Oracle Identity Manager 11g to run. OIM 11g compared to OIM 10g requires a tremendous amount of java allocation. More often than not, when you're running your job schedulers, process forms, or even starting up the system, you may experience "java.lang.OutOfMemoryError: PermGen space". No worries, here are the simple steps to resolve the issue.
Whilst connecting OIM with OIA, you may receive an error stating that you cannot receive the 'current Data Collection Session ID'. OIM data collection scheduler has
to be enabled, which by default it is, though you may be experiencing the following error whilst attempting to import the usr or application data.
After identifying that the registered control files are incorrect (after receiving the ORA-00205: error in identifying control file, check alert log for more info error)
though after executing the system set control files, I would receive and ORA-02095: specified initialization parameter cannot be modified error
The OIM11gR2 PS2 installation is 95% difference with the OIM11gR2 procedural installation. I was however aware that SOA patch is mandatory for the installation of OIM. When I executed the following command, I would receive the following error:
The steps required to use the exposed OIM 11gR2PS2 APIs from JDeveloper to your VM OIM instance, running on MAC and RHEL respectively. The example
below goes through a quick demonstration on how to create a user using the exposed OIM APIs
It took my a while to determine why my custom-made scheduled tasks were not showing up after following the
new 11g 'how to create a scheduled task via plugin'. Turns out the META-INF folder is an optional which contains the metadata (task definition). If you don't have
this file, you need to import the metadata file into the MDS manually.
When trying to export the metadata, probably using something such as
exportMetadata(application='OIMMetadata',server='oim_server1',toLocation='/home/oracle/Oracle/Middleware/tmp'), I would receive the following error:
When setting up the connector server key, I would receive an 'access denied' with a System.UnauthorizedAccessException trace
System.UnauthorizedAccessException: Access to the path 'C:\Program Files (x86)\Identity Connectors\Connector Server\r2dadszy.tmp' is denied.
Despite that the vague error, Remote host closed connection during handshake, maybe a result of multitude of possible reasons, the reason why this is occurring is because the remove client is dropping the connection.
I notice this issue once the WLS admin was restarted after the schedule task became unresponsive and remaining in the Interrupt status despite that I bounced the WLS managed server.
While integrating OIM 11g with the ICF connector resource for reconciliation, I would often get the following error, javax.servlet.ServletException: java.lang.InstantiationError: java.lang.VirtualMachineError after a couple of attempts: