The other steps required to create a custom report within OIM 10g
Step 10: Copy SQL script into file
By continuing on with the manipulation to the store procedure file, use your SQL query from step 4 and import this information into the file.
You need to change the following:
- The SELECT into the strColumnList
The FROM into the strFromClause
The WHERE into the strWhereClause
Here is my SQL query broken up into the 3 sections:
strColumnList:= distinct usr.usr_login AS "User_Login",'||
'usr.usr_first_name AS "First_Name",'||
'usr.usr_last_name AS "Last_Name",'||
'obj.obj_name AS "Resource_Name",'||
'UD_MY_USERS.UD_MY_USERS_EMAIL AS "E-mail" ';
strFromClause := ' xelsysadm.usr',
|| 'xelsysadm.obi,'
|| 'xelsysadm.obj,'
|| 'xelsysadm.oiu,'
|| 'xelsysadm.ost,'
|| 'xelsysadm.orc,'
|| 'xelsysadm.UD_MY_USERS';
strWhereClause := ' obi.obj_key = obj.obj_key'
||' AND obi.obi_key = oiu.obi_key'
||' AND oiu.usr_key = usr.usr_key'
||' AND ost.ost_key = oiu.ost_key'
||' AND oiu.orc_key = orc.orc_key'
||' AND orc.orc_key = xelsysadm.UD_MY_USERS.orc_key'
||' AND obj.obj_name= 'MY_USERS_GTC''
|| whereclause||' ';
Step 11: Save the file
This is the store procedure file modified and complete so go ahead and save this file. Once saved, execute this whole file within SQL developer. Compile the SQL query then commit for the SQL query to take effect.
Step 12: Alter the xlWebAdmin.properties
You need to ensure that the properties have been altered from within the xlWebAdmin.properties file
Go to the xlWebAdmin.properties (located within the /WEB-INF/classes folder)
and include the following lines....
# Inserted by DR 18th September 2012 # MY USERS GTC reports STARTS report.UsersWithMYUSERSGTCResource.label.userLogin=User Login report.UsersWithMYUSERSGTCResource.label.firstName=First Name report.UsersWithMYUSERSGTCResource.label.lastName=Last Name report.UsersWithMYUSERSGTCResource.label.resourceName=Resource Name report.UsersWithMYUSERSGTCResource.label.email=E-mail report.UsersWithMYUSERSGTCResource.label.resourceStatus=Resource Status # MY USERS GTC reports ENDS
Go ahead and save this file
Step 13: Create the XML report file
Now we need to create the report and place this into the REP table. This is completed by constructing a SQL insert statement
The core component of the report is the XML within the SQL query, the top nodes are the input fields, the bottom are the output of the report. You need to ensure they match the store procedure values
Firstly, include the values you want to search for when executing the report. These values must also match to the values you included from within Step 7.
Next, ensure that the return values match the values associated with the SQL query in step 10
Finally, include the labelling of the values. These must match the values from within Step 12
Step 14: Assign permissions to view the custom report
Log in as xelsysadm
Go to users group --> Manage --> Search and select 'system administrators'
Within the drop-down list, select Allowed Reports
At the bottom left, click Assign Reports
Select the report you have imported in, and click OK
Step 15: Submitting the report
If all goes well, you can now go to Reports and execute the created report.
Note, I have deliberately placed a missing label from step 12 (e-mail) to demonstrate what it would represent if the value was missing
About the author
Daniel is a Technical Manager with over 10 years of consulting expertise in the Identity and Access Management space.Daniel has built from scratch this blog as well as technicalconfessions.com
Follow Daniel on twitter @nervouswiggles
Comments
Other Posts
AS I was migrating my environment into an S3 environment, I wanted to leverage off the SES services that AWS provide, more specifically, to leverage the off the SMTP functionality by sending an email via PHP
Read More...
The WeMos D1 is a ESP8266 WiFi based board is an extension to the current out-of-the-box library that comes with the Arduino installation. Because of this, you need to import in the libraries as well as acknowledging the specific board. This process is highly confusion with a number of different individuals talking about a number of different ways to integrate.
Read More...
NameID element must be present as part of the Subject in the Response message, please enable it in the IDP configuration.
Read More...
For what I see, there's not too many supportive documentations out there that will demonstrate how provision AD group membership with the ICF connector using OpenIDM. The use of the special ldapGroups attribute is not explained anywhere in the Integrators guides to to the date of this blog. This quick blog identifies the tasks required to provision AD group membership from OpenIDM to AD using the LDAP ICF connector. However this doesn't really explain what ldapGroups actually does and there's no real worked example of how to go from an Assignment to ldapGroups to an assigned group in AD. I wrote up a wiki article for my own reference: AD group memberships automatically to users This is just my view, others may disagree, but I think the implementation experience could be improved with some more documentation and a more detailed example here.
Read More...
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...
org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...
ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...
When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
Read More...
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...
During the reconcilation from OpenIDM to the ICF google apps connector, the following error response would occur. ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_grant
Read More...