This article has been designed with the understanding that you know a more than basic knowledge of OIA meaning you have experience in data imports. My goal here is to express the mandatory requirements along with some best practice on importing account.
After implementing OIA on a number of real-world engagements, I’ve slowly grown tired of the 3rd party clover ETL scheduler configured OOTB for data imports. From my experience, many organizations have a centralized ETL framework for manipulations so there’s no logical justification to segregate OIA’s required ETL efforts. But what if they’re missing an ETL framework? Were talking about the minority of companies here though here’s an alterative to scheduling imports into OIA.
Around 1 year ago I came across this issue and could not find a solution. 16-ish months later and I've solved how to have OIA and OIM 11g residing on the same admin domain though on separate managed servers.
The intention here is highlight the policy violations and demonstrate the preventative SOD enforcements between policies. In this example, the word 'preventative' is used loosely. There are clear indications on the SOD enforcements though maybe not as expected.
By default, OIA will only display a maximun 500 Records. I have commonly worked with a high number of identities within OIA. Because of this, I have often had to increase the total value of identities (globalusers) displayed within the OIA GUI. Here is how to increase this value.
I experienced this failed import when trying to import some data feeds. If you've experienced OIA GUI logs before, you'll know the information is inadequate to determine the import.
So for the last two days I have been trying to get LDAP authentication working within OIA (11GR2) 11.1.1.5.4. I did manage to construct an LDAP authentication and ignored the Release notes of OIA 11.1.1.5.x stating 'OIA has Dropped Support for LDAP Authentication'.
So if you've arrived at this website looking for a solution then you will be disappointed. I've spent most of today trying to configure a Weblogic JNDI data store for an OIA database connection by following the Oracle article, ' 3.7 To Configure J2EE Data Sources for Oracle Identity Analytics (Optional)'
Rumors have it, the mechanical toy company Meccano, intentionally developed their instructions incorrectly to develop ingenuity for the developing minds. I guess Oracle are trying to adopt the same nature. If this is true, then the Identity Certification Remediation Steps follow that same ruling.
This post goes through the steps demolish the OIA environment and refresh one. This can be achieved by executing the DB version script and all it's incremental versions.
Typically, OIA would use the global user import will use the Username as the authoritative information for that identity. Based on different scenarios, OIA will treat this in a different manner.
In recent Oracle Identity Analytics versions, risk summary can be associated to all the values such as accounts, attribues, entitlements, role, policies yarda yarda yarda. Here are the steps on how to complete this
In recent Oracle Identity Analytics versions, risk summary can be associated to all the values such as accounts, attribues, entitlements, role, policies yarda yarda yarda. Here are the steps on how to complete this
I noticed that Oracle Identity Analytics (OIA) 11.1.1.5.5 is readily available though I was experiencing difficulties with the installation of the new patch. I currently had OIA 11.1.1.5.4 installed and wished to migrate it up.
Whilst importing accounts into OIA via a flat file feed, you check the progress within the import/Export logs then you're presented
with the ERROR exception level with the UTTER USELESS description of 'Unable to import accounts'
You will noticie within
OIA document under the title, '2.2.6 Importing Glossary Names' for glossary imports,
the expected schema file for 11g are as follows:
When configuring OIA with WLS server clustering environment, I noticed the following error when trying to startup WLS
Unable to start the Universal Connection Pool: oracle.ucp.UniversalConnectionPoolException: Error during pool creation in Universal Connection Pool Manager MBean: oracle.ucp.UniversalConnectionPoolException: Error during pool creation in Universal Connection Pool Manager: oracle.ucp.UniversalConnectionPoolException: Universal Connection Pool already exists in the Universal Connection Pool Manager. Universal Connection Pool cannot be added to the Universal Connection Pool Manager]
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.
I experienced this issue when I was re-deploying the same web app (OIA) from one server, to another by simply sftp'ing over the file to the new server and deploying that.
OIA will take into consideration the aggregated risk-based factors and determine the risk summary based on the
highest value based on these factor. The result will provide the risk level.