Archival utilities into OIM11G

Archival utilities into OIM:


In order to improve performance and have better scalability archival tools in OIM 11g are very important features. Today I will explain a bit more about this features and provide some techinical information about them.

Tasks - refers to one or more activities that comprise a process, which handles the provisioning of a resource. OIM doesn’t remove completed tasks from the active task tables.  As size of the active task tables increases. And some environments are experiencing decreased performance when managing open tasks and pending approvals.

Reconciliation -
OIM Reconciliation Manager does not remove reconciled data from the active reconciliation tables. As the size of the active reconciliation tables increases. So as tasks, you can have decreased performance during the reconciliation process.


Nowadays(OIM11G) , we have online archival that is a better option that what we had for first time into version 9. So, basically we can do archival with everything up and running without any outages , from customer perspective.



This archival utilities comes with OIM files as:
 
$OIM_HOME/db/oim/oracle/Utilities/Recon11gArchival/oim_recon_archival.sh,
$OIM_HOME/db/oim/oracle/Utilities/TaskArchival/OIM_TasksArch.sh
$OIM_HOME/db/oim/oracle/Utilities/RequestArchival/oim_request_archival.sh

I hope this helps you on your IDm project,
Thiago Leoncio.

OAM11G WLST connection issue: DomainRuntime MBeanServer is not enabled on a Managed Server.

[HOME]/common/bin/wlst.sh
wls:/offline> connect('oam_user','******','t3://thiagoleoncio_server:14099')
Connecting to t3://thiagoleoncio_server:14099 with userid oam_user ...
Successfully connected to managed Server 'oam_leoncio' that belongs to domain 'Leoncio_domain'.

Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

wls:/Leoncio_domain/serverConfig> domainRuntime()
DomainRuntime MBeanServer is not enabled on a Managed Server.


To fix this:

Instead of connect directly to OAM managed server, go to AdminServer port as oamuser and do the connection then execute domainRuntime and finish your task as below:



[HOME]/common/bin/wlst.sh
wls:/offline> connect('oam_user','******','t3://thiagoleoncio_server:7001')
Connecting to t3://thiagoleoncio_server:14099 with userid oam_user ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'Leoncio_domain'.

Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.

wls:/Leoncio_domain/serverConfig> domainRuntime()
Location changed to domainRuntime tree. This is a read-only tree with DomainMBean as the root.
For more help, use help(domainRuntime)

wls:/Leoncio_domain/domainRuntime>


I hope this helps,
Thiago Leoncio.