Unlocking the AD account through Oracle Identity Manager 9.1.0.2

Hi friends,
I have a question about Oracle Identity Manager 9.1.0.2, I have configured the Active Directory connector for Identity Manager, you can perform the unlock process when the account was blocked by Active Directory failed attempts at authentication to a workstation .
Very grateful for your support

Hello,
As Sagar suggested, you could -
(1) write a task "Unlock AD account" - write code to unlock an user account in AD. Check if any such task is existing in the connector. You might be able to reuse it. If not, write your own task for this purpose.
(2) Based on your implementation, choose "Changed Password" or "Password Updated" task in your process definition. And on success of this task, add "unlock AD account" task to invoke.
(3) "self-management account unlock" will work automatically as soon as a user will reset his password. You don't have to implement anything else here.
That's it !!!
Hope this helps,

Similar Messages

  • Where can i found the download software of   oracle identity manager 9.1.0.

    where can i found the download software of oracle identity manager 9.1.0.1 Remote Manager
    . can any one help me.
    Edited by: user10545341 on Jul 29, 2011 8:19 AM

    And follow the steps to complete your task:
    Agents in Active Directory 9.1.0.2
    hope this helps,
    Thiago L Guimaraes

  • How to repair the database used by Oracle Identity Manager 11g

    Hi friends,
    I have a question about Oracle Identity Manager 11g.
    As I can repair the database used by Oracle Identity Manager 11g
    Thanks

    I think you can do if the repaired database is replica of old one.
    http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/repair.htm

  • Starting the Oracle Identity Manager 9.1.0.2 Application Cluster (OWS)

    Hello friends,
    I have a question about how to start the Oracle Identity Manager 9.1.0.2 application that is deployed on Oracle WebLogic Server (OWS) 11g on 2 nodes (OIM_SERVER_01 and OIM_SERVER_02).
    What is the procedure to start the Admin Server and then the nodes where the application is deployed Oracle Identity Manager 9.1.0.2
    I left wondering the commands:
    1. xlStartServer.sh
    2. xlStartWLS.sh
    3. xlStartManagedServer.sh
    4. startNodeManager.sh
    Thanks for the support...

    First you need to start the AdminServer by the command xlStartWLS.sh then you can start the nodemanager on the hosts where your OIM server are located via the startNodeManager.sh command and then start the OIM Server via the xlStartManagerServer.sh command. Nodemanager is required to control the managed server if you plan to control them via the weblogic admin console. If you don't want to do that via console then xlStartManagerServer.sh and xlStopNManagedServer.sh would be able to control your oim servers. There is no specific order required for starting the oim servers, just that the admin server should be in running mode before you start the managed servers.
    -Bikash

  • Install the console design of Oraclar Identity Manager 9.1.0.2 on Linux

    Hello friends,
    You can install the console design of Oracle Identity Manager 9.1.0.2 on Linux
    Thanks

    Hello,
    You can check the article: [ID 466390.1] in Metalink.
    Good luck.

  • Error when installing Oracle Identity Manager 9.1.0.1

    Hello friends,
    I installed Oracle Identity Manager 9.1.0.2 Oracle Weblogic Server on a cluster, at the time of treaties authenticated in the web console of Oracle Identity Manager, I get the following message:
    A system error was encountered.
    View the full log here
    http://pastebin.com/ucN1LHP4
    BUILD FAILED
    /opt/oim/xellerate/setup/setup.xml:447: The following error occurred while executing this line:
    /opt/oim/xellerate/setup/weblogic-setup.xml:318: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 3 failed: [Deployer:149026]deploy application Nexaweb on oimCluster.
    Target state: deploy failed on Cluster oimCluster
    javax.servlet.ServletException: [HTTP:101249][ServletContext@59809215[app:Nexaweb module:/Nexaweb path:/Nexaweb spec-version:null]]: Servlet class com.nexaweb.loader.ClientLoaderServlet for servlet ClientClassServlet could not be loaded because the requested class was not found in the classpath .
    java.lang.ClassNotFoundException: com.nexaweb.loader.ClientLoaderServlet.
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:551)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
         at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:508)
         at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:418)
         at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
         at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
         at org.apache.tools.ant.Task.perform(Task.java:348)
         at org.apache.tools.ant.Target.execute(Target.java:357)
         at org.apache.tools.ant.Target.performTasks(Target.java:385)
         at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
         at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
         at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
         at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
         at org.apache.tools.ant.Main.runBuild(Main.java:758)
         at org.apache.tools.ant.Main.startAnt(Main.java:217)
         at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
         at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
    Caused by: /opt/oim/xellerate/setup/weblogic-setup.xml:318: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 3 failed: [Deployer:149026]deploy application Nexaweb on oimCluster.
    Target state: deploy failed on Cluster oimCluster
    javax.servlet.ServletException: [HTTP:101249][ServletContext@59809215[app:Nexaweb module:/Nexaweb path:/Nexaweb spec-version:null]]: Servlet class com.nexaweb.loader.ClientLoaderServlet for servlet ClientClassServlet could not be loaded because the requested class was not found in the classpath .
    java.lang.ClassNotFoundException: com.nexaweb.loader.ClientLoaderServlet.
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:551)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
         at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.java:357)
         at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
         at sun.reflect.GeneratedMethodAccessor167.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
         at org.apache.tools.ant.Task.perform(Task.java:348)
         at org.apache.tools.ant.Target.execute(Target.java:357)
         at org.apache.tools.ant.Target.performTasks(Target.java:385)
         at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
         at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
         at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
         at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:416)
         ... 16 more
    Caused by: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 3 failed: [Deployer:149026]deploy application Nexaweb on oimCluster.
    Target state: deploy failed on Cluster oimCluster
    javax.servlet.ServletException: [HTTP:101249][ServletContext@59809215[app:Nexaweb module:/Nexaweb path:/Nexaweb spec-version:null]]: Servlet class com.nexaweb.loader.ClientLoaderServlet for servlet ClientClassServlet could not be loaded because the requested class was not found in the classpath .
    java.lang.ClassNotFoundException: com.nexaweb.loader.ClientLoaderServlet.
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:551)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
         at weblogic.Deployer.run(Deployer.java:72)
         at weblogic.Deployer.mainWithExceptions(Deployer.java:62)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy.java:419)
         at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.java:349)
         ... 28 more
    Caused by: weblogic.deploy.api.tools.deployer.DeployerException: Task 3 failed: [Deployer:149026]deploy application Nexaweb on oimCluster.
    Target state: deploy failed on Cluster oimCluster
    javax.servlet.ServletException: [HTTP:101249][ServletContext@59809215[app:Nexaweb module:/Nexaweb path:/Nexaweb spec-version:null]]: Servlet class com.nexaweb.loader.ClientLoaderServlet for servlet ClientClassServlet could not be loaded because the requested class was not found in the classpath .
    java.lang.ClassNotFoundException: com.nexaweb.loader.ClientLoaderServlet.
         at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:551)
         at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
         at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
         at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
         at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
         at weblogic.deploy.api.tools.deployer.Jsr88Operation.report(Jsr88Operation.java:542)
         at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:140)
         at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
         at weblogic.utils.compiler.Tool.run(Tool.java:158)
         at weblogic.utils.compiler.Tool.run(Tool.java:115)
         at weblogic.Deployer.run(Deployer.java:70)
         ... 35 more
    As I can solve this problem, not to reinstall everything again
    thanks

    Not sure if I understand your issue correctly. Your deployment failed during the installation and you have started the servers and trying to login?
    When installing OIM in a clustered WLS domain, the docs specify various cluster configurations needed to be completed in the WLS Admin Console before running the OIM installer. These steps DO NOT include starting up of the first managed server. In fact, if you start up the managed server then you may very well run into deployment issues after the OIM application is built. Instead, when installing OIM, the installer detects that not all nodes are on-line and so will queue the deployment for later. Deployment then takes place in later steps when you are instructed to restart the app server and start managed nodes.
    Thus was your managed server running when you were doing the installation? That has caused the issue. I would suggest to dump this domain (save the .xldatabasekey) if you don't wanna to dump the database part and start the installation again BUT don't start the managed server while doing the installation.
    HTH,
    BB

  • Error on installing Oracle Identity Manager 9.1.0.1 in WebLogic Server 11g

    Hello friends.
    Can you help solve this case:
    I installed Oracle 9.1.0.1 on Oracle Identity Manager Weblogic Server 11g, completing the installation with the following errors: attach the log so I can guide the solution.
    link of the complete log
    http://textbin.com/1c824
    Part of the log**************************************
    With the Partitioning, OLAP, Data Mining and Real Application Testing options".>
    ####<Sep 30, 2011 4:23:04 PM PET> <Info> <JDBC> <idm9> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1317417784538> <BEA-001517> <Connection Pool "xlXADS" using Driver: "Oracle JDBC driver", Version: "11.2.0.2.0".>
    ####<Sep 30, 2011 4:23:18 PM PET> <Info> <Common> <idm9> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1317417798143> <BEA-000628> <Created "30" resources for pool "xlXADS", out of which "30" are available and "0" are unavailable.>
    ####<Sep 30, 2011 4:23:18 PM PET> <Info> <JDBC> <idm9> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1317417798147> <BEA-001124> <Created Connection Pool named xlXADS.>
    ####<Sep 30, 2011 4:23:24 PM PET> <Error> <Store> <idm9> <AdminServer> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1317417804279> <BEA-280061> <The persistent store "AdminServer_OIM_JDBCSTORE" could not be deployed: weblogic.store.PersistentStoreException: Can't find JDBC DataSource jdbc/xlDS: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
    weblogic.store.PersistentStoreException: Can't find JDBC DataSource jdbc/xlDS: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
         at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:107)
         at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:186)
         at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:164)
         at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:59)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:240)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
         at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
         at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
         at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
         at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
         at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
         at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)
         at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:102)
         at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:186)
         at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:164)
         at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:59)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
         at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
         at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:187)
         at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:491)
         at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:137)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Sep 30, 2011 4:23:24 PM PET> <Warning> <Management> <idm9> <AdminServer> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1317417804321> <BEA-141197> <The deployment of AdminServer_OIM_JDBCSTORE failed.
    weblogic.management.DeploymentException:
         at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:62)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
         at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
         at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
         at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
         at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
         at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
         at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)
         at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:102)
         at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:186)
         at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:164)
         at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:59)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
         at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
         at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:187)
         at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:491)
         at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:137)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Sep 30, 2011 4:23:24 PM PET> <Error> <JMS> <idm9> <AdminServer> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1317417804381> <BEA-040123> <Failed to start JMS Server "AdminServer_OIM_JMSSERVER" due to weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist.
    weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist
         at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:313)
         at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:200)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:240)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
         at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
         at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
         at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
         at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    ####<Sep 30, 2011 4:23:24 PM PET> <Warning> <Management> <idm9> <AdminServer> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1317417804385> <BEA-141197> <The deployment of AdminServer_OIM_JMSSERVER failed.
    weblogic.management.DeploymentException: Internalrror activating the JMS Server AdminServer_OIM_JMSSERVER: weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist
         at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:215)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
         at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
         at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
         at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
         at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    Caused By: weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist
         at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:313)
         at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:200)
         at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:240)
         at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
         at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
         at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
         at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
         at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
         at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
         at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
         at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >
    Thanks

    Hi Kevin,
    Make your suggestion, delete the domain and reinstall Oracle Identity Manager, the result was the same error, this happens when I start the xlStartServer.sh
    Exception in thread "QuartzWorkerThread-2" java.lang.OutOfMemoryError: PermGen space
    at java.lang.reflect.Proxy.defineClass0(Native Method)
    at java.lang.reflect.Proxy.getProxyClass(Proxy.java:504)
    at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:581)
    at com.thortech.xl.dataaccess.tcDataBaseClient.bindToInstance(Unknown Source)
    at com.thortech.xl.dataaccess.tcDataBaseClient.<init>(Unknown Source)
    at com.thortech.xl.server.tcDataBaseClient.<init>(Unknown Source)
    at com.thortech.xl.client.dataobj.tcDataBaseClient.<init>(Unknown Source)
    at com.thortech.xl.scheduler.core.quartz.QuartzWrapper$TaskExecutionAction.run(Unknown Source)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.security.Security.runAs(Security.java:41)
    at Thor.API.Security.LoginHandler.weblogicLoginSession.runAs(Unknown Source)
    at com.thortech.xl.scheduler.core.quartz.QuartzWrapper.execute(Unknown Source)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:178)
    at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:477)
    CJava HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
    ^CJava HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
    Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
    Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
    Exception in thread "QuartzScheduler_NON_CLUSTERED_MisfireHandler" java.lang.OutOfMemoryError: PermGen space
    Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
    java.lang.OutOfMemoryError: PermGen space
    ^CJava HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
    Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
    Exception in thread "[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
    java.lang.OutOfMemoryError: PermGen space
    Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
    Thanks
    Edited by: JLK on Oct 2, 2011 11:35 PM
    Edited by: JLK on Oct 2, 2011 11:37 PM

  • Tables using  Oracle Identity Manager 11g

    Good evening friends,
    I have a query about the tables used by Identity Manager 11g.
    There is some document that tells me the tables used by Oracle Identity Manager 11g, and how they are linked.
    Very grateful for your help

    This does not exist for 11g. Only 9.x has a database diagram. Most the tables are the same, it's just the request side that is new due to the SOA integration.
    -Kevin

  • IDE for Oracle Identity Manager development?

    Hello
    What's the best IDE for Oracle Identity Manager development? which can suppose workflow, form, rule,custom adapter development etc? and is there any plug-in for this?
    thanks
    TK

    MK wrote:
    Jdeveloper has any plug-in for OIM?
    thanks
    TKOracle has an plugin developed for plugins and MDS which they have shared with some SIs. May be you can get hold of that.
    HTH,
    BB

  • How to lock the AD Account through OIM

    Hi.
    I am provisioning AD through OIM 11g using the AD Connector. I have done the create user, modified user provisioning through OIM in AD successfully without any issue.
    I would like to lock the OIM account and also lock the respective target accounts when OIM account is locked.
    I have done the following task to lock the account in OIM and also in AD through OIM. They are
    Process Definition Task
    I have created the Change Account Status task in process definition.
    This task will populate the OIM Account lock status value to the AD Account is Locked out field in the ADUSER form using the OIM API. The same API is working for all First Name, Last Name etc modification without any issue.
    Lookup Definition
    I have added the following entry in the Lookup.USR_PROCESS_TRIGGERS Lookup Definition
    Code Key : USR_LOCKED and Decode : Change Account Status
    OIM Admin Console
    I have logged into the OIM admin Console as a Administrator and I have search the user and click the Lock Account button. The OIM Account is locked , but target resource account was not locked and also Change Account Status task was not triggered by OIM.
    Do i need to do any special configuration for account lock for the target resource.
    Help is greatly appreciated.

    In your System Configuration variables, find the value for "XLUserResource.ProvisionMode". Make sure this is set to Java and not DB.
    >
    This property determines whether provisioning of the Xellerate User resource to the user's organization occurs in the database layer through stored procedure, or in the Java layer via Event Handlers.
    Note: See Oracle Fusion Middleware Developer's Guide for Oracle Identity Manager for information about Event Handlers.
    This property has the following allowed values:
    DB: Provisioning of the Xellerate User resource to the user's organization occurs in the database layer through stored procedure. This in turn does not trigger any further process. Therefore, custom tasks associated with the Xellerate User provisioning process that is associated with the Xellerate User resource does take place.
    Java: Provisioning of the Xellerate User resource to the user's organization occurs in the database layer via Event Handlers. Custom tasks associated with the Xellerate User provisioning process that is associated with the Xellerate User resource takes place. This is applicable to the upgrade scenario, where you have your own tasks associated with provisioning processes in earlier releases of Oracle Identity Manager, and you want them to run even after 11g upgrade. In such scenario, set the value of this property value to JAVA.
    >
    -Kevin

  • Load Balancer on Oracle Identity Manager 9.1.0.2

    Hello friends,
    I have configured an environment Oracle Identity Manager 9.1.0.2 on 2 nodes in Oracle WebLogic Server 11g.
    As I configured balancer Apache HTTP Server with Apache Proxy Plug-in, when loading the page through a web browser will not display the page of the web management console of Oracle Identity Manager.
    Here the result after entering the web address below: http://192.168.1.10/xlWebApp :
    (404 Not Found)
    Not Found
    The requested URL /xlWebApp was not found on this server.
    Apache/2.0.63 (Unix) DAV/2 Server at 192.168.1.10 Port 80
    Any suggestions for viewing the website of IDM through the load balancer Apache HTTP Server.
    Very grateful for the support

    httpd.conf is placed at /etc/httpd/httpd.conf, if you are using unix like systems. It's configuration file used by Apache http server. Paste its content to see what functions are configured.
    regards,
    GP

  • Error while installing oracle identity manager

    Im using windows installer. I get error below when installing Oracle Identity Manager, any idea to solve this?
    Following Error occured during schema creation connected
    ERROR loading database script C:\oracle identity manager\OIM9.0.1.1\installServer\Xellerate/db/oracle/xell.sql!
    Please contact your DBA! ORA-06550: line 1,
    column 7: PLS-00905: object KOD.PIN_OBJ is invalid ORA-06550: line 1,
    column 7: PL/SQL: Statement ignored [12/13/06 11:36 AM]
    ------------------------------------------------------------------------------

    Hi,
    I got the same error:
    Following Error occurred during schema creation connectedError loading database scriptD:\appl\OIM_902_RC\OIM_902_RC\installServer\Xellerate/db/oracle/xell.sqlPlease contact your DBA!ORA-06550: line 1, column 7: PLS-00905: object VIM_ADMIN.PIN_OBJ is invalid ORA-06550: line 1, column 7: PL/SQL: Statement ignored [12/8/06 5:57 PM]      
    But I could fix it by dropping the schema and recreate it by only executing the prepare_xl_db.sh script as dba user on database server:
    1.     Copy the scripts prepare_xl_db.sh and xell_db_prepare.sql from the distribution CD/Directory to a directory on the machine hosting the database where there is (as the account user performing this task) write permission.
    2.     Run the prepare_xl_db.sh script by entering the following command:
    ./prepare_xl_db.sh
    3.     Provide information appropriate for the database and host machine when the script prompts for the following items:
    •     The location of the Oracle home (ORACLE_HOME)
    •     The name of the database (ORACLE_SID)
    •     The name of the Oracle Identity Manager database user to be created
    •     The password for the Oracle Identity Manager database user
    •     The name of the tablespace to be created for storing Oracle Identity Manager data
    •     The directory in which to store the data file for the Oracle Identity Manager tablespace
    •     The name of the data file ( no need to append the .dbf extension)
    •     The name of the temporary tablespace
    4.     Check the prepare_xell_db.lst log file located in the directory where the xell_db_prepare script was run from to see execution status and additional information.

  • Java class integration with Oracle Identity Manager 9.1.0.2

    Hello Friends,
    I have a java class that is responsible for sending notifications, my question is how do the relationship of this class with the Oracle Identity Manager 9.1.0.2 so you can take the class and notify users when an application is approved or rejected.
    Any recommendation for this process.
    Thanks for the support
    Edited by: JLK on Jun 12, 2012 5:20 PM

    Hi
    Java class integration with OIM happen through concept of adapters. You can go through OIM documentation of how to create adapters.
    In your case you should create a process task adapetrs adn attach it on the Approved response code in your approval process.
    Desingn Console --> Process management --> Process definition --> <Apprlication Process Ex: AD User>.
    Alternatively you can also send notification using OIM OOTB email templates.
    Regards
    user12841694

  • Users reconciled into Oracle Identity Manager 9.1.0.2

    Hello friends,
    I have configured the process of reconciliation between Oracle Identity Manager and LDAP directory (Microsoft Active Directory), my question is: How I can find users who were reconciled to Oracle Identity Manager 9.1.0.2 and I have currently in Oracle through this process.
    thank you very much

    Hi,
    in design console check : Reconciliation Manager -> query for reconciliation event for resource AD.
    hope this helps.

  • Block users in Oracle Identity Manager 9.1.0.2

    Hi,
    I have a status query (User Locked) user in Oracle Identity Manager 9.1.0.2.
    The option to block users, seen in the web administration console of Oracle Identity Manager appears in a disabled state. As I can enable this functionality in Oracle Identity Manager 9 ..?
    Thanks for the support

    Didn't get your question exactly.
    Whenever someone tries to login with wrong password then he gets Locked into OIM. You'll have to go to Admin Console and Unlock it. You can also do this from DB as well.
    To lock user from Admin console, you'll have to create a custom button and extend the same action class to Lock that user into OIM.
    Workaround
    Create a UDF called LOCK.
    Create a trigger on this UDF i.e. whenever LOCK value changes to TRUE then lock the user using DB query or API (UPDATEUSER -- Users.Lock User)

Maybe you are looking for